Public report of tinglesoftware/eventbus, 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, 02:31 UTC · Survey ID cd_5a51054452f84763a04c543742bd9fdc

tinglesoftware/eventbus

Measured 22 October 2026, 02:28 UTC, at code version 995b036

CAI score 54out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 8 since the last survey

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

Performance 100 Exemplary Architecture 98 Exemplary Code Health 94 Exemplary Security and Compliance 65 Adequate Production Readiness 60 Adequate Maturity 34 Weak

A small codebase: 12,552 lines of product code in 32 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Maturity, 34

Findings by how serious they are

14 critical 144 serious 66 minor

2 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, 02:28 UTC

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

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

69of 74 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.
187of 224 findings point to an exact file and line, so you can open each one in the code. The other 37 concern the repository as a whole, such as missing documentation.
74dimensions across 6 lenses, read from 12,552 lines of product code in 32 projects.
Chapters

Executive summary

tinglesoftware/eventbus scores 54 out of 100 and is rated Adequate, while five of its six lenses score higher still: Performance at 100, Architecture at 98 and Code Health at 94, all rated Exemplary, and Security and Compliance at 65 and Production Readiness at 60, both rated Adequate. The project hasn't declared a stable release yet, so its lenses are rated against a lower bar than a released product's, while the score itself is worked out as for any repository.

The score is lower than those five because the weakest lens counts most, and here that is Maturity, which scores 34 and is rated Weak. Its Architecture documentation dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to record your significant design decisions and to reconcile the README with reality: README.md links to `./docs/bus-concepts-and-configuration.md`, but `docs/bus-concepts-and-configuration.md` does not exist; README.md links to `./docs/transport-selection.md`, but `docs/transport-selection.md` does not exist; README.md links to `./docs/multi-transport-one-bus.md`, but `docs/multi-transport-one-bus.md` does not exist; README.md links to `./docs/retries.md`, but `docs/retries.md` does not exist; README.md links to `./docs/events-and-consumers.md`, but `docs/events-and-consumers.md` does not exist, and if Maturity rose to 70, the score would rise from 54 to about 68.

14 findings are critical: 11 in Static Analysis (SAST), two in Explicit Debt and one in Project dependency cycles.

Watchdog couldn't measure Platform End-of-Life in this code, so that dimension is left out of the score. The product code is 12,552 lines, which would take an estimated 0.1 person-years, around €16,000, to rebuild.

Code Health 94 ★ Exemplary Architecture 98 ★ Exemplary Maturity 34 Weak, capped by Architecture documentation and Documentation accuracy Production Readiness 60 Adequate, capped by Security & performance tooling Security and Compliance 65 Adequate, capped by Supply-chain Provenance & Signing Performance 100 ★ 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.
Maturity 34 · counts for 46%Production Readiness 60 · counts for 25%Security and Compliance 65 · counts for 14%Code Health 94 · counts for 8%Architecture 98 · counts for 4%Performance 100 · counts for 2%

If Maturity rose from 34 to 70, the lowest score rated Strong, the score would rise from 54 to about 68.

Code composition: what the lines of code are
Business logic 37%Supporting code 53%Tests 10%
New since the last survey: 16 findings

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

  • Explicit Debt · Dead code: RemoveConsumer src/Tingle.EventBus/DependencyInjection/EventBusBuilder.cs
  • Explicit Debt · Dead code: TryGetConsumerRegistrations src/Tingle.EventBus/DependencyInjection/EventBusOptions.cs
  • Explicit Debt · Dead code: ConfigureConsumer src/Tingle.EventBus/DependencyInjection/EventBusOptions.cs
  • Explicit Debt · Dead code: GetSenderHostInfo src/Tingle.EventBus/EventContext.cs
  • Explicit Debt · Dead code: GetRequiredHeaderValue src/Tingle.EventBus/EventContext.cs
  • Explicit Debt · Dead code: ScheduleRetryAsync src/Tingle.EventBus/Publisher/IEventPublisherExtensions.cs
  • Explicit Debt · Dead code: ScheduleRetryAsync src/Tingle.EventBus/Publisher/IEventPublisherExtensions.cs
  • Explicit Debt · Dead code: WithJitterDelays src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs
  • Explicit Debt · Dead code: WithExponentialDelays src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs
  • Explicit Debt · Dead code: WithLinearDelays src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs
  • Explicit Debt · Dead code: WithConstantDelays src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs
  • Explicit Debt · Dead code: IsLastAttempt src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs
  • Explicit Debt · Dead code: Deconstruct src/Tingle.EventBus/ScheduledResult.cs
  • Supply-chain Provenance & Signing · REDACTED
  • Cancellation propagation · Async method without CancellationToken: TryConnect src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs
  • Cancellation propagation · Async call defeats the CancellationToken: ConnectConsumersAsync src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.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: 1 finding

This critical or serious finding was in the previous survey, on 7 October 2026, and is gone from this one.

  • Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €16,000 · Estimate
Cost to rebuild€5,300 to €27,000, for 89 to 286 hours of work, about 0.1 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 54. 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: 12,552 lines of product code, of which 42% is declarations and boilerplate, 18% straight logic and 41% logic with branches
Comment linesThe estimate prices 8,732 lines. Comment lines count towards the size of 12,552 lines but aren't priced as work.

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

Top priorities

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

1
Record your significant design decisions.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Raises the score by about 10 points · Medium effort · Architecture documentation
2
Reconcile the README with reality: README.md links to `./docs/bus-concepts-and-configuration.md`, but `docs/bus-concepts-and-configuration.md` does not exist; README.md links to `./docs/transport-selection.md`, but `docs/transport-selection.md` does not exist; README.md links to `./docs/multi-transport-one-bus.md`, but `docs/multi-transport-one-bus.md` does not exist; README.md links to `./docs/retries.md`, but `docs/retries.md` does not exist; README.md links to `./docs/events-and-consumers.md`, but `docs/events-and-consumers.md` does not exist.
Raises the score by about 10 points · Medium effort · Documentation accuracy
3
Resolve the 1 redundant comment finding(s) in Comment Value — start with RabbitMqTransport.cs.
Raises the score by about 2 points · Low effort · Comment Value

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €16,000 to build again, about 0.1 person-years of work. Its weakest lens is Maturity, at 34 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Record your significant design decisions. Of all the actions in this report, it raises the score most for the work it takes: about 10 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch AmazonSqsAndSns AmazonSqsAndSns Tingle.EventBus.Transports.Amazon.Sqs Sqs AmazonSqsAndSns->Tingle.EventBus.Transports.Amazon.Sqs AotSupport AotSupport Tingle.EventBus.Transports.InMemory InMemory AotSupport->Tingle.EventBus.Transports.InMemory AzureIotHub AzureIotHub Tingle.EventBus.Transports.Azure.EventHubs EventHubs AzureIotHub->Tingle.EventBus.Transports.Azure.EventHubs AzureManagedIdentity AzureManagedIdentity Tingle.EventBus.Transports.Azure.ServiceBus ServiceBus AzureManagedIdentity->Tingle.EventBus.Transports.Azure.ServiceBus ConfigSample ConfigSample ConfigSample->Tingle.EventBus.Transports.Azure.ServiceBus ConfigSample->Tingle.EventBus.Transports.InMemory CustomEventConfigurator CustomEventConfigurator Tingle.EventBus.Transports.Azure.QueueStorage QueueStorage CustomEventConfigurator->Tingle.EventBus.Transports.Azure.QueueStorage CustomEventSerializer CustomEventSerializer CustomEventSerializer->Tingle.EventBus.Transports.Azure.QueueStorage HealthCheck HealthCheck HealthCheck->Tingle.EventBus.Transports.Azure.ServiceBus InMemoryBackgroundProcessing InMemoryBackgroundProcessing InMemoryBackgroundProcessing->Tingle.EventBus.Transports.InMemory MultipleConsumers MultipleConsumers Tingle.EventBus.Serializers.NewtonsoftJson NewtonsoftJson MultipleConsumers->Tingle.EventBus.Serializers.NewtonsoftJson MultipleConsumers->Tingle.EventBus.Transports.InMemory MultipleDifferentTransports MultipleDifferentTransports MultipleDifferentTransports->Tingle.EventBus.Transports.Azure.EventHubs MultipleDifferentTransports->Tingle.EventBus.Transports.Azure.ServiceBus Tingle.EventBus EventBus Tingle.EventBus.Serializers.NewtonsoftJson->Tingle.EventBus Tingle.EventBus.Transports.Amazon.Abstractions Abstractions Tingle.EventBus.Transports.Amazon.Abstractions->Tingle.EventBus Tingle.EventBus.Transports.Amazon.Sqs->Tingle.EventBus.Transports.Amazon.Abstractions Tingle.EventBus.Transports.Azure.Abstractions Abstractions Tingle.EventBus.Transports.Azure.Abstractions->Tingle.EventBus Tingle.EventBus.Transports.Azure.EventHubs->Tingle.EventBus.Transports.Azure.Abstractions Tingle.EventBus.Transports.Azure.QueueStorage->Tingle.EventBus.Transports.Azure.Abstractions Tingle.EventBus.Transports.Azure.ServiceBus->Tingle.EventBus.Transports.Azure.Abstractions Tingle.EventBus.Transports.InMemory->Tingle.EventBus __more__ +7 more projects

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.

