Public report of litenova/LiteBus, published 8 November 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.11.2). Assert 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, 8 November 2026, 15:36 UTC · Survey ID cd_34f3ee9dcf5d44f584f5ae95be801e90

litenova/LiteBus

Measured 8 November 2026, 15:35 UTC, at code version e8ec7f0

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 57out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 2 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.

A medium codebase: 96,176 lines of product code in 106 projects, tests not counted · Estimated rebuild effort: about 2.6 person-years · Weakest lens: Security and Compliance, 48

Findings by how serious they are

51 critical 404 serious 241 minor

7 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
8 November 2026, 15:35 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 the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work 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 ▸

93of 93 dimensions measured by tools.
603of 696 findings point to an exact file and line, so you can open each one in the code. The other 93 concern the repository as a whole, such as missing documentation.
93dimensions across 8 lenses, read from 96,176 lines of product code in 106 projects.
Chapters

Executive summary

litenova/LiteBus falls short of our standard for production, in part because we found no encryption of stored data, no key vault and no enforced HTTPS. It scores 57 out of 100 and is rated Adequate, and four of its 51 critical findings are security problems.

Security and Compliance, at 48, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 7 points. Fixing the security flaws the scanner found comes next, worth about 4 points. Raising Security and Compliance to 70 would lift the score to about 65.

One password or key in the code and one in the code's history are open to anyone who can read the repository. One weakness in the code could be used by an attacker, and six errors are caught and ignored, so failures can go unnoticed. Replacing each exposed password or key, fixing the weaknesses the scanner points to and handling or logging the ignored errors would close these risks. The unsafe setting in infrastructure or container files needs changing to safe values. The 32 analysis rules switched off in the settings need switching back on in the settings file.

The product code is 96,176 lines, about €380,000 to rebuild.

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

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

If Security and Compliance rose from 48 to 70, the lowest score rated Strong, the score would rise from 57 to about 65.

