Public report of itlibrium/DDD-starter-dotnet, published 22 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 22 October 2026, 01:02 UTC · Survey ID cd_493460cb8cce491c918ab22bc313052e

itlibrium/DDD-starter-dotnet

Measured 22 October 2026, 00:56 UTC, at code version 7950712

Supply-chain provenance & signing: not measured

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 55out of 100 At risk Down 1 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Domain Modelling 100 Exemplary Event-Driven 100 Exemplary Architecture 81 Strong Performance 78 Exemplary Code Health 70 Strong Security and Compliance 59 Adequate Maturity 50 Adequate Production Readiness 48 Adequate

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

Findings by how serious they are

32 critical 207 serious 118 minor

6 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 00:56 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

81of 86 dimensions measured by tools. The other 5 are advisory notes from an AI model, which explain the code but don't count towards the score.
321of 357 findings point to an exact file and line, so you can open each one in the code. The other 36 concern the repository as a whole, such as missing documentation.
86dimensions across 8 lenses, read from 6,758 lines of product code in 45 projects.
Chapters

Executive summary

itlibrium/DDD-starter-dotnet scores 55 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged. Watchdog judged it as a template, sample or demo, meant to be read or copied, so the dimensions about building, releasing and running a product don't apply, and its lenses are rated against a lower bar. The score itself is worked out as for any repository.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 48 and is rated Adequate. Its Domain vs controller coverage dimension scores 1 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 4 Deprecated finding(s) in Dependency Hygiene and to resolve the 1 Vulnerable finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 55 to about 59.

32 findings are critical: ten in Dependency Vulnerabilities, five in Incompleteness & stubs, five in Static Analysis (SAST), four in Explicit Debt, four in Secrets (history), three in Project dependency cycles and one in Dependency Hygiene.

Watchdog couldn't measure IL Efficiency and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 6,758 lines, which would take an estimated 0.1 person-years, around €11,000, to rebuild.

Code Health 70 Strong Architecture 81 Strong Maturity 50 Adequate, capped by Knowledge Freshness and Architecture documentation Production Readiness 48 Adequate, capped by Code Coverage, Dependency Hygiene and Domain vs controller coverage Security and Compliance 59 Adequate, capped by Dependency Vulnerabilities Domain Modelling 100 ★ Exemplary Event-Driven 100 ★ Exemplary Performance 78 ★ Exemplary

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

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

If Production Readiness rose from 48 to 70, the lowest score rated Strong, the score would rise from 55 to about 59.

Code composition: what the lines of code are Most of the hand-written code is supporting code, such as wiring, settings and declarations, and business logic is 10% of it. That is normal for a service that mainly connects other systems or stores and fetches records, and worth a look if this product is meant to hold complex business rules.
Business logic 9%Supporting code 75%Tests 5%Generated by tools 12%
New since the last survey: 42 findings

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

  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Mvc.Versioning Sources/Contacts/Contacts/Contacts.csproj
  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Mvc.Versioning Sources/Sales/Sales.RestApi/Sales.RestApi.csproj
  • Dependency Hygiene · Deprecated: xunit Sources/Sales/Sales.DeepModel.Tests/Sales.DeepModel.Tests.csproj
  • Dependency Hygiene · Deprecated: xunit Sources/Sales/Sales.ProcessModel.Tests/Sales.ProcessModel.Tests.csproj
  • Explicit Debt · Dead code: PaymentsIHttpCalls Sources/Sales/Sales.Adapters/Integrations/Payments/PaymentsInMemoryCalls.cs
  • Explicit Debt · Dead code: RiskManagementInMemoryCalls Sources/Sales/Sales.Adapters/Integrations/RiskManagementInMemoryCalls.cs
  • Explicit Debt · Dead code: InPlaceOrderEventsOutbox Sources/Sales/Sales.Adapters/Orders/InPLaceOrderEventsOutbox.cs
  • Explicit Debt · Dead code: KafkaOrderEventsOutbox Sources/Sales/Sales.Adapters/Orders/KafkaOrderEventsOutbox.cs
  • Explicit Debt · Dead code: OrderDetailsSqlRepository Sources/Sales/Sales.Adapters/Orders/OrderDetailsSqlRepository.cs
  • Explicit Debt · Dead code: RequestOrderAcceptance Sources/Sales/Sales.ProcessModel/Fulfillment/RequestOrderAcceptance.cs
  • Explicit Debt · Dead code: PaymentRequestFulfilled Sources/Sales/Sales.ProcessModel/Integrations/Payments/PaymentRequestFulfilled.cs
  • Explicit Debt · Dead code: AddPaymentRequestFor Sources/Sales/Sales.ProcessModel/Integrations/Payments/PaymentsModule.cs
  • Explicit Debt · Dead code: ProductsDeliveryModule Sources/Sales/Sales.ProcessModel/Integrations/ProductsDelivery/ProductsDeliveryModule.cs
  • Explicit Debt · Dead code: ProductLevelDiscounts2 Sources/Sales/Sales.DeepModel/Pricing/Discounts/ProductLevelDiscounts.cs
  • Explicit Debt · Dead code: AggregatedModifier Sources/Sales/Sales.DeepModel/Pricing/OfferModifier.cs
  • Explicit Debt · Dead code: GetBasePriceFor Sources/Sales/Sales.DeepModel/Pricing/PriceLists/PriceListRepository.cs
  • Explicit Debt · Dead code: HasSameDataAs Sources/TechnicalStuff/TechnicalStuff/DataEquals.cs
  • Explicit Debt · Dead code: HasSameItemsAs Sources/TechnicalStuff/TechnicalStuff/EqualsExtensions.cs
  • Explicit Debt · Dead code: HasSameItemsAs Sources/TechnicalStuff/TechnicalStuff/EqualsExtensions.cs
  • Explicit Debt · Dead code: HasSameItemsAs Sources/TechnicalStuff/TechnicalStuff/EqualsExtensions.cs
  • Explicit Debt · Dead code: NonTransactionalKafkaOutbox Sources/TechnicalStuff/TechnicalStuff.Outbox.Kafka/NonTransactionalKafkaOutbox.cs
  • Explicit Debt · Dead code: PaymentRequestFulfilled Sources/Payments/Payments.ProcessModel/Requesting/PaymentRequestFulfilled.cs
  • Explicit Debt · Dead code: OutboxBackgroundServiceSettings Sources/TechnicalStuff/TechnicalStuff.Outbox.Quartz/OutboxBackgroundServiceSettings.cs
  • Supply-chain Provenance & Signing · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Cancellation propagation · Async method without CancellationToken: GetBy Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Document.cs
  • Cancellation propagation · Async method without CancellationToken: Save Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Document.cs
  • Cancellation propagation · Async method without CancellationToken: GetBy Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EF.cs
  • Cancellation propagation · Async method without CancellationToken: Save Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EF.cs
  • Cancellation propagation · Async method without CancellationToken: GetBy Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EventsSourcing.cs
  • Cancellation propagation · Async method without CancellationToken: Save Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EventsSourcing.cs
  • Cancellation propagation · Async method without CancellationToken: GetBy Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.cs
  • Cancellation propagation · Async method without CancellationToken: Save Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.cs
  • Cancellation propagation · Async method without CancellationToken: SaveNestedDbEntities Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.Data.cs
  • Cancellation propagation · Async method without CancellationToken: Handle Sources/Sales/Sales.ProcessModel/OnlineOrdering/PlaceOrderHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle Sources/Sales/Sales.ProcessModel/OnlineOrdering/PriceCartHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle Sources/Sales/Sales.ProcessModel/WholesaleOrdering/AddToOrderHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle Sources/Sales/Sales.ProcessModel/WholesaleOrdering/ConfirmOfferHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle Sources/Sales/Sales.ProcessModel/WholesaleOrdering/CreateOrderHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle Sources/Sales/Sales.ProcessModel/WholesaleOrdering/GetOfferHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle Sources/Sales/Sales.ProcessModel/WholesaleOrdering/GetQuickQuoteHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Handle Sources/Sales/Sales.ProcessModel/WholesaleOrdering/PlaceOrderHandler.cs

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 6 findings

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

  • Coupling · Off the main sequence: Nuke.DockerCompose
  • Coupling · Off the main sequence: TechnicalStuff.Marten
  • Coupling · Off the main sequence: Search.Infrastructure
  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Mvc.Versioning
  • Dependency Hygiene · Deprecated: xunit
  • Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €11,000 · Estimate
Cost to rebuild€3,600 to €18,000, for 60 to 187 hours of work, about 0.1 person-years for one engineer
Difficulty of the problemVery 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.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeSmall: 6,758 lines of product code, of which 55% is declarations and boilerplate, 35% straight logic and 10% logic with branches

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with Contacts.csproj, Sales.RestApi.csproj, Sales.DeepModel.Tests.csproj.
Raises the score by about 5 points · Low effort · Dependency Hygiene
2
Resolve the 1 Vulnerable finding(s) in Dependency Hygiene.
Raises the score by about 4 points · Low effort · Dependency Hygiene
3
Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with REDACTED, Sales.DeepModel.Tests.csproj.
Raises the score by about 4 points · Low effort · Dependency Hygiene

Diagnosis: what the measurements show together

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

The tests miss the code that carries the risk · Common cause
Little of the code is tested: Code Coverage, which measures how much of the code the tests run, scores 3.4 out of 10. The tests that do exist are also aimed at the wrong place. Most of them exercise the entry points, the code that receives a request from outside, such as a web page asking for an order, and passes it on. The business logic, where the product makes its decisions, such as working out a price or checking that an order may ship, is tested least, and that is where a mistake changes what the product does. Writing more tests of the same kind won't close the gap, because the problem lies in which code the tests reach.
Based on: Code Coverage (3.4 out of 10) · Domain vs controller coverage
What to do: Write tests for the business logic first, starting with the decisions the product makes, and make each test check the result it produces. Then follow the Domain vs controller coverage dimension beside the overall coverage figure, because it shows how much of the business logic is tested.
Where the investment is most exposed · Value at risk
This code would cost about €11,000 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 48 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 4 Deprecated finding(s) in Dependency Hygiene. 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 4 Dependency Hygiene 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.