26 modules, with 73 dependencies between them. One loop runs through 11 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Amazon.Runtime2 Confluent.Kafka3 System4 Tingle.EventBus.Diagnostics5 Tingle.EventBus.Retries6 Tingle.EventBus.Transports.Amazon7 Tingle.EventBus.Serialization8 Tingle.EventBus.Configuration9 Tingle.EventBus.Serializers10 Tingle.EventBus.Transports.Azure.EventHubs.IotHub11 Tingle.EventBus.Ids12 Tingle.EventBus.Transports13 Tingle.EventBus.Internal14 Tingle.EventBus.Transports.InMemory15 Tingle.EventBus.Transports.InMemory.Client16 Tingle.EventBus17 Microsoft.Extensions.DependencyInjection18 Microsoft.Extensions.Logging19 Tingle.EventBus.Serialization.Xml20 Tingle.EventBus.Transports.Amazon.Kinesis21 Tingle.EventBus.Transports.Amazon.Sqs22 Tingle.EventBus.Transports.Azure.EventHubs23 Tingle.EventBus.Transports.Azure.QueueStorage24 Tingle.EventBus.Transports.Azure.ServiceBus25 Tingle.EventBus.Transports.Kafka26 Tingle.EventBus.Transports.RabbitMQ
1 Amazon.Runtime
2 Confluent.Kafka
3 System
4 Tingle.EventBus.Diagnostics
5 Tingle.EventBus.Retries
6 Tingle.EventBus.Transports.Amazon
7 Tingle.EventBus.Serialization212
8 Tingle.EventBus.Configuration244
9 Tingle.EventBus.Serializers41
10 Tingle.EventBus.Transports.Azure.EventHubs.IotHub41
11 Tingle.EventBus.Ids2
12 Tingle.EventBus.Transports743
13 Tingle.EventBus.Internal1111
14 Tingle.EventBus.Transports.InMemory221633
15 Tingle.EventBus.Transports.InMemory.Client1
16 Tingle.EventBus6611211
17 Microsoft.Extensions.DependencyInjection145261
18 Microsoft.Extensions.Logging1
19 Tingle.EventBus.Serialization.Xml71
20 Tingle.EventBus.Transports.Amazon.Kinesis1122
21 Tingle.EventBus.Transports.Amazon.Sqs21132
22 Tingle.EventBus.Transports.Azure.EventHubs31122
23 Tingle.EventBus.Transports.Azure.QueueStorage21122
24 Tingle.EventBus.Transports.Azure.ServiceBus31122
25 Tingle.EventBus.Transports.Kafka3122
26 Tingle.EventBus.Transports.RabbitMQ31122
Uses a module listed above itPart of a loopThe module itself
1 Amazon.Runtime2 Confluent.Kafka3 System4 Tingle.EventBus.Diagnostics5 Tingle.EventBus.Retries6 Tingle.EventBus.Transports.Amazon7 Tingle.EventBus.Serialization8 Tingle.EventBus.Configuration9 Tingle.EventBus.Serializers10 Tingle.EventBus.Transports.Azure.EventHubs.IotHub11 Tingle.EventBus.Ids12 Tingle.EventBus.Transports13 Tingle.EventBus.Internal14 Tingle.EventBus.Transports.InMemory15 Tingle.EventBus.Transports.InMemory.Client16 Tingle.EventBus17 Microsoft.Extensions.DependencyInjection18 Microsoft.Extensions.Logging19 Tingle.EventBus.Serialization.Xml20 Tingle.EventBus.Transports.Amazon.Kinesis21 Tingle.EventBus.Transports.Amazon.Sqs22 Tingle.EventBus.Transports.Azure.EventHubs23 Tingle.EventBus.Transports.Azure.QueueStorage24 Tingle.EventBus.Transports.Azure.ServiceBus25 Tingle.EventBus.Transports.Kafka26 Tingle.EventBus.Transports.RabbitMQAmazon.Runtime1Confluent.Kafka2System3Tingle.EventBus.Diagnostics4Tingle.EventBus.Retries5Tingle.EventBus.Transports.Amazon6Tingle.EventBus.Serialization7Tingle.EventBus.Configuration8Tingle.EventBus.Serializers9Tingle.EventBus.Transports.Azure.EventHubs.IotHub10Tingle.EventBus.Ids11Tingle.EventBus.Transports12Tingle.EventBus.Internal13Tingle.EventBus.Transports.InMemory14Tingle.EventBus.Transports.InMemory.Client15Tingle.EventBus16Microsoft.Extensions.DependencyInjection17Microsoft.Extensions.Logging18Tingle.EventBus.Serialization.Xml19Tingle.EventBus.Transports.Amazon.Kinesis20Tingle.EventBus.Transports.Amazon.Sqs21Tingle.EventBus.Transports.Azure.EventHubs22Tingle.EventBus.Transports.Azure.QueueStorage23Tingle.EventBus.Transports.Azure.ServiceBus24Tingle.EventBus.Transports.Kafka25Tingle.EventBus.Transports.RabbitMQ2621224441412743111122163316611211145261171112221132311222112231122312231122

At a glance — Code Health · 94% · Exemplary ·

The Good
D1 · .NET / C# Cyclomatic Complexity 10.0 D2 · .NET / C# Cognitive Complexity 9.4 D3 · .NET / C# God Classes 10.0 D4 · .NET / C# Code Duplication 8.9 D17 · .NET / C# Explicit Debt 9.1 D18 · .NET / C# Solution Shape 10.0 D39 · .NET / C# IL Efficiency 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 9.7 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 8.9
The Bad
X18 · Repo Disposal-pattern correctness 5.0

At a glance — Architecture · 98% · Exemplary ·

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

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

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

At a glance — Readiness · 60% · Adequate · gated by P3 ·

The Good
D8 · .NET / C# Code Coverage 7.7 D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D11 · .NET / C# Test Reliability 10.0 D12 · .NET / C# Dependency Hygiene 8.8 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 9.9
The Bad
ED5 · Repo Idempotency 5.3 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0
The Ugly
P3 · Repo Security & performance tooling 3.0

At a glance — Security · 65% · Adequate · gated by D36 ·

The Good
D28 · .NET / C# Secrets (history) 10.0 D30 · .NET / C# Dependency Vulnerabilities 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Bad
D29 · .NET / C# Static Analysis (SAST) 6.0
The Ugly
D36 · .NET / C# Supply-chain Provenance & Signing 0.0

At a glance — Performance · 100% · Exemplary ·

The Good
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
A05:2025 — Injection11High / Critical
A03:2025 — Software Supply Chain Failures6Medium

Roadmap

First, establish a structured record of significant design decisions in a dedicated folder to capture context and consequences. Next, correct broken links in the README and fill in missing documentation to ensure the guide accurately reflects the current codebase. Then, address low XML documentation coverage in key project files to improve code clarity and maintainability. Finally, integrate a static analysis security step into the continuous integration pipeline to automatically block security regressions.

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

Do thisHelpsEffortDimension
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.+10.0 ptsMediumArchitecture documentation
Reconcile the README with reality: README.md links to `./docs/bus-concepts-and-configuration.md`, but `docs/bus-concepts-and-configuration.md` does not exist; README.md links to `./docs/transport-selection.md`, but `docs/transport-selection.md` does not exist; README.md links to `./docs/multi-transport-one-bus.md`, but `docs/multi-transport-one-bus.md` does not exist; README.md links to `./docs/retries.md`, but `docs/retries.md` does not exist; README.md links to `./docs/events-and-consumers.md`, but `docs/events-and-consumers.md` does not exist.+10.0 ptsMediumDocumentation accuracy
Resolve the 1 redundant comment finding(s) in Comment Value — start with RabbitMqTransport.cs.+1.5 ptsLowComment Value
Resolve the 16 Low XML-doc coverage finding(s) in Documentation Quality — start with AmazonSqsAndSns.csproj, AotSupport.csproj, AzureIotHub.csproj.+3.1 ptsMediumDocumentation Quality
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.+2.4 ptsMediumDocumentation (README)
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+2.3 ptsMediumSecurity & performance tooling
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.+1.5 ptsMediumDeployment & Rollback
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+1.5 ptsMediumRelease Hygiene

File quality

Per-file score 0–10 — a quality signature. Of 75 files carrying findings, judged against the Preview bar: 3% slop · 16% mixed · 81% near-clean.

