Public report of dotnetcore/CAP, published 23 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, 23 October 2026, 11:21 UTC · Survey ID cd_5367046f35c04f9faf00760a25ed3603

dotnetcore/CAP

Measured 23 October 2026, 11:18 UTC, at code version ad19c50

Regression: 2 dimensions fell since the last survey

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

CAI score 50out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 4 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.

Architecture 86 Strong Maturity 77 Strong Accessibility 70 Adequate Performance 66 Adequate Code Health 53 Adequate Security and Compliance 53 Adequate Production Readiness 41 Weak

A small codebase: 19,579 lines of product code in 39 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 41

Findings by how serious they are

90 critical 330 serious 157 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 11:18 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 ▸

85of 89 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
486of 577 findings point to an exact file and line, so you can open each one in the code. The other 91 concern the repository as a whole, such as missing documentation.
89dimensions across 7 lenses, read from 19,579 lines of product code in 39 projects.
Chapters

Executive summary

dotnetcore/CAP scores 50 out of 100 and is rated Adequate, while six of its seven lenses score higher still: Architecture at 86 and Maturity at 77, both rated Strong, and Accessibility at 70, Performance at 66 and Security and Compliance and Code Health at 53, all rated Adequate.

The score is lower than those six because the weakest lens counts most, and here that is Production Readiness, which scores 41 and is rated Weak. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 3 Leaked secret finding(s) in REDACTED Scanning and to resolve the 8 Deprecated finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 50 to about 58.

90 findings are critical: 35 in Explicit Debt, 17 in Dependency Vulnerabilities, 16 in Static Analysis (SAST), 11 in Secrets (history), three in REDACTED Scanning, two in Change Coupling, two in Incompleteness & stubs, two in Security & performance tooling, one in Async correctness and one in Project dependency cycles.

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

Code Health 53 Adequate, capped by Structured logging Architecture 86 Strong Maturity 77 Strong Production Readiness 41 Weak, capped by Dependency Hygiene, REDACTED Scanning, Security & performance tooling and Outbound HTTP resilience Security and Compliance 53 Adequate, capped by Secrets (history), Static Analysis (SAST), Dependency Vulnerabilities, Supply-chain Provenance & Signing and Data Protection Accessibility 70 Adequate Performance 66 Adequate

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

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

If Production Readiness rose from 41 to 70, the lowest score rated Strong, the score would rise from 50 to about 58.

Code composition: what the lines of code are
Business logic 31%Supporting code 54%Tests 15%Generated by tools 0%
New since the last survey: 107 findings

These 107 critical or serious findings weren't in the previous survey, on 9 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

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

These 105 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one. The first 100 are listed here.

  • Code Coverage · No test project references DotNetCore.CAP.NATS src/DotNetCore.CAP.NATS/DotNetCore.CAP.NATS.csproj
  • Dependency Hygiene · Deprecated: xunit
  • Explicit Debt · EmptyCatchBlock src/DotNetCore.CAP.NATS/NATSConsumerClient.cs
  • Static Analysis (SAST) · Medium: REDACTED samples/Sample.Kafka.PostgreSql/Controllers/ValuesController.cs
  • Static Analysis (SAST) · Medium: REDACTED samples/Sample.RabbitMQ.MySql/Controllers/ValuesController.cs
  • Static Analysis (SAST) · Medium: REDACTED samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing REDACTED
  • Async correctness · async void method: SubscriptionMessageHandler src/DotNetCore.CAP.NATS/NATSConsumerClient.cs
  • Cancellation propagation · Async method without CancellationToken: ExecuteWithParameterAsync src/DotNetCore.CAP/Internal/ISubscribeInvoker.Default.cs
  • Cancellation propagation · Async method without CancellationToken: GetSafelyAsync src/DotNetCore.CAP/Processor/IProcessor.NeedRetry.cs
  • Cancellation propagation · Async method without CancellationToken: ConsumeAsync src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs
  • Cancellation propagation · Async method without CancellationToken: BasicReject src/DotNetCore.CAP.RabbitMQ/RabbitMQBasicConsumer.cs
  • Cancellation propagation · Async method without CancellationToken: ConnectAsync src/DotNetCore.CAP.RabbitMQ/RabbitMQConsumerClient.cs
  • Cancellation propagation · Async method without CancellationToken: ChangeMessageStateAsync REDACTED
  • Cancellation propagation · Async method without CancellationToken: StoreReceivedMessage REDACTED
  • Cancellation propagation · Async method without CancellationToken: GetMessagesOfNeedRetryAsync REDACTED
  • Cancellation propagation · Async method without CancellationToken: ExecuteNonQueryAsync src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: ExecuteReaderAsync src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: ExecuteScalarAsync src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: GetNumberOfMessage src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs
  • Cancellation propagation · Async method without CancellationToken: GetTimelineStats src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs
  • Cancellation propagation · Async method without CancellationToken: GetMessageAsync src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs
  • Cancellation propagation · Async method without CancellationToken: ChangeMessageStateAsync REDACTED
  • Cancellation propagation · Async method without CancellationToken: StoreReceivedMessage REDACTED
  • Cancellation propagation · Async method without CancellationToken: GetMessagesOfNeedRetryAsync REDACTED
  • Cancellation propagation · Async method without CancellationToken: ExecuteNonQueryAsync src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: ExecuteReaderAsync src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: ExecuteScalarAsync src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: GetNumberOfMessage src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs
  • Cancellation propagation · Async method without CancellationToken: GetTimelineStats src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs
  • Cancellation propagation · Async method without CancellationToken: GetMessageAsync src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs
  • Cancellation propagation · Async method without CancellationToken: Start samples/Sample.RabbitMQ.MySql/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: Stop samples/Sample.RabbitMQ.MySql/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: Delay samples/Sample.RabbitMQ.MySql/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: AdonetWithTransaction samples/Sample.RabbitMQ.MySql/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: ChangeMessageStateAsync src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs
  • Cancellation propagation · Async method without CancellationToken: StoreReceivedMessage src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs
  • Cancellation propagation · Async method without CancellationToken: GetMessagesOfNeedRetryAsync src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs
  • Cancellation propagation · Async method without CancellationToken: ExecuteNonQueryAsync src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: ExecuteReaderAsync src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: ExecuteScalarAsync src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: GetNumberOfMessage src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs
  • Cancellation propagation · Async method without CancellationToken: GetTimelineStats src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs
  • Cancellation propagation · Async method without CancellationToken: GetMessageAsync src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs
  • Cancellation propagation · Async method without CancellationToken: FindReceivedMessages src/DotNetCore.CAP.MongoDB/IMonitoringApi.MongoDB.cs
  • Cancellation propagation · Async method without CancellationToken: FindPublishedMessages src/DotNetCore.CAP.MongoDB/IMonitoringApi.MongoDB.cs
  • Cancellation propagation · Async method without CancellationToken: GetNumberOfReceivedMessages src/DotNetCore.CAP.MongoDB/IMonitoringApi.MongoDB.cs
  • Cancellation propagation · Async method without CancellationToken: GetNumberOfPublishedMessages src/DotNetCore.CAP.MongoDB/IMonitoringApi.MongoDB.cs
  • Cancellation propagation · Async method without CancellationToken: Delay samples/Sample.RabbitMQ.MongoDB/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: _serviceBusProcessor_ProcessMessageAsync src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs
  • Cancellation propagation · Async method without CancellationToken: _serviceBusProcessor_ProcessSessionMessageAsync src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs
  • Cancellation propagation · Async method without CancellationToken: ConnectAsync src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs
  • Cancellation propagation · Async method without CancellationToken: Invoke src/DotNetCore.CAP.Dashboard/GatewayProxy/GatewayProxyAgent.cs
  • Cancellation propagation · Async method without CancellationToken: SetResponseOnHttpContext src/DotNetCore.CAP.Dashboard/GatewayProxy/GatewayProxyAgent.cs
  • Cancellation propagation · Async method without CancellationToken: MapContent src/DotNetCore.CAP.Dashboard/GatewayProxy/IRequestMapper.Default.cs
  • Cancellation propagation · Async method without CancellationToken: ToByteArray src/DotNetCore.CAP.Dashboard/GatewayProxy/IRequestMapper.Default.cs
  • Cancellation propagation · Async method without CancellationToken: Metrics REDACTED
  • Cancellation propagation · Async method without CancellationToken: MetaInfo REDACTED
  • Cancellation propagation · Async method without CancellationToken: Stats REDACTED
  • Cancellation propagation · Async method without CancellationToken: MetricsHistory REDACTED
  • Cancellation propagation · Async method without CancellationToken: PublishedMessageDetails REDACTED
  • Cancellation propagation · Async method without CancellationToken: ReceivedMessageDetails REDACTED
  • Cancellation propagation · Async method without CancellationToken: PublishedRequeue REDACTED
  • Cancellation propagation · Async method without CancellationToken: PublishedDelete REDACTED
  • Cancellation propagation · Async method without CancellationToken: ReceivedRequeue REDACTED
  • Cancellation propagation · Async method without CancellationToken: ReceivedDelete REDACTED
  • Cancellation propagation · Async method without CancellationToken: PublishedList REDACTED
  • Cancellation propagation · Async method without CancellationToken: ReceivedList REDACTED
  • Cancellation propagation · Async method without CancellationToken: Subscribers REDACTED
  • Cancellation propagation · Async method without CancellationToken: Nodes REDACTED
  • Cancellation propagation · Async method without CancellationToken: ListServices REDACTED
  • Cancellation propagation · Async method without CancellationToken: PingServices REDACTED
  • Cancellation propagation · Async method without CancellationToken: Start samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: Stop samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: WithoutTransaction samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: Delay samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: DelayWithTransaction samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: AdonetWithTransaction samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: TypePublish samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: Handle samples/Sample.RabbitMQ.SqlServer/Messages/VeryFastProcessingReceiver.cs
  • Cancellation propagation · Async method without CancellationToken: Handle samples/Sample.RabbitMQ.SqlServer/Messages/XSlowProcessingReceiver.cs
  • Cancellation propagation · Async method without CancellationToken: Start samples/Sample.Kafka.PostgreSql/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: Stop samples/Sample.Kafka.PostgreSql/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: Delay samples/Sample.Kafka.PostgreSql/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: WithoutTransaction samples/Sample.Kafka.PostgreSql/Controllers/ValuesController.cs
  • Cancellation propagation · Async method without CancellationToken: ShowTime samples/Sample.ConsoleApp/EventSubscriber.cs
  • Cancellation propagation · Async method without CancellationToken: ConnectAsync src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs
  • Cancellation propagation · Async method without CancellationToken: GenerateSqsAccessPolicyAsync src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs
  • Cancellation propagation · Async method without CancellationToken: SubscribeToTopics src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs
  • Cancellation propagation · Async method without CancellationToken: FetchExistingTopicArns src/DotNetCore.CAP.AmazonSQS/ITransport.AmazonSQS.cs
  • Cancellation propagation · Async method without CancellationToken: SubscriptionMessageHandler src/DotNetCore.CAP.NATS/NATSConsumerClient.cs
  • Cancellation propagation · Async method without CancellationToken: Publish REDACTED
  • Cancellation propagation · Async method without CancellationToken: Init src/DotNetCore.CAP.RedisStreams/IConnectionPool.Default.cs
  • Cancellation propagation · Async method without CancellationToken: ConnectAsync src/DotNetCore.CAP.RedisStreams/IConnectionPool.LazyConnection.cs
  • Cancellation propagation · Async method without CancellationToken: ConsumeMessages src/DotNetCore.CAP.RedisStreams/IConsumerClient.Redis.cs
  • Cancellation propagation · Async method without CancellationToken: ConnectAsync src/DotNetCore.CAP.RedisStreams/IRedisStream.Manager.Default.cs
  • Cancellation propagation · Async method without CancellationToken: TryGetOrCreateConsumerGroupPositionsAsync src/DotNetCore.CAP.RedisStreams/IRedisStream.Manager.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: TryGetOrCreateStreamConsumerGroupAsync src/DotNetCore.CAP.RedisStreams/IRedisStream.Manager.Extensions.cs
  • Cancellation propagation · Async method without CancellationToken: TryGetOrCreateStreamGroupAsync src/DotNetCore.CAP.RedisStreams/IRedisStream.Manager.Extensions.cs
Rebuild cost: about €33,000 · Estimate
Cost to rebuild€11,000 to €55,000, for 180 to 579 hours of work, about 0.2 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 50. 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: 19,579 lines of product code
Comment linesThe estimate prices 16,512 lines. Comment lines count towards the size of 19,579 lines but aren't priced as work.

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

Top priorities

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

1
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 8 points · Low effort · REDACTED Scanning
2
Resolve the 8 Deprecated finding(s) in Dependency Hygiene — start with package.json (4), DotNetCore.CAP.MySql.Test.csproj, DotNetCore.CAP.Test.csproj.
Raises the score by about 8 points · Low effort · Dependency Hygiene
3
Resolve the 7 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json.
Raises the score by about 7 points · Low effort · Dependency Hygiene

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €33,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 41 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 3 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — 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 BuildScript BuildScript DotNetCore.CAP CAP DotNetCore.CAP.AmazonSQS AmazonSQS DotNetCore.CAP.AmazonSQS->DotNetCore.CAP DotNetCore.CAP.AzureServiceBus AzureServiceBus DotNetCore.CAP.AzureServiceBus->DotNetCore.CAP DotNetCore.CAP.Dashboard Dashboard DotNetCore.CAP.Dashboard->DotNetCore.CAP DotNetCore.CAP.Dashboard.K8s K8s DotNetCore.CAP.Dashboard.K8s->DotNetCore.CAP.Dashboard DotNetCore.CAP.InMemoryStorage InMemoryStorage DotNetCore.CAP.InMemoryStorage->DotNetCore.CAP DotNetCore.CAP.Kafka Kafka DotNetCore.CAP.Kafka->DotNetCore.CAP DotNetCore.CAP.MongoDB MongoDB DotNetCore.CAP.MongoDB->DotNetCore.CAP DotNetCore.CAP.MySql MySql DotNetCore.CAP.MySql->DotNetCore.CAP DotNetCore.CAP.NATS NATS DotNetCore.CAP.NATS->DotNetCore.CAP DotNetCore.CAP.OpenTelemetry OpenTelemetry DotNetCore.CAP.OpenTelemetry->DotNetCore.CAP DotNetCore.CAP.PostgreSql PostgreSql DotNetCore.CAP.PostgreSql->DotNetCore.CAP DotNetCore.CAP.Pulsar Pulsar DotNetCore.CAP.Pulsar->DotNetCore.CAP DotNetCore.CAP.RabbitMQ RabbitMQ DotNetCore.CAP.RabbitMQ->DotNetCore.CAP DotNetCore.CAP.RedisStreams RedisStreams DotNetCore.CAP.RedisStreams->DotNetCore.CAP DotNetCore.CAP.SqlServer SqlServer DotNetCore.CAP.SqlServer->DotNetCore.CAP

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.