arch Startup Startup ctx:Contacts Contacts Contacts Startup->ctx:Contacts ctx:ProcessModel ProcessModel ProcessModel Startup->ctx:ProcessModel ctx:ProductsDelivery.ProcessModel ProductsDelivery.ProcessModel ProcessModel Startup->ctx:ProductsDelivery.ProcessModel ctx:RiskManagement.ProcessModel RiskManagement.ProcessModel ProcessModel Startup->ctx:RiskManagement.ProcessModel ctx:Sales.Adapters Sales.Adapters Adapters Startup->ctx:Sales.Adapters ctx:Sales.DeepModel Sales.DeepModel DeepModel Startup->ctx:Sales.DeepModel ctx:Sales.ProcessModel Sales.ProcessModel ProcessModel Startup->ctx:Sales.ProcessModel ctx:TechnicalStuff TechnicalStuff Api · Persistence · TechnicalStuff Startup->ctx:TechnicalStuff ctx:TechnicalStuff.ProcessModel TechnicalStuff.ProcessModel ProcessModel Startup->ctx:TechnicalStuff.ProcessModel Nuke Nuke FluentMigrations FluentMigrations Search.Startup Search.Startup ctx:Crud Crud Api · Crud ctx:Contacts->ctx:Crud ctx:Crud.Ef Crud.Ef Ef ctx:Contacts->ctx:Crud.Ef ctx:ProcessModel->ctx:TechnicalStuff.ProcessModel ctx:ProductsDelivery.ProcessModel->ctx:TechnicalStuff.ProcessModel ctx:RiskManagement.ProcessModel->ctx:TechnicalStuff.ProcessModel ctx:Sales.Adapters->ctx:ProcessModel ctx:Sales.Adapters->ctx:RiskManagement.ProcessModel ctx:Sales.Adapters->ctx:Sales.DeepModel ctx:Sales.Adapters->ctx:Sales.ProcessModel ctx:Sales.Adapters->ctx:TechnicalStuff ctx:Sales.Adapters->ctx:Crud.Ef ctx:Outbox.Kafka Outbox.Kafka Kafka ctx:Sales.Adapters->ctx:Outbox.Kafka ctx:Outbox.Postgres Outbox.Postgres Postgres ctx:Sales.Adapters->ctx:Outbox.Postgres ctx:Sales.Adapters->ctx:TechnicalStuff.ProcessModel ctx:Sales.DeepModel->ctx:TechnicalStuff ctx:Sales.DeepModel->ctx:Crud ctx:Sales.ProcessModel->ctx:Sales.DeepModel ctx:Sales.ProcessModel->ctx:TechnicalStuff.ProcessModel ctx:Crud->ctx:TechnicalStuff ctx:Crud.Ef->ctx:Crud ctx:Outbox Outbox Outbox ctx:Outbox->ctx:TechnicalStuff ctx:Outbox->ctx:TechnicalStuff.ProcessModel ctx:Outbox.Kafka->ctx:Outbox ctx:Outbox.Postgres->ctx:Outbox ctx:TechnicalStuff.ProcessModel->ctx:TechnicalStuff __more__ +20 more contexts

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.

79 modules, with 143 dependencies between them. 3 loops run through 12 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 39 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 Nuke2 Sales.Clients3 Sales.Commons4 Sales.Products5 TechnicalStuff.Crud6 TechnicalStuff.Crud.Operations.Results7 TechnicalStuff.Persistence8 TechnicalStuff.ProcessModel9 Contacts.Tags10 Payments.Requesting11 Sales.Database.Sql.Documents12 Sales.ExchangeRates13 Sales.Integrations.RiskManagement14 Sales.Pricing.Discounts15 Sales.Pricing.PriceLists16 TechnicalStuff.Crud.Operations17 TechnicalStuff.Outbox18 Contacts.Groups19 Sales.Integrations20 Sales.Pricing21 TechnicalStuff.Crud.Ef22 TechnicalStuff.Outbox.Kafka23 Contacts.Companies24 Sales.Orders.PriceChanges25 Contacts.Database26 Sales.WholesaleOrdering27 Contacts28 Sales.OnlineOrdering29 Contacts.Companies.OldApi30 Contacts.Companies.RestApi31 Contacts.Groups.OldApi32 Contacts.Groups.RestApi33 Contacts.Tags.OldApi34 Contacts.Tags.RestApi35 Sales.Fulfillment36 Sales.Orders37 Sales.Database.Sql.EF38 Sales39 Infrastructure40 Sales.Integrations.Payments
1 Nuke
2 Sales.Clients
3 Sales.Commons
4 Sales.Products
5 TechnicalStuff.Crud
6 TechnicalStuff.Crud.Operations.Results
7 TechnicalStuff.Persistence
8 TechnicalStuff.ProcessModel
9 Contacts.Tags111
10 Payments.Requesting3
11 Sales.Database.Sql.Documents13
12 Sales.ExchangeRates31
13 Sales.Integrations.RiskManagement11
14 Sales.Pricing.Discounts25613
15 Sales.Pricing.PriceLists134
16 TechnicalStuff.Crud.Operations3
17 TechnicalStuff.Outbox5
18 Contacts.Groups111
19 Sales.Integrations1111
20 Sales.Pricing376144
21 TechnicalStuff.Crud.Ef34
22 TechnicalStuff.Outbox.Kafka18
23 Contacts.Companies111
24 Sales.Orders.PriceChanges213
25 Contacts.Database111
26 Sales.WholesaleOrdering522181711614
27 Contacts111
28 Sales.OnlineOrdering21265143
29 Contacts.Companies.OldApi121
30 Contacts.Companies.RestApi11124
31 Contacts.Groups.OldApi11
32 Contacts.Groups.RestApi112
33 Contacts.Tags.OldApi11
34 Contacts.Tags.RestApi11
35 Sales.Fulfillment311
36 Sales.Orders1842121554111227
37 Sales.Database.Sql.EF15
38 Sales3111
39 Infrastructure121
40 Sales.Integrations.Payments31131
Uses a module listed above itPart of a loopThe module itself
1 Nuke2 Sales.Clients3 Sales.Commons4 Sales.Products5 TechnicalStuff.Crud6 TechnicalStuff.Crud.Operations.Results7 TechnicalStuff.Persistence8 TechnicalStuff.ProcessModel9 Contacts.Tags10 Payments.Requesting11 Sales.Database.Sql.Documents12 Sales.ExchangeRates13 Sales.Integrations.RiskManagement14 Sales.Pricing.Discounts15 Sales.Pricing.PriceLists16 TechnicalStuff.Crud.Operations17 TechnicalStuff.Outbox18 Contacts.Groups19 Sales.Integrations20 Sales.Pricing21 TechnicalStuff.Crud.Ef22 TechnicalStuff.Outbox.Kafka23 Contacts.Companies24 Sales.Orders.PriceChanges25 Contacts.Database26 Sales.WholesaleOrdering27 Contacts28 Sales.OnlineOrdering29 Contacts.Companies.OldApi30 Contacts.Companies.RestApi31 Contacts.Groups.OldApi32 Contacts.Groups.RestApi33 Contacts.Tags.OldApi34 Contacts.Tags.RestApi35 Sales.Fulfillment36 Sales.Orders37 Sales.Database.Sql.EF38 Sales39 Infrastructure40 Sales.Integrations.PaymentsNuke1Sales.Clients2Sales.Commons3Sales.Products4TechnicalStuff.Crud5TechnicalStuff.Crud.Operations.Results6TechnicalStuff.Persistence7TechnicalStuff.ProcessModel8Contacts.Tags9Payments.Requesting10Sales.Database.Sql.Documents11Sales.ExchangeRates12Sales.Integrations.RiskManagement13Sales.Pricing.Discounts14Sales.Pricing.PriceLists15TechnicalStuff.Crud.Operations16TechnicalStuff.Outbox17Contacts.Groups18Sales.Integrations19Sales.Pricing20TechnicalStuff.Crud.Ef21TechnicalStuff.Outbox.Kafka22Contacts.Companies23Sales.Orders.PriceChanges24Contacts.Database25Sales.WholesaleOrdering26Contacts27Sales.OnlineOrdering28Contacts.Companies.OldApi29Contacts.Companies.RestApi30Contacts.Groups.OldApi31Contacts.Groups.RestApi32Contacts.Tags.OldApi33Contacts.Tags.RestApi34Sales.Fulfillment35Sales.Orders36Sales.Database.Sql.EF37Sales38Infrastructure39Sales.Integrations.Payments4011131331112561313435111111137614434181112131115221817116141112126514312111124111121111311184212155411122715311112131131+39 more modules (most-connected shown)

At a glance — Code Health · 70% · Strong ·

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

At a glance — Architecture · 81% · Strong ·

The Good
D5 · .NET / C# Coupling 9.3 D6 · .NET / C# Cohesion (LCOM4) 10.0 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 9.5 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 7.7 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.9 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0
The Bad
AX2 · Repo Stateful singletons 4.8

At a glance — Maturity · 50% · Adequate · gated by D34, M2 ·

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

At a glance — Readiness · 48% · Adequate · gated by D8, D12, P9 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D11 · .NET / C# Test Reliability 10.0 D13 · .NET / C# REDACTED Scanning 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 8.9 P1 · Repo CI/CD gates 8.5 P2 · Repo Observability 5.4 P7 · Repo Outbound HTTP resilience 10.0 P8 · Repo Schema migrations 10.0
The Bad
D8 · .NET / C# Code Coverage 3.4 D12 · .NET / C# Dependency Hygiene 3.9 P6 · Repo Release Hygiene 5.0
The Ugly
P9 · Repo Domain vs controller coverage 1.0

At a glance — Security · 59% · Adequate · gated by D30 ·

The Good
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
D28 · .NET / C# Secrets (history) 6.0 D29 · .NET / C# Static Analysis (SAST) 5.0 C4 · Repo Data Retention 6.5 S1 · Repo Web-Security Posture 6.0
The Ugly
D30 · .NET / C# Dependency Vulnerabilities 1.4

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

The Good
DM10 · Repo One transaction, one aggregate 10.0 DM12 · Repo Ambient inputs in the domain 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 10.0

At a glance — Event-Driven · 100% · Exemplary ·

The Good
ED1 · Repo Handler temporal coupling 10.0 ED4 · Repo Outbox / dual-write 10.0

At a glance — Performance · 78% · Exemplary ·

The Good
PF1 · Repo Benchmark discipline 6.0 PF2 · Repo Allocation hygiene 8.4 PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures16High / Critical
A07:2025 — Authentication Failures5High / Critical
A05:2025 — Injection5High / Critical

Roadmap

Begin by addressing dependency hygiene, specifically resolving deprecated references in the Contacts, Sales REST API, and Sales Deep Model test projects, followed by fixing the single vulnerable dependency and updating outdated packages in the Monolith startup and test projects. Next, improve knowledge freshness by removing 21 orphaned files, prioritizing the Companies controller, EF CRUD data access object, and Order entity. Finally, establish a structured approach to architecture documentation by recording significant design decisions as dated documents in a dedicated ADR folder to capture context and consequences.

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

Do thisHelpsEffortDimension
Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with Contacts.csproj, Sales.RestApi.csproj, Sales.DeepModel.Tests.csproj.+5.4 ptsLowDependency Hygiene
Resolve the 1 Vulnerable finding(s) in Dependency Hygiene.+4.4 ptsLowDependency Hygiene
Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with REDACTED, Sales.DeepModel.Tests.csproj.+4.0 ptsLowDependency Hygiene
Resolve the 21 Orphaned file finding(s) in Knowledge Freshness — start with CompaniesController.cs (2), EfCrudDao.cs, Order.cs.+5.0 ptsMediumKnowledge Freshness
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+4.0 ptsMediumArchitecture documentation
Shift coverage toward the domain: aim to cover aggregates/domain services above the web layer, since that's where the costly bugs are.+3.7 ptsMediumDomain vs controller coverage
Resolve the 47 Low coverage finding(s) in Code Coverage — start with DbOrder.cs (2), EndpointVersioningProcessor.cs, VersioningServiceCollectionExtensions.cs.+3.3 ptsMediumCode Coverage
Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED, REDACTED.+1.5 ptsLowDependency Vulnerabilities

File quality

Per-file score 0–10 — a quality signature. Of 110 files carrying findings, judged against the Template bar: 1% slop · 3% mixed · 96% near-clean.