Code composition: what the lines of code are
Business logic 12%Supporting code 20%Tests 65%Code analyzers 3%
New since the last survey: 210 findings

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

  • Cyclomatic Complexity · highlight.classifyCSharp (cyclomatic 76) site/lib/highlight.ts
  • Cyclomatic Complexity · highlight.contextualTypeRole (cyclomatic 45) site/lib/highlight.ts
  • Cyclomatic Complexity · RecurringCommandBackgroundService.ExecuteAsync (cyclomatic 30) src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs
  • Cyclomatic Complexity · highlight.classifyBash (cyclomatic 28) site/lib/highlight.ts
  • Cyclomatic Complexity · SingleStreamHandlerMediationEnumerable.MediateAsync (cyclomatic 27) src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs
  • Cyclomatic Complexity · highlight.positionalPropertyRole (cyclomatic 26) site/lib/highlight.ts
  • Cyclomatic Complexity · docs-article.DocsArticle (cyclomatic 24) site/components/docs-article.tsx
  • Cyclomatic Complexity · search-box.SearchBox (cyclomatic 24) site/components/search-box.tsx
  • Cyclomatic Complexity · highlight.findGenericEnd (cyclomatic 24) site/lib/highlight.ts
  • Cyclomatic Complexity · highlight.classifyGeneric (cyclomatic 22) site/lib/highlight.ts
  • Cyclomatic Complexity · highlight.findGenericOpen (cyclomatic 21) site/lib/highlight.ts
  • Cyclomatic Complexity · highlight.isUsingOrNamespaceChain (cyclomatic 20) site/lib/highlight.ts
  • Cyclomatic Complexity · highlight.classifyXml (cyclomatic 19) site/lib/highlight.ts
  • Cyclomatic Complexity · docs-drawer.DocsDrawer (cyclomatic 18) site/components/docs-drawer.tsx
  • Cyclomatic Complexity · PostgreSqlInboxStore.AddBatchAsync (cyclomatic 16) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs
  • Cyclomatic Complexity · PostgreSqlOutboxStore.AddBatchAsync (cyclomatic 16) src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs
  • Cognitive Complexity · highlight.classifyCSharp (cognitive 68) site/lib/highlight.ts
  • Cognitive Complexity · RecurringCommandBackgroundService.ExecuteAsync (cognitive 49) src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs
  • Cognitive Complexity · highlight.contextualTypeRole (cognitive 46) site/lib/highlight.ts
  • Cognitive Complexity · SingleStreamHandlerMediationEnumerable.MediateAsync (cognitive 38) src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs
  • Cognitive Complexity · highlight.findGenericEnd (cognitive 33) site/lib/highlight.ts
  • Cognitive Complexity · highlight.positionalPropertyRole (cognitive 32) site/lib/highlight.ts
  • Cognitive Complexity · DeclarationAnalysis.CollectDeclaringAttributes (cognitive 28) src/LiteBus.Analyzers/Analysis/DeclarationAnalysis.cs
  • Cognitive Complexity · highlight.isUsingOrNamespaceChain (cognitive 28) site/lib/highlight.ts
  • Cognitive Complexity · highlight.findGenericOpen (cognitive 27) site/lib/highlight.ts
  • Cognitive Complexity · highlight.classifyBash (cognitive 27) site/lib/highlight.ts
  • Cognitive Complexity · docs-article.DocsArticle (cognitive 26) site/components/docs-article.tsx
  • Cognitive Complexity · search-box.SearchBox (cognitive 24) site/components/search-box.tsx
  • Cognitive Complexity · KafkaConsumer.StopAsync (cognitive 22) src/LiteBus.Transport.Kafka/KafkaConsumer.cs
  • Cognitive Complexity · highlight.isInObjectCreation (cognitive 21) site/lib/highlight.ts
  • Cognitive Complexity · highlight.classifyXml (cognitive 20) site/lib/highlight.ts
  • Cognitive Complexity · PostgreSqlIdempotencyStore.TryClaimAsync (cognitive 19) src/LiteBus.Commands.Storage.PostgreSql/PostgreSqlIdempotencyStore.cs
  • Cognitive Complexity · TransportInboxIngressConsumer.AcceptAndAcknowledgeBatchAsync (cognitive 19) src/LiteBus.Inbox.Ingress/TransportInboxIngressConsumer.cs
  • Cognitive Complexity · SingleAsyncHandlerMediationStrategy.Mediate (cognitive 19) src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs
  • Cognitive Complexity · DiagnosticCheckRunner.RunAsync (cognitive 19) src/LiteBus.Runtime.Abstractions/Diagnostics/DiagnosticCheckRunner.cs
  • Cognitive Complexity · OrphanHandlerTagAnalyzer.GetHandlerTags (cognitive 18) src/LiteBus.Analyzers/OrphanHandlerTagAnalyzer.cs
  • Cognitive Complexity · RequiredDeclarationValidator.Validate (cognitive 18) src/LiteBus.Messaging/Registry/RequiredDeclarationValidator.cs
  • Cognitive Complexity · docs-article.classifyBlockquote (cognitive 18) site/components/docs-article.tsx
  • Cognitive Complexity · docs-drawer.DocsDrawer (cognitive 18) site/components/docs-drawer.tsx
  • Cognitive Complexity · highlight.classifyGeneric (cognitive 18) site/lib/highlight.ts
  • Cognitive Complexity · CommandHandlerAnalysis.MatchesAnyMarker (cognitive 17) src/LiteBus.Analyzers/Analysis/CommandHandlerAnalysis.cs
  • Cognitive Complexity · PostgreSqlSchemaManager.ValidateCoreAsync (cognitive 17) src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs
  • Cognitive Complexity · AmqpConsumer.StartCoreAsync (cognitive 17) src/LiteBus.Transport.Amqp/AmqpConsumer.cs
  • Cognitive Complexity · highlight.readTokenBackward (cognitive 16) site/lib/highlight.ts
  • Cognitive Complexity · highlight.isAttributePosition (cognitive 16) site/lib/highlight.ts
  • God Classes · FileTooLong: lib/highlight.ts site/lib/highlight.ts
  • God Classes · MethodTooLong: SingleStreamHandlerMediationEnumerable.MediateAsync src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs
  • God Classes · MethodTooLong: EfCoreOutboxStore.AddBatchAsync src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs
  • God Classes · FunctionTooLong: docs-article.DocsArticle site/components/docs-article.tsx
  • God Classes · FunctionTooLong: docs-drawer.DocsDrawer site/components/docs-drawer.tsx
  • God Classes · FunctionTooLong: home-stepper.HomeStepper REDACTED
  • God Classes · FunctionTooLong: search-box.SearchBox site/components/search-box.tsx
  • Code Duplication · Near-duplicate member pair (60 shared lines) src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs
  • Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/LiteBus.Commands.Recurring.Storage.PostgreSql/PostgreSqlRecurringLeaseSchemaScripts.cs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/LiteBus.Inbox.Ingress.Amqp/AmqpInboxIngressModule.cs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/LiteBus.Transport.AwsSqs/SqsPublisher.cs
  • Code Duplication · Duplicated block (83 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Duplicated block (72–74 lines × 2) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs
  • Code Duplication · Duplicated block (49–63 lines × 5) src/LiteBus.Commands.Recurring.Storage.PostgreSql/PostgreSqlRecurringLeaseSchemaScripts.cs
  • Code Duplication · Duplicated block (59 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs
  • Code Duplication · Duplicated block (41–46 lines × 2) src/LiteBus.Transport.Abstractions/TransportPublishRequest.cs
  • Code Duplication · Duplicated block (34 lines × 2) src/LiteBus.Inbox/InboxCleanupBackgroundService.cs
  • Code Duplication · Duplicated block (31–33 lines × 3) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs
  • Code Duplication · Duplicated block (29 lines × 2) src/LiteBus.Runtime.Extensions.Autofac.Hosting/AutofacDiagnosticHostingExtensions.cs
  • Code Duplication · Duplicated block (30 lines × 2) src/LiteBus.Outbox/OutboxEnvelopeFactory.cs
  • Code Duplication · Duplicated block (26–29 lines × 4) src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs
  • Code Duplication · Duplicated block (28 lines × 3) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs
  • Code Duplication · Duplicated block (17–29 lines × 2) src/LiteBus.Messaging/Pipeline/MessageContextExtensions.cs
  • Code Duplication · Duplicated block (24–27 lines × 3) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs
  • Code Duplication · Duplicated block (20–27 lines × 2) src/LiteBus.Inbox/InboxEnvelopeFactory.cs
  • Code Duplication · Duplicated block (25–26 lines × 2) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs
  • Code Duplication · Duplicated block (25 lines × 2) src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs
  • Code Duplication · Duplicated block (25 lines × 2) src/LiteBus.Runtime.Extensions.Autofac/ContainerBuilderExtensions.cs
  • Code Duplication · Duplicated block (23 lines × 2) src/LiteBus.Commands/CommandModule.cs
  • Code Duplication · Duplicated block (20 lines × 2) src/LiteBus.Commands/Idempotency/IdempotentCommandShortcut[TCommand, TCommandResult].cs
  • Code Duplication · Duplicated block (24 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Duplicated block (17 lines × 2) src/LiteBus.Inbox/InboxModule.cs
  • Code Duplication · Duplicated block (14 lines × 2) src/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs
  • Code Duplication · Duplicated block (23 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Duplicated block (21 lines × 3) src/LiteBus.Commands.Storage.Marten/MartenIdempotencyStore.cs
  • Code Duplication · Duplicated block (15 lines × 3) src/LiteBus.Commands/CommandModuleBuilder.cs
  • Code Duplication · Duplicated block (19 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs
  • Code Duplication · Duplicated block (19 lines × 3) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs
  • Code Duplication · Duplicated block (20 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Duplicated block (18–20 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs
  • Code Duplication · Duplicated block (19 lines × 2) src/LiteBus.Messaging.Abstractions/Contracts/MessageContractBuilder.cs
  • Code Duplication · Duplicated block (19 lines × 2) src/LiteBus.Commands.Storage.Marten/MartenIdempotencyStore.cs
  • Code Duplication · Duplicated block (18 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs
  • Code Duplication · Duplicated block (17 lines × 3) src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs
  • Code Duplication · Duplicated block (16 lines × 2) src/LiteBus.Analyzers/MissingCommandHandlerAnalyzer.cs
  • Code Duplication · Duplicated block (18 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Duplicated block (16 lines × 2) src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs
  • Code Duplication · Duplicated block (17 lines × 2) src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs
  • Code Duplication · Duplicated block (16 lines × 2) src/LiteBus.Outbox/OutboxWriterCore.cs
  • Code Duplication · Duplicated block (15 lines × 3) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs
  • Code Duplication · Duplicated block (15 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs

We compare 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: 229 findings

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

  • Cyclomatic Complexity · SingleStreamHandlerMediationStrategy.Mediate (cyclomatic 27) src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs
  • Cyclomatic Complexity · MessageDescriptor.AddDescriptor (cyclomatic 16) src/LiteBus.Messaging/Registry/Descriptors/MessageDescriptor.cs
  • Cognitive Complexity · SingleStreamHandlerMediationStrategy.Mediate (cognitive 47) src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs
  • Cognitive Complexity · TagReferenceAnalysis.CollectReferencedTags (cognitive 31) src/LiteBus.Analyzers/Analysis/TagReferenceAnalysis.cs
  • Cognitive Complexity · OrphanHandlerTagAnalyzer.Initialize (cognitive 22) src/LiteBus.Analyzers/OrphanHandlerTagAnalyzer.cs
  • Cognitive Complexity · page.highlight (cognitive 18) site/app/page.tsx
  • Cognitive Complexity · ContractRegistrationAnalysis.CollectRegisteredContractTypes (cognitive 16) src/LiteBus.Analyzers/Analysis/ContractRegistrationAnalysis.cs
  • Code Duplication · Near-duplicate member pair (59 shared lines) src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/LiteBus.Inbox.Ingress.Amqp/AmqpInboxIngressModule.cs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/LiteBus.Commands/CommandModule.cs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/LiteBus.Transport.AwsSqs/SqsConsumer.cs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/LiteBus.Transport.AwsSqs/SqsPublisher.cs
  • Code Duplication · Duplicated block (49–65 lines × 3) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxSchemaScripts.cs
  • Code Duplication · Duplicated block (53 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs
  • Code Duplication · Duplicated block (47 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Duplicated block (41 lines × 3) src/LiteBus.Transport.AwsSqs/SqsConsumer.cs
  • Code Duplication · Duplicated block (39 lines × 2) src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStorageModule.cs
  • Code Duplication · Duplicated block (10–36 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStorageModule.cs
  • Code Duplication · Duplicated block (34 lines × 2) src/LiteBus.Inbox/InboxCleanupBackgroundService.cs
  • Code Duplication · Duplicated block (24 lines × 2) src/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs
  • Code Duplication · Duplicated block (28 lines × 2) src/LiteBus.Transport.Abstractions/TransportPublishRequest.cs
  • Code Duplication · Duplicated block (23–30 lines × 2) src/LiteBus.Inbox/InboxEnvelopeFactory.cs
  • Code Duplication · Duplicated block (24–27 lines × 4) src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs
  • Code Duplication · Duplicated block (26 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs
  • Code Duplication · Duplicated block (25–26 lines × 3) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs
  • Code Duplication · Duplicated block (23 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs
  • Code Duplication · Duplicated block (20 lines × 2) src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs
  • Code Duplication · Duplicated block (23–24 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Duplicated block (17 lines × 2) src/LiteBus.Inbox/InboxModule.cs
  • Code Duplication · Duplicated block (20 lines × 2) src/LiteBus.Transport.AwsSqs/SqsConsumer.cs
  • Code Duplication · Duplicated block (20 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Duplicated block (19 lines × 2) src/LiteBus.Messaging.Abstractions/Contracts/MessageContractBuilder.cs
  • Code Duplication · Duplicated block (18 lines × 2) src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs
  • Code Duplication · Duplicated block (19 lines × 2) src/LiteBus.Runtime.Extensions.Autofac/ContainerBuilderExtensions.cs
  • Code Duplication · Duplicated block (18 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs
  • Code Duplication · Duplicated block (15 lines × 3) src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs
  • Code Duplication · Duplicated block (15 lines × 2) src/LiteBus.Outbox/OutboxEnvelopeFactory.cs
  • Code Duplication · Duplicated block (15 lines × 4) src/LiteBus.Commands/CommandModule.cs
  • Code Duplication · Duplicated block (15 lines × 3) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Duplicated block (12 lines × 2) src/LiteBus.Analyzers/Analysis/MessageAnalysis.cs
  • Code Duplication · Duplicated block (12 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs
  • Code Duplication · Duplicated block (8 lines × 2) src/LiteBus.Analyzers/Analysis/ContractRegistrationAnalysis.cs
  • Code Duplication · Duplicated block (9 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs
  • Code Duplication · Duplicated block (8 lines × 3) src/LiteBus.Analyzers/Analysis/HandlerAnalysis.cs
  • Code Duplication · Duplicated block (8 lines × 3) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxSchemaScripts.cs
  • Code Duplication · Duplicated block (8 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs
  • Code Duplication · Duplicated block (5 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs
  • Code Duplication · Duplicated block (5 lines × 2) src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs
  • Code Duplication · Duplicated block (8 lines × 2) src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaStore.cs
  • Code Duplication · Duplicated block (5 lines × 3) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs
  • Code Duplication · Duplicated block (5 lines × 3) src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs
  • Code Duplication · Duplicated block (5 lines × 4) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs
  • Code Duplication · Duplicated block (111 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStorageModule.cs
  • Code Duplication · Duplicated block (16 lines × 2) src/LiteBus.Inbox/InboxPayloadProtector.cs
  • Code Duplication · Duplicated block (10 lines × 2) src/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs
  • Code Duplication · Duplicated block (10 lines × 2) src/LiteBus.Inbox/InboxModule.cs
  • Code Duplication · Duplicated block (12 lines × 2) src/LiteBus.Inbox/InboxProcessorFactory.cs
  • Test Quality · No assertions: UnknownContract_ShouldDiscardWithoutStoreWrite tests/LiteBus.Durable.IntegrationTests/Ingress/InMemory/InMemoryIngressFailureIntegrationTests.cs
  • Test Quality · No assertions: InvalidJson_ShouldDiscardWithoutStoreWrite tests/LiteBus.Durable.IntegrationTests/Ingress/InMemory/InMemoryIngressFailureIntegrationTests.cs
  • Test Quality · No assertions: EnsureAsync_ShouldCreateSchemaAndBeIdempotent tests/LiteBus.Storage.IntegrationTests/PostgreSql/PostgreSqlInboxSchemaTests.cs
  • Test Quality · No assertions: EnsureAsync_ShouldHandleConcurrentBootstrap tests/LiteBus.Storage.IntegrationTests/PostgreSql/PostgreSqlInboxSchemaTests.cs
  • Test Quality · No assertions: EnsureAsync_ShouldCreateSchemaAndBeIdempotent tests/LiteBus.Storage.IntegrationTests/PostgreSql/PostgreSqlOutboxSchemaTests.cs
  • Test Quality · No assertions: EnsureAsync_ShouldHandleConcurrentBootstrap tests/LiteBus.Storage.IntegrationTests/PostgreSql/PostgreSqlOutboxSchemaTests.cs
  • Test Quality · No assertions: SchemaInitializer_SecondRun_ShouldRemainIdempotent tests/LiteBus.Storage.IntegrationTests/PostgreSql/PostgreSqlSchemaHostingTests.cs
  • Test Quality · Races the wall clock: ProcessPendingAsync_WhenShutdownBeginsAfterAmqpPublish_ShouldApplyTerminalPersistPolicy tests/LiteBus.Durable.IntegrationTests/Dispatch/Outbox/Amqp/AmqpOutboxDispatchIntegrationTests.cs
  • Churn × Complexity Hotspots · Hotspot: src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationStrategy[TMessage, TMessageResult].cs
  • Churn × Complexity Hotspots · Hotspot: src/LiteBus.Analyzers/CommandWithResultScheduledToInboxAnalyzer.cs src/LiteBus.Analyzers/CommandWithResultScheduledToInboxAnalyzer.cs
  • Churn × Complexity Hotspots · Hotspot: src/LiteBus.Analyzers/Analysis/TagReferenceAnalysis.cs src/LiteBus.Analyzers/Analysis/TagReferenceAnalysis.cs
  • Churn × Complexity Hotspots · Hotspot: src/LiteBus.Messaging/Processing/ProcessorBackgroundService[TProcessor].cs src/LiteBus.Messaging/Processing/ProcessorBackgroundService[TProcessor].cs
  • Explicit Debt · WriteOnlyPrivateField src/LiteBus.Saga/SagaProcessorHook.cs
  • Explicit Debt · AnalyzerSeverityNone tests/.editorconfig
  • Explicit Debt · AnalyzerSeverityNone tests/.editorconfig
  • Explicit Debt · AnalyzerSeverityNone tests/.editorconfig
  • Explicit Debt · AnalyzerSeverityNone tests/.editorconfig
  • Explicit Debt · AnalyzerSeverityNone tests/.editorconfig
  • Explicit Debt · AnalyzerSeverityNone tests/.editorconfig
  • Explicit Debt · Dead code: GetImplementedHandlerInterfaces src/LiteBus.Analyzers/Analysis/LiteBusSymbols.cs
  • Explicit Debt · Dead code: ICommandValidator src/LiteBus.Commands.Abstractions/ICommandValidator[TCommand].cs
  • Explicit Debt · Dead code: UseConnectionString src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxModuleBuilder.cs
  • Explicit Debt · Dead code: IAsyncMessageErrorHandler src/LiteBus.Messaging.Abstractions/Handler/Error/IAsyncMessageErrorHandler[TMessage].cs
  • Explicit Debt · Dead code: DeclaredTypeMessageContractResolver src/LiteBus.Messaging/Contracts/DeclaredTypeMessageContractResolver.cs
  • Explicit Debt · Dead code: UseConnectionString src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxModuleBuilder.cs
  • Explicit Debt · Dead code: IQueryValidator src/LiteBus.Queries.Abstractions/IQueryValidator[TQuery].cs
  • Explicit Debt · Dead code: UseConnectionString src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaModuleBuilder.cs
  • Explicit Debt · Dead code: GetOutboxProcessorHostedService tests/LiteBus.Outbox.UnitTests/OutboxTestInfrastructure.cs
  • Solution Shape · Build failed
  • Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/build-and-test.yml
  • Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/build-and-test.yml
  • Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/build-and-test.yml
  • Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/build-and-test.yml
  • Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/build-and-test.yml
  • Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/build-and-test.yml
  • Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action .github/workflows/build-and-test.yml
  • Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/manual-test-and-coverage.yml
  • Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/manual-test-and-coverage.yml
  • Static Analysis (SAST) · High: github-actions-mutable-action-tag .github/workflows/manual-test-and-coverage.yml
  • Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action .github/workflows/manual-test-and-coverage.yml
  • Static Analysis (SAST) · High: github-actions-mutable-action-tag REDACTED
Rebuild cost: about €380,000 · Estimate
Cost to rebuild€130,000 to €640,000, for 2,100 to 6,733 hours of work, about 2.6 person-years for 1 to 5 engineers
Difficulty of the problemVery high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 57. 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.
SizeMedium: 96,176 lines of product code
Comment linesThe estimate prices 61,300 lines. Comment lines count towards the size of 96,176 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price 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
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault.
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 7 points · Medium effort · Data Protection
2
Resolve the 27 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (27).
Raises the score by about 4 points · Medium effort · Static Analysis (SAST)
3
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 2 points · Low effort · Secret Scanning

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 €380,000 to build again, about 2.6 person-years of work. Its weakest lens is Security and Compliance, at 48 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch LiteBus LiteBus LiteBus.Commands Commands LiteBus->LiteBus.Commands LiteBus.Commands.Abstractions Abstractions LiteBus->LiteBus.Commands.Abstractions LiteBus.DurableMessaging.Abstractions Abstractions LiteBus->LiteBus.DurableMessaging.Abstractions LiteBus.Events Events LiteBus->LiteBus.Events LiteBus.Inbox Inbox LiteBus->LiteBus.Inbox LiteBus.Inbox.Abstractions Abstractions LiteBus->LiteBus.Inbox.Abstractions LiteBus.Messaging Messaging LiteBus->LiteBus.Messaging LiteBus.Messaging.Abstractions Abstractions LiteBus->LiteBus.Messaging.Abstractions LiteBus.Outbox Outbox LiteBus->LiteBus.Outbox LiteBus.Outbox.Abstractions Abstractions LiteBus->LiteBus.Outbox.Abstractions LiteBus.Commands->LiteBus.Commands.Abstractions LiteBus.Commands->LiteBus.Messaging LiteBus.Runtime.Abstractions Abstractions LiteBus.Commands->LiteBus.Runtime.Abstractions LiteBus.Commands.Abstractions->LiteBus.Messaging.Abstractions LiteBus.DurableMessaging.Abstractions->LiteBus.Messaging.Abstractions LiteBus.DurableMessaging.Abstractions->LiteBus.Runtime.Abstractions LiteBus.Events->LiteBus.Messaging LiteBus.Events->LiteBus.Messaging.Abstractions LiteBus.Events->LiteBus.Runtime.Abstractions LiteBus.Inbox->LiteBus.DurableMessaging.Abstractions LiteBus.Inbox->LiteBus.Inbox.Abstractions LiteBus.Inbox->LiteBus.Messaging LiteBus.Inbox->LiteBus.Runtime.Abstractions LiteBus.Inbox.Abstractions->LiteBus.DurableMessaging.Abstractions LiteBus.Inbox.Abstractions->LiteBus.Messaging.Abstractions LiteBus.Inbox.Abstractions->LiteBus.Runtime.Abstractions LiteBus.Inbox.Dispatch Dispatch LiteBus.Inbox.Dispatch->LiteBus.Inbox.Abstractions LiteBus.Inbox.Dispatch->LiteBus.Messaging LiteBus.Inbox.Dispatch->LiteBus.Runtime.Abstractions LiteBus.Transport Transport LiteBus.Inbox.Dispatch->LiteBus.Transport LiteBus.Transport.Abstractions Abstractions LiteBus.Inbox.Dispatch->LiteBus.Transport.Abstractions LiteBus.Inbox.Dispatch.InProcess InProcess LiteBus.Inbox.Dispatch.InProcess->LiteBus.Commands LiteBus.Inbox.Dispatch.InProcess->LiteBus.Commands.Abstractions LiteBus.Inbox.Dispatch.InProcess->LiteBus.Inbox LiteBus.Inbox.Dispatch.InProcess->LiteBus.Inbox.Abstractions LiteBus.Inbox.Dispatch.InProcess->LiteBus.Messaging LiteBus.Inbox.Dispatch.InProcess->LiteBus.Runtime.Abstractions LiteBus.Inbox.Ingress Ingress LiteBus.Inbox.Ingress->LiteBus.Inbox.Abstractions LiteBus.Inbox.Ingress->LiteBus.Messaging.Abstractions LiteBus.Inbox.Ingress->LiteBus.Runtime.Abstractions LiteBus.Inbox.Ingress->LiteBus.Transport LiteBus.Inbox.Ingress->LiteBus.Transport.Abstractions LiteBus.Messaging->LiteBus.DurableMessaging.Abstractions LiteBus.Messaging->LiteBus.Messaging.Abstractions LiteBus.Messaging->LiteBus.Runtime.Abstractions LiteBus.Messaging.Abstractions->LiteBus.Runtime.Abstractions LiteBus.Outbox->LiteBus.DurableMessaging.Abstractions LiteBus.Outbox->LiteBus.Messaging LiteBus.Outbox->LiteBus.Outbox.Abstractions LiteBus.Outbox->LiteBus.Runtime.Abstractions LiteBus.Outbox.Abstractions->LiteBus.DurableMessaging.Abstractions LiteBus.Outbox.Abstractions->LiteBus.Messaging.Abstractions LiteBus.Outbox.Abstractions->LiteBus.Runtime.Abstractions LiteBus.Outbox.Dispatch Dispatch LiteBus.Outbox.Dispatch->LiteBus.Messaging LiteBus.Outbox.Dispatch->LiteBus.Outbox.Abstractions LiteBus.Outbox.Dispatch->LiteBus.Runtime.Abstractions LiteBus.Outbox.Dispatch->LiteBus.Transport LiteBus.Outbox.Dispatch->LiteBus.Transport.Abstractions LiteBus.Testing.DurableMessaging DurableMessaging LiteBus.Testing.DurableMessaging->LiteBus.Inbox LiteBus.Testing.DurableMessaging->LiteBus.Inbox.Abstractions LiteBus.Testing.DurableMessaging->LiteBus.Messaging LiteBus.Testing.DurableMessaging->LiteBus.Outbox LiteBus.Testing.DurableMessaging->LiteBus.Outbox.Abstractions LiteBus.Testing.DurableMessaging->LiteBus.Runtime.Abstractions LiteBus.Transport->LiteBus.Runtime.Abstractions LiteBus.Transport->LiteBus.Transport.Abstractions LiteBus.Transport.IntegrationTesting IntegrationTesting LiteBus.Transport.IntegrationTesting->LiteBus.Inbox LiteBus.Transport.IntegrationTesting->LiteBus.Inbox.Abstractions LiteBus.Transport.IntegrationTesting->LiteBus.Inbox.Dispatch.InProcess LiteBus.Transport.IntegrationTesting->LiteBus.Messaging LiteBus.Transport.IntegrationTesting->LiteBus.Outbox LiteBus.Transport.IntegrationTesting->LiteBus.Outbox.Abstractions LiteBus.Transport.IntegrationTesting->LiteBus.Runtime.Abstractions LiteBus.Transport.IntegrationTesting->LiteBus.Transport.Abstractions __more__ +69 more projects

Architecture: which parts of the code depend on which

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

127 modules, with 258 dependencies between them. 2 loops run through 5 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Messaging.Abstractions2 Messaging.Abstractions.DurableMessaging3 Transport.Abstractions4 Commands.Abstractions5 Events.Abstractions6 Messaging.Abstractions.Processing7 Messaging.Registry.Descriptors8 Runtime.Abstractions.Hosting9 Storage.PostgreSql10 Runtime.Abstractions.Diagnostics11 Runtime.Abstractions12 Commands13 Inbox.Abstractions14 Messaging.Processing15 Messaging.Registry16 Outbox.Abstractions17 Runtime.Modules18 Saga19 Transport20 Commands.Recurring21 Commands.Storage.PostgreSql22 Extensions.AspNetCore23 Inbox24 Inbox.Dispatch25 Inbox.Dispatch.InProcess26 Inbox.Ingress27 Inbox.Storage.EntityFrameworkCore28 Inbox.Storage.InMemory29 Inbox.Storage.PostgreSql30 Messaging31 Outbox32 Outbox.Dispatch33 Outbox.Dispatch.InProcess34 Outbox.Storage.EntityFrameworkCore35 Outbox.Storage.InMemory36 Outbox.Storage.PostgreSql37 Saga.Storage.PostgreSql38 Transport.Amqp39 Commands.Recurring.Storage.PostgreSql40 Inbox.Ingress.Amqp
1 Messaging.Abstractions
2 Messaging.Abstractions.DurableMessaging
3 Transport.Abstractions
4 Commands.Abstractions13
5 Events.Abstractions10
6 Messaging.Abstractions.Processing2
7 Messaging.Registry.Descriptors221
8 Runtime.Abstractions.Hosting11
9 Storage.PostgreSql2
10 Runtime.Abstractions.Diagnostics1
11 Runtime.Abstractions1
12 Commands1057
13 Inbox.Abstractions611634
14 Messaging.Processing591
15 Messaging.Registry2611
16 Outbox.Abstractions711733
17 Runtime.Modules15
18 Saga325
19 Transport32
20 Commands.Recurring251
21 Commands.Storage.PostgreSql26251
22 Extensions.AspNetCore431288
23 Inbox1017311537
24 Inbox.Dispatch2226
25 Inbox.Dispatch.InProcess2125
26 Inbox.Ingress25513
27 Inbox.Storage.EntityFrameworkCore31222
28 Inbox.Storage.InMemory131213
29 Inbox.Storage.PostgreSql1393418
30 Messaging64671
31 Outbox1517311756
32 Outbox.Dispatch23126
33 Outbox.Dispatch.InProcess2325
34 Outbox.Storage.EntityFrameworkCore31226
35 Outbox.Storage.InMemory131214
36 Outbox.Storage.PostgreSql1393421
37 Saga.Storage.PostgreSql1631
38 Transport.Amqp5233
39 Commands.Recurring.Storage.PostgreSql72413
40 Inbox.Ingress.Amqp212341
Uses a module listed above itPart of a loopThe module itself
1 Messaging.Abstractions2 Messaging.Abstractions.DurableMessaging3 Transport.Abstractions4 Commands.Abstractions5 Events.Abstractions6 Messaging.Abstractions.Processing7 Messaging.Registry.Descriptors8 Runtime.Abstractions.Hosting9 Storage.PostgreSql10 Runtime.Abstractions.Diagnostics11 Runtime.Abstractions12 Commands13 Inbox.Abstractions14 Messaging.Processing15 Messaging.Registry16 Outbox.Abstractions17 Runtime.Modules18 Saga19 Transport20 Commands.Recurring21 Commands.Storage.PostgreSql22 Extensions.AspNetCore23 Inbox24 Inbox.Dispatch25 Inbox.Dispatch.InProcess26 Inbox.Ingress27 Inbox.Storage.EntityFrameworkCore28 Inbox.Storage.InMemory29 Inbox.Storage.PostgreSql30 Messaging31 Outbox32 Outbox.Dispatch33 Outbox.Dispatch.InProcess34 Outbox.Storage.EntityFrameworkCore35 Outbox.Storage.InMemory36 Outbox.Storage.PostgreSql37 Saga.Storage.PostgreSql38 Transport.Amqp39 Commands.Recurring.Storage.PostgreSql40 Inbox.Ingress.AmqpMessaging.Abstractions1Messaging.Abstractions.DurableMessaging2Transport.Abstractions3Commands.Abstractions4Events.Abstractions5Messaging.Abstractions.Processing6Messaging.Registry.Descriptors7Runtime.Abstractions.Hosting8Storage.PostgreSql9Runtime.Abstractions.Diagnostics10Runtime.Abstractions11Commands12Inbox.Abstractions13Messaging.Processing14Messaging.Registry15Outbox.Abstractions16Runtime.Modules17Saga18Transport19Commands.Recurring20Commands.Storage.PostgreSql21Extensions.AspNetCore22Inbox23Inbox.Dispatch24Inbox.Dispatch.InProcess25Inbox.Ingress26Inbox.Storage.EntityFrameworkCore27Inbox.Storage.InMemory28Inbox.Storage.PostgreSql29Messaging30Outbox31Outbox.Dispatch32Outbox.Dispatch.InProcess33Outbox.Storage.EntityFrameworkCore34Outbox.Storage.InMemory35Outbox.Storage.PostgreSql36Saga.Storage.PostgreSql37Transport.Amqp38Commands.Recurring.Storage.PostgreSql39Inbox.Ingress.Amqp40131022211121110576116345912611711733153253225126251431288101731153722262125255133122213121313934186467115173117562312623253122613121413934211631523372413212341+87 more modules (most-connected shown)

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

At a glance — Architecture · 81% · Strong ·

At a glance — Maturity · 82% · Strong ·

At a glance — Readiness · 61% · Adequate ·

At a glance — Security · 48% · Weak · gated by D29, D36, C1 ·

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

At a glance — Accessibility · 66% · Adequate ·

At a glance — Performance · 75% · Strong ·

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 — Injection31High / Critical
A03:2025 — Software Supply Chain Failures7Medium
A02:2025 — Security Misconfiguration3High / Critical
A07:2025 — Authentication Failures2High / Critical

Roadmap

Top priorities: 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.); Resolve the 27 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (27); Resolve the 66 Deprecated finding(s) in Dependency Hygiene — start with packages.lock.json (66).

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

Do thisHelpsEffortDimension
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.).+7.4 ptsMediumData Protection
Resolve the 27 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (27).+4.1 ptsMediumStatic Analysis (SAST)
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+2.0 ptsLowSecret Scanning
Resolve the 2 Banned license finding(s) in License Compliance — start with Directory.Packages.props.+1.9 ptsLowLicense Compliance
Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with LiteBus.Analyzers.csproj, LiteBus.Runtime.UnitTests.csproj, Directory.Build.props.+1.2 ptsLowExplicit Debt
Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with KafkaTransportTestInfrastructure.cs (3), KafkaIngressTestSupport.cs (2), REDACTED.+1.2 ptsLowExplicit Debt
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED.+1.1 ptsLowSecrets (history)
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.+1.1 ptsLowStatic Analysis (SAST)

File quality

Per-file score 0–10 — a quality signature. Of 197 files carrying findings, judged against the Production bar: 2% slop · 22% mixed · 76% near-clean.

FileScoreBandWorst signal
tests/LiteBus.Transport.IntegrationTesting/Kafka/KafkaTransportTestInfrastructure.cs3.1SlopExplicit Debt: EmptyCatchBlock
REDACTED3.3SlopStatic Analysis (SAST): High: REDACTED
tests/LiteBus.Transport.IntegrationTesting/Kafka/KafkaIngressTestSupport.cs3.7SlopExplicit Debt: EmptyCatchBlock
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
tests/Directory.Packages.props5.0MixedLicense Compliance: Banned license: MySql.EntityFrameworkCore
src/.editorconfig5.2MixedExplicit Debt: AnalyzerSeverityNone
tests/.editorconfig5.2MixedExplicit Debt: AnalyzerSeverityNone
src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs6.0MixedExplicit Debt: BarePragmaDisable
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
tests/LiteBus.Inbox.UnitTests/InboxTestInfrastructure.cs6.9MixedExplicit Debt: Dead code: CreateProcessingStore
site/lib/highlight.ts7.0MixedCyclomatic Complexity: highlight.classifyCSharp (cyclomatic 76)
src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs7.0MixedCyclomatic Complexity: EfCoreOutboxStore.AddBatchAsync (cyclomatic 28)
src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs7.0MixedCyclomatic Complexity: EfCoreInboxStore.AddBatchAsync (cyclomatic 21)
src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs7.0MixedCyclomatic Complexity: PostgreSqlInboxStore.AddBatchAsync (cyclomatic 16)
src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs7.0MixedGod Classes: TooManyMethods: InMemoryInboxStore
src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs7.0MixedCode Duplication: Members sharing a duplicated core (5 members, 50+ identical tokens)
src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs7.1MixedCyclomatic Complexity: PostgreSqlOutboxStore.AddBatchAsync (cyclomatic 16)
src/LiteBus.Inbox/InboxProcessorControl.cs7.1MixedCode Duplication: Duplicated block (40 lines × 2)

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

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

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

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

Could not be resolved — 7

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

This survey 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. All 93 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 93 dimensions across the health lenses
D1D2D3D4D5D6D7D8D9D10D11D12D13D14D15D17D18D19D20D24D26D27D28D29D30D31D34D35D36D37D39D43D44AC2AC3AC5AC6AC7AX1AX10AX2AX3AX5AX6AX8AX9C1C2C3C4C5ED1ED2ED4GD1IC1M1M2M3M4P1P2P3P4P5P6PF1PF3X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 603 of 696 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 or a scanner, 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
Canine Code Analyzer 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

Every finding is locatable in findings.md. Run 01a1bbcd-03b5-7baf-a9b4-ea585cacf26f.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. At least one `dotnet test` target was stopped at its time budget, so the gathered reports cover only part of the suite. The overall 87.5% is a FLOOR (everything the completed runs covered really is covered), but a per-file figure from a partial gather cannot tell an untested file from one whose test project never ran — so per-file and CRAP rows are withheld rather than published as measurements. You can widen what we reach: optional: commit the Cobertura/OpenCover/lcov report your CI already produces, and per-file rows can be read without a re-run.
  • D11 Test Reliability — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. Test reliability is scored on the 2 tier(s) that produced comparable repeat runs; 1 tier(s) did not, and are excluded from the measurement rather than counted (unit: measured (0 flaky); integration: not included — too large to re-run within its budget; other: measured (0 flaky)). This is OUR limitation, not a defect in the repository.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 613 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 3 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D21 Naming Consistency — not measured this run — We 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (91,288 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We 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. `site/lib/source.ts`, `src/LiteBus.Commands.Abstractions/ICommand.cs`, `src/LiteBus.Commands.Abstractions/ICommandCompletionHandler.cs`, `src/LiteBus.Commands.Abstractions/ICommandCompletionHandler[TCommand, TCommandResult].cs`, `src/LiteBus.Commands.Abstractions/ICommandCompletionHandler[TCommand].cs`, … (+71 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AXB2 Runtime readiness — not measured this run — We 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • AXR1 Runtime accessibility — not measured this run — We 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 DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • ED5 Idempotency — not measured this run — We 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. Idempotency could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: Syntax node is not within syntax tree.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P10 Library API & versioning — not measured this run — We 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. Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P11 BDD / executable specs — not measured this run — We 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. BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P7 Outbound HTTP resilience — not measured this run — We 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. Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P8 Schema migrations — not measured this run — We 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. Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').

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

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do 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.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our 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 — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • 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 REDACTED (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.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
  • 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.
  • C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.8 / 10Adequate✓ 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 6.8 / 10 · rule-coverage 100% · ceiling Prevented

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

highlight.classifyCSharp (cyclomatic 76)site/lib/highlight.ts:617
highlight.contextualTypeRole (cyclomatic 45)site/lib/highlight.ts:753
RecurringCommandBackgroundService.ExecuteAsync (cyclomatic 30)src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs:96
EfCoreOutboxStore.AddBatchAsync (cyclomatic 28)src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:578
highlight.classifyBash (cyclomatic 28)site/lib/highlight.ts:923

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

What to do

  1. Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with highlight.classifyCSharp (cyclomatic 76), highlight.contextualTypeRole (cyclomatic 45). — 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 2 together lifts Cyclomatic Complexity from 6.8 to about 7.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  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 Complexity6.4 / 10Adequate✓ 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 6.4 / 10 · rule-coverage 100% · ceiling Prevented

39 method(s) exceeded the cognitive complexity threshold of 15; the worst was EfCoreOutboxStore.AddBatchAsync at 69.

EfCoreOutboxStore.AddBatchAsync (cognitive 69)src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:578
highlight.classifyCSharp (cognitive 68)site/lib/highlight.ts:617
RecurringCommandBackgroundService.ExecuteAsync (cognitive 49)src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs:96
highlight.contextualTypeRole (cognitive 46)site/lib/highlight.ts:753
EfCoreInboxStore.AddBatchAsync (cognitive 38)src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:530

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

What to do

  1. Bring the 9 bodies over 30 down to 30 or less in Cognitive Complexity — start with EfCoreOutboxStore.AddBatchAsync (cognitive 69), highlight.classifyCSharp (cognitive 68), RecurringCommandBackgroundService.ExecuteAsync (cognitive 49). — 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 9 together lifts Cognitive Complexity from 6.4 to about 7.3/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.2 / 10Stronggated by 21 serious findings✓ Tool-verified

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

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

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

21 god class(es) detected.

TooManyMethods: EfCoreOutboxStore · ×7src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs
FunctionTooLong: page.HomePage · ×6site/app/page.tsx:286
FileTooLong: LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs · ×5src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs
MethodTooLong: SingleStreamHandlerMediationEnumerable.MediateAsync · ×3src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:108

What to do

  1. Resolve the 7 TooManyMethods finding(s) in God Classes — start with EfCoreOutboxStore.cs, EfCoreInboxStore.cs, PostgreSqlOutboxStore.cs. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 6 FunctionTooLong finding(s) in God Classes — start with page.tsx (2), docs-article.tsx, docs-drawer.tsx. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 5 FileTooLong finding(s) in God Classes — start with EfCoreOutboxStore.cs, EfCoreInboxStore.cs, highlight.ts. — One of this dimension's main actionable groups (5 warning-level).
  4. 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.2 / 10Stronggated by 166 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.2 / 10 · rule-coverage 100% · ceiling Verified

158 duplicated block group(s) detected. A further 8 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (19 lines × 2) · ×8src/LiteBus.Inbox/InboxProcessorTelemetry.cs:63
Duplicated block (13 lines × 2) · ×8src/LiteBus.Inbox.Dispatch.InProcess/CommandInboxDispatcher.cs:77
Duplicated block (11 lines × 2) · ×8src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:240
Duplicated block (8 lines × 2) · ×7src/LiteBus.Messaging/Registry/Builders/PostHandlerDescriptorBuilder.cs:30
Duplicated block (16 lines × 2) · ×6src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:273

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

What to do

  1. Resolve the 8 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with InMemoryInboxStore.cs (2), InboxProcessorTelemetry.cs, InboxEntityFrameworkCoreModelExtensions.cs. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 8 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with EfCoreInboxStore.cs (2), CommandInboxDispatcher.cs, PostgreSqlInboxStore.cs. — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 8 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with PostgreSqlInboxStore.cs (2), InMemoryInboxStore.cs, InMemoryOutboxStore.cs. — One of this dimension's main actionable groups (8 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

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

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

Off the main sequence: LiteBus.Inbox · ×6src/LiteBus.Inbox/LiteBus.Inbox.csproj:1
Unstable project LiteBus.Inbox.Dispatch.InProcesssrc/LiteBus.Inbox.Dispatch.InProcess/LiteBus.Inbox.Dispatch.InProcess.csproj:1
Unstable project LiteBus.Inbox.Ingress.Kafkasrc/LiteBus.Inbox.Ingress.Kafka/LiteBus.Inbox.Ingress.Kafka.csproj:1
Unstable project LiteBus.Outbox.Dispatch.InProcesssrc/LiteBus.Outbox.Dispatch.InProcess/LiteBus.Outbox.Dispatch.InProcess.csproj:1

What to do

  1. Resolve the 6 Off the main sequence finding(s) in Coupling — start with LiteBus.Inbox.csproj, LiteBus.Messaging.csproj, LiteBus.Outbox.csproj. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 1 Unstable project LiteBus.Inbox.Dispatch.InProcess finding(s) in Coupling — start with LiteBus.Inbox.Dispatch.InProcess.csproj. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project LiteBus.Inbox.Ingress.Kafka finding(s) in Coupling — start with LiteBus.Inbox.Ingress.Kafka.csproj. — One of this dimension's main actionable groups (1 warning-level).
  4. 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)9.8 / 10Stronggated by 3 serious findings✓ Tool-verified

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

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

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

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

3 of 149 classes have LCOM4 above 3.

Low cohesion: MessageModuleBuilder (LCOM4 13) · ×3src/LiteBus.Messaging/MessageModuleBuilder.cs:17

What to do

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

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

D7 · Architectural Integrity6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.

What to do

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

Detailed fixes: d7_recommendation.md.

D8 · Code Coverage10.0 / 10Stronggated by 3 serious findings✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

Line coverage 87.5%.

No test project references LiteBus.ConsumerSmokesmoke/LiteBus.ConsumerSmoke/LiteBus.ConsumerSmoke.csproj
No test project references LiteBus.Messaging.Extensions.OpenTelemetrysrc/LiteBus.Messaging.Extensions.OpenTelemetry/LiteBus.Messaging.Extensions.OpenTelemetry.csproj
No test project references LiteBus.Transport.Amqp.Extensions.OpenTelemetrysrc/LiteBus.Transport.Amqp.Extensions.OpenTelemetry/LiteBus.Transport.Amqp.Extensions.OpenTelemetry.csproj

What to do

  1. Resolve the 1 No test project references LiteBus.ConsumerSmoke finding(s) in Code Coverage — start with LiteBus.ConsumerSmoke.csproj. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 No test project references LiteBus.Messaging.Extensions.OpenTelemetry finding(s) in Code Coverage — start with LiteBus.Messaging.Extensions.OpenTelemetry.csproj. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 No test project references LiteBus.Transport.Amqp.Extensions.OpenTelemet… finding(s) in Code Coverage — start with LiteBus.Transport.Amqp.Extensions.OpenTelemetry.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

2072 test methods: 1956 unit, 116 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Stronggated by 7 serious findings✓ Tool-verified

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

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

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

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

No assertions: WaitForWorkOrDelayAsync_zero_interval_completes_immediately · ×6tests/LiteBus.Inbox.UnitTests/InboxPollingWorkSignalTests.cs:8
Fixed-sleep synchronisation: BatchAccept_WhenBufferFull_ShouldBlockUntilFlushCompletestests/LiteBus.Inbox.UnitTests/Ingress/TransportInboxIngressConsumerTests.cs:218

What to do

  1. Resolve the 6 No assertions finding(s) in Test Quality — start with InboxPollingWorkSignalTests.cs, TestMediatorDoubleTests.cs, ThrowingValidatorTests.cs. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with TransportInboxIngressConsumerTests.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. 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

Only 2 of 3 test tiers measured — the score covers those alone. 0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: not included — too large to re-run within its budget; other: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

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

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

9 outdated, 0 vulnerable, 2 deprecated, 1 prerelease packages. Those are the NuGet packages; this repository's npm dependencies were read too — 65 outdated of 232 package(s) across 1 lockfile(s).

Deprecated: Microsoft.CodeAnalysis.CSharp.Analyzer.Testing.XUnit · ×3tests/Directory.Packages.props:5
Prerelease dependency: StyleCop.Analyzers
Deprecated: Microsoft.CodeAnalysis.Testing.Verifiers.XUnit · ×66tests/LiteBus.Analyzers.UnitTests/packages.lock.json:140
Outdated (npm): nanoid
Outdated (npm): @cfworker/json-schema · ×64

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

What to do

  1. Resolve the 66 Deprecated finding(s) in Dependency Hygiene — start with packages.lock.json (66). — One of this dimension's main actionable groups (66 recommendation-level).
  2. Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2), package.json. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).

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

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

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

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

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

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce Secret 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 Compliance6.0 / 10Adequate✓ Tool-verified

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

2 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 52 direct `PackageReference`(s), and 201 further package(s) were reached beyond them by closing the graph over the committed `packages.lock.json` and 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

Banned license: MySql.EntityFrameworkCore · ×2tests/Directory.Packages.props:30

What to do

  1. Resolve the 2 Banned license finding(s) in License Compliance — start with Directory.Packages.props. — One of this dimension's main actionable groups (2 issue-level).
  2. Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 9 serious findings✓ 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

Top hotspots: src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs (9×28=252); src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs (5×30=150); src/LiteBus.Messaging/Registry/Descriptors/MessageDescriptor.cs (8×16=128)

Hotspot: src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs · ×9src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:578

What to do

  1. Resolve the 9 Hotspot finding(s) in Churn × Complexity Hotspots — start with EfCoreOutboxStore.cs, RecurringCommandBackgroundService.cs, MessageDescriptor.cs. — One of this dimension's main actionable groups (9 warning-level).

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

D17 · Explicit Debt8.9 / 10Adequategated by 41 critical findings✓ Tool-verified

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

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

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

43 deducted debt markers + 41 dead symbols across 91288 LoC in the .NET projects (0.6/KLoC) → score 8.9.

AnalyzerSeverityNone · ×32src/.editorconfig:15
EmptyCatchBlock · ×6REDACTED:121
NoWarnInCsproj · ×3src/LiteBus.Analyzers/LiteBus.Analyzers.csproj:25
Dead code: ProcessPaymentCommandValidator · ×41samples/LiteBus.Sample/Commands/ProcessPaymentCommandValidator.cs:22
BarePragmaDisable · ×2src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:264

What to do

  1. Resolve the 32 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (32). — One of this dimension's main actionable groups (32 issue-level).
  2. Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with KafkaTransportTestInfrastructure.cs (3), KafkaIngressTestSupport.cs (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
  3. Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with LiteBus.Analyzers.csproj, LiteBus.Runtime.UnitTests.csproj, Directory.Build.props. — 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

105 projects, 2029 source files, 193877 hand-written lines of code (90948 production / 102929 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), 526 inter-project edges.

Shell project: LiteBus.Events.Extensions.Autofac · ×3src/LiteBus.Events.Extensions.Autofac/LiteBus.Events.Extensions.Autofac.csproj

✓ On the Gold path — maintain.

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

2 of 2 documentation facets pass in full. 266 document(s) read across 86 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality10.0 / 10Exemplary○ Nothing flagged

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.md.

D24 · Comment Value9.5 9.5 / 10Exemplary✓ Tool-verified

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

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

3 of 619 judged comments only repeat the code they sit on (0.5 %). 3 comment(s) in another language or script were not judged.

redundant comment · ×3src/LiteBus.Messaging/Mediator/MessageMediator.cs:118
doc comments repeat the names · ×28src/LiteBus.Analyzers/Analysis/ContractRegistrationAnalysis.cs:16

✓ On the Gold path — maintain.

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

D26 · Project Cohesion9.8 / 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.

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

1 of 106 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionsrc/LiteBus.Messaging.Abstractions/LiteBus.Messaging.Abstractions.csproj:1

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.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

77 % of calls cross a namespace and 7 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.

Pass-through layer · ×5src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxWorkSignal.cs:13

What to do

  1. Resolve the 5 Pass-through layer finding(s) in Navigability — start with PostgreSqlInboxWorkSignal.cs, TransactionalOutboxAdapter[TContext].cs, PostgreSqlOutboxWorkSignal.cs. — One of this dimension's main actionable groups (5 recommendation-level).

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

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

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

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

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

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

REDACTED

What to do

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

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

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

31 finding(s): 0 critical, 1 high, 30 medium, 0 low. semgrep hit a parse error in 76 file(s) — `site/lib/source.ts` (line 52), `src/LiteBus.Commands.Abstractions/ICommand.cs` (line 11), `src/LiteBus.Commands.Abstractions/ICommandCompletionHandler.cs` (line 14), `src/LiteBus.Commands.Abstractions/ICommandCompletionHandler[TCommand, TCommandResult].cs` (lines 15–16), `src/LiteBus.Commands.Abstractions/ICommandCompletionHandler[TCommand].cs` (lines 14–15), … (+71 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 27 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (27). — One of this dimension's main actionable groups (27 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D30 · Dependency Vulnerabilities9.8 / 10Stronggated by 1 serious finding✓ 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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

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

REDACTED

What to do

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

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

D31 · IaC & Container Security9.5 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ 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 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/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. — One of this dimension's main actionable groups (1 recommendation-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.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

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

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

7 of 3654 first-party methods have an oversized IL body.

IL efficiency: 7 authored method(s) exceed the IL budgetsrc/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs:48

✓ 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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

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.

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 safety4.0 / 10Weak✓ Tool-verified

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.

  • `.search input[type="search"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — site/app/globals.css:257
  • `.explorer:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — site/app/docs/docs.css:10

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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-jsx-a11y) 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 21 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. — site/package.json:33

What to do

  • Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, 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 composition7.6 / 10Strong✓ Tool-verified

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

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

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

What to do

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

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

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

  • `BackgroundServiceHostedServiceIndex` is a singleton (one shared instance) but mutates instance state outside any lock (_backgroundServicesByImplementationType; e.g. `_backgroundServicesByImplementationType` at line 29). — src/LiteBus.Runtime.Extensions.Microsoft.Hosting/BackgroundServiceHostedServiceIndex.cs:12
  • `KafkaBrokerHost` is not registered, but `KafkaBrokerSharedLifecycle` creates it and keeps it in the static `_sharedHost`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (TransportOptions, IsAvailable, _container; e.g. `TransportOptions` at line 71). — tests/LiteBus.Transport.IntegrationTesting/Kafka/KafkaBrokerHost.cs:11

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 LiteBus.Runtime.Abstractions ↔ LiteBus.Runtime.Abstractions.Diagnostics ↔ LiteBus.Runtime.Abstractions.Hosting depend on each other. The lightest dependency in the cycle is LiteBus.Runtime.Abstractions → LiteBus.Runtime.Abstractions.Diagnostics (LiteBus.Runtime.Abstractions.IModuleConfiguration → LiteBus.Runtime.Abstractions.Diagnostics.DiagnosticCheckDescriptor, 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/LiteBus.Runtime.Abstractions/Modules/IModuleConfiguration.cs:3
  • The namespaces LiteBus.Messaging.Registry ↔ LiteBus.Messaging.Registry.Descriptors depend on each other. The lightest dependency in the cycle is LiteBus.Messaging.Registry → LiteBus.Messaging.Registry.Descriptors (LiteBus.Messaging.Registry.MessageRegistry → LiteBus.Messaging.Registry.Descriptors.MessageDescriptor, 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/LiteBus.Messaging/Registry/MessageRegistry.cs:10

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.
AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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

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

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

AX9 · CQS / query purity8.9 / 10Strong✓ Tool-verified

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

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

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

  • `PostgreSql.PostgreSqlInboxStore` is a read (query) handler but its body writes persistent state one call away, in PostgreSqlInboxStore.AddFilterParameters — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:35
  • `PostgreSql.PostgreSqlOutboxStore` is a read (query) handler but its body writes persistent state one call away, in PostgreSqlOutboxStore.AddFilterParameters — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:42

What to do

  • Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
C1 · Data Protection0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
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.

C3 · Audit Trail10.0 / 10Exemplary✓ Tool-verified

Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.

Method: Roslyn scan: audit-trail mechanism graded (SaveChanges interceptor/immutable AuditLog/[Audited] strong; bare IAuditable/AddAuditing weak). Deterministic.

C4 · Data Retention7.5 / 10Strong✓ Tool-verified

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

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

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

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
C5 · Data-Subject Rights4.0 / 10Weak✓ Tool-verified

Other · Security — Whether GDPR data-subject requests are supported in code — erasure, export/portability, consent.

Method: Roslyn scan: GDPR data-subject-rights corroboration (erasure/export/consent vocabulary co-occurring with subject-id store crossing or explicit GDPR pattern). Deterministic, gated by PII.

  • Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.

What to do

  • Implement data export/portability for a data subject (a machine-readable export of their personal data).
  • Track GDPR consent (lawful basis) alongside the personal data it authorises.
ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 89 of 91 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation7.0 / 10Strong✓ 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.

  • 1 ADR-shaped document(s) detected by content — `site/content/docs/architecture/decisions.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.

What to do

  • Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
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 accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

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

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling4.0 / 10Weak✓ Tool-verified

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

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

  • `benchmarks/Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — benchmarks/Directory.Packages.props:3

What to do

  • The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning.
  • 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.

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

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
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.

PF1 · Benchmark discipline9.5 / 10Exemplary✓ Tool-verified

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

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

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 each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • 3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×3) — benchmarks/LiteBus.Processor.Benchmarks/PipelinedInboxProcessorBenchmarks.cs:86, REDACTED:162, src/LiteBus.Transport.AzureServiceBus/AzureServiceBusPublisher.cs:63

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
X1 · Async correctness7.7 / 10Strong✓ Tool-verified

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

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

  • 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. — benchmarks/LiteBus.Processor.Benchmarks/PipelinedInboxProcessorBenchmarks.cs:76
  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. (×2) — REDACTED:162, src/LiteBus.Transport.AzureServiceBus/AzureServiceBusPublisher.cs:63
  • 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/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs:325

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

  • `TransportInboxIngressConsumer` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_batchFlushTimer` itself (line 61), which makes that instance its own. But `_batchFlushTimer` is named in none of the methods the disposal search covered: `Dispose` (line 204), `CancelBatchFlushTimer` (line 373) — 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` (`_batchFlushTimer?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/LiteBus.Inbox.Ingress/TransportInboxIngressConsumer.cs:61
  • `_dispatchScope` is never created by `MediationResourceScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 44). Its declared type `IMessageDispatchScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Messaging/Mediator/MediationResourceScope.cs:44
  • `_dispatchScope` is never created by `MediationResourceScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 58). Its declared type `IMessageDispatchScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Messaging/Mediator/MediationResourceScope.cs:58
  • `_source` is never created by `ScopeRetainedAsyncEnumerator` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 261). Its declared type `IAsyncEnumerator` is an interface, so the instance came from whoever chose and created 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/LiteBus.Messaging/Mediator/MediationScopeRetention.cs:261
  • `_scope` is never created by `AutofacMessageDispatchScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 66). Its declared type `ILifetimeScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Runtime.Extensions.Autofac/AutofacMessageDispatchScopeFactory.cs:66
  • `_scope` is never created by `AutofacMessageDispatchScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 72). Its declared type `ILifetimeScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Runtime.Extensions.Autofac/AutofacMessageDispatchScopeFactory.cs:72
  • `_scope` is never created by `MicrosoftMessageDispatchScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 60). Its declared type `IServiceScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Runtime.Extensions.Microsoft.DependencyInjection/MicrosoftMessageDispatchScopeFactory.cs:60
  • `_scope` is never created by `MicrosoftMessageDispatchScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 71). Its declared type `IServiceScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Runtime.Extensions.Microsoft.DependencyInjection/MicrosoftMessageDispatchScopeFactory.cs:71
  • `DataSource` is never created by `PostgreSqlDataSourceOwner` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 62). Its declared type `NpgsqlDataSource` is an abstract class, so the instance came from whoever chose and created 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/LiteBus.Storage.PostgreSql/PostgreSqlDataSourceOwner[TModule].cs:62
  • `admission` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 350). Every use of it in `CreateBoundedHandler` 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 admission = …;`), which releases it at the end of the scope on every path including a throw. — src/LiteBus.Transport.Amqp/AmqpConsumer.cs:350
  • `_consumer` is never created by `KafkaConsumer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 247). Its declared type `IConsumer` is an interface, so the instance came from whoever chose and created 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/LiteBus.Transport.Kafka/KafkaConsumer.cs:247
  • `admission` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 32). Every use of it in `CreateBoundedHandler` 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 admission = …;`), which releases it at the end of the scope on every path including a throw. — src/LiteBus.Transport/TransportConsumerHandlerInvoker.cs:32
  • `admission` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 63). Every use of it in `CreateBoundedOutcomeHandler` 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 admission = …;`), which releases it at the end of the scope on every path including a throw. — src/LiteBus.Transport/TransportConsumerHandlerInvoker.cs:63

What to do

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

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

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

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

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

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

  • Only 311/331 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. (×10) — benchmarks/LiteBus.Processor.Benchmarks/PipelinedInboxProcessorBenchmarks.cs:95, src/LiteBus.Commands.Recurring.Storage.PostgreSql/PostgreSqlRecurringCommandLease.cs:361, src/LiteBus.Inbox.Ingress/TransportInboxIngressConsumer.cs:356, …
  • 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. (×9) — src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:67, src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:394, src/LiteBus.Messaging.Abstractions/Handler/Main/IAsyncMessageHandler[TMessage, TMessageResult].cs:37, …
  • No CancellationToken parameter, and the token `executionContext.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `executionContext.CancellationToken` on, or take a CancellationToken. — src/LiteBus.Messaging/Pipeline/MessageContextExtensions.cs:563
  • 5 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
  • Holds a CancellationToken but hands `CancellationToken.None` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). (×5) — src/LiteBus.Commands/Idempotency/IdempotencyCompletionHandler.cs:87, src/LiteBus.Runtime.Abstractions/Diagnostics/DiagnosticCheckRunner.cs:198, src/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs:330, …

What to do

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

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

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

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

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

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

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

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

X3 · Exception handling7.6 / 10Strong✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). — REDACTED:121
  • `catch (ObjectDisposedException) 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. — REDACTED:252
  • `catch (Exception)` 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/LiteBus.Transport.AwsSqs/SqsVisibilityHeartbeat.cs:114
  • `catch (ObjectDisposedException)` 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/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs:232

What to do

  • Swallowed exception (empty catch)
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 logging1.2 / 10Critical✓ 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. (×19) — src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:46, src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:54, src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:80, …

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types9.7 / 10Exemplary✓ Tool-verified

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

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

  • ~0.4 `!` suppressions per 1k syntax nodes — 103 suppression(s) across the 249721 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

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

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 Health64%Adequate — gated by X4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture81%StrongSolid.
Maturity82%StrongSolid.
Readiness61%AdequateAcceptable, with room to improve.
Security48%Weak — gated by D29, D36, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven100%ExemplaryStrongest area.
Accessibility66%AdequateAcceptable, with room to improve.
Performance75%StrongSolid.
Unscored — 3 check(s) recorded observations but carry no score

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

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 29 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.
  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. 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
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
  • D22 Internal API Consistency — N/A — too few peer members to establish a convention across 32 exposed C# types.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
  • D32 Data Compliance (PII/GDPR) — 76 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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.
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (25 value object(s))
  • ED3 Event naming — no domain or integration events detected — event-naming check not applicable
  • ED5 Idempotency — Idempotency could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an event-store package (Marten/EventStore))
  • P10 Library API & versioning — Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P11 BDD / executable specs — BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P7 Outbound HTTP resilience — Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P8 Schema migrations — Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P9 Domain vs controller coverage — coverage data present for 41 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.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 — 51 finding(s)
D17 · Explicit Debt · AnalyzerSeverityNone · ×32
  • AnalyzerSeverityNone src/.editorconfig:15 — SA1633 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone tests/.editorconfig:12 — SA1633 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:16 — SA1634 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone tests/.editorconfig:13 — SA1634 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:17 — SA1635 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone tests/.editorconfig:14 — SA1635 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:18 — SA1636 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone tests/.editorconfig:15 — SA1636 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:19 — SA1637 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone tests/.editorconfig:16 — SA1637 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:20 — SA1638 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone tests/.editorconfig:17 — SA1638 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:28 — CA1062 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:34 — SA1649 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:39 — IDE0290 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:40 — IDE0007 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:44 — CA1710 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:47 — CA1716 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:50 — CA1716 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:55 — CA1716 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:61 — CA1716 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone tests/.editorconfig:33 — CA1716 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:58 — CA1711 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone src/.editorconfig:64 — CA1711 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone tests/.editorconfig:31 — CA1711 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • + 7 more in this group — see findings.md.
D17 · Explicit Debt · EmptyCatchBlock · ×6
  • EmptyCatchBlock REDACTED:121 — 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 tests/LiteBus.Transport.IntegrationTesting/Kafka/KafkaIngressTestSupport.cs:203 — 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 tests/LiteBus.Transport.IntegrationTesting/Kafka/KafkaIngressTestSupport.cs:293 — 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 tests/LiteBus.Transport.IntegrationTesting/Kafka/KafkaTransportTestInfrastructure.cs:177 — 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 tests/LiteBus.Transport.IntegrationTesting/Kafka/KafkaTransportTestInfrastructure.cs:180 — 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 tests/LiteBus.Transport.IntegrationTesting/Kafka/KafkaTransportTestInfrastructure.cs:183 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D17 · Explicit Debt · NoWarnInCsproj · ×3
  • NoWarnInCsproj src/LiteBus.Analyzers/LiteBus.Analyzers.csproj:25 — RS2008 — 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 tests/LiteBus.Runtime.UnitTests/LiteBus.Runtime.UnitTests.csproj:4 — CS8002 — 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/Directory.Build.props:26 — 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.
AX3 · Project dependency cycles · Namespace dependency cycle · ×2
  • Namespace dependency cycle src/LiteBus.Runtime.Abstractions/Modules/IModuleConfiguration.cs:3 — The namespaces LiteBus.Runtime.Abstractions ↔ LiteBus.Runtime.Abstractions.Diagnostics ↔ LiteBus.Runtime.Abstractions.Hosting depend on each other. The lightest dependency in the cycle is LiteBus.Runtime.Abstractions → LiteBus.Runtime.Abstractions.Diagnostics (LiteBus.Runtime.Abstractions.IModuleConfiguration → LiteBus.Runtime.Abstractions.Diagnostics.DiagnosticCheckDescriptor, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/LiteBus.Messaging/Registry/MessageRegistry.cs:10 — The namespaces LiteBus.Messaging.Registry ↔ LiteBus.Messaging.Registry.Descriptors depend on each other. The lightest dependency in the cycle is LiteBus.Messaging.Registry → LiteBus.Messaging.Registry.Descriptors (LiteBus.Messaging.Registry.MessageRegistry → LiteBus.Messaging.Registry.Descriptors.MessageDescriptor, 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.
D14 · License Compliance · Banned license · ×2
  • Banned license: MySql.EntityFrameworkCore tests/Directory.Packages.props:30 — `MySql.EntityFrameworkCore` 10.0.12 resolves to SPDX id GPL-2.0-only WITH Universal-FOSS-exception-1.0, and this run's banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an `OR` is a choice and is charged only when every branch is banned, an `AND` binds every operand, and a `WITH` exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison — which is how variants like `-only` and `-or-later` are caught while `LGPL-2.0-only` is not read as `GPL-2.0`, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. ★ This arm reads the resolved package list and knows nothing about dependency SCOPE — it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. ★ DEPTH: this repository's MSBuild projects declare 52 direct `PackageReference`(s), and 201 further package(s) were reached beyond them by closing the graph over the committed `packages.lock.json` and 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.
  • Banned license: MySql.Data — `MySql.Data` 26.10.0 resolves to SPDX id GPL-2.0-only WITH Universal-FOSS-exception-1.0, and this run's banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an `OR` is a choice and is charged only when every branch is banned, an `AND` binds every operand, and a `WITH` exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison — which is how variants like `-only` and `-or-later` are caught while `LGPL-2.0-only` is not read as `GPL-2.0`, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. ★ This arm reads the resolved package list and knows nothing about dependency SCOPE — it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. ★ DEPTH: this repository's MSBuild projects declare 52 direct `PackageReference`(s), and 201 further package(s) were reached beyond them by closing the graph over the committed `packages.lock.json` and 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.
AX9 · CQS / query purity · Query handler writes persistent state one call away, in PostgreSqlInboxStore.AddFilterParameters · ×1
  • Query handler writes persistent state one call away, in PostgreSqlInboxStore.AddFilterParameters: PostgreSql.PostgreSqlInboxStore src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:35 — `PostgreSql.PostgreSqlInboxStore` is a read (query) handler but its body writes persistent state one call away, in PostgreSqlInboxStore.AddFilterParameters — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica.
AX9 · CQS / query purity · Query handler writes persistent state one call away, in PostgreSqlOutboxStore.AddFilterParameters · ×1
  • Query handler writes persistent state one call away, in PostgreSqlOutboxStore.AddFilterParameters: PostgreSql.PostgreSqlOutboxStore src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:42 — `PostgreSql.PostgreSqlOutboxStore` is a read (query) handler but its body writes persistent state one call away, in PostgreSqlOutboxStore.AddFilterParameters — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica.
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · High IaC · ×1
  • REDACTED
Serious — 404 finding(s)
D17 · Explicit Debt · Dead code · ×41
  • Dead code: ProcessPaymentCommandValidator samples/LiteBus.Sample/Commands/ProcessPaymentCommandValidator.cs:22 — NamedType ProcessPaymentCommandValidator — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Sample, 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: ModuleRegistrationSnippet samples/LiteBus.Sample/Documentation/ModuleRegistrationSnippet.cs:14 — NamedType ModuleRegistrationSnippet — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Sample, 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: AllApplied src/LiteBus.DurableMessaging.Abstractions/Processing/PersistResult.cs:54 — Method AllApplied — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.DurableMessaging.Abstractions, 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: EnsureSchemaCreationOnStartup src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxModuleBuilder.cs:131 — Method EnsureSchemaCreationOnStartup — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Inbox.Storage.PostgreSql, 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: EnsureSchemaCreationOnStartup src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxModuleBuilder.cs:146 — Method EnsureSchemaCreationOnStartup — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Outbox.Storage.PostgreSql, 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: ThrowingQueryValidator src/LiteBus.Queries.Abstractions/ThrowingQueryValidator[TQuery, TException].cs:17 — NamedType ThrowingQueryValidator — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Queries.Abstractions, 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: RegisterState src/LiteBus.Saga/SagaModuleBuilder.cs:34 — Method RegisterState — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Saga, 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: Merge src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaSqlTokens.cs:46 — Method Merge — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Storage.PostgreSql, 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: AddAmqpTransport src/LiteBus.Transport.Amqp/LiteBusBuilderAmqpTransportExtensions.cs:17 — Method AddAmqpTransport — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Transport.Amqp, 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: AddAwsSqsTransport src/LiteBus.Transport.AwsSqs/LiteBusBuilderAwsSqsTransportExtensions.cs:17 — Method AddAwsSqsTransport — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Transport.AwsSqs, 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: LiteBusTransportAwsTelemetry src/LiteBus.Transport.AwsSqs/LiteBusTransportAwsTelemetry.cs:12 — NamedType LiteBusTransportAwsTelemetry — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Transport.AwsSqs, 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: AddAzureServiceBusTransport src/LiteBus.Transport.AzureServiceBus/LiteBusBuilderAzureServiceBusTransportExtensions.cs:17 — Method AddAzureServiceBusTransport — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Transport.AzureServiceBus, 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: LiteBusTransportAzureServiceBusTelemetry src/LiteBus.Transport.AzureServiceBus/LiteBusTransportAzureServiceBusTelemetry.cs:12 — NamedType LiteBusTransportAzureServiceBusTelemetry — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Transport.AzureServiceBus, 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: LiteBusInMemoryTelemetry src/LiteBus.Transport.InMemory/LiteBusInMemoryTelemetry.cs:10 — NamedType LiteBusInMemoryTelemetry — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Transport.InMemory, 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: AddKafkaTransport src/LiteBus.Transport.Kafka/LiteBusBuilderKafkaTransportExtensions.cs:17 — Method AddKafkaTransport — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Transport.Kafka, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: LiteBusTransportKafkaTelemetry src/LiteBus.Transport.Kafka/LiteBusTransportKafkaTelemetry.cs:11 — NamedType LiteBusTransportKafkaTelemetry — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Transport.Kafka, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: TransportReconnectOptions src/LiteBus.Transport/TransportReconnectOptions.cs:8 — NamedType TransportReconnectOptions — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Transport, 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: VerifyDiagnosticWithReferencesAsync tests/LiteBus.Analyzers.UnitTests/AnalyzerTest.cs:224 — Method VerifyDiagnosticWithReferencesAsync — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Analyzers.UnitTests, 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: ContractVersion tests/LiteBus.Durable.IntegrationTests/Dispatch/Inbox/Amqp/PostgreSqlAmqpInboxDispatchIntegrationTests.cs:23 — Field ContractVersion — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Durable.IntegrationTests, 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: ContractVersion tests/LiteBus.Durable.IntegrationTests/Dispatch/Inbox/AwsSqs/AwsSqsInboxDispatchIntegrationTests.cs:23 — Field ContractVersion — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Durable.IntegrationTests, 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: GetOrderStatusCommand tests/LiteBus.Inbox.UnitTests/InboxTestFixtures.cs:87 — NamedType GetOrderStatusCommand — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Inbox.UnitTests, 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: CreateProcessingStore tests/LiteBus.Inbox.UnitTests/InboxTestInfrastructure.cs:31 — Method CreateProcessingStore — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Inbox.UnitTests, 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: ThrowingInboxLeaseStore tests/LiteBus.Inbox.UnitTests/InboxTestInfrastructure.cs:74 — NamedType ThrowingInboxLeaseStore — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Inbox.UnitTests, 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: DelegatingInboxLeaseStore tests/LiteBus.Inbox.UnitTests/InboxTestInfrastructure.cs:106 — NamedType DelegatingInboxLeaseStore — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Inbox.UnitTests, 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: ProductUpdatedLogPayload tests/LiteBus.Mediator.UnitTests/UseCases/Commands/UseCases/LogActivity/ProductUpdatedLogPayload.cs:3 — NamedType ProductUpdatedLogPayload — Roslyn's SymbolFinder walked every project the solution loads, including LiteBus.Mediator.UnitTests, 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.
  • + 16 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 2 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×11
  • Async method without CancellationToken: ProcessPendingAsync benchmarks/LiteBus.Processor.Benchmarks/PipelinedInboxProcessorBenchmarks.cs:95 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RenewOnceAsync src/LiteBus.Commands.Recurring.Storage.PostgreSql/PostgreSqlRecurringCommandLease.cs:361 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnBatchFlushTimerElapsedAsync src/LiteBus.Inbox.Ingress/TransportInboxIngressConsumer.cs:356 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsyncCompletionHandlers src/LiteBus.Messaging/Pipeline/MessageContextExtensions.cs:506 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsyncCompletionHandlers src/LiteBus.Messaging/Pipeline/MessageContextExtensions.cs:563 — No CancellationToken parameter, and the token `executionContext.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `executionContext.CancellationToken` on, or take a CancellationToken.
  • Async method without CancellationToken: InvokeCompletionHandlerAsync src/LiteBus.Messaging/Pipeline/MessageContextExtensions.cs:704 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync smoke/LiteBus.ConsumerSmoke/InboxSmoke.cs:25 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LeaseAsync smoke/LiteBus.ConsumerSmoke/InboxSmoke.cs:78 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync smoke/LiteBus.ConsumerSmoke/MartenSmoke.cs:25 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync smoke/LiteBus.ConsumerSmoke/OutboxSmoke.cs:25 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LeaseAsync smoke/LiteBus.ConsumerSmoke/OutboxSmoke.cs:94 — No CancellationToken parameter — this work can't be stopped early once started.
D15 · Churn × Complexity Hotspots · Hotspot · ×9
  • Hotspot: src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:578 — src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in EfCoreOutboxStore.AddBatchAsync at line 578. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 18:24:17 +01:00' --until='2026-11-05 18:24:17 +01:00' --full-history --no-merges -- src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs:96 — src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in RecurringCommandBackgroundService.ExecuteAsync at line 96. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 18:24:17 +01:00' --until='2026-11-05 18:24:17 +01:00' --full-history --no-merges -- src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/LiteBus.Messaging/Registry/Descriptors/MessageDescriptor.cs src/LiteBus.Messaging/Registry/Descriptors/MessageDescriptor.cs:246 — src/LiteBus.Messaging/Registry/Descriptors/MessageDescriptor.cs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in MessageDescriptor.AddDescriptor at line 246. 2 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 18:24:17 +01:00' --until='2026-11-05 18:24:17 +01:00' --full-history --no-merges -- src/LiteBus.Messaging/Registry/Descriptors/MessageDescriptor.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:530 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in EfCoreInboxStore.AddBatchAsync at line 530. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 18:24:17 +01:00' --until='2026-11-05 18:24:17 +01:00' --full-history --no-merges -- src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: site/components/docs-article.tsx site/components/docs-article.tsx:366 — site/components/docs-article.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in docs-article.DocsArticle at line 366. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 18:24:17 +01:00' --until='2026-11-05 18:24:17 +01:00' --full-history --no-merges -- site/components/docs-article.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:680 — src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in PostgreSqlOutboxStore.AddBatchAsync at line 680. 2 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 18:24:17 +01:00' --until='2026-11-05 18:24:17 +01:00' --full-history --no-merges -- src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/LiteBus.Outbox/OutboxModule.cs src/LiteBus.Outbox/OutboxModule.cs:49 — src/LiteBus.Outbox/OutboxModule.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in OutboxModule.Build at line 49. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 18:24:17 +01:00' --until='2026-11-05 18:24:17 +01:00' --full-history --no-merges -- src/LiteBus.Outbox/OutboxModule.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:108 — src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in SingleStreamHandlerMediationEnumerable.MediateAsync at line 108. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 18:24:17 +01:00' --until='2026-11-05 18:24:17 +01:00' --full-history --no-merges -- src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:644 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in PostgreSqlInboxStore.AddBatchAsync at line 644. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-07..2026-11-05, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-07 18:24:17 +01:00' --until='2026-11-05 18:24:17 +01:00' --full-history --no-merges -- src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
X18 · Disposal-pattern correctness · Disposes a dependency it does not own · ×9
  • Disposes a dependency it does not own src/LiteBus.Messaging/Mediator/MediationResourceScope.cs:44 — `_dispatchScope` is never created by `MediationResourceScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 44). Its declared type `IMessageDispatchScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Messaging/Mediator/MediationResourceScope.cs:58 — `_dispatchScope` is never created by `MediationResourceScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 58). Its declared type `IMessageDispatchScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Messaging/Mediator/MediationScopeRetention.cs:261 — `_source` is never created by `ScopeRetainedAsyncEnumerator` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 261). Its declared type `IAsyncEnumerator` is an interface, so the instance came from whoever chose and created 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/LiteBus.Runtime.Extensions.Autofac/AutofacMessageDispatchScopeFactory.cs:66 — `_scope` is never created by `AutofacMessageDispatchScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 66). Its declared type `ILifetimeScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Runtime.Extensions.Autofac/AutofacMessageDispatchScopeFactory.cs:72 — `_scope` is never created by `AutofacMessageDispatchScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 72). Its declared type `ILifetimeScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Runtime.Extensions.Microsoft.DependencyInjection/MicrosoftMessageDispatchScopeFactory.cs:60 — `_scope` is never created by `MicrosoftMessageDispatchScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 60). Its declared type `IServiceScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Runtime.Extensions.Microsoft.DependencyInjection/MicrosoftMessageDispatchScopeFactory.cs:71 — `_scope` is never created by `MicrosoftMessageDispatchScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 71). Its declared type `IServiceScope` is an interface, so the instance came from whoever chose and created 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/LiteBus.Storage.PostgreSql/PostgreSqlDataSourceOwner[TModule].cs:62 — `DataSource` is never created by `PostgreSqlDataSourceOwner` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 62). Its declared type `NpgsqlDataSource` is an abstract class, so the instance came from whoever chose and created 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/LiteBus.Transport.Kafka/KafkaConsumer.cs:247 — `_consumer` is never created by `KafkaConsumer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 247). Its declared type `IConsumer` is an interface, so the instance came from whoever chose and created 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×8
  • Duplicated block (19 lines × 2) src/LiteBus.Inbox/InboxProcessorTelemetry.cs:63 — src/LiteBus.Inbox/InboxProcessorTelemetry.cs:63-81 | src/LiteBus.Outbox/OutboxProcessorTelemetry.cs:62-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (19 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs:96 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs:96-114 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs:98-116 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `entity` to `EntityTypeBuilder<InboxMessageEntity>` in one and `EntityTypeBuilder<OutboxMessageEntity>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (19 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:185 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:185-203 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:197-215 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `filter` to `InboxMessageFilter` in one and `OutboxMessageFilter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (19 lines × 2) src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs:74 — src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs:74-92 | src/LiteBus.Outbox/OutboxPipelinedMessageProcessorOperations.cs:74-92 — before extracting anything, compare `src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs` and `src/LiteBus.Outbox/OutboxPipelinedMessageProcessorOperations.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 2) src/LiteBus.Messaging.Abstractions/Contracts/MessageContractBuilder.cs:63 — src/LiteBus.Messaging.Abstractions/Contracts/MessageContractBuilder.cs:63-81 | src/LiteBus.Messaging/Contracts/MessageContractRegistry.cs:157-175 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 2) src/LiteBus.Commands.Storage.Marten/MartenIdempotencyStore.cs:92 — src/LiteBus.Commands.Storage.Marten/MartenIdempotencyStore.cs:92-110 | src/LiteBus.Commands.Storage.Marten/MartenIdempotencyStore.cs:159-177 — 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/LiteBus.Commands.Storage.Marten/MartenIdempotencyStore.cs:92` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (19 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/LiteBusInboxSaveChangesInterceptor.cs:87 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/LiteBusInboxSaveChangesInterceptor.cs:87-105 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/LiteBusOutboxSaveChangesInterceptor.cs:86-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/LiteBusInboxSaveChangesInterceptor.cs:87` 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 matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelope` to `InboxEnvelope` in one and `OutboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (19 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:349 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:349-367 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:361-379 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:349` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelopes` to `IReadOnlyList<InboxEnvelope>` in one and `IReadOnlyList<OutboxEnvelope>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×8
  • Duplicated block (13 lines × 2) src/LiteBus.Inbox.Dispatch.InProcess/CommandInboxDispatcher.cs:77 — src/LiteBus.Inbox.Dispatch.InProcess/CommandInboxDispatcher.cs:77-89 | src/LiteBus.Outbox.Dispatch.InProcess/EventOutboxDispatcher.cs:113-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (13 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:844 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:844-856 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:882-894 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:844` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs:131 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs:131-143 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs:140-152 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `entity` to `EntityTypeBuilder<InboxMessageEntity>` in one and `EntityTypeBuilder<OutboxMessageEntity>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs:145` calls `HasIndex`, `IsUnique`, `HasFilter` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs:154` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 2) src/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs:89 — src/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs:89-101 | src/LiteBus.Analyzers/TransactionalOutboxWithoutDbContextAnalyzer.cs:89-101 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:294 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:294-306 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:348-360 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:294` 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 (13 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1349 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1349-1361 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1434-1446 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1349` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `IInboxDbContext` in one and `IOutboxDbContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (13 lines × 2) src/LiteBus.Inbox/InboxCleanupBackgroundService.cs:122 — src/LiteBus.Inbox/InboxCleanupBackgroundService.cs:122-134 | src/LiteBus.Outbox/OutboxCleanupBackgroundService.cs:126-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox/InboxCleanupBackgroundService.cs:122` 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 (13 lines × 2) src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs:187 — src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs:187-199 | src/LiteBus.Outbox/OutboxPipelinedMessageProcessorOperations.cs:187-199 — before extracting anything, compare `src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs` and `src/LiteBus.Outbox/OutboxPipelinedMessageProcessorOperations.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs:187` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×8
  • Duplicated block (11 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:240 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:240-250 | src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:264-274 — 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/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:240` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `LeaseRenewalRequest` in one and `LeaseReleaseRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:239` calls `ThrowIfLessThanOrEqual` and `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:263` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:252 — src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:252-262 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:276-286 — 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/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:252` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `LeaseRenewalRequest` in one and `LeaseReleaseRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:251` calls `ThrowIfLessThanOrEqual` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:275` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1205 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1205-1215 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1203-1213 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs:214 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs:214-224 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:216-226 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs:214` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelope` to `InboxEnvelope` in one and `OutboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (11 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:325 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:325-335 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:385-395 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:325` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `filter` to `InboxMessageFilter` in one and `OutboxMessageFilter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (11 lines × 2) src/LiteBus.Analyzers/Analysis/CompilationEndOrdering.cs:24 — src/LiteBus.Analyzers/Analysis/CompilationEndOrdering.cs:24-34 | src/LiteBus.Analyzers/Analysis/DeclarationAnalysis.cs:430-440 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) src/LiteBus.Inbox/InboxObservableMetrics.cs:102 — src/LiteBus.Inbox/InboxObservableMetrics.cs:102-112 | src/LiteBus.Outbox/OutboxObservableMetrics.cs:103-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) src/LiteBus.Inbox/InboxRetentionCoordinator.cs:82 — src/LiteBus.Inbox/InboxRetentionCoordinator.cs:82-92 | src/LiteBus.Outbox/OutboxRetentionCoordinator.cs:83-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D3 · God Classes · TooManyMethods · ×7
  • TooManyMethods: EfCoreOutboxStore src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs — TooManyMethods — 1017 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: EfCoreInboxStore src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs — TooManyMethods — 1011 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PostgreSqlOutboxStore src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs — TooManyMethods — 705 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PostgreSqlInboxStore src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs — TooManyMethods — 674 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: LiteBusManagementEndpointExtensions REDACTED — TooManyMethods — 447 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: InMemoryOutboxStore src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs — TooManyMethods — 357 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: InMemoryInboxStore src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs — TooManyMethods — 330 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×7
  • Duplicated block (8 lines × 2) src/LiteBus.Messaging/Registry/Builders/PostHandlerDescriptorBuilder.cs:30 — src/LiteBus.Messaging/Registry/Builders/PostHandlerDescriptorBuilder.cs:30-37 | src/LiteBus.Messaging/Registry/Builders/RefusalMapperDescriptorBuilder.cs:30-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Messaging/Registry/Builders/PostHandlerDescriptorBuilder.cs:30` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs:236 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs:236-243 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:238-245 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelope` to `InboxEnvelope` in one and `OutboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1018 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1018-1025 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1056-1063 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1018` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelopes` to `IReadOnlyList<InboxEnvelope>` in one and `IReadOnlyList<OutboxEnvelope>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) src/LiteBus.Commands/CommandMediator.cs:264 — src/LiteBus.Commands/CommandMediator.cs:264-271 | src/LiteBus.Messaging/MediationResultFactory.cs:25-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Commands/CommandMediator.cs:264` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1049 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1049-1056 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1087-1094 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1049` 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.
  • Duplicated block (8 lines × 2) src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaStore.cs:247 — src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaStore.cs:247-254 | src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaStore.cs:329-336 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `filter` to `SagaQueryFilter` in one and `SagaPurgeFilter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) src/LiteBus.Transport.Amqp/AmqpConsumer.cs:490 — src/LiteBus.Transport.Amqp/AmqpConsumer.cs:490-497 | src/LiteBus.Transport.Amqp/AmqpPublisher.cs:286-293 — 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. 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.
D10 · Test Quality · No assertions · ×6
  • No assertions: WaitForWorkOrDelayAsync_zero_interval_completes_immediately tests/LiteBus.Inbox.UnitTests/InboxPollingWorkSignalTests.cs:8 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: The_doubles_reject_a_null_message tests/LiteBus.Mediator.UnitTests/Pipeline/TestMediatorDoubleTests.cs:285 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: A_valid_message_passes_through_the_adapter tests/LiteBus.Mediator.UnitTests/Pipeline/ThrowingValidatorTests.cs:44 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: Lease_loss_cancels_the_in_flight_send tests/LiteBus.Mediator.UnitTests/UseCases/Commands/RecurringCommandLeaseTests.cs:166 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: Send_Command_WithHandledErrorOutcome_ShouldSuppressException tests/LiteBus.Mediator.UnitTests/UseCases/Messaging/MediationCorrectnessTests.cs:76 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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: PublishAsync_without_collected_events_should_not_require_a_transactional_outbox tests/LiteBus.Outbox.UnitTests/DomainEvents/DomainEventStagingTests.cs:116 — 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*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, 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.
D3 · God Classes · FunctionTooLong · ×6
  • FunctionTooLong: page.HomePage site/app/page.tsx:286 — FunctionTooLong — HomePage runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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.
  • FunctionTooLong: page.PrivacyPage site/app/privacy/page.tsx:41 — FunctionTooLong — PrivacyPage runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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.
  • FunctionTooLong: docs-article.DocsArticle site/components/docs-article.tsx:366 — FunctionTooLong — DocsArticle runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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.
  • FunctionTooLong: docs-drawer.DocsDrawer site/components/docs-drawer.tsx:19 — FunctionTooLong — DocsDrawer runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× 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.
  • FunctionTooLong: home-stepper.HomeStepper REDACTED:32 — FunctionTooLong — HomeStepper runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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.
  • FunctionTooLong: search-box.SearchBox site/components/search-box.tsx:50 — FunctionTooLong — SearchBox runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×6
  • Duplicated block (16 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:273 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:273-288 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:327-342 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:273` 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 (16 lines × 2) src/LiteBus.Analyzers/DuplicateCommandHandlerAnalyzer.cs:72 — src/LiteBus.Analyzers/DuplicateCommandHandlerAnalyzer.cs:72-87 | src/LiteBus.Analyzers/DuplicateQueryHandlerAnalyzer.cs:90-105 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Analyzers/DuplicateCommandHandlerAnalyzer.cs:72` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) src/LiteBus.Analyzers/MissingCommandHandlerAnalyzer.cs:87 — src/LiteBus.Analyzers/MissingCommandHandlerAnalyzer.cs:87-102 | src/LiteBus.Analyzers/MissingQueryHandlerAnalyzer.cs:113-128 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Analyzers/MissingCommandHandlerAnalyzer.cs:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `CompilationAnalysisContext` in one and `CompilationStartAnalysisContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (16 lines × 2) src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs:270 — src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs:270-285 | src/LiteBus.Outbox/OutboxPipelinedMessageProcessorOperations.cs:270-285 — before extracting anything, compare `src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs` and `src/LiteBus.Outbox/OutboxPipelinedMessageProcessorOperations.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs:270` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 2) src/LiteBus.Outbox/OutboxWriterCore.cs:49 — src/LiteBus.Outbox/OutboxWriterCore.cs:49-64 | src/LiteBus.Outbox/OutboxWriterCore.cs:135-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Outbox/OutboxWriterCore.cs:49` 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 (16 lines × 2) src/LiteBus.Transport.InMemory/InMemoryConsumer.cs:67 — src/LiteBus.Transport.InMemory/InMemoryConsumer.cs:67-82 | src/LiteBus.Transport.Kafka/KafkaConsumer.cs:92-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Transport.InMemory/InMemoryConsumer.cs:67` 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 (15 lines × 2) · ×6
  • Duplicated block (15 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1207 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1207-1221 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1225-1239 — 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/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1207` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (15 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1521 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1521-1535 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1638-1652 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:676 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:676-690 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:712-726 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:676` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelopes` to `IReadOnlyList<InboxEnvelope>` in one and `IReadOnlyList<OutboxEnvelope>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (15 lines × 2) src/LiteBus.Inbox/InboxProcessorEnvelopeHandler.cs:145 — src/LiteBus.Inbox/InboxProcessorEnvelopeHandler.cs:145-161 | src/LiteBus.Outbox/OutboxProcessorEnvelopeHandler.cs:108-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox/InboxProcessorEnvelopeHandler.cs:145` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (15 lines × 2) src/LiteBus.Inbox.Abstractions/InboxPollingWorkSignal.cs:21 — src/LiteBus.Inbox.Abstractions/InboxPollingWorkSignal.cs:21-35 | src/LiteBus.Outbox.Abstractions/OutboxPollingWorkSignal.cs:21-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 2) src/LiteBus.Inbox/InboxProcessorControl.cs:99 — src/LiteBus.Inbox/InboxProcessorControl.cs:99-113 | src/LiteBus.Outbox/OutboxProcessorControl.cs:99-113 — before extracting anything, compare `src/LiteBus.Inbox/InboxProcessorControl.cs` and `src/LiteBus.Outbox/OutboxProcessorControl.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×6
  • Duplicated block (6 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1832 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1832-1837 | src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:654-659 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1832` 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.
  • Duplicated block (6 lines × 2) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1847 — src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1847-1852 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:698-703 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1847` 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.
  • Duplicated block (6 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:394 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:394-399 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:456-461 — 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 (6 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1330 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1330-1335 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1336-1341 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelope` to `InboxEnvelope` in one and `OutboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1343` calls `AddWithValue` and `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1337` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:455 — src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:455-460 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:517-522 — 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 (6 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:534 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:534-539 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:576-581 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D5 · Coupling · Off the main sequence · ×6
  • Off the main sequence: LiteBus.Inbox src/LiteBus.Inbox/LiteBus.Inbox.csproj:1 — LiteBus.Inbox: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
  • Off the main sequence: LiteBus.Messaging src/LiteBus.Messaging/LiteBus.Messaging.csproj:1 — LiteBus.Messaging: abstractness 0.03, instability 0.15, distance 0.82 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
  • Off the main sequence: LiteBus.Outbox src/LiteBus.Outbox/LiteBus.Outbox.csproj:1 — LiteBus.Outbox: abstractness 0.00, instability 0.22, distance 0.78 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
  • Off the main sequence: LiteBus.Runtime src/LiteBus.Runtime/LiteBus.Runtime.csproj:1 — LiteBus.Runtime: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: LiteBus.Commands src/LiteBus.Commands/LiteBus.Commands.csproj:1 — LiteBus.Commands: abstractness 0.00, instability 0.27, distance 0.73 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
  • Off the main sequence: LiteBus.Transport src/LiteBus.Transport/LiteBus.Transport.csproj:1 — LiteBus.Transport: abstractness 0.11, instability 0.18, distance 0.71 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
D3 · God Classes · FileTooLong · ×5
  • FileTooLong: LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs — FileTooLong — 1082 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 582 over it, 2.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs — FileTooLong — 1072 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 572 over it, 2.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: lib/highlight.ts site/lib/highlight.ts — FileTooLong — 787 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 287 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs — FileTooLong — 722 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 222 over it, 1.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs — FileTooLong — 691 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 191 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×5
  • Duplicated block (17 lines × 2) src/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs:44 — src/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs:44-60 | src/LiteBus.Analyzers/TransactionalOutboxWithoutDbContextAnalyzer.cs:44-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs:44` 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 (17 lines × 2) src/LiteBus.Inbox/InboxModule.cs:79 — src/LiteBus.Inbox/InboxModule.cs:79-95 | src/LiteBus.Outbox/OutboxModule.cs:91-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox/InboxModule.cs:79` 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 (17 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1317 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1317-1333 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1402-1418 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1317` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `IInboxDbContext` in one and `IOutboxDbContext` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (17 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:139 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:139-155 | src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:214-230 — 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/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:139` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:310 — src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:310-326 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:858-874 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:310` 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 (23 lines × 2) · ×5
  • Duplicated block (23 lines × 2) src/LiteBus.Commands/CommandModule.cs:120 — src/LiteBus.Commands/CommandModule.cs:120-142 | src/LiteBus.Queries/QueryModule.cs:85-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Commands/CommandModule.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.
  • Duplicated block (23 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:105 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:105-127 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:104-126 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/LiteBus.Inbox/InboxProcessorPassRecorder.cs:31 — src/LiteBus.Inbox/InboxProcessorPassRecorder.cs:31-53 | src/LiteBus.Inbox/InboxProcessorPassRecorder.cs:71-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/LiteBus.Outbox/OutboxProcessorPassRecorder.cs:31 — src/LiteBus.Outbox/OutboxProcessorPassRecorder.cs:31-53 | src/LiteBus.Outbox/OutboxProcessorPassRecorder.cs:71-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1742 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1742-1764 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1752-1774 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1742` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `filter` to `InboxMessageFilter` in one and `OutboxMessageFilter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×5
  • Duplicated block (12 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:237 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:237-248 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:291-302 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:237` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `pageRequest` to `InboxMessagePageRequest` in one and `OutboxMessagePageRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (12 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:208 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:208-219 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:220-231 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:208` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `filter` to `InboxMessageFilter` in one and `OutboxMessageFilter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (12 lines × 2) src/LiteBus.Commands/UnitOfWork/CommandUnitOfWorkCompletionHandler[TUnitOfWork].cs:49 — src/LiteBus.Commands/UnitOfWork/CommandUnitOfWorkCompletionHandler[TUnitOfWork].cs:49-60 | src/LiteBus.Queries/UnitOfWork/QueryUnitOfWorkCompletionHandler[TUnitOfWork].cs:49-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) src/LiteBus.Inbox/InboxProcessorFactory.cs:64 — src/LiteBus.Inbox/InboxProcessorFactory.cs:64-75 | src/LiteBus.Outbox/OutboxProcessorFactory.cs:64-75 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:87 — src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:87-98 | src/LiteBus.Outbox.Storage.Marten/MartenTransactionalOutbox.cs:102-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
X2 · Cancellation propagation · Async call defeats the CancellationToken · ×5
  • Async call defeats the CancellationToken: HandleCompletionAsync src/LiteBus.Commands/Idempotency/IdempotencyCompletionHandler.cs:87 — Holds a CancellationToken but hands `CancellationToken.None` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
  • Async call defeats the CancellationToken: RunAsync src/LiteBus.Runtime.Abstractions/Diagnostics/DiagnosticCheckRunner.cs:198 — Holds a CancellationToken but hands `CancellationToken.None` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
  • Async call defeats the CancellationToken: RunProcessorSessionAsync src/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs:330 — Holds a CancellationToken but hands `CancellationToken.None` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
  • Async call defeats the CancellationToken: RunConsumeLoopAsync src/LiteBus.Transport.InMemory/InMemoryConsumer.cs:215 — Holds a CancellationToken but hands `CancellationToken.None` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
  • Async call defeats the CancellationToken: StopAsync src/LiteBus.Transport.Kafka/KafkaConsumer.cs:169 — Holds a CancellationToken but hands `CancellationToken.None` to the awaited call on this line, so the caller's cancellation never reaches that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible).
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×4
  • Duplicated block (15 lines × 3) src/LiteBus.Commands/CommandModuleBuilder.cs:318 — src/LiteBus.Commands/CommandModuleBuilder.cs:318-332 | src/LiteBus.Events/EventModuleBuilder.cs:215-229 | src/LiteBus.Queries/QueryModuleBuilder.cs:210-224 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Commands/CommandModuleBuilder.cs:318` 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 (15 lines × 3) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:83 — src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:83-97 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:56-70 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs:70-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:83` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:54` calls `CreateScope` and `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:81` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (15 lines × 3) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1207 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1207-1221 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1225-1239 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1243-1257 — all 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1207` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (15 lines × 3) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1293 — src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1293-1307 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1311-1325 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1329-1343 — all 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1293` 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 (10 lines × 2) · ×4
  • Duplicated block (10 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:592 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:592-601 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:637-646 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:592` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `filter` to `InboxMessageFilter` in one and `OutboxMessageFilter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:270 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:270-279 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:282-291 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:270` 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 (10 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:575 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:575-584 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:592-601 — 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/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:592` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:623 — src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:623-632 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:635-644 — 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/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:635` 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. 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 (7 lines × 2) · ×4
  • Duplicated block (7 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:400 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:400-406 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:461-467 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:400` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `InboxLeaseRequest` in one and `OutboxLeaseRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:462 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:462-468 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:523-529 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:462` 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.
  • Duplicated block (7 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:797 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:797-803 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:630-636 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:797` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/LiteBus.Inbox.Abstractions/InboxCleanupHostOptions.cs:33 — src/LiteBus.Inbox.Abstractions/InboxCleanupHostOptions.cs:33-39 | src/LiteBus.Outbox.Abstractions/OutboxCleanupHostOptions.cs:33-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaVersionStore.cs:124 — src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaVersionStore.cs:124-128 | src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaVersionStore.cs:182-186 — 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 (5 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1349 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1349-1353 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1357-1361 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1349` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelope` to `InboxEnvelope` in one and `OutboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1357` calls `AddWithValue` and `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1349` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1345 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1345-1349 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1352-1356 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelope` to `InboxEnvelope` in one and `OutboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1357` calls `AddWithValue` and `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1351` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) src/LiteBus.Commands.Storage.PostgreSql/PostgreSqlIdempotencySchemaScripts.cs:165 — src/LiteBus.Commands.Storage.PostgreSql/PostgreSqlIdempotencySchemaScripts.cs:165-169 | src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaSchemaScripts.cs:166-170 — before extracting anything, compare `src/LiteBus.Commands.Storage.PostgreSql/PostgreSqlIdempotencySchemaScripts.cs` and `src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaSchemaScripts.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×4
  • Sync-over-async blocking — 3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking benchmarks/LiteBus.Processor.Benchmarks/PipelinedInboxProcessorBenchmarks.cs:86 — `.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:162 — `.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/LiteBus.Transport.AzureServiceBus/AzureServiceBusPublisher.cs:63 — `.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).
D12 · Dependency Hygiene · Deprecated · ×3
  • Deprecated: Microsoft.CodeAnalysis.CSharp.Analyzer.Testing.XUnit tests/Directory.Packages.props:5 — Microsoft.CodeAnalysis.CSharp.Analyzer.Testing.XUnit 1.1.2 — Legacy — the publisher's replacement is `Microsoft.CodeAnalysis.CSharp.Analyzer.Testing`; migrate the reference to it.
  • Deprecated: xunit tests/Directory.Packages.props:47 — 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: eslint site/package.json:37 — eslint 9.39.5, declared in site/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.
D3 · God Classes · MethodTooLong · ×3
  • MethodTooLong: SingleStreamHandlerMediationEnumerable.MediateAsync src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:108 — MethodTooLong — MediateAsync runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× 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.
  • MethodTooLong: EfCoreOutboxStore.AddBatchAsync src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:578 — MethodTooLong — AddBatchAsync runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× 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.
  • MethodTooLong: EfCoreInboxStore.AddBatchAsync src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:530 — MethodTooLong — AddBatchAsync runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/LiteBus.Commands.Recurring.Storage.PostgreSql/PostgreSqlRecurringLeaseSchemaScripts.cs:85 — src/LiteBus.Commands.Recurring.Storage.PostgreSql/PostgreSqlRecurringLeaseSchemaScripts.cs:85-93 | src/LiteBus.Commands.Storage.PostgreSql/PostgreSqlIdempotencySchemaScripts.cs:89-97 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxSchemaScripts.cs:104-112 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxSchemaScripts.cs:124-132 | src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaSchemaScripts.cs:90-98 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:68 — src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:68-210 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:40-212 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs:57-183 | src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:114-423 | src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:130-161 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/LiteBus.Inbox.Ingress.Amqp/AmqpInboxIngressModule.cs:36 — src/LiteBus.Inbox.Ingress.Amqp/AmqpInboxIngressModule.cs:36-87 | src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs:37-84 | src/LiteBus.Inbox.Ingress.AzureServiceBus/AzureServiceBusInboxIngressModule.cs:37-87 | src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs:37-80 | src/LiteBus.Inbox.Ingress.Kafka/KafkaInboxIngressModule.cs:37-82 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×3
  • Duplicated block (34 lines × 2) src/LiteBus.Inbox.Abstractions/InboxReceipt.cs:19 — src/LiteBus.Inbox.Abstractions/InboxReceipt.cs:19-52 | src/LiteBus.Inbox.Abstractions/InboxReceipt[TMessage].cs:18-51 — 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 (34 lines × 2) src/LiteBus.Inbox/InboxCleanupBackgroundService.cs:87 — src/LiteBus.Inbox/InboxCleanupBackgroundService.cs:87-120 | src/LiteBus.Outbox/OutboxCleanupBackgroundService.cs:91-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox/InboxCleanupBackgroundService.cs:87` 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 (34 lines × 2) src/LiteBus.Outbox.Abstractions/OutboxReceipt.cs:19 — src/LiteBus.Outbox.Abstractions/OutboxReceipt.cs:19-52 | src/LiteBus.Outbox.Abstractions/OutboxReceipt[TEvent].cs:21-54 — before extracting anything, compare `src/LiteBus.Outbox.Abstractions/OutboxReceipt.cs` and `src/LiteBus.Outbox.Abstractions/OutboxReceipt[TEvent].cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×3
  • Duplicated block (27 lines × 2) REDACTED:816 — REDACTED:816-842 | REDACTED:870-896 — 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:816` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (27 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1881 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1881-1907 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1893-1919 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1914` calls `Column` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1921` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (27 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStorageModule.cs:30 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStorageModule.cs:30-56 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStorageModule.cs:31-92 — 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 × 2) · ×3
  • Duplicated block (20 lines × 2) src/LiteBus.Commands/Idempotency/IdempotentCommandShortcut[TCommand, TCommandResult].cs:95 — src/LiteBus.Commands/Idempotency/IdempotentCommandShortcut[TCommand, TCommandResult].cs:95-114 | src/LiteBus.Commands/Idempotency/IdempotentCommandShortcut[TCommand].cs:93-112 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Commands/Idempotency/IdempotentCommandShortcut[TCommand, TCommandResult].cs:95` 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 (20 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:360 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:360-379 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:414-433 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:360` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `InboxLeaseRequest` in one and `OutboxLeaseRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (20 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1769 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1769-1788 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1784-1803 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1769` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `filter` to `InboxMessageFilter` in one and `OutboxMessageFilter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×3
  • Duplicated block (21 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:568 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:568-588 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:608-628 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `filter` to `InboxMessageFilter` in one and `OutboxMessageFilter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (21 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:159 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:159-179 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:151-171 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:159` 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 (21 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:439 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:439-459 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:493-513 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:439` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelopes` to `IReadOnlyList<InboxEnvelope>` in one and `IReadOnlyList<OutboxEnvelope>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×3
  • Duplicated block (18 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1231 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1231-1248 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1256-1273 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1231` 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 (18 lines × 2) src/LiteBus.Inbox/InboxProcessorControl.cs:77 — src/LiteBus.Inbox/InboxProcessorControl.cs:77-94 | src/LiteBus.Outbox/OutboxProcessorControl.cs:77-94 — before extracting anything, compare `src/LiteBus.Inbox/InboxProcessorControl.cs` and `src/LiteBus.Outbox/OutboxProcessorControl.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2074 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2074-2091 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs:269-286 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2074` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `existing` to `InboxMessageEntity` in one and `InboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D6 · Cohesion (LCOM4) · Low cohesion · ×3
  • Low cohesion: MessageModuleBuilder (LCOM4 13) src/LiteBus.Messaging/MessageModuleBuilder.cs:17 — MessageModuleBuilder's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: OutboxModuleBuilder (LCOM4 10) src/LiteBus.Outbox/OutboxModuleBuilder.cs:16 — OutboxModuleBuilder's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: InboxModuleBuilder (LCOM4 7) src/LiteBus.Inbox/InboxModuleBuilder.cs:18 — InboxModuleBuilder's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×3
  • Sync-over-async (deadlock risk) benchmarks/LiteBus.Processor.Benchmarks/PipelinedInboxProcessorBenchmarks.cs:76 — 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:162 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
  • Sync-over-async (deadlock risk) src/LiteBus.Transport.AzureServiceBus/AzureServiceBusPublisher.cs:63 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×3
  • Disposable created and abandoned in the method that made it src/LiteBus.Transport.Amqp/AmqpConsumer.cs:350 — `admission` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 350). Every use of it in `CreateBoundedHandler` 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 admission = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/LiteBus.Transport/TransportConsumerHandlerInvoker.cs:32 — `admission` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 32). Every use of it in `CreateBoundedHandler` 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 admission = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/LiteBus.Transport/TransportConsumerHandlerInvoker.cs:63 — `admission` is a `SemaphoreSlim`, which implements `IDisposable`, and it is created here (line 63). Every use of it in `CreateBoundedOutcomeHandler` 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 admission = …;`), which releases it at the end of the scope on every path including a throw.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×3
  • Swallowed exception (caught, then discarded) REDACTED:252 — `catch (ObjectDisposedException) 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.
  • Swallowed exception (caught, then discarded) src/LiteBus.Transport.AwsSqs/SqsVisibilityHeartbeat.cs:114 — `catch (Exception)` 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/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs:232 — `catch (ObjectDisposedException)` 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.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×2
  • Focus outline removed in CSS without a :focus replacement site/app/globals.css:257 — `.search input[type="search"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement site/app/docs/docs.css:10 — `.explorer:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
D17 · Explicit Debt · BarePragmaDisable · ×2
  • BarePragmaDisable src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:264 — #pragma warning disable CA2219 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/LiteBus.Transport/TransportConsumerHandlerInvoker.cs:127 — #pragma warning disable CA1031 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
D31 · IaC & Container Security · Medium IaC · ×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/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:236 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:236-255 | src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:261-279 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:248-267 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:273-291 — 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) src/LiteBus.Transport.AwsSqs/SqsPublisher.cs:50 — src/LiteBus.Transport.AwsSqs/SqsPublisher.cs:50-113 | src/LiteBus.Transport.AzureServiceBus/AzureServiceBusPublisher.cs:105-162 | src/LiteBus.Transport.InMemory/InMemoryPublisher.cs:46-107 | src/LiteBus.Transport.Kafka/KafkaPublisher.cs:70-130 — 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 (38 lines × 2) · ×2
  • Duplicated block (38 lines × 2) src/LiteBus.Extensions.AspNetCore/InboxMessageQueryBinding.cs:45 — src/LiteBus.Extensions.AspNetCore/InboxMessageQueryBinding.cs:45-82 | src/LiteBus.Extensions.AspNetCore/OutboxMessageQueryBinding.cs:51-88 — 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 (38 lines × 2) src/LiteBus.Inbox/InboxPayloadProtector.cs:27 — src/LiteBus.Inbox/InboxPayloadProtector.cs:27-64 | src/LiteBus.Outbox/OutboxPayloadProtector.cs:27-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×2
  • Duplicated block (25 lines × 2) src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:45 — src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:45-69 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs:59-83 — before extracting anything, compare `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs` and `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:45` 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 (25 lines × 2) src/LiteBus.Runtime.Extensions.Autofac/ContainerBuilderExtensions.cs:56 — src/LiteBus.Runtime.Extensions.Autofac/ContainerBuilderExtensions.cs:56-80 | src/LiteBus.Runtime.Extensions.Microsoft.DependencyInjection/ServiceCollectionExtensions.cs:60-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Runtime.Extensions.Autofac/ContainerBuilderExtensions.cs:56` 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 (24 lines × 2) · ×2
  • Duplicated block (24 lines × 2) src/LiteBus.Inbox/InboxProcessorControl.cs:173 — src/LiteBus.Inbox/InboxProcessorControl.cs:173-196 | src/LiteBus.Outbox/OutboxProcessorControl.cs:173-196 — before extracting anything, compare `src/LiteBus.Inbox/InboxProcessorControl.cs` and `src/LiteBus.Outbox/OutboxProcessorControl.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:926 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:926-949 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1026-1049 — 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/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:926` 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. 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 (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) src/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:248 — src/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:248-261 | src/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:296-309 — 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/LiteBus.Analyzers/Analysis/ModuleConfigurationAnalysis.cs:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:863 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:863-876 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:901-914 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:863` 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 × 2) · ×2
  • Duplicated block (22 lines × 2) src/LiteBus.Inbox.Abstractions/InboxDeadLetterStoreExtensions.cs:25 — src/LiteBus.Inbox.Abstractions/InboxDeadLetterStoreExtensions.cs:25-46 | src/LiteBus.Outbox.Abstractions/OutboxDeadLetterStoreExtensions.cs:25-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `store` to `this IInboxDeadLetterStore` in one and `this IOutboxDeadLetterStore` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (22 lines × 2) src/LiteBus.Inbox/InboxManager.cs:118 — src/LiteBus.Inbox/InboxManager.cs:118-139 | src/LiteBus.Outbox/OutboxManager.cs:115-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox/InboxManager.cs:118` 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 (17 lines × 3) · ×2
  • Duplicated block (17 lines × 3) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:820 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:820-836 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:922-938 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1022-1038 — all 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:820` 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 (17 lines × 3) src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:193 — src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:193-209 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs:166-182 | src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:401-417 — before extracting anything, compare `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs` and `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:193` 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 (12 lines × 3) · ×2
  • Duplicated block (12 lines × 3) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2078 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2078-2089 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs:273-284 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:2104-2115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2078` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `existing` to `InboxMessageEntity` in one and `InboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:2101` calls `Equals` and `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2076` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 3) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:801 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:801-812 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:313-324 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:861-872 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:801` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelope` to `InboxEnvelope` in one and `OutboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:792 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:792-800 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:850-858 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:792` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelope` to `InboxEnvelope` in one and `OutboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (9 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1275 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1275-1283 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1586-1594 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×2
  • Duplicated block (5 lines × 3) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:924 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:924-928 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1014-1018 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1111-1115 — all 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:924` 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 (5 lines × 3) src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:962 — src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:962-966 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1052-1056 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1149-1153 — all 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:962` 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 (8 lines × 4) · ×2
  • Duplicated block (8 lines × 4) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:2100 — src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:2100-2107 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:309-316 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:857-864 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:666-673 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:2100` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `existing` to `OutboxMessageEntity` in one and `OutboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 4) src/LiteBus.Transport.Amqp/AmqpConsumer.cs:287 — src/LiteBus.Transport.Amqp/AmqpConsumer.cs:287-294 | src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:180-187 | src/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs:179-186 | src/LiteBus.Transport.InMemory/InMemoryConsumer.cs:175-182 — before extracting anything, compare `src/LiteBus.Transport.AwsSqs/SqsConsumer.cs` and `src/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×2
  • Duplicated block (8 lines × 3) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1433 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1433-1440 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1462-1469 | src/LiteBus.Storage.EntityFrameworkCore/EfCoreJsonTextNormalizer.cs:17-24 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:168 — src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:168-175 | src/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs:167-174 | src/LiteBus.Transport.Kafka/KafkaConsumer.cs:224-231 — before extracting anything, compare `src/LiteBus.Transport.AwsSqs/SqsConsumer.cs` and `src/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung site/package.json:33 — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) 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 21 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.
AX2 · Stateful singletons · Stateful singleton · ×1
  • Stateful singleton: BackgroundServiceHostedServiceIndex src/LiteBus.Runtime.Extensions.Microsoft.Hosting/BackgroundServiceHostedServiceIndex.cs:12 — `BackgroundServiceHostedServiceIndex` is a singleton (one shared instance) but mutates instance state outside any lock (_backgroundServicesByImplementationType; e.g. `_backgroundServicesByImplementationType` at line 29).
AX2 · Stateful singletons · Stateful shared instance · ×1
  • Stateful shared instance: KafkaBrokerHost tests/LiteBus.Transport.IntegrationTesting/Kafka/KafkaBrokerHost.cs:11 — `KafkaBrokerHost` is not registered, but `KafkaBrokerSharedLifecycle` creates it and keeps it in the static `_sharedHost`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (TransportOptions, IsAvailable, _container; e.g. `TransportOptions` at line 71).
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 · highlight.classifyCSharp (cyclomatic 76) · ×1
  • highlight.classifyCSharp (cyclomatic 76) site/lib/highlight.ts:617 — highlight.classifyCSharp has cyclomatic complexity 76 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: site/lib/highlight.ts holds 9 of the 19 methods over the threshold — including the worst — and 146 of the 223 points over it (65%), 9.7× the next-largest file (src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs at 15). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · highlight.contextualTypeRole (cyclomatic 45) · ×1
  • highlight.contextualTypeRole (cyclomatic 45) site/lib/highlight.ts:753 — highlight.contextualTypeRole has cyclomatic complexity 45 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: site/lib/highlight.ts holds 9 of the 19 methods over the threshold — including the worst — and 146 of the 223 points over it (65%), 9.7× the next-largest file (src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs at 15). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · RecurringCommandBackgroundService.ExecuteAsync (cyclomatic 30) · ×1
  • RecurringCommandBackgroundService.ExecuteAsync (cyclomatic 30) src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs:96 — RecurringCommandBackgroundService.ExecuteAsync has cyclomatic complexity 30 (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 · EfCoreOutboxStore.AddBatchAsync (cyclomatic 28) · ×1
  • EfCoreOutboxStore.AddBatchAsync (cyclomatic 28) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:578 — EfCoreOutboxStore.AddBatchAsync has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 589). 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.
D1 · Cyclomatic Complexity · highlight.classifyBash (cyclomatic 28) · ×1
  • highlight.classifyBash (cyclomatic 28) site/lib/highlight.ts:923 — highlight.classifyBash has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: site/lib/highlight.ts holds 9 of the 19 methods over the threshold — including the worst — and 146 of the 223 points over it (65%), 9.7× the next-largest file (src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs at 15). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · SingleStreamHandlerMediationEnumerable.MediateAsync (cyclomatic 27) · ×1
  • SingleStreamHandlerMediationEnumerable.MediateAsync (cyclomatic 27) src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:108 — SingleStreamHandlerMediationEnumerable.MediateAsync has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · highlight.positionalPropertyRole (cyclomatic 26) · ×1
  • highlight.positionalPropertyRole (cyclomatic 26) site/lib/highlight.ts:841 — highlight.positionalPropertyRole has cyclomatic complexity 26 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: site/lib/highlight.ts holds 9 of the 19 methods over the threshold — including the worst — and 146 of the 223 points over it (65%), 9.7× the next-largest file (src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs at 15). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · docs-article.DocsArticle (cyclomatic 24) · ×1
  • docs-article.DocsArticle (cyclomatic 24) site/components/docs-article.tsx:366 — docs-article.DocsArticle has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · search-box.SearchBox (cyclomatic 24) · ×1
  • search-box.SearchBox (cyclomatic 24) site/components/search-box.tsx:50 — search-box.SearchBox has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 133, 67, 92, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · highlight.findGenericEnd (cyclomatic 24) · ×1
  • highlight.findGenericEnd (cyclomatic 24) site/lib/highlight.ts:327 — highlight.findGenericEnd has cyclomatic complexity 24 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: site/lib/highlight.ts holds 9 of the 19 methods over the threshold — including the worst — and 146 of the 223 points over it (65%), 9.7× the next-largest file (src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs at 15). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpressions (cyclomatic 23) · ×1
  • CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpressions (cyclomatic 23) src/LiteBus.Analyzers/CommandWithResultScheduledToInboxAnalyzer.cs:309 — CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpressions has cyclomatic complexity 23 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · highlight.classifyGeneric (cyclomatic 22) · ×1
  • highlight.classifyGeneric (cyclomatic 22) site/lib/highlight.ts:1068 — highlight.classifyGeneric has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: site/lib/highlight.ts holds 9 of the 19 methods over the threshold — including the worst — and 146 of the 223 points over it (65%), 9.7× the next-largest file (src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs at 15). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · EfCoreInboxStore.AddBatchAsync (cyclomatic 21) · ×1
  • EfCoreInboxStore.AddBatchAsync (cyclomatic 21) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:530 — EfCoreInboxStore.AddBatchAsync has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 541). 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.
D1 · Cyclomatic Complexity · highlight.findGenericOpen (cyclomatic 21) · ×1
  • highlight.findGenericOpen (cyclomatic 21) site/lib/highlight.ts:380 — highlight.findGenericOpen has cyclomatic complexity 21 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: site/lib/highlight.ts holds 9 of the 19 methods over the threshold — including the worst — and 146 of the 223 points over it (65%), 9.7× the next-largest file (src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs at 15). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · highlight.isUsingOrNamespaceChain (cyclomatic 20) · ×1
  • highlight.isUsingOrNamespaceChain (cyclomatic 20) site/lib/highlight.ts:555 — highlight.isUsingOrNamespaceChain has cyclomatic complexity 20 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: site/lib/highlight.ts holds 9 of the 19 methods over the threshold — including the worst — and 146 of the 223 points over it (65%), 9.7× the next-largest file (src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs at 15). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · highlight.classifyXml (cyclomatic 19) · ×1
  • highlight.classifyXml (cyclomatic 19) site/lib/highlight.ts:985 — highlight.classifyXml has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: site/lib/highlight.ts holds 9 of the 19 methods over the threshold — including the worst — and 146 of the 223 points over it (65%), 9.7× the next-largest file (src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs at 15). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · docs-drawer.DocsDrawer (cyclomatic 18) · ×1
  • docs-drawer.DocsDrawer (cyclomatic 18) site/components/docs-drawer.tsx:19 — docs-drawer.DocsDrawer has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 57, 32, 95). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · PostgreSqlInboxStore.AddBatchAsync (cyclomatic 16) · ×1
  • PostgreSqlInboxStore.AddBatchAsync (cyclomatic 16) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:644 — PostgreSqlInboxStore.AddBatchAsync has cyclomatic complexity 16 (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 · PostgreSqlOutboxStore.AddBatchAsync (cyclomatic 16) · ×1
  • PostgreSqlOutboxStore.AddBatchAsync (cyclomatic 16) src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:680 — PostgreSqlOutboxStore.AddBatchAsync has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D10 · Test Quality · Fixed-sleep synchronisation · ×1
  • Fixed-sleep synchronisation: BatchAccept_WhenBufferFull_ShouldBlockUntilFlushCompletes tests/LiteBus.Inbox.UnitTests/Ingress/TransportInboxIngressConsumerTests.cs:218 — This test starts a background task and then orders itself against it with `Task.Delay(100)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
D12 · Dependency Hygiene · Prerelease dependency · ×1
  • Prerelease dependency: StyleCop.Analyzers — StyleCop.Analyzers resolves to 1.2.0-beta.556, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
D2 · Cognitive Complexity · EfCoreOutboxStore.AddBatchAsync (cognitive 69) · ×1
  • EfCoreOutboxStore.AddBatchAsync (cognitive 69) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:578 — EfCoreOutboxStore.AddBatchAsync has cognitive complexity 69 (threshold 15). Most of this is not in the body itself: 1 of the 69 points is its own statement and the rest belongs to one function literal inside it that branches (line 589). 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 · highlight.classifyCSharp (cognitive 68) · ×1
  • highlight.classifyCSharp (cognitive 68) site/lib/highlight.ts:617 — highlight.classifyCSharp has cognitive complexity 68 (threshold 15). Drivers by points: if/else 31 (34 pts), boolean chains 27, ternaries 4 (7 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · RecurringCommandBackgroundService.ExecuteAsync (cognitive 49) · ×1
  • RecurringCommandBackgroundService.ExecuteAsync (cognitive 49) src/LiteBus.Commands.Recurring/RecurringCommandBackgroundService.cs:96 — RecurringCommandBackgroundService.ExecuteAsync has cognitive complexity 49 (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 · highlight.contextualTypeRole (cognitive 46) · ×1
  • highlight.contextualTypeRole (cognitive 46) site/lib/highlight.ts:753 — highlight.contextualTypeRole has cognitive complexity 46 (threshold 15). Drivers by points: if/else 22 (29 pts), boolean chains 17 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · EfCoreInboxStore.AddBatchAsync (cognitive 38) · ×1
  • EfCoreInboxStore.AddBatchAsync (cognitive 38) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:530 — EfCoreInboxStore.AddBatchAsync has cognitive complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to one function literal inside it that branches (line 541). 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 · SingleStreamHandlerMediationEnumerable.MediateAsync (cognitive 38) · ×1
  • SingleStreamHandlerMediationEnumerable.MediateAsync (cognitive 38) src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:108 — SingleStreamHandlerMediationEnumerable.MediateAsync has cognitive complexity 38 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpressions (cognitive 34) · ×1
  • CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpressions (cognitive 34) src/LiteBus.Analyzers/CommandWithResultScheduledToInboxAnalyzer.cs:309 — CommandWithResultScheduledToInboxAnalyzer.GetCollectionElementExpressions has cognitive complexity 34 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · highlight.findGenericEnd (cognitive 33) · ×1
  • highlight.findGenericEnd (cognitive 33) site/lib/highlight.ts:327 — highlight.findGenericEnd has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (28 pts), boolean chains 4, loops 1 (nesting depth added 14). 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 · highlight.positionalPropertyRole (cognitive 32) · ×1
  • highlight.positionalPropertyRole (cognitive 32) site/lib/highlight.ts:841 — highlight.positionalPropertyRole has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 9, ternaries 1 (3 pts) (nesting depth added 11). 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 · SqsConsumer.RunConsumeLoopAsync (cognitive 29) · ×1
  • SqsConsumer.RunConsumeLoopAsync (cognitive 29) src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:245 — SqsConsumer.RunConsumeLoopAsync has cognitive complexity 29 (threshold 15). Of this number, 26 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DeclarationAnalysis.CollectDeclaringAttributes (cognitive 28) · ×1
  • DeclarationAnalysis.CollectDeclaringAttributes (cognitive 28) src/LiteBus.Analyzers/Analysis/DeclarationAnalysis.cs:776 — DeclarationAnalysis.CollectDeclaringAttributes 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 · highlight.isUsingOrNamespaceChain (cognitive 28) · ×1
  • highlight.isUsingOrNamespaceChain (cognitive 28) site/lib/highlight.ts:555 — highlight.isUsingOrNamespaceChain has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 10, loops 1 (nesting depth added 9). 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 · ProcessorBackgroundService.ExecuteAsync (cognitive 27) · ×1
  • ProcessorBackgroundService.ExecuteAsync (cognitive 27) src/LiteBus.Messaging/Processing/ProcessorBackgroundService[TProcessor].cs:106 — ProcessorBackgroundService.ExecuteAsync has cognitive complexity 27 (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 · highlight.findGenericOpen (cognitive 27) · ×1
  • highlight.findGenericOpen (cognitive 27) site/lib/highlight.ts:380 — highlight.findGenericOpen has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 2, loops 1 (nesting depth added 11). 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 · highlight.classifyBash (cognitive 27) · ×1
  • highlight.classifyBash (cognitive 27) site/lib/highlight.ts:923 — highlight.classifyBash has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · PostgreSqlInboxStore.AddBatchAsync (cognitive 26) · ×1
  • PostgreSqlInboxStore.AddBatchAsync (cognitive 26) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:644 — PostgreSqlInboxStore.AddBatchAsync has cognitive complexity 26 (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 · PostgreSqlOutboxStore.AddBatchAsync (cognitive 26) · ×1
  • PostgreSqlOutboxStore.AddBatchAsync (cognitive 26) src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:680 — PostgreSqlOutboxStore.AddBatchAsync has cognitive complexity 26 (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 · docs-article.DocsArticle (cognitive 26) · ×1
  • docs-article.DocsArticle (cognitive 26) site/components/docs-article.tsx:366 — docs-article.DocsArticle has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 11 (13 pts), if/else 5 (7 pts), boolean chains 4, loops 2 (nesting depth added 4). Of this number, 19 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · search-box.SearchBox (cognitive 24) · ×1
  • search-box.SearchBox (cognitive 24) site/components/search-box.tsx:50 — search-box.SearchBox has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 7 (8 pts), boolean chains 6 (nesting depth added 2). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 133, 67, 92, …). 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 · KafkaConsumer.StopAsync (cognitive 22) · ×1
  • KafkaConsumer.StopAsync (cognitive 22) src/LiteBus.Transport.Kafka/KafkaConsumer.cs:136 — KafkaConsumer.StopAsync has cognitive complexity 22 (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 · highlight.isInObjectCreation (cognitive 21) · ×1
  • highlight.isInObjectCreation (cognitive 21) site/lib/highlight.ts:458 — highlight.isInObjectCreation has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 2, loops 1 (nesting depth added 10). 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 · highlight.classifyXml (cognitive 20) · ×1
  • highlight.classifyXml (cognitive 20) site/lib/highlight.ts:985 — highlight.classifyXml has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · PostgreSqlIdempotencyStore.TryClaimAsync (cognitive 19) · ×1
  • PostgreSqlIdempotencyStore.TryClaimAsync (cognitive 19) src/LiteBus.Commands.Storage.PostgreSql/PostgreSqlIdempotencyStore.cs:87 — PostgreSqlIdempotencyStore.TryClaimAsync 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 · TransportInboxIngressConsumer.AcceptAndAcknowledgeBatchAsync (cognitive 19) · ×1
  • TransportInboxIngressConsumer.AcceptAndAcknowledgeBatchAsync (cognitive 19) src/LiteBus.Inbox.Ingress/TransportInboxIngressConsumer.cs:502 — TransportInboxIngressConsumer.AcceptAndAcknowledgeBatchAsync has cognitive complexity 19 (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 · SingleAsyncHandlerMediationStrategy.Mediate (cognitive 19) · ×1
  • SingleAsyncHandlerMediationStrategy.Mediate (cognitive 19) src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:36 — SingleAsyncHandlerMediationStrategy.Mediate 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 · DiagnosticCheckRunner.RunAsync (cognitive 19) · ×1
  • DiagnosticCheckRunner.RunAsync (cognitive 19) src/LiteBus.Runtime.Abstractions/Diagnostics/DiagnosticCheckRunner.cs:77 — DiagnosticCheckRunner.RunAsync has cognitive complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OrphanHandlerTagAnalyzer.GetHandlerTags (cognitive 18) · ×1
  • OrphanHandlerTagAnalyzer.GetHandlerTags (cognitive 18) src/LiteBus.Analyzers/OrphanHandlerTagAnalyzer.cs:209 — OrphanHandlerTagAnalyzer.GetHandlerTags has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RequiredDeclarationValidator.Validate (cognitive 18) · ×1
  • RequiredDeclarationValidator.Validate (cognitive 18) src/LiteBus.Messaging/Registry/RequiredDeclarationValidator.cs:29 — RequiredDeclarationValidator.Validate has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · docs-article.classifyBlockquote (cognitive 18) · ×1
  • docs-article.classifyBlockquote (cognitive 18) site/components/docs-article.tsx:242 — docs-article.classifyBlockquote has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 1 (nesting depth added 9). 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 · docs-drawer.DocsDrawer (cognitive 18) · ×1
  • docs-drawer.DocsDrawer (cognitive 18) site/components/docs-drawer.tsx:19 — docs-drawer.DocsDrawer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, ternaries 4, loops 2 (nesting depth added 1). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 57, 32, 95). 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 · highlight.classifyGeneric (cognitive 18) · ×1
  • highlight.classifyGeneric (cognitive 18) site/lib/highlight.ts:1068 — highlight.classifyGeneric has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9, boolean chains 7, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · CommandHandlerAnalysis.MatchesAnyMarker (cognitive 17) · ×1
  • CommandHandlerAnalysis.MatchesAnyMarker (cognitive 17) src/LiteBus.Analyzers/Analysis/CommandHandlerAnalysis.cs:184 — CommandHandlerAnalysis.MatchesAnyMarker has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgreSqlSchemaManager.ValidateCoreAsync (cognitive 17) · ×1
  • PostgreSqlSchemaManager.ValidateCoreAsync (cognitive 17) src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:404 — PostgreSqlSchemaManager.ValidateCoreAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgreSqlWorkSignal.RunListenerLoopAsync (cognitive 17) · ×1
  • PostgreSqlWorkSignal.RunListenerLoopAsync (cognitive 17) REDACTED:228 — PostgreSqlWorkSignal.RunListenerLoopAsync has cognitive complexity 17 (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 · AmqpConsumer.StartCoreAsync (cognitive 17) · ×1
  • AmqpConsumer.StartCoreAsync (cognitive 17) src/LiteBus.Transport.Amqp/AmqpConsumer.cs:96 — AmqpConsumer.StartCoreAsync has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 139). 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 · InboxPipelinedMessageProcessorOperations.PersistTerminalOutcomeAsync (cognitive 16) · ×1
  • InboxPipelinedMessageProcessorOperations.PersistTerminalOutcomeAsync (cognitive 16) src/LiteBus.Inbox/InboxPipelinedMessageProcessorOperations.cs:230 — InboxPipelinedMessageProcessorOperations.PersistTerminalOutcomeAsync 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.
D2 · Cognitive Complexity · OutboxPipelinedMessageProcessorOperations.PersistTerminalOutcomeAsync (cognitive 16) · ×1
  • OutboxPipelinedMessageProcessorOperations.PersistTerminalOutcomeAsync (cognitive 16) src/LiteBus.Outbox/OutboxPipelinedMessageProcessorOperations.cs:230 — OutboxPipelinedMessageProcessorOperations.PersistTerminalOutcomeAsync 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.
D2 · Cognitive Complexity · highlight.readTokenBackward (cognitive 16) · ×1
  • highlight.readTokenBackward (cognitive 16) site/lib/highlight.ts:265 — highlight.readTokenBackward has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 4). 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 · highlight.isAttributePosition (cognitive 16) · ×1
  • highlight.isAttributePosition (cognitive 16) site/lib/highlight.ts:499 — highlight.isAttributePosition has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 1 (nesting depth added 5). 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
D30 · Dependency Vulnerabilities · Medium CVE · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member pair (60 shared lines) · ×1
  • Near-duplicate member pair (60 shared lines) src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs:47 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs:47-153 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs:47-161 — These two members are variants of one another: 60 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2068 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2068-2091 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs:268-286 | src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:791-814 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:629-641 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:2092-2117 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:301-326 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:849-874 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:663-677 — These 8 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 8 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 8 times.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:887 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:887-959 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:970-1056 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1067-1153 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:925-997 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1008-1094 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1105-1191 — These 6 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 6 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 6 times.
D4 · Code Duplication · Duplicated block (83 lines × 2) · ×1
  • Duplicated block (83 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1929 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1929-2011 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1953-2035 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (80 lines × 2) · ×1
  • Duplicated block (80 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:599 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:599-678 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:642-721 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:599` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelopes` to `IReadOnlyList<InboxEnvelope>` in one and `IReadOnlyList<OutboxEnvelope>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (72–74 lines × 2) · ×1
  • Duplicated block (72–74 lines × 2) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:133 — src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:133-206 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs:108-179 — before extracting anything, compare `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs` and `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 194 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:133` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (49–63 lines × 5) · ×1
  • Duplicated block (49–63 lines × 5) src/LiteBus.Commands.Recurring.Storage.PostgreSql/PostgreSqlRecurringLeaseSchemaScripts.cs:23 — src/LiteBus.Commands.Recurring.Storage.PostgreSql/PostgreSqlRecurringLeaseSchemaScripts.cs:23-77 | src/LiteBus.Commands.Storage.PostgreSql/PostgreSqlIdempotencySchemaScripts.cs:23-81 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxSchemaScripts.cs:48-96 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxSchemaScripts.cs:54-116 | src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaSchemaScripts.cs:23-82 — before extracting anything, compare `src/LiteBus.Commands.Storage.PostgreSql/PostgreSqlIdempotencySchemaScripts.cs` and `src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaSchemaScripts.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxSchemaScripts.cs:48` 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 (59 lines × 2) · ×1
  • Duplicated block (59 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:716 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:716-774 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:754-812 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:716` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelopes` to `IReadOnlyList<InboxEnvelope>` in one and `IReadOnlyList<OutboxEnvelope>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (55 lines × 2) · ×1
  • Duplicated block (55 lines × 2) src/LiteBus.Extensions.AspNetCore/OutboxMessagePurgeBinding.cs:15 — src/LiteBus.Extensions.AspNetCore/OutboxMessagePurgeBinding.cs:15-69 | src/LiteBus.Extensions.AspNetCore/OutboxMessageQueryBinding.cs:20-74 — before extracting anything, compare `src/LiteBus.Extensions.AspNetCore/OutboxMessagePurgeBinding.cs` and `src/LiteBus.Extensions.AspNetCore/OutboxMessageQueryBinding.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (49 lines × 2) · ×1
  • Duplicated block (49 lines × 2) src/LiteBus.Extensions.AspNetCore/InboxMessagePurgeBinding.cs:15 — src/LiteBus.Extensions.AspNetCore/InboxMessagePurgeBinding.cs:15-63 | src/LiteBus.Extensions.AspNetCore/InboxMessageQueryBinding.cs:20-68 — before extracting anything, compare `src/LiteBus.Extensions.AspNetCore/InboxMessagePurgeBinding.cs` and `src/LiteBus.Extensions.AspNetCore/InboxMessageQueryBinding.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (44 lines × 2) · ×1
  • Duplicated block (44 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStoreOptions.cs:12 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStoreOptions.cs:12-55 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStoreOptions.cs:12-55 — 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 (41–46 lines × 2) · ×1
  • Duplicated block (41–46 lines × 2) src/LiteBus.Transport.Abstractions/TransportPublishRequest.cs:21 — src/LiteBus.Transport.Abstractions/TransportPublishRequest.cs:21-61 | src/LiteBus.Transport.Amqp/AmqpPublishRequest.cs:19-64 — 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 (42 lines × 2) · ×1
  • Duplicated block (42 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxMessageEntity.cs:61 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxMessageEntity.cs:61-102 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxMessageEntity.cs:66-107 — 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 (42–44 lines × 2) · ×1
  • Duplicated block (42–44 lines × 2) src/LiteBus.Inbox.Dispatch/TransportInboxDispatcher.cs:79 — src/LiteBus.Inbox.Dispatch/TransportInboxDispatcher.cs:79-120 | src/LiteBus.Outbox.Dispatch/TransportOutboxDispatcher.cs:88-131 — 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 (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) src/LiteBus.Inbox/InboxProcessorControl.cs:14 — src/LiteBus.Inbox/InboxProcessorControl.cs:14-53 | src/LiteBus.Outbox/OutboxProcessorControl.cs:14-53 — before extracting anything, compare `src/LiteBus.Inbox/InboxProcessorControl.cs` and `src/LiteBus.Outbox/OutboxProcessorControl.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (36–37 lines × 2) · ×1
  • Duplicated block (36–37 lines × 2) src/LiteBus.Inbox.Abstractions/Envelopes/InboxEnvelope.cs:72 — src/LiteBus.Inbox.Abstractions/Envelopes/InboxEnvelope.cs:72-108 | src/LiteBus.Outbox.Abstractions/Envelopes/OutboxEnvelope.cs:77-112 — 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 (31–33 lines × 3) · ×1
  • Duplicated block (31–33 lines × 3) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:174 — src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:174-206 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:176-206 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs:149-179 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:174` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) src/LiteBus.Inbox.Abstractions/InboxAcceptMetadata.cs:24 — src/LiteBus.Inbox.Abstractions/InboxAcceptMetadata.cs:24-56 | src/LiteBus.Outbox.Abstractions/OutboxEnqueueMetadata.cs:24-57 — 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 (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) src/LiteBus.Runtime.Extensions.Autofac.Hosting/AutofacDiagnosticHostingExtensions.cs:36 — src/LiteBus.Runtime.Extensions.Autofac.Hosting/AutofacDiagnosticHostingExtensions.cs:36-64 | src/LiteBus.Runtime.Extensions.Microsoft.Hosting/MicrosoftDiagnosticHostingExtensions.cs:38-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Runtime.Extensions.Autofac.Hosting/AutofacDiagnosticHostingExtensions.cs:36` 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 (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) src/LiteBus.Inbox.Abstractions/Store/InboxMessagePageCursor.cs:36 — src/LiteBus.Inbox.Abstractions/Store/InboxMessagePageCursor.cs:36-66 | src/LiteBus.Outbox.Abstractions/Store/OutboxMessagePageCursor.cs:36-66 — before extracting anything, compare `src/LiteBus.Inbox.Abstractions/Store/InboxMessagePageCursor.cs` and `src/LiteBus.Outbox.Abstractions/Store/OutboxMessagePageCursor.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (29 lines × 4) · ×1
  • Duplicated block (29 lines × 4) src/LiteBus.Extensions.AspNetCore/InboxMessagePurgeBinding.cs:36 — src/LiteBus.Extensions.AspNetCore/InboxMessagePurgeBinding.cs:36-64 | src/LiteBus.Extensions.AspNetCore/InboxMessageQueryBinding.cs:41-69 | src/LiteBus.Extensions.AspNetCore/OutboxMessagePurgeBinding.cs:42-70 | src/LiteBus.Extensions.AspNetCore/OutboxMessageQueryBinding.cs:47-75 — before extracting anything, compare `src/LiteBus.Extensions.AspNetCore/InboxMessagePurgeBinding.cs` and `src/LiteBus.Extensions.AspNetCore/InboxMessageQueryBinding.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) src/LiteBus.Outbox/OutboxEnvelopeFactory.cs:143 — src/LiteBus.Outbox/OutboxEnvelopeFactory.cs:143-172 | src/LiteBus.Outbox/OutboxEnvelopeFactory.cs:179-208 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (26–29 lines × 4) · ×1
  • Duplicated block (26–29 lines × 4) src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs:53 — src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs:53-79 | src/LiteBus.Inbox.Ingress.AzureServiceBus/AzureServiceBusInboxIngressModule.cs:54-82 | src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs:50-75 | src/LiteBus.Inbox.Ingress.Kafka/KafkaInboxIngressModule.cs:52-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs:53` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs:53` calls `ValidateReceiveBatchSize` and `src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs:50` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (28 lines × 3) · ×1
  • Duplicated block (28 lines × 3) src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:911 — src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:911-938 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1011-1038 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1111-1138 — all 3 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (28–29 lines × 2) · ×1
  • Duplicated block (28–29 lines × 2) src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs:47 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs:47-75 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs:47-74 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/InboxEntityFrameworkCoreModelExtensions.cs:47` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `entity` to `EntityTypeBuilder<InboxMessageEntity>` in one and `EntityTypeBuilder<OutboxMessageEntity>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (17–29 lines × 2) · ×1
  • Duplicated block (17–29 lines × 2) src/LiteBus.Messaging/Pipeline/MessageContextExtensions.cs:233 — src/LiteBus.Messaging/Pipeline/MessageContextExtensions.cs:233-261 | src/LiteBus.Messaging/Pipeline/MessageContextExtensions.cs:297-313 — 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/LiteBus.Messaging/Pipeline/MessageContextExtensions.cs:233` 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. 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 (27–28 lines × 2) · ×1
  • Duplicated block (27–28 lines × 2) src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1486 — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:1486-1512 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs:1602-1629 — before extracting anything, compare `src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs` and `src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `filter` to `InboxMessageFilter` in one and `OutboxMessageFilter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (26 lines × 4) · ×1
  • Duplicated block (26 lines × 4) src/LiteBus.Transport.AwsSqs/SqsPublisher.cs:51 — src/LiteBus.Transport.AwsSqs/SqsPublisher.cs:51-76 | src/LiteBus.Transport.AzureServiceBus/AzureServiceBusPublisher.cs:106-131 | src/LiteBus.Transport.InMemory/InMemoryPublisher.cs:47-72 | src/LiteBus.Transport.Kafka/KafkaPublisher.cs:71-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Transport.AwsSqs/SqsPublisher.cs:51` 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 (24–27 lines × 3) · ×1
  • Duplicated block (24–27 lines × 3) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:140 — src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:140-166 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs:115-141 | src/LiteBus.Messaging/MediationStrategies/SingleStreamHandlerMediationEnumerable[TMessage, TMessageResult].cs:130-153 — before extracting anything, compare `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs` and `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 194 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:140` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (26 lines × 3) · ×1
  • Duplicated block (26 lines × 3) src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:117 — src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:117-142 | src/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs:122-147 | src/LiteBus.Transport.InMemory/InMemoryConsumer.cs:99-124 — before extracting anything, compare `src/LiteBus.Transport.AwsSqs/SqsConsumer.cs` and `src/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:117` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/LiteBus.Transport.AwsSqs/SqsConsumer.cs:147` calls `SignalStopped` and `src/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs:148` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (20–27 lines × 2) · ×1
  • Duplicated block (20–27 lines × 2) src/LiteBus.Inbox/InboxEnvelopeFactory.cs:142 — src/LiteBus.Inbox/InboxEnvelopeFactory.cs:142-161 | src/LiteBus.Outbox/OutboxEnvelopeFactory.cs:227-253 — 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 (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) src/LiteBus.Inbox/InboxProcessorControl.cs:118 — src/LiteBus.Inbox/InboxProcessorControl.cs:118-143 | src/LiteBus.Outbox/OutboxProcessorControl.cs:118-143 — before extracting anything, compare `src/LiteBus.Inbox/InboxProcessorControl.cs` and `src/LiteBus.Outbox/OutboxProcessorControl.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (26–27 lines × 2) · ×1
  • Duplicated block (26–27 lines × 2) src/LiteBus.Inbox/InboxProcessorEnvelopeHandler.cs:163 — src/LiteBus.Inbox/InboxProcessorEnvelopeHandler.cs:163-189 | src/LiteBus.Outbox/OutboxProcessorEnvelopeHandler.cs:124-149 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox/InboxProcessorEnvelopeHandler.cs:163` 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 (25–26 lines × 2) · ×1
  • Duplicated block (25–26 lines × 2) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:82 — src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:82-106 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs:69-94 — before extracting anything, compare `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs` and `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 194 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:82` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs:68` calls `CreateScope` and `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:81` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×1
  • Duplicated block (21 lines × 3) src/LiteBus.Commands.Storage.Marten/MartenIdempotencyStore.cs:281 — src/LiteBus.Commands.Storage.Marten/MartenIdempotencyStore.cs:281-301 | src/LiteBus.Storage.EntityFrameworkCore/Stores/EfCoreUniqueViolation.cs:160-180 | src/LiteBus.Storage.PostgreSql/PostgreSqlConstraintRefusalClassifier.cs:107-127 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×1
  • Duplicated block (19 lines × 3) src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:134 — src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:134-152 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage, TMessageResult].cs:113-131 | src/LiteBus.Messaging/MediationStrategies/SingleAsyncHandlerMediationStrategy[TMessage].cs:109-127 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Events/MediationStrategies/AsyncBroadcastMediationStrategy[TMessage].cs:134` 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 (18–20 lines × 3) · ×1
  • Duplicated block (18–20 lines × 3) src/LiteBus.Inbox.Abstractions/InboxReceiptMapper.cs:86 — src/LiteBus.Inbox.Abstractions/InboxReceiptMapper.cs:86-105 | src/LiteBus.Messaging/DurableEnvelopeMetadataMapper.cs:118-135 | src/LiteBus.Outbox.Abstractions/OutboxReceiptMapper.cs:81-100 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×1
  • Duplicated block (18–20 lines × 2) src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:294 — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:294-313 | src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs:308-325 — before extracting anything, compare `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs` and `src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:294` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `InboxLeaseRequest` in one and `OutboxLeaseRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (16 lines × 5) · ×1
  • Duplicated block (16 lines × 5) src/LiteBus.Inbox.Ingress.Amqp/AmqpInboxIngressModule.cs:72 — src/LiteBus.Inbox.Ingress.Amqp/AmqpInboxIngressModule.cs:72-87 | src/LiteBus.Inbox.Ingress.AwsSqs/AwsSqsInboxIngressModule.cs:69-84 | src/LiteBus.Inbox.Ingress.AzureServiceBus/AzureServiceBusInboxIngressModule.cs:72-87 | src/LiteBus.Inbox.Ingress.InMemory/InMemoryInboxIngressModule.cs:65-80 | src/LiteBus.Inbox.Ingress.Kafka/KafkaInboxIngressModule.cs:67-82 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Ingress.Amqp/AmqpInboxIngressModule.cs:72` 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 (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2069 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2069-2077 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:2093-2101 | src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs:302-310 — before extracting anything, compare `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs` and `src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 387 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2069` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `envelope` to `InboxEnvelope` in one and `OutboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) src/LiteBus.Commands.Recurring.Storage.PostgreSql/PostgreSqlRecurringLeaseSchemaScripts.cs:86 — src/LiteBus.Commands.Recurring.Storage.PostgreSql/PostgreSqlRecurringLeaseSchemaScripts.cs:86-93 | src/LiteBus.Commands.Storage.PostgreSql/PostgreSqlIdempotencySchemaScripts.cs:90-97 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxSchemaScripts.cs:105-112 | src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxSchemaScripts.cs:125-132 | src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaSchemaScripts.cs:91-98 — before extracting anything, compare `src/LiteBus.Commands.Storage.PostgreSql/PostgreSqlIdempotencySchemaScripts.cs` and `src/LiteBus.Saga.Storage.PostgreSql/PostgreSqlSagaSchemaScripts.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2076 — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2076-2081 | src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs:271-276 | src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:799-804 | src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:632-637 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:2076` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `existing` to `InboxMessageEntity` in one and `InboxEnvelope` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) src/LiteBus.Commands/CommandAuditCompletionHandler.cs:34 — src/LiteBus.Commands/CommandAuditCompletionHandler.cs:34-39 | src/LiteBus.Events/EventAuditCompletionHandler.cs:43-48 | src/LiteBus.Queries/QueryAuditCompletionHandler.cs:34-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (111 lines × 2) · ×1
  • Duplicated block (111 lines × 2) src/LiteBus.Inbox/InboxProcessorLogMessages.cs:93 — src/LiteBus.Inbox/InboxProcessorLogMessages.cs:93-203 | src/LiteBus.Outbox/OutboxProcessorLogMessages.cs:93-203 — 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.
D5 · Coupling · Unstable project LiteBus.Inbox.Dispatch.InProcess · ×1
  • Unstable project LiteBus.Inbox.Dispatch.InProcess src/LiteBus.Inbox.Dispatch.InProcess/LiteBus.Inbox.Dispatch.InProcess.csproj:1 — LiteBus.Inbox.Dispatch.InProcess has instability 0.43 with 8 dependents.
D5 · Coupling · Unstable project LiteBus.Inbox.Ingress.Kafka · ×1
  • Unstable project LiteBus.Inbox.Ingress.Kafka src/LiteBus.Inbox.Ingress.Kafka/LiteBus.Inbox.Ingress.Kafka.csproj:1 — LiteBus.Inbox.Ingress.Kafka has instability 0.75 with 2 dependents.
D5 · Coupling · Unstable project LiteBus.Outbox.Dispatch.InProcess · ×1
  • Unstable project LiteBus.Outbox.Dispatch.InProcess src/LiteBus.Outbox.Dispatch.InProcess/LiteBus.Outbox.Dispatch.InProcess.csproj:1 — LiteBus.Outbox.Dispatch.InProcess has instability 0.50 with 6 dependents.
D8 · Code Coverage · No test project references LiteBus.ConsumerSmoke · ×1
  • No test project references LiteBus.ConsumerSmoke smoke/LiteBus.ConsumerSmoke/LiteBus.ConsumerSmoke.csproj — No test project in this repository references LiteBus.ConsumerSmoke (6 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 87.5% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references LiteBus.Messaging.Extensions.OpenTelemetry · ×1
  • No test project references LiteBus.Messaging.Extensions.OpenTelemetry src/LiteBus.Messaging.Extensions.OpenTelemetry/LiteBus.Messaging.Extensions.OpenTelemetry.csproj — No test project in this repository references LiteBus.Messaging.Extensions.OpenTelemetry (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 87.5% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage · No test project references LiteBus.Transport.Amqp.Extensions.OpenTelemetry · ×1
  • No test project references LiteBus.Transport.Amqp.Extensions.OpenTelemetry src/LiteBus.Transport.Amqp.Extensions.OpenTelemetry/LiteBus.Transport.Amqp.Extensions.OpenTelemetry.csproj — No test project in this repository references LiteBus.Transport.Amqp.Extensions.OpenTelemetry (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 87.5% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×1
  • Sync-over-async (deadlock risk) through `.Result` src/LiteBus.Transport.AzureServiceBus/AzureServiceBusConsumer.cs:325 — 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.
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×1
  • Owned disposable field is never released src/LiteBus.Inbox.Ingress/TransportInboxIngressConsumer.cs:61 — `TransportInboxIngressConsumer` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_batchFlushTimer` itself (line 61), which makes that instance its own. But `_batchFlushTimer` is named in none of the methods the disposal search covered: `Dispose` (line 204), `CancelBatchFlushTimer` (line 373) — 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` (`_batchFlushTimer?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) REDACTED:121 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Minor — 140 finding(s)
D12 · Dependency Hygiene · Deprecated · ×66
  • Deprecated: Microsoft.CodeAnalysis.Testing.Verifiers.XUnit tests/LiteBus.Analyzers.UnitTests/packages.lock.json:140 — Microsoft.CodeAnalysis.Testing.Verifiers.XUnit 1.1.2 — Legacy. It is resolved transitively in tests/LiteBus.Analyzers.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: System.Security.Cryptography.Pkcs tests/LiteBus.Analyzers.UnitTests/packages.lock.json:406 — System.Security.Cryptography.Pkcs 5.0.0 — Other,Legacy. It is resolved transitively in tests/LiteBus.Analyzers.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.assert tests/LiteBus.Analyzers.UnitTests/packages.lock.json:320 — xunit.assert 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.assert`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Analyzers.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.core tests/LiteBus.Analyzers.UnitTests/packages.lock.json:325 — xunit.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Analyzers.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.core tests/LiteBus.Analyzers.UnitTests/packages.lock.json:334 — xunit.extensibility.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Analyzers.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.execution tests/LiteBus.Analyzers.UnitTests/packages.lock.json:342 — xunit.extensibility.execution 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Analyzers.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.assert tests/LiteBus.Durable.IntegrationTests/packages.lock.json:636 — xunit.assert 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.assert`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Durable.IntegrationTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.core tests/LiteBus.Durable.IntegrationTests/packages.lock.json:641 — xunit.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Durable.IntegrationTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.core tests/LiteBus.Durable.IntegrationTests/packages.lock.json:650 — xunit.extensibility.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Durable.IntegrationTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.execution tests/LiteBus.Durable.IntegrationTests/packages.lock.json:658 — xunit.extensibility.execution 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Durable.IntegrationTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.assert tests/LiteBus.Enterprise.UnitTests/packages.lock.json:80 — xunit.assert 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.assert`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Enterprise.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.core tests/LiteBus.Enterprise.UnitTests/packages.lock.json:85 — xunit.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Enterprise.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.core tests/LiteBus.Enterprise.UnitTests/packages.lock.json:94 — xunit.extensibility.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Enterprise.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.execution tests/LiteBus.Enterprise.UnitTests/packages.lock.json:102 — xunit.extensibility.execution 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Enterprise.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.assert tests/LiteBus.Extensions.IntegrationTests/packages.lock.json:519 — xunit.assert 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.assert`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Extensions.IntegrationTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.core tests/LiteBus.Extensions.IntegrationTests/packages.lock.json:524 — xunit.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Extensions.IntegrationTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.core tests/LiteBus.Extensions.IntegrationTests/packages.lock.json:533 — xunit.extensibility.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Extensions.IntegrationTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.execution tests/LiteBus.Extensions.IntegrationTests/packages.lock.json:541 — xunit.extensibility.execution 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Extensions.IntegrationTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.assert tests/LiteBus.Extensions.UnitTests/packages.lock.json:333 — xunit.assert 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.assert`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Extensions.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.core tests/LiteBus.Extensions.UnitTests/packages.lock.json:338 — xunit.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Extensions.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.core tests/LiteBus.Extensions.UnitTests/packages.lock.json:347 — xunit.extensibility.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Extensions.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.execution tests/LiteBus.Extensions.UnitTests/packages.lock.json:355 — xunit.extensibility.execution 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Extensions.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.assert tests/LiteBus.Inbox.UnitTests/packages.lock.json:151 — xunit.assert 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.assert`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Inbox.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.core tests/LiteBus.Inbox.UnitTests/packages.lock.json:156 — xunit.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Inbox.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: xunit.extensibility.core tests/LiteBus.Inbox.UnitTests/packages.lock.json:165 — xunit.extensibility.core 2.9.3 — Legacy — the publisher's replacement is `xunit.v3.extensibility.core`; migrate the reference to it. It is resolved transitively in tests/LiteBus.Inbox.UnitTests/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • + 41 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate src/LiteBus.Inbox/InboxCleanupBackgroundService.cs:89 — `!_hostOptions.Enabled || _hostOptions.Retention is null` appears character-identically in 2 files — src/LiteBus.Inbox/InboxCleanupBackgroundService.cs, src/LiteBus.Outbox/OutboxCleanupBackgroundService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Storage.EntityFrameworkCore/LiteBusInboxSaveChangesInterceptor.cs:80 — `!_pendingEnvelopesByContext.TryGetValue(context, out var pending) || pending.Count == 0` appears character-identically in 2 files — src/LiteBus.Inbox.Storage.EntityFrameworkCore/LiteBusInboxSaveChangesInterceptor.cs, src/LiteBus.Outbox.Storage.EntityFrameworkCore/LiteBusOutboxSaveChangesInterceptor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate tests/LiteBus.Transport.IntegrationTesting/InMemory/InMemoryTransportTestInfrastructure.cs:63 — `!condition() && Environment.TickCount64 < deadline` appears character-identically in 2 files — tests/LiteBus.Transport.IntegrationTesting/InMemory/InMemoryTransportTestInfrastructure.cs, tests/LiteBus.Transport.IntegrationTesting/PollingWait.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Runtime.Abstractions/Dependencies/DependencyDescriptor.cs:381 — `!implementationType.IsClass || implementationType.IsAbstract` appears character-identically in 2 files — src/LiteBus.Runtime.Abstractions/Dependencies/DependencyDescriptor.cs, src/LiteBus.Runtime/Modules/ModuleConfiguration.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Storage.EntityFrameworkCore/LiteBusInboxSaveChangesInterceptor.cs:183 — `!seenIds.Add(envelope.Id) && envelope.IdempotencyConflictMode == IdempotencyConflictMode.ReturnExisting` appears character-identically in 2 files — src/LiteBus.Inbox.Storage.EntityFrameworkCore/LiteBusInboxSaveChangesInterceptor.cs, src/LiteBus.Outbox.Storage.EntityFrameworkCore/LiteBusOutboxSaveChangesInterceptor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Abstractions/InboxReceiptMapper.cs:94 — `!string.IsNullOrWhiteSpace(correlationId) && !string.IsNullOrWhiteSpace(causationId)` appears character-identically in 4 files — src/LiteBus.Inbox.Abstractions/InboxReceiptMapper.cs, src/LiteBus.Inbox.Ingress/TransportInboxIngressMapper.cs, src/LiteBus.Messaging/DurableEnvelopeMetadataMapper.cs, src/LiteBus.Outbox.Abstractions/OutboxReceiptMapper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:690 — `!string.IsNullOrWhiteSpace(envelope.IdempotencyKey) && _idempotencyIndex.TryGetValue(CreateScopeKey(envelope.TenantId, envelope.IdempotencyK…` appears character-identically in 2 files — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs, src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:611 — `!string.IsNullOrWhiteSpace(envelope.IdempotencyKey) && pendingIdempotencyKeys.TryGetValue( EfCoreIdempotencyResolution.CreateScopeKey(envelo…` appears character-identically in 2 files — src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs, src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Storage.EntityFrameworkCore/LiteBusInboxSaveChangesInterceptor.cs:95 — `!string.IsNullOrWhiteSpace(envelope.IdempotencyKey) && string.Equals(candidate.IdempotencyKey, envelope.IdempotencyKey, StringComparison.Ord…` appears character-identically in 2 files — src/LiteBus.Inbox.Storage.EntityFrameworkCore/LiteBusInboxSaveChangesInterceptor.cs, src/LiteBus.Outbox.Storage.EntityFrameworkCore/LiteBusOutboxSaveChangesInterceptor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Abstractions/InboxReceiptMapper.cs:87 — `!string.IsNullOrWhiteSpace(traceContext) && !string.IsNullOrWhiteSpace(correlationId) && !string.IsNullOrWhiteSpace(causationId)` appears character-identically in 4 files — src/LiteBus.Inbox.Abstractions/InboxReceiptMapper.cs, src/LiteBus.Inbox.Ingress/TransportInboxIngressMapper.cs, src/LiteBus.Messaging/DurableEnvelopeMetadataMapper.cs, src/LiteBus.Outbox.Abstractions/OutboxReceiptMapper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox/InboxObservableMetrics.cs:154 — `DateTimeOffset.UtcNow >= _cacheExpiresAt && _refreshTask.IsCompleted && Volatile.Read(ref _disposeState) == 0` appears character-identically in 2 files — src/LiteBus.Inbox/InboxObservableMetrics.cs, src/LiteBus.Outbox/OutboxObservableMetrics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Messaging.Abstractions/Handler/Refusal/Refusal.cs:164 — `Outcome == other.Outcome && string.Equals(Reason, other.Reason, StringComparison.Ordinal) && string.Equals(Code, other.Code, StringCompariso…` appears character-identically in 3 files — src/LiteBus.Messaging.Abstractions/Handler/Refusal/Refusal.cs, src/LiteBus.Messaging.Abstractions/Pipeline/MediationDecision.cs, src/LiteBus.Messaging.Abstractions/Pipeline/MediationResult.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox/InboxManager.cs:196 — `_cleanupHostOptions.Retention is null || _cleanupHostOptions.Retention <= TimeSpan.Zero` appears character-identically in 2 files — src/LiteBus.Inbox/InboxManager.cs, src/LiteBus.Outbox/OutboxManager.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:144 — `_envelopes.TryGetValue(messageId, out var envelope) && !string.IsNullOrWhiteSpace(envelope.IdempotencyKey)` appears character-identically in 2 files — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs, src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:698 — `_options.Capacity > 0 && _envelopes.Count >= _options.Capacity` appears character-identically in 2 files — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs, src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs:837 — `_transactionConnection is null || _transaction is null` appears character-identically in 2 files — src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxStore.cs, src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxStore.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs:239 — `candidate.Id == envelope.Id || !string.IsNullOrWhiteSpace(envelope.IdempotencyKey) && string.Equals(candidate.IdempotencyKey, envelope.Idemp…` appears character-identically in 2 files — src/LiteBus.Inbox.Storage.EntityFrameworkCore/TransactionalInbox[TContext].cs, src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutbox[TContext].cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Analyzers/Analysis/HandlerRegistrationCollector.cs:107 — `compilation.GetAssemblyOrModuleSymbol(reference) is not IAssemblySymbol assemblySymbol || !HandlerAnalysis.ShouldScanReferencedAssembly(asse…` appears character-identically in 2 files — src/LiteBus.Analyzers/Analysis/HandlerRegistrationCollector.cs, src/LiteBus.Analyzers/Analysis/MessageTypeCollector.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Commands/CommandModule.cs:101 — `configuration.TryGetContext<LiteBusCompositionSummary>(out var summary) && summary is not null` appears character-identically in 3 files — src/LiteBus.Commands/CommandModule.cs, src/LiteBus.Events/EventModule.cs, src/LiteBus.Queries/QueryModule.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Commands.Recurring/CommandModuleBuilderRecurringExtensions.cs:82 — `contract.IsGenericType && contract.GetGenericTypeDefinition() == typeof(ICommand<>)` appears character-identically in 3 files — src/LiteBus.Commands.Recurring/CommandModuleBuilderRecurringExtensions.cs, src/LiteBus.Commands.Recurring/RecurringCommandContracts.cs, src/LiteBus.Commands/Idempotency/IdempotentCommandShortcut[TCommand].cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Commands/CommandModuleBuilder.cs:330 — `contractDefinition == typeof(IMessageDefinition<,>) || contractDefinition == typeof(IMessageDefinition<>)` appears character-identically in 3 files — src/LiteBus.Commands/CommandModuleBuilder.cs, src/LiteBus.Events/EventModuleBuilder.cs, src/LiteBus.Queries/QueryModuleBuilder.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs:91 — `current.Name == "DbContext" && current is INamedTypeSymbol named && named.TypeKind == TypeKind.Class && named.ContainingNamespace?.ToDisplay…` appears character-identically in 2 files — src/LiteBus.Analyzers/TransactionalInboxWithoutDbContextAnalyzer.cs, src/LiteBus.Analyzers/TransactionalOutboxWithoutDbContextAnalyzer.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Messaging/Registry/MessageCatalog.cs:35 — `descriptor.MessageType.IsAbstract || descriptor.MessageType.IsInterface` appears character-identically in 2 files — src/LiteBus.Messaging/Registry/MessageCatalog.cs, src/LiteBus.Messaging/Registry/RequiredDeclarationValidator.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox/InboxProcessorEnvelopeHandler.cs:171 — `envelope.AttemptCount >= options.Retry.MaxAttempts || !MediationExceptionFilters.IsRetryableDispatchException(exception) || IsPermanent(opti…` appears character-identically in 2 files — src/LiteBus.Inbox/InboxProcessorEnvelopeHandler.cs, src/LiteBus.Outbox/OutboxProcessorEnvelopeHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs:639 — `envelope.CreatedAt > cursorCreatedAt || envelope.CreatedAt == cursorCreatedAt && envelope.Id.CompareTo(cursorMessageId) > 0` appears character-identically in 2 files — src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStore.cs, src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStore.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X4 · Structured logging · Interpolated log message defeats structured logging · ×19
  • Interpolated log message defeats structured logging src/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:54 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:80 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:88 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:117 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:122 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:134 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:149 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:197 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:266 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:426 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:464 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:496 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:522 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:585 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaManager.cs:672 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaVersionStore.cs:59 — 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/LiteBus.Storage.PostgreSql/PostgreSqlSchemaVersionStore.cs:176 — 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.
D27 · Navigability · Pass-through layer · ×5
  • Pass-through layer src/LiteBus.Inbox.Storage.PostgreSql/PostgreSqlInboxWorkSignal.cs:13 — PostgreSqlInboxWorkSignal: all 3 public methods forward their arguments unchanged to _inner and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _inner directly, or give the layer a job.
  • Pass-through layer src/LiteBus.Outbox.Storage.EntityFrameworkCore/TransactionalOutboxAdapter[TContext].cs:21 — TransactionalOutboxAdapter: all 3 public methods forward their arguments unchanged to _inner and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _inner directly, or give the layer a job.
  • Pass-through layer src/LiteBus.Outbox.Storage.PostgreSql/PostgreSqlOutboxWorkSignal.cs:13 — PostgreSqlOutboxWorkSignal: all 3 public methods forward their arguments unchanged to _inner and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _inner directly, or give the layer a job.
  • Pass-through layer src/LiteBus.Testing.DurableMessaging/TestInboxStore.cs:21 — TestInboxStore: all 14 public methods forward their arguments unchanged to _inner and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _inner directly, or give the layer a job.
  • Pass-through layer src/LiteBus.Testing.DurableMessaging/TestOutboxStore.cs:21 — TestOutboxStore: all 15 public methods forward their arguments unchanged to _inner and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _inner directly, or give the layer a job.
D18 · Solution Shape · Shell project · ×3
  • Shell project: LiteBus.Events.Extensions.Autofac src/LiteBus.Events.Extensions.Autofac/LiteBus.Events.Extensions.Autofac.csproj — `LiteBus.Events.Extensions.Autofac` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
  • Shell project: LiteBus.Messaging.Extensions.Autofac src/LiteBus.Messaging.Extensions.Autofac/LiteBus.Messaging.Extensions.Autofac.csproj — `LiteBus.Messaging.Extensions.Autofac` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
  • Shell project: LiteBus.Queries.Extensions.Autofac src/LiteBus.Queries.Extensions.Autofac/LiteBus.Queries.Extensions.Autofac.csproj — `LiteBus.Queries.Extensions.Autofac` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
D24 · Comment Value · redundant comment · ×3
  • redundant comment src/LiteBus.Messaging/Mediator/MessageMediator.cs:118 — "Find the message descriptor." repeats the code it sits on: 3 of its 3 words (find, message, descriptor) are already in `var descriptor = request.MessageResolveStrategy.Find(messageType, _messageReader);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/LiteBus.Mediator.UnitTests/UseCases/Messaging/MessageRegistryTests.cs:200 — "Act - register the open generic handler" repeats the code it sits on: 4 of its 5 words (register, open, generic, handler) are already in `registry.Register(typeof(OpenGenericTestPreHandler<>));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/LiteBus.Mediator.UnitTests/UseCases/Messaging/MessageRegistryTests.cs:215 — "Register the open generic handler first" repeats the code it sits on: 4 of its 5 words (register, open, generic, handler) are already in `registry.Register(typeof(OpenGenericTestPreHandler<>));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
C5 · Data-Subject Rights · Partial data-subject-rights support · ×1
  • Partial data-subject-rights support — Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
D12 · Dependency Hygiene · Outdated (npm) · ×1
  • Outdated (npm): nanoid — nanoid 3.3.20 → 6.0.2 available.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion src/LiteBus.Messaging.Abstractions/LiteBus.Messaging.Abstractions.csproj:1 — `LiteBus.Messaging.Abstractions` overshoots its size bounds (9902 LoC, 152 public types across 1 namespaces). 1 of 106 project(s) overshoot their size bounds, lowering Project Cohesion to 9.8/10. Review these for cohesion — split a project that spans unrelated responsibilities.
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
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D39 · IL Efficiency · IL efficiency · ×1
  • IL efficiency: 7 authored method(s) exceed the IL budget src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs:48 — 7 of 3654 first-party methods compile to oversized IL bodies (> 250 instructions); worst: LiteBus.Outbox.Storage.EntityFrameworkCore.OutboxEntityFrameworkCoreModelExtensions.ConfigureOutboxMessageEntity @ src/LiteBus.Outbox.Storage.EntityFrameworkCore/OutboxEntityFrameworkCoreModelExtensions.cs:48, 826 IL instructions; that pulled this dimension to 10.0/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 · ADRs not easily discoverable · ×1
  • ADRs not easily discoverable — 1 ADR-shaped document(s) detected by content — `site/content/docs/architecture/decisions.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
P12 · CI test-gate honesty · Sleep-based test synchronization · ×1
  • Sleep-based test synchronization — 144 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 13/34 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 34, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation benchmarks/Directory.Packages.props:3 — `benchmarks/Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 311/331 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X2 · Cancellation propagation · Some async methods drop the CancellationToken they accept · ×1
  • Some async methods drop the CancellationToken they accept — 5 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.4 `!` suppressions per 1k syntax nodes — 103 suppression(s) across the 249721 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/LiteBus.Transport.AwsSqs/SqsMessageMapper.cs:176 — `IsValidUtf8Text` swallows `DecoderFallbackException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Minor — 101 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×64
  • Outdated (npm): @cfworker/json-schema — @cfworker/json-schema 4.1.1 → 4.1.6 available.
  • Outdated (npm): @fumadocs/local-content — @fumadocs/local-content 0.2.2 → 0.3.0 available.
  • Outdated (npm): @fumadocs/local-md — @fumadocs/local-md 0.3.5 → 0.4.0 available.
  • Outdated (npm): @modelcontextprotocol/server — @modelcontextprotocol/server 2.0.0-alpha.4 → 2.4.0 available.
  • Outdated (npm): @next/env — @next/env 16.4.2 → 16.4.5 available.
  • Outdated (npm): @next/swc-darwin-arm64 — @next/swc-darwin-arm64 16.4.2 → 16.4.5 available.
  • Outdated (npm): @next/swc-darwin-x64 — @next/swc-darwin-x64 16.4.2 → 16.4.5 available.
  • Outdated (npm): @next/swc-linux-arm64-gnu — @next/swc-linux-arm64-gnu 16.4.2 → 16.4.5 available.
  • Outdated (npm): @next/swc-linux-arm64-musl — @next/swc-linux-arm64-musl 16.4.2 → 16.4.5 available.
  • Outdated (npm): @next/swc-linux-x64-gnu — @next/swc-linux-x64-gnu 16.4.2 → 16.4.5 available.
  • Outdated (npm): @next/swc-linux-x64-musl — @next/swc-linux-x64-musl 16.4.2 → 16.4.5 available.
  • Outdated (npm): @next/swc-win32-arm64-msvc — @next/swc-win32-arm64-msvc 16.4.2 → 16.4.5 available.
  • Outdated (npm): @next/swc-win32-x64-msvc — @next/swc-win32-x64-msvc 16.4.2 → 16.4.5 available.
  • Outdated (npm): @scalar/openapi-types — @scalar/openapi-types 0.8.0 → 0.9.8 available.
  • Outdated (npm): @shikijs/core — @shikijs/core 4.5.0 → 4.6.0 available.
  • Outdated (npm): @shikijs/engine-javascript — @shikijs/engine-javascript 4.5.0 → 4.6.0 available.
  • Outdated (npm): @shikijs/engine-oniguruma — @shikijs/engine-oniguruma 4.5.0 → 4.6.0 available.
  • Outdated (npm): @shikijs/langs — @shikijs/langs 4.5.0 → 4.6.0 available.
  • Outdated (npm): @shikijs/primitive — @shikijs/primitive 4.5.0 → 4.6.0 available.
  • Outdated (npm): @shikijs/themes — @shikijs/themes 4.5.0 → 4.6.0 available.
  • Outdated (npm): @shikijs/types — @shikijs/types 4.5.0 → 4.6.0 available.
  • Outdated (npm): @shikijs/vscode-textmate — @shikijs/vscode-textmate 10.0.2 → 10.1.0 available.
  • Outdated (npm): @swc/helpers — @swc/helpers 0.5.23 → 0.5.24 available.
  • Outdated (npm): @toon-format/toon — @toon-format/toon 2.3.1 → 4.4.0 available.
  • Outdated (npm): @types/estree — @types/estree 1.0.9 → 1.0.10 available.
  • + 39 more in this group — see findings.md.
D24 · Comment Value · doc comments repeat the names · ×28
  • doc comments repeat the names src/LiteBus.Analyzers/Analysis/ContractRegistrationAnalysis.cs:16 — 35 of 472 documented parameters and 0 of 405 summaries in `LiteBus.Analyzers` only repeat the member or parameter name (e.g. "Types registered through ." for `registeredTypes`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names tests/LiteBus.Analyzers.UnitTests/AnalyzerTest.cs:76 — 1 of 59 documented parameters and 0 of 309 summaries in `LiteBus.Analyzers.UnitTests` only repeat the member or parameter name (e.g. "The expected diagnostics." for `expectedDiagnostics`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/LiteBus.Commands.Recurring/RecurringCommandHostOptions.cs:223 — 1 of 50 documented parameters and 0 of 59 summaries in `LiteBus.Commands.Recurring` only repeat the member or parameter name (e.g. "The property name." for `propertyName`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names smoke/LiteBus.ConsumerSmoke/SmokeDbContext.cs:29 — 0 of 13 documented parameters and 2 of 16 summaries in `LiteBus.ConsumerSmoke` only repeat the member or parameter name (e.g. "Gets the inbox messages." for `InboxMessages`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names tests/LiteBus.Durable.IntegrationTests/Ingress/AwsSqs/AwsSqsInboxIngressEndToEndIntegrationTests.cs:120 — 7 of 181 documented parameters and 0 of 308 summaries in `LiteBus.Durable.IntegrationTests` only repeat the member or parameter name (e.g. "The ingress queue URL." for `ingressQueueUrl`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/LiteBus.DurableMessaging.Abstractions/DurableMessaging/DurableIdempotencyScope.cs:19 — 1 of 97 documented parameters and 0 of 172 summaries in `LiteBus.DurableMessaging.Abstractions` only repeat the member or parameter name (e.g. "The idempotency key." for `idempotencyKey`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names REDACTED:327 — 0 of 174 documented parameters and 2 of 152 summaries in `LiteBus.Extensions.AspNetCore` only repeat the member or parameter name (e.g. "Returns inbox status counts." for `GetInboxStatusCountsAsync`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names tests/LiteBus.Extensions.UnitTests/Autofac/UseCases/RegisterComponentCommandPostHandler.cs:5 — 0 of 3 documented parameters and 2 of 32 summaries in `LiteBus.Extensions.UnitTests` only repeat the member or parameter name (e.g. "A post-handler for ." for `RegisterComponentCommandPostHandler`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/LiteBus.Inbox/ModuleRegistryExtensions.cs:33 — 2 of 173 documented parameters and 0 of 243 summaries in `LiteBus.Inbox` only repeat the member or parameter name (e.g. "The module registry." for `moduleRegistry`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/LiteBus.Inbox.Storage.EntityFrameworkCore/EfCoreInboxStore.cs:1469 — 1 of 153 documented parameters and 0 of 149 summaries in `LiteBus.Inbox.Storage.EntityFrameworkCore` only repeat the member or parameter name (e.g. "The cancellation token." for `cancellationToken`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/LiteBus.Inbox.Storage.InMemory/InMemoryInboxStorageModuleBuilder.cs:53 — 1 of 34 documented parameters and 0 of 41 summaries in `LiteBus.Inbox.Storage.InMemory` only repeat the member or parameter name (e.g. "The time provider instance." for `timeProvider`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names tests/LiteBus.Inbox.UnitTests/InboxWriterTestFactory.cs:15 — 1 of 106 documented parameters and 2 of 381 summaries in `LiteBus.Inbox.UnitTests` only repeat the member or parameter name (e.g. "The contract registry." for `contractRegistry`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names tests/LiteBus.Mediator.UnitTests/Auditing/AuditTestTypes.cs:405 — 0 of 275 documented parameters and 9 of 1129 summaries in `LiteBus.Mediator.UnitTests` only repeat the member or parameter name (e.g. "The first declaration for ." for `FirstDoubleDeclaration`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/LiteBus.Messaging/Extensions/ServiceProviderExtensions.cs:16 — 8 of 579 documented parameters and 0 of 574 summaries in `LiteBus.Messaging` only repeat the member or parameter name (e.g. "The service provider instance." for `serviceProvider`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/LiteBus.Messaging.Abstractions/Exceptions/AmbiguousMessageResolveException.cs:65 — 10 of 485 documented parameters and 7 of 768 summaries in `LiteBus.Messaging.Abstractions` only repeat the member or parameter name (e.g. "The resolve strategy type." for `resolveStrategyType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/LiteBus.Outbox/ModuleRegistryExtensions.cs:33 — 2 of 190 documented parameters and 0 of 266 summaries in `LiteBus.Outbox` only repeat the member or parameter name (e.g. "The module registry." for `moduleRegistry`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/LiteBus.Outbox.Storage.EntityFrameworkCore/EfCoreOutboxStore.cs:1554 — 1 of 148 documented parameters and 0 of 155 summaries in `LiteBus.Outbox.Storage.EntityFrameworkCore` only repeat the member or parameter name (e.g. "The cancellation token." for `cancellationToken`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/LiteBus.Outbox.Storage.InMemory/InMemoryOutboxStorageModuleBuilder.cs:36 — 1 of 37 documented parameters and 0 of 45 summaries in `LiteBus.Outbox.Storage.InMemory` only repeat the member or parameter name (e.g. "The time provider instance." for `timeProvider`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names tests/LiteBus.Outbox.UnitTests/OutboxWriterTestFactory.cs:15 — 1 of 59 documented parameters and 2 of 351 summaries in `LiteBus.Outbox.UnitTests` only repeat the member or parameter name (e.g. "The contract registry." for `contractRegistry`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/LiteBus.Runtime.Abstractions/Dependencies/DependencyDescriptor.cs:316 — 1 of 141 documented parameters and 2 of 150 summaries in `LiteBus.Runtime.Abstractions` only repeat the member or parameter name (e.g. "Returns the hash code for this instance." for `GetHashCode`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names tests/LiteBus.Runtime.UnitTests/ArchitectureDependencyPolicyTests.cs:315 — 3 of 28 documented parameters and 0 of 95 summaries in `LiteBus.Runtime.UnitTests` only repeat the member or parameter name (e.g. "The referenced project." for `referencedProject`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/LiteBus.Saga/SagaExecutionContext.cs:90 — 6 of 87 documented parameters and 0 of 102 summaries in `LiteBus.Saga` only repeat the member or parameter name (e.g. "The current state object." for `state`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/LiteBus.Storage.EntityFrameworkCore/EfCoreRelationalLeaseExecutor.cs:25 — 26 of 132 documented parameters and 2 of 91 summaries in `LiteBus.Storage.EntityFrameworkCore` only repeat the member or parameter name (e.g. "The schema name." for `schemaName`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names tests/LiteBus.Storage.IntegrationTests/PostgreSql/PostgreSqlOutboxTransactionalIntegrationTests.cs:139 — 6 of 250 documented parameters and 3 of 560 summaries in `LiteBus.Storage.IntegrationTests` only repeat the member or parameter name (e.g. "The orders table name." for `ordersTableName`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/LiteBus.Storage.PostgreSql/Stores/PostgreSqlBatchIdempotencyLookup.cs:128 — 2 of 238 documented parameters and 0 of 217 summaries in `LiteBus.Storage.PostgreSql` only repeat the member or parameter name (e.g. "The idempotency key." for `IdempotencyKey`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • + 3 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated · ×9
  • Outdated: Microsoft.CodeAnalysis.Analyzers — Microsoft.CodeAnalysis.Analyzers 3.3.4 → 5.9.0 available (referenced by LiteBus.Analyzers).
  • Outdated: Microsoft.CodeAnalysis.CSharp — Microsoft.CodeAnalysis.CSharp 4.8.0 → 5.9.0 available (referenced by LiteBus.Analyzers).
  • Outdated: System.Collections.Immutable — System.Collections.Immutable 8.0.0 → 10.0.14 available (referenced by LiteBus.Analyzers).
  • Outdated: Npgsql — Npgsql 9.0.5 → 10.0.3 available (referenced by LiteBus.Commands.Recurring.Storage.PostgreSql).
  • Outdated: Marten — Marten 9.57.0 → 9.58.0 available (referenced by LiteBus.Commands.Storage.Marten).
  • Outdated: AWSSDK.SQS — AWSSDK.SQS 4.0.100.23 → 4.0.100.25 available (referenced by LiteBus.Transport.AwsSqs).
  • Outdated: Microsoft.CodeAnalysis.CSharp.Workspaces — Microsoft.CodeAnalysis.CSharp.Workspaces 4.8.0 → 5.9.0 available (referenced by LiteBus.Analyzers.UnitTests).
  • Outdated: Microsoft.CodeAnalysis.Workspaces.Common — Microsoft.CodeAnalysis.Workspaces.Common 4.8.0 → 5.9.0 available (referenced by LiteBus.Analyzers.UnitTests).
  • Outdated: SQLitePCLRaw.bundle_e_sqlite3 — SQLitePCLRaw.bundle_e_sqlite3 2.1.14 → 3.0.5 available (referenced by LiteBus.Storage.IntegrationTests).

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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d5f410a28f07465e9c91b3e73493ad0b/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d5f410a28f07465e9c91b3e73493ad0b/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .31artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list LiteBus.slnx package --vulnerable --include-transitive --format json1artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .3artifacts/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 76 file(s) — `site/lib/source.ts`, `src/LiteBus.Commands.Abstractions/ICommand.cs`, `src/LiteBus.Commands.Abstractions/ICommandCompletionHandler.cs`, `src/LiteBus.Commands.Abstractions/ICommandCompletionHandler[TCommand, TCommandResult].cs`, `src/LiteBus.Commands.Abstractions/ICommandCompletionHandler[TCommand].cs`, … (+71 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
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 01a1bbcd-03b5-7baf-a9b4-ea585cacf26f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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