40 modules, with 102 dependencies between them. One loop runs through 8 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 BuildScript2 DotNetCore.CAP.Dashboard.GatewayProxy.Requester3 DotNetCore.CAP.Messages4 DotNetCore.CAP.OpenTelemetry5 Microsoft.Extensions.Internal6 OpenTelemetry.Trace7 samples.Sample_Dashboard_Jwt.wwwroot.js8 src.DotNetCore_CAP_Dashboard.wwwroot.src9 src.DotNetCore_CAP_Dashboard.wwwroot.src.assets10 DotNetCore.CAP.AzureServiceBus.Producer11 DotNetCore.CAP.Monitoring12 DotNetCore.CAP.Serialization13 DotNetCore.CAP.Persistence14 DotNetCore.CAP.Transport15 DotNetCore.CAP.AzureServiceBus.Helpers16 DotNetCore.CAP.Diagnostics17 DotNetCore.CAP.Internal18 DotNetCore.CAP.Pulsar19 DotNetCore.CAP.Filter20 DotNetCore.CAP.SqlServer.Diagnostics21 DotNetCore.CAP22 DotNetCore.CAP.AmazonSQS23 DotNetCore.CAP.AzureServiceBus24 DotNetCore.CAP.Dashboard.NodeDiscovery25 DotNetCore.CAP.InMemoryStorage26 DotNetCore.CAP.Kafka27 DotNetCore.CAP.MongoDB28 DotNetCore.CAP.MySql29 DotNetCore.CAP.NATS30 DotNetCore.CAP.PostgreSql31 DotNetCore.CAP.Processor32 DotNetCore.CAP.RabbitMQ33 DotNetCore.CAP.RedisStreams34 DotNetCore.CAP.SqlServer35 Microsoft.EntityFrameworkCore.Storage36 MongoDB.Driver37 DotNetCore.CAP.Dashboard.GatewayProxy38 DotNetCore.CAP.Dashboard.K8s39 Microsoft.Extensions.DependencyInjection40 DotNetCore.CAP.Dashboard
1 BuildScript
2 DotNetCore.CAP.Dashboard.GatewayProxy.Requester
3 DotNetCore.CAP.Messages
4 DotNetCore.CAP.OpenTelemetry
5 Microsoft.Extensions.Internal
6 OpenTelemetry.Trace
7 samples.Sample_Dashboard_Jwt.wwwroot.js
8 src.DotNetCore_CAP_Dashboard.wwwroot.src
9 src.DotNetCore_CAP_Dashboard.wwwroot.src.assets
10 DotNetCore.CAP.AzureServiceBus.Producer1
11 DotNetCore.CAP.Monitoring21
12 DotNetCore.CAP.Serialization41
13 DotNetCore.CAP.Persistence211
14 DotNetCore.CAP.Transport2121
15 DotNetCore.CAP.AzureServiceBus.Helpers1
16 DotNetCore.CAP.Diagnostics42
17 DotNetCore.CAP.Internal61310813
18 DotNetCore.CAP.Pulsar274
19 DotNetCore.CAP.Filter4
20 DotNetCore.CAP.SqlServer.Diagnostics12
21 DotNetCore.CAP1225111
22 DotNetCore.CAP.AmazonSQS274
23 DotNetCore.CAP.AzureServiceBus2274
24 DotNetCore.CAP.Dashboard.NodeDiscovery11
25 DotNetCore.CAP.InMemoryStorage2615132
26 DotNetCore.CAP.Kafka274
27 DotNetCore.CAP.MongoDB262423
28 DotNetCore.CAP.MySql262625
29 DotNetCore.CAP.NATS274
30 DotNetCore.CAP.PostgreSql262625
31 DotNetCore.CAP.Processor4363
32 DotNetCore.CAP.RabbitMQ385
33 DotNetCore.CAP.RedisStreams377
34 DotNetCore.CAP.SqlServer262625
35 Microsoft.EntityFrameworkCore.Storage1
36 MongoDB.Driver1
37 DotNetCore.CAP.Dashboard.GatewayProxy13
38 DotNetCore.CAP.Dashboard.K8s13
39 Microsoft.Extensions.DependencyInjection71
40 DotNetCore.CAP.Dashboard1111
Uses a module listed above itPart of a loopThe module itself
1 BuildScript2 DotNetCore.CAP.Dashboard.GatewayProxy.Requester3 DotNetCore.CAP.Messages4 DotNetCore.CAP.OpenTelemetry5 Microsoft.Extensions.Internal6 OpenTelemetry.Trace7 samples.Sample_Dashboard_Jwt.wwwroot.js8 src.DotNetCore_CAP_Dashboard.wwwroot.src9 src.DotNetCore_CAP_Dashboard.wwwroot.src.assets10 DotNetCore.CAP.AzureServiceBus.Producer11 DotNetCore.CAP.Monitoring12 DotNetCore.CAP.Serialization13 DotNetCore.CAP.Persistence14 DotNetCore.CAP.Transport15 DotNetCore.CAP.AzureServiceBus.Helpers16 DotNetCore.CAP.Diagnostics17 DotNetCore.CAP.Internal18 DotNetCore.CAP.Pulsar19 DotNetCore.CAP.Filter20 DotNetCore.CAP.SqlServer.Diagnostics21 DotNetCore.CAP22 DotNetCore.CAP.AmazonSQS23 DotNetCore.CAP.AzureServiceBus24 DotNetCore.CAP.Dashboard.NodeDiscovery25 DotNetCore.CAP.InMemoryStorage26 DotNetCore.CAP.Kafka27 DotNetCore.CAP.MongoDB28 DotNetCore.CAP.MySql29 DotNetCore.CAP.NATS30 DotNetCore.CAP.PostgreSql31 DotNetCore.CAP.Processor32 DotNetCore.CAP.RabbitMQ33 DotNetCore.CAP.RedisStreams34 DotNetCore.CAP.SqlServer35 Microsoft.EntityFrameworkCore.Storage36 MongoDB.Driver37 DotNetCore.CAP.Dashboard.GatewayProxy38 DotNetCore.CAP.Dashboard.K8s39 Microsoft.Extensions.DependencyInjection40 DotNetCore.CAP.DashboardBuildScript1DotNetCore.CAP.Dashboard.GatewayProxy.Requester2DotNetCore.CAP.Messages3DotNetCore.CAP.OpenTelemetry4Microsoft.Extensions.Internal5OpenTelemetry.Trace6samples.Sample_Dashboard_Jwt.wwwroot.js7src.DotNetCore_CAP_Dashboard.wwwroot.src8src.DotNetCore_CAP_Dashboard.wwwroot.src.assets9DotNetCore.CAP.AzureServiceBus.Producer10DotNetCore.CAP.Monitoring11DotNetCore.CAP.Serialization12DotNetCore.CAP.Persistence13DotNetCore.CAP.Transport14DotNetCore.CAP.AzureServiceBus.Helpers15DotNetCore.CAP.Diagnostics16DotNetCore.CAP.Internal17DotNetCore.CAP.Pulsar18DotNetCore.CAP.Filter19DotNetCore.CAP.SqlServer.Diagnostics20DotNetCore.CAP21DotNetCore.CAP.AmazonSQS22DotNetCore.CAP.AzureServiceBus23DotNetCore.CAP.Dashboard.NodeDiscovery24DotNetCore.CAP.InMemoryStorage25DotNetCore.CAP.Kafka26DotNetCore.CAP.MongoDB27DotNetCore.CAP.MySql28DotNetCore.CAP.NATS29DotNetCore.CAP.PostgreSql30DotNetCore.CAP.Processor31DotNetCore.CAP.RabbitMQ32DotNetCore.CAP.RedisStreams33DotNetCore.CAP.SqlServer34Microsoft.EntityFrameworkCore.Storage35MongoDB.Driver36DotNetCore.CAP.Dashboard.GatewayProxy37DotNetCore.CAP.Dashboard.K8s38Microsoft.Extensions.DependencyInjection39DotNetCore.CAP.Dashboard4012141211212114261310813274412122511127422741126151322742624232626252742626254363385377262625111313711111

At a glance — Code Health · 53% · Adequate · gated by X4 ·

The Good
D1 · .NET / C# Cyclomatic Complexity 8.6 D2 · .NET / C# Cognitive Complexity 7.6 D3 · .NET / C# God Classes 9.8 D4 · .NET / C# Code Duplication 9.3 D18 · .NET / C# Solution Shape 10.0 D39 · .NET / C# IL Efficiency 9.9 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 7.9 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 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0
The Bad
D17 · .NET / C# Explicit Debt 6.2 X1 · Repo Async correctness 5.5 X18 · Repo Disposal-pattern correctness 5.0 X2 · Repo Cancellation propagation 5.5 X20 · Repo Mistyped argument guard 6.8 X23 · Repo Unguarded diagnostic materialisation 6.5 X3 · Repo Exception handling 6.5 X5 · Repo Nullable reference types 5.2
The Ugly
X4 · Repo Structured logging 3.8

At a glance — Architecture · 86% · Strong ·

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 8.9 D35 · .NET / C# Change Coupling 9.8 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 9.8 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.8 AX8 · Repo Test isolation 10.0
The Bad
AX2 · Repo Stateful singletons 5.2

At a glance — Maturity · 77% · Strong ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 8.8 D21 · .NET / C# Naming Consistency 9.5 D24 · .NET / C# Comment Value 9.0 D34 · .NET / C# Knowledge Freshness 9.9 M1 · Repo Documentation (README) 7.4 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 9.8
The Bad
M2 · Repo Architecture documentation 5.0

At a glance — Readiness · 41% · Weak · gated by D12, D13, P3, P7 ·

The Good
D8 · .NET / C# Code Coverage 7.6 D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 9.5 D11 · .NET / C# Test Reliability 10.0 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 8.5 P2 · Repo Observability 8.5 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 P8 · Repo Schema migrations 10.0
The Ugly
D12 · .NET / C# Dependency Hygiene 3.9 D13 · .NET / C# REDACTED Scanning 0.0 P3 · Repo Security & performance tooling 0.0 P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 53% · Adequate · gated by D28, D29, D30, D36, C1 ·

The Good
D31 · .NET / C# IaC & Container Security 10.0 D43 · .NET / C# Malicious Dependencies 10.0 D44 · .NET / C# Platform End-of-Life 10.0 C2 · Repo Access Controls 10.0 C4 · Repo Data Retention 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
The Ugly
D28 · .NET / C# Secrets (history) 0.0 D29 · .NET / C# Static Analysis (SAST) 0.4 D30 · .NET / C# Dependency Vulnerabilities 0.0 D36 · .NET / C# Supply-chain Provenance & Signing 0.0 C1 · Repo Data Protection 3.0 S1 · Repo Web-Security Posture 4.5 X24 · Repo Document value interpolated into markup unescaped 4.3

At a glance — Accessibility · 70% · Adequate ·

The Good
AC2 · Repo Forms & labels 10.0 AC5 · Repo ARIA correctness 10.0 AC6 · Repo Visual & motion safety 10.0
The Bad
AC3 · Repo Page structure 5.6
The Ugly
AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 66% · Adequate ·

The Good
PF2 · Repo Allocation hygiene 8.6
The Bad
PF1 · Repo Benchmark discipline 6.0 PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection47High / Critical
A03:2025 — Software Supply Chain Failures31High / Critical
A07:2025 — Authentication Failures15High / Critical

Roadmap

Immediately resolve the three leaked secrets in configuration files and address the eight deprecated and seven outdated dependencies to restore code hygiene. Strengthen the build pipeline by integrating a SAST step to automatically block security regressions before they merge. Finally, implement resilience handlers for all outbound HTTP clients to prevent external service failures from taking down the application.

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

Do thisHelpsEffortDimension
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.+8.0 ptsLowREDACTED Scanning
Resolve the 8 Deprecated finding(s) in Dependency Hygiene — start with package.json (4), DotNetCore.CAP.MySql.Test.csproj, DotNetCore.CAP.Test.csproj.+7.5 ptsLowDependency Hygiene
Resolve the 7 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json.+7.3 ptsLowDependency Hygiene
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.+5.9 ptsMediumSecurity & performance tooling
Resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED, IConnectionFactory.Default.cs, TestLogger.cs.+2.2 ptsLowExplicit Debt
Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with CapCache.cs (3), KafkaConsumerClient.cs.+2.2 ptsLowExplicit Debt
Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.+3.6 ptsMediumOutbound HTTP resilience
Resolve the 28 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED (6), DotNetCore.CAP.Test.csproj (4), DotNetCore.CAP.csproj (4).+2.2 ptsMediumExplicit Debt

File quality

Per-file score 0–10 — a quality signature. Of 128 files carrying findings, judged against the Production bar: 9% slop · 39% mixed · 52% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED0.2SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.5SlopStatic Analysis (SAST): High: REDACTED
src/DotNetCore.CAP.Kafka/DotNetCore.CAP.Kafka.csproj1.6SlopExplicit Debt: NoWarnInCsproj
REDACTED1.8SlopDependency Vulnerabilities: High CVE: REDACTED
src/DotNetCore.CAP/DotNetCore.CAP.csproj2.5SlopExplicit Debt: NoWarnInCsproj
src/DotNetCore.CAP.RedisStreams/DotNetCore.CAP.RedisStreams.csproj2.5SlopExplicit Debt: NoWarnInCsproj
src/DotNetCore.CAP.AmazonSQS/DotNetCore.CAP.AmazonSQS.csproj2.5SlopExplicit Debt: NoWarnInCsproj
REDACTED3.1SlopStatic Analysis (SAST): High: REDACTED
src/DotNetCore.CAP.AzureServiceBus/DotNetCore.CAP.AzureServiceBus.csproj3.1SlopExplicit Debt: NoWarnInCsproj
test/DotNetCore.CAP.Test/DotNetCore.CAP.Test.csproj4.0MixedExplicit Debt: NoWarnInCsproj
REDACTED4.2MixedDependency Vulnerabilities: High CVE: REDACTED
samples/Sample.Kafka.PostgreSql/Sample.Kafka.PostgreSql.csproj4.3MixedExplicit Debt: NoWarnInCsproj
REDACTED4.3MixedStatic Analysis (SAST): High: REDACTED
src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs4.4MixedCognitive Complexity: AzureServiceBusConsumerClient.ConnectAsync (cognitive 24)
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs4.5MixedCognitive Complexity: InMemoryMonitoringApi.GetMessagesAsync (cognitive 16)
src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs4.8MixedCode Duplication: Duplicated block (23 lines × 3)
REDACTED5.4MixedSecrets (history): High secret: REDACTED

How the grades work

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

Critical — 90

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

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

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

Could not be resolved — 4

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 85 of 89 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 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 — 89 dimensions across the health lenses
D1D2D3D4D5D6D8D9D10D11D12D13D14D15D17D18D19D21D24D26D27D28D29D30D31D34D35D36D39D43D44AC2AC3AC5AC6AC7AX1AX10AX2AX3AX4AX5AX6AX8C1C2C4GD1IC1M1M2M3M4P1P2P3P4P6P7P8PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 486 of 577 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1687b-8947-774b-98f5-9df5d312230e.

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