FileScoreBandWorst signal
REDACTED1.3SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.0MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.0MixedStatic Analysis (SAST): High: REDACTED
REDACTED3.7MixedDependency Vulnerabilities: Critical CVE: REDACTED
Sources/TechnicalStuff/TechnicalStuff/EqualsExtensions.cs6.0Near-cleanExplicit Debt: Dead code: HasSameItemsAs
Sources/Sales/Sales.DeepModel/Orders/Order.PriceAgreement.cs6.0Near-cleanExplicit Debt: BareSuppressMessage
Build/Nuke/Nuke.csproj6.4Near-cleanExplicit Debt: NoWarnInCsproj
Sources/TechnicalStuff/TechnicalStuff.Api/Versioning/VersioningServiceCollectionExtensions.cs6.7Near-cleanExplicit Debt: TodoComment
Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Document.cs6.7Near-cleanExplicit Debt: TodoComment
Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EF.cs6.7Near-cleanExplicit Debt: TodoComment
Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EventsSourcing.cs6.7Near-cleanExplicit Debt: TodoComment
Sources/Sales/Sales.DeepModel/Products/ProductAmount.cs6.7Near-cleanExplicit Debt: BareSuppressMessage
Sources/Sales/Sales.DeepModel/Pricing/Offer.cs6.7Near-cleanExplicit Debt: TodoComment
Sources/Sales/Sales.DeepModel/Pricing/Discounts/ProductLevelDiscounts.cs6.7Near-cleanExplicit Debt: Dead code: ProductLevelDiscounts2
Sources/Sales/Sales.DeepModel/Orders/Order.Item.cs6.7Near-cleanExplicit Debt: BareSuppressMessage
REDACTED6.7Near-cleanDependency Vulnerabilities: High CVE: REDACTED
Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs7.1Near-cleanCode Duplication: Duplicated block (13 lines × 2)
REDACTED7.2Near-cleanSecrets (history): REDACTED: REDACTED
REDACTED7.2Near-cleanSecrets (history): REDACTED: REDACTED
REDACTED7.2Near-cleanSecrets (history): REDACTED: REDACTED

How the grades work

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

Critical — 32

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

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

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

Could not be resolved — 6

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 81 of 86 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 86 dimensions across the health lenses
D1D2D3D4D5D6D8D9D10D11D12D13D14D15D17D18D19D21D24D26D27D28D29D30D34D35D44AX1AX10AX2AX3AX4AX5AX6AX8AX9C4DM10DM12DM6DM8DM9ED1ED4ED5GD1IC1M1M2M3M4P1P2P6P7P8P9PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1611b-b6d4-7e77-ae6d-9b0655ca7dee.

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.

  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 207 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 3 hold 1.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • 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. `Sources/Contacts/Contacts/Companies/OldApi/NamespaceInfo.cs`, `Sources/Contacts/Contacts/ContactsEfDao.cs`, `Sources/Monolith.Startup/Infrastructure/FakeMessageConsumer.cs`, `Sources/Payments/Payments.ProcessModel/Requesting/PaymentRequestFulfilled.cs`, `Sources/Payments/Payments.ProcessModel/Requesting/RequestPayment.cs`, … (+71 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet build` exited 0, so the repository built; our search of the build output found no first-party assembly to read. That is a gap in how we locate build output, not a property of this repository.
  • 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 ToolchainServer (Sources/Monolith.Startup). the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'REDACTED'`: , CallSiteChain callSiteChain, Int32 slot) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.GetCallSite(ServiceDescriptor serviceDescriptor, CallSiteChain callSiteChain)…; runtime evidence skipped (launch chosen because REDACTED is a Microsoft.NET.Sdk.Web project).
  • P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 31 further occurrence(s) are not listed individually; the score already reflects all 71.

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

The LLM boundary

LLM-set scores this run (5): D19, D21, D24, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic 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.

D2 · Cognitive Complexity10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

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

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md.

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

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

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

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

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

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

7 duplicated block group(s) detected.

Duplicated block (9 lines × 2) · ×3Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:88
Duplicated block (5 lines × 2) · ×2Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:64
Duplicated block (13 lines × 2)Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:128
Duplicated block (14 lines × 2)Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:43

What to do

  1. Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with CompaniesController.cs (2), GroupsController.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with CompaniesController.cs, TagsController.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with CompaniesController.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling9.3 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

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

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

Off the main sequence: Payments.DeepModel · ×4Sources/Payments/Payments.DeepModel/Payments.DeepModel.csproj:1

What to do

  1. Resolve the 4 Off the main sequence finding(s) in Coupling — start with Payments.DeepModel.csproj, RiskManagement.DeepModel.csproj, ProductsDelivery.DeepModel.csproj. — One of this dimension's main actionable groups (4 warning-level).
  2. 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.

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 33 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage3.4 / 10Weak✓ 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 3.4 / 10 · rule-coverage 100% · ceiling Verified

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

Low coverage: Sources/TechnicalStuff/TechnicalStuff.Api/Versioning/EndpointVersioningProcessor.cs · ×47Sources/TechnicalStuff/TechnicalStuff.Api/Versioning/EndpointVersioningProcessor.cs:1
CRAP 30: PriceAgreement.CanChangePrice · ×4Sources/Sales/Sales.DeepModel/Orders/Order.PriceAgreement.cs:37
CRAP 42: PricesConfirmed.PricesConfirmed.ctor · ×3Sources/Sales/Sales.DeepModel/Orders/Order.Events.cs:51
No test project references Search.InfrastructureSources/Search/Search.Infrastructure/Search.Infrastructure.csproj
No test project references Sales.FluentMigrationsREDACTED

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

What to do

  1. Resolve the 47 Low coverage finding(s) in Code Coverage — start with DbOrder.cs (2), EndpointVersioningProcessor.cs, VersioningServiceCollectionExtensions.cs. — One of this dimension's main actionable groups (47 warning-level).
  2. Resolve the 4 CRAP 30 finding(s) in Code Coverage — start with Order.PriceAgreement.cs (2), Order.cs, EndpointVersioningProcessor.cs. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 3 CRAP 42 finding(s) in Code Coverage — start with Order.Events.cs, Order.cs, ValueObjectExtensions.cs. — One of this dimension's main actionable groups (3 warning-level).
  4. 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.

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

18 test methods: 16 unit, 2 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 18 tests.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

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.

D12 · Dependency Hygiene3.9 / 10Weak✓ 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 3.9 / 10 · rule-coverage 100% · ceiling Verified

20 outdated, 1 vulnerable, 2 deprecated packages.

Vulnerable: Marten
Deprecated: Microsoft.AspNetCore.Mvc.Versioning · ×4Sources/Contacts/Contacts/Contacts.csproj:21
Outdated: Scrutor · ×2REDACTED:22
Outdated: JetBrains.Annotations · ×18

What to do

  1. Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with Contacts.csproj, Sales.RestApi.csproj, Sales.DeepModel.Tests.csproj. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with REDACTED, Sales.DeepModel.Tests.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
  4. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 369 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 42 direct `PackageReference`(s), and 208 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.

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.

D17 · Explicit Debt7.1 / 10Adequategated by 4 critical findings✓ Tool-verified

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

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

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

27 deducted debt markers + 19 dead symbols across 6758 LoC in the .NET projects (1.4/KLoC) → score 7.1.

WriteOnlyPrivateField · ×2Sources/Search/Search.Infrastructure/Products/ProductElasticRepository.cs:8
NoWarnInCsproj · ×2Build/Nuke/Nuke.csproj:6
TodoComment · ×19Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.cs:51
Dead code: PaymentsIHttpCalls · ×19Sources/Sales/Sales.Adapters/Integrations/Payments/PaymentsInMemoryCalls.cs:21
BareSuppressMessage · ×4Sources/Sales/Sales.DeepModel/Commons/Money.cs:52

What to do

  1. Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ProductElasticRepository.cs, PostgresOutboxRepository.cs. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with Nuke.csproj (2). — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 19 TodoComment finding(s) in Explicit Debt — start with AllOrderDetails.cs (2), CompaniesController.cs, CrossCuttingConcerns.cs. — One of this dimension's main actionable groups (19 warning-level).
  4. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D18 · Solution Shape8.8 / 10Strong✓ 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 8.8 / 10 · rule-coverage 100% · ceiling Documented

45 projects, 316 source files, 7167 hand-written lines of code (6758 production / 409 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 1017 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 79 inter-project edges.

Thin analysable surface across projects: Payments.Adapters.Api · ×6Sources/Payments/Payments.Adapters.Api/Payments.Adapters.Api.csproj

What to do

  1. Resolve the 6 Thin analysable surface across projects finding(s) in Solution Shape — start with Payments.Adapters.Api.csproj, Payments.Adapters.Out.csproj, RiskManagement.Adapters.Api.csproj. — One of this dimension's main actionable groups (6 recommendation-level).

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

D19 · Documentation QualityAdequate◐ 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 Adequate / 10 · rule-coverage 100% · ceiling Documented

The root README is clear and well-structured: a strong 'About' section explaining what the project is (a DDD starter for .NET showing various implementation options with guidelines), a dedicated 'What *DDD starter* is not?' disclaimer, and an outline naming every visible section. It is clipped mid-outline but does not show any of the per-directory READMEs or architecture docs that would contradict it; the quality is high given the absence of architecture documentation.

XML-doc coverage: Contacts · ×41Sources/Contacts/Contacts/Contacts.csproj

What to do

  1. Improve Documentation Quality — currently 6.0/10. — The root README is clear and well-structured: a strong 'About' section explaining what the project is (a DDD starter for .NET showing various implementation options with guidelines), a dedicated 'What *DDD starter* is not?' disclaimer, and an outline naming every visible section. It is clipped mid-outline but does not show any of the per-directory READMEs or architecture docs that would contradict it; the quality is high given the absence of architecture documentation.

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

1 naming inconsistencies across 200 sampled symbols.

Inconsistent verb form in test method names: 'ResultIs' uses a present tense clause, while 'CanDividedByInteger' uses a modal verb with a past participle ('Divided') instead of the base form ('Divide').

✓ On the Gold path — maintain.

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

D24 · Comment ValueExemplary◐ Sampled · advisory

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

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

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

16 valuable / 0 redundant across 19 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

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

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

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

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

0 of 45 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability9.5 / 10Exemplary✓ 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 9.5 / 10 · rule-coverage 100% · ceiling Documented

90 % of calls cross a namespace and 10 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)6.0 / 10Adequate✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

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