FileScoreBandWorst signal
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs2.4SlopExplicit Debt: WriteOnlyPrivateField
src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs4.5MixedCode Duplication: Duplicated block (35–37 lines × 2)
src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs5.7MixedCode Duplication: Duplicated block (19 lines × 2)
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
src/Tingle.EventBus/EventBus.cs5.9MixedCode Duplication: Duplicated block (17 lines × 2)
src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs6.0MixedExplicit Debt: TodoComment
src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs6.0MixedExplicit Debt: TodoComment
src/Tingle.EventBus/EventContext.cs6.0MixedExplicit Debt: Dead code: GetSenderHostInfo
src/Tingle.EventBus/DependencyInjection/EventBusOptions.cs6.0MixedExplicit Debt: Dead code: TryGetConsumerRegistrations
src/Tingle.EventBus/Publisher/IEventPublisherExtensions.cs6.0MixedExplicit Debt: Dead code: ScheduleRetryAsync
src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs6.0MixedExplicit Debt: Dead code: WithJitterDelays
src/Tingle.EventBus.Transports.Kafka/KafkaConfigureOptions.cs6.3MixedCognitive Complexity: KafkaConfigureOptions.PostConfigure (cognitive 18)
src/Tingle.EventBus/ScheduledResult.cs6.7MixedExplicit Debt: Dead code: Deconstruct
src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsConfigureOptions.cs7.0Near-cleanCognitive Complexity: AzureEventHubsConfigureOptions.PostConfigure (cognitive 20)
src/Tingle.EventBus.Transports.Amazon.Sqs/Tingle.EventBus.Transports.Amazon.Sqs.csproj7.0Near-cleanCode Coverage: No test project references Tingle.EventBus.Transports.Amazon.Sqs
REDACTED7.2Near-cleanStatic Analysis (SAST): High: REDACTED
src/Tingle.EventBus/DependencyInjection/EventBusBuilder.cs7.3Near-cleanExplicit Debt: TodoComment
tests/Tingle.EventBus.Transports.Azure.EventHubs.Tests/IotHubEventSerializerTests.cs7.3Near-cleanExplicit Debt: Dead code: DummyTelemetry1
samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs7.4Near-cleanCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)

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

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

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

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