Run transparency — what happened this run

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

  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (135 contributor(s) across 2235 commit(s) sampled, automation and bot accounts excluded). One of them holds 87% of the history; the other 134 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/DotNetCore.CAP.Dashboard/HtmlHelper.cs`, `src/DotNetCore.CAP.RedisStreams/ICapOptionsExtension.Redis.cs`, `src/DotNetCore.CAP.RedisStreams/IConnectionPool.LazyConnection.cs`, `src/DotNetCore.CAP.RedisStreams/IConsumerClient.Redis.cs`, `src/DotNetCore.CAP.RedisStreams/IConsumerClientFactory.Redis.cs`, … (+3 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (samples/Sample.RabbitMQ.MongoDB/docker-compose.yml). compose up failed (exit 18 — an image could not be pulled) — mongodb Pulling rabbitmq Pulling rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden mongodb Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: mongodb Pulling rabbitmq Pulling rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden mongodb Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 184 further occurrence(s) are not listed individually; the score already reflects all 224.
  • X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 9 further occurrence(s) are not listed individually; the score already reflects all 49.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • 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.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • 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 (4): D19, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity8.6 / 10Strong✓ 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 8.6 / 10 · rule-coverage 100% · ceiling Prevented

3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DiagnosticListener.OnNext at 44.

DiagnosticListener.OnNext (cyclomatic 44)src/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs:33
AmazonSQSConsumerClient.ConnectAsync (cyclomatic 18)src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs:161
AwaitableInfo.IsTypeAwaitable (cyclomatic 17)src/DotNetCore.CAP/Internal/ObjectMethodExecutor/AwaitableInfo.cs:41

What to do

  1. Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with DiagnosticListener.OnNext (cyclomatic 44), AmazonSQSConsumerClient.ConnectAsync (cyclomatic 18), AwaitableInfo.IsTypeAwaitable (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity7.6 / 10Strong✓ Tool-verified

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

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

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

10 method(s) exceeded the cognitive complexity threshold of 15; the worst was DiagnosticListener.OnNext at 67.

DiagnosticListener.OnNext (cognitive 67)src/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs:33
AmazonSQSConsumerClient.ConnectAsync (cognitive 49)src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs:161
SubscribeInvoker.InvokeAsync (cognitive 39)src/DotNetCore.CAP/Internal/ISubscribeInvoker.Default.cs:31
ConsumerServiceSelector.FindConsumersFromInterfaceTypes (cognitive 28)src/DotNetCore.CAP/Internal/IConsumerServiceSelector.Default.cs:70
AzureServiceBusConsumerClient.ConnectAsync (cognitive 24)src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs:192

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

What to do

  1. Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with DiagnosticListener.OnNext (cognitive 67), AmazonSQSConsumerClient.ConnectAsync (cognitive 49), SubscribeInvoker.InvokeAsync (cognitive 39). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 7.6 to about 8.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  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 Classes9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

1 over-large unit(s) detected — types, modules or files that carry too much.

MethodTooLong: DiagnosticListener.OnNextsrc/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs:33

What to do

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

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

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

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

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

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

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

Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:167
Duplicated block (10 lines × 2) · ×2src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:246
Duplicated block (20 lines × 3) · ×2REDACTED:362
Duplicated block (16 lines × 2) · ×2src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutor.cs:144
Duplicated block (14 lines × 2) · ×2src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:44

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

What to do

  1. Resolve the 2 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with IMonitoringApi.InMemory.cs, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with IMonitoringApi.PostgreSql.cs, K8sDiscoveryOptionsExtensions.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Duplicated block (20 lines × 3) finding(s) in Code Duplication — start with REDACTED, IDbConnection.Extensions.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

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

Off the main sequence: DotNetCore.CAP(net8.0)src/DotNetCore.CAP/DotNetCore.CAP.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with DotNetCore.CAP.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 70 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage7.6 / 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.6 / 10 · rule-coverage 100% · ceiling Verified

Line coverage 39.0% — 41 file(s) below 50% · 15 method(s) over the CRAP-30 risk line.

Low coverage: src/DotNetCore.CAP/Internal/ObjectMethodExecutor/AwaitableInfo.cs · ×41src/DotNetCore.CAP/Internal/ObjectMethodExecutor/AwaitableInfo.cs:1
CRAP 90: InMemoryMonitoringApi.GetMessagesAsync · ×2src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:57
No test project references DotNetCore.CAP.RedisStreamssrc/DotNetCore.CAP.RedisStreams/DotNetCore.CAP.RedisStreams.csproj
No test project references DotNetCore.CAP.SqlServerREDACTED
No test project references DotNetCore.CAP.MongoDBsrc/DotNetCore.CAP.MongoDB/DotNetCore.CAP.MongoDB.csproj

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

What to do

  1. Resolve the 41 Low coverage finding(s) in Code Coverage — start with CAP.Options.Extensions.cs (2), AwaitableInfo.cs, CoercedAwaitableInfo.cs. — One of this dimension's main actionable groups (41 warning-level).
  2. Resolve the 2 CRAP 90 finding(s) in Code Coverage — start with IMonitoringApi.InMemory.cs, IMonitoringApi.MySql.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 No test project references DotNetCore.CAP.RedisStreams finding(s) in Code Coverage — start with DotNetCore.CAP.RedisStreams.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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.5 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

0 skipped, 2 zero-assertion, 1 mock references across 65 tests.

No assertions: ChangePublishStateTest · ×2test/DotNetCore.CAP.MySql.Test/MySqlStorageConnectionTest.cs:62
Mock framework: NSubstitute

What to do

  1. Resolve the 2 No assertions finding(s) in Test Quality — start with MySqlStorageConnectionTest.cs (2). — One of this dimension's main actionable groups (2 warning-level).
  2. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

0 flaky across 2 measured tier(s). unit: measured (0 flaky); other: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene3.9 / 10Weak✓ Tool-verified

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

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

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

34 outdated, 0 vulnerable, 1 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 37 outdated of 43 package(s) across 1 lockfile(s).

Deprecated: xunit · ×8test/DotNetCore.CAP.MySql.Test/DotNetCore.CAP.MySql.Test.csproj:16
Outdated (npm): ansi-styles · ×7
Deprecated: popper.jsREDACTED:1703
Outdated: Microsoft.Extensions.Hosting.Abstractions · ×34
Outdated (npm): @babel/parser · ×30

What to do

  1. Resolve the 8 Deprecated finding(s) in Dependency Hygiene — start with package.json (4), DotNetCore.CAP.MySql.Test.csproj, DotNetCore.CAP.Test.csproj. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 7 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (7 recommendation-level).
  3. Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
  4. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

3 secret(s) detected.

REDACTED

What to do

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

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

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 275 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 41 direct `PackageReference`(s), and 209 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 Debt6.2 / 10Adequate✓ 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 6.2 / 10 · rule-coverage 100% · ceiling Prevented

43 deducted debt markers + 9 dead symbols across 19562 LoC in the .NET projects (1.9/KLoC) → score 6.2.

NoWarnInCsproj · ×28REDACTED:8
EmptyCatchBlock · ×4src/DotNetCore.CAP.Dashboard/CapCache.cs:79
WriteOnlyPrivateField · ×3REDACTED:14
Dead code: Exists · ×9src/DotNetCore.CAP.Dashboard/GatewayProxy/Requester/IHttpClientCache.cs:10
CommentedOutCode · ×5REDACTED:13

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

What to do

  1. Resolve the 28 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED (6), DotNetCore.CAP.Test.csproj (4), DotNetCore.CAP.csproj (4). — One of this dimension's main actionable groups (28 issue-level).
  2. Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with CapCache.cs (3), KafkaConsumerClient.cs. — One of this dimension's main actionable groups (4 issue-level).
  3. Resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED, IConnectionFactory.Default.cs, TestLogger.cs. — One of this dimension's main actionable groups (3 issue-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

39 projects, 566 source files, 22452 hand-written lines of code (19562 production / 2890 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 95 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 61 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: it states CAP as a .NET library providing distributed transactions and an event bus with the Outbox pattern, explains its reliability guarantee (local message table integrated with database), lists key features, and begins an architecture overview before clipping. The docs directory README is focused on that directory rather than the repository, so it does not fall under the root's scope. A dedicated Architecture/Docs markdown set of 69 files covers detailed design documentation, while XML-doc coverage (162/458) reflects the project's comprehensive API reference and usage. The repository's documentation is comprehensive and well-structured. The READMEs for each CAP tier (eventing, distributed transactions, monitoring) are complete with installation, usage examples, and contribution guidance. Architecture/Docs markdown files provide detailed design docs covering every CAP feature set, while XML-doc coverage reflects the high quality of API reference material across 72 packages. The repository's documentation is strong and well-organized. The README for eShopOnContainers gives a clear overview of the project (a .NET Core reference application powered by Microsoft based on a simplified microservices architecture with Docker containers) plus cross-platform support notes, an architecture description showing multiple autonomous microservices implementing different approaches within each service, and a dedicated CAP section explaining how to use CAP in the sample. The FAQ covers common CAP questions such as whether each application needs its own database, how to share a single database across applications, and whether CAP avoids using the database for event storage versus eventual consistency, with code examples. A comprehensive Storage chapter explains persistence before and after sending messages, the supported transaction-enabled databases (SQL Server, MySQL, PostgreSQL, MongoDB, in-memory), and initialization of published/ received-message storage, with an info note about production readiness.

Low XML-doc coverage: DotNetCore.CAP(net8.0) · ×26src/DotNetCore.CAP/DotNetCore.CAP.csproj
Documentation: no project overviewREADME.md

What to do

  1. Resolve the 26 Low XML-doc coverage finding(s) in Documentation Quality — start with DotNetCore.CAP.csproj, DotNetCore.CAP.Kafka.csproj, DotNetCore.CAP.RabbitMQ.csproj. — One of this dimension's main actionable groups (26 warning-level).
  2. Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-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

1 naming inconsistencies across 200 sampled symbols.

The test method `GetCallbackNameTest` duplicates the name of the method under test `GetCallbackName` by appending 'Test'. While common in some frameworks, the codebase generally uses descriptive test names (e.g., `EnqueueToPublish_ShouldInvokeSend_WhenParallelSendDisabled`) or distinct names. More importantly, the test name `GetCallbackNameTest` is structurally identical to the production method `GetCallbackName` plus a suffix, which can be confusing when reading stack traces or logs where the distinction is purely syntactic. However, this is a minor style issue. A more significant inconsistency is found in the naming of the helper/fixture vs the concept it represents.

✓ On the Gold path — maintain.

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

D24 · Comment ValueExemplary◐ Sampled · advisory

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

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

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

59 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

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

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

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

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

0 of 31 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability8.9 / 10Strong✓ Tool-verified

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

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

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

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

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

What to do

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

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

47 finding(s): 0 critical, 16 high, 31 medium, 0 low. 7 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 9 file(s) — `samples/Sample.Kafka.PostgreSql/Controllers/ValuesController.cs` (lines 10–15, lines 89–90), `src/DotNetCore.CAP.Dashboard/HtmlHelper.cs` (line 22, line 50), `src/DotNetCore.CAP.RedisStreams/ICapOptionsExtension.Redis.cs` (line 17), `src/DotNetCore.CAP.RedisStreams/IConnectionPool.LazyConnection.cs` (lines 12–13, lines 14–15, line 62), `src/DotNetCore.CAP.RedisStreams/IConsumerClient.Redis.cs` (lines 17–20, line 21, line 22), … (+4 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 8 of those file(s) — `samples/Sample.Kafka.PostgreSql/Controllers/ValuesController.cs`, `src/DotNetCore.CAP.RedisStreams/ICapOptionsExtension.Redis.cs`, `src/DotNetCore.CAP.RedisStreams/IConnectionPool.LazyConnection.cs`, `src/DotNetCore.CAP.RedisStreams/IConsumerClient.Redis.cs`, `src/DotNetCore.CAP.RedisStreams/IConsumerClientFactory.Redis.cs`, … (+3 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 1 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/DotNetCore.CAP.RedisStreams/TransportMessage.Redis.Exceptions.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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

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

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

25 finding(s): 1 critical, 16 high, 5 medium, 3 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

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

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

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

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

1 of 92 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/DotNetCore.CAP.AzureServiceBus/ServiceBusProcessorFacade.cs. Counted over 92 of the 236 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge
Orphaned filesrc/DotNetCore.CAP.AzureServiceBus/ServiceBusProcessorFacade.cs:1

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.8 / 10Adequategated by 2 critical findings✓ 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.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: IDataStorage.PostgreSql.cs↔IStorageInitializer.PostgreSql.cs 75%; REDACTED↔REDACTED 73%; AzureServiceBusConsumerClient.cs↔ITransport.AzureServiceBus.cs 62%

Boundary-crossing change coupling: KafkaConsumerClient.cs ↔ RabbitMQConsumerClientFactory.cs · ×2src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs:1
Change coupling: IDataStorage.PostgreSql.cs ↔ IStorageInitializer.PostgreSql.cs · ×4src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs:1

What to do

  1. Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with KafkaConsumerClient.cs, IStorageInitializer.PostgreSql.cs. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 4 Change coupling finding(s) in Change Coupling — start with IDataStorage.PostgreSql.cs, REDACTED, AzureServiceBusConsumerClient.cs. — One of this dimension's main actionable groups (4 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 recommendation-level).

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

D39 · IL Efficiency9.9 / 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 9.9 / 10 · rule-coverage 100% · ceiling Verified

5 of 1231 first-party methods have an oversized IL body.

IL efficiency: 5 authored method(s) exceed the IL budgetsrc/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs:35

✓ On the Gold path — maintain.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC3 · Page structure5.6 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it. — src/DotNetCore.CAP.Dashboard/wwwroot/index.html:2

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 9 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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.8 / 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 singletons5.2 / 10Adequate✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `ConsumerRegister` is a singleton (one shared instance) but mutates instance state outside any lock (_cts, _selector, _dispatcher, _serializer, _storage, _consumerClientFactory; e.g. `_cts` at line 59). — src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:21
  • `MessageNeedToRetryProcessor` is a singleton (one shared instance) but mutates instance state outside any lock (_failedRetryConsumeTask; e.g. `_failedRetryConsumeTask` at line 63). — src/DotNetCore.CAP/Processor/IProcessor.NeedRetry.cs:17
  • `Dispatcher` is a singleton (one shared instance) but mutates instance state outside any lock (_tasksCts, _disposed; e.g. `_tasksCts` at line 60). — src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:19
  • `Bootstrapper` is a singleton (one shared instance) but mutates instance state outside any lock (_cts, _processors, _disposed; e.g. `_cts` at line 46). — src/DotNetCore.CAP/Internal/IBootstrapper.Default.cs:18
  • `ConnectionPool` is a singleton (one shared instance) but mutates instance state outside any lock (_maxSize; e.g. `_maxSize` at line 73). — src/DotNetCore.CAP.Kafka/IConnectionPool.Default.cs:14
  • `ConnectionChannelPool` is a singleton (one shared instance) but mutates instance state outside any lock (_maxSize; e.g. `_maxSize` at line 88). — src/DotNetCore.CAP.RabbitMQ/IConnectionChannelPool.Default.cs:16
  • `MySqlStorageInitializer` is a singleton (one shared instance) but mutates instance state outside any lock (_serverVersion; e.g. `_serverVersion` at line 56). — src/DotNetCore.CAP.MySql/IStorageInitializer.MySql.cs:14
  • `GatewayProxyAgent` is a singleton (one shared instance) but mutates instance state outside any lock (DownstreamRequest; e.g. `DownstreamRequest` at line 95). — src/DotNetCore.CAP.Dashboard/GatewayProxy/GatewayProxyAgent.cs:20
  • `RedisStreamManager` is a singleton (one shared instance) but mutates instance state outside any lock (_redis; e.g. `_redis` at line 138). — src/DotNetCore.CAP.RedisStreams/IRedisStream.Manager.Default.cs:16
  • `RedisConnectionPool` is a singleton (one shared instance) but mutates instance state outside any lock (_poolAlreadyConfigured; e.g. `_poolAlreadyConfigured` at line 51). — src/DotNetCore.CAP.RedisStreams/IConnectionPool.Default.cs:15
  • `ConnectionFactory` is a singleton (one shared instance) but mutates instance state outside any lock (_client; e.g. `_client` at line 42). — src/DotNetCore.CAP.Pulsar/IConnectionFactory.Default.cs:14

What to do

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

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

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

  • The namespaces DotNetCore.CAP ↔ DotNetCore.CAP.Internal ↔ DotNetCore.CAP.Monitoring ↔ DotNetCore.CAP.Persistence ↔ DotNetCore.CAP.Pulsar ↔ DotNetCore.CAP.Serialization ↔ DotNetCore.CAP.SqlServer.Diagnostics ↔ DotNetCore.CAP.Transport depend on each other. The lightest dependency in the cycle is DotNetCore.CAP → DotNetCore.CAP.Internal (DotNetCore.CAP.CapSubscribeAttribute → DotNetCore.CAP.Internal.TopicAttribute, 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/DotNetCore.CAP/CAP.Attribute.cs:7

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

  • `IDataStorage` declares 16 members: `AcquireLockAsync`, `ReleaseLockAsync`, `RenewLockAsync`, `ChangePublishStateToDelayedAsync`, `ChangePublishStateAsync`, `ChangeReceiveStateAsync`, `StoreMessageAsync`, `StoreReceivedExceptionMessageAsync`, `StoreReceivedMessageAsync`, `DeleteExpiresAsync`, `GetPublishedMessagesOfNeedRetry`, `ScheduleMessagesOfDelayedAsync`, `GetReceivedMessagesOfNeedRetry`, `DeleteReceivedMessageAsync`, `DeletePublishedMessageAsync`, `GetMonitoringApi`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DotNetCore.CAP/Persistence/IDataStorage.cs:14

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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.

C1 · Data Protection3.0 / 10Weak✓ Tool-verified

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

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

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

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

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

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

C4 · Data Retention10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×4) — src/DotNetCore.CAP.Dashboard/CircularBuffer.cs:153, src/DotNetCore.CAP.Dashboard/CircularBuffer.cs:173, src/DotNetCore.CAP.Dashboard/NodeDiscovery/INodeDiscoveryProvider.cs:17, …

What to do

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

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `RegisterNode` is a shipped member whose body only throws — and it is REACHED: src/DotNetCore.CAP.Dashboard/NodeDiscovery/IProcessingServer.Consul.cs:21 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/DotNetCore.CAP.Dashboard/NodeDiscovery/INodeDiscoveryProvider.cs:17
  • `ListServices` is a shipped member whose body only throws — and it is REACHED: REDACTED:408 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/DotNetCore.CAP.Dashboard/NodeDiscovery/INodeDiscoveryProvider.cs:27
  • `Contains` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/DotNetCore.CAP.Dashboard/CircularBuffer.cs:153
  • `Remove` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/DotNetCore.CAP.Dashboard/CircularBuffer.cs:173
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×4) — src/DotNetCore.CAP.Dashboard/CAP.MetricsEventListener.cs:78, src/DotNetCore.CAP.Dashboard/CAP.MetricsEventListener.cs:79, src/DotNetCore.CAP.Dashboard/CAP.MetricsEventListener.cs:80, …

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)7.4 / 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 a README to the 30 of 31 project(s) that lack one — worth up to 1.9 pts.
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

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

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

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

M4 · Documentation accuracy9.8 / 10Exemplary◐ Sampled · advisory

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

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

  • docs/readme.md changes into `CAP/docs`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/readme.md:16
  • docs/content/user-guide/en/cap/idempotence.md links to `The`, but `docs/content/user-guide/en/cap/The` 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. — docs/content/user-guide/en/cap/idempotence.md:7
  • docs/content/user-guide/en/cap/transactions.md links to `This`, but `docs/content/user-guide/en/cap/This` 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. — docs/content/user-guide/en/cap/transactions.md:17

What to do

  • Reconcile the README with reality: docs/readme.md changes into `CAP/docs`, but no such folder exists; docs/content/user-guide/en/cap/idempotence.md links to `The`, but `docs/content/user-guide/en/cap/The` does not exist; docs/content/user-guide/en/cap/transactions.md links to `This`, but `docs/content/user-guide/en/cap/This` does not exist.
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified

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

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

What to do

  • Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability8.5 / 10Strong✓ Tool-verified

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

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

  • Only 21/25 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 25, 9 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
  • `samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs` reports through `Console.Write…` at line 161 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs:161

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
  • Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling0.0 / 10Critical✓ 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.

  • `NoWarn` silences NU1903 — NuGet's vulnerability-audit warnings for high advisories. Suppressed advisories are still shipped; they are only invisible in the build log. Remove these codes from NoWarn and address or explicitly accept each advisory instead. (×2) — REDACTED:8, REDACTED:12
  • 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 2952 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.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `new HttpClient(CreateHttpMessageHandler(httpclientHandler))` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/DotNetCore.CAP.Dashboard/GatewayProxy/Requester/HttpClientBuilder.cs:20
  • `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — REDACTED:418

What to do

  • Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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

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

PF1 · Benchmark discipline6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

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

What to do

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

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

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

What to do

  • Raise allocation-aware density on the hot paths — currently 107 use(s) across 20,481 production line(s) (~5.2/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • 21 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×19) — src/DotNetCore.CAP/ICapTransaction.Base.cs:108, src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:94, src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:99, …
  • `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:260, REDACTED:75

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Web-Security Posture4.5 / 10Weak✓ Tool-verified

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

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

  • `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — REDACTED:57
  • `ValidateAudience`, `ValidateIssuer` are all set to `false`, which means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. — REDACTED:32
  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×8) — samples/Sample.AzureServiceBus.InMemory/Program.cs:8, samples/Sample.Dashboard.Auth/Program.cs:14, REDACTED:9, …
  • No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.) — src/DotNetCore.CAP.Dashboard/GatewayProxy/GatewayProxyAgent.cs:112