5 finding(s): 0 critical, 5 high, 0 medium, 0 low. 1 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 76 file(s) — `Sources/Contacts/Contacts/Companies/OldApi/NamespaceInfo.cs` (lines 6–8), `Sources/Contacts/Contacts/ContactsEfDao.cs` (lines 7–9), `Sources/Monolith.Startup/Infrastructure/FakeMessageConsumer.cs` (lines 7–9, line 10), `Sources/Payments/Payments.ProcessModel/Requesting/PaymentRequestFulfilled.cs` (line 5), `Sources/Payments/Payments.ProcessModel/Requesting/RequestPayment.cs` (line 5), … (+71 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 75 of those file(s) — `Sources/Contacts/Contacts/ContactsEfDao.cs`, `Sources/Monolith.Startup/Infrastructure/FakeMessageConsumer.cs`, `Sources/Payments/Payments.ProcessModel/Requesting/PaymentRequestFulfilled.cs`, `Sources/Payments/Payments.ProcessModel/Requesting/RequestPayment.cs`, `Sources/Sales/Sales.Adapters/Database/Sql/EF/SalesDbContext.cs`, … (+70 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 2 of those file(s) — `Sources/Contacts/Contacts/ContactsEfDao.cs`, `Sources/Sales/Sales.Adapters/SalesCrudEfDao.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D30 · Dependency Vulnerabilities1.4 / 10Critical✓ 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 1.4 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

21 of 21 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Sources/TechnicalStuff/TechnicalStuff.Crud.Ef/EfCrudDao.cs. Counted over 21 of the 313 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×21Sources/TechnicalStuff/TechnicalStuff.Crud.Ef/EfCrudDao.cs:1
Dormant codebase

What to do

  1. Resolve the 21 Orphaned file finding(s) in Knowledge Freshness — start with CompaniesController.cs (2), EfCrudDao.cs, Order.cs. — One of this dimension's main actionable groups (21 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change 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.

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

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.

AX10 · Code composition7.7 / 10Strong✓ Tool-verified

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

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons4.8 / 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.

  • `MessageTypes` is a singleton (one shared instance) but mutates instance state outside any lock (_id2Type, _type2Id; e.g. `_id2Type` at line 21). — Sources/TechnicalStuff/TechnicalStuff.ProcessModel/MessageTypes.cs:3

What to do

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

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

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

  • The namespaces MyCompany.ECommerce.Contacts.Companies ↔ MyCompany.ECommerce.Contacts.Groups ↔ MyCompany.ECommerce.Contacts.Tags depend on each other. The lightest dependency in the cycle is MyCompany.ECommerce.Contacts.Companies → MyCompany.ECommerce.Contacts.Groups (MyCompany.ECommerce.Contacts.Companies.CompanyGroup → MyCompany.ECommerce.Contacts.Groups.Group, 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. — Sources/Contacts/Contacts/Companies/CompanyGroup.cs:2
  • The namespaces MyCompany.ECommerce.Sales.ExchangeRates ↔ MyCompany.ECommerce.Sales.Pricing ↔ MyCompany.ECommerce.Sales.Pricing.Discounts depend on each other. The lightest dependency in the cycle is MyCompany.ECommerce.Sales.ExchangeRates → MyCompany.ECommerce.Sales.Pricing (MyCompany.ECommerce.Sales.ExchangeRates.ExchangeRate → MyCompany.ECommerce.Sales.Pricing.PriceModifier, 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. — Sources/Sales/Sales.DeepModel/ExchangeRates/ExchangeRate.cs:3
  • The namespaces MyCompany.ECommerce.Sales ↔ MyCompany.ECommerce.Sales.Database.Sql.Documents ↔ MyCompany.ECommerce.Sales.Database.Sql.EF ↔ MyCompany.ECommerce.Sales.OnlineOrdering ↔ MyCompany.ECommerce.Sales.Orders ↔ MyCompany.ECommerce.Sales.WholesaleOrdering depend on each other. The lightest dependency in the cycle is MyCompany.ECommerce.Sales → MyCompany.ECommerce.Sales.Database.Sql.EF (MyCompany.ECommerce.Sales.SalesCrudEfDao → MyCompany.ECommerce.Sales.Database.Sql.EF.SalesDbContext, 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. — Sources/Sales/Sales.Adapters/SalesCrudEfDao.cs:2

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

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation9.9 / 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.

  • `CrudOperations` declares 20 members under just 7 distinct name(s): `Entities`, `CheckIfExists`, `Create`, `Read`, `Read`, `Read`, `Read`, `Read`, `Update`, `Update`, `Update`, `Update`, `Update`, `Update`, `Update`, `Update`, `Update`, `Update`, `Delete`, `SaveChanges`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 20 separate responsibilities: a caller binds to 7 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 20 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — Sources/TechnicalStuff/TechnicalStuff.Crud/Operations/CrudOperations.cs:7

What to do

  • Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
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.

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.

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

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

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

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

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged

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

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

DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged

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.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

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.

ED4 · Outbox / dual-write10.0 / 10Exemplary○ Nothing flagged

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.

ED5 · Idempotency8.9 / 10Exemplary◐ 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.

  • `WholesaleOrdering.AddToOrderHandler.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. — Sources/Sales/Sales.ProcessModel/WholesaleOrdering/AddToOrderHandler.cs:14
  • `WholesaleOrdering.PlaceOrderHandler.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. — Sources/Sales/Sales.ProcessModel/WholesaleOrdering/PlaceOrderHandler.cs:17

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.
GD1 · Unfinished & placeholder code9.8 / 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. (×18) — Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.cs:47, Sources/Sales/Sales.Adapters/Clients/ClientSqlRepository.cs:8, Sources/Sales/Sales.Adapters/Integrations/Payments/PaymentsInMemoryCalls.cs:14, …

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs5.5 / 10Adequate✓ 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.

  • `Handle` is a shipped member whose body only throws — and it is REACHED: Sources/Sales/Sales.ProcessModel/Fulfillment/OrderPlacedHandler.cs:16 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — Sources/Sales/Sales.ProcessModel/Fulfillment/OrderPlacedHandler.cs:21
  • `Handle` is a shipped member whose body only throws — and it is REACHED: Sources/Sales/Sales.ProcessModel/Fulfillment/OrderPlacedHandler.cs:17 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — Sources/Sales/Sales.ProcessModel/Fulfillment/OrderPlacedHandler.cs:27
  • `GetUnprocessedMessagesFor` is a shipped member whose body only throws — and it is REACHED: Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxProcessor.cs:32 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:16
  • `SaveCurrentOffset` is a shipped member whose body only throws — and it is REACHED: Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxProcessor.cs:41 references it (1 further site(s) in this project). This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:22
  • `MoveToUnprocessableMessages` is a shipped member whose body only throws — and it is REACHED: Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxProcessor.cs:66 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:27
  • `SearchV2` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.cs:47
  • `Handle` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×3) — Sources/Payments/Payments.ProcessModel/Requesting/RequestPaymentHandler.cs:10, Sources/ProductsDelivery/ProductsDelivery.ProcessModel/Requesting/RequestDeliveryHandler.cs:10, Sources/RiskManagement/RiskManagement.ProcessModel/Publication/GetRiskScoreHandler.cs:10
  • `GetStatusFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Sources/Sales/Sales.Adapters/Clients/ClientSqlRepository.cs:8
  • `AddPaymentRequestFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — Sources/Sales/Sales.Adapters/Integrations/Payments/PaymentsInMemoryCalls.cs:14, Sources/Sales/Sales.Adapters/Integrations/Payments/PaymentsInMemoryCalls.cs:24
  • `GetMaxOrderTotalCostFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Sources/Sales/Sales.Adapters/Integrations/RiskManagementInMemoryCalls.cs:10
  • `GetFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — Sources/Sales/Sales.Adapters/Pricing/Discounts/DiscountsSqlRepository.cs:11, Sources/Sales/Sales.Adapters/Pricing/Discounts/DiscountsSqlRepository.cs:14
  • `GetBasePriceFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Sources/Sales/Sales.Adapters/Pricing/PriceListSqlRepository.cs:13
  • `GetBasePricesFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Sources/Sales/Sales.Adapters/Pricing/PriceListSqlRepository.cs:16
  • `PostgresOutboxRepository` has 4 unfinished members out of 4 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented. — Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:6
  • `Save` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:11
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×6) — Sources/Sales/Sales.DeepModel/Orders/Order.cs:28, Sources/Sales/Sales.DeepModel/Orders/Order.cs:66, Sources/Sales/Sales.DeepModel/Orders/Order.cs:108, …
  • `Down`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional. — Sources/Sales/Sales.FluentMigrations/Raw/2022/AddOrderTables.cs:34

What to do

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

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

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

What to do

  • Add a README to the 45 of 45 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation2.0 / 10Weak✓ Tool-verified

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

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

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

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure8.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.

  • Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.

What to do

  • Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
M4 · Documentation accuracy10.0 / 10Exemplary◐ 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.

P1 · CI/CD gates8.5 / 10Exemplary✓ Tool-verified

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.

What to do

  • Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability5.4 / 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 8/17 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 17, 7 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P6 · Release Hygiene5.0 / 10Adequate✓ 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.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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.

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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.

P9 · Domain vs controller coverage1.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether test coverage concentrates on the domain (business rules) rather than the trivial web/controller layer — a focus check a generic tool can't make.

Method: Roslyn plus test-execution analysis: domain-layer versus trivial web/controller coverage ratio. Computed metric, deterministic.

  • Domain coverage is 0% but the web/controller layer is at 21% — the trivial layer is better tested than the business rules. Coverage effort should concentrate where the invariants and decisions live (the domain), not on thin controllers/endpoints.

What to do

  • Shift coverage toward the domain: aim to cover aggregates/domain services above the web layer, since that's where the costly bugs are.
PF1 · Benchmark discipline6.0 / 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.

  • No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

  • Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF2 · Allocation hygiene8.4 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

  • Raise allocation-aware density on the hot paths — currently 41 use(s) across 8,701 production line(s) (~4.7/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ 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.

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. (×2) — Sources/Monolith.Startup/Program.cs:17, Sources/Search.Startup/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. (×2) — Sources/Monolith.Startup/Program.cs:17, Sources/Search.Startup/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.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

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

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

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

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

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

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

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

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

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

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

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

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

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

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

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `connection` is a `NpgsqlConnection`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `BeginTransaction` 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 connection = …;`), which releases it at the end of the scope on every path including a throw. — Sources/TechnicalStuff/TechnicalStuff.Postgres/PostgresTransactionProvider.cs:21

What to do

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

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation4.8 / 10Adequate✓ Tool-verified

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

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

  • Only 10/80 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×39) — Sources/Sales/Sales.RestApi/OnlineOrdering/OffersController.cs:17, Sources/Sales/Sales.RestApi/OnlineOrdering/OrdersController.cs:22, Sources/Sales/Sales.RestApi/OnlineOrdering/OrdersController.cs:31, …

What to do

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

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

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

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

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

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

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

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

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

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

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

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

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

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

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

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

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

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

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

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

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

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

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

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

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

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

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

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

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

X5 · Nullable reference types9.3 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

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

What to do

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

Reference — by lens

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