Could not be resolved — 2

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. 69 of 74 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 1.0 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 74 dimensions across the health lenses
D1D2D3D4D5D6D8D9D10D11D12D13D14D15D17D18D19D21D24D26D27D28D29D30D34D35D36D39AX1AX10AX2AX3AX4AX5AX6AX8ED5GD1IC1M1M2M3M4P1P2P3P4P6PF3X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 187 of 224 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 01a16170-24e7-76d5-b6f6-a7ef4da1b57b.

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-contributor repository — bus factor is not applicable (1 contributor(s) across 1292 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so 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. `src/Tingle.EventBus.Transports.Amazon.Abstractions/AmazonTransportConfigureOptions.cs`, `src/Tingle.EventBus.Transports.Amazon.Kinesis/AmazonKinesisConfigureOptions.cs`, `src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsConfigureOptions.cs`, `src/Tingle.EventBus.Transports.Azure.Abstractions/AzureTransportConfigureOptions.cs`, `src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsConfigureOptions.cs`, … (+31 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.
  • D44 Platform End-of-Life — 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. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

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 Complexity9.4 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

4 method(s) exceeded the cognitive complexity threshold of 15; the worst was AmazonSqsTransport.PublishCoreAsync at 20.

AmazonSqsTransport.PublishCoreAsync (cognitive 20)src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:155
AzureEventHubsConfigureOptions.PostConfigure (cognitive 20)src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsConfigureOptions.cs:56
KafkaConfigureOptions.PostConfigure (cognitive 18)src/Tingle.EventBus.Transports.Kafka/KafkaConfigureOptions.cs:19
RabbitMqConfigureOptions.PostConfigure (cognitive 17)src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqConfigureOptions.cs:19

What to do

  1. Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with AmazonSqsTransport.PublishCoreAsync (cognitive 20), AzureEventHubsConfigureOptions.PostConfigure (cognitive 20), KafkaConfigureOptions.PostConfigure (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D4 · Code Duplication8.9 / 10Strong✓ 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 8.9 / 10 · rule-coverage 100% · ceiling Verified

31 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 9 of the 34 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (12 lines × 2) · ×3src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:428
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:346
Duplicated block (19 lines × 2) · ×2src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:12
Duplicated block (17 lines × 2) · ×2src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:125
Duplicated block (5 lines × 2) · ×2src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:113

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

What to do

  1. Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with AmazonSqsTransport.cs, EventBus.cs, AzureServiceBusTransport.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with AzureEventHubsTransport.cs, VehicleTelemetryEventsConsumer.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with ILoggerExtensions.cs, Program.cs. — One of this dimension's main actionable groups (2 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.8 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

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

Off the main sequence: Tingle.EventBussrc/Tingle.EventBus/Tingle.EventBus.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with Tingle.EventBus.csproj. — One of this dimension's main actionable groups (1 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 30 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

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

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

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

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

Line coverage 40.5% — 35 file(s) below 50% · 11 method(s) over the CRAP-30 risk line.

Low coverage: src/Tingle.EventBus.Transports.Kafka/KafkaExtensions.cs · ×35src/Tingle.EventBus.Transports.Kafka/KafkaExtensions.cs:1
CRAP 68: KafkaTransport.OnEventReceivedAsync · ×3src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:265
No test project references Tingle.EventBus.Transports.Amazon.Kinesissrc/Tingle.EventBus.Transports.Amazon.Kinesis/Tingle.EventBus.Transports.Amazon.Kinesis.csproj
No test project references Tingle.EventBus.Transports.Amazon.Sqssrc/Tingle.EventBus.Transports.Amazon.Sqs/Tingle.EventBus.Transports.Amazon.Sqs.csproj
No test project references Tingle.EventBus.Transports.RabbitMQsrc/Tingle.EventBus.Transports.RabbitMQ/Tingle.EventBus.Transports.RabbitMQ.csproj

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

What to do

  1. Resolve the 35 Low coverage finding(s) in Code Coverage — start with ILoggerExtensions.cs (4), KafkaExtensions.cs, KafkaConfigureOptions.cs. — One of this dimension's main actionable groups (35 warning-level).
  2. Resolve the 3 CRAP 68 finding(s) in Code Coverage — start with AzureServiceBusTransport.cs (2), KafkaTransport.cs. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 No test project references Tingle.EventBus.Transports.Amazon.Kinesis finding(s) in Code Coverage — start with Tingle.EventBus.Transports.Amazon.Kinesis.csproj. — One of this dimension's main actionable groups (1 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

31 test methods: 31 unit, 0 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 31 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 1 measured tier(s). unit: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

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

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

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

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

23 outdated, 0 vulnerable, 0 deprecated packages.

Outdated: Microsoft.Extensions.Hosting · ×23

What to do

  1. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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 176 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 27 direct `PackageReference`(s), and 149 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 Debt9.1 / 10Adequategated by 2 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 9.1 / 10 · rule-coverage 100% · ceiling Prevented

8 deducted debt markers + 15 dead symbols across 12552 LoC in the .NET projects (0.4/KLoC) → score 9.1.

WriteOnlyPrivateField · ×2src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:21
Dead code: RemoveConsumer · ×15src/Tingle.EventBus/DependencyInjection/EventBusBuilder.cs:322
TodoComment · ×6src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:436

What to do

  1. Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with KafkaTransport.cs (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 15 Dead code finding(s) in Explicit Debt — start with IRetryableEventExtensions.cs (5), EventBusOptions.cs (2), EventContext.cs (2). — One of this dimension's main actionable groups (15 warning-level).
  3. Resolve the 6 TodoComment finding(s) in Explicit Debt — start with AmazonSqsTransport.cs, AzureEventHubsTransport.cs, AzureQueueStorageTransport.cs. — One of this dimension's main actionable groups (6 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 Shape10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

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

32 projects, 267 source files, 13513 hand-written lines of code (12552 production / 961 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), 38 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation QualityStrong◐ Sampled · advisory

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

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

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

The repository's root README is clear and well-structured for a project overview: it states what the project does (simplify adding events to .NET projects), names the NuGet packages, links to a GitHub workflow badge, and gives an organisational note about Tingle Software. It also lists all the packages in a table of contents-style Packages section. The README itself is clipped mid-table row for further content; the visible material shows strong overview, installation/usage guidance (Getting started), features, samples, instrumentation, issues, and license, with architecture/design docs and XML coverage below.

Low XML-doc coverage: AmazonSqsAndSns · ×16samples/AmazonSqsAndSns/AmazonSqsAndSns.csproj
XML-doc coverage: SimplePublisher · ×11samples/SimplePublisher/SimplePublisher.csproj

What to do

  1. Resolve the 16 Low XML-doc coverage finding(s) in Documentation Quality — start with AmazonSqsAndSns.csproj, AotSupport.csproj, AzureIotHub.csproj. — One of this dimension's main actionable groups (16 warning-level).

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.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

80 valuable / 1 redundant across 200 sampled comments; 1 shown with locations.

redundant commentsrc/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:281

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.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 32 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

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

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

Pass-through layersrc/Tingle.EventBus/Publisher/WrappedEventPublisher.cs:11

✓ On the Gold path — maintain.

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

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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

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

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

11 finding(s): 0 critical, 11 high, 0 medium, 0 low. 8 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 61 file(s) — `samples/AmazonSqsAndSns/DoorOpenedConsumer.cs` (line 3), `samples/AmazonSqsAndSns/PublisherService.cs` (line 3), `samples/AotSupport/Program.cs` (line 25, lines 51–53, line 82), `samples/AzureIotHub/AzureIotEventsConsumer.cs` (line 8), `samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs` (line 3), … (+56 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 60 of those file(s) — `samples/AmazonSqsAndSns/DoorOpenedConsumer.cs`, `samples/AmazonSqsAndSns/PublisherService.cs`, `samples/AotSupport/Program.cs`, `samples/AzureIotHub/AzureIotEventsConsumer.cs`, `samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs`, … (+55 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 1 of those file(s) — `src/Tingle.EventBus/Serialization/SerializationContext.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

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 8 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 (8 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

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

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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

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

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 46 of the 134 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

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

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

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

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

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

Strongest change-coupling: AbstractEventSerializer.cs↔EventBusTransport.cs 57%

Change coupling: AbstractEventSerializer.cs ↔ EventBusTransport.cssrc/Tingle.EventBus/Serialization/AbstractEventSerializer.cs:1

What to do

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

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

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

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d39_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 composition9.4 / 10Exemplary✓ 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 singletons10.0 / 10Exemplary✓ 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.

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 Microsoft.Extensions.DependencyInjection ↔ Tingle.EventBus ↔ Tingle.EventBus.Configuration ↔ Tingle.EventBus.Ids ↔ Tingle.EventBus.Internal ↔ Tingle.EventBus.Serialization ↔ Tingle.EventBus.Serializers ↔ Tingle.EventBus.Transports ↔ Tingle.EventBus.Transports.Azure.EventHubs.IotHub ↔ Tingle.EventBus.Transports.InMemory ↔ Tingle.EventBus.Transports.InMemory.Client depend on each other. The lightest dependency in the cycle is Microsoft.Extensions.DependencyInjection → Tingle.EventBus (Microsoft.Extensions.DependencyInjection.AmazonKinesisTransportOptions → Tingle.EventBus.EventContext, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Tingle.EventBus.Transports.Amazon.Kinesis/AmazonKinesisTransportOptions.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 segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

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

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

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

ED5 · Idempotency5.3 / 10Adequate◐ Sampled · advisory

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

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

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

  • `AmazonSqsAndSns.PublisherService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — samples/AmazonSqsAndSns/PublisherService.cs:5
  • `ProducerService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. (×2) — samples/AotSupport/Program.cs:27, samples/InMemoryBackgroundProcessing/Program.cs:26
  • `ConfigSample.VisualsProducerService.ExecuteAsync` mutates persistent state (an event publish one hop away, in VisualsProducerService.DoPublishAsync) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — samples/ConfigSample/VisualsProducerService.cs:5
  • `MultiEventsConsumer.DummyProducerService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — samples/MultiEventsConsumer/DummyProducerService.cs:5
  • `MultipleConsumers.PublisherService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — samples/MultipleConsumers/PublisherService.cs:5
  • `VisualsProducerService.ExecuteAsync` mutates persistent state (an event publish one hop away, in VisualsProducerService.DoPublishAsync) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — samples/MultipleSimilarTransports/Program.cs:26
  • `SimplePublisher.PublisherService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — samples/SimplePublisher/PublisherService.cs:5

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 code10.0 / 10Exemplary○ Nothing flagged

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.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

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.

  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — src/Tingle.EventBus/DependencyInjection/EventBusBuilder.cs:131

What to do

  • 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)6.7 / 10Strong✓ Tool-verified

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 32 of 32 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure8.0 / 10Strong✓ 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.

  • Only 17/32 projects share a common root namespace — the code's module identity is inconsistent.

What to do

  • Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
M4 · Documentation accuracy0.0 / 10Critical◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

  • README.md links to `./docs/bus-concepts-and-configuration.md`, but `docs/bus-concepts-and-configuration.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:34
  • README.md links to `./docs/transport-selection.md`, but `docs/transport-selection.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:38
  • README.md links to `./docs/multi-transport-one-bus.md`, but `docs/multi-transport-one-bus.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:39
  • README.md links to `./docs/retries.md`, but `docs/retries.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:40
  • README.md links to `./docs/events-and-consumers.md`, but `docs/events-and-consumers.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:41
  • README.md links to `./docs/observability.md`, but `docs/observability.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:42
  • README.md links to `./docs/work-with-configuration.md`, but `docs/work-with-configuration.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:47
  • README.md links to `./docs/work-with-azure-iot-hub.md`, but `docs/work-with-azure-iot-hub.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:48
  • README.md links to `./docs/work-with-azure-managed-identities.md`, but `docs/work-with-azure-managed-identities.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:49
  • README.md links to `./docs/advanced-service-bus-options.md`, but `docs/advanced-service-bus-options.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:50
  • README.md links to `./docs/work-with-feature-management.md`, but `docs/work-with-feature-management.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:51
  • README.md links to `./docs/extend-event-configuration.md`, but `docs/extend-event-configuration.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:52

What to do

  • Reconcile the README with reality: README.md links to `./docs/bus-concepts-and-configuration.md`, but `docs/bus-concepts-and-configuration.md` does not exist; README.md links to `./docs/transport-selection.md`, but `docs/transport-selection.md` does not exist; README.md links to `./docs/multi-transport-one-bus.md`, but `docs/multi-transport-one-bus.md` does not exist; README.md links to `./docs/retries.md`, but `docs/retries.md` does not exist; README.md links to `./docs/events-and-consumers.md`, but `docs/events-and-consumers.md` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability9.9 / 10Exemplary✓ 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.

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3350 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

  • The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.
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.

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

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

What to do

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

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

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

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

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

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

  • Only 133/140 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 — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×3) — src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:345, src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:500, src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:312
  • No CancellationToken parameter — this work can't be stopped early once started. (×4) — src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:425, src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:429, src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:438, …
  • 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
  • Holds a CancellationToken but hands `CancellationToken.None` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). — src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:281

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 types8.9 / 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.

  • ~1.4 `!` suppressions per 1k syntax nodes — 79 suppression(s) across the 56981 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 Health94%ExemplarySolid.
Architecture98%ExemplarySolid.
Maturity34%Weak — gated by M2, M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness60%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security65%Adequate — gated by D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 1 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.

  • X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 44 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
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — small single-context codebase (12,552 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) — 36 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 value object(s))
  • ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 24 event handler(s); a message-bus package
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — coverage data present for 124 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 — 14 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · WriteOnlyPrivateField · ×2
  • WriteOnlyPrivateField src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:21 — private TimeSpan StandardTimeout — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:27 — private Lazy<IAdminClient> adminClient — 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.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/Tingle.EventBus.Transports.Amazon.Kinesis/AmazonKinesisTransportOptions.cs:2 — The namespaces Microsoft.Extensions.DependencyInjection ↔ Tingle.EventBus ↔ Tingle.EventBus.Configuration ↔ Tingle.EventBus.Ids ↔ Tingle.EventBus.Internal ↔ Tingle.EventBus.Serialization ↔ Tingle.EventBus.Serializers ↔ Tingle.EventBus.Transports ↔ Tingle.EventBus.Transports.Azure.EventHubs.IotHub ↔ Tingle.EventBus.Transports.InMemory ↔ Tingle.EventBus.Transports.InMemory.Client depend on each other. The lightest dependency in the cycle is Microsoft.Extensions.DependencyInjection → Tingle.EventBus (Microsoft.Extensions.DependencyInjection.AmazonKinesisTransportOptions → Tingle.EventBus.EventContext, 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 144 finding(s)
D8 · Code Coverage · Low coverage · ×35
  • Low coverage: src/Tingle.EventBus.Transports.Kafka/KafkaExtensions.cs src/Tingle.EventBus.Transports.Kafka/KafkaExtensions.cs:1 — 0.0% line coverage (0/15).
  • Low coverage: src/Tingle.EventBus.Transports.Kafka/KafkaConfigureOptions.cs src/Tingle.EventBus.Transports.Kafka/KafkaConfigureOptions.cs:1 — 0.0% line coverage (0/44).
  • Low coverage: src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:1 — 2.2% line coverage (5/223).
  • Low coverage: src/Tingle.EventBus.Transports.InMemory/ILoggerExtensions.cs src/Tingle.EventBus.Transports.InMemory/ILoggerExtensions.cs:1 — 0.0% line coverage (0/17).
  • Low coverage: src/Tingle.EventBus.Transports.InMemory/InMemoryEventContextExtensions.cs src/Tingle.EventBus.Transports.InMemory/InMemoryEventContextExtensions.cs:1 — 40.0% line coverage (6/15).
  • Low coverage: src/Tingle.EventBus.Transports.InMemory/InMemoryTestHarness.cs src/Tingle.EventBus.Transports.InMemory/InMemoryTestHarness.cs:1 — 44.4% line coverage (20/45).
  • Low coverage: src/Tingle.EventBus.Transports.InMemory/Client/BroadcastChannelWriter.cs src/Tingle.EventBus.Transports.InMemory/Client/BroadcastChannelWriter.cs:1 — 0.0% line coverage (0/5).
  • Low coverage: src/Tingle.EventBus.Transports.InMemory/Client/InMemoryMessage.cs src/Tingle.EventBus.Transports.InMemory/Client/InMemoryMessage.cs:1 — 42.1% line coverage (8/19).
  • Low coverage: src/Tingle.EventBus/Extensions/ILoggerExtensions.cs src/Tingle.EventBus/Extensions/ILoggerExtensions.cs:1 — 29.4% line coverage (10/34).
  • Low coverage: src/Tingle.EventBus/DependencyInjection/EventBusOptions.cs src/Tingle.EventBus/DependencyInjection/EventBusOptions.cs:1 — 47.5% line coverage (29/61).
  • Low coverage: src/Tingle.EventBus/Serialization/Xml/EventBusBuilderExtensions.cs src/Tingle.EventBus/Serialization/Xml/EventBusBuilderExtensions.cs:1 — 0.0% line coverage (0/7).
  • Low coverage: src/Tingle.EventBus/EventBus.cs src/Tingle.EventBus/EventBus.cs:1 — 46.6% line coverage (62/133).
  • Low coverage: src/Tingle.EventBus/Publisher/IEventPublisherExtensions.cs src/Tingle.EventBus/Publisher/IEventPublisherExtensions.cs:1 — 8.5% line coverage (4/47).
  • Low coverage: src/Tingle.EventBus/Publisher/WrappedEventPublisher.cs src/Tingle.EventBus/Publisher/WrappedEventPublisher.cs:1 — 11.8% line coverage (2/17).
  • Low coverage: src/Tingle.EventBus/ScheduledResult.cs src/Tingle.EventBus/ScheduledResult.cs:1 — 28.6% line coverage (4/14).
  • Low coverage: src/Tingle.EventBus/Serialization/Xml/XmlEventEnvelope.cs src/Tingle.EventBus/Serialization/Xml/XmlEventEnvelope.cs:1 — 0.0% line coverage (0/27).
  • Low coverage: src/Tingle.EventBus/Serialization/Xml/XmlEventSerializer.cs src/Tingle.EventBus/Serialization/Xml/XmlEventSerializer.cs:1 — 0.0% line coverage (0/12).
  • Low coverage: src/Tingle.EventBus/Serialization/Xml/XmlHeader.cs src/Tingle.EventBus/Serialization/Xml/XmlHeader.cs:1 — 0.0% line coverage (0/9).
  • Low coverage: src/Tingle.EventBus/Retries/AbstractRetryableEvent.cs src/Tingle.EventBus/Retries/AbstractRetryableEvent.cs:1 — 0.0% line coverage (0/14).
  • Low coverage: src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs:1 — 0.0% line coverage (0/47).
  • Low coverage: src/Tingle.EventBus/Configuration/Attributes/EventTransportNameAttribute.cs src/Tingle.EventBus/Configuration/Attributes/EventTransportNameAttribute.cs:1 — 0.0% line coverage (0/8).
  • Low coverage: src/Tingle.EventBus/Configuration/EventConsumerRegistration.cs src/Tingle.EventBus/Configuration/EventConsumerRegistration.cs:1 — 46.9% line coverage (15/32).
  • Low coverage: src/Tingle.EventBus/Internal/EventBusHost.cs src/Tingle.EventBus/Internal/EventBusHost.cs:1 — 0.0% line coverage (0/20).
  • Low coverage: src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:1 — 0.0% line coverage (0/17).
  • Low coverage: src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusConfigureOptions.cs src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusConfigureOptions.cs:1 — 0.0% line coverage (0/43).
  • + 10 more in this group — see findings.md.
D19 · Documentation Quality · Low XML-doc coverage · ×16
  • Low XML-doc coverage: AmazonSqsAndSns samples/AmazonSqsAndSns/AmazonSqsAndSns.csproj — AmazonSqsAndSns: 38 % XML-doc coverage (3/8).
  • Low XML-doc coverage: AotSupport samples/AotSupport/AotSupport.csproj — AotSupport: 0 % XML-doc coverage (0/5).
  • Low XML-doc coverage: AzureIotHub samples/AzureIotHub/AzureIotHub.csproj — AzureIotHub: 0 % XML-doc coverage (0/5).
  • Low XML-doc coverage: AzureManagedIdentity samples/AzureManagedIdentity/AzureManagedIdentity.csproj — AzureManagedIdentity: 0 % XML-doc coverage (0/14).
  • Low XML-doc coverage: ConfigSample samples/ConfigSample/ConfigSample.csproj — ConfigSample: 0 % XML-doc coverage (0/19).
  • Low XML-doc coverage: CustomEventConfigurator samples/CustomEventConfigurator/CustomEventConfigurator.csproj — CustomEventConfigurator: 0 % XML-doc coverage (0/15).
  • Low XML-doc coverage: CustomEventSerializer samples/CustomEventSerializer/CustomEventSerializer.csproj — CustomEventSerializer: 45 % XML-doc coverage (9/20).
  • Low XML-doc coverage: HealthCheck samples/HealthCheck/HealthCheck.csproj — HealthCheck: 0 % XML-doc coverage (0/15).
  • Low XML-doc coverage: InMemoryBackgroundProcessing samples/InMemoryBackgroundProcessing/InMemoryBackgroundProcessing.csproj — InMemoryBackgroundProcessing: 0 % XML-doc coverage (0/4).
  • Low XML-doc coverage: MultiEventsConsumer samples/MultiEventsConsumer/MultiEventsConsumer.csproj — MultiEventsConsumer: 46 % XML-doc coverage (6/13).
  • Low XML-doc coverage: MultipleConsumers samples/MultipleConsumers/MultipleConsumers.csproj — MultipleConsumers: 30 % XML-doc coverage (3/10).
  • Low XML-doc coverage: MultipleDifferentTransports samples/MultipleDifferentTransports/MultipleDifferentTransports.csproj — MultipleDifferentTransports: 0 % XML-doc coverage (0/13).
  • Low XML-doc coverage: MultipleSimilarTransports samples/MultipleSimilarTransports/MultipleSimilarTransports.csproj — MultipleSimilarTransports: 0 % XML-doc coverage (0/8).
  • Low XML-doc coverage: SimpleConsumer samples/SimpleConsumer/SimpleConsumer.csproj — SimpleConsumer: 0 % XML-doc coverage (0/11).
  • Low XML-doc coverage: Tingle.EventBus.Transports.Amazon.Sqs src/Tingle.EventBus.Transports.Amazon.Sqs/Tingle.EventBus.Transports.Amazon.Sqs.csproj — Tingle.EventBus.Transports.Amazon.Sqs: 45 % XML-doc coverage (15/33).
  • Low XML-doc coverage: Tingle.EventBus.Transports.Azure.ServiceBus src/Tingle.EventBus.Transports.Azure.ServiceBus/Tingle.EventBus.Transports.Azure.ServiceBus.csproj — Tingle.EventBus.Transports.Azure.ServiceBus: 46 % XML-doc coverage (25/54).
D17 · Explicit Debt · Dead code · ×15
  • Dead code: RemoveConsumer src/Tingle.EventBus/DependencyInjection/EventBusBuilder.cs:322 — Method RemoveConsumer — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: TryGetConsumerRegistrations src/Tingle.EventBus/DependencyInjection/EventBusOptions.cs:176 — Method TryGetConsumerRegistrations — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: ConfigureConsumer src/Tingle.EventBus/DependencyInjection/EventBusOptions.cs:226 — Method ConfigureConsumer — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: GetSenderHostInfo src/Tingle.EventBus/EventContext.cs:104 — Method GetSenderHostInfo — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: GetRequiredHeaderValue src/Tingle.EventBus/EventContext.cs:177 — Method GetRequiredHeaderValue — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: ScheduleRetryAsync src/Tingle.EventBus/Publisher/IEventPublisherExtensions.cs:168 — Method ScheduleRetryAsync — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: ScheduleRetryAsync src/Tingle.EventBus/Publisher/IEventPublisherExtensions.cs:189 — Method ScheduleRetryAsync — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: WithJitterDelays src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs:33 — Method WithJitterDelays — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: WithExponentialDelays src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs:55 — Method WithExponentialDelays — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: WithLinearDelays src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs:74 — Method WithLinearDelays — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: WithConstantDelays src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs:92 — Method WithConstantDelays — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: IsLastAttempt src/Tingle.EventBus/Retries/IRetryableEventExtensions.cs:143 — Method IsLastAttempt — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: Deconstruct src/Tingle.EventBus/ScheduledResult.cs:52 — Method Deconstruct — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus, 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: DummyTelemetry1 tests/Tingle.EventBus.Transports.Azure.EventHubs.Tests/IotHubEventSerializerTests.cs:223 — NamedType DummyTelemetry1 — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus.Transports.Azure.EventHubs.Tests, 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: DummyEvent2 tests/Tingle.EventBus.Transports.Azure.EventHubs.Tests/IotHubEventSerializerTests.cs:224 — NamedType DummyEvent2 — Roslyn's SymbolFinder walked every project the solution loads, including Tingle.EventBus.Transports.Azure.EventHubs.Tests, 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.
ED5 · Idempotency · Non-idempotent mutation · ×8
  • Non-idempotent mutation: AmazonSqsAndSns.PublisherService.ExecuteAsync samples/AmazonSqsAndSns/PublisherService.cs:5 — `AmazonSqsAndSns.PublisherService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
  • Non-idempotent mutation: ProducerService.ExecuteAsync samples/AotSupport/Program.cs:27 — `ProducerService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
  • Non-idempotent mutation: ConfigSample.VisualsProducerService.ExecuteAsync samples/ConfigSample/VisualsProducerService.cs:5 — `ConfigSample.VisualsProducerService.ExecuteAsync` mutates persistent state (an event publish one hop away, in VisualsProducerService.DoPublishAsync) 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: ProducerService.ExecuteAsync samples/InMemoryBackgroundProcessing/Program.cs:26 — `ProducerService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
  • Non-idempotent mutation: MultiEventsConsumer.DummyProducerService.ExecuteAsync samples/MultiEventsConsumer/DummyProducerService.cs:5 — `MultiEventsConsumer.DummyProducerService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
  • Non-idempotent mutation: MultipleConsumers.PublisherService.ExecuteAsync samples/MultipleConsumers/PublisherService.cs:5 — `MultipleConsumers.PublisherService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
  • Non-idempotent mutation: VisualsProducerService.ExecuteAsync samples/MultipleSimilarTransports/Program.cs:26 — `VisualsProducerService.ExecuteAsync` mutates persistent state (an event publish one hop away, in VisualsProducerService.DoPublishAsync) 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: SimplePublisher.PublisherService.ExecuteAsync samples/SimplePublisher/PublisherService.cs:5 — `SimplePublisher.PublisherService.ExecuteAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
D17 · Explicit Debt · TodoComment · ×6
  • TodoComment src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:436 — // TODO: figure out what to do when dead-letter fails — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:417 — // TODO: figure out what to do when dead-letter fails — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Tingle.EventBus.Transports.Azure.QueueStorage/AzureQueueStorageTransport.cs:332 — // TODO: figure out what to do when dead-letter fails — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:367 — // TODO: figure out what to do when dead-letter fails — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:320 — // TODO: figure out what to do when dead-letter fails — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Tingle.EventBus/DependencyInjection/EventBusBuilder.cs:106 — // TODO: remove after https://github.com/dotnet/runtime/issues/42358 is addressed
X2 · Cancellation propagation · Async method without CancellationToken · ×4
  • Async method without CancellationToken: TryConnect src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:425 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnConnectionBlockedAsync src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:429 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnCallbackExceptionAsync src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:438 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnConnectionShutdownAsync src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:447 — No CancellationToken parameter — this work can't be stopped early once started.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:428 — src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:428-439 | src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:312-323 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:428` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) src/Tingle.EventBus/EventBus.cs:47 — src/Tingle.EventBus/EventBus.cs:47-58 | src/Tingle.EventBus/EventBus.cs:105-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:82 — src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:82-93 | src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:68-79 — before extracting anything, compare `src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs` and `src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D8 · Code Coverage · CRAP 68 · ×3
  • CRAP 68: KafkaTransport.OnEventReceivedAsync src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:265 — Cyclomatic 8 with 2.2% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
  • CRAP 68: AzureServiceBusTransport.PublishCoreAsync src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:177 — Cyclomatic 8 with 2.3% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
  • CRAP 68: AzureServiceBusTransport.DecideAction src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:625 — Cyclomatic 8 with 2.3% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×3
  • Owned disposable field is never released src/Tingle.EventBus.Transports.InMemory/Client/InMemorySender.cs:16 — `InMemorySender` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `available` itself (line 16), which makes that instance its own. But `available` is named in none of the methods the disposal search covered: `Dispose` (line 199) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`available?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released src/Tingle.EventBus.Transports.InMemory/Client/InMemorySender.cs:17 — `InMemorySender` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `updateLock` itself (line 17), which makes that instance its own. But `updateLock` is named in none of the methods the disposal search covered: `Dispose` (line 199) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`updateLock?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:32 — `RabbitMqTransport` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `connectionLock` itself (line 32), which makes that instance its own. But `connectionLock` is named in none of the methods the disposal search covered: `Dispose` (line 466), `Dispose` (line 487), `Dispose` (line 466), `Dispose` (line 487) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`connectionLock?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:346 — src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:346-446 | src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:501-581 | src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:313-375 | src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:288-352 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs:6 — samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs:6-34 | samples/ConfigSample/VehicleTelemetryEventsConsumer.cs:6-34 | samples/HealthCheck/VehicleTelemetryEventsConsumer.cs:6-34 | samples/MultipleDifferentTransports/VehicleTelemetryEventsConsumer.cs:10-48 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2
  • Duplicated block (19 lines × 2) src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:12 — src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:12-30 | src/Tingle.EventBus.Transports.InMemory/ILoggerExtensions.cs:11-29 — `src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs` and `src/Tingle.EventBus.Transports.InMemory/ILoggerExtensions.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) samples/AotSupport/Program.cs:57 — samples/AotSupport/Program.cs:57-75 | samples/InMemoryBackgroundProcessing/Program.cs:56-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • Duplicated block (17 lines × 2) src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:125 — src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:125-141 | src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:204-220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (17 lines × 2) src/Tingle.EventBus/EventBus.cs:167 — src/Tingle.EventBus/EventBus.cs:167-183 | src/Tingle.EventBus/EventBus.cs:199-215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tingle.EventBus/EventBus.cs:167` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • Duplicated block (5 lines × 2) src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:113 — src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:113-117 | src/Tingle.EventBus.Transports.InMemory/ILoggerExtensions.cs:71-75 — `src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs` and `src/Tingle.EventBus.Transports.InMemory/ILoggerExtensions.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (5 lines × 2) src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:113 — src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:113-117 | src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:183-189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×2
  • Duplicated block (20 lines × 2) src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:91 — src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:91-110 | src/Tingle.EventBus.Transports.InMemory/ILoggerExtensions.cs:49-68 — `src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs` and `src/Tingle.EventBus.Transports.InMemory/ILoggerExtensions.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (20 lines × 2) samples/AotSupport/Program.cs:29 — samples/AotSupport/Program.cs:29-48 | samples/InMemoryBackgroundProcessing/Program.cs:28-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D2 · Cognitive Complexity · AmazonSqsTransport.PublishCoreAsync (cognitive 20) · ×1
  • AmazonSqsTransport.PublishCoreAsync (cognitive 20) src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:155 — AmazonSqsTransport.PublishCoreAsync has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AzureEventHubsConfigureOptions.PostConfigure (cognitive 20) · ×1
  • AzureEventHubsConfigureOptions.PostConfigure (cognitive 20) src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsConfigureOptions.cs:56 — AzureEventHubsConfigureOptions.PostConfigure has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · KafkaConfigureOptions.PostConfigure (cognitive 18) · ×1
  • KafkaConfigureOptions.PostConfigure (cognitive 18) src/Tingle.EventBus.Transports.Kafka/KafkaConfigureOptions.cs:19 — KafkaConfigureOptions.PostConfigure has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RabbitMqConfigureOptions.PostConfigure (cognitive 17) · ×1
  • RabbitMqConfigureOptions.PostConfigure (cognitive 17) src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqConfigureOptions.cs:19 — RabbitMqConfigureOptions.PostConfigure has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: AbstractEventSerializer.cs ↔ EventBusTransport.cs src/Tingle.EventBus/Serialization/AbstractEventSerializer.cs:1 — `src/Tingle.EventBus/Serialization/AbstractEventSerializer.cs` and `src/Tingle.EventBus/Transports/EventBusTransport.cs` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `2ec951e3` Drop all older targets except .NET 10 (#907); `bc1172ed` Use RegEx source generators on .NET 7 or later (#625); `83637866` Added ConfigureAwait(false) with an analyzer (at that commit the file was still `src/Tingle.EventBus/Transports/EventBusTransportBase.cs`) — run `git show` on any of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:387 — src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:387-456 | src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:346-446 | src/Tingle.EventBus.Transports.Azure.QueueStorage/AzureQueueStorageTransport.cs:288-346 | src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:313-375 | src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:266-352 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Duplicated block (22–42 lines × 2) · ×1
  • Duplicated block (22–42 lines × 2) src/Tingle.EventBus/EventContext.cs:43 — src/Tingle.EventBus/EventContext.cs:43-84 | src/Tingle.EventBus/Serialization/EventEnvelope.cs:9-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (35–37 lines × 2) · ×1
  • Duplicated block (35–37 lines × 2) src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:508 — src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:508-544 | src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:319-353 — before extracting anything, compare `src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs` and `src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:117 — src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:117-140 | src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:198-221 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (15–21 lines × 3) · ×1
  • Duplicated block (15–21 lines × 3) src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:358 — src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:358-378 | src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:508-524 | src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:319-333 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) src/Tingle.EventBus/EventBus.cs:74 — src/Tingle.EventBus/EventBus.cs:74-89 | src/Tingle.EventBus/EventBus.cs:135-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tingle.EventBus/EventBus.cs:74` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) src/Tingle.EventBus/EventContext.cs:43 — src/Tingle.EventBus/EventContext.cs:43-68 | src/Tingle.EventBus/Serialization/EventEnvelope.cs:9-24 | src/Tingle.EventBus/Serialization/Xml/XmlEventEnvelope.cs:29-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:396 — src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:396-408 | src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:278-290 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:396` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (12 lines × 5) · ×1
  • Duplicated block (12 lines × 5) src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:428 — src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:428-439 | src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:409-420 | src/Tingle.EventBus.Transports.Azure.QueueStorage/AzureQueueStorageTransport.cs:324-335 | src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:355-370 | src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:312-323 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:428` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:405` calls `SetConsumerGroup`, `SetPartitionContext`, `SetEventData` and `src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs:310` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:70 — src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:70-81 | src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:105-116 | src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:91-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:70` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) src/Tingle.EventBus.Transports.Azure.EventHubs/EventDataExtensions.cs:42 — src/Tingle.EventBus.Transports.Azure.EventHubs/EventDataExtensions.cs:42-53 | src/Tingle.EventBus/EventContext.cs:133-143 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tingle.EventBus.Transports.Azure.EventHubs/EventDataExtensions.cs:42` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:551 — src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:551-558 | src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:323-330 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:374 — src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:374-378 | src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:520-524 | src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:329-333 | src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:301-305 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:517` calls `ToString` and `src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs:326` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:72 — src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs:72-80 | src/Tingle.EventBus.Transports.InMemory/ILoggerExtensions.cs:32-38 — `src/Tingle.EventBus.Transports.Azure.ServiceBus/ILoggerExtensions.cs` and `src/Tingle.EventBus.Transports.InMemory/ILoggerExtensions.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:76 — src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:76-90 | src/Tingle.EventBus.Transports.Azure.QueueStorage/AzureQueueStorageTransport.cs:66-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (28 lines × 3) · ×1
  • Duplicated block (28 lines × 3) samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs:7 — samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs:7-34 | samples/ConfigSample/VehicleTelemetryEventsConsumer.cs:7-34 | samples/HealthCheck/VehicleTelemetryEventsConsumer.cs:7-34 — `samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs` and `samples/ConfigSample/VehicleTelemetryEventsConsumer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 41 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) samples/ConfigSample/VisualsProducerService.cs:7 — samples/ConfigSample/VisualsProducerService.cs:7-29 | samples/MultipleSimilarTransports/Program.cs:28-50 — before extracting anything, compare `samples/ConfigSample/VisualsProducerService.cs` and `samples/MultipleSimilarTransports/Program.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×1
  • Duplicated block (19 lines × 3) samples/AmazonSqsAndSns/PublisherService.cs:7 — samples/AmazonSqsAndSns/PublisherService.cs:7-25 | samples/MultipleConsumers/PublisherService.cs:7-25 | samples/SimplePublisher/PublisherService.cs:7-25 — `samples/AmazonSqsAndSns/PublisherService.cs` and `samples/MultipleConsumers/PublisherService.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 19 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×1
  • Duplicated block (13 lines × 4) samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs:9 — samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs:9-21 | samples/ConfigSample/VehicleTelemetryEventsConsumer.cs:9-21 | samples/HealthCheck/VehicleTelemetryEventsConsumer.cs:9-21 | samples/MultipleDifferentTransports/VehicleTelemetryEventsConsumer.cs:22-34 — `samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs` and `samples/ConfigSample/VehicleTelemetryEventsConsumer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 41 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/MultipleDifferentTransports/VehicleTelemetryEventsConsumer.cs:36` calls `GetIotHubDeviceId` and `samples/AzureManagedIdentity/VehicleTelemetryEventsConsumer.cs:23` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) samples/AzureManagedIdentity/VehicleTelemetryEvent.cs:5 — samples/AzureManagedIdentity/VehicleTelemetryEvent.cs:5-17 | samples/ConfigSample/VehicleDoorOpenedEvent.cs:13-21 | samples/HealthCheck/VehicleTelemetryEvent.cs:5-17 — `samples/AzureManagedIdentity/VehicleTelemetryEvent.cs` and `samples/HealthCheck/VehicleTelemetryEvent.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 13 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `samples/AzureManagedIdentity/VehicleTelemetryEvent.cs:5` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) samples/MultipleConsumers/FirstEventConsumer.cs:7 — samples/MultipleConsumers/FirstEventConsumer.cs:7-12 | samples/MultipleConsumers/SecondEventConsumer.cs:7-12 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: Tingle.EventBus src/Tingle.EventBus/Tingle.EventBus.csproj:1 — Tingle.EventBus: abstractness 0.26, instability 0.00, distance 0.74 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