What to do

  • Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
  • Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
  • Set secure cookie flags — CookieSecurePolicy.Always, HttpOnly, and SameSite (Strict/Lax) on auth/session cookies. Skip only if the app sets no cookies.
X1 · Async correctness5.5 / 10Adequate✓ Tool-verified

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

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

  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×20) — src/DotNetCore.CAP/ICapTransaction.Base.cs:108, src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:94, src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:99, …
  • `WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`). (×5) — src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:223, src/DotNetCore.CAP.RabbitMQ/RabbitMQConsumerClient.cs:87, src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs:121, …
  • `SemaphoreSlim.Wait` parks the thread while it queues for the semaphore. `await semaphore.WaitAsync(…)` yields the thread instead. (×2) — src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs:132, src/DotNetCore.CAP.Pulsar/PulsarConsumerClient.cs:65
  • This blocks on a Task **while holding a `lock`**, which is worse than an ordinary sync-over-async in two ways. `await` is illegal inside a `lock` body, so the usual fix — make the caller `async` and await it — cannot be applied where this block stands. And the thread parks while still holding the lock, so it occupies the critical section doing no work: every other caller serialises behind an operation that is only waiting, and if the awaited task itself needs a thread the pool has run out of, they wait forever. Do the async work OUTSIDE the critical section: take the lock only to read the shared state, release it, await the call, then re-take the lock to publish the result — re-checking on re-entry whether another caller won the race and, if so, discarding your result rather than overwriting theirs. Where the critical section genuinely has to span the async call, `lock` is the wrong primitive: use an async-aware one (`SemaphoreSlim` with `await WaitAsync()`) so waiters yield their thread instead of parking it. — src/DotNetCore.CAP.RabbitMQ/IConnectionChannelPool.Default.cs:81
  • `AzureServiceBusTransport.GetSenderForProducer` is a synchronous helper that blocks (`SemaphoreSlim.Wait`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll). — src/DotNetCore.CAP.AzureServiceBus/ITransport.AzureServiceBus.cs:62
  • This acquires a `SemaphoreSlim` with the BLOCKING `Wait()` inside a method that is already `async`. The thread does not yield while it queues for the semaphore: it parks a pool thread doing no work, and under contention the pool must grow (or the holders must finish) before any waiter can proceed — which is how a bounded-concurrency gate turns into a throughput collapse under exactly the load it exists to bound. `SemaphoreSlim` ships an asynchronous acquire for this: `await semaphore.WaitAsync()` releases the thread while it waits and is legal here because the enclosing method is already `async`, so this is a one-word change with no signature to break. Where the acquire must be bounded, `await semaphore.WaitAsync(timeout)`/`WaitAsync(cancellationToken)` keep that property; and whichever you use, release it in a `finally` so a throw inside the critical section cannot leak a permit. — src/DotNetCore.CAP.RedisStreams/IConsumerClient.Redis.cs:102
  • Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — src/DotNetCore.CAP.Pulsar/IConnectionFactory.Default.cs:71

What to do

  • Sync-over-async (deadlock risk)
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.

  • `KafkaConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 25), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 157) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs:25
  • `RabbitMqConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 18), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 102) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/DotNetCore.CAP.RabbitMQ/RabbitMQConsumerClient.cs:18
  • `_transaction` is never created by `CapEFDbTransaction` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 29). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/DotNetCore.CAP.SqlServer/IDbContextTransaction.CAP.cs:29
  • `_transaction` is never created by `CapEFDbTransaction` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 54). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. (×2) — src/DotNetCore.CAP.SqlServer/IDbContextTransaction.CAP.cs:54, src/DotNetCore.CAP.PostgreSql/IDbContextTransaction.CAP.cs:54
  • `_transaction` is never created by `CapEFDbTransaction` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 30). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/DotNetCore.CAP.MySql/IDbContextTransaction.CAP.cs:30
  • `_transaction` is never created by `CapEFDbTransaction` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 27). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/DotNetCore.CAP.PostgreSql/IDbContextTransaction.CAP.cs:27
  • `_transaction` is never created by `CapMongoDbClientSessionHandle` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 27). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/DotNetCore.CAP.MongoDB/IClientSessionHandle.CAP.cs:27
  • `AzureServiceBusConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_connectionLock` itself (line 22), which makes that instance its own. But `_connectionLock` is named in none of the methods the disposal search covered: `DisposeAsync` (line 145) — 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/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs:22
  • `AzureServiceBusConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 27), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 145) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs:27
  • `httpClient` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 418). Every use of it in `PingServices` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var httpClient = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:418
  • `cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 15). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cts = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:15
  • `AmazonSQSConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 26), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 153) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs:26
  • `RedisConnectionPool` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_poolLock` itself (line 20), which makes that instance its own. But `_poolLock` is named in none of the methods the disposal search covered: `Dispose` (line 41), `Dispose` (line 88), `Dispose` (line 41), `Dispose` (line 88) — 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` (`_poolLock?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/DotNetCore.CAP.RedisStreams/IConnectionPool.Default.cs:20
  • `RedisConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 24), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 72) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/DotNetCore.CAP.RedisStreams/IConsumerClient.Redis.cs:24
  • `PulsarConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 22), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 112) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/DotNetCore.CAP.Pulsar/PulsarConsumerClient.cs:22
  • `client` is a `Kubernetes`, which implements `IDisposable`, and it is created here (line 28). Every use of it in `GetNode` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:28
  • `client` is a `Kubernetes`, which implements `IDisposable`, and it is created here (line 76). Every use of it in `GetNamespaces` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:76
  • `client` is a `Kubernetes`, which implements `IDisposable`, and it is created here (line 95). Every use of it in `ListServices` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:95

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

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

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

  • Only 71/294 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×18) — src/DotNetCore.CAP/ICapTransaction.Base.cs:116, src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:73, src/DotNetCore.CAP/Internal/IMessageSender.Default.cs:44, …
  • 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. (×17) — src/DotNetCore.CAP/Internal/IBootstrapper.Default.cs:84, src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:110, src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:114, …
  • No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken. (×3) — src/DotNetCore.CAP/Processor/IProcessor.Delayed.cs:28, src/DotNetCore.CAP/Processor/IProcessor.InfiniteRetry.cs:23, src/DotNetCore.CAP/Processor/IProcessor.TransportCheck.cs:24
  • Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. — src/DotNetCore.CAP/Processor/IProcessor.Delayed.cs:43

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard6.8 / 10Adequate✓ Tool-verified

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

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

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

What to do

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

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

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

  • `LogDebug` at line 27 is called with an argument built by `JsonConvert.SerializeObject(_options, Formatting.Indented)` (line 27), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/DotNetCore.CAP.Pulsar/IConnectionFactory.Default.cs:27

What to do

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

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.

  • `htmlBuilder.ToString()` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:75

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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 handling6.5 / 10Adequate✓ Tool-verified

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

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

  • `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/DotNetCore.CAP/CAP.Builder.cs:46
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs:75, src/DotNetCore.CAP.Dashboard/CapCache.cs:79, src/DotNetCore.CAP.Dashboard/CapCache.cs:248, …
  • `catch (Exception) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/DotNetCore.CAP.MongoDB/IDataStorage.MongoDB.cs:373

What to do

  • Swallowed exception (caught, then discarded)
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 logging3.8 / 10Weak✓ Tool-verified

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

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

  • Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×40) — src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:127, src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:155, src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:159, …

What to do

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

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

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

  • This method contradicts itself about `possibleFSharpAsyncGenericType`: line 76 writes `possibleFSharpAsyncGenericType?.FullName`, which says `possibleFSharpAsyncGenericType` can be null, but line 85 then dereferences it directly as `possibleFSharpAsyncGenericType.Assembly` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `possibleFSharpAsyncGenericType` truly cannot be null here, the `?.` is misleading. Settle it one way — test `possibleFSharpAsyncGenericType` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutorFSharpSupport.cs:85
  • 17/26 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
  • ~3.5 `!` suppressions per 1k syntax nodes — 266 suppression(s) across the 75823 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

  • Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