LensScoreRatingImpact
Code Health70%StrongSolid.
Architecture81%StrongSolid.
Maturity50%Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness48%Adequate — gated by D8, D12, P9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security59%Adequate — gated by D30Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling100%ExemplaryStrongest area.
Event-Driven100%ExemplarySolid.
Performance78%ExemplarySolid.
Unscored — 3 check(s) recorded observations but carry no score

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

  • D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • 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 — 3 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.
  • 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.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 41 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 service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'REDACTED'`: , CallSiteChain callSiteChain, Int32 slot) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.GetCallSite(ServiceDescriptor serviceDescriptor, CallSiteChain callSiteChain)…; runtime evidence skipped (launch chosen because REDACTED is a Microsoft.NET.Sdk.Web project) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — This is a dotnet-new template — at-rest encryption and key-vaulting are deferred to the application you build from it. Add ASP.NET Data Protection / column encryption + a key vault for your real data store when you productionise.
  • C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — small single-context codebase (6,758 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 76 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — IL not measured — no first-party assembly was located after a successful build
  • 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 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
  • DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
  • DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
  • DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
  • ED3 Event naming — no domain or integration events detected — event-naming check not applicable
  • ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an event-store package (Marten/EventStore))
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 32 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Unfinished stub · ×5
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.ProcessModel/Fulfillment/OrderPlacedHandler.cs:21 — `Handle` is a shipped member whose body only throws — and it is REACHED: Sources/Sales/Sales.ProcessModel/Fulfillment/OrderPlacedHandler.cs:16 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.ProcessModel/Fulfillment/OrderPlacedHandler.cs:27 — `Handle` is a shipped member whose body only throws — and it is REACHED: Sources/Sales/Sales.ProcessModel/Fulfillment/OrderPlacedHandler.cs:17 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:16 — `GetUnprocessedMessagesFor` is a shipped member whose body only throws — and it is REACHED: Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxProcessor.cs:32 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:22 — `SaveCurrentOffset` is a shipped member whose body only throws — and it is REACHED: Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxProcessor.cs:41 references it (1 further site(s) in this project). This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:27 — `MoveToUnprocessableMessages` is a shipped member whose body only throws — and it is REACHED: Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxProcessor.cs:66 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
D28 · Secrets (history) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX3 · Project dependency cycles · Namespace dependency cycle · ×3
  • Namespace dependency cycle Sources/Contacts/Contacts/Companies/CompanyGroup.cs:2 — The namespaces MyCompany.ECommerce.Contacts.Companies ↔ MyCompany.ECommerce.Contacts.Groups ↔ MyCompany.ECommerce.Contacts.Tags depend on each other. The lightest dependency in the cycle is MyCompany.ECommerce.Contacts.Companies → MyCompany.ECommerce.Contacts.Groups (MyCompany.ECommerce.Contacts.Companies.CompanyGroup → MyCompany.ECommerce.Contacts.Groups.Group, 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 Sources/Sales/Sales.DeepModel/ExchangeRates/ExchangeRate.cs:3 — The namespaces MyCompany.ECommerce.Sales.ExchangeRates ↔ MyCompany.ECommerce.Sales.Pricing ↔ MyCompany.ECommerce.Sales.Pricing.Discounts depend on each other. The lightest dependency in the cycle is MyCompany.ECommerce.Sales.ExchangeRates → MyCompany.ECommerce.Sales.Pricing (MyCompany.ECommerce.Sales.ExchangeRates.ExchangeRate → MyCompany.ECommerce.Sales.Pricing.PriceModifier, 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 Sources/Sales/Sales.Adapters/SalesCrudEfDao.cs:2 — The namespaces MyCompany.ECommerce.Sales ↔ MyCompany.ECommerce.Sales.Database.Sql.Documents ↔ MyCompany.ECommerce.Sales.Database.Sql.EF ↔ MyCompany.ECommerce.Sales.OnlineOrdering ↔ MyCompany.ECommerce.Sales.Orders ↔ MyCompany.ECommerce.Sales.WholesaleOrdering depend on each other. The lightest dependency in the cycle is MyCompany.ECommerce.Sales → MyCompany.ECommerce.Sales.Database.Sql.EF (MyCompany.ECommerce.Sales.SalesCrudEfDao → MyCompany.ECommerce.Sales.Database.Sql.EF.SalesDbContext, 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.
D17 · Explicit Debt · WriteOnlyPrivateField · ×2
  • WriteOnlyPrivateField Sources/Search/Search.Infrastructure/Products/ProductElasticRepository.cs:8 — private SearchDb _db — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:9 — private MainDb _db — 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.
D17 · Explicit Debt · NoWarnInCsproj · ×2
  • NoWarnInCsproj Build/Nuke/Nuke.csproj:6 — CS0649 — 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 Build/Nuke/Nuke.csproj:6 — CS0169 — 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.
D30 · Dependency Vulnerabilities · Critical CVE · ×2
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Vulnerable · ×1
  • Vulnerable: Marten — REDACTED — Critical severity. https://github.com/advisories/[GHSA redacted]
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 207 finding(s)
D8 · Code Coverage · Low coverage · ×47
  • Low coverage: Sources/TechnicalStuff/TechnicalStuff.Api/Versioning/EndpointVersioningProcessor.cs Sources/TechnicalStuff/TechnicalStuff.Api/Versioning/EndpointVersioningProcessor.cs:1 — 0.0% line coverage (0/42).
  • Low coverage: Sources/TechnicalStuff/TechnicalStuff.Api/Versioning/VersioningServiceCollectionExtensions.cs Sources/TechnicalStuff/TechnicalStuff.Api/Versioning/VersioningServiceCollectionExtensions.cs:1 — 44.0% line coverage (11/25).
  • Low coverage: Sources/Monolith.Startup/Infrastructure/FakeMessageConsumer.cs Sources/Monolith.Startup/Infrastructure/FakeMessageConsumer.cs:1 — 0.0% line coverage (0/44).
  • Low coverage: Sources/Sales/Sales.Adapters/FakeMessageBroker.cs Sources/Sales/Sales.Adapters/FakeMessageBroker.cs:1 — 0.0% line coverage (0/22).
  • Low coverage: Sources/Sales/Sales.Adapters/Time/SystemClock.cs Sources/Sales/Sales.Adapters/Time/SystemClock.cs:1 — 0.0% line coverage (0/5).
  • Low coverage: Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Document.cs Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Document.cs:1 — 0.0% line coverage (0/24).
  • Low coverage: Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EF.cs Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EF.cs:1 — 0.0% line coverage (0/31).
  • Low coverage: Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EventsSourcing.cs Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EventsSourcing.cs:1 — 21.9% line coverage (7/32).
  • Low coverage: Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EventsSourcing.Data.cs Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EventsSourcing.Data.cs:1 — 0.0% line coverage (0/7).
  • Low coverage: Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.cs Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.cs:1 — 0.0% line coverage (0/24).
  • Low coverage: Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.Data.cs Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.Data.cs:1 — 0.0% line coverage (0/51).
  • Low coverage: Sources/Sales/Sales.Adapters/Database/Sql/EF/DbOrder.cs Sources/Sales/Sales.Adapters/Database/Sql/EF/DbOrder.cs:1 — 0.0% line coverage (0/8).
  • Low coverage: Sources/Sales/Sales.Adapters/Database/Sql/EF/SalesDbContext.cs Sources/Sales/Sales.Adapters/Database/Sql/EF/SalesDbContext.cs:1 — 0.0% line coverage (0/37).
  • Low coverage: Sources/Sales/Sales.Adapters/Database/Sql/Documents/DbOrder.cs Sources/Sales/Sales.Adapters/Database/Sql/Documents/DbOrder.cs:1 — 0.0% line coverage (0/8).
  • Low coverage: Sources/TechnicalStuff/TechnicalStuff/EqualsExtensions.cs Sources/TechnicalStuff/TechnicalStuff/EqualsExtensions.cs:1 — 0.0% line coverage (0/45).
  • Low coverage: Sources/TechnicalStuff/TechnicalStuff/HashCodeExtensions.cs Sources/TechnicalStuff/TechnicalStuff/HashCodeExtensions.cs:1 — 0.0% line coverage (0/13).
  • Low coverage: Sources/TechnicalStuff/TechnicalStuff/ValueObjects/ValueObjectExtensions.cs Sources/TechnicalStuff/TechnicalStuff/ValueObjects/ValueObjectExtensions.cs:1 — 0.0% line coverage (0/23).
  • Low coverage: Sources/Sales/Sales.DeepModel/Products/Amount.cs Sources/Sales/Sales.DeepModel/Products/Amount.cs:1 — 0.0% line coverage (0/13).
  • Low coverage: Sources/Sales/Sales.DeepModel/Products/ProductAmount.cs Sources/Sales/Sales.DeepModel/Products/ProductAmount.cs:1 — 0.0% line coverage (0/16).
  • Low coverage: Sources/Sales/Sales.DeepModel/Products/ProductId.cs Sources/Sales/Sales.DeepModel/Products/ProductId.cs:1 — 0.0% line coverage (0/8).
  • Low coverage: Sources/Sales/Sales.DeepModel/Products/ProductUnit.cs Sources/Sales/Sales.DeepModel/Products/ProductUnit.cs:1 — 0.0% line coverage (0/11).
  • Low coverage: Sources/Sales/Sales.DeepModel/Pricing/CalculatePrices.cs Sources/Sales/Sales.DeepModel/Pricing/CalculatePrices.cs:1 — 0.0% line coverage (0/17).
  • Low coverage: Sources/Sales/Sales.DeepModel/Pricing/IndividualSalesConditions.cs Sources/Sales/Sales.DeepModel/Pricing/IndividualSalesConditions.cs:1 — 0.0% line coverage (0/9).
  • Low coverage: Sources/Sales/Sales.DeepModel/Pricing/Offer.cs Sources/Sales/Sales.DeepModel/Pricing/Offer.cs:1 — 0.0% line coverage (0/30).
  • Low coverage: Sources/Sales/Sales.DeepModel/Pricing/OfferModifiers.cs Sources/Sales/Sales.DeepModel/Pricing/OfferModifiers.cs:1 — 0.0% line coverage (0/14).
  • + 22 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×39
  • Async method without CancellationToken: PriceCart Sources/Sales/Sales.RestApi/OnlineOrdering/OffersController.cs:17 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Place Sources/Sales/Sales.RestApi/OnlineOrdering/OrdersController.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Get Sources/Sales/Sales.RestApi/OnlineOrdering/OrdersController.cs:31 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ConfirmOffer Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersConfirmedOfferController.cs:21 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Create Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersController.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Get Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersController.cs:32 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetOffer Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersCurrentOfferController.cs:17 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Read Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersHeaderController.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Create Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersHeaderNotesController.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Read Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersHeaderNotesController.cs:30 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Update Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersHeaderNotesController.cs:37 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Delete Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersHeaderNotesController.cs:44 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CheckIfOrderExists Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersHeaderNotesController.cs:50 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Add Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersItemsController.cs:20 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Place Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersPlacementController.cs:17 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetQuote Sources/Sales/Sales.RestApi/WholesaleOrdering/QuotesController.cs:17 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetBy Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Document.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Save Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Document.cs:36 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetBy Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EF.cs:31 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Save Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EF.cs:45 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetBy Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EventsSourcing.cs:27 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Save Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EventsSourcing.cs:43 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetBy Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.cs:18 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Save Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.cs:35 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SaveNestedDbEntities Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.Data.cs:73 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 14 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×19
  • TodoComment Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.cs:51 — // TODO: search using full text search in postgresql — 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 Sources/Monolith.Startup/DI/CrossCuttingConcerns.cs:26 — // TODO: registering types — 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 Sources/Monolith.Startup/DI/Modules/Sales.cs:30 — // TODO: Same connection provider for all data access libraries (EF, Marten, RepoDB) — 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 Sources/Monolith.Startup/Program.cs:46 — // TODO: additional media types in Open API documents — 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 Sources/Sales/Sales.Adapters/Orders/OrderDetailsSqlRepository.cs:3 — // TODO: implementation for all persistence options used for OrderRepository — 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 Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Document.cs:38 — // TODO: document versioning — 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 Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EF.cs:51 — // TODO: error when not all tracked orders are explicitly saved — 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 Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.EventsSourcing.cs:45 — // TODO: event versioning — 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 Sources/Sales/Sales.DeepModel/Orders/AllOrderDetails.cs:10 — //TODO: DomainModel + Raw — 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 Sources/Sales/Sales.DeepModel/Orders/AllOrderDetails.cs:15 — // TODO: invoicing details, notes, etc. — 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 Sources/Sales/Sales.DeepModel/Pricing/Offer.cs:58 — // TODO: real Equals and GetHashCode — 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 Sources/Sales/Sales.ProcessModel/OnlineOrdering/OrderDetails.cs:8 — // TODO: subset of data from AllAOderDetails — 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 Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersConfirmedOfferController.cs:25 — // TODO: change to SeeOther — 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 Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersPlacementController.cs:20 — // TODO: change to SeeOther — 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 Sources/Sales/Sales.RestApi/WholesaleOrdering/OrdersItemsController.cs:29 — // TODO: RemoveOrderItem — 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 Sources/TechnicalStuff/TechnicalStuff.Api/Versioning/VersioningServiceCollectionExtensions.cs:38 — // TODO: better schemas naming - configuration (attributes, fluent api, etc.) — 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 Sources/TechnicalStuff/TechnicalStuff.Outbox.Kafka/TransactionalKafkaOutbox.cs:26 — // TODO: flexible serialization (json, avro, etc. - Kafka specific) — 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 Sources/TechnicalStuff/TechnicalStuff.Outbox.Quartz/OutboxJob.cs:6 — // TODO: deleting processed messages in separate Job — 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 Sources/TechnicalStuff/TechnicalStuff.Postgres/PostgresConnectionProvider.cs:7 — // TODO: Upgrade to Npgsql 7.x when possible (now Marten is incompatible) and use NpgsqlDataSource
D17 · Explicit Debt · Dead code · ×19
  • Dead code: PaymentsIHttpCalls Sources/Sales/Sales.Adapters/Integrations/Payments/PaymentsInMemoryCalls.cs:21 — NamedType PaymentsIHttpCalls — Roslyn's SymbolFinder walked every project the solution loads, including Sales.Adapters, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: RiskManagementInMemoryCalls Sources/Sales/Sales.Adapters/Integrations/RiskManagementInMemoryCalls.cs:8 — NamedType RiskManagementInMemoryCalls — Roslyn's SymbolFinder walked every project the solution loads, including Sales.Adapters, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: InPlaceOrderEventsOutbox Sources/Sales/Sales.Adapters/Orders/InPLaceOrderEventsOutbox.cs:6 — NamedType InPlaceOrderEventsOutbox — Roslyn's SymbolFinder walked every project the solution loads, including Sales.Adapters, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: KafkaOrderEventsOutbox Sources/Sales/Sales.Adapters/Orders/KafkaOrderEventsOutbox.cs:8 — NamedType KafkaOrderEventsOutbox — Roslyn's SymbolFinder walked every project the solution loads, including Sales.Adapters, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: OrderDetailsSqlRepository Sources/Sales/Sales.Adapters/Orders/OrderDetailsSqlRepository.cs:4 — NamedType OrderDetailsSqlRepository — Roslyn's SymbolFinder walked every project the solution loads, including Sales.Adapters, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: RequestOrderAcceptance Sources/Sales/Sales.ProcessModel/Fulfillment/RequestOrderAcceptance.cs:5 — NamedType RequestOrderAcceptance — Roslyn's SymbolFinder walked every project the solution loads, including Sales.ProcessModel, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: PaymentRequestFulfilled Sources/Sales/Sales.ProcessModel/Integrations/Payments/PaymentRequestFulfilled.cs:3 — NamedType PaymentRequestFulfilled — Roslyn's SymbolFinder walked every project the solution loads, including Sales.ProcessModel, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: AddPaymentRequestFor Sources/Sales/Sales.ProcessModel/Integrations/Payments/PaymentsModule.cs:8 — Method AddPaymentRequestFor — Roslyn's SymbolFinder walked every project the solution loads, including Sales.ProcessModel, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ProductsDeliveryModule Sources/Sales/Sales.ProcessModel/Integrations/ProductsDelivery/ProductsDeliveryModule.cs:5 — NamedType ProductsDeliveryModule — Roslyn's SymbolFinder walked every project the solution loads, including Sales.ProcessModel, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ProductLevelDiscounts2 Sources/Sales/Sales.DeepModel/Pricing/Discounts/ProductLevelDiscounts.cs:31 — NamedType ProductLevelDiscounts2 — Roslyn's SymbolFinder walked every project the solution loads, including Sales.DeepModel, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: AggregatedModifier Sources/Sales/Sales.DeepModel/Pricing/OfferModifier.cs:16 — NamedType AggregatedModifier — Roslyn's SymbolFinder walked every project the solution loads, including Sales.DeepModel, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: GetBasePriceFor Sources/Sales/Sales.DeepModel/Pricing/PriceLists/PriceListRepository.cs:12 — Method GetBasePriceFor — Roslyn's SymbolFinder walked every project the solution loads, including Sales.DeepModel, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: HasSameDataAs Sources/TechnicalStuff/TechnicalStuff/DataEquals.cs:5 — Method HasSameDataAs — Roslyn's SymbolFinder walked every project the solution loads, including TechnicalStuff, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: HasSameItemsAs Sources/TechnicalStuff/TechnicalStuff/EqualsExtensions.cs:5 — Method HasSameItemsAs — Roslyn's SymbolFinder walked every project the solution loads, including TechnicalStuff, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: HasSameItemsAs Sources/TechnicalStuff/TechnicalStuff/EqualsExtensions.cs:37 — Method HasSameItemsAs — Roslyn's SymbolFinder walked every project the solution loads, including TechnicalStuff, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: HasSameItemsAs Sources/TechnicalStuff/TechnicalStuff/EqualsExtensions.cs:51 — Method HasSameItemsAs — Roslyn's SymbolFinder walked every project the solution loads, including TechnicalStuff, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: NonTransactionalKafkaOutbox Sources/TechnicalStuff/TechnicalStuff.Outbox.Kafka/NonTransactionalKafkaOutbox.cs:5 — NamedType NonTransactionalKafkaOutbox — Roslyn's SymbolFinder walked every project the solution loads, including TechnicalStuff.Outbox.Kafka, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: PaymentRequestFulfilled Sources/Payments/Payments.ProcessModel/Requesting/PaymentRequestFulfilled.cs:5 — NamedType PaymentRequestFulfilled — Roslyn's SymbolFinder walked every project the solution loads, including Payments.ProcessModel, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: OutboxBackgroundServiceSettings Sources/TechnicalStuff/TechnicalStuff.Outbox.Quartz/OutboxBackgroundServiceSettings.cs:3 — NamedType OutboxBackgroundServiceSettings — Roslyn's SymbolFinder walked every project the solution loads, including TechnicalStuff.Outbox.Quartz, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
GD1 · Unfinished & placeholder code · Unfinished stub · ×18
  • Unfinished stub — throws NotImplementedException Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.cs:47 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Clients/ClientSqlRepository.cs:8 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Integrations/Payments/PaymentsInMemoryCalls.cs:14 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Integrations/Payments/PaymentsInMemoryCalls.cs:24 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Integrations/RiskManagementInMemoryCalls.cs:10 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Pricing/Discounts/DiscountsSqlRepository.cs:11 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Pricing/Discounts/DiscountsSqlRepository.cs:14 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Pricing/PriceListSqlRepository.cs:13 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Pricing/PriceListSqlRepository.cs:16 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.ProcessModel/Fulfillment/OrderPlacedHandler.cs:21 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.ProcessModel/Fulfillment/OrderPlacedHandler.cs:27 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:11 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:16 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:22 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:27 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Payments/Payments.ProcessModel/Requesting/RequestPaymentHandler.cs:10 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/ProductsDelivery/ProductsDelivery.ProcessModel/Requesting/RequestDeliveryHandler.cs:10 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/RiskManagement/RiskManagement.ProcessModel/Publication/GetRiskScoreHandler.cs:10 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×13
  • Unfinished stub — throws NotImplementedException Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.cs:47 — `SearchV2` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Payments/Payments.ProcessModel/Requesting/RequestPaymentHandler.cs:10 — `Handle` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/ProductsDelivery/ProductsDelivery.ProcessModel/Requesting/RequestDeliveryHandler.cs:10 — `Handle` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/RiskManagement/RiskManagement.ProcessModel/Publication/GetRiskScoreHandler.cs:10 — `Handle` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Clients/ClientSqlRepository.cs:8 — `GetStatusFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Integrations/Payments/PaymentsInMemoryCalls.cs:14 — `AddPaymentRequestFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Integrations/Payments/PaymentsInMemoryCalls.cs:24 — `AddPaymentRequestFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Integrations/RiskManagementInMemoryCalls.cs:10 — `GetMaxOrderTotalCostFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Pricing/Discounts/DiscountsSqlRepository.cs:11 — `GetFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Pricing/Discounts/DiscountsSqlRepository.cs:14 — `GetFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Pricing/PriceListSqlRepository.cs:13 — `GetBasePriceFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/Sales/Sales.Adapters/Pricing/PriceListSqlRepository.cs:16 — `GetBasePricesFor` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:11 — `Save` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