D8 · Code Coverage · No test project references Tingle.EventBus.Transports.Amazon.Kinesis · ×1
  • No test project references Tingle.EventBus.Transports.Amazon.Kinesis src/Tingle.EventBus.Transports.Amazon.Kinesis/Tingle.EventBus.Transports.Amazon.Kinesis.csproj — No test project in this repository references Tingle.EventBus.Transports.Amazon.Kinesis (7 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 40.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 Tingle.EventBus.Transports.Amazon.Sqs · ×1
  • No test project references Tingle.EventBus.Transports.Amazon.Sqs src/Tingle.EventBus.Transports.Amazon.Sqs/Tingle.EventBus.Transports.Amazon.Sqs.csproj — No test project in this repository references Tingle.EventBus.Transports.Amazon.Sqs (7 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 40.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 Tingle.EventBus.Transports.RabbitMQ · ×1
  • No test project references Tingle.EventBus.Transports.RabbitMQ src/Tingle.EventBus.Transports.RabbitMQ/Tingle.EventBus.Transports.RabbitMQ.csproj — No test project in this repository references Tingle.EventBus.Transports.RabbitMQ (6 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 40.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 Tingle.EventBus.Serializers.NewtonsoftJson · ×1
  • No test project references Tingle.EventBus.Serializers.NewtonsoftJson src/Tingle.EventBus.Serializers.NewtonsoftJson/Tingle.EventBus.Serializers.NewtonsoftJson.csproj — No test project in this repository references Tingle.EventBus.Serializers.NewtonsoftJson (5 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 40.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 Tingle.EventBus.Transports.Amazon.Abstractions · ×1
  • No test project references Tingle.EventBus.Transports.Amazon.Abstractions src/Tingle.EventBus.Transports.Amazon.Abstractions/Tingle.EventBus.Transports.Amazon.Abstractions.csproj — No test project in this repository references Tingle.EventBus.Transports.Amazon.Abstractions (4 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 40.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 182 · ×1
  • CRAP 182: KafkaConfigureOptions.PostConfigure src/Tingle.EventBus.Transports.Kafka/KafkaConfigureOptions.cs:19 — Cyclomatic 13 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 124 · ×1
  • CRAP 124: AzureServiceBusTransport.OnMessageReceivedAsync src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:500 — Cyclomatic 11 with 2.3% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 72 · ×1
  • CRAP 72: AzureServiceBusConfigureOptions.PostConfigure src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusConfigureOptions.cs:41 — Cyclomatic 8 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 66 · ×1
  • CRAP 66: AzureEventHubsTransport.OnEventReceivedAsync src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:345 — Cyclomatic 8 with 3.3% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 53 · ×1
  • CRAP 53: AzureServiceBusTransport.PublishCoreAsync src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:119 — Cyclomatic 7 with 2.3% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
X2 · Cancellation propagation · Async call defeats the CancellationToken · ×1
  • Async call defeats the CancellationToken: ConnectConsumersAsync src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:281 — Holds a CancellationToken but hands `CancellationToken.None` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
Minor — 32 finding(s)
M4 · Documentation accuracy · README/code drift · ×12
  • README/code drift README.md:34 — README.md links to `./docs/bus-concepts-and-configuration.md`, but `docs/bus-concepts-and-configuration.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:38 — README.md links to `./docs/transport-selection.md`, but `docs/transport-selection.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:39 — README.md links to `./docs/multi-transport-one-bus.md`, but `docs/multi-transport-one-bus.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:40 — README.md links to `./docs/retries.md`, but `docs/retries.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:41 — README.md links to `./docs/events-and-consumers.md`, but `docs/events-and-consumers.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:42 — README.md links to `./docs/observability.md`, but `docs/observability.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:47 — README.md links to `./docs/work-with-configuration.md`, but `docs/work-with-configuration.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:48 — README.md links to `./docs/work-with-azure-iot-hub.md`, but `docs/work-with-azure-iot-hub.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:49 — README.md links to `./docs/work-with-azure-managed-identities.md`, but `docs/work-with-azure-managed-identities.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:50 — README.md links to `./docs/advanced-service-bus-options.md`, but `docs/advanced-service-bus-options.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:51 — README.md links to `./docs/work-with-feature-management.md`, but `docs/work-with-feature-management.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:52 — README.md links to `./docs/extend-event-configuration.md`, but `docs/extend-event-configuration.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X10 · Duplicated predicate · Duplicated predicate · ×5
  • Duplicated predicate src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs:438 — `!successful && ecr.UnhandledErrorBehaviour == UnhandledConsumerErrorBehaviour.Deadletter` appears character-identically in 5 files — src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsTransport.cs, src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs, src/Tingle.EventBus.Transports.Azure.QueueStorage/AzureQueueStorageTransport.cs, src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:147 — `@event.Expires != null && @event.Expires > DateTimeOffset.UtcNow` appears character-identically in 2 files — src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs, src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs:141 — `scheduled != null && scheduled > DateTimeOffset.UtcNow` appears character-identically in 2 files — src/Tingle.EventBus.Transports.Azure.ServiceBus/AzureServiceBusTransport.cs, src/Tingle.EventBus.Transports.InMemory/InMemoryTransport.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs:484 — `successful || behaviour == UnhandledConsumerErrorBehaviour.Deadletter || behaviour == UnhandledConsumerErrorBehaviour.Discard` appears character-identically in 2 files — src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsTransport.cs, src/Tingle.EventBus.Transports.Kafka/KafkaTransport.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Tingle.EventBus.Transports.Azure.EventHubs/EventDataExtensions.cs:43 — `t.IsGenericType && t.GetGenericTypeDefinition().Equals(typeof(Nullable<>))` appears character-identically in 2 files — src/Tingle.EventBus.Transports.Azure.EventHubs/EventDataExtensions.cs, src/Tingle.EventBus/EventContext.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.
D24 · Comment Value · redundant comment · ×1
  • redundant comment src/Tingle.EventBus.Transports.RabbitMQ/RabbitMqTransport.cs:281 — "do not chain CancellationToken" — keep - records a call-site gotcha
D27 · Navigability · Pass-through layer · ×1
  • Pass-through layer src/Tingle.EventBus/Publisher/WrappedEventPublisher.cs:11 — WrappedEventPublisher: all 5 public methods forward their arguments unchanged to inner and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call inner directly, or give the layer a job.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Commented-out code · ×1
  • Commented-out code src/Tingle.EventBus/DependencyInjection/EventBusBuilder.cs:131 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
M3 · Folder & project structure · Inconsistent root namespaces · ×1
  • Inconsistent root namespaces — Only 17/32 projects share a common root namespace — the code's module identity is inconsistent.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3350 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
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.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 133/140 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X2 · Cancellation propagation · Some async methods drop the CancellationToken they accept · ×1
  • Some async methods drop the CancellationToken they accept — 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~1.4 `!` suppressions per 1k syntax nodes — 79 suppression(s) across the 56981 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Minor — 34 finding(s)
D12 · Dependency Hygiene · Outdated · ×23
  • Outdated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 10.0.7 → 10.0.13 available (referenced by AmazonSqsAndSns).
  • Outdated: Microsoft.Extensions.Diagnostics.HealthChecks — Microsoft.Extensions.Diagnostics.HealthChecks 10.0.7 → 10.0.13 available (referenced by HealthCheck).
  • Outdated: Microsoft.Extensions.Caching.Memory — Microsoft.Extensions.Caching.Memory 10.0.7 → 10.0.13 available (referenced by MultiEventsConsumer).
  • Outdated: AWSSDK.Core — AWSSDK.Core 4.0.6 → 4.0.102.13 available (referenced by Tingle.EventBus.Transports.Amazon.Abstractions).
  • Outdated: AWSSDK.Kinesis — AWSSDK.Kinesis 4.0.8.13 → 4.0.104.6 available (referenced by Tingle.EventBus.Transports.Amazon.Kinesis).
  • Outdated: AWSSDK.SimpleNotificationService — AWSSDK.SimpleNotificationService 4.0.2.29 → 4.0.100.21 available (referenced by Tingle.EventBus.Transports.Amazon.Sqs).
  • Outdated: AWSSDK.SQS — AWSSDK.SQS 4.0.2.27 → 4.0.100.20 available (referenced by Tingle.EventBus.Transports.Amazon.Sqs).
  • Outdated: Azure.Core — Azure.Core 1.54.0 → 1.63.0 available (referenced by Tingle.EventBus.Transports.Azure.Abstractions).
  • Outdated: Azure.Storage.Queues — Azure.Storage.Queues 12.25.0 → 12.28.1 available (referenced by Tingle.EventBus.Transports.Azure.QueueStorage).
  • Outdated: Azure.Messaging.ServiceBus — Azure.Messaging.ServiceBus 7.20.1 → 7.21.0 available (referenced by Tingle.EventBus.Transports.Azure.ServiceBus).
  • Outdated: Confluent.Kafka — Confluent.Kafka 2.14.0 → 2.16.0 available (referenced by Tingle.EventBus.Transports.Kafka).
  • Outdated: RabbitMQ.Client — RabbitMQ.Client 7.2.1 → 7.2.2 available (referenced by Tingle.EventBus.Transports.RabbitMQ).
  • Outdated: Microsoft.Extensions.Configuration.Binder — Microsoft.Extensions.Configuration.Binder 10.0.7 → 10.0.13 available (referenced by Tingle.EventBus).
  • Outdated: Microsoft.Extensions.Hosting.Abstractions — Microsoft.Extensions.Hosting.Abstractions 10.0.7 → 10.0.13 available (referenced by Tingle.EventBus).
  • Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 10.0.7 → 10.0.13 available (referenced by Tingle.EventBus).
  • Outdated: Microsoft.Extensions.Options — Microsoft.Extensions.Options 10.0.7 → 10.0.13 available (referenced by Tingle.EventBus).
  • Outdated: Polly.Core — Polly.Core 8.6.6 → 8.8.0 available (referenced by Tingle.EventBus).
  • Outdated: System.Memory.Data — System.Memory.Data 10.0.7 → 10.0.13 available (referenced by Tingle.EventBus).
  • Outdated: coverlet.collector — coverlet.collector 10.0.0 → 10.1.0 available (referenced by Tingle.EventBus.Tests).
  • Outdated: MartinCostello.Logging.XUnit.v3 — MartinCostello.Logging.XUnit.v3 0.7.0 → 0.7.1 available (referenced by Tingle.EventBus.Tests).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 18.5.1 → 18.11.0 available (referenced by Tingle.EventBus.Tests).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 3.1.5 → 4.0.1 available (referenced by Tingle.EventBus.Tests).
  • Outdated: xunit.v3 — xunit.v3 3.2.2 → 4.0.2 available (referenced by Tingle.EventBus.Tests).
D19 · Documentation Quality · XML-doc coverage · ×11
  • XML-doc coverage: SimplePublisher samples/SimplePublisher/SimplePublisher.csproj — SimplePublisher: 50 % XML-doc coverage (3/6).
  • XML-doc coverage: Tingle.EventBus.Serializers.NewtonsoftJson src/Tingle.EventBus.Serializers.NewtonsoftJson/Tingle.EventBus.Serializers.NewtonsoftJson.csproj — Tingle.EventBus.Serializers.NewtonsoftJson: 75 % XML-doc coverage (6/8).
  • XML-doc coverage: Tingle.EventBus.Transports.Amazon.Abstractions src/Tingle.EventBus.Transports.Amazon.Abstractions/Tingle.EventBus.Transports.Amazon.Abstractions.csproj — Tingle.EventBus.Transports.Amazon.Abstractions: 100 % XML-doc coverage (15/15).
  • XML-doc coverage: Tingle.EventBus.Transports.Amazon.Kinesis src/Tingle.EventBus.Transports.Amazon.Kinesis/Tingle.EventBus.Transports.Amazon.Kinesis.csproj — Tingle.EventBus.Transports.Amazon.Kinesis: 76 % XML-doc coverage (13/17).
  • XML-doc coverage: Tingle.EventBus.Transports.Azure.Abstractions src/Tingle.EventBus.Transports.Azure.Abstractions/Tingle.EventBus.Transports.Azure.Abstractions.csproj — Tingle.EventBus.Transports.Azure.Abstractions: 100 % XML-doc coverage (6/6).
  • XML-doc coverage: Tingle.EventBus.Transports.Azure.EventHubs src/Tingle.EventBus.Transports.Azure.EventHubs/Tingle.EventBus.Transports.Azure.EventHubs.csproj — Tingle.EventBus.Transports.Azure.EventHubs: 85 % XML-doc coverage (105/123).
  • XML-doc coverage: Tingle.EventBus.Transports.Azure.QueueStorage src/Tingle.EventBus.Transports.Azure.QueueStorage/Tingle.EventBus.Transports.Azure.QueueStorage.csproj — Tingle.EventBus.Transports.Azure.QueueStorage: 55 % XML-doc coverage (17/31).
  • XML-doc coverage: Tingle.EventBus.Transports.InMemory src/Tingle.EventBus.Transports.InMemory/Tingle.EventBus.Transports.InMemory.csproj — Tingle.EventBus.Transports.InMemory: 77 % XML-doc coverage (77/100).
  • XML-doc coverage: Tingle.EventBus.Transports.Kafka src/Tingle.EventBus.Transports.Kafka/Tingle.EventBus.Transports.Kafka.csproj — Tingle.EventBus.Transports.Kafka: 60 % XML-doc coverage (15/25).
  • XML-doc coverage: Tingle.EventBus.Transports.RabbitMQ src/Tingle.EventBus.Transports.RabbitMQ/Tingle.EventBus.Transports.RabbitMQ.csproj — Tingle.EventBus.Transports.RabbitMQ: 94 % XML-doc coverage (15/16).
  • XML-doc coverage: Tingle.EventBus src/Tingle.EventBus/Tingle.EventBus.csproj — Tingle.EventBus: 83 % XML-doc coverage (325/391).

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-1c893970583c4f1a90f4dbbef42e15c8/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1c893970583c4f1a90f4dbbef42e15c8/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .11artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list Tingle.EventBus.slnx package --vulnerable --include-transitive --format json0artifacts/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 36 file(s) — `src/Tingle.EventBus.Transports.Amazon.Abstractions/AmazonTransportConfigureOptions.cs`, `src/Tingle.EventBus.Transports.Amazon.Kinesis/AmazonKinesisConfigureOptions.cs`, `src/Tingle.EventBus.Transports.Amazon.Sqs/AmazonSqsConfigureOptions.cs`, `src/Tingle.EventBus.Transports.Azure.Abstractions/AzureTransportConfigureOptions.cs`, `src/Tingle.EventBus.Transports.Azure.EventHubs/AzureEventHubsConfigureOptions.cs`, … (+31 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 01a16170-24e7-76d5-b6f6-a7ef4da1b57b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 14 · Warnings: 144 · Recommendations: 32 · Info: 34 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 02:28 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