WCAG coverage — what static analysis assessed

Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 45 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.1, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

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 Health53%Adequate — gated by X4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture86%StrongStrongest area.
Maturity77%StrongSolid.
Readiness41%Weak — gated by D12, D13, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security53%Adequate — gated by D28, D29, D30, D36, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility70%AdequateAcceptable, with room to improve.
Performance66%AdequateAcceptable, with room to improve.
Unscored — 3 check(s) recorded observations but carry no score

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

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 25 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 image/media element found in the parsed markup — AC1 not applicable here.
  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — mongodb Pulling rabbitmq Pulling rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden mongodb Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: mongodb Pulling rabbitmq Pulling rabbitmq Error Get "https://registry-1.docker.io/v2/": Forbidden mongodb Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — small single-context codebase (19,562 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — 8 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.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 2 value object(s); a Domain/Aggregates/ValueObjects layer
  • ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 4 event handler(s); a message-bus package
  • ED5 Idempotency — 4 mutating command handler(s)/consumer(s) detected and 4 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • 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.
  • P9 Domain vs controller coverage — coverage data present for 89 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 90 finding(s)
D17 · Explicit Debt · NoWarnInCsproj · ×28
  • NoWarnInCsproj REDACTED:8 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj REDACTED:12 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/DotNetCore.CAP.Test/DotNetCore.CAP.Test.csproj:9 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP/DotNetCore.CAP.csproj:10 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP.RedisStreams/DotNetCore.CAP.RedisStreams.csproj:12 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP.AmazonSQS/DotNetCore.CAP.AmazonSQS.csproj:11 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj REDACTED:8 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj REDACTED:12 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/DotNetCore.CAP.Test/DotNetCore.CAP.Test.csproj:9 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP/DotNetCore.CAP.csproj:10 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP.RedisStreams/DotNetCore.CAP.RedisStreams.csproj:12 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP.AmazonSQS/DotNetCore.CAP.AmazonSQS.csproj:11 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj — known-vulnerability alert suppressed REDACTED:8 — NU1903 — this is not a style rule being switched off: it is the dependency audit reporting that a package this project references has a KNOWN, already-published security vulnerability, and the entry deletes that report for the whole project — for this package and for every dependency the project takes from here on, including ones added long after whoever wrote the line has moved on. Nothing in the build will raise it again, so the next reader has no way to learn it was ever accepted. Upgrade the package to a version carrying the fix, or replace it, and drop the code from the list. Where the fix genuinely does not exist yet, keep the report and stop it FAILING the build — demote it to a warning without silencing it — and write down which advisory is being accepted and until when, so it is the acceptance that expires rather than the alert.
  • NoWarnInCsproj — known-vulnerability alert suppressed REDACTED:12 — NU1903 — this is not a style rule being switched off: it is the dependency audit reporting that a package this project references has a KNOWN, already-published security vulnerability, and the entry deletes that report for the whole project — for this package and for every dependency the project takes from here on, including ones added long after whoever wrote the line has moved on. Nothing in the build will raise it again, so the next reader has no way to learn it was ever accepted. Upgrade the package to a version carrying the fix, or replace it, and drop the code from the list. Where the fix genuinely does not exist yet, keep the report and stop it FAILING the build — demote it to a warning without silencing it — and write down which advisory is being accepted and until when, so it is the acceptance that expires rather than the alert.
  • NoWarnInCsproj test/DotNetCore.CAP.Test/DotNetCore.CAP.Test.csproj:9 — CS0067 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj REDACTED:7 — CS0067 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj test/DotNetCore.CAP.Test/DotNetCore.CAP.Test.csproj:9 — CA1822 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP/DotNetCore.CAP.csproj:10 — 1705 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP.RedisStreams/DotNetCore.CAP.RedisStreams.csproj:12 — 1705 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP.AmazonSQS/DotNetCore.CAP.AmazonSQS.csproj:11 — 1705 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP/DotNetCore.CAP.csproj:10 — CS1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
  • NoWarnInCsproj src/DotNetCore.CAP.RedisStreams/DotNetCore.CAP.RedisStreams.csproj:12 — CS1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP.Kafka/DotNetCore.CAP.Kafka.csproj:11 — CS1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP.AzureServiceBus/DotNetCore.CAP.AzureServiceBus.csproj:11 — CS1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj src/DotNetCore.CAP.AmazonSQS/DotNetCore.CAP.AmazonSQS.csproj:11 — CS1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
  • + 3 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×16
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×4
  • EmptyCatchBlock src/DotNetCore.CAP.Dashboard/CapCache.cs:79 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DotNetCore.CAP.Dashboard/CapCache.cs:248 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DotNetCore.CAP.Dashboard/CapCache.cs:280 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs:75 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · REDACTED Scanning · Leaked secret · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · WriteOnlyPrivateField · ×3
  • WriteOnlyPrivateField REDACTED:14 — private IOptions<CapOptions> _options — 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/DotNetCore.CAP.Pulsar/IConnectionFactory.Default.cs:16 — private ILogger<ConnectionFactory> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField test/DotNetCore.CAP.Test/Helpers/TestLogger.cs:36 — private object _state — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×2
  • Boundary-crossing change coupling: KafkaConsumerClient.cs ↔ RabbitMQConsumerClientFactory.cs src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs:1 — `src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs` (context DotNetCore.CAP.Kafka) and `src/DotNetCore.CAP.RabbitMQ/RabbitMQConsumerClientFactory.cs` (context DotNetCore.CAP.RabbitMQ) sit in DIFFERENT parts of the tree yet change together 58% of the time (7 of the 12 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `19f64079` Add GroupConcurrent option to support subscriber concurrent execution…; `2a620b54` Change the SnowflakeId from static singleton to dependency injection …; `36d9c7fd` Replace client event to delegate callback to support async. — run `git show` on any of them.
  • Boundary-crossing change coupling: IStorageInitializer.PostgreSql.cs ↔ REDACTED src/DotNetCore.CAP.PostgreSql/IStorageInitializer.PostgreSql.cs:1 — `src/DotNetCore.CAP.PostgreSql/IStorageInitializer.PostgreSql.cs` (context DotNetCore.CAP.PostgreSql) and `REDACTED` (context DotNetCore.CAP.SqlServer) sit in DIFFERENT parts of the tree yet change together 58% of the time (7 of the 12 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `1cafc93c` Add default indexes to the database tables during creation and adjust…; `98e0884d` Rename option IsUseStorageLock to UseStorageLock; `f4fe7f80` Add docs for IsUseStorageLock option. — run `git show` on any of them.
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException src/DotNetCore.CAP.Dashboard/NodeDiscovery/INodeDiscoveryProvider.cs:17 — `RegisterNode` is a shipped member whose body only throws — and it is REACHED: src/DotNetCore.CAP.Dashboard/NodeDiscovery/IProcessingServer.Consul.cs:21 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException src/DotNetCore.CAP.Dashboard/NodeDiscovery/INodeDiscoveryProvider.cs:27 — `ListServices` is a shipped member whose body only throws — and it is REACHED: REDACTED:408 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
P3 · Security & performance tooling · NuGet vulnerability audit suppressed via NoWarn · ×2
  • NuGet vulnerability audit suppressed via NoWarn REDACTED:8 — `NoWarn` silences NU1903 — NuGet's vulnerability-audit warnings for high advisories. Suppressed advisories are still shipped; they are only invisible in the build log. Remove these codes from NoWarn and address or explicitly accept each advisory instead.
  • NuGet vulnerability audit suppressed via NoWarn REDACTED:12 — `NoWarn` silences NU1903 — NuGet's vulnerability-audit warnings for high advisories. Suppressed advisories are still shipped; they are only invisible in the build log. Remove these codes from NoWarn and address or explicitly accept each advisory instead.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/DotNetCore.CAP/CAP.Attribute.cs:7 — The namespaces DotNetCore.CAP ↔ DotNetCore.CAP.Internal ↔ DotNetCore.CAP.Monitoring ↔ DotNetCore.CAP.Persistence ↔ DotNetCore.CAP.Pulsar ↔ DotNetCore.CAP.Serialization ↔ DotNetCore.CAP.SqlServer.Diagnostics ↔ DotNetCore.CAP.Transport depend on each other. The lightest dependency in the cycle is DotNetCore.CAP → DotNetCore.CAP.Internal (DotNetCore.CAP.CapSubscribeAttribute → DotNetCore.CAP.Internal.TopicAttribute, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×1
  • REDACTED
X1 · Async correctness · Blocking wait while holding a `lock` · ×1
  • Blocking wait while holding a `lock` src/DotNetCore.CAP.RabbitMQ/IConnectionChannelPool.Default.cs:81 — This blocks on a Task **while holding a `lock`**, which is worse than an ordinary sync-over-async in two ways. `await` is illegal inside a `lock` body, so the usual fix — make the caller `async` and await it — cannot be applied where this block stands. And the thread parks while still holding the lock, so it occupies the critical section doing no work: every other caller serialises behind an operation that is only waiting, and if the awaited task itself needs a thread the pool has run out of, they wait forever. Do the async work OUTSIDE the critical section: take the lock only to read the shared state, release it, await the call, then re-take the lock to publish the result — re-checking on re-entry whether another caller won the race and, if so, discarding your result rather than overwriting theirs. Where the critical section genuinely has to span the async call, `lock` is the wrong primitive: use an async-aware one (`SemaphoreSlim` with `await WaitAsync()`) so waiters yield their thread instead of parking it.
Serious — 330 finding(s)
D8 · Code Coverage · Low coverage · ×41
  • Low coverage: src/DotNetCore.CAP/Internal/ObjectMethodExecutor/AwaitableInfo.cs src/DotNetCore.CAP/Internal/ObjectMethodExecutor/AwaitableInfo.cs:1 — 14.3% line coverage (10/70).
  • Low coverage: src/DotNetCore.CAP/Internal/ObjectMethodExecutor/CoercedAwaitableInfo.cs src/DotNetCore.CAP/Internal/ObjectMethodExecutor/CoercedAwaitableInfo.cs:1 — 27.6% line coverage (8/29).
  • Low coverage: src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutor.cs src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutor.cs:1 — 32.3% line coverage (54/167).
  • Low coverage: src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutorAwaitable.cs src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutorAwaitable.cs:1 — 0.0% line coverage (0/31).
  • Low coverage: src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutorFSharpSupport.cs src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutorFSharpSupport.cs:1 — 21.1% line coverage (15/71).
  • Low coverage: src/DotNetCore.CAP/CAP.Attribute.cs src/DotNetCore.CAP/CAP.Attribute.cs:1 — 15.0% line coverage (3/20).
  • Low coverage: src/DotNetCore.CAP/ICapTransaction.Base.cs src/DotNetCore.CAP/ICapTransaction.Base.cs:1 — 0.0% line coverage (0/33).
  • Low coverage: src/DotNetCore.CAP/OperateResult.cs src/DotNetCore.CAP/OperateResult.cs:1 — 39.1% line coverage (9/23).
  • Low coverage: src/DotNetCore.CAP/Transport/BrokerAddress.cs src/DotNetCore.CAP/Transport/BrokerAddress.cs:1 — 28.6% line coverage (6/21).
  • Low coverage: src/DotNetCore.CAP/Internal/Filter/ExceptionContext.cs src/DotNetCore.CAP/Internal/Filter/ExceptionContext.cs:1 — 0.0% line coverage (0/7).
  • Low coverage: src/DotNetCore.CAP/Internal/Filter/ExecutedContext.cs src/DotNetCore.CAP/Internal/Filter/ExecutedContext.cs:1 — 0.0% line coverage (0/5).
  • Low coverage: src/DotNetCore.CAP/Internal/Filter/ExecutingContext.cs src/DotNetCore.CAP/Internal/Filter/ExecutingContext.cs:1 — 0.0% line coverage (0/5).
  • Low coverage: src/DotNetCore.CAP/Internal/Filter/SubscribeFilter.cs src/DotNetCore.CAP/Internal/Filter/SubscribeFilter.cs:1 — 0.0% line coverage (0/9).
  • Low coverage: src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:1 — 43.3% line coverage (65/150).
  • Low coverage: src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:1 — 47.1% line coverage (140/297).
  • Low coverage: src/DotNetCore.CAP/Internal/IConsumerServiceSelector.Assembly.cs src/DotNetCore.CAP/Internal/IConsumerServiceSelector.Assembly.cs:1 — 0.0% line coverage (0/17).
  • Low coverage: src/DotNetCore.CAP/Internal/IMessageSender.Default.cs src/DotNetCore.CAP/Internal/IMessageSender.Default.cs:1 — 35.1% line coverage (40/114).
  • Low coverage: src/DotNetCore.CAP/Internal/ISubscribeExector.Default.cs src/DotNetCore.CAP/Internal/ISubscribeExector.Default.cs:1 — 35.3% line coverage (60/170).
  • Low coverage: src/DotNetCore.CAP/Internal/LoggerExtensions.cs src/DotNetCore.CAP/Internal/LoggerExtensions.cs:1 — 31.4% line coverage (16/51).
  • Low coverage: src/DotNetCore.CAP/Internal/PublisherSentFailedException.cs src/DotNetCore.CAP/Internal/PublisherSentFailedException.cs:1 — 0.0% line coverage (0/6).
  • Low coverage: src/DotNetCore.CAP/Internal/SubscriberExecutionFailedException.cs src/DotNetCore.CAP/Internal/SubscriberExecutionFailedException.cs:1 — 0.0% line coverage (0/6).
  • Low coverage: src/DotNetCore.CAP/Diagnostics/EventCounterSource.Cap.cs src/DotNetCore.CAP/Diagnostics/EventCounterSource.Cap.cs:1 — 28.0% line coverage (14/50).
  • Low coverage: src/DotNetCore.CAP.AzureServiceBus/CAP.Options.Extensions.cs src/DotNetCore.CAP.AzureServiceBus/CAP.Options.Extensions.cs:1 — 0.0% line coverage (0/9).
  • Low coverage: src/DotNetCore.CAP.AzureServiceBus/CAP.AzureServiceBusOptionsExtension.cs src/DotNetCore.CAP.AzureServiceBus/CAP.AzureServiceBusOptionsExtension.cs:1 — 0.0% line coverage (0/10).
  • Low coverage: src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs:1 — 0.0% line coverage (0/203).
  • + 16 more in this group — see findings.md.
D19 · Documentation Quality · Low XML-doc coverage · ×26
  • Low XML-doc coverage: DotNetCore.CAP(net8.0) src/DotNetCore.CAP/DotNetCore.CAP.csproj — DotNetCore.CAP(net8.0): 35 % XML-doc coverage (162/458).
  • Low XML-doc coverage: DotNetCore.CAP.Kafka src/DotNetCore.CAP.Kafka/DotNetCore.CAP.Kafka.csproj — DotNetCore.CAP.Kafka: 23 % XML-doc coverage (10/43).
  • Low XML-doc coverage: DotNetCore.CAP.RabbitMQ src/DotNetCore.CAP.RabbitMQ/DotNetCore.CAP.RabbitMQ.csproj — DotNetCore.CAP.RabbitMQ: 34 % XML-doc coverage (23/67).
  • Low XML-doc coverage: DotNetCore.CAP.SqlServer(net8.0) REDACTED — DotNetCore.CAP.SqlServer(net8.0): 10 % XML-doc coverage (10/96).
  • Low XML-doc coverage: DotNetCore.CAP.MySql(net8.0) src/DotNetCore.CAP.MySql/DotNetCore.CAP.MySql.csproj — DotNetCore.CAP.MySql(net8.0): 12 % XML-doc coverage (10/82).
  • Low XML-doc coverage: Sample.RabbitMQ.MySql samples/Sample.RabbitMQ.MySql/Sample.RabbitMQ.MySql.csproj — Sample.RabbitMQ.MySql: 0 % XML-doc coverage (0/11).
  • Low XML-doc coverage: DotNetCore.CAP.PostgreSql(net8.0) src/DotNetCore.CAP.PostgreSql/DotNetCore.CAP.PostgreSql.csproj — DotNetCore.CAP.PostgreSql(net8.0): 14 % XML-doc coverage (11/78).
  • Low XML-doc coverage: DotNetCore.CAP.MongoDB src/DotNetCore.CAP.MongoDB/DotNetCore.CAP.MongoDB.csproj — DotNetCore.CAP.MongoDB: 8 % XML-doc coverage (8/102).
  • Low XML-doc coverage: Sample.RabbitMQ.MongoDB samples/Sample.RabbitMQ.MongoDB/Sample.RabbitMQ.MongoDB.csproj — Sample.RabbitMQ.MongoDB: 0 % XML-doc coverage (0/7).
  • Low XML-doc coverage: DotNetCore.CAP.AzureServiceBus src/DotNetCore.CAP.AzureServiceBus/DotNetCore.CAP.AzureServiceBus.csproj — DotNetCore.CAP.AzureServiceBus: 31 % XML-doc coverage (24/78).
  • Low XML-doc coverage: DotNetCore.CAP.Dashboard src/DotNetCore.CAP.Dashboard/DotNetCore.CAP.Dashboard.csproj — DotNetCore.CAP.Dashboard: 16 % XML-doc coverage (28/176).
  • Low XML-doc coverage: Sample.RabbitMQ.SqlServer REDACTED — Sample.RabbitMQ.SqlServer: 0 % XML-doc coverage (0/35).
  • Low XML-doc coverage: Sample.Kafka.PostgreSql samples/Sample.Kafka.PostgreSql/Sample.Kafka.PostgreSql.csproj — Sample.Kafka.PostgreSql: 0 % XML-doc coverage (0/23).
  • Low XML-doc coverage: BuildScript REDACTED — BuildScript: 0 % XML-doc coverage (0/16).
  • Low XML-doc coverage: DotNetCore.CAP.InMemoryStorage src/DotNetCore.CAP.InMemoryStorage/DotNetCore.CAP.InMemoryStorage.csproj — DotNetCore.CAP.InMemoryStorage: 0 % XML-doc coverage (0/44).
  • Low XML-doc coverage: Sample.ConsoleApp samples/Sample.ConsoleApp/Sample.ConsoleApp.csproj — Sample.ConsoleApp: 0 % XML-doc coverage (0/6).
  • Low XML-doc coverage: DotNetCore.CAP.AmazonSQS src/DotNetCore.CAP.AmazonSQS/DotNetCore.CAP.AmazonSQS.csproj — DotNetCore.CAP.AmazonSQS: 15 % XML-doc coverage (5/34).
  • Low XML-doc coverage: DotNetCore.CAP.NATS src/DotNetCore.CAP.NATS/DotNetCore.CAP.NATS.csproj — DotNetCore.CAP.NATS: 24 % XML-doc coverage (9/37).
  • Low XML-doc coverage: Samples.Redis.SqlServer samples/Samples.Redis.SqlServer/Samples.Redis.SqlServer.csproj — Samples.Redis.SqlServer: 0 % XML-doc coverage (0/8).
  • Low XML-doc coverage: DotNetCore.CAP.RedisStreams src/DotNetCore.CAP.RedisStreams/DotNetCore.CAP.RedisStreams.csproj — DotNetCore.CAP.RedisStreams: 12 % XML-doc coverage (6/49).
  • Low XML-doc coverage: Sample.Dashboard.Auth samples/Sample.Dashboard.Auth/Sample.Dashboard.Auth.csproj — Sample.Dashboard.Auth: 0 % XML-doc coverage (0/18).
  • Low XML-doc coverage: DotNetCore.CAP.Pulsar REDACTED — DotNetCore.CAP.Pulsar: 8 % XML-doc coverage (3/39).
  • Low XML-doc coverage: DotNetCore.CAP.OpenTelemetry src/DotNetCore.CAP.OpenTelemetry/DotNetCore.CAP.OpenTelemetry.csproj — DotNetCore.CAP.OpenTelemetry: 20 % XML-doc coverage (3/15).
  • Low XML-doc coverage: Sample.AzureServiceBus.InMemory samples/Sample.AzureServiceBus.InMemory/Sample.AzureServiceBus.InMemory.csproj — Sample.AzureServiceBus.InMemory: 0 % XML-doc coverage (0/7).
  • Low XML-doc coverage: Sample.Dashboard.Jwt samples/Sample.Dashboard.Jwt/Sample.Dashboard.Jwt.csproj — Sample.Dashboard.Jwt: 0 % XML-doc coverage (0/3).
  • + 1 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×22
  • Sync-over-async blocking — 21 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP/ICapTransaction.Base.cs:108 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:94 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:99 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:104 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:109 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:260 — `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.RabbitMQ/IConnectionChannelPool.Default.cs:81 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.SqlServer/ICapTransaction.SqlServer.cs:169 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.SqlServer/ICapTransaction.SqlServer.cs:235 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.SqlServer/ICapTransaction.SqlServer.cs:237 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:149 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:214 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:216 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.cs:147 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.cs:148 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.cs:214 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.MongoDB/ICapTransaction.MongoDB.cs:97 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking REDACTED:75 — `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.AmazonSQS/ITransport.AmazonSQS.cs:143 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.RedisStreams/IConnectionPool.Default.cs:29 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/DotNetCore.CAP.RedisStreams/IConnectionPool.LazyConnection.cs:18 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
X2 · Cancellation propagation · Async method without CancellationToken · ×21
  • Async method without CancellationToken: FlushAsync src/DotNetCore.CAP/ICapTransaction.Base.cs:116 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ReStartAsync src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:73 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendAsync src/DotNetCore.CAP/Internal/IMessageSender.Default.cs:44 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendWithoutRetryAsync src/DotNetCore.CAP/Internal/IMessageSender.Default.cs:57 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SetSuccessfulState src/DotNetCore.CAP/Internal/IMessageSender.Default.cs:81 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SetFailedState src/DotNetCore.CAP/Internal/IMessageSender.Default.cs:87 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SetFailedState src/DotNetCore.CAP/Internal/ISubscribeExector.Default.cs:127 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: EnqueueToScheduler src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:74 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: EnqueueToPublish src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:89 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendScheduledMessageDirectlyAsync src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:288 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendBatchParallelAsync src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:330 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendBatchSequentialAsync src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:346 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendMessageAsync src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:354 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendMessageDirectlyAsync src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:370 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ProcessAsync src/DotNetCore.CAP/Processor/IProcessor.Delayed.cs:28 — No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken.
  • Async method without CancellationToken: ProcessAsync src/DotNetCore.CAP/Processor/IProcessor.InfiniteRetry.cs:23 — No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken.
  • Async method without CancellationToken: ProcessAsync src/DotNetCore.CAP/Processor/IProcessor.TransportCheck.cs:24 — No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken.
  • Async method without CancellationToken: SendAsync src/DotNetCore.CAP.Kafka/ITransport.Kafka.cs:29 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Rent src/DotNetCore.CAP.RabbitMQ/IConnectionChannelPool.Default.cs:125 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendAsync src/DotNetCore.CAP.RabbitMQ/ITransport.RabbitMQ.cs:31 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BasicAck src/DotNetCore.CAP.RabbitMQ/RabbitMQBasicConsumer.cs:93 — No CancellationToken parameter — this work can't be stopped early once started.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×20
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP/ICapTransaction.Base.cs:108 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:94 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:99 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:104 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:109 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:258 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.SqlServer/ICapTransaction.SqlServer.cs:169 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.SqlServer/ICapTransaction.SqlServer.cs:235 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.SqlServer/ICapTransaction.SqlServer.cs:237 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:149 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:214 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:216 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.cs:147 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.cs:148 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.cs:214 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.MongoDB/ICapTransaction.MongoDB.cs:97 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) REDACTED:75 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.AmazonSQS/ITransport.AmazonSQS.cs:143 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.RedisStreams/IConnectionPool.Default.cs:29 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/DotNetCore.CAP.RedisStreams/IConnectionPool.LazyConnection.cs:18 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
D29 · Static Analysis (SAST) · REDACTED · ×19
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX2 · Stateful singletons · Stateful singleton · ×11
  • Stateful singleton: ConsumerRegister src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:21 — `ConsumerRegister` is a singleton (one shared instance) but mutates instance state outside any lock (_cts, _selector, _dispatcher, _serializer, _storage, _consumerClientFactory; e.g. `_cts` at line 59).
  • Stateful singleton: MessageNeedToRetryProcessor src/DotNetCore.CAP/Processor/IProcessor.NeedRetry.cs:17 — `MessageNeedToRetryProcessor` is a singleton (one shared instance) but mutates instance state outside any lock (_failedRetryConsumeTask; e.g. `_failedRetryConsumeTask` at line 63).
  • Stateful singleton: Dispatcher src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:19 — `Dispatcher` is a singleton (one shared instance) but mutates instance state outside any lock (_tasksCts, _disposed; e.g. `_tasksCts` at line 60).
  • Stateful singleton: Bootstrapper src/DotNetCore.CAP/Internal/IBootstrapper.Default.cs:18 — `Bootstrapper` is a singleton (one shared instance) but mutates instance state outside any lock (_cts, _processors, _disposed; e.g. `_cts` at line 46).
  • Stateful singleton: ConnectionPool src/DotNetCore.CAP.Kafka/IConnectionPool.Default.cs:14 — `ConnectionPool` is a singleton (one shared instance) but mutates instance state outside any lock (_maxSize; e.g. `_maxSize` at line 73).
  • Stateful singleton: ConnectionChannelPool src/DotNetCore.CAP.RabbitMQ/IConnectionChannelPool.Default.cs:16 — `ConnectionChannelPool` is a singleton (one shared instance) but mutates instance state outside any lock (_maxSize; e.g. `_maxSize` at line 88).
  • Stateful singleton: MySqlStorageInitializer src/DotNetCore.CAP.MySql/IStorageInitializer.MySql.cs:14 — `MySqlStorageInitializer` is a singleton (one shared instance) but mutates instance state outside any lock (_serverVersion; e.g. `_serverVersion` at line 56).
  • Stateful singleton: GatewayProxyAgent src/DotNetCore.CAP.Dashboard/GatewayProxy/GatewayProxyAgent.cs:20 — `GatewayProxyAgent` is a singleton (one shared instance) but mutates instance state outside any lock (DownstreamRequest; e.g. `DownstreamRequest` at line 95).
  • Stateful singleton: RedisStreamManager src/DotNetCore.CAP.RedisStreams/IRedisStream.Manager.Default.cs:16 — `RedisStreamManager` is a singleton (one shared instance) but mutates instance state outside any lock (_redis; e.g. `_redis` at line 138).
  • Stateful singleton: RedisConnectionPool src/DotNetCore.CAP.RedisStreams/IConnectionPool.Default.cs:15 — `RedisConnectionPool` is a singleton (one shared instance) but mutates instance state outside any lock (_poolAlreadyConfigured; e.g. `_poolAlreadyConfigured` at line 51).
  • Stateful singleton: ConnectionFactory src/DotNetCore.CAP.Pulsar/IConnectionFactory.Default.cs:14 — `ConnectionFactory` is a singleton (one shared instance) but mutates instance state outside any lock (_client; e.g. `_client` at line 42).
D17 · Explicit Debt · Dead code · ×9
  • Dead code: Exists src/DotNetCore.CAP.Dashboard/GatewayProxy/Requester/IHttpClientCache.cs:10 — Method Exists — Roslyn's SymbolFinder walked every project the solution loads, including DotNetCore.CAP.Dashboard, 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: Handle samples/Sample.RabbitMQ.SqlServer/Messages/VeryFastProcessingReceiver.cs:18 — Method Handle — Roslyn's SymbolFinder walked every project the solution loads, including Sample.RabbitMQ.SqlServer, 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: Handle samples/Sample.RabbitMQ.SqlServer/Messages/XSlowProcessingReceiver.cs:18 — Method Handle — Roslyn's SymbolFinder walked every project the solution loads, including Sample.RabbitMQ.SqlServer, 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: TypedConsumerServiceSelector samples/Sample.RabbitMQ.SqlServer/TypedConsumers/TypedConsumerServiceSelector.cs:12 — NamedType TypedConsumerServiceSelector — Roslyn's SymbolFinder walked every project the solution loads, including Sample.RabbitMQ.SqlServer, 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: GetAbstract test/DotNetCore.CAP.Test/ConsumerServiceSelectorTest.cs:252 — Method GetAbstract — Roslyn's SymbolFinder walked every project the solution loads, including DotNetCore.CAP.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: GetAbstract2 test/DotNetCore.CAP.Test/ConsumerServiceSelectorTest.cs:259 — Method GetAbstract2 — Roslyn's SymbolFinder walked every project the solution loads, including DotNetCore.CAP.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: GenericConsumerServiceSelector test/DotNetCore.CAP.Test/GenericConsumerServiceSelector.cs:16 — NamedType GenericConsumerServiceSelector — Roslyn's SymbolFinder walked every project the solution loads, including DotNetCore.CAP.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: DockerRestartTests test/DotNetCore.CAP.NATS.Test/DockerRestartTests.cs:28 — NamedType DockerRestartTests — Roslyn's SymbolFinder walked every project the solution loads, including DotNetCore.CAP.NATS.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: NatsIntegrationTests test/DotNetCore.CAP.NATS.Test/NatsIntegrationTests.cs:20 — NamedType NatsIntegrationTests — Roslyn's SymbolFinder walked every project the solution loads, including DotNetCore.CAP.NATS.Test, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
D12 · Dependency Hygiene · Deprecated · ×8
  • Deprecated: xunit test/DotNetCore.CAP.MySql.Test/DotNetCore.CAP.MySql.Test.csproj:16 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit test/DotNetCore.CAP.Test/DotNetCore.CAP.Test.csproj:16 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit test/DotNetCore.CAP.AzureServiceBus.Test/DotNetCore.CAP.AzureServiceBus.Test.csproj:13 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit test/DotNetCore.CAP.NATS.Test/DotNetCore.CAP.NATS.Test.csproj:11 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: bootstrap src/DotNetCore.CAP.Dashboard/wwwroot/package.json:20 — bootstrap 4.6.2, declared in src/DotNetCore.CAP.Dashboard/wwwroot/package.json, is marked deprecated by its publisher: "This version of Bootstrap is no longer supported. Please upgrade to the latest version.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: vue src/DotNetCore.CAP.Dashboard/wwwroot/package.json:23 — vue 2.7.16, declared in src/DotNetCore.CAP.Dashboard/wwwroot/package.json, is marked deprecated by its publisher: "Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: vue-i18n src/DotNetCore.CAP.Dashboard/wwwroot/package.json:24 — vue-i18n 8.28.2, declared in src/DotNetCore.CAP.Dashboard/wwwroot/package.json, is marked deprecated by its publisher: "v9 and v10 no longer supported. please migrate to v11. about maintenance status, see https://vue-i18n.intlify.dev/guide/maintenance.html". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint src/DotNetCore.CAP.Dashboard/wwwroot/package.json:33 — eslint 8.57.0, declared in src/DotNetCore.CAP.Dashboard/wwwroot/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×8
  • Owned disposable field is never released src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs:25 — `KafkaConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 25), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 157) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released src/DotNetCore.CAP.RabbitMQ/RabbitMQConsumerClient.cs:18 — `RabbitMqConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 18), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 102) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs:22 — `AzureServiceBusConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_connectionLock` itself (line 22), which makes that instance its own. But `_connectionLock` is named in none of the methods the disposal search covered: `DisposeAsync` (line 145) — 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.
  • Owned disposable field is never released src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs:27 — `AzureServiceBusConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 27), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 145) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs:26 — `AmazonSQSConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 26), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 153) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released src/DotNetCore.CAP.RedisStreams/IConnectionPool.Default.cs:20 — `RedisConnectionPool` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_poolLock` itself (line 20), which makes that instance its own. But `_poolLock` is named in none of the methods the disposal search covered: `Dispose` (line 41), `Dispose` (line 88), `Dispose` (line 41), `Dispose` (line 88) — 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` (`_poolLock?.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/DotNetCore.CAP.RedisStreams/IConsumerClient.Redis.cs:24 — `RedisConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 24), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 72) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released src/DotNetCore.CAP.Pulsar/PulsarConsumerClient.cs:22 — `PulsarConsumerClient` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 22), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 112) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