D30 · Dependency Vulnerabilities · Medium CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Deprecated · ×4
  • Deprecated: Microsoft.AspNetCore.Mvc.Versioning Sources/Contacts/Contacts/Contacts.csproj:21 — Microsoft.AspNetCore.Mvc.Versioning 5.1.0 — Other — the publisher's replacement is `Asp.Versioning.Mvc`; migrate the reference to it.
  • Deprecated: Microsoft.AspNetCore.Mvc.Versioning Sources/Sales/Sales.RestApi/Sales.RestApi.csproj:20 — Microsoft.AspNetCore.Mvc.Versioning 5.1.0 — Other — the publisher's replacement is `Asp.Versioning.Mvc`; migrate the reference to it.
  • Deprecated: xunit Sources/Sales/Sales.DeepModel.Tests/Sales.DeepModel.Tests.csproj:19 — xunit 2.8.0 — 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 Sources/Sales/Sales.ProcessModel.Tests/Sales.ProcessModel.Tests.csproj:18 — xunit 2.8.0 — 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.
D17 · Explicit Debt · BareSuppressMessage · ×4
  • BareSuppressMessage Sources/Sales/Sales.DeepModel/Commons/Money.cs:52 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage Sources/Sales/Sales.DeepModel/Orders/Order.Item.cs:23 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage Sources/Sales/Sales.DeepModel/Orders/Order.PriceAgreement.cs:34 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage Sources/Sales/Sales.DeepModel/Products/ProductAmount.cs:17 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
D5 · Coupling · Off the main sequence · ×4
  • Off the main sequence: Payments.DeepModel Sources/Payments/Payments.DeepModel/Payments.DeepModel.csproj:1 — Payments.DeepModel: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: RiskManagement.DeepModel Sources/RiskManagement/RiskManagement.DeepModel/RiskManagement.DeepModel.csproj:1 — RiskManagement.DeepModel: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: ProductsDelivery.DeepModel Sources/ProductsDelivery/ProductsDelivery.DeepModel/ProductsDelivery.DeepModel.csproj:1 — ProductsDelivery.DeepModel: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: TechnicalStuff Sources/TechnicalStuff/TechnicalStuff/TechnicalStuff.csproj:1 — TechnicalStuff: abstractness 0.17, instability 0.00, distance 0.83 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
D8 · Code Coverage · CRAP 30 · ×4
  • CRAP 30: PriceAgreement.CanChangePrice Sources/Sales/Sales.DeepModel/Orders/Order.PriceAgreement.cs:37 — 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: PriceAgreement.IsValidOn Sources/Sales/Sales.DeepModel/Orders/Order.PriceAgreement.cs:45 — 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: Order.ConfirmPrices Sources/Sales/Sales.DeepModel/Orders/Order.cs:46 — 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: EndpointVersioningProcessor.OperationIsForSingleVersion Sources/TechnicalStuff/TechnicalStuff.Api/Versioning/EndpointVersioningProcessor.cs:21 — Cyclomatic 5 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:88 — Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:88-96 | Sources/Contacts/Contacts/Companies/RestApi/CompaniesGroupsController.cs:42-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:117 — Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:117-125 | Sources/Contacts/Contacts/Companies/RestApi/CompaniesTagsController.cs:42-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Sources/Contacts/Contacts/Groups/OldApi/GroupsController.cs:58 — Sources/Contacts/Contacts/Groups/OldApi/GroupsController.cs:58-66 | Sources/Contacts/Contacts/Groups/RestApi/GroupsTagsController.cs:42-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/Contacts/Contacts/Groups/OldApi/GroupsController.cs:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D8 · Code Coverage · CRAP 42 · ×3
  • CRAP 42: PricesConfirmed.PricesConfirmed.ctor Sources/Sales/Sales.DeepModel/Orders/Order.Events.cs:51 — 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: Order.ApplyPriceAgreements Sources/Sales/Sales.DeepModel/Orders/Order.cs:77 — 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: ValueObjectExtensions.GetValueObjectsMeta Sources/TechnicalStuff/TechnicalStuff/ValueObjects/ValueObjectExtensions.cs:7 — Cyclomatic 6 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D36 · Supply-chain Provenance & Signing REDACTED · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • Duplicated block (5 lines × 2) Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:64 — Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:64-68 | Sources/Contacts/Contacts/Companies/RestApi/CompaniesAddressController.cs:35-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) Sources/Contacts/Contacts/Tags/OldApi/TagsController.cs:26 — Sources/Contacts/Contacts/Tags/OldApi/TagsController.cs:26-30 | Sources/Contacts/Contacts/Tags/RestApi/TagsController.cs:27-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
ED5 · Idempotency · Non-idempotent mutation · ×2
  • Non-idempotent mutation: WholesaleOrdering.AddToOrderHandler.Handle Sources/Sales/Sales.ProcessModel/WholesaleOrdering/AddToOrderHandler.cs:14 — `WholesaleOrdering.AddToOrderHandler.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.
  • Non-idempotent mutation: WholesaleOrdering.PlaceOrderHandler.Handle Sources/Sales/Sales.ProcessModel/WholesaleOrdering/PlaceOrderHandler.cs:17 — `WholesaleOrdering.PlaceOrderHandler.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 · ×1
  • Stateful singleton: MessageTypes Sources/TechnicalStuff/TechnicalStuff.ProcessModel/MessageTypes.cs:3 — `MessageTypes` is a singleton (one shared instance) but mutates instance state outside any lock (_id2Type, _type2Id; e.g. `_id2Type` at line 21).
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:128 — Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:128-140 | Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.cs:78-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:43 — Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:43-56 | Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.cs:57-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D8 · Code Coverage · No test project references Search.Infrastructure · ×1
  • No test project references Search.Infrastructure Sources/Search/Search.Infrastructure/Search.Infrastructure.csproj — No test project in this repository references Search.Infrastructure (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 13.5% 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 Sales.FluentMigrations · ×1
  • No test project references Sales.FluentMigrations REDACTED — No test project in this repository references Sales.FluentMigrations (2 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 13.5% 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 Search.Api · ×1
  • No test project references Search.Api Sources/Search/Search.Api/Search.Api.csproj — No test project in this repository references Search.Api (2 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 13.5% 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 Payments.Adapters.Api · ×1
  • No test project references Payments.Adapters.Api Sources/Payments/Payments.Adapters.Api/Payments.Adapters.Api.csproj — No test project in this repository references Payments.Adapters.Api (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 13.5% 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 Payments.Adapters.Out · ×1
  • No test project references Payments.Adapters.Out Sources/Payments/Payments.Adapters.Out/Payments.Adapters.Out.csproj — No test project in this repository references Payments.Adapters.Out (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 13.5% 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 ProductsDelivery.Adapters.Api · ×1
  • No test project references ProductsDelivery.Adapters.Api Sources/ProductsDelivery/ProductsDelivery.Adapters.Api/ProductsDelivery.Adapters.Api.csproj — No test project in this repository references ProductsDelivery.Adapters.Api (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 13.5% 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 ProductsDelivery.Adapters.Out · ×1
  • No test project references ProductsDelivery.Adapters.Out Sources/ProductsDelivery/ProductsDelivery.Adapters.Out/ProductsDelivery.Adapters.Out.csproj — No test project in this repository references ProductsDelivery.Adapters.Out (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 13.5% 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 RiskManagement.Adapters.Api · ×1
  • No test project references RiskManagement.Adapters.Api Sources/RiskManagement/RiskManagement.Adapters.Api/RiskManagement.Adapters.Api.csproj — No test project in this repository references RiskManagement.Adapters.Api (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 13.5% 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 RiskManagement.Adapters.Out · ×1
  • No test project references RiskManagement.Adapters.Out Sources/RiskManagement/RiskManagement.Adapters.Out/RiskManagement.Adapters.Out.csproj — No test project in this repository references RiskManagement.Adapters.Out (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 13.5% 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 Search.Startup · ×1
  • No test project references Search.Startup Sources/Search.Startup/Search.Startup.csproj — No test project in this repository references Search.Startup (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 13.5% 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 56 · ×1
  • CRAP 56: EqualsExtensions.HasSameItemsAs Sources/TechnicalStuff/TechnicalStuff/EqualsExtensions.cs:5 — Cyclomatic 7 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
IC1 · Incompleteness & stubs · Skeleton type · ×1
  • Skeleton type — most members are unfinished Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxRepository.cs:6 — `PostgresOutboxRepository` has 4 unfinished members out of 4 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented.
P9 · Domain vs controller coverage · Inverted test priorities · ×1
  • Inverted test priorities: domain under-tested vs controllers — Domain coverage is 0% but the web/controller layer is at 21% — the trivial layer is better tested than the business rules. Coverage effort should concentrate where the invariants and decisions live (the domain), not on thin controllers/endpoints.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×1
  • Disposable created and abandoned in the method that made it Sources/TechnicalStuff/TechnicalStuff.Postgres/PostgresTransactionProvider.cs:21 — `connection` is a `NpgsqlConnection`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `BeginTransaction` 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 connection = …;`), which releases it at the end of the scope on every path including a throw.
Minor — 59 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×21
  • Orphaned file Sources/TechnicalStuff/TechnicalStuff.Crud.Ef/EfCrudDao.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 Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.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 Sources/Sales/Sales.DeepModel/Orders/Order.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 Sources/TechnicalStuff/TechnicalStuff.Crud.Api/CrudControllerExtensions.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 Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/PostgresOutboxProcessor.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 Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.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 Sources/Sales/Sales.DeepModel/Commons/Percentage.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 Sources/Sales/Sales.Adapters/Orders/OrderSqlRepository.Raw.Data.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 Sources/Contacts/Contacts/Database/ContactsDbContext.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 Sources/Monolith.Startup/DI/Modules/Sales.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 Sources/TechnicalStuff/TechnicalStuff.Persistence/TrackedSet.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 Sources/TechnicalStuff/TechnicalStuff.Crud/Operations/CrudOperations.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 Sources/Monolith.Startup/Program.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 Sources/Sales/Sales.DeepModel/Pricing/Offer.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 Sources/Sales/Sales.ProcessModel/WholesaleOrdering/ConfirmOfferHandler.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 Sources/TechnicalStuff/TechnicalStuff.Postgres/PostgresTransactionProvider.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 Sources/Sales/Sales.DeepModel/Commons/Money.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 Sources/Monolith.Startup/Infrastructure/FakeMessageConsumer.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 Sources/Sales/Sales.DeepModel/Orders/Order.Events.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 Sources/TechnicalStuff/TechnicalStuff.Outbox.Kafka/KafkaOutboxMessageProcessor.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 Sources/Sales/Sales.DeepModel/Orders/Order.PriceAgreement.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.
D18 · Solution Shape · Thin analysable surface across projects · ×6
  • Thin analysable surface across projects: Payments.Adapters.Api Sources/Payments/Payments.Adapters.Api/Payments.Adapters.Api.csproj — 6 project(s) carry only a thin slice of real code; `Payments.Adapters.Api` has 10 significant line(s). The mean analysable-surface weight is 85 %; this project lowers Solution Shape by about 0.2 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
  • Thin analysable surface across projects: Payments.Adapters.Out Sources/Payments/Payments.Adapters.Out/Payments.Adapters.Out.csproj — 6 project(s) carry only a thin slice of real code; `Payments.Adapters.Out` has 10 significant line(s). The mean analysable-surface weight is 85 %; this project lowers Solution Shape by about 0.2 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
  • Thin analysable surface across projects: RiskManagement.Adapters.Api Sources/RiskManagement/RiskManagement.Adapters.Api/RiskManagement.Adapters.Api.csproj — 6 project(s) carry only a thin slice of real code; `RiskManagement.Adapters.Api` has 10 significant line(s). The mean analysable-surface weight is 85 %; this project lowers Solution Shape by about 0.2 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
  • Thin analysable surface across projects: RiskManagement.Adapters.Out Sources/RiskManagement/RiskManagement.Adapters.Out/RiskManagement.Adapters.Out.csproj — 6 project(s) carry only a thin slice of real code; `RiskManagement.Adapters.Out` has 10 significant line(s). The mean analysable-surface weight is 85 %; this project lowers Solution Shape by about 0.2 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
  • Thin analysable surface across projects: ProductsDelivery.Adapters.Api Sources/ProductsDelivery/ProductsDelivery.Adapters.Api/ProductsDelivery.Adapters.Api.csproj — 6 project(s) carry only a thin slice of real code; `ProductsDelivery.Adapters.Api` has 10 significant line(s). The mean analysable-surface weight is 85 %; this project lowers Solution Shape by about 0.2 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
  • Thin analysable surface across projects: ProductsDelivery.Adapters.Out Sources/ProductsDelivery/ProductsDelivery.Adapters.Out/ProductsDelivery.Adapters.Out.csproj — 6 project(s) carry only a thin slice of real code; `ProductsDelivery.Adapters.Out` has 10 significant line(s). The mean analysable-surface weight is 85 %; this project lowers Solution Shape by about 0.2 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
IC1 · Incompleteness & stubs · Commented-out code · ×6
  • Commented-out code Sources/Sales/Sales.DeepModel/Orders/Order.cs:28 — 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 Sources/Sales/Sales.DeepModel/Orders/Order.cs:66 — 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 Sources/Sales/Sales.DeepModel/Orders/Order.cs:108 — 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 Sources/Sales/Sales.RestApi/OnlineOrdering/OrdersController.cs:26 — 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 Sources/TechnicalStuff/TechnicalStuff.Crud.Api/CrudControllerExtensions.cs:126 — 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 Sources/TechnicalStuff/TechnicalStuff.Crud.Api/CrudControllerExtensions.cs:127 — 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 · ×3
  • 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 Sources/Monolith.Startup/Program.cs:17 — 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 Sources/Search.Startup/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.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×3
  • 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 Sources/Monolith.Startup/Program.cs:17 — 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 Sources/Search.Startup/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.
X10 · Duplicated predicate · Duplicated predicate · ×3
  • Duplicated predicate Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:37 — `name == null || company.Name.Contains(name)` appears character-identically in 2 files — Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs, Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.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 Sources/Contacts/Contacts/Groups/OldApi/GroupsController.cs:26 — `name == null || group.Name.Contains(name)` appears character-identically in 2 files — Sources/Contacts/Contacts/Groups/OldApi/GroupsController.cs, Sources/Contacts/Contacts/Groups/RestApi/GroupsController.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 Sources/Sales/Sales.DeepModel/Orders/Order.cs:115 — `other is not null && Id.Equals(other.Id)` appears character-identically in 2 files — Sources/Sales/Sales.DeepModel/Orders/Order.Item.cs, Sources/Sales/Sales.DeepModel/Orders/Order.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D12 · Dependency Hygiene · Outdated · ×2
  • Outdated: Scrutor REDACTED:22 — Scrutor 4.2.2 → 7.0.0 available (referenced by Monolith.Startup).
  • Outdated: coverlet.collector Sources/Sales/Sales.DeepModel.Tests/Sales.DeepModel.Tests.csproj:24 — coverlet.collector 6.0.2 → 10.1.0 available (referenced by Sales.DeepModel.Tests).
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: CrudOperations (20 members) Sources/TechnicalStuff/TechnicalStuff.Crud/Operations/CrudOperations.cs:7 — `CrudOperations` declares 20 members under just 7 distinct name(s): `Entities`, `CheckIfExists`, `Create`, `Read`, `Read`, `Read`, `Read`, `Read`, `Update`, `Update`, `Update`, `Update`, `Update`, `Update`, `Update`, `Update`, `Update`, `Update`, `Delete`, `SaveChanges`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 20 separate responsibilities: a caller binds to 7 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 20 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
D21 · Naming Consistency · Inconsistent verb form in test method names · ×1
  • Inconsistent verb form in test method names: 'ResultIs' uses a present tense clause, while 'CanDividedByInteger' uses a modal verb with a past participle ('Divided') instead of the base form ('Divide'). — Standardize test names to use the base form of the verb after 'Can' (e.g., 'CanDivideByInteger') or consistent clause structure. (symbols: MyCompany.ECommerce.Sales.Commons.MoneyTests.ResultIs(decimal, MyCompany.ECommerce.Sales.Commons.Currency), MyCompany.ECommerce.Sales.Commons.MoneyTests.CanDividedByInteger())
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 21 of 21 significant files have no living knowledge — the codebase as a whole is dormant, not 21 separate risks. Counted over 21 of the 313 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Member throws NotSupportedException · ×1
  • Member throws NotSupportedException Sources/Sales/Sales.FluentMigrations/Raw/2022/AddOrderTables.cs:34 — `Down`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional.
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.
M3 · Folder & project structure · No tests/ separation · ×1
  • No tests/ separation — Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 8/17 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 17, 7 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
PF1 · Benchmark discipline · No performance benchmarks · ×1
  • No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 10/80 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 40/42 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 — 16 suppression(s) across the 42349 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Minor — 59 finding(s)
D19 · Documentation Quality · XML-doc coverage · ×41
  • XML-doc coverage: Contacts Sources/Contacts/Contacts/Contacts.csproj — Contacts: 0 % XML-doc coverage (0/143).
  • XML-doc coverage: Monolith.Startup REDACTED — Monolith.Startup: 0 % XML-doc coverage (0/14).
  • XML-doc coverage: Sales.RestApi Sources/Sales/Sales.RestApi/Sales.RestApi.csproj — Sales.RestApi: 0 % XML-doc coverage (0/46).
  • XML-doc coverage: Sales.Adapters REDACTED — Sales.Adapters: 0 % XML-doc coverage (0/89).
  • XML-doc coverage: Sales.ProcessModel Sources/Sales/Sales.ProcessModel/Sales.ProcessModel.csproj — Sales.ProcessModel: 0 % XML-doc coverage (0/128).
  • XML-doc coverage: Sales.DeepModel Sources/Sales/Sales.DeepModel/Sales.DeepModel.csproj — Sales.DeepModel: 0 % XML-doc coverage (0/312).
  • XML-doc coverage: TechnicalStuff Sources/TechnicalStuff/TechnicalStuff/TechnicalStuff.csproj — TechnicalStuff: 0 % XML-doc coverage (0/31).
  • XML-doc coverage: TechnicalStuff.Crud Sources/TechnicalStuff/TechnicalStuff.Crud/TechnicalStuff.Crud.csproj — TechnicalStuff.Crud: 0 % XML-doc coverage (0/41).
  • XML-doc coverage: Nuke Build/Nuke/Nuke.csproj — Nuke: 0 % XML-doc coverage (0/77).
  • XML-doc coverage: Nuke.DockerCompose REDACTED — Nuke.DockerCompose: 0 % XML-doc coverage (0/23).
  • XML-doc coverage: TechnicalStuff.Marten Sources/TechnicalStuff/TechnicalStuff.Marten/TechnicalStuff.Marten.csproj — TechnicalStuff.Marten: 0 % XML-doc coverage (0/3).
  • XML-doc coverage: TechnicalStuff.Transactions Sources/TechnicalStuff/TechnicalStuff.Transactions/TechnicalStuff.Transactions.csproj — TechnicalStuff.Transactions: 0 % XML-doc coverage (0/8).
  • XML-doc coverage: TechnicalStuff.ProcessModel Sources/TechnicalStuff/TechnicalStuff.ProcessModel/TechnicalStuff.ProcessModel.csproj — TechnicalStuff.ProcessModel: 0 % XML-doc coverage (0/14).
  • XML-doc coverage: TechnicalStuff.Kafka Sources/TechnicalStuff/TechnicalStuff.Kafka/TechnicalStuff.Kafka.csproj — TechnicalStuff.Kafka: 0 % XML-doc coverage (0/8).
  • XML-doc coverage: TechnicalStuff.Outbox.Kafka Sources/TechnicalStuff/TechnicalStuff.Outbox.Kafka/TechnicalStuff.Outbox.Kafka.csproj — TechnicalStuff.Outbox.Kafka: 0 % XML-doc coverage (0/7).
  • XML-doc coverage: TechnicalStuff.Api Sources/TechnicalStuff/TechnicalStuff.Api/TechnicalStuff.Api.csproj — TechnicalStuff.Api: 0 % XML-doc coverage (0/9).
  • XML-doc coverage: TechnicalStuff.Crud.Ef Sources/TechnicalStuff/TechnicalStuff.Crud.Ef/TechnicalStuff.Crud.Ef.csproj — TechnicalStuff.Crud.Ef: 0 % XML-doc coverage (0/22).
  • XML-doc coverage: TechnicalStuff.Crud.Api Sources/TechnicalStuff/TechnicalStuff.Crud.Api/TechnicalStuff.Crud.Api.csproj — TechnicalStuff.Crud.Api: 0 % XML-doc coverage (0/14).
  • XML-doc coverage: TechnicalStuff.Outbox Sources/TechnicalStuff/TechnicalStuff.Outbox/TechnicalStuff.Outbox.csproj — TechnicalStuff.Outbox: 0 % XML-doc coverage (0/35).
  • XML-doc coverage: TechnicalStuff.Outbox.Postgres Sources/TechnicalStuff/TechnicalStuff.Outbox.Postgres/TechnicalStuff.Outbox.Postgres.csproj — TechnicalStuff.Outbox.Postgres: 0 % XML-doc coverage (0/18).
  • XML-doc coverage: TechnicalStuff.Postgres Sources/TechnicalStuff/TechnicalStuff.Postgres/TechnicalStuff.Postgres.csproj — TechnicalStuff.Postgres: 0 % XML-doc coverage (0/11).
  • XML-doc coverage: Payments.ProcessModel Sources/Payments/Payments.ProcessModel/Payments.ProcessModel.csproj — Payments.ProcessModel: 0 % XML-doc coverage (0/14).
  • XML-doc coverage: ProductsDelivery.ProcessModel Sources/ProductsDelivery/ProductsDelivery.ProcessModel/ProductsDelivery.ProcessModel.csproj — ProductsDelivery.ProcessModel: 0 % XML-doc coverage (0/7).
  • XML-doc coverage: RiskManagement.ProcessModel Sources/RiskManagement/RiskManagement.ProcessModel/RiskManagement.ProcessModel.csproj — RiskManagement.ProcessModel: 0 % XML-doc coverage (0/12).
  • XML-doc coverage: TechnicalStuff.Outbox.Quartz Sources/TechnicalStuff/TechnicalStuff.Outbox.Quartz/TechnicalStuff.Outbox.Quartz.csproj — TechnicalStuff.Outbox.Quartz: 0 % XML-doc coverage (0/6).
  • + 16 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated · ×18
  • Outdated: JetBrains.Annotations — JetBrains.Annotations 2025.2.2 → 2026.2.0 available (referenced by Contacts).
  • Outdated: NoesisVision.Annotations — NoesisVision.Annotations 0.1.0 → 0.1.3 available (referenced by Contacts).
  • Outdated: Npgsql.EntityFrameworkCore.PostgreSQL — Npgsql.EntityFrameworkCore.PostgreSQL 8.0.4 → 10.0.3 available (referenced by Contacts).
  • Outdated: Microsoft.AspNetCore.Mvc.NewtonsoftJson — Microsoft.AspNetCore.Mvc.NewtonsoftJson 8.0.5 → 10.0.13 available (referenced by Monolith.Startup).
  • Outdated: Microsoft.EntityFrameworkCore.Design — Microsoft.EntityFrameworkCore.Design 8.0.5 → 10.0.13 available (referenced by Monolith.Startup).
  • Outdated: Microsoft.EntityFrameworkCore — Microsoft.EntityFrameworkCore 8.0.5 → 10.0.13 available (referenced by Sales.RestApi).
  • Outdated: Marten — REDACTED → 9.51.0 available (referenced by Sales.Adapters).
  • Outdated: Npgsql — Npgsql 8.0.3 → 10.0.3 available (referenced by Sales.Adapters).
  • Outdated: RepoDb — RepoDb 1.13.1 → 1.16.0 available (referenced by Sales.Adapters).
  • Outdated: RepoDb.PostgreSql — RepoDb.PostgreSql 1.13.1 → 1.16.0 available (referenced by Sales.Adapters).
  • Outdated: TaskTupleAwaiter — TaskTupleAwaiter 2.1.0 → 2.3.0 available (referenced by Sales.ProcessModel).
  • Outdated: System.Collections.Immutable — System.Collections.Immutable 8.0.0 → 10.0.13 available (referenced by Sales.DeepModel).
  • Outdated: BDD-toolkit-dotnet — BDD-toolkit-dotnet 2.4.0 → 2.5.0 available (referenced by Sales.DeepModel.Tests).
  • Outdated: FluentAssertions — FluentAssertions 6.12.0 → 8.11.0 available (referenced by Sales.DeepModel.Tests).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.9.0 → 18.11.0 available (referenced by Sales.DeepModel.Tests).
  • Outdated: xunit — xunit 2.8.0 → 2.9.3 available (referenced by Sales.DeepModel.Tests).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 2.8.0 → 4.0.1 available (referenced by Sales.DeepModel.Tests).
  • Outdated: Microsoft.AspNetCore.JsonPatch — Microsoft.AspNetCore.JsonPatch 8.0.5 → 10.0.13 available (referenced by TechnicalStuff.Crud).

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6ef5832251274747aa3a6ca771d9da0c/history.json --exit-code 0 --source .4artifacts/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-6ef5832251274747aa3a6ca771d9da0c/tree.json --exit-code 0 --source .4artifacts/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 .5artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list MyCompany.ECommerce.sln package --vulnerable --include-transitive --format json16artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
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 76 file(s) — `Sources/Contacts/Contacts/Companies/OldApi/NamespaceInfo.cs`, `Sources/Contacts/Contacts/ContactsEfDao.cs`, `Sources/Monolith.Startup/Infrastructure/FakeMessageConsumer.cs`, `Sources/Payments/Payments.ProcessModel/Requesting/PaymentRequestFulfilled.cs`, `Sources/Payments/Payments.ProcessModel/Requesting/RequestPayment.cs`, … (+71 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 Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (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 01a1611b-b6d4-7e77-ae6d-9b0655ca7dee · 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 — 6 field(s) across 3 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Phone — 3 field(s)
  • Company.Phones Sources/Contacts/Contacts/Companies/Company.cs:21
  • ListItem.Phones Sources/Contacts/Contacts/Companies/OldApi/CompaniesController.cs:147
  • ListItem.Phones Sources/Contacts/Contacts/Companies/RestApi/CompaniesController.cs:97
Address — 2 field(s)
  • Address.ZipCode Sources/Contacts/Contacts/Companies/Address.cs:21
  • AddressV1.ZipCode Sources/Contacts/Contacts/Companies/RestApi/CompaniesAddressController.cs:64
Government ID (SSN / passport / tax) — 1 field(s)
  • InvoicingDetails.TaxId Sources/Sales/Sales.DeepModel/Orders/InvoicingDetails.cs:11

Issues: 32 · Warnings: 207 · Recommendations: 59 · Info: 59 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 00:56 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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