D29 · Static Analysis (SAST) · REDACTED · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X18 · Disposal-pattern correctness · Disposes a dependency it does not own · ×6
  • Disposes a dependency it does not own src/DotNetCore.CAP.SqlServer/IDbContextTransaction.CAP.cs:29 — `_transaction` is never created by `CapEFDbTransaction` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 29). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own src/DotNetCore.CAP.SqlServer/IDbContextTransaction.CAP.cs:54 — `_transaction` is never created by `CapEFDbTransaction` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 54). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own src/DotNetCore.CAP.MySql/IDbContextTransaction.CAP.cs:30 — `_transaction` is never created by `CapEFDbTransaction` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 30). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own src/DotNetCore.CAP.PostgreSql/IDbContextTransaction.CAP.cs:27 — `_transaction` is never created by `CapEFDbTransaction` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 27). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own src/DotNetCore.CAP.PostgreSql/IDbContextTransaction.CAP.cs:54 — `_transaction` is never created by `CapEFDbTransaction` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 54). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
  • Disposes a dependency it does not own src/DotNetCore.CAP.MongoDB/IClientSessionHandle.CAP.cs:27 — `_transaction` is never created by `CapMongoDbClientSessionHandle` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 27). Its declared type `ICapTransaction` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
D17 · Explicit Debt · CommentedOutCode · ×5
  • CommentedOutCode REDACTED:13 — 3 consecutive commented-code lines
  • CommentedOutCode samples/Sample.RabbitMQ.SqlServer/Program.cs:42 — 7 consecutive commented-code lines
  • CommentedOutCode src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutor.cs:303 — 7 consecutive commented-code lines
  • CommentedOutCode src/DotNetCore.CAP.Dashboard/CAP.MetricsEventListener.cs:76 — 6 consecutive commented-code lines
  • CommentedOutCode src/DotNetCore.CAP.InMemoryStorage/IDataStorage.InMemory.cs:193 — 4 consecutive commented-code lines
X1 · Async correctness · Blocking `WaitHandle.WaitOne` inside an `async` method · ×5
  • Blocking `WaitHandle.WaitOne` inside an `async` method src/DotNetCore.CAP/Processor/IDispatcher.Default.cs:223 — `WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`).
  • Blocking `WaitHandle.WaitOne` inside an `async` method src/DotNetCore.CAP.RabbitMQ/RabbitMQConsumerClient.cs:87 — `WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`).
  • Blocking `WaitHandle.WaitOne` inside an `async` method src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs:121 — `WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`).
  • Blocking `WaitHandle.WaitOne` inside an `async` method src/DotNetCore.CAP.RedisStreams/IRedisStream.Manager.Default.cs:58 — `WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`).
  • Blocking `WaitHandle.WaitOne` inside an `async` method src/DotNetCore.CAP.RedisStreams/IRedisStream.Manager.Default.cs:79 — `WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`).
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×5
  • Disposable created and abandoned in the method that made it REDACTED:418 — `httpClient` is a `HttpClient`, which implements `IDisposable`, and it is created here (line 418). Every use of it in `PingServices` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var httpClient = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:15 — `cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 15). Every use of it in `Main` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cts = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:28 — `client` is a `Kubernetes`, which implements `IDisposable`, and it is created here (line 28). Every use of it in `GetNode` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:76 — `client` is a `Kubernetes`, which implements `IDisposable`, and it is created here (line 76). Every use of it in `GetNamespaces` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:95 — `client` is a `Kubernetes`, which implements `IDisposable`, and it is created here (line 95). Every use of it in `ListServices` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
D30 · Dependency Vulnerabilities · Medium CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: IDataStorage.PostgreSql.cs ↔ IStorageInitializer.PostgreSql.cs src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs:1 — `src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs` and `src/DotNetCore.CAP.PostgreSql/IStorageInitializer.PostgreSql.cs` change together 75% of the time (9 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `1cafc93c` Add default indexes to the database tables during creation and adjust…; `f0646a3f` Allow configuring PostgreSQL using an Npgsql data source (#1496); `ea2ec345` Fixed character string convert to datetime exception. — run `git show` on any of them.
  • Change coupling: REDACTED ↔ REDACTED REDACTED:1 — `REDACTED` and `REDACTED` change together 73% of the time (11 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `1cafc93c` Add default indexes to the database tables during creation and adjust…; `1b236d5f` Fixed SqlServer character string convert to datetime2 exception. #1302; `d203fef3` Fixed SqlServer character string convert to datetime2 exception. #1302 — run `git show` on any of them.
  • Change coupling: AzureServiceBusConsumerClient.cs ↔ ITransport.AzureServiceBus.cs src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs:1 — `src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs` and `src/DotNetCore.CAP.AzureServiceBus/ITransport.AzureServiceBus.cs` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `42431919` Add missing ConfigureAwait(false). (#1697); `225a513b` fix: BrokerAddress property in AzureServiceBus transport (#1576); `228820eb` Allow publishing to multiple Service Bus topics (attempt 2) (#1283) — run `git show` on any of them.
  • Change coupling: IConsumerServiceSelector.Default.cs ↔ MethodMatcherCache.cs src/DotNetCore.CAP/Internal/IConsumerServiceSelector.Default.cs:1 — `src/DotNetCore.CAP/Internal/IConsumerServiceSelector.Default.cs` and `src/DotNetCore.CAP/Internal/MethodMatcherCache.cs` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `19f64079` Add GroupConcurrent option to support subscriber concurrent execution…; `773e9428` support pattern matching for consumer. (#132); `68243b88` support pattern matching for consumer. (#132) — run `git show` on any of them.
GD1 · Unfinished & placeholder code · Unfinished stub · ×4
  • Unfinished stub — throws NotImplementedException src/DotNetCore.CAP.Dashboard/CircularBuffer.cs:153 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/DotNetCore.CAP.Dashboard/CircularBuffer.cs:173 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/DotNetCore.CAP.Dashboard/NodeDiscovery/INodeDiscoveryProvider.cs:17 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/DotNetCore.CAP.Dashboard/NodeDiscovery/INodeDiscoveryProvider.cs:27 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
X3 · Exception handling · Swallowed exception (empty catch) · ×4
  • Swallowed exception (empty catch) src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs:75 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/DotNetCore.CAP.Dashboard/CapCache.cs:79 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/DotNetCore.CAP.Dashboard/CapCache.cs:248 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/DotNetCore.CAP.Dashboard/CapCache.cs:280 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D17 · Explicit Debt · ContradictedWarningsAsErrors · ×3
  • ContradictedWarningsAsErrors src/DotNetCore.CAP.Kafka/DotNetCore.CAP.Kafka.csproj:10 — NU1701 — this project promotes that code to a build ERROR and, in the same project, also lists it as suppressed. Suppression is applied first, so the warning never reaches the promotion: this entry has no effect on any build, and the project enforces nothing for the code it appears to guard most strictly. The two lines record opposite decisions and the quiet one is winning, which is the expensive part — a reader auditing the gates sees the promotion and concludes the code is enforced. Decide which was meant: if the rule should fail the build, drop the code from the suppression list and fix what it reports; if the suppression is the real decision, delete this promotion so the configuration says what the build does.
  • ContradictedWarningsAsErrors src/DotNetCore.CAP.AzureServiceBus/DotNetCore.CAP.AzureServiceBus.csproj:10 — NU1701 — this project promotes that code to a build ERROR and, in the same project, also lists it as suppressed. Suppression is applied first, so the warning never reaches the promotion: this entry has no effect on any build, and the project enforces nothing for the code it appears to guard most strictly. The two lines record opposite decisions and the quiet one is winning, which is the expensive part — a reader auditing the gates sees the promotion and concludes the code is enforced. Decide which was meant: if the rule should fail the build, drop the code from the suppression list and fix what it reports; if the suppression is the real decision, delete this promotion so the configuration says what the build does.
  • ContradictedWarningsAsErrors samples/Sample.Kafka.PostgreSql/Sample.Kafka.PostgreSql.csproj:5 — NU1701 — this project promotes that code to a build ERROR and, in the same project, also lists it as suppressed. Suppression is applied first, so the warning never reaches the promotion: this entry has no effect on any build, and the project enforces nothing for the code it appears to guard most strictly. The two lines record opposite decisions and the quiet one is winning, which is the expensive part — a reader auditing the gates sees the promotion and concludes the code is enforced. Decide which was meant: if the rule should fail the build, drop the code from the suppression list and fix what it reports; if the suppression is the real decision, delete this promotion so the configuration says what the build does.
D10 · Test Quality · No assertions · ×2
  • No assertions: ChangePublishStateTest test/DotNetCore.CAP.MySql.Test/MySqlStorageConnectionTest.cs:62 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: ChangeReceiveStateTest test/DotNetCore.CAP.MySql.Test/MySqlStorageConnectionTest.cs:77 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
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/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:167 — src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:167-204 | src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:206-257 | src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:210-259 | src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs:209-269 — 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) REDACTED:201 — REDACTED:201-219 | REDACTED:222-236 | REDACTED:239-257 | REDACTED:260-274 — 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 (10 lines × 2) · ×2
  • Duplicated block (10 lines × 2) src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:246 — src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:246-255 | src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs:256-265 — `src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs` and `src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.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 7 separate duplicated blocks between them, totalling at least 97 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/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:246` 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 (10 lines × 2) src/DotNetCore.CAP.Dashboard.K8s/K8sDiscoveryOptionsExtensions.cs:25 — src/DotNetCore.CAP.Dashboard.K8s/K8sDiscoveryOptionsExtensions.cs:25-34 | src/DotNetCore.CAP.Dashboard/NodeDiscovery/CAP.ConsulDiscoveryOptionsExtensions.cs:25-34 — 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 (20 lines × 3) · ×2
  • Duplicated block (20 lines × 3) REDACTED:362 — REDACTED:362-381 | src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs:360-379 | REDACTED:358-377 — `REDACTED` and `src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.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 3 separate duplicated blocks between them, totalling at least 50 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 `REDACTED:362` 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.
  • Duplicated block (20 lines × 3) src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:37 — src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:37-56 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:36-55 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:36-55 — `src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs` and `src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.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 5 separate duplicated blocks between them, totalling at least 88 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 (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutor.cs:144 — src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutor.cs:144-159 | src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutor.cs:196-211 — 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 (16 lines × 2) src/DotNetCore.CAP.MongoDB/IDataStorage.MongoDB.cs:260 — src/DotNetCore.CAP.MongoDB/IDataStorage.MongoDB.cs:260-275 | src/DotNetCore.CAP.MongoDB/IDataStorage.MongoDB.cs:281-296 — 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/DotNetCore.CAP.MongoDB/IDataStorage.MongoDB.cs:260` 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 (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:44 — src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:44-57 | src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.cs:43-56 — `src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs` and `src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.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 52 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.
  • Duplicated block (14 lines × 2) src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:27 — src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:27-40 | src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.cs:26-39 — `src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs` and `src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.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 52 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 (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) src/DotNetCore.CAP/Diagnostics/EventData.Cap.P.cs:25 — src/DotNetCore.CAP/Diagnostics/EventData.Cap.P.cs:25-35 | src/DotNetCore.CAP/Diagnostics/EventData.Cap.S.cs:13-23 — 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.
  • Duplicated block (11 lines × 2) REDACTED:202 — REDACTED:202-212 | REDACTED:240-250 — 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 `REDACTED:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:61 — src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:61-72 | src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.cs:60-71 — `src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs` and `src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.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 52 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.
  • Duplicated block (12 lines × 2) src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:76 — src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs:76-87 | src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.cs:75-86 — `src/DotNetCore.CAP.MySql/ICapTransaction.MySql.cs` and `src/DotNetCore.CAP.PostgreSql/ICapTransaction.PostgreSql.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 52 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.
D8 · Code Coverage · CRAP 90 · ×2
  • CRAP 90: InMemoryMonitoringApi.GetMessagesAsync src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:57 — Cyclomatic 9 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
  • CRAP 90: MySqlMonitoringApi.GetMessagesAsync src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:86 — Cyclomatic 9 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException src/DotNetCore.CAP.Dashboard/CircularBuffer.cs:153 — `Contains` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/DotNetCore.CAP.Dashboard/CircularBuffer.cs:173 — `Remove` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×2
  • Outbound HTTP without resilience src/DotNetCore.CAP.Dashboard/GatewayProxy/Requester/HttpClientBuilder.cs:20 — `new HttpClient(CreateHttpMessageHandler(httpclientHandler))` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
  • Outbound HTTP without resilience REDACTED:418 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
X1 · Async correctness · Blocking `SemaphoreSlim.Wait` inside an `async` method · ×2
  • Blocking `SemaphoreSlim.Wait` inside an `async` method src/DotNetCore.CAP.Kafka/KafkaConsumerClient.cs:132 — `SemaphoreSlim.Wait` parks the thread while it queues for the semaphore. `await semaphore.WaitAsync(…)` yields the thread instead.
  • Blocking `SemaphoreSlim.Wait` inside an `async` method src/DotNetCore.CAP.Pulsar/PulsarConsumerClient.cs:65 — `SemaphoreSlim.Wait` parks the thread while it queues for the semaphore. `await semaphore.WaitAsync(…)` yields the thread instead.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×2
  • Swallowed exception (caught, then discarded) src/DotNetCore.CAP/CAP.Builder.cs:46 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) src/DotNetCore.CAP.MongoDB/IDataStorage.MongoDB.cs:373 — `catch (Exception) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark src/DotNetCore.CAP.Dashboard/wwwroot/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 9 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
D1 · Cyclomatic Complexity · DiagnosticListener.OnNext (cyclomatic 44) · ×1
  • DiagnosticListener.OnNext (cyclomatic 44) src/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs:33 — DiagnosticListener.OnNext has cyclomatic complexity 44 (threshold 15). Of this number, 36 points are the body's own statements and 8 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AmazonSQSConsumerClient.ConnectAsync (cyclomatic 18) · ×1
  • AmazonSQSConsumerClient.ConnectAsync (cyclomatic 18) src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs:161 — AmazonSQSConsumerClient.ConnectAsync has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AwaitableInfo.IsTypeAwaitable (cyclomatic 17) · ×1
  • AwaitableInfo.IsTypeAwaitable (cyclomatic 17) src/DotNetCore.CAP/Internal/ObjectMethodExecutor/AwaitableInfo.cs:41 — AwaitableInfo.IsTypeAwaitable has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 79, 90, 46, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · DiagnosticListener.OnNext (cognitive 67) · ×1
  • DiagnosticListener.OnNext (cognitive 67) src/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs:33 — DiagnosticListener.OnNext has cognitive complexity 67 (threshold 15). Of this number, 55 points are the body's own statements and 12 belong to 4 function literals inside it that branch. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · AmazonSQSConsumerClient.ConnectAsync (cognitive 49) · ×1
  • AmazonSQSConsumerClient.ConnectAsync (cognitive 49) src/DotNetCore.CAP.AmazonSQS/AmazonSQSConsumerClient.cs:161 — AmazonSQSConsumerClient.ConnectAsync has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SubscribeInvoker.InvokeAsync (cognitive 39) · ×1
  • SubscribeInvoker.InvokeAsync (cognitive 39) src/DotNetCore.CAP/Internal/ISubscribeInvoker.Default.cs:31 — SubscribeInvoker.InvokeAsync has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ConsumerServiceSelector.FindConsumersFromInterfaceTypes (cognitive 28) · ×1
  • ConsumerServiceSelector.FindConsumersFromInterfaceTypes (cognitive 28) src/DotNetCore.CAP/Internal/IConsumerServiceSelector.Default.cs:70 — ConsumerServiceSelector.FindConsumersFromInterfaceTypes has cognitive complexity 28 (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 · AzureServiceBusConsumerClient.ConnectAsync (cognitive 24) · ×1
  • AzureServiceBusConsumerClient.ConnectAsync (cognitive 24) src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs:192 — AzureServiceBusConsumerClient.ConnectAsync has cognitive complexity 24 (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 · GatewayProxyAgent.Invoke (cognitive 19) · ×1
  • GatewayProxyAgent.Invoke (cognitive 19) src/DotNetCore.CAP.Dashboard/GatewayProxy/GatewayProxyAgent.cs:48 — GatewayProxyAgent.Invoke has cognitive complexity 19 (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 · RedisConsumerClient.ConsumeMessages (cognitive 19) · ×1
  • RedisConsumerClient.ConsumeMessages (cognitive 19) src/DotNetCore.CAP.RedisStreams/IConsumerClient.Redis.cs:90 — RedisConsumerClient.ConsumeMessages has cognitive complexity 19 (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 · ConsumerRegister.RegisterMessageProcessor (cognitive 18) · ×1
  • ConsumerRegister.RegisterMessageProcessor (cognitive 18) src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:168 — ConsumerRegister.RegisterMessageProcessor has cognitive complexity 18 (threshold 15). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 171). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · DiagnosticObserver.OnNext (cognitive 16) · ×1
  • DiagnosticObserver.OnNext (cognitive 16) src/DotNetCore.CAP.SqlServer/Diagnostics/DiagnosticObserver.cs:36 — DiagnosticObserver.OnNext has cognitive complexity 16 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · InMemoryMonitoringApi.GetMessagesAsync (cognitive 16) · ×1
  • InMemoryMonitoringApi.GetMessagesAsync (cognitive 16) src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:57 — InMemoryMonitoringApi.GetMessagesAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: DiagnosticListener.OnNext src/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs:33 — MethodTooLong — OnNext runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×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 (9 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:16 — src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:16-32 | src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:36-56 | src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:60-86 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:16-31 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:35-55 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:59-85 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:16-31 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:35-55 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:59-85 — These 9 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 9 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 9 times.
D4 · Code Duplication · Duplicated block (35–36 lines × 2) · ×1
  • Duplicated block (35–36 lines × 2) src/DotNetCore.CAP.MongoDB/IMonitoringApi.MongoDB.cs:128 — src/DotNetCore.CAP.MongoDB/IMonitoringApi.MongoDB.cs:128-163 | src/DotNetCore.CAP.MongoDB/IMonitoringApi.MongoDB.cs:169-203 — 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/DotNetCore.CAP.MongoDB/IMonitoringApi.MongoDB.cs:128` 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 (28–29 lines × 2) · ×1
  • Duplicated block (28–29 lines × 2) src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:69 — src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:69-96 | src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:111-139 — 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/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×1
  • Duplicated block (27–28 lines × 2) src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:120 — src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:120-146 | src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs:124-151 — `src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs` and `src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.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 7 separate duplicated blocks between them, totalling at least 97 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/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:120` 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 (26 lines × 3) · ×1
  • Duplicated block (26 lines × 3) src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:61 — src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:61-86 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:60-85 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:60-85 — `src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs` and `src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.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 5 separate duplicated blocks between them, totalling at least 88 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 (24–26 lines × 2) · ×1
  • Duplicated block (24–26 lines × 2) REDACTED:278 — REDACTED:278-301 | REDACTED:304-329 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (23 lines × 3) · ×1
  • Duplicated block (23 lines × 3) src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:264 — src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:264-286 | src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:267-289 | src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs:276-298 — `src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs` and `src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.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 6 separate duplicated blocks between them, totalling at least 78 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/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:264` 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 (22 lines × 3) · ×1
  • Duplicated block (22 lines × 3) REDACTED:280 — REDACTED:280-301 | src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs:273-294 | REDACTED:275-296 — `REDACTED` and `src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.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 3 separate duplicated blocks between them, totalling at least 50 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 `REDACTED:280` 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 (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:54 — src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:54-72 | src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:65-83 — `src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs` and `src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.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 6 separate duplicated blocks between them, totalling at least 78 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/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:54` 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–17 lines × 3) · ×1
  • Duplicated block (16–17 lines × 3) src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:16 — src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:16-32 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:16-31 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:16-31 — `src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs` and `src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.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 5 separate duplicated blocks between them, totalling at least 88 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) src/DotNetCore.CAP.MongoDB/StorageMessage.cs:19 — src/DotNetCore.CAP.MongoDB/StorageMessage.cs:19-31 | src/DotNetCore.CAP.MongoDB/StorageMessage.cs:40-52 — 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 (12–13 lines × 6) · ×1
  • Duplicated block (12–13 lines × 6) src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:17 — src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:17-29 | src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:37-48 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:17-28 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:36-47 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:17-28 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:36-47 — `src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs` and `src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.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 5 separate duplicated blocks between them, totalling at least 88 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 (8–13 lines × 2) · ×1
  • Duplicated block (8–13 lines × 2) src/DotNetCore.CAP.InMemoryStorage/IDataStorage.InMemory.cs:187 — src/DotNetCore.CAP.InMemoryStorage/IDataStorage.InMemory.cs:187-199 | src/DotNetCore.CAP.InMemoryStorage/IDataStorage.InMemory.cs:204-211 — 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/DotNetCore.CAP.InMemoryStorage/IDataStorage.InMemory.cs:187` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–12 lines × 9) · ×1
  • Duplicated block (11–12 lines × 9) src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:16 — src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:16-27 | src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:36-46 | src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:60-70 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:16-26 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:35-45 | src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.cs:59-69 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:16-26 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:35-45 | src/DotNetCore.CAP.SqlServer/IDbConnection.Extensions.cs:59-69 — `src/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs` and `src/DotNetCore.CAP.PostgreSql/IDbConnection.Extensions.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 5 separate duplicated blocks between them, totalling at least 88 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/DotNetCore.CAP.MySql/IDbConnection.Extensions.cs:16` 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 (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:249 — src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:249-257 | src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:251-259 | src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs:261-269 — `src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs` and `src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.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 6 separate duplicated blocks between them, totalling at least 78 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/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:249` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) REDACTED:202 — REDACTED:202-211 | REDACTED:223-232 | REDACTED:240-249 | REDACTED:261-270 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) REDACTED:147 — REDACTED:147-154 | src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs:144-151 | REDACTED:144-151 — `REDACTED` and `src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.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 3 separate duplicated blocks between them, totalling at least 50 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 `REDACTED:147` 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 (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:63 — src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:63-69 | src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:101-107 — 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 (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:59 — src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:59-68 | src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:70-79 | src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs:60-69 — `src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs` and `src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.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 6 separate duplicated blocks between them, totalling at least 78 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. 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 (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:197 — src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:197-201 | src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:250-254 | src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:252-256 | src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs:262-266 — `src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs` and `src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.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 6 separate duplicated blocks between them, totalling at least 78 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 (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:189 — src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs:189-200 | src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.cs:193-204 | src/DotNetCore.CAP.SqlServer/IMonitoringApi.SqlServer.cs:195-206 — `src/DotNetCore.CAP.MySql/IMonitoringApi.MySql.cs` and `src/DotNetCore.CAP.PostgreSql/IMonitoringApi.PostgreSql.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 6 separate duplicated blocks between them, totalling at least 78 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: DotNetCore.CAP(net8.0) src/DotNetCore.CAP/DotNetCore.CAP.csproj:1 — DotNetCore.CAP(net8.0): abstractness 0.27, instability 0.00, distance 0.73 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
D8 · Code Coverage · No test project references DotNetCore.CAP.RedisStreams · ×1
  • No test project references DotNetCore.CAP.RedisStreams src/DotNetCore.CAP.RedisStreams/DotNetCore.CAP.RedisStreams.csproj — No test project in this repository references DotNetCore.CAP.RedisStreams (17 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 39.0% 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 DotNetCore.CAP.SqlServer · ×1
  • No test project references DotNetCore.CAP.SqlServer REDACTED — No test project in this repository references DotNetCore.CAP.SqlServer (13 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 39.0% 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 DotNetCore.CAP.MongoDB · ×1
  • No test project references DotNetCore.CAP.MongoDB src/DotNetCore.CAP.MongoDB/DotNetCore.CAP.MongoDB.csproj — No test project in this repository references DotNetCore.CAP.MongoDB (10 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 39.0% 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 DotNetCore.CAP.PostgreSql · ×1
  • No test project references DotNetCore.CAP.PostgreSql src/DotNetCore.CAP.PostgreSql/DotNetCore.CAP.PostgreSql.csproj — No test project in this repository references DotNetCore.CAP.PostgreSql (10 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 39.0% 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 DotNetCore.CAP.AmazonSQS · ×1
  • No test project references DotNetCore.CAP.AmazonSQS src/DotNetCore.CAP.AmazonSQS/DotNetCore.CAP.AmazonSQS.csproj — No test project in this repository references DotNetCore.CAP.AmazonSQS (9 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 39.0% 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 DotNetCore.CAP.Kafka · ×1
  • No test project references DotNetCore.CAP.Kafka src/DotNetCore.CAP.Kafka/DotNetCore.CAP.Kafka.csproj — No test project in this repository references DotNetCore.CAP.Kafka (9 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 39.0% 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 DotNetCore.CAP.Pulsar · ×1
  • No test project references DotNetCore.CAP.Pulsar REDACTED — No test project in this repository references DotNetCore.CAP.Pulsar (9 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 39.0% 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 DotNetCore.CAP.RabbitMQ · ×1
  • No test project references DotNetCore.CAP.RabbitMQ src/DotNetCore.CAP.RabbitMQ/DotNetCore.CAP.RabbitMQ.csproj — No test project in this repository references DotNetCore.CAP.RabbitMQ (9 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 39.0% 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 DotNetCore.CAP.Dashboard.K8s · ×1
  • No test project references DotNetCore.CAP.Dashboard.K8s src/DotNetCore.CAP.Dashboard.K8s/DotNetCore.CAP.Dashboard.K8s.csproj — No test project in this repository references DotNetCore.CAP.Dashboard.K8s (4 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 39.0% 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 DotNetCore.CAP.OpenTelemetry · ×1
  • No test project references DotNetCore.CAP.OpenTelemetry src/DotNetCore.CAP.OpenTelemetry/DotNetCore.CAP.OpenTelemetry.csproj — No test project in this repository references DotNetCore.CAP.OpenTelemetry (4 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 39.0% 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 199 · ×1
  • CRAP 199: AwaitableInfo.IsTypeAwaitable src/DotNetCore.CAP/Internal/ObjectMethodExecutor/AwaitableInfo.cs:41 — Cyclomatic 17 with 14.3% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 110 · ×1
  • CRAP 110: AzureServiceBusConsumerClient.ConnectAsync src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs:192 — Cyclomatic 10 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 56 · ×1
  • CRAP 56: AzureServiceBusConsumerClient.SubscribeAsync src/DotNetCore.CAP.AzureServiceBus/AzureServiceBusConsumerClient.cs:54 — Cyclomatic 7 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 43 · ×1
  • CRAP 43: ConsumerRegister.WriteLog src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:276 — Cyclomatic 14 with 47.1% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
D8 · Code Coverage · CRAP 42 · ×1
  • CRAP 42: InMemoryMonitoringApi.GetHourlyTimelineStats src/DotNetCore.CAP.InMemoryStorage/IMonitoringApi.InMemory.cs:166 — Cyclomatic 6 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 39 · ×1
  • CRAP 39: ObjectMethodExecutorFSharpSupport.TryPopulateFSharpValueCaches src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutorFSharpSupport.cs:92 — Cyclomatic 8 with 21.1% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
S1 · Web-Security Posture · Token validation disabled · ×1
  • Token validation disabled REDACTED:32 — `ValidateAudience`, `ValidateIssuer` are all set to `false`, which means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
X1 · Async correctness · Blocking `AzureServiceBusTransport.GetSenderForProducer` inside an `async` method · ×1
  • Blocking `AzureServiceBusTransport.GetSenderForProducer` inside an `async` method src/DotNetCore.CAP.AzureServiceBus/ITransport.AzureServiceBus.cs:62 — `AzureServiceBusTransport.GetSenderForProducer` is a synchronous helper that blocks (`SemaphoreSlim.Wait`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll).
X1 · Async correctness · Blocking `SemaphoreSlim.Wait()` inside an `async` method · ×1
  • Blocking `SemaphoreSlim.Wait()` inside an `async` method src/DotNetCore.CAP.RedisStreams/IConsumerClient.Redis.cs:102 — This acquires a `SemaphoreSlim` with the BLOCKING `Wait()` inside a method that is already `async`. The thread does not yield while it queues for the semaphore: it parks a pool thread doing no work, and under contention the pool must grow (or the holders must finish) before any waiter can proceed — which is how a bounded-concurrency gate turns into a throughput collapse under exactly the load it exists to bound. `SemaphoreSlim` ships an asynchronous acquire for this: `await semaphore.WaitAsync()` releases the thread while it waits and is legal here because the enclosing method is already `async`, so this is a one-word change with no signature to break. Where the acquire must be bounded, `await semaphore.WaitAsync(timeout)`/`WaitAsync(cancellationToken)` keep that property; and whichever you use, release it in a `finally` so a throw inside the critical section cannot leak a permit.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×1
  • Sync-over-async (deadlock risk) through `.Result` src/DotNetCore.CAP.Pulsar/IConnectionFactory.Default.cs:71 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
X2 · Cancellation propagation · Async local function without CancellationToken · ×1
  • Async local function without CancellationToken: ScheduleTask src/DotNetCore.CAP/Processor/IProcessor.Delayed.cs:43 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×1
  • Argument guard throws the exception its own condition disproves src/DotNetCore.CAP/Internal/ICapPublisher.Default.cs:115 — The guard on line 115 rejects `name` and line 115 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×1
  • Untrusted text written into markup unescaped REDACTED:75 — `htmlBuilder.ToString()` is text this program did not author, and it is written into the text of an element through `HttpResponse.WriteAsync` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×1
  • Symbol treated as nullable, then dereferenced unguarded src/DotNetCore.CAP/Internal/ObjectMethodExecutor/ObjectMethodExecutorFSharpSupport.cs:85 — This method contradicts itself about `possibleFSharpAsyncGenericType`: line 76 writes `possibleFSharpAsyncGenericType?.FullName`, which says `possibleFSharpAsyncGenericType` can be null, but line 85 then dereferences it directly as `possibleFSharpAsyncGenericType.Assembly` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `possibleFSharpAsyncGenericType` truly cannot be null here, the `?.` is misleading. Settle it one way — test `possibleFSharpAsyncGenericType` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Minor — 92 finding(s)
X4 · Structured logging · Interpolated log message defeats structured logging · ×40
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:127 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:155 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:159 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:282 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:286 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:289 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:293 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:296 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:299 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:303 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:306 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:309 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:313 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:316 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/IConsumerRegister.Default.cs:320 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/LoggerExtensions.cs:13 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/LoggerExtensions.cs:19 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/LoggerExtensions.cs:25 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/LoggerExtensions.cs:30 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/LoggerExtensions.cs:36 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/LoggerExtensions.cs:41 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/LoggerExtensions.cs:46 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/LoggerExtensions.cs:51 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/LoggerExtensions.cs:57 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/DotNetCore.CAP/Internal/LoggerExtensions.cs:63 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • + 15 more in this group — see findings.md.
S1 · Web-Security Posture · No security response headers detected · ×9
  • No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • No security response headers detected samples/Sample.AzureServiceBus.InMemory/Program.cs:8 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected samples/Sample.Dashboard.Auth/Program.cs:14 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected REDACTED:9 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected samples/Sample.Kafka.PostgreSql/Program.cs:7 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected samples/Sample.RabbitMQ.MongoDB/Program.cs:6 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected samples/Sample.RabbitMQ.MySql/Program.cs:5 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected samples/Sample.RabbitMQ.SqlServer/Program.cs:7 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected REDACTED:4 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
D12 · Dependency Hygiene · Outdated (npm) · ×7
  • Outdated (npm): ansi-styles — ansi-styles 4.3.0 → 7.0.0 available.
  • Outdated (npm): nanoid — nanoid 3.3.7 → 6.0.2 available.
  • Outdated (npm): supports-color — supports-color 7.2.0 → 11.0.0 available.
  • Outdated (npm): tr46 — tr46 0.0.3 → 7.0.0 available.
  • Outdated (npm): vue-i18n src/DotNetCore.CAP.Dashboard/wwwroot/package.json:24 — vue-i18n 8.28.2 → 11.4.16 available.
  • Outdated (npm): webidl-conversions — webidl-conversions 3.0.1 → 8.0.1 available.
  • Outdated (npm): whatwg-url — whatwg-url 5.0.0 → 17.3.0 available.
IC1 · Incompleteness & stubs · Commented-out code · ×4
  • Commented-out code src/DotNetCore.CAP.Dashboard/CAP.MetricsEventListener.cs:78 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/DotNetCore.CAP.Dashboard/CAP.MetricsEventListener.cs:79 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/DotNetCore.CAP.Dashboard/CAP.MetricsEventListener.cs:80 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/DotNetCore.CAP.InMemoryStorage/IDataStorage.InMemory.cs:195 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
D30 · Dependency Vulnerabilities · Low CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
M4 · Documentation accuracy · README/code drift · ×3
  • README/code drift docs/readme.md:16 — docs/readme.md changes into `CAP/docs`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/content/user-guide/en/cap/idempotence.md:7 — docs/content/user-guide/en/cap/idempotence.md links to `The`, but `docs/content/user-guide/en/cap/The` 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 docs/content/user-guide/en/cap/transactions.md:17 — docs/content/user-guide/en/cap/transactions.md links to `This`, but `docs/content/user-guide/en/cap/This` 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.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IDataStorage (16 members) src/DotNetCore.CAP/Persistence/IDataStorage.cs:14 — `IDataStorage` declares 16 members: `AcquireLockAsync`, `ReleaseLockAsync`, `RenewLockAsync`, `ChangePublishStateToDelayedAsync`, `ChangePublishStateAsync`, `ChangeReceiveStateAsync`, `StoreMessageAsync`, `StoreReceivedExceptionMessageAsync`, `StoreReceivedMessageAsync`, `DeleteExpiresAsync`, `GetPublishedMessagesOfNeedRetry`, `ScheduleMessagesOfDelayedAsync`, `GetReceivedMessagesOfNeedRetry`, `DeleteReceivedMessageAsync`, `DeletePublishedMessageAsync`, `GetMonitoringApi`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D12 · Dependency Hygiene · Deprecated · ×1
  • Deprecated: popper.js REDACTED:1703 — popper.js 1.16.1 is resolved in REDACTED and is marked deprecated by its publisher: "You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no project overview README.md — The opening paragraph describes CAP as a library providing distributed transactions and an event bus with Outbox pattern but does not state what the repository is or what it does beyond its features list. State the project's purpose (distributed transaction/event-bus solution) and the two main use cases it addresses in one sentence above the opening paragraph.
D21 · Naming Consistency · The test method `GetCallbackNameTest` duplicates the name of the method under test `GetCallbackName` by appending 'Test'. While common in some frameworks, the codebase generally uses descriptive test names (e.g., `EnqueueToPublish_ShouldInvokeSend_WhenParallelSendDisabled`) or distinct names. More importantly, the test name `GetCallbackNameTest` is structurally identical to the production method `GetCallbackName` plus a suffix, which can be confusing when reading stack traces or logs where the distinction is purely syntactic. However, this is a minor style issue. A more significant inconsistency is found in the naming of the helper/fixture vs the concept it represents. · ×1
  • The test method `GetCallbackNameTest` duplicates the name of the method under test `GetCallbackName` by appending 'Test'. While common in some frameworks, the codebase generally uses descriptive test names (e.g., `EnqueueToPublish_ShouldInvokeSend_WhenParallelSendDisabled`) or distinct names. More importantly, the test name `GetCallbackNameTest` is structurally identical to the production method `GetCallbackName` plus a suffix, which can be confusing when reading stack traces or logs where the distinction is purely syntactic. However, this is a minor style issue. A more significant inconsistency is found in the naming of the helper/fixture vs the concept it represents. — Rename `GetCallbackNameTest` to `GetCallbackName_ShouldReturnCorrectValue` or similar to follow the descriptive naming convention seen in other tests like `EnqueueToPublish_ShouldInvokeSend_WhenParallelSendDisabled`. (symbols: DotNetCore.CAP.Test.MessageExtensionTest.GetCallbackNameTest, DotNetCore.CAP.Messages.MessageExtensions.GetCallbackName)
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 1 of 92 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 92 of the 236 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/DotNetCore.CAP.AzureServiceBus/ServiceBusProcessorFacade.cs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D34 · Knowledge Freshness · Orphaned file · ×1
  • Orphaned file src/DotNetCore.CAP.AzureServiceBus/ServiceBusProcessorFacade.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D39 · IL Efficiency · IL efficiency · ×1
  • IL efficiency: 5 authored method(s) exceed the IL budget src/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs:35 — 5 of 1231 first-party methods compile to oversized IL bodies (> 250 instructions); worst: DotNetCore.CAP.OpenTelemetry.DiagnosticListener.OnNext @ src/DotNetCore.CAP.OpenTelemetry/DiagnosticListener.cs:35, 851 IL instructions; that pulled this dimension to 9.9/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.
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.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 21/25 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 25, 9 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P2 · Observability · Console output used as the logging channel · ×1
  • Console output used as the logging channel samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs:161 — `samples/Sample.RabbitMQ.SqlServer/Controllers/ValuesController.cs` reports through `Console.Write…` at line 161 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
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 2952 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.
PF1 · Benchmark discipline · No performance benchmarks · ×1
  • No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
S1 · Web-Security Posture · OIDC metadata fetched over HTTP · ×1
  • OIDC metadata fetched over HTTP REDACTED:57 — `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path.
S1 · Web-Security Posture · Secure cookie flags not detected · ×1
  • Secure cookie flags not detected src/DotNetCore.CAP.Dashboard/GatewayProxy/GatewayProxyAgent.cs:112 — No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.)
X10 · Duplicated predicate · Duplicated predicate · ×1
  • Duplicated predicate REDACTED:150 — `dbTrans == null && transaction is IDbContextTransaction dbContextTrans` appears character-identically in 3 files — REDACTED, src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs, REDACTED. 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.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 71/294 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×1
  • Diagnostic log message is built whether or not it is wanted src/DotNetCore.CAP.Pulsar/IConnectionFactory.Default.cs:27 — `LogDebug` at line 27 is called with an argument built by `JsonConvert.SerializeObject(_options, Formatting.Indented)` (line 27), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 17/26 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~3.5 `!` suppressions per 1k syntax nodes — 266 suppression(s) across the 75823 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch src/DotNetCore.CAP/Internal/Helper.cs:53 — `GetInstanceHostname` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×1
  • Silent fallback default on parse failure src/DotNetCore.CAP/Internal/MethodMatcherCache.cs:52 — `GetGroupConcurrentLimit` falls back to `(byte)1` when `GroupConcurrent.TryGetValue(group, out byte value)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Minor — 65 finding(s)
D12 · Dependency Hygiene · Outdated · ×34
  • Outdated: Microsoft.Extensions.Hosting.Abstractions — Microsoft.Extensions.Hosting.Abstractions 10.0.0 → 10.0.13 available (referenced by DotNetCore.CAP).
  • Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 10.0.0 → 10.0.13 available (referenced by DotNetCore.CAP).
  • Outdated: Microsoft.Extensions.Options — Microsoft.Extensions.Options 10.0.0 → 10.0.13 available (referenced by DotNetCore.CAP).
  • Outdated: Microsoft.SourceLink.GitHub — Microsoft.SourceLink.GitHub 10.0.203 → 10.0.402 available (referenced by DotNetCore.CAP).
  • Outdated: Confluent.Kafka — Confluent.Kafka 2.14.2 → 2.16.0 available (referenced by DotNetCore.CAP.Kafka).
  • Outdated: RabbitMQ.Client — RabbitMQ.Client 7.2.1 → 7.2.2 available (referenced by DotNetCore.CAP.RabbitMQ).
  • Outdated: Microsoft.Data.SqlClient — Microsoft.Data.SqlClient 7.0.1 → 7.1.1 available (referenced by DotNetCore.CAP.SqlServer).
  • Outdated: Microsoft.EntityFrameworkCore.Relational — Microsoft.EntityFrameworkCore.Relational 10.0.0 → 10.0.13 available (referenced by DotNetCore.CAP.SqlServer).
  • Outdated: MySqlConnector — MySqlConnector 2.6.0 → 2.6.2 available (referenced by DotNetCore.CAP.MySql).
  • Outdated: coverlet.collector — coverlet.collector 10.0.1 → 10.1.0 available (referenced by DotNetCore.CAP.MySql.Test).
  • Outdated: Dapper — Dapper 2.1.79 → 2.1.89 available (referenced by DotNetCore.CAP.MySql.Test).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 18.0.1 → 18.11.0 available (referenced by DotNetCore.CAP.MySql.Test).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 3.1.5 → 4.0.1 available (referenced by DotNetCore.CAP.MySql.Test).
  • Outdated: Microsoft.AspNetCore.Authentication.JwtBearer — Microsoft.AspNetCore.Authentication.JwtBearer 10.0.0 → 10.0.13 available (referenced by Sample.RabbitMQ.MySql).
  • Outdated: Npgsql — Npgsql 10.0.2 → 10.0.3 available (referenced by DotNetCore.CAP.PostgreSql).
  • Outdated: MongoDB.Driver — MongoDB.Driver 3.9.0 → 3.13.0 available (referenced by DotNetCore.CAP.MongoDB).
  • Outdated: Azure.Messaging.ServiceBus — Azure.Messaging.ServiceBus 7.20.1 → 7.21.0 available (referenced by DotNetCore.CAP.AzureServiceBus).
  • Outdated: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer 10.0.0 → 10.0.13 available (referenced by Sample.RabbitMQ.SqlServer).
  • Outdated: Npgsql.EntityFrameworkCore.PostgreSQL — Npgsql.EntityFrameworkCore.PostgreSQL 10.0.1 → 10.0.3 available (referenced by Sample.Kafka.PostgreSql).
  • Outdated: FluentAssertions — FluentAssertions 8.10.0 → 8.11.0 available (referenced by DotNetCore.CAP.Test).
  • Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 10.0.0 → 10.0.13 available (referenced by DotNetCore.CAP.Test).
  • Outdated: Microsoft.Extensions.Logging — Microsoft.Extensions.Logging 10.0.0 → 10.0.13 available (referenced by DotNetCore.CAP.Test).
  • Outdated: NSubstitute — NSubstitute 5.3.0 → 6.2.0 available (referenced by DotNetCore.CAP.Test).
  • Outdated: Microsoft.Extensions.Logging.Console — Microsoft.Extensions.Logging.Console 10.0.0 → 10.0.13 available (referenced by Sample.ConsoleApp).
  • Outdated: AWSSDK.SimpleNotificationService — AWSSDK.SimpleNotificationService 4.0.3.8 → 4.0.100.21 available (referenced by DotNetCore.CAP.AmazonSQS).
  • + 9 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated (npm) · ×30
  • Outdated (npm): @babel/parser — @babel/parser 7.24.5 → 8.0.7 available.
  • Outdated (npm): @nuxt/opencollective — @nuxt/opencollective 0.3.3 → 0.4.1 available.
  • Outdated (npm): @vue/compiler-sfc — @vue/compiler-sfc 2.7.16 → 3.5.44 available.
  • Outdated (npm): asynckit — asynckit 0.4.0 → 0.5.0 available.
  • Outdated (npm): axios — axios 0.28.1 → 1.20.0 available.
  • Outdated (npm): bignumber.js — bignumber.js 9.1.2 → 11.1.5 available.
  • Outdated (npm): bootstrap — bootstrap 4.6.2 → 5.3.8 available.
  • Outdated (npm): chalk — chalk 4.1.2 → 6.0.1 available.
  • Outdated (npm): color-convert — color-convert 2.0.1 → 3.1.3 available.
  • Outdated (npm): color-name — color-name 1.1.4 → 2.1.1 available.
  • Outdated (npm): consola — consola 2.15.3 → 3.4.2 available.
  • Outdated (npm): csstype — csstype 3.1.3 → 3.2.3 available.
  • Outdated (npm): follow-redirects — follow-redirects 1.15.6 → 1.16.1 available.
  • Outdated (npm): form-data — form-data 4.0.0 → 4.0.6 available.
  • Outdated (npm): has-flag — has-flag 4.0.0 → 5.0.1 available.
  • Outdated (npm): jquery — jquery 3.7.1 → 4.0.0 available.
  • Outdated (npm): mime-db — mime-db 1.52.0 → 1.54.0 available.
  • Outdated (npm): mime-types — mime-types 2.1.35 → 3.0.2 available.
  • Outdated (npm): node-fetch — node-fetch 2.7.0 → 3.3.2 available.
  • Outdated (npm): picocolors — picocolors 1.0.0 → 1.1.1 available.
  • Outdated (npm): portal-vue — portal-vue 2.1.7 → 3.0.0 available.
  • Outdated (npm): postcss — postcss 8.4.38 → 8.5.31 available.
  • Outdated (npm): prettier — prettier 2.8.8 → 3.9.10 available.
  • Outdated (npm): proxy-from-env — proxy-from-env 1.1.0 → 2.1.0 available.
  • Outdated (npm): source-map — source-map 0.6.1 → 0.8.0 available.
  • + 5 more in this group — see findings.md.
D10 · Test Quality · Mock framework · ×1
  • Mock framework: NSubstitute — DotNetCore.CAP.Test references NSubstitute.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-bca87a78200f413a912fbb68d3740650/history.json --exit-code 0 --source .1artifacts/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-bca87a78200f413a912fbb68d3740650/tree.json --exit-code 0 --source .1artifacts/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 .47artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list CAP.sln package --vulnerable --include-transitive --format json25artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 8 file(s) — `src/DotNetCore.CAP.Dashboard/HtmlHelper.cs`, `src/DotNetCore.CAP.RedisStreams/ICapOptionsExtension.Redis.cs`, `src/DotNetCore.CAP.RedisStreams/IConnectionPool.LazyConnection.cs`, `src/DotNetCore.CAP.RedisStreams/IConsumerClient.Redis.cs`, `src/DotNetCore.CAP.RedisStreams/IConsumerClientFactory.Redis.cs`, … (+3 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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a1687b-8947-774b-98f5-9df5d312230e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 90 · Warnings: 330 · Recommendations: 92 · Info: 65 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 11:18 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