Executive summary
zarusz/SlimMessageBus falls short of our standard for production because we found no access checks on the code's endpoints or handlers and it has pipeline tools referenced by a changeable name. It scores 53 out of 100 and is rated Adequate, and 46 of its 80 critical findings are security problems.
Security and Compliance, at 43, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 8 points. Replacing the two exposed passwords or keys and switching the old ones off comes next, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 62.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Nineteen weaknesses in the code could be used by an attacker, and six errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, fixing the weaknesses the scanner points to and handling or logging the ignored errors would close these risks. Updating the vulnerable packages would fix the package with a known security hole, and the two passwords or keys in the code and the password or key in the code's history need replacing, with the old ones switched off. The 12 pieces of business logic tied to the database or web code need separating from the database and web code.
The product code is 27,083 lines, about €110,000 to rebuild.
If Security and Compliance rose from 43 to 70, the lowest score rated Strong, the score would rise from 53 to about 62.
New since the last survey: 15 findings
- Code Duplication · Duplicated block (6 lines × 3) src/SlimMessageBus.Host.Outbox.Sql/ObjectToInferredTypesConverter.cs
- Code Duplication · Duplicated block (6 lines × 2) src/SlimMessageBus.Host.PostgreSql/Configuration/PostgreSqlMessageBusSettings.cs
- Code Duplication · Duplicated block (11 lines × 2) src/Samples/Sample.OutboxWebApi/Program.cs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Outbox / dual-write · Dual write (no outbox): NatsMessageBus.ProduceToTransport src/SlimMessageBus.Host.Nats/NatsMessageBus.cs
- Stateful singletons · Process-global static state: MessageBus src/SlimMessageBus/MessageBus.cs
- Stateful singletons · Process-global static state: Secrets src/Tools/SecretStore/Secrets.cs
- Schema migrations · Schema created by a CREATE TABLE statement outside the migrations REDACTED
- Schema migrations · Schema created by a CREATE TABLE statement outside the migrations src/SlimMessageBus.Host.PostgreSql/PostgreSqlTopologyService.cs
- Schema migrations · Schema created by a CREATE TABLE statement outside the migrations src/SlimMessageBus.Host.Outbox.PostgreSql/Services/PostgreSqlOutboxMigrationService.cs
Fixed since the last survey: 118 findings
- Explicit Debt · Dead code: DeleteFile src/Samples/Sample.Images.FileStore/IFileStore.cs
- Explicit Debt · Dead code: CustomerUpdated src/Tests/SlimMessageBus.Host.Memory.Test/MemoryMessageBusBuilderTests.cs
- Explicit Debt · Dead code: GenericConsumer src/Tests/SlimMessageBus.Host.Memory.Test/MemoryMessageBusTests.cs
- Explicit Debt · Dead code: AuditingHandler src/Samples/Sample.DomainEvents.Application/DomainEventHandlers/AuditingHandler.cs
- Explicit Debt · Dead code: CustomerEventConsumer src/Samples/Sample.AsyncApi.Service/Messages/CustomerEventConsumer.cs
- Static Analysis (SAST) · High: pull-request-target-code-checkout REDACTED
- Static Analysis (SAST) · High: pull-request-target-code-checkout REDACTED
- Static Analysis (SAST) · High: pull-request-target-code-checkout REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: watchdog-secret-interpolated-into-run REDACTED
- Static Analysis (SAST) · High: watchdog-secret-interpolated-into-run REDACTED
- Static Analysis (SAST) · High: pull-request-target-code-checkout REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Pkcs 8.0.1 src/SlimMessageBus.Host.Sql.Common/SlimMessageBus.Host.Sql.Common.csproj
- Dependency Vulnerabilities · High CVE: System.Security.Cryptography.Pkcs 9.0.13 src/SlimMessageBus.Host.Sql.Common/SlimMessageBus.Host.Sql.Common.csproj
- Dependency Vulnerabilities · High CVE: SSH.NET 2025.1.0 src/Tests/SlimMessageBus.Host.Outbox.MongoDb.Test/SlimMessageBus.Host.Outbox.MongoDb.Test.csproj
- Dependency Vulnerabilities · Medium CVE: Microsoft.Build.Tasks.Git 8.0.0
- Supply-chain Provenance & Signing · REDACTED handed to the step that runs a pull request's code
- Cancellation propagation · Async method without CancellationToken: NextOfTyped src/SlimMessageBus.Host/Consumer/InterceptorPipelines/ConsumerInterceptorPipeline.cs
- Cancellation propagation · Async method without CancellationToken: DoHandleInternal src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs
- Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: DestroyConsumers src/SlimMessageBus.Host/MessageBusBase.cs
- Cancellation propagation · Async method without CancellationToken: NextOfObject src/SlimMessageBus.Host/Producer/InterceptorPipelines/SendInterceptorPipeline.cs
- Cancellation propagation · Async method without CancellationToken: OnMessage src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs
- Cancellation propagation · Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.Kafka/KafkaMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.AzureEventHub/EventHubMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: GetImage src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs
- Cancellation propagation · Async method without CancellationToken: LoadImage src/Samples/Sample.Images.Worker/Handlers/GenerateThumbnailRequestHandler.cs
- Cancellation propagation · Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.AzureServiceBus/ServiceBusMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: EnsurePathExists src/SlimMessageBus.Host.AzureServiceBus/ServiceBusMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: TryCreateQueue src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: TryCreateTopic src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: TryCreateSubscription src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: TryCreateRule src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: TryDeleteRule src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: TryUpdateRule src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: PrepareSubscription src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: DoProvisionTopology src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: CustomerDoesSomeStuff src/Samples/Sample.Hybrid.ConsoleApp/Application.cs
- Cancellation propagation · Async method without CancellationToken: ChangeEmail src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs
- Cancellation propagation · Async method without CancellationToken: AddLoop src/Samples/Sample.Serialization.ConsoleApp/Program.cs
- Cancellation propagation · Async method without CancellationToken: MultiplyLoop src/Samples/Sample.Serialization.ConsoleApp/Program.cs
- Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Redis/Consumers/RedisListCheckerConsumer.cs
- Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Redis/RedisMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.Redis/RedisMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs
- Cancellation propagation · Async method without CancellationToken: BeginTransaction src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs
- Cancellation propagation · Async method without CancellationToken: TryCompleteTransaction src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs
- Cancellation propagation · Async method without CancellationToken: OnBusLifecycle src/SlimMessageBus.Host.Outbox/Services/OutboxCleanUpTask.cs
- Cancellation propagation · Async method without CancellationToken: Shutdown src/SlimMessageBus.Host.Outbox/Services/OutboxCleanUpTask.cs
- Cancellation propagation · Async method without CancellationToken: OnBusLifecycle src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs
- Cancellation propagation · Async local function without CancellationToken: CreateDbIfNotExists src/Samples/Sample.OutboxWebApi/Program.cs
- Cancellation propagation · Async method without CancellationToken: OnHandle src/SlimMessageBus.Host.Outbox.Sql/Interceptors/SqlTransactionConsumerInterceptor.cs
- Cancellation propagation · Async method without CancellationToken: OnBeginTransaction src/SlimMessageBus.Host.Outbox.Sql.DbContext/DbContextTransactionService.cs
- Cancellation propagation · Async method without CancellationToken: OnCompleteTransaction src/SlimMessageBus.Host.Outbox.Sql.DbContext/DbContextTransactionService.cs
- Cancellation propagation · Async method without CancellationToken: OnStop src/SlimMessageBus.Host.Mqtt/MqttMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: DestroyConsumers src/SlimMessageBus.Host.Mqtt/MqttMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: OnChannelRecovered src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs
- Cancellation propagation · Async method without CancellationToken: ReRegisterConsumer src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs
- Cancellation propagation · Async method without CancellationToken: OnStop src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs
- Cancellation propagation · Async method without CancellationToken: OnMessageReceived src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs
- Cancellation propagation · Async method without CancellationToken: NackMessage src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs
- Cancellation propagation · Async method without CancellationToken: AckMessage src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs
- Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs
- Cancellation propagation · Async method without CancellationToken: ConfirmMessage src/SlimMessageBus.Host.RabbitMQ/Consumers/RabbitMqConsumer.cs
- Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.RabbitMQ/Consumers/RabbitMqConsumer.cs
- Cancellation propagation · Async method without CancellationToken: EstablishConnection src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
- Cancellation propagation · Async method without CancellationToken: ProvisionTopology src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
- Cancellation propagation · Async method without CancellationToken: CloseAndDisposeChannelAsync src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
- Cancellation propagation · Async method without CancellationToken: CloseAndDisposeConnectionAsync src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
- Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
- Cancellation propagation · Async method without CancellationToken: DisposeResourcesAsync src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
- Cancellation propagation · Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.RabbitMQ/RabbitMqMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.RabbitMQ/RabbitMqMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: ProvisionTopology src/SlimMessageBus.Host.RabbitMQ/RabbitMqTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: ProvisionConsumers src/SlimMessageBus.Host.RabbitMQ/RabbitMqTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: DeclareQueueBinding src/SlimMessageBus.Host.RabbitMQ/RabbitMqTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: ProvisionProducers src/SlimMessageBus.Host.RabbitMQ/RabbitMqTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: DeclareQueue src/SlimMessageBus.Host.RabbitMQ/RabbitMqTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: DeclareExchange src/SlimMessageBus.Host.RabbitMQ/RabbitMqTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: DeclareExchange src/SlimMessageBus.Host.RabbitMQ/RabbitMqTopologyService.cs
- Cancellation propagation · Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.Relational/RelationalMessageBusBase.cs
- Cancellation propagation · Async method without CancellationToken: EnsureConnection REDACTED
- Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Sql.Common/Transactions/AbstractSqlTransactionService.cs
- Cancellation propagation · Async method without CancellationToken: BeginTransaction src/SlimMessageBus.Host.Sql.Common/Transactions/AbstractSqlTransactionService.cs
- Cancellation propagation · Async method without CancellationToken: TryCompleteTransaction src/SlimMessageBus.Host.Sql.Common/Transactions/AbstractSqlTransactionService.cs
- Cancellation propagation · Async method without CancellationToken: OnBeginTransaction src/SlimMessageBus.Host.Sql.Common/Transactions/SqlTransactionService.cs
- Cancellation propagation · Async method without CancellationToken: OnCompleteTransaction src/SlimMessageBus.Host.Sql.Common/Transactions/SqlTransactionService.cs
- Cancellation propagation · Async method without CancellationToken: Subscribe src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs
- Cancellation propagation · Async method without CancellationToken: Subscribe src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckCircuitBreaker.cs
- Cancellation propagation · Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.Nats/NatsMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Nats/NatsMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: EnsureClientAuthenticated src/SlimMessageBus.Host.AmazonSQS/ClientFactory/AbstractTemporaryCredentialsSqsClientProvider.cs
- Cancellation propagation · Async method without CancellationToken: RefreshCredentialsAsync src/SlimMessageBus.Host.AmazonSQS/ClientFactory/AbstractTemporaryCredentialsSqsClientProvider.cs
- Cancellation propagation · Async method without CancellationToken: DeleteMessages src/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs
- Cancellation propagation · Async method without CancellationToken: CreateConsumers src/SlimMessageBus.Host.AmazonSQS/SqsMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: InitAsync src/SlimMessageBus.Host.AmazonSQS/SqsMessageBus.cs
- Cancellation propagation · Async method without CancellationToken: OnStop src/SlimMessageBus.Host.GooglePubSub/Consumer/GooglePubSubConsumer.cs
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €36,000 to €180,000, for 598 to 1,921 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 27,083 lines of product code, of which 36% is declarations and boilerplate, 23% straight logic and 41% logic with branches |
| Comment lines | The estimate prices 23,847 lines. Comment lines count towards the size of 27,083 lines but aren't priced as work. |
| What it is not | Not 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 SlimMessageBus | 2 SlimMessageBus.Host.Serialization | 3 SlimMessageBus.Host.Sql.Common | 4 SlimMessageBus.Host.Collections | 5 SlimMessageBus.Host.Interceptor | 6 SlimMessageBus.Host | 7 SlimMessageBus.Host.Consumer.ErrorHandling | 8 SlimMessageBus.Host.FluentValidation | 9 SlimMessageBus.Host.Hybrid | 10 SlimMessageBus.Host.Outbox | 11 SlimMessageBus.Host.Relational | 12 SlimMessageBus.Host.Services | 13 SlimMessageBus.Host.AmazonSQS | 14 SlimMessageBus.Host.AzureEventHub | 15 SlimMessageBus.Host.AzureServiceBus | 16 SlimMessageBus.Host.GooglePubSub | 17 SlimMessageBus.Host.Kafka | 18 SlimMessageBus.Host.Memory | 19 SlimMessageBus.Host.Mqtt | 20 SlimMessageBus.Host.Nats | 21 SlimMessageBus.Host.Outbox.MongoDb | 22 SlimMessageBus.Host.Outbox.MongoDb.Configuration | 23 SlimMessageBus.Host.Outbox.MongoDb.Transactions | 24 SlimMessageBus.Host.Outbox.PostgreSql.Configuration | 25 SlimMessageBus.Host.Outbox.Services | 26 SlimMessageBus.Host.Outbox.Sql | 27 SlimMessageBus.Host.PostgreSql | 28 SlimMessageBus.Host.RabbitMQ | 29 SlimMessageBus.Host.Redis | 30 SlimMessageBus.Host.Sql | 31 SlimMessageBus.Host.AzureServiceBus.Consumer | 32 SlimMessageBus.Host.Outbox.MongoDb.Interceptors | 33 SlimMessageBus.Host.Outbox.MongoDb.Repositories | 34 SlimMessageBus.Host.Outbox.MongoDb.Services | 35 SlimMessageBus.Host.Outbox.PostgreSql.Transactions | 36 SlimMessageBus.Host.Outbox.Sql.DbContext | 37 SlimMessageBus.Host.Outbox.PostgreSql | 38 SlimMessageBus.Host.Outbox.PostgreSql.Repositories | 39 SlimMessageBus.Host.Outbox.PostgreSql.Services | 40 SlimMessageBus.Host.Outbox.PostgreSql.DbContext |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 SlimMessageBus | ||||||||||||||||||||||||||||||||||||||||
| 2 SlimMessageBus.Host.Serialization | ||||||||||||||||||||||||||||||||||||||||
| 3 SlimMessageBus.Host.Sql.Common | ||||||||||||||||||||||||||||||||||||||||
| 4 SlimMessageBus.Host.Collections | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 5 SlimMessageBus.Host.Interceptor | 6 | |||||||||||||||||||||||||||||||||||||||
| 6 SlimMessageBus.Host | 26 | 4 | 5 | 2 | ||||||||||||||||||||||||||||||||||||
| 7 SlimMessageBus.Host.Consumer.ErrorHandling | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 8 SlimMessageBus.Host.FluentValidation | 3 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 9 SlimMessageBus.Host.Hybrid | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||||||
| 10 SlimMessageBus.Host.Outbox | 9 | |||||||||||||||||||||||||||||||||||||||
| 11 SlimMessageBus.Host.Relational | 1 | 21 | ||||||||||||||||||||||||||||||||||||||
| 12 SlimMessageBus.Host.Services | 7 | |||||||||||||||||||||||||||||||||||||||
| 13 SlimMessageBus.Host.AmazonSQS | 1 | 3 | 23 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 14 SlimMessageBus.Host.AzureEventHub | 1 | 2 | 24 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 15 SlimMessageBus.Host.AzureServiceBus | 1 | 1 | 25 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 16 SlimMessageBus.Host.GooglePubSub | 1 | 20 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 17 SlimMessageBus.Host.Kafka | 1 | 8 | 1 | 1 | 25 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 18 SlimMessageBus.Host.Memory | 3 | 12 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 SlimMessageBus.Host.Mqtt | 12 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 SlimMessageBus.Host.Nats | 16 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 21 SlimMessageBus.Host.Outbox.MongoDb | 3 | |||||||||||||||||||||||||||||||||||||||
| 22 SlimMessageBus.Host.Outbox.MongoDb.Configuration | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 SlimMessageBus.Host.Outbox.MongoDb.Transactions | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 SlimMessageBus.Host.Outbox.PostgreSql.Configuration | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 SlimMessageBus.Host.Outbox.Services | 2 | 4 | 5 | 7 | ||||||||||||||||||||||||||||||||||||
| 26 SlimMessageBus.Host.Outbox.Sql | 5 | 7 | 8 | |||||||||||||||||||||||||||||||||||||
| 27 SlimMessageBus.Host.PostgreSql | 21 | 1 | 5 | 2 | ||||||||||||||||||||||||||||||||||||
| 28 SlimMessageBus.Host.RabbitMQ | 1 | 40 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 29 SlimMessageBus.Host.Redis | 3 | 1 | 22 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 30 SlimMessageBus.Host.Sql | 5 | 21 | 1 | 5 | 2 | |||||||||||||||||||||||||||||||||||
| 31 SlimMessageBus.Host.AzureServiceBus.Consumer | 7 | 6 | ||||||||||||||||||||||||||||||||||||||
| 32 SlimMessageBus.Host.Outbox.MongoDb.Interceptors | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 SlimMessageBus.Host.Outbox.MongoDb.Repositories | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 SlimMessageBus.Host.Outbox.MongoDb.Services | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 SlimMessageBus.Host.Outbox.PostgreSql.Transactions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 SlimMessageBus.Host.Outbox.Sql.DbContext | 3 | 2 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 37 SlimMessageBus.Host.Outbox.PostgreSql | 1 | 1 | 4 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 38 SlimMessageBus.Host.Outbox.PostgreSql.Repositories | 1 | 2 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 39 SlimMessageBus.Host.Outbox.PostgreSql.Services | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 40 SlimMessageBus.Host.Outbox.PostgreSql.DbContext | 1 | 3 | 2 | 1 | 1 |
4→1 SlimMessageBus.Host.Collections uses SlimMessageBus✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Collections uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.Collections.RuntimeTypeCache→SlimMessageBus.IConsumerContextSlimMessageBus.Host.Collections.RuntimeTypeCache→SlimMessageBus.IProducerContext
- Direction
- SlimMessageBus.Host.Collections uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.Collections, while a change to SlimMessageBus.Host.Collections can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.Collections uses a module listed above it, which is the healthy direction.
4→6 SlimMessageBus.Host.Collections uses SlimMessageBus.Host part of a loop✕
- Connections
- 4 pairs of types, where a type in SlimMessageBus.Host.Collections uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Collections.KindMapping→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Collections.KindMapping→SlimMessageBus.Host.PathKindSlimMessageBus.Host.Collections.KindMapping→SlimMessageBus.Host.ProducerSettingsSlimMessageBus.Host.Collections.RuntimeTypeCache→SlimMessageBus.Host.ProcessResult
- Direction
- SlimMessageBus.Host.Collections uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Collections, while a change to SlimMessageBus.Host.Collections can't break SlimMessageBus.Host.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→1 SlimMessageBus.Host.Interceptor uses SlimMessageBus✕
- Connections
- 6 pairs of types, where a type in SlimMessageBus.Host.Interceptor uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.Interceptor.IConsumerInterceptor→SlimMessageBus.IConsumerContextSlimMessageBus.Host.Interceptor.IMessageBusLifecycleInterceptor→SlimMessageBus.IMessageBusSlimMessageBus.Host.Interceptor.IProducerInterceptor→SlimMessageBus.IProducerContextSlimMessageBus.Host.Interceptor.IPublishInterceptor→SlimMessageBus.IProducerContextSlimMessageBus.Host.Interceptor.IRequestHandlerInterceptor→SlimMessageBus.IConsumerContextSlimMessageBus.Host.Interceptor.ISendInterceptor→SlimMessageBus.IProducerContext
- Direction
- SlimMessageBus.Host.Interceptor uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.Interceptor, while a change to SlimMessageBus.Host.Interceptor can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.Interceptor uses a module listed above it, which is the healthy direction.
6→1 SlimMessageBus.Host uses SlimMessageBus✕
- Connections
- 26 pairs of types, where a type in SlimMessageBus.Host uses a type in SlimMessageBus. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SlimMessageBus.Host.ConfigurationMessageBusException→SlimMessageBus.MessageBusExceptionSlimMessageBus.Host.ConsumerBuilder→SlimMessageBus.IConsumerContextSlimMessageBus.Host.ConsumerContext→SlimMessageBus.IConsumerContextSlimMessageBus.Host.ConsumerContext→SlimMessageBus.IMessageBusSlimMessageBus.Host.ConsumerInterceptorPipeline→SlimMessageBus.IConsumerContextSlimMessageBus.Host.ConsumerMethod→SlimMessageBus.IConsumerContextSlimMessageBus.Host.CurrentMessageBusProvider→SlimMessageBus.IMessageBusSlimMessageBus.Host.HandlerBuilder→SlimMessageBus.IConsumerContextSlimMessageBus.Host.HttpContextAccessorCurrentMessageBusProvider→SlimMessageBus.IMessageBusSlimMessageBus.Host.IConsumerContextExtensions→SlimMessageBus.IConsumerContextSlimMessageBus.Host.IConsumerErrorHandler→SlimMessageBus.IConsumerContextSlimMessageBus.Host.ICurrentMessageBusProvider→SlimMessageBus.IMessageBusSlimMessageBus.Host.IMessageBusTarget→SlimMessageBus.IMessageBusSlimMessageBus.Host.IMessageHandler→SlimMessageBus.IConsumerContextSlimMessageBus.Host.IProducerContextExtensions→SlimMessageBus.IProducerContextSlimMessageBus.Host.MessageBusProxy→SlimMessageBus.IRequestSlimMessageBus.Host.MessageConsumerContext→SlimMessageBus.IConsumerContextSlimMessageBus.Host.MessageConsumerContext→SlimMessageBus.IMessageBusSlimMessageBus.Host.MessageHandler→SlimMessageBus.IConsumerContextSlimMessageBus.Host.MessageHandler→SlimMessageBus.IMessageBusSlimMessageBus.Host.MessageProcessor→SlimMessageBus.IMessageBusSlimMessageBus.Host.ProducerContext→SlimMessageBus.IMessageBusSlimMessageBus.Host.ProducerContext→SlimMessageBus.IProducerContextSlimMessageBus.Host.ProducerInterceptorPipeline→SlimMessageBus.IProducerContextSlimMessageBus.Host.PublishInterceptorPipeline→SlimMessageBus.IProducerContext
- Direction
- SlimMessageBus.Host uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host, while a change to SlimMessageBus.Host can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host uses a module listed above it, which is the healthy direction.
6→2 SlimMessageBus.Host uses SlimMessageBus.Host.Serialization✕
- Connections
- 4 pairs of types, where a type in SlimMessageBus.Host uses a type in SlimMessageBus.Host.Serialization.
- The types involved
SlimMessageBus.Host.IMasterMessageBus→SlimMessageBus.Host.Serialization.IMessageSerializerProviderSlimMessageBus.Host.IMessageSerializerExtensions→SlimMessageBus.Host.Serialization.IMessageSerializerSlimMessageBus.Host.MessageBusSettingsExtensions→SlimMessageBus.Host.Serialization.IMessageSerializerProviderSlimMessageBus.Host.MessageWithHeadersSerializer→SlimMessageBus.Host.Serialization.IMessageSerializer
- Direction
- SlimMessageBus.Host uses SlimMessageBus.Host.Serialization, so a change to SlimMessageBus.Host.Serialization can break SlimMessageBus.Host, while a change to SlimMessageBus.Host can't break SlimMessageBus.Host.Serialization.
- Position
- Below the diagonal: SlimMessageBus.Host uses a module listed above it, which is the healthy direction.
6→4 SlimMessageBus.Host uses SlimMessageBus.Host.Collections✕
- Connections
- 5 pairs of types, where a type in SlimMessageBus.Host uses a type in SlimMessageBus.Host.Collections.
- The types involved
SlimMessageBus.Host.AssemblyQualifiedNameMessageTypeResolver→SlimMessageBus.Host.Collections.SafeDictionaryWrapperSlimMessageBus.Host.ConsumerInterceptorPipeline→SlimMessageBus.Host.Collections.RuntimeTypeCacheSlimMessageBus.Host.MessageHandler→SlimMessageBus.Host.Collections.RuntimeTypeCacheSlimMessageBus.Host.ProducerInterceptorPipeline→SlimMessageBus.Host.Collections.RuntimeTypeCacheSlimMessageBus.Host.PublishInterceptorPipeline→SlimMessageBus.Host.Collections.RuntimeTypeCache
- Direction
- SlimMessageBus.Host uses SlimMessageBus.Host.Collections, so a change to SlimMessageBus.Host.Collections can break SlimMessageBus.Host, while a change to SlimMessageBus.Host can't break SlimMessageBus.Host.Collections.
- Position
- Below the diagonal: SlimMessageBus.Host uses a module listed above it, which is the healthy direction.
6→5 SlimMessageBus.Host uses SlimMessageBus.Host.Interceptor✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host uses a type in SlimMessageBus.Host.Interceptor.
- The types involved
SlimMessageBus.Host.IAbstractConsumerInterceptor→SlimMessageBus.Host.Interceptor.IInterceptorWithOrderSlimMessageBus.Host.InterceptorExtensions→SlimMessageBus.Host.Interceptor.IInterceptor
- Direction
- SlimMessageBus.Host uses SlimMessageBus.Host.Interceptor, so a change to SlimMessageBus.Host.Interceptor can break SlimMessageBus.Host, while a change to SlimMessageBus.Host can't break SlimMessageBus.Host.Interceptor.
- Position
- Below the diagonal: SlimMessageBus.Host uses a module listed above it, which is the healthy direction.
7→1 SlimMessageBus.Host.Consumer.ErrorHandling uses SlimMessageBus✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Consumer.ErrorHandling uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler→SlimMessageBus.IConsumerContext
- Direction
- SlimMessageBus.Host.Consumer.ErrorHandling uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.Consumer.ErrorHandling, while a change to SlimMessageBus.Host.Consumer.ErrorHandling can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.Consumer.ErrorHandling uses a module listed above it, which is the healthy direction.
7→6 SlimMessageBus.Host.Consumer.ErrorHandling uses SlimMessageBus.Host✕
- Connections
- 3 pairs of types, where a type in SlimMessageBus.Host.Consumer.ErrorHandling uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Consumer.ErrorHandling.BaseConsumerErrorHandler→SlimMessageBus.Host.ProcessResultSlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler→SlimMessageBus.Host.ProcessResult
- Direction
- SlimMessageBus.Host.Consumer.ErrorHandling uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Consumer.ErrorHandling, while a change to SlimMessageBus.Host.Consumer.ErrorHandling can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Consumer.ErrorHandling uses a module listed above it, which is the healthy direction.
8→1 SlimMessageBus.Host.FluentValidation uses SlimMessageBus✕
- Connections
- 3 pairs of types, where a type in SlimMessageBus.Host.FluentValidation uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.FluentValidation.ConsumerValidationInterceptor→SlimMessageBus.IConsumerContextSlimMessageBus.Host.FluentValidation.HandlerValidationInterceptor→SlimMessageBus.IConsumerContextSlimMessageBus.Host.FluentValidation.ProducerValidationInterceptor→SlimMessageBus.IProducerContext
- Direction
- SlimMessageBus.Host.FluentValidation uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.FluentValidation, while a change to SlimMessageBus.Host.FluentValidation can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.FluentValidation uses a module listed above it, which is the healthy direction.
8→5 SlimMessageBus.Host.FluentValidation uses SlimMessageBus.Host.Interceptor✕
- Connections
- 3 pairs of types, where a type in SlimMessageBus.Host.FluentValidation uses a type in SlimMessageBus.Host.Interceptor.
- The types involved
SlimMessageBus.Host.FluentValidation.ConsumerValidationInterceptor→SlimMessageBus.Host.Interceptor.IConsumerInterceptorSlimMessageBus.Host.FluentValidation.HandlerValidationInterceptor→SlimMessageBus.Host.Interceptor.IRequestHandlerInterceptorSlimMessageBus.Host.FluentValidation.ProducerValidationInterceptor→SlimMessageBus.Host.Interceptor.IProducerInterceptor
- Direction
- SlimMessageBus.Host.FluentValidation uses SlimMessageBus.Host.Interceptor, so a change to SlimMessageBus.Host.Interceptor can break SlimMessageBus.Host.FluentValidation, while a change to SlimMessageBus.Host.FluentValidation can't break SlimMessageBus.Host.Interceptor.
- Position
- Below the diagonal: SlimMessageBus.Host.FluentValidation uses a module listed above it, which is the healthy direction.
8→6 SlimMessageBus.Host.FluentValidation uses SlimMessageBus.Host✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.FluentValidation uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.FluentValidation.FluentValidationMessageBusBuilder→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.FluentValidation.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilder
- Direction
- SlimMessageBus.Host.FluentValidation uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.FluentValidation, while a change to SlimMessageBus.Host.FluentValidation can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.FluentValidation uses a module listed above it, which is the healthy direction.
9→2 SlimMessageBus.Host.Hybrid uses SlimMessageBus.Host.Serialization✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Hybrid uses a type in SlimMessageBus.Host.Serialization.
- The types involved
SlimMessageBus.Host.Hybrid.HybridMessageBus→SlimMessageBus.Host.Serialization.IMessageSerializerProvider
- Direction
- SlimMessageBus.Host.Hybrid uses SlimMessageBus.Host.Serialization, so a change to SlimMessageBus.Host.Serialization can break SlimMessageBus.Host.Hybrid, while a change to SlimMessageBus.Host.Hybrid can't break SlimMessageBus.Host.Serialization.
- Position
- Below the diagonal: SlimMessageBus.Host.Hybrid uses a module listed above it, which is the healthy direction.
9→4 SlimMessageBus.Host.Hybrid uses SlimMessageBus.Host.Collections✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Hybrid uses a type in SlimMessageBus.Host.Collections.
- The types involved
SlimMessageBus.Host.Hybrid.HybridMessageBus→SlimMessageBus.Host.Collections.ProducerByMessageTypeCache
- Direction
- SlimMessageBus.Host.Hybrid uses SlimMessageBus.Host.Collections, so a change to SlimMessageBus.Host.Collections can break SlimMessageBus.Host.Hybrid, while a change to SlimMessageBus.Host.Hybrid can't break SlimMessageBus.Host.Collections.
- Position
- Below the diagonal: SlimMessageBus.Host.Hybrid uses a module listed above it, which is the healthy direction.
9→6 SlimMessageBus.Host.Hybrid uses SlimMessageBus.Host✕
- Connections
- 7 pairs of types, where a type in SlimMessageBus.Host.Hybrid uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Hybrid.HybridMessageBus→SlimMessageBus.Host.ICompositeMessageBusSlimMessageBus.Host.Hybrid.HybridMessageBus→SlimMessageBus.Host.IMasterMessageBusSlimMessageBus.Host.Hybrid.HybridMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.Hybrid.HybridMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.Hybrid.HybridMessageBus→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Hybrid.HybridMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Hybrid.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilder
- Direction
- SlimMessageBus.Host.Hybrid uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Hybrid, while a change to SlimMessageBus.Host.Hybrid can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Hybrid uses a module listed above it, which is the healthy direction.
10→6 SlimMessageBus.Host.Outbox uses SlimMessageBus.Host✕
- Connections
- 9 pairs of types, where a type in SlimMessageBus.Host.Outbox uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Outbox.BuilderExtensions→SlimMessageBus.Host.ConsumerBuilderSlimMessageBus.Host.Outbox.BuilderExtensions→SlimMessageBus.Host.HandlerBuilderSlimMessageBus.Host.Outbox.BuilderExtensions→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.Outbox.BuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Outbox.BuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.Outbox.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Outbox.OutboxSettings→SlimMessageBus.Host.IMessageTypeResolverSlimMessageBus.Host.Outbox.SettingsExtensions→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.Outbox.SettingsExtensions→SlimMessageBus.Host.MessageBusSettings
- Direction
- SlimMessageBus.Host.Outbox uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Outbox, while a change to SlimMessageBus.Host.Outbox can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox uses a module listed above it, which is the healthy direction.
11→4 SlimMessageBus.Host.Relational uses SlimMessageBus.Host.Collections✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Relational uses a type in SlimMessageBus.Host.Collections.
- The types involved
SlimMessageBus.Host.Relational.RelationalMessageBusBase→SlimMessageBus.Host.Collections.KindMapping
- Direction
- SlimMessageBus.Host.Relational uses SlimMessageBus.Host.Collections, so a change to SlimMessageBus.Host.Collections can break SlimMessageBus.Host.Relational, while a change to SlimMessageBus.Host.Relational can't break SlimMessageBus.Host.Collections.
- Position
- Below the diagonal: SlimMessageBus.Host.Relational uses a module listed above it, which is the healthy direction.
11→6 SlimMessageBus.Host.Relational uses SlimMessageBus.Host✕
- Connections
- 21 pairs of types, where a type in SlimMessageBus.Host.Relational uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Relational.IRelationalRepository→SlimMessageBus.Host.PathKindSlimMessageBus.Host.Relational.RelationalBuilderExtensions→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Relational.RelationalBuilderExtensions→SlimMessageBus.Host.ConsumerBuilderSlimMessageBus.Host.Relational.RelationalBuilderExtensions→SlimMessageBus.Host.HandlerBuilderSlimMessageBus.Host.Relational.RelationalBuilderExtensions→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.Relational.RelationalBuilderExtensions→SlimMessageBus.Host.PathKindSlimMessageBus.Host.Relational.RelationalBuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.Relational.RelationalBuilderExtensions→SlimMessageBus.Host.RequestResponseBuilderSlimMessageBus.Host.Relational.RelationalConsumerBase→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.Relational.RelationalConsumerBase→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Relational.RelationalConsumerBase→SlimMessageBus.Host.IAbstractConsumerInterceptorSlimMessageBus.Host.Relational.RelationalConsumerBase→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Relational.RelationalConsumerBase→SlimMessageBus.Host.PathKindSlimMessageBus.Host.Relational.RelationalMessageBusBase→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.Relational.RelationalMessageBusBase→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Relational.RelationalMessageBusBase→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.Relational.RelationalMessageBusBase→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Relational.RelationalMessageBusBase→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.Relational.RelationalMessageBusBase→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Relational.RelationalMessageBusBase→SlimMessageBus.Host.PathKindSlimMessageBus.Host.Relational.RelationalMessageBusBase→SlimMessageBus.Host.ProduceToTransportBulkResult
- Direction
- SlimMessageBus.Host.Relational uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Relational, while a change to SlimMessageBus.Host.Relational can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Relational uses a module listed above it, which is the healthy direction.
12→6 SlimMessageBus.Host.Services uses SlimMessageBus.Host✕
- Connections
- 7 pairs of types, where a type in SlimMessageBus.Host.Services uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService→SlimMessageBus.Host.ConsumerSettingsSlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService→SlimMessageBus.Host.ProducerSettingsSlimMessageBus.Host.Services.IMessageHeaderService→SlimMessageBus.Host.ProducerSettingsSlimMessageBus.Host.Services.MessageHeaderService→SlimMessageBus.Host.IMessageTypeResolverSlimMessageBus.Host.Services.MessageHeaderService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Services.MessageHeaderService→SlimMessageBus.Host.ProducerSettings
- Direction
- SlimMessageBus.Host.Services uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Services, while a change to SlimMessageBus.Host.Services can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Services uses a module listed above it, which is the healthy direction.
13→1 SlimMessageBus.Host.AmazonSQS uses SlimMessageBus✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.AmazonSQS uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.AmazonSQS.SqsConsumerContextExtensions→SlimMessageBus.IConsumerContext
- Direction
- SlimMessageBus.Host.AmazonSQS uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.AmazonSQS, while a change to SlimMessageBus.Host.AmazonSQS can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.AmazonSQS uses a module listed above it, which is the healthy direction.
13→2 SlimMessageBus.Host.AmazonSQS uses SlimMessageBus.Host.Serialization✕
- Connections
- 3 pairs of types, where a type in SlimMessageBus.Host.AmazonSQS uses a type in SlimMessageBus.Host.Serialization.
- The types involved
SlimMessageBus.Host.AmazonSQS.SqsBaseConsumer→SlimMessageBus.Host.Serialization.IMessageSerializerSlimMessageBus.Host.AmazonSQS.SqsMessageBus→SlimMessageBus.Host.Serialization.IMessageSerializerSlimMessageBus.Host.AmazonSQS.SqsQueueConsumer→SlimMessageBus.Host.Serialization.IMessageSerializer
- Direction
- SlimMessageBus.Host.AmazonSQS uses SlimMessageBus.Host.Serialization, so a change to SlimMessageBus.Host.Serialization can break SlimMessageBus.Host.AmazonSQS, while a change to SlimMessageBus.Host.AmazonSQS can't break SlimMessageBus.Host.Serialization.
- Position
- Below the diagonal: SlimMessageBus.Host.AmazonSQS uses a module listed above it, which is the healthy direction.
13→6 SlimMessageBus.Host.AmazonSQS uses SlimMessageBus.Host✕
- Connections
- 23 pairs of types, where a type in SlimMessageBus.Host.AmazonSQS uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.AmazonSQS.ISqsConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.AmazonSQS.ISqsTopologyCache→SlimMessageBus.Host.PathKindSlimMessageBus.Host.AmazonSQS.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.AmazonSQS.SqsBaseConsumer→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.AmazonSQS.SqsBaseConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AmazonSQS.SqsBaseConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.AmazonSQS.SqsConsumerBuilderExtensions→SlimMessageBus.Host.ConsumerBuilderSlimMessageBus.Host.AmazonSQS.SqsConsumerContextExtensions→SlimMessageBus.Host.ConsumerContextSlimMessageBus.Host.AmazonSQS.SqsMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.AmazonSQS.SqsMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.AmazonSQS.SqsMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.AmazonSQS.SqsMessageBus→SlimMessageBus.Host.ProduceToTransportBulkResultSlimMessageBus.Host.AmazonSQS.SqsMessageBusSettingsValidationService→SlimMessageBus.Host.ConsumerSettingsSlimMessageBus.Host.AmazonSQS.SqsMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.AmazonSQS.SqsPathMeta→SlimMessageBus.Host.PathKindSlimMessageBus.Host.AmazonSQS.SqsProducerBuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.AmazonSQS.SqsProducerFifoBuilder→SlimMessageBus.Host.ProducerSettingsSlimMessageBus.Host.AmazonSQS.SqsProperties→SlimMessageBus.Host.ProviderExtensionPropertySlimMessageBus.Host.AmazonSQS.SqsQueueConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AmazonSQS.SqsQueueConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.AmazonSQS.SqsRequestResponseBuilderExtensions→SlimMessageBus.Host.RequestResponseBuilderSlimMessageBus.Host.AmazonSQS.SqsTopologyCache→SlimMessageBus.Host.PathKindSlimMessageBus.Host.AmazonSQS.SqsTopologyService→SlimMessageBus.Host.MessageBusSettings
- Direction
- SlimMessageBus.Host.AmazonSQS uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.AmazonSQS, while a change to SlimMessageBus.Host.AmazonSQS can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.AmazonSQS uses a module listed above it, which is the healthy direction.
13→7 SlimMessageBus.Host.AmazonSQS uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.AmazonSQS uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.AmazonSQS.SqsConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.AmazonSQS uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.AmazonSQS, while a change to SlimMessageBus.Host.AmazonSQS can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.AmazonSQS uses a module listed above it, which is the healthy direction.
13→12 SlimMessageBus.Host.AmazonSQS uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.AmazonSQS uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.AmazonSQS.SqsMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.AmazonSQS.SqsMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.AmazonSQS uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.AmazonSQS, while a change to SlimMessageBus.Host.AmazonSQS can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.AmazonSQS uses a module listed above it, which is the healthy direction.
14→1 SlimMessageBus.Host.AzureEventHub uses SlimMessageBus✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.AzureEventHub uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.AzureEventHub.EhConsumerContextExtensions→SlimMessageBus.IConsumerContext
- Direction
- SlimMessageBus.Host.AzureEventHub uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.AzureEventHub, while a change to SlimMessageBus.Host.AzureEventHub can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureEventHub uses a module listed above it, which is the healthy direction.
14→4 SlimMessageBus.Host.AzureEventHub uses SlimMessageBus.Host.Collections✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.AzureEventHub uses a type in SlimMessageBus.Host.Collections.
- The types involved
SlimMessageBus.Host.AzureEventHub.EhGroupConsumer→SlimMessageBus.Host.Collections.SafeDictionaryWrapperSlimMessageBus.Host.AzureEventHub.EventHubMessageBus→SlimMessageBus.Host.Collections.SafeDictionaryWrapper
- Direction
- SlimMessageBus.Host.AzureEventHub uses SlimMessageBus.Host.Collections, so a change to SlimMessageBus.Host.Collections can break SlimMessageBus.Host.AzureEventHub, while a change to SlimMessageBus.Host.AzureEventHub can't break SlimMessageBus.Host.Collections.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureEventHub uses a module listed above it, which is the healthy direction.
14→6 SlimMessageBus.Host.AzureEventHub uses SlimMessageBus.Host✕
- Connections
- 24 pairs of types, where a type in SlimMessageBus.Host.AzureEventHub uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.AzureEventHub.BuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.AzureEventHub.BuilderExtensions→SlimMessageBus.Host.RequestResponseBuilderSlimMessageBus.Host.AzureEventHub.EhConsumerContextExtensions→SlimMessageBus.Host.ConsumerContextSlimMessageBus.Host.AzureEventHub.EhGroupConsumer→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.AzureEventHub.EhGroupConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AzureEventHub.EhPartitionConsumer→SlimMessageBus.Host.ICheckpointTriggerSlimMessageBus.Host.AzureEventHub.EhPartitionConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.AzureEventHub.EhPartitionConsumerForConsumers→SlimMessageBus.Host.ConsumerContextSlimMessageBus.Host.AzureEventHub.EhPartitionConsumerForConsumers→SlimMessageBus.Host.ConsumerSettingsSlimMessageBus.Host.AzureEventHub.EhPartitionConsumerForConsumers→SlimMessageBus.Host.ICheckpointTriggerSlimMessageBus.Host.AzureEventHub.EhPartitionConsumerForConsumers→SlimMessageBus.Host.MessageProviderSlimMessageBus.Host.AzureEventHub.EhPartitionConsumerForResponses→SlimMessageBus.Host.IPendingRequestStoreSlimMessageBus.Host.AzureEventHub.EhPartitionConsumerForResponses→SlimMessageBus.Host.MessageProviderSlimMessageBus.Host.AzureEventHub.EhPartitionConsumerForResponses→SlimMessageBus.Host.RequestResponseSettingsSlimMessageBus.Host.AzureEventHub.EventHubMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.AzureEventHub.EventHubMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.AzureEventHub.EventHubMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.AzureEventHub.EventHubMessageBus→SlimMessageBus.Host.ProduceToTransportBulkResultSlimMessageBus.Host.AzureEventHub.EventHubMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.AzureEventHub.IEventHubConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.AzureEventHub.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.AzureEventHub.MessageBusSettingsExtensions→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.AzureEventHub.SettingsExtensions→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AzureEventHub.SettingsExtensions→SlimMessageBus.Host.ProducerSettings
- Direction
- SlimMessageBus.Host.AzureEventHub uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.AzureEventHub, while a change to SlimMessageBus.Host.AzureEventHub can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureEventHub uses a module listed above it, which is the healthy direction.
14→7 SlimMessageBus.Host.AzureEventHub uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.AzureEventHub uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.AzureEventHub.EventHubConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.AzureEventHub uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.AzureEventHub, while a change to SlimMessageBus.Host.AzureEventHub can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureEventHub uses a module listed above it, which is the healthy direction.
14→12 SlimMessageBus.Host.AzureEventHub uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.AzureEventHub uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.AzureEventHub.EventHubMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.AzureEventHub.EventHubMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.AzureEventHub uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.AzureEventHub, while a change to SlimMessageBus.Host.AzureEventHub can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureEventHub uses a module listed above it, which is the healthy direction.
15→1 SlimMessageBus.Host.AzureServiceBus uses SlimMessageBus✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.AzureServiceBus uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.AzureServiceBus.ServiceBusConsumerContextExtensions→SlimMessageBus.IConsumerContext
- Direction
- SlimMessageBus.Host.AzureServiceBus uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.AzureServiceBus, while a change to SlimMessageBus.Host.AzureServiceBus can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureServiceBus uses a module listed above it, which is the healthy direction.
15→4 SlimMessageBus.Host.AzureServiceBus uses SlimMessageBus.Host.Collections✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.AzureServiceBus uses a type in SlimMessageBus.Host.Collections.
- The types involved
SlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBus→SlimMessageBus.Host.Collections.SafeDictionaryWrapper
- Direction
- SlimMessageBus.Host.AzureServiceBus uses SlimMessageBus.Host.Collections, so a change to SlimMessageBus.Host.Collections can break SlimMessageBus.Host.AzureServiceBus, while a change to SlimMessageBus.Host.AzureServiceBus can't break SlimMessageBus.Host.Collections.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureServiceBus uses a module listed above it, which is the healthy direction.
15→6 SlimMessageBus.Host.AzureServiceBus uses SlimMessageBus.Host✕
- Connections
- 25 pairs of types, where a type in SlimMessageBus.Host.AzureServiceBus uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.AzureServiceBus.AsbAbstractConsumerSettingsExtensions→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AzureServiceBus.AsbAbstractConsumerSettingsExtensions→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.AzureServiceBus.AsbConsumerBuilderExtensions→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AzureServiceBus.AsbConsumerSessionBuilder→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AzureServiceBus.AsbProducerBuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.AzureServiceBus.AsbProperties→SlimMessageBus.Host.ProviderExtensionPropertySlimMessageBus.Host.AzureServiceBus.AsbRequestResponseBuilderExtensions→SlimMessageBus.Host.RequestResponseBuilderSlimMessageBus.Host.AzureServiceBus.DeadLetterState→SlimMessageBus.Host.ProcessResultSlimMessageBus.Host.AzureServiceBus.FailureStateWithProperties→SlimMessageBus.Host.FailureStateSlimMessageBus.Host.AzureServiceBus.IServiceBusConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.AzureServiceBus.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.AzureServiceBus.ServiceBusConsumerContextExtensions→SlimMessageBus.Host.ConsumerContextSlimMessageBus.Host.AzureServiceBus.ServiceBusConsumerErrorHandler→SlimMessageBus.Host.ProcessResultSlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBus→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBus→SlimMessageBus.Host.ProduceToTransportBulkResultSlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBusSettings→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBusSettingsValidationService→SlimMessageBus.Host.ConsumerSettingsSlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBusSettingsValidationService→SlimMessageBus.Host.ProducerSettingsSlimMessageBus.Host.AzureServiceBus.ServiceBusProcessResult→SlimMessageBus.Host.ProcessResultSlimMessageBus.Host.AzureServiceBus.ServiceBusTopologyService→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AzureServiceBus.ServiceBusTopologyService→SlimMessageBus.Host.MessageBusSettings
- Direction
- SlimMessageBus.Host.AzureServiceBus uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.AzureServiceBus, while a change to SlimMessageBus.Host.AzureServiceBus can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureServiceBus uses a module listed above it, which is the healthy direction.
15→7 SlimMessageBus.Host.AzureServiceBus uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.AzureServiceBus uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.AzureServiceBus.ServiceBusConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.AzureServiceBus uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.AzureServiceBus, while a change to SlimMessageBus.Host.AzureServiceBus can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureServiceBus uses a module listed above it, which is the healthy direction.
15→12 SlimMessageBus.Host.AzureServiceBus uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.AzureServiceBus uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.AzureServiceBus uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.AzureServiceBus, while a change to SlimMessageBus.Host.AzureServiceBus can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureServiceBus uses a module listed above it, which is the healthy direction.
16→1 SlimMessageBus.Host.GooglePubSub uses SlimMessageBus✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.GooglePubSub uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.GooglePubSub.GooglePubSubConsumerContextExtensions→SlimMessageBus.IConsumerContext
- Direction
- SlimMessageBus.Host.GooglePubSub uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.GooglePubSub, while a change to SlimMessageBus.Host.GooglePubSub can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.GooglePubSub uses a module listed above it, which is the healthy direction.
16→6 SlimMessageBus.Host.GooglePubSub uses SlimMessageBus.Host✕
- Connections
- 20 pairs of types, where a type in SlimMessageBus.Host.GooglePubSub uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.GooglePubSub.GooglePubSubConsumer→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.GooglePubSub.GooglePubSubConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.GooglePubSub.GooglePubSubConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.GooglePubSub.GooglePubSubConsumerContextExtensions→SlimMessageBus.Host.ConsumerContextSlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBus→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBus→SlimMessageBus.Host.ProduceToTransportBulkResultSlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBusSettings→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBusSettingsValidationService→SlimMessageBus.Host.ConsumerSettingsSlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBusSettingsValidationService→SlimMessageBus.Host.ProducerSettingsSlimMessageBus.Host.GooglePubSub.GooglePubSubProducerBuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.GooglePubSub.GooglePubSubProperties→SlimMessageBus.Host.ProviderExtensionPropertySlimMessageBus.Host.GooglePubSub.GooglePubSubSettingsExtensions→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.GooglePubSub.GooglePubSubSettingsExtensions→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.GooglePubSub.GooglePubSubTopologyService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.GooglePubSub.IGooglePubSubConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.GooglePubSub.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilder
- Direction
- SlimMessageBus.Host.GooglePubSub uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.GooglePubSub, while a change to SlimMessageBus.Host.GooglePubSub can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.GooglePubSub uses a module listed above it, which is the healthy direction.
16→7 SlimMessageBus.Host.GooglePubSub uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.GooglePubSub uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.GooglePubSub.GooglePubSubConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.GooglePubSub uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.GooglePubSub, while a change to SlimMessageBus.Host.GooglePubSub can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.GooglePubSub uses a module listed above it, which is the healthy direction.
16→12 SlimMessageBus.Host.GooglePubSub uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.GooglePubSub uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.GooglePubSub.GooglePubSubMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.GooglePubSub uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.GooglePubSub, while a change to SlimMessageBus.Host.GooglePubSub can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.GooglePubSub uses a module listed above it, which is the healthy direction.
17→1 SlimMessageBus.Host.Kafka uses SlimMessageBus✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Kafka uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.Kafka.KafkaConsumerContextExtensions→SlimMessageBus.IConsumerContext
- Direction
- SlimMessageBus.Host.Kafka uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.Kafka, while a change to SlimMessageBus.Host.Kafka can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.Kafka uses a module listed above it, which is the healthy direction.
17→2 SlimMessageBus.Host.Kafka uses SlimMessageBus.Host.Serialization✕
- Connections
- 8 pairs of types, where a type in SlimMessageBus.Host.Kafka uses a type in SlimMessageBus.Host.Serialization.
- The types involved
SlimMessageBus.Host.Kafka.DefaultKafkaHeaderSerializer→SlimMessageBus.Host.Serialization.IMessageSerializerSlimMessageBus.Host.Kafka.DefaultKafkaHeaderSerializer→SlimMessageBus.Host.Serialization.IMessageSerializerProviderSlimMessageBus.Host.Kafka.KafkaExtensions→SlimMessageBus.Host.Serialization.IMessageSerializerSlimMessageBus.Host.Kafka.KafkaMessageBus→SlimMessageBus.Host.Serialization.IMessageSerializerProviderSlimMessageBus.Host.Kafka.KafkaMessageBusSettings→SlimMessageBus.Host.Serialization.IMessageSerializerProviderSlimMessageBus.Host.Kafka.KafkaPartitionConsumer→SlimMessageBus.Host.Serialization.IMessageSerializerSlimMessageBus.Host.Kafka.KafkaPartitionConsumerForConsumers→SlimMessageBus.Host.Serialization.IMessageSerializerSlimMessageBus.Host.Kafka.KafkaPartitionConsumerForResponses→SlimMessageBus.Host.Serialization.IMessageSerializer
- Direction
- SlimMessageBus.Host.Kafka uses SlimMessageBus.Host.Serialization, so a change to SlimMessageBus.Host.Serialization can break SlimMessageBus.Host.Kafka, while a change to SlimMessageBus.Host.Kafka can't break SlimMessageBus.Host.Serialization.
- Position
- Below the diagonal: SlimMessageBus.Host.Kafka uses a module listed above it, which is the healthy direction.
17→4 SlimMessageBus.Host.Kafka uses SlimMessageBus.Host.Collections✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Kafka uses a type in SlimMessageBus.Host.Collections.
- The types involved
SlimMessageBus.Host.Kafka.KafkaGroupConsumer→SlimMessageBus.Host.Collections.SafeDictionaryWrapper
- Direction
- SlimMessageBus.Host.Kafka uses SlimMessageBus.Host.Collections, so a change to SlimMessageBus.Host.Collections can break SlimMessageBus.Host.Kafka, while a change to SlimMessageBus.Host.Kafka can't break SlimMessageBus.Host.Collections.
- Position
- Below the diagonal: SlimMessageBus.Host.Kafka uses a module listed above it, which is the healthy direction.
17→5 SlimMessageBus.Host.Kafka uses SlimMessageBus.Host.Interceptor✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Kafka uses a type in SlimMessageBus.Host.Interceptor.
- The types involved
SlimMessageBus.Host.Kafka.IKafkaLoopFailureInterceptor→SlimMessageBus.Host.Interceptor.IInterceptorWithOrder
- Direction
- SlimMessageBus.Host.Kafka uses SlimMessageBus.Host.Interceptor, so a change to SlimMessageBus.Host.Interceptor can break SlimMessageBus.Host.Kafka, while a change to SlimMessageBus.Host.Kafka can't break SlimMessageBus.Host.Interceptor.
- Position
- Below the diagonal: SlimMessageBus.Host.Kafka uses a module listed above it, which is the healthy direction.
17→6 SlimMessageBus.Host.Kafka uses SlimMessageBus.Host✕
- Connections
- 25 pairs of types, where a type in SlimMessageBus.Host.Kafka uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Kafka.IKafkaConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.Kafka.KafkaAbstractConsumerBuilderExtensions→SlimMessageBus.Host.RequestResponseBuilderSlimMessageBus.Host.Kafka.KafkaConsumerContextExtensions→SlimMessageBus.Host.ConsumerContextSlimMessageBus.Host.Kafka.KafkaGroupConsumer→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.Kafka.KafkaGroupConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Kafka.KafkaGroupConsumer→SlimMessageBus.Host.IAbstractConsumerInterceptorSlimMessageBus.Host.Kafka.KafkaMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.Kafka.KafkaMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.Kafka.KafkaMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Kafka.KafkaMessageBus→SlimMessageBus.Host.ProducerSettingsSlimMessageBus.Host.Kafka.KafkaMessageBusSettingsValidationService→SlimMessageBus.Host.ConsumerSettingsSlimMessageBus.Host.Kafka.KafkaMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Kafka.KafkaPartitionConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Kafka.KafkaPartitionConsumer→SlimMessageBus.Host.ICheckpointTriggerSlimMessageBus.Host.Kafka.KafkaPartitionConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Kafka.KafkaPartitionConsumerForConsumers→SlimMessageBus.Host.ConsumerSettingsSlimMessageBus.Host.Kafka.KafkaPartitionConsumerForConsumers→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.Kafka.KafkaPartitionConsumerForConsumers→SlimMessageBus.Host.MessageProviderSlimMessageBus.Host.Kafka.KafkaPartitionConsumerForResponses→SlimMessageBus.Host.IPendingRequestStoreSlimMessageBus.Host.Kafka.KafkaPartitionConsumerForResponses→SlimMessageBus.Host.MessageProviderSlimMessageBus.Host.Kafka.KafkaPartitionConsumerForResponses→SlimMessageBus.Host.RequestResponseSettingsSlimMessageBus.Host.Kafka.KafkaProducerBuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.Kafka.KafkaProducerSettingsExtensions→SlimMessageBus.Host.ProducerSettingsSlimMessageBus.Host.Kafka.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Kafka.SettingsExtensions→SlimMessageBus.Host.AbstractConsumerSettings
- Direction
- SlimMessageBus.Host.Kafka uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Kafka, while a change to SlimMessageBus.Host.Kafka can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Kafka uses a module listed above it, which is the healthy direction.
17→7 SlimMessageBus.Host.Kafka uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Kafka uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.Kafka.KafkaConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.Kafka uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.Kafka, while a change to SlimMessageBus.Host.Kafka can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.Kafka uses a module listed above it, which is the healthy direction.
17→12 SlimMessageBus.Host.Kafka uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Kafka uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.Kafka.KafkaMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.Kafka.KafkaMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.Kafka uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.Kafka, while a change to SlimMessageBus.Host.Kafka can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.Kafka uses a module listed above it, which is the healthy direction.
18→2 SlimMessageBus.Host.Memory uses SlimMessageBus.Host.Serialization✕
- Connections
- 3 pairs of types, where a type in SlimMessageBus.Host.Memory uses a type in SlimMessageBus.Host.Serialization.
- The types involved
SlimMessageBus.Host.Memory.MemoryMessageBus→SlimMessageBus.Host.Serialization.IMessageSerializerProviderSlimMessageBus.Host.Memory.NullMessageSerializerProvider→SlimMessageBus.Host.Serialization.IMessageSerializerSlimMessageBus.Host.Memory.NullMessageSerializerProvider→SlimMessageBus.Host.Serialization.IMessageSerializerProvider
- Direction
- SlimMessageBus.Host.Memory uses SlimMessageBus.Host.Serialization, so a change to SlimMessageBus.Host.Serialization can break SlimMessageBus.Host.Memory, while a change to SlimMessageBus.Host.Memory can't break SlimMessageBus.Host.Serialization.
- Position
- Below the diagonal: SlimMessageBus.Host.Memory uses a module listed above it, which is the healthy direction.
18→6 SlimMessageBus.Host.Memory uses SlimMessageBus.Host✕
- Connections
- 12 pairs of types, where a type in SlimMessageBus.Host.Memory uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Memory.AbstractMessageProcessorQueue→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Memory.ConcurrentMessageProcessorQueue→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Memory.IMemoryConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.Memory.MemoryMessageBus→SlimMessageBus.Host.ConsumerSettingsSlimMessageBus.Host.Memory.MemoryMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.Memory.MemoryMessageBus→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Memory.MemoryMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.Memory.MemoryMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Memory.MemoryMessageBus→SlimMessageBus.Host.ProducerSettingsSlimMessageBus.Host.Memory.MemoryMessageBusBuilder→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Memory.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Memory.MessageProcessorQueue→SlimMessageBus.Host.IMessageProcessor
- Direction
- SlimMessageBus.Host.Memory uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Memory, while a change to SlimMessageBus.Host.Memory can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Memory uses a module listed above it, which is the healthy direction.
18→7 SlimMessageBus.Host.Memory uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Memory uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.Memory.MemoryConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.Memory uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.Memory, while a change to SlimMessageBus.Host.Memory can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.Memory uses a module listed above it, which is the healthy direction.
19→6 SlimMessageBus.Host.Mqtt uses SlimMessageBus.Host✕
- Connections
- 12 pairs of types, where a type in SlimMessageBus.Host.Mqtt uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Mqtt.HasProviderExtensionsExtensions→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.Mqtt.IMqttConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.Mqtt.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Mqtt.MqttMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.Mqtt.MqttMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.Mqtt.MqttMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Mqtt.MqttMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Mqtt.MqttTopicConsumer→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.Mqtt.MqttTopicConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Mqtt.MqttTopicConsumer→SlimMessageBus.Host.IAbstractConsumerInterceptorSlimMessageBus.Host.Mqtt.MqttTopicConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Mqtt.ProducerBuilderExtensions→SlimMessageBus.Host.ProducerBuilder
- Direction
- SlimMessageBus.Host.Mqtt uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Mqtt, while a change to SlimMessageBus.Host.Mqtt can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Mqtt uses a module listed above it, which is the healthy direction.
19→7 SlimMessageBus.Host.Mqtt uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Mqtt uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.Mqtt.MqttConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.Mqtt uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.Mqtt, while a change to SlimMessageBus.Host.Mqtt can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.Mqtt uses a module listed above it, which is the healthy direction.
19→12 SlimMessageBus.Host.Mqtt uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Mqtt uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.Mqtt.MqttMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.Mqtt.MqttMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.Mqtt uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.Mqtt, while a change to SlimMessageBus.Host.Mqtt can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.Mqtt uses a module listed above it, which is the healthy direction.
20→6 SlimMessageBus.Host.Nats uses SlimMessageBus.Host✕
- Connections
- 16 pairs of types, where a type in SlimMessageBus.Host.Nats uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Nats.INatsConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.Nats.NatsConsumerBuilderExtensions→SlimMessageBus.Host.ConsumerBuilderSlimMessageBus.Host.Nats.NatsHandlerBuilderExtensions→SlimMessageBus.Host.HandlerBuilderSlimMessageBus.Host.Nats.NatsMessageBus→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Nats.NatsMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.Nats.NatsMessageBus→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Nats.NatsMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.Nats.NatsMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Nats.NatsMessageBusSettings→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.Nats.NatsMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Nats.NatsProducerBuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.Nats.NatsRequestResponseBuilderExtensions→SlimMessageBus.Host.RequestResponseBuilderSlimMessageBus.Host.Nats.NatsSubjectConsumer→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.Nats.NatsSubjectConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Nats.NatsSubjectConsumer→SlimMessageBus.Host.IAbstractConsumerInterceptorSlimMessageBus.Host.Nats.NatsSubjectConsumer→SlimMessageBus.Host.IMessageProcessor
- Direction
- SlimMessageBus.Host.Nats uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Nats, while a change to SlimMessageBus.Host.Nats can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Nats uses a module listed above it, which is the healthy direction.
20→7 SlimMessageBus.Host.Nats uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Nats uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.Nats.NatsConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.Nats uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.Nats, while a change to SlimMessageBus.Host.Nats can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.Nats uses a module listed above it, which is the healthy direction.
20→12 SlimMessageBus.Host.Nats uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Nats uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.Nats.NatsMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.Nats.NatsMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.Nats uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.Nats, while a change to SlimMessageBus.Host.Nats can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.Nats uses a module listed above it, which is the healthy direction.
21→10 SlimMessageBus.Host.Outbox.MongoDb uses SlimMessageBus.Host.Outbox✕
- Connections
- 3 pairs of types, where a type in SlimMessageBus.Host.Outbox.MongoDb uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.IMongoDbMessageOutboxRepository→SlimMessageBus.Host.Outbox.IOutboxMessageFactorySlimMessageBus.Host.Outbox.MongoDb.IMongoDbMessageOutboxRepository→SlimMessageBus.Host.Outbox.IOutboxMessageRepositorySlimMessageBus.Host.Outbox.MongoDb.MongoDbOutboxMessage→SlimMessageBus.Host.Outbox.OutboxMessage
- Direction
- SlimMessageBus.Host.Outbox.MongoDb uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.MongoDb, while a change to SlimMessageBus.Host.Outbox.MongoDb can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb uses a module listed above it, which is the healthy direction.
22→6 SlimMessageBus.Host.Outbox.MongoDb.Configuration uses SlimMessageBus.Host✕
- Connections
- 5 pairs of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Configuration uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Configuration.BuilderExtensions→SlimMessageBus.Host.ConsumerBuilderSlimMessageBus.Host.Outbox.MongoDb.Configuration.BuilderExtensions→SlimMessageBus.Host.HandlerBuilderSlimMessageBus.Host.Outbox.MongoDb.Configuration.BuilderExtensions→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.Outbox.MongoDb.Configuration.BuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Outbox.MongoDb.Configuration.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilder
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Configuration uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Outbox.MongoDb.Configuration, while a change to SlimMessageBus.Host.Outbox.MongoDb.Configuration can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Configuration uses a module listed above it, which is the healthy direction.
22→10 SlimMessageBus.Host.Outbox.MongoDb.Configuration uses SlimMessageBus.Host.Outbox✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Configuration uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Configuration.MongoDbOutboxSettings→SlimMessageBus.Host.Outbox.OutboxSettings
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Configuration uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.MongoDb.Configuration, while a change to SlimMessageBus.Host.Outbox.MongoDb.Configuration can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Configuration uses a module listed above it, which is the healthy direction.
23→10 SlimMessageBus.Host.Outbox.MongoDb.Transactions uses SlimMessageBus.Host.Outbox✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Transactions uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Transactions.AbstractMongoDbTransactionService→SlimMessageBus.Host.Outbox.AbstractOutboxTransactionService
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Transactions uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.MongoDb.Transactions, while a change to SlimMessageBus.Host.Outbox.MongoDb.Transactions can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Transactions uses a module listed above it, which is the healthy direction.
24→6 SlimMessageBus.Host.Outbox.PostgreSql.Configuration uses SlimMessageBus.Host✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Configuration uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Configuration.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilder
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Configuration uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Outbox.PostgreSql.Configuration, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Configuration can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Configuration uses a module listed above it, which is the healthy direction.
24→10 SlimMessageBus.Host.Outbox.PostgreSql.Configuration uses SlimMessageBus.Host.Outbox✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Configuration uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Configuration.PostgreSqlOutboxSettings→SlimMessageBus.Host.Outbox.OutboxSettings
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Configuration uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.PostgreSql.Configuration, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Configuration can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Configuration uses a module listed above it, which is the healthy direction.
25→1 SlimMessageBus.Host.Outbox.Services uses SlimMessageBus✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Outbox.Services uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.Outbox.Services.OutboxCleanUpTask→SlimMessageBus.IMessageBusSlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.IMessageBus
- Direction
- SlimMessageBus.Host.Outbox.Services uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.Outbox.Services, while a change to SlimMessageBus.Host.Outbox.Services can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Services uses a module listed above it, which is the healthy direction.
25→5 SlimMessageBus.Host.Outbox.Services uses SlimMessageBus.Host.Interceptor✕
- Connections
- 4 pairs of types, where a type in SlimMessageBus.Host.Outbox.Services uses a type in SlimMessageBus.Host.Interceptor.
- The types involved
SlimMessageBus.Host.Outbox.Services.OutboxCleanUpTask→SlimMessageBus.Host.Interceptor.IMessageBusLifecycleInterceptorSlimMessageBus.Host.Outbox.Services.OutboxCleanUpTask→SlimMessageBus.Host.Interceptor.MessageBusLifecycleEventTypeSlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.Host.Interceptor.IMessageBusLifecycleInterceptorSlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.Host.Interceptor.MessageBusLifecycleEventType
- Direction
- SlimMessageBus.Host.Outbox.Services uses SlimMessageBus.Host.Interceptor, so a change to SlimMessageBus.Host.Interceptor can break SlimMessageBus.Host.Outbox.Services, while a change to SlimMessageBus.Host.Outbox.Services can't break SlimMessageBus.Host.Interceptor.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Services uses a module listed above it, which is the healthy direction.
25→6 SlimMessageBus.Host.Outbox.Services uses SlimMessageBus.Host✕
- Connections
- 5 pairs of types, where a type in SlimMessageBus.Host.Outbox.Services uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Outbox.Services.OutboxBulkMessage→SlimMessageBus.Host.BulkMessageEnvelopeSlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.Host.ICompositeMessageBusSlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.Host.IMasterMessageBusSlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.Host.ITransportBulkProducer
- Direction
- SlimMessageBus.Host.Outbox.Services uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Outbox.Services, while a change to SlimMessageBus.Host.Outbox.Services can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Services uses a module listed above it, which is the healthy direction.
25→10 SlimMessageBus.Host.Outbox.Services uses SlimMessageBus.Host.Outbox✕
- Connections
- 7 pairs of types, where a type in SlimMessageBus.Host.Outbox.Services uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.Services.OutboxCleanUpTask→SlimMessageBus.Host.Outbox.OutboxSettingsSlimMessageBus.Host.Outbox.Services.OutboxLockRenewalTimer→SlimMessageBus.Host.Outbox.IInstanceIdProviderSlimMessageBus.Host.Outbox.Services.OutboxLockRenewalTimer→SlimMessageBus.Host.Outbox.IOutboxMessageRepositorySlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.Host.Outbox.AsyncManualResetEventSlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.Host.Outbox.IOutboxMessageRepositorySlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.Host.Outbox.IOutboxNotificationServiceSlimMessageBus.Host.Outbox.Services.OutboxSendingTask→SlimMessageBus.Host.Outbox.OutboxSettings
- Direction
- SlimMessageBus.Host.Outbox.Services uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.Services, while a change to SlimMessageBus.Host.Outbox.Services can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Services uses a module listed above it, which is the healthy direction.
26→3 SlimMessageBus.Host.Outbox.Sql uses SlimMessageBus.Host.Sql.Common✕
- Connections
- 5 pairs of types, where a type in SlimMessageBus.Host.Outbox.Sql uses a type in SlimMessageBus.Host.Sql.Common.
- The types involved
SlimMessageBus.Host.Outbox.Sql.SqlOutboxMessageRepository→SlimMessageBus.Host.Sql.Common.CommonSqlRepositorySlimMessageBus.Host.Outbox.Sql.SqlOutboxMessageRepository→SlimMessageBus.Host.Sql.Common.ISqlTransactionServiceSlimMessageBus.Host.Outbox.Sql.SqlOutboxMigrationService→SlimMessageBus.Host.Sql.Common.CommonSqlMigrationServiceSlimMessageBus.Host.Outbox.Sql.SqlOutboxMigrationService→SlimMessageBus.Host.Sql.Common.ISqlTransactionServiceSlimMessageBus.Host.Outbox.Sql.SqlOutboxSettings→SlimMessageBus.Host.Sql.Common.SqlSettings
- Direction
- SlimMessageBus.Host.Outbox.Sql uses SlimMessageBus.Host.Sql.Common, so a change to SlimMessageBus.Host.Sql.Common can break SlimMessageBus.Host.Outbox.Sql, while a change to SlimMessageBus.Host.Outbox.Sql can't break SlimMessageBus.Host.Sql.Common.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Sql uses a module listed above it, which is the healthy direction.
26→6 SlimMessageBus.Host.Outbox.Sql uses SlimMessageBus.Host✕
- Connections
- 7 pairs of types, where a type in SlimMessageBus.Host.Outbox.Sql uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Outbox.Sql.BuilderExtensions→SlimMessageBus.Host.ConsumerBuilderSlimMessageBus.Host.Outbox.Sql.BuilderExtensions→SlimMessageBus.Host.HandlerBuilderSlimMessageBus.Host.Outbox.Sql.BuilderExtensions→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.Outbox.Sql.BuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Outbox.Sql.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Outbox.Sql.SqlOutboxMessageIdGenerationSettings→SlimMessageBus.Host.IGuidGeneratorSlimMessageBus.Host.Outbox.Sql.SqlOutboxMessageRepository→SlimMessageBus.Host.IGuidGenerator
- Direction
- SlimMessageBus.Host.Outbox.Sql uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Outbox.Sql, while a change to SlimMessageBus.Host.Outbox.Sql can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Sql uses a module listed above it, which is the healthy direction.
26→10 SlimMessageBus.Host.Outbox.Sql uses SlimMessageBus.Host.Outbox✕
- Connections
- 8 pairs of types, where a type in SlimMessageBus.Host.Outbox.Sql uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.Sql.ISqlMessageOutboxRepository→SlimMessageBus.Host.Outbox.IOutboxMessageFactorySlimMessageBus.Host.Outbox.Sql.ISqlMessageOutboxRepository→SlimMessageBus.Host.Outbox.IOutboxMessageRepositorySlimMessageBus.Host.Outbox.Sql.MeasuringSqlMessageOutboxRepositoryDecorator→SlimMessageBus.Host.Outbox.OutboxMessageSlimMessageBus.Host.Outbox.Sql.SqlOutboxMessage→SlimMessageBus.Host.Outbox.OutboxMessageSlimMessageBus.Host.Outbox.Sql.SqlOutboxMessageRepository→SlimMessageBus.Host.Outbox.IInstanceIdProviderSlimMessageBus.Host.Outbox.Sql.SqlOutboxMessageRepository→SlimMessageBus.Host.Outbox.OutboxMessageSlimMessageBus.Host.Outbox.Sql.SqlOutboxMigrationService→SlimMessageBus.Host.Outbox.IOutboxMigrationServiceSlimMessageBus.Host.Outbox.Sql.SqlOutboxSettings→SlimMessageBus.Host.Outbox.OutboxSettings
- Direction
- SlimMessageBus.Host.Outbox.Sql uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.Sql, while a change to SlimMessageBus.Host.Outbox.Sql can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Sql uses a module listed above it, which is the healthy direction.
27→6 SlimMessageBus.Host.PostgreSql uses SlimMessageBus.Host✕
- Connections
- 21 pairs of types, where a type in SlimMessageBus.Host.PostgreSql uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.PostgreSql.IPostgreSqlConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.PostgreSql.PostgreSqlConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.PostgreSql.PostgreSqlConsumer→SlimMessageBus.Host.IAbstractConsumerInterceptorSlimMessageBus.Host.PostgreSql.PostgreSqlConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.PostgreSql.PostgreSqlConsumer→SlimMessageBus.Host.PathKindSlimMessageBus.Host.PostgreSql.PostgreSqlConsumerBuilderExtensions→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.PostgreSql.PostgreSqlConsumerBuilderExtensions→SlimMessageBus.Host.ConsumerBuilderSlimMessageBus.Host.PostgreSql.PostgreSqlHandlerBuilderExtensions→SlimMessageBus.Host.HandlerBuilderSlimMessageBus.Host.PostgreSql.PostgreSqlMessageBus→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.PostgreSql.PostgreSqlMessageBus→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.PostgreSql.PostgreSqlMessageBus→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.PostgreSql.PostgreSqlMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.PostgreSql.PostgreSqlMessageBus→SlimMessageBus.Host.PathKindSlimMessageBus.Host.PostgreSql.PostgreSqlMessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.PostgreSql.PostgreSqlMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.PostgreSql.PostgreSqlMessageIdGenerationSettings→SlimMessageBus.Host.IGuidGeneratorSlimMessageBus.Host.PostgreSql.PostgreSqlProducerBuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.PostgreSql.PostgreSqlRepository→SlimMessageBus.Host.PathKindSlimMessageBus.Host.PostgreSql.PostgreSqlRequestResponseBuilderExtensions→SlimMessageBus.Host.RequestResponseBuilderSlimMessageBus.Host.PostgreSql.PostgreSqlSequentialGuidGenerator→SlimMessageBus.Host.IGuidGeneratorSlimMessageBus.Host.PostgreSql.PostgreSqlTransportMessage→SlimMessageBus.Host.PathKind
- Direction
- SlimMessageBus.Host.PostgreSql uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.PostgreSql, while a change to SlimMessageBus.Host.PostgreSql can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.PostgreSql uses a module listed above it, which is the healthy direction.
27→7 SlimMessageBus.Host.PostgreSql uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.PostgreSql uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.PostgreSql.PostgreSqlConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.PostgreSql uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.PostgreSql, while a change to SlimMessageBus.Host.PostgreSql can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.PostgreSql uses a module listed above it, which is the healthy direction.
27→11 SlimMessageBus.Host.PostgreSql uses SlimMessageBus.Host.Relational✕
- Connections
- 5 pairs of types, where a type in SlimMessageBus.Host.PostgreSql uses a type in SlimMessageBus.Host.Relational.
- The types involved
SlimMessageBus.Host.PostgreSql.IPostgreSqlRepository→SlimMessageBus.Host.Relational.IRelationalRepositorySlimMessageBus.Host.PostgreSql.PostgreSqlConsumer→SlimMessageBus.Host.Relational.RelationalConsumerBaseSlimMessageBus.Host.PostgreSql.PostgreSqlMessageBus→SlimMessageBus.Host.Relational.RelationalMessageBusBaseSlimMessageBus.Host.PostgreSql.PostgreSqlMessageBusSettings→SlimMessageBus.Host.Relational.IRelationalMessageBusSettingsSlimMessageBus.Host.PostgreSql.PostgreSqlTransportMessage→SlimMessageBus.Host.Relational.IRelationalTransportMessage
- Direction
- SlimMessageBus.Host.PostgreSql uses SlimMessageBus.Host.Relational, so a change to SlimMessageBus.Host.Relational can break SlimMessageBus.Host.PostgreSql, while a change to SlimMessageBus.Host.PostgreSql can't break SlimMessageBus.Host.Relational.
- Position
- Below the diagonal: SlimMessageBus.Host.PostgreSql uses a module listed above it, which is the healthy direction.
27→12 SlimMessageBus.Host.PostgreSql uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.PostgreSql uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.PostgreSql.PostgreSqlMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.PostgreSql.PostgreSqlMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.PostgreSql uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.PostgreSql, while a change to SlimMessageBus.Host.PostgreSql can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.PostgreSql uses a module listed above it, which is the healthy direction.
28→1 SlimMessageBus.Host.RabbitMQ uses SlimMessageBus✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.RabbitMQ uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.RabbitMQ.RabbitMqConsumerContextExtensions→SlimMessageBus.IConsumerContext
- Direction
- SlimMessageBus.Host.RabbitMQ uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.RabbitMQ, while a change to SlimMessageBus.Host.RabbitMQ can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.RabbitMQ uses a module listed above it, which is the healthy direction.
28→6 SlimMessageBus.Host.RabbitMQ uses SlimMessageBus.Host✕
- Connections
- 40 pairs of types, where a type in SlimMessageBus.Host.RabbitMQ uses a type in SlimMessageBus.Host. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SlimMessageBus.Host.RabbitMQ.AbstractRabbitMqConsumer→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.RabbitMQ.AbstractRabbitMqConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.RabbitMQ.AbstractRabbitMqConsumer→SlimMessageBus.Host.IAbstractConsumerInterceptorSlimMessageBus.Host.RabbitMQ.IRabbitMqConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.RabbitMQ.RabbitMqAutoAcknowledgeMessageProcessor→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.RabbitMQ.RabbitMqAutoAcknowledgeMessageProcessor→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.RabbitMQ.RabbitMqAutoAcknowledgeMessageProcessor→SlimMessageBus.Host.ProcessMessageResultSlimMessageBus.Host.RabbitMQ.RabbitMqChannelManager→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.RabbitMQ.RabbitMqConsumer→SlimMessageBus.Host.ConsumerContextSlimMessageBus.Host.RabbitMQ.RabbitMqConsumer→SlimMessageBus.Host.ConsumerSettingsSlimMessageBus.Host.RabbitMQ.RabbitMqConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.RabbitMQ.RabbitMqConsumer→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.RabbitMQ.RabbitMqConsumer→SlimMessageBus.Host.MessageProviderSlimMessageBus.Host.RabbitMQ.RabbitMqConsumerErrorHandler→SlimMessageBus.Host.ProcessResultSlimMessageBus.Host.RabbitMQ.RabbitMqHasProviderExtensions→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.RabbitMQ.RabbitMqHasProviderExtensions→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.RabbitMQ.RabbitMqHasProviderExtensions→SlimMessageBus.Host.ProducerSettingsSlimMessageBus.Host.RabbitMQ.RabbitMqMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.RabbitMQ.RabbitMqMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.RabbitMQ.RabbitMqMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.RabbitMQ.RabbitMqMessageBus→SlimMessageBus.Host.ProduceToTransportBulkResultSlimMessageBus.Host.RabbitMQ.RabbitMqMessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.RabbitMQ.RabbitMqMessageBusSettings→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.RabbitMQ.RabbitMqMessageBusSettingsValidationService→SlimMessageBus.Host.ConsumerSettingsSlimMessageBus.Host.RabbitMQ.RabbitMqMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettings
- Direction
- SlimMessageBus.Host.RabbitMQ uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.RabbitMQ, while a change to SlimMessageBus.Host.RabbitMQ can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.RabbitMQ uses a module listed above it, which is the healthy direction.
28→7 SlimMessageBus.Host.RabbitMQ uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.RabbitMQ uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.RabbitMQ.RabbitMqConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.RabbitMQ uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.RabbitMQ, while a change to SlimMessageBus.Host.RabbitMQ can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.RabbitMQ uses a module listed above it, which is the healthy direction.
28→12 SlimMessageBus.Host.RabbitMQ uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.RabbitMQ uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.RabbitMQ.RabbitMqMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.RabbitMQ.RabbitMqMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.RabbitMQ uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.RabbitMQ, while a change to SlimMessageBus.Host.RabbitMQ can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.RabbitMQ uses a module listed above it, which is the healthy direction.
29→2 SlimMessageBus.Host.Redis uses SlimMessageBus.Host.Serialization✕
- Connections
- 3 pairs of types, where a type in SlimMessageBus.Host.Redis uses a type in SlimMessageBus.Host.Serialization.
- The types involved
SlimMessageBus.Host.Redis.RedisListCheckerConsumer→SlimMessageBus.Host.Serialization.IMessageSerializerSlimMessageBus.Host.Redis.RedisMessageBusSettings→SlimMessageBus.Host.Serialization.IMessageSerializerSlimMessageBus.Host.Redis.RedisTopicConsumer→SlimMessageBus.Host.Serialization.IMessageSerializer
- Direction
- SlimMessageBus.Host.Redis uses SlimMessageBus.Host.Serialization, so a change to SlimMessageBus.Host.Serialization can break SlimMessageBus.Host.Redis, while a change to SlimMessageBus.Host.Redis can't break SlimMessageBus.Host.Serialization.
- Position
- Below the diagonal: SlimMessageBus.Host.Redis uses a module listed above it, which is the healthy direction.
29→4 SlimMessageBus.Host.Redis uses SlimMessageBus.Host.Collections✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Redis uses a type in SlimMessageBus.Host.Collections.
- The types involved
SlimMessageBus.Host.Redis.RedisMessageBus→SlimMessageBus.Host.Collections.KindMapping
- Direction
- SlimMessageBus.Host.Redis uses SlimMessageBus.Host.Collections, so a change to SlimMessageBus.Host.Collections can break SlimMessageBus.Host.Redis, while a change to SlimMessageBus.Host.Redis can't break SlimMessageBus.Host.Collections.
- Position
- Below the diagonal: SlimMessageBus.Host.Redis uses a module listed above it, which is the healthy direction.
29→6 SlimMessageBus.Host.Redis uses SlimMessageBus.Host✕
- Connections
- 22 pairs of types, where a type in SlimMessageBus.Host.Redis uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Redis.IRedisConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.Redis.QueueProcessors→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Redis.QueueProcessors→SlimMessageBus.Host.MessageWithHeadersSlimMessageBus.Host.Redis.RedisConsumerBuilderExtensions→SlimMessageBus.Host.ConsumerBuilderSlimMessageBus.Host.Redis.RedisHandlerBuilderExtensions→SlimMessageBus.Host.HandlerBuilderSlimMessageBus.Host.Redis.RedisListCheckerConsumer→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.Redis.RedisListCheckerConsumer→SlimMessageBus.Host.IAbstractConsumerInterceptorSlimMessageBus.Host.Redis.RedisListCheckerConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Redis.RedisListCheckerConsumer→SlimMessageBus.Host.MessageWithHeadersSlimMessageBus.Host.Redis.RedisMessageBus→SlimMessageBus.Host.IMessageBusTargetSlimMessageBus.Host.Redis.RedisMessageBus→SlimMessageBus.Host.MessageBusBaseSlimMessageBus.Host.Redis.RedisMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Redis.RedisMessageBus→SlimMessageBus.Host.PathKindSlimMessageBus.Host.Redis.RedisMessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Redis.RedisMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Redis.RedisProducerBuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.Redis.RedisRequestResponseBuilderExtensions→SlimMessageBus.Host.RequestResponseBuilderSlimMessageBus.Host.Redis.RedisTopicConsumer→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.Redis.RedisTopicConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Redis.RedisTopicConsumer→SlimMessageBus.Host.IAbstractConsumerInterceptorSlimMessageBus.Host.Redis.RedisTopicConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Redis.RedisTopicConsumer→SlimMessageBus.Host.MessageWithHeaders
- Direction
- SlimMessageBus.Host.Redis uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Redis, while a change to SlimMessageBus.Host.Redis can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Redis uses a module listed above it, which is the healthy direction.
29→7 SlimMessageBus.Host.Redis uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Redis uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.Redis.RedisConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.Redis uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.Redis, while a change to SlimMessageBus.Host.Redis can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.Redis uses a module listed above it, which is the healthy direction.
29→12 SlimMessageBus.Host.Redis uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Redis uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.Redis.RedisMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.Redis.RedisMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.Redis uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.Redis, while a change to SlimMessageBus.Host.Redis can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.Redis uses a module listed above it, which is the healthy direction.
30→3 SlimMessageBus.Host.Sql uses SlimMessageBus.Host.Sql.Common✕
- Connections
- 5 pairs of types, where a type in SlimMessageBus.Host.Sql uses a type in SlimMessageBus.Host.Sql.Common.
- The types involved
SlimMessageBus.Host.Sql.SqlMessageBusSettings→SlimMessageBus.Host.Sql.Common.SqlSettingsSlimMessageBus.Host.Sql.SqlRepository→SlimMessageBus.Host.Sql.Common.CommonSqlRepositorySlimMessageBus.Host.Sql.SqlRepository→SlimMessageBus.Host.Sql.Common.ISqlTransactionServiceSlimMessageBus.Host.Sql.SqlTopologyService→SlimMessageBus.Host.Sql.Common.CommonSqlMigrationServiceSlimMessageBus.Host.Sql.SqlTopologyService→SlimMessageBus.Host.Sql.Common.ISqlTransactionService
- Direction
- SlimMessageBus.Host.Sql uses SlimMessageBus.Host.Sql.Common, so a change to SlimMessageBus.Host.Sql.Common can break SlimMessageBus.Host.Sql, while a change to SlimMessageBus.Host.Sql can't break SlimMessageBus.Host.Sql.Common.
- Position
- Below the diagonal: SlimMessageBus.Host.Sql uses a module listed above it, which is the healthy direction.
30→6 SlimMessageBus.Host.Sql uses SlimMessageBus.Host✕
- Connections
- 21 pairs of types, where a type in SlimMessageBus.Host.Sql uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Sql.ISqlConsumerErrorHandler→SlimMessageBus.Host.IConsumerErrorHandlerSlimMessageBus.Host.Sql.SqlConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Sql.SqlConsumer→SlimMessageBus.Host.IAbstractConsumerInterceptorSlimMessageBus.Host.Sql.SqlConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Sql.SqlConsumer→SlimMessageBus.Host.PathKindSlimMessageBus.Host.Sql.SqlConsumerBuilderExtensions→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Sql.SqlConsumerBuilderExtensions→SlimMessageBus.Host.ConsumerBuilderSlimMessageBus.Host.Sql.SqlHandlerBuilderExtensions→SlimMessageBus.Host.HandlerBuilderSlimMessageBus.Host.Sql.SqlMessageBus→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.Sql.SqlMessageBus→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.Sql.SqlMessageBus→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.Sql.SqlMessageBus→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Sql.SqlMessageBus→SlimMessageBus.Host.PathKindSlimMessageBus.Host.Sql.SqlMessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilderSlimMessageBus.Host.Sql.SqlMessageBusSettingsValidationService→SlimMessageBus.Host.MessageBusSettingsSlimMessageBus.Host.Sql.SqlMessageIdGenerationSettings→SlimMessageBus.Host.IGuidGeneratorSlimMessageBus.Host.Sql.SqlProducerBuilderExtensions→SlimMessageBus.Host.ProducerBuilderSlimMessageBus.Host.Sql.SqlRepository→SlimMessageBus.Host.PathKindSlimMessageBus.Host.Sql.SqlRequestResponseBuilderExtensions→SlimMessageBus.Host.RequestResponseBuilderSlimMessageBus.Host.Sql.SqlSequentialGuidGenerator→SlimMessageBus.Host.IGuidGeneratorSlimMessageBus.Host.Sql.SqlTransportMessage→SlimMessageBus.Host.PathKind
- Direction
- SlimMessageBus.Host.Sql uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Sql, while a change to SlimMessageBus.Host.Sql can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Sql uses a module listed above it, which is the healthy direction.
30→7 SlimMessageBus.Host.Sql uses SlimMessageBus.Host.Consumer.ErrorHandling✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Sql uses a type in SlimMessageBus.Host.Consumer.ErrorHandling.
- The types involved
SlimMessageBus.Host.Sql.SqlConsumerErrorHandler→SlimMessageBus.Host.Consumer.ErrorHandling.ConsumerErrorHandler
- Direction
- SlimMessageBus.Host.Sql uses SlimMessageBus.Host.Consumer.ErrorHandling, so a change to SlimMessageBus.Host.Consumer.ErrorHandling can break SlimMessageBus.Host.Sql, while a change to SlimMessageBus.Host.Sql can't break SlimMessageBus.Host.Consumer.ErrorHandling.
- Position
- Below the diagonal: SlimMessageBus.Host.Sql uses a module listed above it, which is the healthy direction.
30→11 SlimMessageBus.Host.Sql uses SlimMessageBus.Host.Relational✕
- Connections
- 5 pairs of types, where a type in SlimMessageBus.Host.Sql uses a type in SlimMessageBus.Host.Relational.
- The types involved
SlimMessageBus.Host.Sql.ISqlRepository→SlimMessageBus.Host.Relational.IRelationalRepositorySlimMessageBus.Host.Sql.SqlConsumer→SlimMessageBus.Host.Relational.RelationalConsumerBaseSlimMessageBus.Host.Sql.SqlMessageBus→SlimMessageBus.Host.Relational.RelationalMessageBusBaseSlimMessageBus.Host.Sql.SqlMessageBusSettings→SlimMessageBus.Host.Relational.IRelationalMessageBusSettingsSlimMessageBus.Host.Sql.SqlTransportMessage→SlimMessageBus.Host.Relational.IRelationalTransportMessage
- Direction
- SlimMessageBus.Host.Sql uses SlimMessageBus.Host.Relational, so a change to SlimMessageBus.Host.Relational can break SlimMessageBus.Host.Sql, while a change to SlimMessageBus.Host.Sql can't break SlimMessageBus.Host.Relational.
- Position
- Below the diagonal: SlimMessageBus.Host.Sql uses a module listed above it, which is the healthy direction.
30→12 SlimMessageBus.Host.Sql uses SlimMessageBus.Host.Services✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Sql uses a type in SlimMessageBus.Host.Services.
- The types involved
SlimMessageBus.Host.Sql.SqlMessageBus→SlimMessageBus.Host.Services.IMessageBusSettingsValidationServiceSlimMessageBus.Host.Sql.SqlMessageBusSettingsValidationService→SlimMessageBus.Host.Services.DefaultMessageBusSettingsValidationService
- Direction
- SlimMessageBus.Host.Sql uses SlimMessageBus.Host.Services, so a change to SlimMessageBus.Host.Services can break SlimMessageBus.Host.Sql, while a change to SlimMessageBus.Host.Sql can't break SlimMessageBus.Host.Services.
- Position
- Below the diagonal: SlimMessageBus.Host.Sql uses a module listed above it, which is the healthy direction.
31→6 SlimMessageBus.Host.AzureServiceBus.Consumer uses SlimMessageBus.Host✕
- Connections
- 7 pairs of types, where a type in SlimMessageBus.Host.AzureServiceBus.Consumer uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.AzureServiceBus.Consumer.AsbBaseConsumer→SlimMessageBus.Host.AbstractConsumerSlimMessageBus.Host.AzureServiceBus.Consumer.AsbBaseConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AzureServiceBus.Consumer.AsbBaseConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.AzureServiceBus.Consumer.AsbQueueConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AzureServiceBus.Consumer.AsbQueueConsumer→SlimMessageBus.Host.IMessageProcessorSlimMessageBus.Host.AzureServiceBus.Consumer.AsbTopicSubscriptionConsumer→SlimMessageBus.Host.AbstractConsumerSettingsSlimMessageBus.Host.AzureServiceBus.Consumer.AsbTopicSubscriptionConsumer→SlimMessageBus.Host.IMessageProcessor
- Direction
- SlimMessageBus.Host.AzureServiceBus.Consumer uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.AzureServiceBus.Consumer, while a change to SlimMessageBus.Host.AzureServiceBus.Consumer can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureServiceBus.Consumer uses a module listed above it, which is the healthy direction.
31→15 SlimMessageBus.Host.AzureServiceBus.Consumer uses SlimMessageBus.Host.AzureServiceBus✕
- Connections
- 6 pairs of types, where a type in SlimMessageBus.Host.AzureServiceBus.Consumer uses a type in SlimMessageBus.Host.AzureServiceBus.
- The types involved
SlimMessageBus.Host.AzureServiceBus.Consumer.AsbBaseConsumer→SlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBusSlimMessageBus.Host.AzureServiceBus.Consumer.AsbBaseConsumer→SlimMessageBus.Host.AzureServiceBus.TopicSubscriptionParamsSlimMessageBus.Host.AzureServiceBus.Consumer.AsbQueueConsumer→SlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBusSlimMessageBus.Host.AzureServiceBus.Consumer.AsbQueueConsumer→SlimMessageBus.Host.AzureServiceBus.TopicSubscriptionParamsSlimMessageBus.Host.AzureServiceBus.Consumer.AsbTopicSubscriptionConsumer→SlimMessageBus.Host.AzureServiceBus.ServiceBusMessageBusSlimMessageBus.Host.AzureServiceBus.Consumer.AsbTopicSubscriptionConsumer→SlimMessageBus.Host.AzureServiceBus.TopicSubscriptionParams
- Direction
- SlimMessageBus.Host.AzureServiceBus.Consumer uses SlimMessageBus.Host.AzureServiceBus, so a change to SlimMessageBus.Host.AzureServiceBus can break SlimMessageBus.Host.AzureServiceBus.Consumer, while a change to SlimMessageBus.Host.AzureServiceBus.Consumer can't break SlimMessageBus.Host.AzureServiceBus.
- Position
- Below the diagonal: SlimMessageBus.Host.AzureServiceBus.Consumer uses a module listed above it, which is the healthy direction.
32→1 SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses SlimMessageBus✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Interceptors.MongoDbTransactionConsumerInterceptor→SlimMessageBus.IConsumerContext
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.Outbox.MongoDb.Interceptors, while a change to SlimMessageBus.Host.Outbox.MongoDb.Interceptors can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses a module listed above it, which is the healthy direction.
32→5 SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses SlimMessageBus.Host.Interceptor✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses a type in SlimMessageBus.Host.Interceptor.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Interceptors.MongoDbTransactionConsumerInterceptor→SlimMessageBus.Host.Interceptor.IConsumerInterceptor
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses SlimMessageBus.Host.Interceptor, so a change to SlimMessageBus.Host.Interceptor can break SlimMessageBus.Host.Outbox.MongoDb.Interceptors, while a change to SlimMessageBus.Host.Outbox.MongoDb.Interceptors can't break SlimMessageBus.Host.Interceptor.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses a module listed above it, which is the healthy direction.
32→23 SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses SlimMessageBus.Host.Outbox.MongoDb.Transactions✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses a type in SlimMessageBus.Host.Outbox.MongoDb.Transactions.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Interceptors.MongoDbTransactionConsumerInterceptor→SlimMessageBus.Host.Outbox.MongoDb.Transactions.IMongoDbTransactionService
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses SlimMessageBus.Host.Outbox.MongoDb.Transactions, so a change to SlimMessageBus.Host.Outbox.MongoDb.Transactions can break SlimMessageBus.Host.Outbox.MongoDb.Interceptors, while a change to SlimMessageBus.Host.Outbox.MongoDb.Interceptors can't break SlimMessageBus.Host.Outbox.MongoDb.Transactions.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Interceptors uses a module listed above it, which is the healthy direction.
33→10 SlimMessageBus.Host.Outbox.MongoDb.Repositories uses SlimMessageBus.Host.Outbox✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Repositories uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Repositories.MongoDbOutboxMessageRepository→SlimMessageBus.Host.Outbox.OutboxMessage
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Repositories uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.MongoDb.Repositories, while a change to SlimMessageBus.Host.Outbox.MongoDb.Repositories can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Repositories uses a module listed above it, which is the healthy direction.
33→21 SlimMessageBus.Host.Outbox.MongoDb.Repositories uses SlimMessageBus.Host.Outbox.MongoDb✕
- Connections
- 5 pairs of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Repositories uses a type in SlimMessageBus.Host.Outbox.MongoDb.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Repositories.MongoDbOutboxMessageRepository→SlimMessageBus.Host.Outbox.MongoDb.IMongoDbMessageOutboxRepositorySlimMessageBus.Host.Outbox.MongoDb.Repositories.MongoDbOutboxMessageRepository→SlimMessageBus.Host.Outbox.MongoDb.MongoDbOutboxAdminMessageSlimMessageBus.Host.Outbox.MongoDb.Repositories.MongoDbOutboxMessageRepository→SlimMessageBus.Host.Outbox.MongoDb.MongoDbOutboxDocumentSlimMessageBus.Host.Outbox.MongoDb.Repositories.MongoDbOutboxMessageRepository→SlimMessageBus.Host.Outbox.MongoDb.MongoDbOutboxLockDocumentSlimMessageBus.Host.Outbox.MongoDb.Repositories.MongoDbOutboxMessageRepository→SlimMessageBus.Host.Outbox.MongoDb.MongoDbOutboxMessage
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Repositories uses SlimMessageBus.Host.Outbox.MongoDb, so a change to SlimMessageBus.Host.Outbox.MongoDb can break SlimMessageBus.Host.Outbox.MongoDb.Repositories, while a change to SlimMessageBus.Host.Outbox.MongoDb.Repositories can't break SlimMessageBus.Host.Outbox.MongoDb.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Repositories uses a module listed above it, which is the healthy direction.
33→23 SlimMessageBus.Host.Outbox.MongoDb.Repositories uses SlimMessageBus.Host.Outbox.MongoDb.Transactions✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Repositories uses a type in SlimMessageBus.Host.Outbox.MongoDb.Transactions.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Repositories.MongoDbOutboxMessageRepository→SlimMessageBus.Host.Outbox.MongoDb.Transactions.IMongoDbTransactionService
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Repositories uses SlimMessageBus.Host.Outbox.MongoDb.Transactions, so a change to SlimMessageBus.Host.Outbox.MongoDb.Transactions can break SlimMessageBus.Host.Outbox.MongoDb.Repositories, while a change to SlimMessageBus.Host.Outbox.MongoDb.Repositories can't break SlimMessageBus.Host.Outbox.MongoDb.Transactions.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Repositories uses a module listed above it, which is the healthy direction.
34→10 SlimMessageBus.Host.Outbox.MongoDb.Services uses SlimMessageBus.Host.Outbox✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Services uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Services.MongoDbOutboxMigrationService→SlimMessageBus.Host.Outbox.IOutboxMigrationService
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Services uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.MongoDb.Services, while a change to SlimMessageBus.Host.Outbox.MongoDb.Services can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Services uses a module listed above it, which is the healthy direction.
34→21 SlimMessageBus.Host.Outbox.MongoDb.Services uses SlimMessageBus.Host.Outbox.MongoDb✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Services uses a type in SlimMessageBus.Host.Outbox.MongoDb.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Services.MongoDbOutboxMigrationService→SlimMessageBus.Host.Outbox.MongoDb.MongoDbMigrationDocument
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Services uses SlimMessageBus.Host.Outbox.MongoDb, so a change to SlimMessageBus.Host.Outbox.MongoDb can break SlimMessageBus.Host.Outbox.MongoDb.Services, while a change to SlimMessageBus.Host.Outbox.MongoDb.Services can't break SlimMessageBus.Host.Outbox.MongoDb.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Services uses a module listed above it, which is the healthy direction.
34→22 SlimMessageBus.Host.Outbox.MongoDb.Services uses SlimMessageBus.Host.Outbox.MongoDb.Configuration✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.MongoDb.Services uses a type in SlimMessageBus.Host.Outbox.MongoDb.Configuration.
- The types involved
SlimMessageBus.Host.Outbox.MongoDb.Services.MongoDbOutboxMigrationService→SlimMessageBus.Host.Outbox.MongoDb.Configuration.MongoDbSettings
- Direction
- SlimMessageBus.Host.Outbox.MongoDb.Services uses SlimMessageBus.Host.Outbox.MongoDb.Configuration, so a change to SlimMessageBus.Host.Outbox.MongoDb.Configuration can break SlimMessageBus.Host.Outbox.MongoDb.Services, while a change to SlimMessageBus.Host.Outbox.MongoDb.Services can't break SlimMessageBus.Host.Outbox.MongoDb.Configuration.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.MongoDb.Services uses a module listed above it, which is the healthy direction.
35→10 SlimMessageBus.Host.Outbox.PostgreSql.Transactions uses SlimMessageBus.Host.Outbox✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Transactions uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Transactions.AbstractPostgreSqlTransactionService→SlimMessageBus.Host.Outbox.AbstractOutboxTransactionService
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Transactions uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.PostgreSql.Transactions, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Transactions can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Transactions uses a module listed above it, which is the healthy direction.
35→24 SlimMessageBus.Host.Outbox.PostgreSql.Transactions uses SlimMessageBus.Host.Outbox.PostgreSql.Configuration✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Transactions uses a type in SlimMessageBus.Host.Outbox.PostgreSql.Configuration.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Transactions.PostgreSqlTransactionService→SlimMessageBus.Host.Outbox.PostgreSql.Configuration.PostgreSqlSettings
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Transactions uses SlimMessageBus.Host.Outbox.PostgreSql.Configuration, so a change to SlimMessageBus.Host.Outbox.PostgreSql.Configuration can break SlimMessageBus.Host.Outbox.PostgreSql.Transactions, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Transactions can't break SlimMessageBus.Host.Outbox.PostgreSql.Configuration.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Transactions uses a module listed above it, which is the healthy direction.
36→3 SlimMessageBus.Host.Outbox.Sql.DbContext uses SlimMessageBus.Host.Sql.Common✕
- Connections
- 3 pairs of types, where a type in SlimMessageBus.Host.Outbox.Sql.DbContext uses a type in SlimMessageBus.Host.Sql.Common.
- The types involved
SlimMessageBus.Host.Outbox.Sql.DbContext.DbContextOutboxRepository→SlimMessageBus.Host.Sql.Common.ISqlTransactionServiceSlimMessageBus.Host.Outbox.Sql.DbContext.DbContextTransactionService→SlimMessageBus.Host.Sql.Common.AbstractSqlTransactionServiceSlimMessageBus.Host.Outbox.Sql.DbContext.DbContextTransactionService→SlimMessageBus.Host.Sql.Common.ISqlSettings
- Direction
- SlimMessageBus.Host.Outbox.Sql.DbContext uses SlimMessageBus.Host.Sql.Common, so a change to SlimMessageBus.Host.Sql.Common can break SlimMessageBus.Host.Outbox.Sql.DbContext, while a change to SlimMessageBus.Host.Outbox.Sql.DbContext can't break SlimMessageBus.Host.Sql.Common.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Sql.DbContext uses a module listed above it, which is the healthy direction.
36→6 SlimMessageBus.Host.Outbox.Sql.DbContext uses SlimMessageBus.Host✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Outbox.Sql.DbContext uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Outbox.Sql.DbContext.DbContextOutboxRepository→SlimMessageBus.Host.IGuidGeneratorSlimMessageBus.Host.Outbox.Sql.DbContext.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilder
- Direction
- SlimMessageBus.Host.Outbox.Sql.DbContext uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Outbox.Sql.DbContext, while a change to SlimMessageBus.Host.Outbox.Sql.DbContext can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Sql.DbContext uses a module listed above it, which is the healthy direction.
36→10 SlimMessageBus.Host.Outbox.Sql.DbContext uses SlimMessageBus.Host.Outbox✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.Sql.DbContext uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.Sql.DbContext.DbContextOutboxRepository→SlimMessageBus.Host.Outbox.IInstanceIdProvider
- Direction
- SlimMessageBus.Host.Outbox.Sql.DbContext uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.Sql.DbContext, while a change to SlimMessageBus.Host.Outbox.Sql.DbContext can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Sql.DbContext uses a module listed above it, which is the healthy direction.
36→26 SlimMessageBus.Host.Outbox.Sql.DbContext uses SlimMessageBus.Host.Outbox.Sql✕
- Connections
- 4 pairs of types, where a type in SlimMessageBus.Host.Outbox.Sql.DbContext uses a type in SlimMessageBus.Host.Outbox.Sql.
- The types involved
SlimMessageBus.Host.Outbox.Sql.DbContext.DbContextOutboxRepository→SlimMessageBus.Host.Outbox.Sql.ISqlOutboxTemplateSlimMessageBus.Host.Outbox.Sql.DbContext.DbContextOutboxRepository→SlimMessageBus.Host.Outbox.Sql.SqlOutboxMessageRepositorySlimMessageBus.Host.Outbox.Sql.DbContext.DbContextOutboxRepository→SlimMessageBus.Host.Outbox.Sql.SqlOutboxSettingsSlimMessageBus.Host.Outbox.Sql.DbContext.MessageBusBuilderExtensions→SlimMessageBus.Host.Outbox.Sql.SqlOutboxSettings
- Direction
- SlimMessageBus.Host.Outbox.Sql.DbContext uses SlimMessageBus.Host.Outbox.Sql, so a change to SlimMessageBus.Host.Outbox.Sql can break SlimMessageBus.Host.Outbox.Sql.DbContext, while a change to SlimMessageBus.Host.Outbox.Sql.DbContext can't break SlimMessageBus.Host.Outbox.Sql.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.Sql.DbContext uses a module listed above it, which is the healthy direction.
37→1 SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql uses a type in SlimMessageBus.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.PostgreSqlTransactionConsumerInterceptor→SlimMessageBus.IConsumerContext
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus, so a change to SlimMessageBus can break SlimMessageBus.Host.Outbox.PostgreSql, while a change to SlimMessageBus.Host.Outbox.PostgreSql can't break SlimMessageBus.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql uses a module listed above it, which is the healthy direction.
37→5 SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus.Host.Interceptor✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql uses a type in SlimMessageBus.Host.Interceptor.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.PostgreSqlTransactionConsumerInterceptor→SlimMessageBus.Host.Interceptor.IConsumerInterceptor
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus.Host.Interceptor, so a change to SlimMessageBus.Host.Interceptor can break SlimMessageBus.Host.Outbox.PostgreSql, while a change to SlimMessageBus.Host.Outbox.PostgreSql can't break SlimMessageBus.Host.Interceptor.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql uses a module listed above it, which is the healthy direction.
37→6 SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus.Host✕
- Connections
- 4 pairs of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.BuilderExtensions→SlimMessageBus.Host.ConsumerBuilderSlimMessageBus.Host.Outbox.PostgreSql.BuilderExtensions→SlimMessageBus.Host.HandlerBuilderSlimMessageBus.Host.Outbox.PostgreSql.BuilderExtensions→SlimMessageBus.Host.HasProviderExtensionsSlimMessageBus.Host.Outbox.PostgreSql.BuilderExtensions→SlimMessageBus.Host.MessageBusBuilder
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Outbox.PostgreSql, while a change to SlimMessageBus.Host.Outbox.PostgreSql can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql uses a module listed above it, which is the healthy direction.
37→10 SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus.Host.Outbox✕
- Connections
- 3 pairs of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.IPostgreSqlMessageOutboxRepository→SlimMessageBus.Host.Outbox.IOutboxMessageFactorySlimMessageBus.Host.Outbox.PostgreSql.IPostgreSqlMessageOutboxRepository→SlimMessageBus.Host.Outbox.IOutboxMessageRepositorySlimMessageBus.Host.Outbox.PostgreSql.PostgreSqlOutboxMessage→SlimMessageBus.Host.Outbox.OutboxMessage
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.PostgreSql, while a change to SlimMessageBus.Host.Outbox.PostgreSql can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql uses a module listed above it, which is the healthy direction.
37→24 SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus.Host.Outbox.PostgreSql.Configuration✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql uses a type in SlimMessageBus.Host.Outbox.PostgreSql.Configuration.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.IPostgreSqlRepository→SlimMessageBus.Host.Outbox.PostgreSql.Configuration.RetrySettingsSlimMessageBus.Host.Outbox.PostgreSql.PostgreSqlOutboxTemplate→SlimMessageBus.Host.Outbox.PostgreSql.Configuration.PostgreSqlSettings
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus.Host.Outbox.PostgreSql.Configuration, so a change to SlimMessageBus.Host.Outbox.PostgreSql.Configuration can break SlimMessageBus.Host.Outbox.PostgreSql, while a change to SlimMessageBus.Host.Outbox.PostgreSql can't break SlimMessageBus.Host.Outbox.PostgreSql.Configuration.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql uses a module listed above it, which is the healthy direction.
37→35 SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus.Host.Outbox.PostgreSql.Transactions✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql uses a type in SlimMessageBus.Host.Outbox.PostgreSql.Transactions.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.PostgreSqlTransactionConsumerInterceptor→SlimMessageBus.Host.Outbox.PostgreSql.Transactions.IPostgreSqlTransactionService
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql uses SlimMessageBus.Host.Outbox.PostgreSql.Transactions, so a change to SlimMessageBus.Host.Outbox.PostgreSql.Transactions can break SlimMessageBus.Host.Outbox.PostgreSql, while a change to SlimMessageBus.Host.Outbox.PostgreSql can't break SlimMessageBus.Host.Outbox.PostgreSql.Transactions.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql uses a module listed above it, which is the healthy direction.
38→10 SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses SlimMessageBus.Host.Outbox✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Repositories.PostgreSqlOutboxMessageRepository→SlimMessageBus.Host.Outbox.OutboxMessage
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.PostgreSql.Repositories, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Repositories can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses a module listed above it, which is the healthy direction.
38→24 SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses SlimMessageBus.Host.Outbox.PostgreSql.Configuration✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses a type in SlimMessageBus.Host.Outbox.PostgreSql.Configuration.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Repositories.PostgreSqlOutboxMessageRepository→SlimMessageBus.Host.Outbox.PostgreSql.Configuration.PostgreSqlSettingsSlimMessageBus.Host.Outbox.PostgreSql.Repositories.PostgreSqlOutboxMessageRepository→SlimMessageBus.Host.Outbox.PostgreSql.Configuration.RetrySettings
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses SlimMessageBus.Host.Outbox.PostgreSql.Configuration, so a change to SlimMessageBus.Host.Outbox.PostgreSql.Configuration can break SlimMessageBus.Host.Outbox.PostgreSql.Repositories, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Repositories can't break SlimMessageBus.Host.Outbox.PostgreSql.Configuration.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses a module listed above it, which is the healthy direction.
38→35 SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses SlimMessageBus.Host.Outbox.PostgreSql.Transactions✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses a type in SlimMessageBus.Host.Outbox.PostgreSql.Transactions.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Repositories.PostgreSqlOutboxMessageRepository→SlimMessageBus.Host.Outbox.PostgreSql.Transactions.IPostgreSqlTransactionService
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses SlimMessageBus.Host.Outbox.PostgreSql.Transactions, so a change to SlimMessageBus.Host.Outbox.PostgreSql.Transactions can break SlimMessageBus.Host.Outbox.PostgreSql.Repositories, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Repositories can't break SlimMessageBus.Host.Outbox.PostgreSql.Transactions.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses a module listed above it, which is the healthy direction.
38→37 SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses SlimMessageBus.Host.Outbox.PostgreSql✕
- Connections
- 4 pairs of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses a type in SlimMessageBus.Host.Outbox.PostgreSql.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Repositories.PostgreSqlOutboxMessageRepository→SlimMessageBus.Host.Outbox.PostgreSql.IPostgreSqlMessageOutboxRepositorySlimMessageBus.Host.Outbox.PostgreSql.Repositories.PostgreSqlOutboxMessageRepository→SlimMessageBus.Host.Outbox.PostgreSql.IPostgreSqlOutboxTemplateSlimMessageBus.Host.Outbox.PostgreSql.Repositories.PostgreSqlOutboxMessageRepository→SlimMessageBus.Host.Outbox.PostgreSql.PostgreSqlOutboxAdminMessageSlimMessageBus.Host.Outbox.PostgreSql.Repositories.PostgreSqlOutboxMessageRepository→SlimMessageBus.Host.Outbox.PostgreSql.PostgreSqlOutboxMessage
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses SlimMessageBus.Host.Outbox.PostgreSql, so a change to SlimMessageBus.Host.Outbox.PostgreSql can break SlimMessageBus.Host.Outbox.PostgreSql.Repositories, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Repositories can't break SlimMessageBus.Host.Outbox.PostgreSql.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Repositories uses a module listed above it, which is the healthy direction.
39→10 SlimMessageBus.Host.Outbox.PostgreSql.Services uses SlimMessageBus.Host.Outbox✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Services uses a type in SlimMessageBus.Host.Outbox.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Services.PostgreSqlOutboxMigrationService→SlimMessageBus.Host.Outbox.IOutboxMigrationService
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Services uses SlimMessageBus.Host.Outbox, so a change to SlimMessageBus.Host.Outbox can break SlimMessageBus.Host.Outbox.PostgreSql.Services, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Services can't break SlimMessageBus.Host.Outbox.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Services uses a module listed above it, which is the healthy direction.
39→24 SlimMessageBus.Host.Outbox.PostgreSql.Services uses SlimMessageBus.Host.Outbox.PostgreSql.Configuration✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Services uses a type in SlimMessageBus.Host.Outbox.PostgreSql.Configuration.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Services.PostgreSqlOutboxMigrationService→SlimMessageBus.Host.Outbox.PostgreSql.Configuration.PostgreSqlOutboxSettings
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Services uses SlimMessageBus.Host.Outbox.PostgreSql.Configuration, so a change to SlimMessageBus.Host.Outbox.PostgreSql.Configuration can break SlimMessageBus.Host.Outbox.PostgreSql.Services, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Services can't break SlimMessageBus.Host.Outbox.PostgreSql.Configuration.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Services uses a module listed above it, which is the healthy direction.
39→37 SlimMessageBus.Host.Outbox.PostgreSql.Services uses SlimMessageBus.Host.Outbox.PostgreSql✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.Services uses a type in SlimMessageBus.Host.Outbox.PostgreSql.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.Services.PostgreSqlOutboxMigrationService→SlimMessageBus.Host.Outbox.PostgreSql.IPostgreSqlOutboxTemplateSlimMessageBus.Host.Outbox.PostgreSql.Services.PostgreSqlOutboxMigrationService→SlimMessageBus.Host.Outbox.PostgreSql.IPostgreSqlRepository
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.Services uses SlimMessageBus.Host.Outbox.PostgreSql, so a change to SlimMessageBus.Host.Outbox.PostgreSql can break SlimMessageBus.Host.Outbox.PostgreSql.Services, while a change to SlimMessageBus.Host.Outbox.PostgreSql.Services can't break SlimMessageBus.Host.Outbox.PostgreSql.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.Services uses a module listed above it, which is the healthy direction.
40→6 SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses SlimMessageBus.Host✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses a type in SlimMessageBus.Host.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.DbContext.MessageBusBuilderExtensions→SlimMessageBus.Host.MessageBusBuilder
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses SlimMessageBus.Host, so a change to SlimMessageBus.Host can break SlimMessageBus.Host.Outbox.PostgreSql.DbContext, while a change to SlimMessageBus.Host.Outbox.PostgreSql.DbContext can't break SlimMessageBus.Host.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses a module listed above it, which is the healthy direction.
40→24 SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses SlimMessageBus.Host.Outbox.PostgreSql.Configuration✕
- Connections
- 3 pairs of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses a type in SlimMessageBus.Host.Outbox.PostgreSql.Configuration.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.DbContext.DbContextOutboxRepository→SlimMessageBus.Host.Outbox.PostgreSql.Configuration.PostgreSqlOutboxSettingsSlimMessageBus.Host.Outbox.PostgreSql.DbContext.DbContextTransactionService→SlimMessageBus.Host.Outbox.PostgreSql.Configuration.PostgreSqlSettingsSlimMessageBus.Host.Outbox.PostgreSql.DbContext.MessageBusBuilderExtensions→SlimMessageBus.Host.Outbox.PostgreSql.Configuration.PostgreSqlOutboxSettings
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses SlimMessageBus.Host.Outbox.PostgreSql.Configuration, so a change to SlimMessageBus.Host.Outbox.PostgreSql.Configuration can break SlimMessageBus.Host.Outbox.PostgreSql.DbContext, while a change to SlimMessageBus.Host.Outbox.PostgreSql.DbContext can't break SlimMessageBus.Host.Outbox.PostgreSql.Configuration.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses a module listed above it, which is the healthy direction.
40→35 SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses SlimMessageBus.Host.Outbox.PostgreSql.Transactions✕
- Connections
- 2 pairs of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses a type in SlimMessageBus.Host.Outbox.PostgreSql.Transactions.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.DbContext.DbContextOutboxRepository→SlimMessageBus.Host.Outbox.PostgreSql.Transactions.IPostgreSqlTransactionServiceSlimMessageBus.Host.Outbox.PostgreSql.DbContext.DbContextTransactionService→SlimMessageBus.Host.Outbox.PostgreSql.Transactions.AbstractPostgreSqlTransactionService
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses SlimMessageBus.Host.Outbox.PostgreSql.Transactions, so a change to SlimMessageBus.Host.Outbox.PostgreSql.Transactions can break SlimMessageBus.Host.Outbox.PostgreSql.DbContext, while a change to SlimMessageBus.Host.Outbox.PostgreSql.DbContext can't break SlimMessageBus.Host.Outbox.PostgreSql.Transactions.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses a module listed above it, which is the healthy direction.
40→37 SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses SlimMessageBus.Host.Outbox.PostgreSql✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses a type in SlimMessageBus.Host.Outbox.PostgreSql.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.DbContext.DbContextOutboxRepository→SlimMessageBus.Host.Outbox.PostgreSql.IPostgreSqlOutboxTemplate
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses SlimMessageBus.Host.Outbox.PostgreSql, so a change to SlimMessageBus.Host.Outbox.PostgreSql can break SlimMessageBus.Host.Outbox.PostgreSql.DbContext, while a change to SlimMessageBus.Host.Outbox.PostgreSql.DbContext can't break SlimMessageBus.Host.Outbox.PostgreSql.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses a module listed above it, which is the healthy direction.
40→38 SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses SlimMessageBus.Host.Outbox.PostgreSql.Repositories✕
- Connections
- 1 pair of types, where a type in SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses a type in SlimMessageBus.Host.Outbox.PostgreSql.Repositories.
- The types involved
SlimMessageBus.Host.Outbox.PostgreSql.DbContext.DbContextOutboxRepository→SlimMessageBus.Host.Outbox.PostgreSql.Repositories.PostgreSqlOutboxMessageRepository
- Direction
- SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses SlimMessageBus.Host.Outbox.PostgreSql.Repositories, so a change to SlimMessageBus.Host.Outbox.PostgreSql.Repositories can break SlimMessageBus.Host.Outbox.PostgreSql.DbContext, while a change to SlimMessageBus.Host.Outbox.PostgreSql.DbContext can't break SlimMessageBus.Host.Outbox.PostgreSql.Repositories.
- Position
- Below the diagonal: SlimMessageBus.Host.Outbox.PostgreSql.DbContext uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 43 | High / Critical |
| A02:2025 — Security Misconfiguration | 11 | Medium |
| A07:2025 — Authentication Failures | 4 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
| A01:2025 — Broken Access Control | 1 | Medium |
Roadmap
Top priorities: Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler; 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 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. | +8.1 pts | Medium | Access Controls |
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). | +3.4 pts | Low | REDACTED Scanning |
| Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). | +2.1 pts | Low | Static Analysis (SAST) |
| 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.). | +3.8 pts | Medium | Data Protection |
| Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED (2). | +3.0 pts | Medium | Static Analysis (SAST) |
| Resolve the 3 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (3). | +1.3 pts | Low | Explicit Debt |
| Resolve the 5 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED, OutboxBenchmarkTests.cs, OutboxForwardingPublishInterceptorTests.cs. | +1.3 pts | Low | Explicit Debt |
| Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with RabbitMqChannelManager.cs (4), SqsTopologyCache.cs, MessageProcessor.cs. | +1.3 pts | Low | Explicit Debt |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs | 3.3 | Slop | Explicit Debt: EmptyCatchBlock |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs | 5.0 | Mixed | Explicit Debt: EmptyCatchBlock |
| REDACTED | 5.5 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs | 5.8 | Mixed | Explicit Debt: EmptyCatchBlock |
| src/.editorconfig | 5.8 | Mixed | Explicit Debt: AnalyzerSeverityNone |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs | 6.8 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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 0.8, the weighted average across measured dimensions.
What we checked — 93 dimensions across the health lenses
- 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, 364 of 380 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — 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. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, commit the Cobertura/OpenCover/lcov report your CI already produces and real coverage will be read. You can widen what we reach: optional: commit the Cobertura/OpenCover/lcov report your CI already produces, and the real number is read on the next scan.
- D11 Test Reliability — 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. Test reliability not included — no test tier completed within its budget.
- D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- 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 (21 contributor(s) across 787 commit(s) sampled, automation and bot accounts excluded). One of them holds 93% of the history; the other 20 hold 0.4% 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.
- D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/SlimMessageBus/SlimMessageBus.csproj' with message: The URL of repository remote 'origin' is invalid: ''.
- 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.
- 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 — 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. 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.
- D21 Naming Consistency — 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. 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.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- 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 (27,083 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) — 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. `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/AddConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/SubtractConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/AddRandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/RandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/SubtractRandomHealthCheck.cs`, … (+75 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D39 IL Efficiency — not measured this run — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- 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 DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — d093df972510 Downloading [> ] 48.55kB/3.865MB 74c614fb2c68 Verifying Checksum 74c614fb2c68 Download complete 74c614fb2c68 Extracting [> ] 65.54kB/3.853MB d093df972510 Verifying Checksum d093df972510 Download complete write /var/lib/docker/tmp/GetImageBlob1852963211: no space left on device; the earlier `compose pull` step reported: 51601473dc3c Extracting [============================> ] 72.42MB/126.5MB bbccc42d671a Downloading [==================================================>] 369B/369B dde0fd524f40 Downloading [==================================================>] 490MB/490MB write /var/lib/docker/tmp/GetImageBlob3903648843: no space left on device; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- DM8 Value-object opportunities — 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. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- 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.
- X2 Cancellation propagation — 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. 112 further occurrence(s) are not listed individually; the score already reflects all 152.
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
- 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.
- 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.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- 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 Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MemoryMessageBusBuilder.AutoDeclareFrom at 25. A further 1 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 DefaultGooglePubSubHeaderSerializer.Deserialize at 17 — 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/SlimMessageBus.Host.GooglePubSub/Headers/DefaultGooglePubSubHeaderSerializer.cs (DefaultGooglePubSubHeaderSerializer.Deserialize at 17). 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.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MemoryMessageBusBuilder.AutoDeclareFrom (cyclomatic 25), ServiceBusTopologyService.PrepareSubscription (cyclomatic 21), MessageProcessor.ProcessMessage (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
12 method(s) exceeded the cognitive complexity threshold of 15; the worst was MemoryMessageBusBuilder.AutoDeclareFrom at 53.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with MemoryMessageBusBuilder.AutoDeclareFrom (cognitive 53), ServiceBusTopologyService.PrepareSubscription (cognitive 37), MessageProcessor.ProcessMessage (cognitive 36). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 7.7 to about 8.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with MessageBusBase.cs, RabbitMqChannelManager.cs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
29 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 2 of the 30 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 6 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with MongoDbOutboxMessageRepository.cs (2), MemoryMessageBusBuilder.cs, PostgreSqlMessageBusSettings.cs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with PostgreSqlSequentialGuidGenerator.cs, PostgreSqlHelper.cs, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with PostgreSqlHelper.cs, RabbitMqMessageBus.cs, ServiceScopeExtensions.cs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
177 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 115 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with RuntimeTypeCache.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
839 test methods: 653 unit, 186 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 1 zero-assertion, 2 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 839 tests.
What to do
- Resolve the 5 Mock-dominated test finding(s) in Test Quality — start with HybridMessageSerializerProviderTests.cs (2), MessageHandlerTest.cs, ServiceBusMessageBusSettingsTests.cs. — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 2 Fixed-sleep synchronisation finding(s) in Test Quality — start with AsyncManualResetEventTests.cs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 No assertions finding(s) in Test Quality — start with MessageScopeAccessorTests.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 333 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 63 direct `PackageReference`(s), and 187 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
47 deducted debt markers + unmeasured dead symbols across 27083 LoC in the .NET projects (0.8/KLoC) → score 8.3. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with RabbitMqChannelManager.cs (4), SqsTopologyCache.cs, MessageProcessor.cs. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 5 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED, OutboxBenchmarkTests.cs, OutboxForwardingPublishInterceptorTests.cs. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 3 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (3). — One of this dimension's main actionable groups (3 issue-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
177 projects, 2342 source files, 51246 hand-written lines of code (27083 production / 24163 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 117 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 377 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 48 document(s) read across 37 unit(s).
D21 · Naming Consistency
2 naming inconsistencies among 43 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `WithProviderAmazonSQS` spells `SQS` where 12 names in the project spell… finding(s) in Naming Consistency — start with MessageBusBuilderExtensions.cs. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `WithProviderRabbitMQ` spells `MQ` where 29 names in the project spell… finding(s) in Naming Consistency — start with RabbitMqMessageBusBuilderExtensions.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
33 of 795 judged comments only repeat the code they sit on (4.2 %). 13 comment(s) in another language or script were not judged.
What to do
- Resolve the 29 redundant comment finding(s) in Comment Value — start with ServiceCollectionExtensions.cs (3), ConsumerInstanceMessageProcessorTest.cs (3), RabbitMqChannelManager.cs (2). — One of this dimension's main actionable groups (29 recommendation-level).
D26 · Project Cohesion
0 of 90 projects flagged as possibly oversized/incoherent.
D27 · Navigability
67 % of calls cross a namespace and 11 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What to do
- Improve Navigability — currently 8.9/10. — 67 % of calls cross a namespace and 11 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
43 finding(s): 0 critical, 42 high, 1 medium, 0 low. 22 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 128 file(s) — `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/AddConsumer.cs` (line 3), `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/SubtractConsumer.cs` (line 3), `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/AddRandomHealthCheck.cs` (line 3), `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/RandomHealthCheck.cs` (line 5), `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/SubtractRandomHealthCheck.cs` (line 3), … (+123 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 109 of those file(s) — `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/AddConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/SubtractConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/AddRandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/RandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/SubtractRandomHealthCheck.cs`, … (+104 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 4 of those file(s) — `src/SlimMessageBus.Host.Memory/Consumers/ConcurrentMessageProcessorQueue.cs`, `src/Tests/SlimMessageBus.Host.Outbox.Sql.Test/CommonSqlMigrationLockTests.cs`, `src/Tests/SlimMessageBus.Host.Outbox.Sql.Test/SqlConnectionRecoveryTests.cs`, `src/Tests/SlimMessageBus.Host.Test/Consumer/AbstractConsumerTests.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (7 issue-level).
- No action in Static Analysis (SAST) — all 22 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (22 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
11 finding(s): 0 critical, 0 high, 11 medium, 0 low.
What to do
- Resolve the 11 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
D32 · Data Compliance (PII/GDPR)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 80 file(s) — `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/AddConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/Consumers/SubtractConsumer.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/AddRandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/RandomHealthCheck.cs`, `src/Samples/Sample.CircuitBreaker.HealthCheck/HealthChecks/SubtractRandomHealthCheck.cs`, … (+75 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
What to do
- Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
11 of 138 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/SlimMessageBus.Host.Outbox.PostgreSql/Repositories/PostgreSqlOutboxMessageRepository.cs. Counted over 138 of the 565 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 27 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.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
- `PendingRequestManager` is registered as a SINGLETON but its constructor takes `IPendingRequestStore store`, which is registered as Transient. The singleton captures one instance of the transient dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IPendingRequestStore` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/SlimMessageBus.Host/RequestResponse/PendingRequestManager.cs:19
- `OutboxSendingTask` is registered as a SINGLETON but its constructor takes `OutboxSettings outboxSettings`, which is registered as Transient. The singleton captures one instance of the transient dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `OutboxSettings` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:5
- `OutboxCleanUpTask` is registered as a SINGLETON but its constructor takes `OutboxSettings outboxSettings`, which is registered as Transient. The singleton captures one instance of the transient dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `OutboxSettings` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/SlimMessageBus.Host.Outbox/Services/OutboxCleanUpTask.cs:20
What to do
- Don't inject scoped/transient services into singletons; resolve them per-use via IServiceScopeFactory or a factory delegate, or align the lifetimes.
AX10 · Code composition
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 singletons
- `HybridMessageSerializerProvider` is a singleton (one shared instance) but mutates instance state outside any lock (DefaultSerializer, _serializerProviderByType; e.g. `DefaultSerializer` at line 34). — src/SlimMessageBus.Host.Serialization.Hybrid/HybridMessageSerializerProvider.cs:10
- `OutboxSendingTask` is a singleton (one shared instance) but mutates instance state outside any lock (_loopCts, _loopTask, _startBusTask, _stopBusTask; e.g. `_loopCts` at line 51). — src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:3
- `HealthCheckBackgroundService` is a singleton (one shared instance) but mutates instance state outside any lock (_onChangeDelegates; e.g. `_onChangeDelegates` at line 52). — src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs:3
- `MessageBus` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_provider; e.g. `_provider` at line 14). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/SlimMessageBus/MessageBus.cs:6
- `Secrets` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_store, Service; e.g. `_store` at line 10). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Tools/SecretStore/Secrets.cs:3
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces SlimMessageBus.Host ↔ SlimMessageBus.Host.Collections depend on each other. The lightest dependency in the cycle is SlimMessageBus.Host.Collections → SlimMessageBus.Host (SlimMessageBus.Host.Collections.KindMapping → SlimMessageBus.Host.MessageBusSettings, 4 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/SlimMessageBus.Host/Collections/KindMapping.cs:3
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
- No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
- `WeatherForecastController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:22
- `OrdersController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:16
- `ValuesController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:9, src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs:10, src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs:17
- `ImageController.GetImageThumbnail` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:25
- `ImageController.GetImage` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:53
- `MapGet("/publish-message")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.Nats.WebApi/Program.cs:59
- `MapGet("/publish-message-queue")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.Nats.WebApi/Program.cs:65
- `MapPost("/customer")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/Samples/Sample.OutboxWebApi/Program.cs:183, src/Samples/Sample.ValidatingWebApi/Program.cs:67
- `MapPost("/customer/search")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Samples/Sample.ValidatingWebApi/Program.cs:71
- `KafkaGroupConsumer.Commit` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×4) — src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275, src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275, src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275, …
What to do
- Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `Customer`'s public constructor takes `firstname`, `lastname` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Customer` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:20
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
- `Customer` reads `DateTime.UtcNow` inside `ChangeEmail` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:33
What to do
- Route the listed sites through the clock abstraction this repo already declares, so the domain's rules can be exercised at a chosen instant.
DM4 · Rich vs anemic model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
- `OrdersController` (domain layer) names `RouteAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:7
- `OrdersController` (domain layer) names `ApiControllerAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:8
- `OrdersController` (domain layer) names `Controller` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:9
- `OrdersController` (domain layer) names `HttpPostAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:15
- `OrdersController` (domain layer) names `IActionResult` from `Microsoft.AspNetCore.Mvc` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:16
- `ValuesController` (domain layer) names `RouteAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:3
- `ValuesController` (domain layer) names `ApiControllerAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:4
- `ValuesController` (domain layer) names `Controller` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:5
- `ValuesController` (domain layer) names `HttpGetAttribute` from `Microsoft.AspNetCore.Mvc` — a HTTP type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:8
- `ValuesController` (domain layer) names `IActionResult` from `Microsoft.AspNetCore.Mvc` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:9
- `Startup` (domain layer) names `IApplicationBuilder` from `Microsoft.AspNetCore.Builder` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Samples/Sample.DomainEvents.WebApi/Startup.cs:49
- `Program` (domain layer) uses `ASP.NET` inside a method body — infrastructure reached without it appearing in any signature. — src/Samples/Sample.DomainEvents.WebApi/Program.cs:6
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM7 · Repository granularity
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED4 · Outbox / dual-write
- `CreateCustomerCommandHandler.OnHandle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Samples/Sample.OutboxWebApi/Application/CreateCustomerCommandHandler.cs:8
- `NatsMessageBus.ProduceToTransport` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/SlimMessageBus.Host.Nats/NatsMessageBus.cs:102
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
ED5 · Idempotency
- `Application.CreateCustomerCommandHandler.OnHandle` mutates persistent state (a database save) and inserts a new `Customer` with a fresh id (`Guid.NewGuid()`) (line 13), so a re-run inserts another one. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Samples/Sample.OutboxWebApi/Application/CreateCustomerCommandHandler.cs:8
What to do
- Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/Samples/Sample.AsyncApi.Service/Messages/CustomerCreatedEventConsumer.cs:11, src/Samples/Sample.AsyncApi.Service/Messages/CustomerEventConsumer.cs:14
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `CloseAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:31
- `ProcessErrorAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:59
- `ProcessErrorAsyncInternal` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/SlimMessageBus.Host.AzureServiceBus/Consumer/AsbBaseConsumer.cs:231
- `CreateConsumers` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/SlimMessageBus.Host.Mqtt/MqttMessageBus.cs:41
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Add a README to the 32 of 53 project(s) that lack one — worth up to 1.2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- Only 35/46 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 46, 11 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 OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- `REDACTED` 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`. — REDACTED:12
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
- No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
P6 · Release Hygiene
P8 · Schema migrations
- This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema. — src/Samples/Sample.OutboxWebApi/Program.cs:160
- This repository evolves its schema with versioned migrations, but a CREATE TABLE statement here creates schema at runtime outside them — structure no migration created and the migration history does not describe, so a later migration that touches it fails on a fresh environment and the environments drift apart. Create it in a migration instead. (×3) — REDACTED:56, src/SlimMessageBus.Host.PostgreSql/PostgreSqlTopologyService.cs:65, src/SlimMessageBus.Host.Outbox.PostgreSql/Services/PostgreSqlOutboxMigrationService.cs:99
What to do
- Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
- 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) — src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:92, src/SlimMessageBus.Host/MessageBusBase.cs:290, src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:458
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×6) — src/Samples/Sample.AsyncApi.Service/Program.cs:19, src/Samples/Sample.DomainEvents.WebApi/Program.cs:9, src/Samples/Sample.Images.WebApi/Program.cs:9, …
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
- 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. (×3) — src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:172, src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:198, src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:218
- 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. (×3) — src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:92, src/SlimMessageBus.Host/MessageBusBase.cs:290, src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:458
- `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs:37
What to do
- Sync-over-async (deadlock risk) through `.Result`
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `AbstractConsumer` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 6), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 166), `DisposeAsyncCore` (line 172) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:6
- `MessageBusBase` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_cancellationTokenSource` itself (line 24), which makes that instance its own. But `_cancellationTokenSource` is named in none of the methods the disposal search covered: `Dispose` (line 280), `Dispose` (line 286), `DisposeAsync` (line 294), `Dispose` (line 280), `Dispose` (line 286), `DisposeAsyncInternal` (line 300) — 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` (`_cancellationTokenSource?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/SlimMessageBus.Host/MessageBusBase.cs:24
- `providers` is a `LoggerProviderCollection`, which implements `IDisposable`, and it is created here (line 30). Every use of it in `BaseIntegrationTest` 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 providers = …;`), which releases it at the end of the scope on every path including a throw. — src/Tests/SlimMessageBus.Host.Test.Common/IntegrationTest/BaseIntegrationTest.cs:30
- `OutboxSendingTask` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_loopCts` itself (line 15), which makes that instance its own. But `_loopCts` is named in none of the methods the disposal search covered: `DisposeAsync` (line 25), `DisposeAsyncCore` (line 43) — 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` (`_loopCts?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:15
- `Settings.ServiceProvider.CreateScope()` (line 18) creates an `IServiceScope`, and it is bound to the local `scope`, which this method only reads through and never disposes. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`. (×2) — src/SlimMessageBus.Host.Sql/SqlMessageBus.cs:18, src/SlimMessageBus.Host.PostgreSql/PostgreSqlMessageBus.cs:18
- `HealthCheckBackgroundService` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 8), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `Dispose` (line 118) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs:8
- `AbstractTemporaryCredentialsSqsClientProvider` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphoreSlim` itself (line 22), which makes that instance its own. But `_semaphoreSlim` is named in none of the methods the disposal search covered: `Dispose` (line 85), `Dispose` (line 99), `Dispose` (line 85), `Dispose` (line 99) — 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` (`_semaphoreSlim?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/SlimMessageBus.Host.AmazonSQS/ClientFactory/AbstractTemporaryCredentialsSqsClientProvider.cs:22
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 state
X2 · Cancellation propagation
- Only 131/275 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. (×28) — src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:52, src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:65, src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:71, …
- 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. (×10) — src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:216, src/SlimMessageBus.Host/Producer/InterceptorPipelines/PublishInterceptorPipeline.cs:19, src/SlimMessageBus.Host/Producer/InterceptorPipelines/SendInterceptorPipeline.cs:21, …
- No CancellationToken parameter, and the token `args.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `args.CancellationToken` on, or take a CancellationToken. — src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:70
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
- The guard on line 19 rejects `queueName` and line 19 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(queueName)` is true of a value that is NOT null: it is satisfied by an EMPTY `queueName`, and on that path `queueName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:19
- The guard on line 58 rejects `exchangeName` and line 58 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:58
- The guard on line 81 rejects `exchangeName` and line 81 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:81
- The guard on line 34 rejects `exchangeName` and line 34 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqProducerBuilderExtensions.cs:34
- The guard on line 18 rejects `exchangeName` and line 18 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(exchangeName)` is true of a value that is NOT null: it is satisfied by an EMPTY `exchangeName`, and on that path `exchangeName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqRequestResponseBuilderExtensions.cs:18
What to do
- Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:169, src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:385, src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:395, …
- `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs:191
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- 14/53 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
- ~0.9 `!` suppressions per 1k syntax nodes — 21 suppression(s) across the 23117 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 63% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 79% | Strong | Solid. |
| Maturity | 70% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 43% | Weak — gated by D29, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 70% | Adequate — gated by DM6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 88% | Strong | Strongest area. |
| Performance | 77% | Strong | Solid. |
Unscored — 4 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 35 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — d093df972510 Downloading [> ] 48.55kB/3.865MB 74c614fb2c68 Verifying Checksum 74c614fb2c68 Download complete 74c614fb2c68 Extracting [> ] 65.54kB/3.853MB d093df972510 Verifying Checksum d093df972510 Download complete write /var/lib/docker/tmp/GetImageBlob1852963211: no space left on device; the earlier `compose pull` step reported: 51601473dc3c Extracting [============================> ] 72.42MB/126.5MB bbccc42d671a Downloading [==================================================>] 369B/369B dde0fd524f40 Downloading [==================================================>] 490MB/490MB write /var/lib/docker/tmp/GetImageBlob3903648843: no space left on device; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D11 Test Reliability — Test reliability not included
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D25 ADR Conformance — no ADRs to check
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — analyzer environment
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED3 Event naming — no domain or integration events detected — event-naming check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- 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)
Critical — 80 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:7
- Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:8
- Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:9
- Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:15
- Domain depends on infrastructure: OrdersController src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:16
- Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:3
- Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:4
- Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:5
- Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:8
- Domain depends on infrastructure: ValuesController src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:9
- Domain depends on infrastructure: Startup src/Samples/Sample.DomainEvents.WebApi/Startup.cs:49
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- EmptyCatchBlock src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs:123
- EmptyCatchBlock src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:385
- EmptyCatchBlock src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:395
- EmptyCatchBlock src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:414
- EmptyCatchBlock src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:424
- EmptyCatchBlock src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:169
- WriteOnlyPrivateField REDACTED:14
- WriteOnlyPrivateField src/Tests/SlimMessageBus.Host.Outbox.PostgreSql.DbContext.Test/OutboxBenchmarkTests.cs:22
- WriteOnlyPrivateField src/Tests/SlimMessageBus.Host.Outbox.Test/Interceptors/OutboxForwardingPublishInterceptorTests.cs:44
- WriteOnlyPrivateField src/Tests/SlimMessageBus.Host.RabbitMQ.Test/Config/RabbitMqProducerBuilderExtensionsTests.cs:5
- WriteOnlyPrivateField src/Tests/SlimMessageBus.Host.Test/Consumer/MessageProcessorTest.cs:11
- Captive dependency: singleton PendingRequestManager captures transient IPendingRequestStore src/SlimMessageBus.Host/RequestResponse/PendingRequestManager.cs:19
- Captive dependency: singleton OutboxSendingTask captures transient OutboxSettings src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:5
- Captive dependency: singleton OutboxCleanUpTask captures transient OutboxSettings src/SlimMessageBus.Host.Outbox/Services/OutboxCleanUpTask.cs:20
- AnalyzerSeverityNone src/.editorconfig:188
- AnalyzerSeverityNone src/.editorconfig:190
- AnalyzerSeverityNone src/.editorconfig:191
- REDACTED
- REDACTED
- NoWarnInCsproj REDACTED:8
- NoWarnInCsproj src/Samples/Sample.DomainEvents.WebApi/Sample.DomainEvents.WebApi.csproj:8
- REDACTED
- REDACTED
- Dual write (no outbox): CreateCustomerCommandHandler.OnHandle src/Samples/Sample.OutboxWebApi/Application/CreateCustomerCommandHandler.cs:8
- Dual write (no outbox): NatsMessageBus.ProduceToTransport src/SlimMessageBus.Host.Nats/NatsMessageBus.cs:102
- Namespace dependency cycle src/SlimMessageBus.Host/Collections/KindMapping.cs:3
- REDACTED
- REDACTED
- REDACTED
- Domain uses infrastructure in a method body: Program src/Samples/Sample.DomainEvents.WebApi/Program.cs:6
Serious — 194 finding(s)
- Async method without CancellationToken: DoStart src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:52
- Async method without CancellationToken: InternalOnStart src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:65
- Async method without CancellationToken: InternalOnStop src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:71
- Async method without CancellationToken: DoStop src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:81
- Async method without CancellationToken: Start src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:94
- Async method without CancellationToken: Stop src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:125
- Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:172
- Async method without CancellationToken: OnBusLifecycle src/SlimMessageBus.Host/MessageBusBase.cs:150
- Async method without CancellationToken: Start src/SlimMessageBus.Host/MessageBusBase.cs:182
- Async method without CancellationToken: Stop src/SlimMessageBus.Host/MessageBusBase.cs:220
- Async method without CancellationToken: DisposeAsyncInternal src/SlimMessageBus.Host/MessageBusBase.cs:300
- Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host/MessageBusBase.cs:321
- Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:47
- Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Kafka/KafkaMessageBus.cs:125
- Async method without CancellationToken: OnStart src/SlimMessageBus.Host.AzureEventHub/Consumer/EhGroupConsumer.cs:49
- Async method without CancellationToken: OnStop src/SlimMessageBus.Host.AzureEventHub/Consumer/EhGroupConsumer.cs:58
- Async method without CancellationToken: Checkpoint src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:70
- Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.AzureEventHub/EventHubMessageBus.cs:80
- Async method without CancellationToken: OnStart src/SlimMessageBus.Host.AzureEventHub/EventHubMessageBus.cs:96
- Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.Memory/MemoryMessageBus.cs:26
- Async method without CancellationToken: AddLoop src/REDACTED:281
- Async method without CancellationToken: MultiplyLoop src/REDACTED:302
- Async method without CancellationToken: Submit src/Samples/Sample.DomainEvents.Domain/Order.cs:37
- Async method without CancellationToken: Post src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:16
- Async method without CancellationToken: DisposeAsyncCore src/SlimMessageBus.Host.AzureServiceBus/Consumer/AsbBaseConsumer.cs:90
- No authorization
- No authorization REDACTED:22
- No authorization src/Samples/Sample.DomainEvents.WebApi/Controllers/OrdersController.cs:16
- No authorization src/Samples/Sample.DomainEvents.WebApi/Controllers/ValuesController.cs:9
- No authorization src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:25
- No authorization src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:53
- No authorization src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs:10
- No authorization src/Samples/Sample.Images.WebApi/Controllers/ValuesController.cs:17
- No authorization src/Samples/Sample.Nats.WebApi/Program.cs:59
- No authorization src/Samples/Sample.Nats.WebApi/Program.cs:65
- No authorization src/Samples/Sample.OutboxWebApi/Program.cs:183
- No authorization src/Samples/Sample.ValidatingWebApi/Program.cs:67
- No authorization src/Samples/Sample.ValidatingWebApi/Program.cs:71
- No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275
- No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275
- No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275
- No authorization src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:275
- TodoComment src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:65
- TodoComment src/Samples/Sample.Images.WebApi/Controllers/ImageController.cs:67
- TodoComment src/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs:142
- TodoComment src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs:125
- TodoComment src/SlimMessageBus.Host.AsyncApi/MessageBusDocumentGenerator.cs:38
- TodoComment src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:50
- TodoComment src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:61
- TodoComment src/SlimMessageBus.Host.Kafka/Consumer/KafkaGroupConsumer.cs:78
- TodoComment src/SlimMessageBus.Host.Kafka/Consumer/KafkaPartitionConsumer.cs:40
- TodoComment src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs:195
- TodoComment src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs:201
- TodoComment src/SlimMessageBus.Host.RabbitMQ/RabbitMqTopologyService.cs:51
- TodoComment src/SlimMessageBus.Host.Serialization.Avro/AvroMessageSerializer.cs:126
- TodoComment src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:93
- TodoComment src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:61
- TodoComment src/SlimMessageBus.Host/MessageWithHeaders.cs:5
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- BareSuppressMessage src/Samples/Sample.Images.Worker/GlobalSuppressions.cs:8
- BareSuppressMessage src/SlimMessageBus.Host.Redis/GlobalSuppressions.cs:9
- BareSuppressMessage src/SlimMessageBus.Host/GlobalSuppressions.cs:12
- BareSuppressMessage src/SlimMessageBus.Host/GlobalSuppressions.cs:13
- BareSuppressMessage src/SlimMessageBus.Host.Redis/GlobalSuppressions.cs:8
- BareSuppressMessage src/Tests/SlimMessageBus.Host.Memory.Test/GlobalSuppressions.cs:8
- Duplicated block (6 lines × 2) src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:85
- Duplicated block (6 lines × 2) src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:162
- Duplicated block (6 lines × 2) src/SlimMessageBus.Host.PostgreSql/Configuration/PostgreSqlMessageBusSettings.cs:11
- Duplicated block (6 lines × 2) src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:13
- Duplicated block (6 lines × 2) src/SlimMessageBus.Host.Outbox.PostgreSql/Repositories/PostgreSqlOutboxMessageRepository.cs:148
- Duplicated block (6 lines × 2) src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:105
- Swallowed exception (empty catch) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:169
- Swallowed exception (empty catch) src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:385
- Swallowed exception (empty catch) src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:395
- Swallowed exception (empty catch) src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:414
- Swallowed exception (empty catch) src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:424
- Swallowed exception (empty catch) src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyCache.cs:123
- Owned disposable field is never released src/SlimMessageBus.Host/Consumer/AbstractConsumer.cs:6
- Owned disposable field is never released src/SlimMessageBus.Host/MessageBusBase.cs:24
- Owned disposable field is never released src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:15
- Owned disposable field is never released src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs:8
- Owned disposable field is never released src/SlimMessageBus.Host.AmazonSQS/ClientFactory/AbstractTemporaryCredentialsSqsClientProvider.cs:22
- Argument guard throws the exception its own condition disproves src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:19
- Argument guard throws the exception its own condition disproves src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:58
- Argument guard throws the exception its own condition disproves src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqConsumerBuilderExtensions.cs:81
- Argument guard throws the exception its own condition disproves src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqProducerBuilderExtensions.cs:34
- Argument guard throws the exception its own condition disproves src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqRequestResponseBuilderExtensions.cs:18
- CommentedOutCode src/Samples/Sample.Serialization.ConsoleApp/Program.cs:78
- CommentedOutCode src/Tests/SlimMessageBus.Host.Memory.Benchmark/Program.cs:13
- CommentedOutCode src/Samples/Sample.Serialization.ConsoleApp/Program.cs:87
- CommentedOutCode src/Tests/SlimMessageBus.Host.Memory.Benchmark/Program.cs:17
- Sync-over-async blocking
- Sync-over-async blocking src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:92
- Sync-over-async blocking src/SlimMessageBus.Host/MessageBusBase.cs:290
- Sync-over-async blocking src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:458
- Stateful singleton: HybridMessageSerializerProvider src/SlimMessageBus.Host.Serialization.Hybrid/HybridMessageSerializerProvider.cs:10
- Stateful singleton: OutboxSendingTask src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:3
- Stateful singleton: HealthCheckBackgroundService src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs:3
- CoverageExclusion src/SlimMessageBus.Host.Kafka/Configs/KafkaAbstractConsumerBuilderExtensions.cs:14
- CoverageExclusion src/SlimMessageBus.Host.Kafka/Configs/KafkaAbstractConsumerBuilderExtensions.cs:26
- CoverageExclusion src/SlimMessageBus.Host/PlatformExtensions.cs:11
- Duplicated block (11 lines × 2) src/SlimMessageBus.Host.PostgreSql/PostgreSqlSequentialGuidGenerator.cs:7
- Duplicated block (11 lines × 2) src/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.cs:56
- Duplicated block (11 lines × 2) src/Samples/Sample.OutboxWebApi/Program.cs:93
- Duplicated block (9 lines × 2) src/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.cs:22
- Duplicated block (9 lines × 2) src/SlimMessageBus.Host.RabbitMQ/RabbitMqMessageBus.cs:89
- Duplicated block (9 lines × 2) src/SlimMessageBus.Host.PostgreSql/ServiceScopeExtensions.cs:7
- Hollow method — returns a constant without doing the work src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:31
- Hollow method — returns a constant without doing the work src/SlimMessageBus.Host.AzureEventHub/Consumer/EhPartitionConsumer.cs:59
- Hollow method — returns a constant without doing the work src/SlimMessageBus.Host.AzureServiceBus/Consumer/AsbBaseConsumer.cs:231
- Schema created by a CREATE TABLE statement outside the migrations REDACTED:56
- Schema created by a CREATE TABLE statement outside the migrations src/SlimMessageBus.Host.PostgreSql/PostgreSqlTopologyService.cs:65
- Schema created by a CREATE TABLE statement outside the migrations src/SlimMessageBus.Host.Outbox.PostgreSql/Services/PostgreSqlOutboxMigrationService.cs:99
- Sync-over-async (deadlock risk) through `.Result` src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:172
- Sync-over-async (deadlock risk) through `.Result` src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:198
- Sync-over-async (deadlock risk) through `.Result` src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:218
- Sync-over-async (deadlock risk) src/SlimMessageBus.Host/Hybrid/HybridMessageBus.cs:92
- Sync-over-async (deadlock risk) src/SlimMessageBus.Host/MessageBusBase.cs:290
- Sync-over-async (deadlock risk) src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:458
- Process-global static state: MessageBus src/SlimMessageBus/MessageBus.cs:6
- Process-global static state: Secrets src/Tools/SecretStore/Secrets.cs:3
- Fixed-sleep synchronisation: Wait_ShouldBlockUntilSet src/Tests/SlimMessageBus.Host.Outbox.Test/AsyncManualResetEventTests.cs:58
- Fixed-sleep synchronisation: Wait_ShouldCancel src/Tests/SlimMessageBus.Host.Outbox.Test/AsyncManualResetEventTests.cs:95
- BarePragmaDisable src/SlimMessageBus.Host.Outbox.Sql/SqlOutboxMigrationService.cs:16
- BarePragmaDisable src/Tests/SlimMessageBus.Host.Outbox.MongoDb.Test/MongoDbOutboxRepositoryTests.cs:69
- TooManyMethods: MessageBusBase src/SlimMessageBus.Host/MessageBusBase.cs
- TooManyMethods: RabbitMqChannelManager src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs
- Duplicated block (8 lines × 2) src/SlimMessageBus.Host.AmazonSQS/Services/SqsTopologyService.cs:286
- Duplicated block (8 lines × 2) src/SlimMessageBus.Host.PostgreSql/ObjectToInferredTypesConverter.cs:9
- Duplicated block (7 lines × 2) src/SlimMessageBus.Host.Outbox.MongoDb/Repositories/MongoDbOutboxMessageRepository.cs:115
- Duplicated block (7 lines × 2) src/Samples/Sample.DomainEvents.WebApi/Program.cs:9
- Unfinished stub — throws NotImplementedException src/Samples/Sample.AsyncApi.Service/Messages/CustomerCreatedEventConsumer.cs:11
- Unfinished stub — throws NotImplementedException src/Samples/Sample.AsyncApi.Service/Messages/CustomerEventConsumer.cs:14
- DI scope created and never disposed src/SlimMessageBus.Host.Sql/SqlMessageBus.cs:18
- DI scope created and never disposed src/SlimMessageBus.Host.PostgreSql/PostgreSqlMessageBus.cs:18
- No data-protection/encryption
- MemoryMessageBusBuilder.AutoDeclareFrom (cyclomatic 25) src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:41
- ServiceBusTopologyService.PrepareSubscription (cyclomatic 21) src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs:153
- MessageProcessor.ProcessMessage (cyclomatic 18) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:82
- MessageHandler.DoHandle (cyclomatic 17) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:57
- No assertions: Given_MemoryConsumer_When_MessageScopeAccessorCalledInsideConsumer_Then_LooksUpInTheMessageScope src/Tests/SlimMessageBus.Host.Integration.Test/MessageScopeAccessor/MessageScopeAccessorTests.cs:30
- MemoryMessageBusBuilder.AutoDeclareFrom (cognitive 53) src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:41
- ServiceBusTopologyService.PrepareSubscription (cognitive 37) src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs:153
- MessageProcessor.ProcessMessage (cognitive 36) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:82
- RedisListCheckerConsumer.Run (cognitive 30) src/SlimMessageBus.Host.Redis/Consumers/RedisListCheckerConsumer.cs:57
- MessageHandler.DoHandle (cognitive 25) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageHandler.cs:57
- KafkaMessageBus.ProduceToTransport (cognitive 24) src/SlimMessageBus.Host.Kafka/KafkaMessageBus.cs:138
- OutboxSendingTask.ProcessMessages (cognitive 24) src/SlimMessageBus.Host.Outbox/Services/OutboxSendingTask.cs:265
- ServiceBusTopologyService.DoProvisionTopology (cognitive 20) src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs:248
- MessageProcessor.TryMatchConsumerInvoker (cognitive 17) src/SlimMessageBus.Host/Consumer/MessageProcessors/MessageProcessor.cs:214
- Retry.WithDelay (cognitive 17) src/SlimMessageBus.Host/Helpers/Retry.cs:7
- AsbBaseConsumer.AsbBaseConsumer.ctor (cognitive 17) src/SlimMessageBus.Host.AzureServiceBus/Consumer/AsbBaseConsumer.cs:14
- SqsBaseConsumer.Run (cognitive 16) src/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs:119
- REDACTED
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:9
- Duplicated block (22 lines × 2) src/SlimMessageBus.Host.Outbox.PostgreSql/Interceptors/PostgreSqlTransactionConsumerInterceptor.cs:14
- Duplicated block (16 lines × 2) src/SlimMessageBus.Host/Collections/GenericTypeCache.cs:77
- Duplicated block (13 lines × 2) src/SlimMessageBus.Host.FluentValidation/FluentValidationMessageBusBuilder.cs:57
- Duplicated block (12 lines × 2) src/SlimMessageBus.Host.RabbitMQ/RabbitMqMessageBusSettingsValidationService.cs:45
- Duplicated block (8–10 lines × 2) src/SlimMessageBus.Host.Outbox.MongoDb/Configuration/MessageBusBuilderExtensions.cs:44
- Duplicated block (7 lines × 3) src/SlimMessageBus.Host.Outbox.PostgreSql/ObjectToInferredTypesConverter.cs:9
- Duplicated block (6 lines × 3) src/SlimMessageBus.Host.Outbox.Sql/ObjectToInferredTypesConverter.cs:16
- Duplicated block (5 lines × 2) src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs:25
- Duplicated block (17 lines × 2) src/SlimMessageBus.Host.Nats/Config/NatsConsumerBuilderExtensions.cs:6
- Duplicated block (27 lines × 2) src/SlimMessageBus.Host.Nats/Config/NatsProducerBuilderExtensions.cs:15
- Duplicated block (19 lines × 2) src/SlimMessageBus.Host.Nats/Config/NatsRequestResponseBuilderExtensions.cs:6
- Duplicated block (58 lines × 2) src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs:18
- Duplicated block (10 lines × 2) src/SlimMessageBus.Host.PostgreSql/Config/PostgreSqlConsumerBuilderExtensions.cs:8
- Low cohesion: RuntimeTypeCache (LCOM4 4) src/SlimMessageBus.Host/Collections/RuntimeTypeCache.cs:3
- Constructible in an invalid state: Customer src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:20
- Domain type reads the wall clock: Customer src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:33
- Non-idempotent mutation: Application.CreateCustomerCommandHandler.OnHandle src/Samples/Sample.OutboxWebApi/Application/CreateCustomerCommandHandler.cs:8
- Fake-async — async method never awaits src/SlimMessageBus.Host.Mqtt/MqttMessageBus.cs:41
- Coverage collected but not gated
- Schema created with EnsureCreated() outside the migrations src/Samples/Sample.OutboxWebApi/Program.cs:160
- NuGet dependencies are not locked
- async void method: OnChannelRecovered src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs:37
- Disposable created and abandoned in the method that made it src/Tests/SlimMessageBus.Host.Test.Common/IntegrationTest/BaseIntegrationTest.cs:30
- Swallowed exception (caught, then discarded) src/SlimMessageBus.Host.AmazonSQS/Consumer/SqsBaseConsumer.cs:191
Minor — 76 finding(s)
- redundant comment src/SlimMessageBus.Host.AmazonSQS/SqsMessageBus.cs:107
- redundant comment src/SlimMessageBus.Host.RabbitMQ/Consumers/AbstractRabbitMqConsumer.cs:43
- redundant comment src/SlimMessageBus.Host.RabbitMQ/Consumers/RabbitMqConsumer.cs:67
- redundant comment src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:141
- redundant comment src/SlimMessageBus.Host.RabbitMQ/RabbitMqChannelManager.cs:272
- redundant comment src/SlimMessageBus.Host.RabbitMQ/RabbitMqMessageBus.cs:188
- redundant comment src/SlimMessageBus.Host/Collections/ProducerByMessageTypeCache.cs:44
- redundant comment src/SlimMessageBus.Host/Consumer/Checkpointing/CheckpointTriggerFactory.cs:23
- redundant comment src/SlimMessageBus.Host/DependencyResolver/ServiceCollectionExtensions.cs:46
- redundant comment src/SlimMessageBus.Host/DependencyResolver/ServiceCollectionExtensions.cs:57
- redundant comment src/SlimMessageBus.Host/DependencyResolver/ServiceCollectionExtensions.cs:72
- redundant comment src/SlimMessageBus.Host/Helpers/ReflectionUtils.cs:173
- redundant comment src/Tests/SlimMessageBus.Host.AzureServiceBus.Test/ServiceBusMessageBusIt.cs:59
- redundant comment src/Tests/SlimMessageBus.Host.Integration.Test/HybridTests.cs:105
- redundant comment src/Tests/SlimMessageBus.Host.Memory.Test/MemoryMessageBusTests.cs:293
- redundant comment src/Tests/SlimMessageBus.Host.Mqtt.Test/MqttMessageBusIt.cs:178
- redundant comment src/Tests/SlimMessageBus.Host.Nats.Test/NatsMessageBusIt.cs:266
- redundant comment src/Tests/SlimMessageBus.Host.RabbitMQ.Test/Consumers/AbstractRabbitMqConsumerTests.cs:483
- redundant comment src/Tests/SlimMessageBus.Host.RabbitMQ.Test/IntegrationTests/RabbitMqDefaultExchangeIt.cs:85
- redundant comment src/Tests/SlimMessageBus.Host.RabbitMQ.Test/IntegrationTests/RabbitMqMessageBusIt.cs:69
- redundant comment src/Tests/SlimMessageBus.Host.RabbitMQ.Test/IntegrationTests/RabbitMqMessageBusIt.cs:452
- redundant comment src/Tests/SlimMessageBus.Host.RabbitMQ.Test/RabbitMqChannelManagerTests.cs:295
- redundant comment src/Tests/SlimMessageBus.Host.Test/Consumer/ConsumerInstanceMessageProcessorTest.cs:137
- redundant comment src/Tests/SlimMessageBus.Host.Test/Consumer/ConsumerInstanceMessageProcessorTest.cs:294
- redundant comment src/Tests/SlimMessageBus.Host.Test/Consumer/ConsumerInstanceMessageProcessorTest.cs:343
- Orphaned file src/SlimMessageBus.Host.Outbox.PostgreSql/Repositories/PostgreSqlOutboxMessageRepository.cs:1
- Orphaned file src/SlimMessageBus.Host.Outbox.PostgreSql/Services/PostgreSqlOutboxMigrationService.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/SlimMessageBus.Host.Serialization.Hybrid/SerializationBuilderExtensions.cs:1
- Orphaned file src/SlimMessageBus.Host.Outbox/Services/OutboxCleanUpTask.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckBackgroundService.cs:1
- Orphaned file src/SlimMessageBus.Host.Outbox.PostgreSql/PostgreSqlHelper.cs:1
- Orphaned file src/SlimMessageBus.Host.Outbox.PostgreSql/Configuration/MessageBusBuilderExtensions.cs:1
- Orphaned file src/SlimMessageBus.Host.CircuitBreaker.HealthCheck/HealthCheckCircuitBreaker.cs:1
- Orphaned file src/SlimMessageBus.Host.Outbox.PostgreSql/Configuration/BuilderExtensions.cs:1
- Duplicated predicate src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs:63
- Duplicated predicate src/SlimMessageBus.Host.Outbox/AbstractOutboxTransactionService.cs:25
- Duplicated predicate src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs:29
- Duplicated predicate src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs:28
- Duplicated predicate src/SlimMessageBus.Host.Kafka/KafkaMessageBus.cs:237
- Duplicated predicate src/SlimMessageBus.Host/Collections/GenericTypeCache.cs:86
- Duplicated predicate src/SlimMessageBus.Host/Collections/GenericTypeCache.cs:85
- Duplicated predicate src/SlimMessageBus.Host.Sql.Common/SqlHelper.cs:28
- Duplicated predicate src/SlimMessageBus.Host.AmazonSQS/Headers/DefaultSnsHeaderSerializer.cs:13
- No security response headers detected
- No security response headers detected src/Samples/Sample.AsyncApi.Service/Program.cs:19
- No security response headers detected src/Samples/Sample.DomainEvents.WebApi/Program.cs:9
- No security response headers detected src/Samples/Sample.Images.WebApi/Program.cs:9
- No security response headers detected src/Samples/Sample.Nats.WebApi/Program.cs:13
- No security response headers detected src/Samples/Sample.OutboxWebApi/Program.cs:23
- No security response headers detected src/Samples/Sample.ValidatingWebApi/Program.cs:16
- Mock-dominated test: When_ExecuteConsumer_Given_ConsumerWithContext_Then_ConsumerContextSet src/Tests/SlimMessageBus.Host.Test/Consumer/MessageHandlerTest.cs:68
- Mock-dominated test: When_WithModifier_Given_SeveralModifiers_Then_ExecutesThemAll src/Tests/SlimMessageBus.Host.AzureServiceBus.Test/ServiceBusMessageBusSettingsTests.cs:59
- Mock-dominated test: When_ASpecialisedMessageIsSerialized_Then_UseSpecializedSerializer src/Tests/SlimMessageBus.Host.Serialization.Hybrid.Test/HybridMessageSerializerProviderTests.cs:48
- Mock-dominated test: When_AGenericMessageIsSerialized_Then_UseDefaultSerializer src/Tests/SlimMessageBus.Host.Serialization.Hybrid.Test/HybridMessageSerializerProviderTests.cs:88
- Mock-dominated test: When_Create_Given_ActiveSession_Then_InsertsDocumentWithSession src/Tests/SlimMessageBus.Host.Outbox.MongoDb.Test/MongoDbOutboxMessageRepositoryTests.cs:90
- Silent fallback default in catch src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs:34
- Silent fallback default in catch src/SlimMessageBus.Host.AzureServiceBus/ServiceBusTopologyService.cs:47
- Partial data-retention evidence
- `WithProviderAmazonSQS` spells `SQS` where 12 names in the project spell it `Sqs` src/SlimMessageBus.Host.AmazonSQS/MessageBusBuilderExtensions.cs:12
- `WithProviderRabbitMQ` spells `MQ` where 29 names in the project spell it `Mq` src/SlimMessageBus.Host.RabbitMQ/Config/RabbitMqMessageBusBuilderExtensions.cs:12
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- Sleep-based test synchronization
- Logging is not universal
- No dependency-update automation REDACTED:12
- Not all async methods take a CancellationToken
- Nullable reference types not enabled everywhere
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 30 finding(s)
- doc comments repeat the names src/SlimMessageBus/IConsumer.cs:13
- doc comments repeat the names src/SlimMessageBus.Host/Collections/GenericTypeCache.cs:44
- doc comments repeat the names src/SlimMessageBus.Host.AmazonSQS/SqsTopologySettings.cs:55
- doc comments repeat the names src/SlimMessageBus.Host.AspNetCore/MessageBusBuilderExtensions.cs:10
- doc comments repeat the names src/SlimMessageBus.Host.AsyncApi/MessageBusBuilderExtensions.cs:13
- doc comments repeat the names src/SlimMessageBus.Host.AzureEventHub/Config/BuilderExtensions.cs:9
- doc comments repeat the names src/SlimMessageBus.Host.AzureServiceBus/Config/AsbConsumerBuilderExtensions.cs:12
- doc comments repeat the names src/Tests/SlimMessageBus.Host.AzureServiceBus.Test/ServiceBusMessageBusSettingsValidationServiceTests.cs:3
- doc comments repeat the names src/Tests/SlimMessageBus.Host.Benchmark/GetTaskResultBenchmark.cs:6
- doc comments repeat the names src/SlimMessageBus.Host.Configuration/Builders/MessageBusBuilder.cs:83
- doc comments repeat the names src/SlimMessageBus.Host.FluentValidation/FluentValidationMessageBusBuilder.cs:36
- doc comments repeat the names src/Tests/SlimMessageBus.Host.Integration.Test/MessageBusCurrent/MessageBusCurrentTests.cs:9
- doc comments repeat the names src/SlimMessageBus.Host.Interceptor/Consumers/IConsumerInterceptor.cs:8
- doc comments repeat the names src/SlimMessageBus.Host.Kafka/Configs/KafkaAbstractConsumerBuilderExtensions.cs:10
- doc comments repeat the names src/SlimMessageBus.Host.Memory/MemoryMessageBusBuilder.cs:36
- doc comments repeat the names src/SlimMessageBus.Host.Mqtt/Config/MessageBusBuilderExtensions.cs:19
- doc comments repeat the names src/SlimMessageBus.Host.Nats/Config/NatsHandlerBuilderExtensions.cs:8
- doc comments repeat the names src/SlimMessageBus.Host.Outbox/Configuration/OutboxSettings.cs:31
- doc comments repeat the names src/SlimMessageBus.Host.Outbox.PostgreSql/Configuration/BuilderExtensions.cs:11
- doc comments repeat the names src/Tests/SlimMessageBus.Host.Outbox.PostgreSql.DbContext.Test/OutboxBenchmarkTests.cs:15
- doc comments repeat the names src/SlimMessageBus.Host.Outbox.Sql/Configuration/BuilderExtensions.cs:13
- doc comments repeat the names src/Tests/SlimMessageBus.Host.Outbox.Sql.DbContext.Test/OutboxBenchmarkTests.cs:21
- doc comments repeat the names src/SlimMessageBus.Host.RabbitMQ/Config/Delegates.cs:14
- doc comments repeat the names src/SlimMessageBus.Host.Redis/Config/RedisHandlerBuilderExtensions.cs:8
- doc comments repeat the names src/SlimMessageBus.Host.Serialization/IMessageSerializerProvider.cs:8
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-83ea9d5823764f1e9f17a4551dad9bcc/history.json --exit-code 0 --source . | 2 | artifacts/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-83ea9d5823764f1e9f17a4551dad9bcc/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/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 --exclude src/Samples/Sample.Serialization.MessagesAvro/Sample --exclude src/Tests/SlimMessageBus.Host.Outbox.Sql.DbContext.Test/Migrations . | 43 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/SlimMessageBus.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 11 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.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 --exclude src/Samples/Sample.Serialization.MessagesAvro/Sample --exclude src/Tests/SlimMessageBus.Host.Outbox.Sql.DbContext.Test/Migrations . | 1 | artifacts/raw/semgrep-gdpr.json |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d1113a58f1d24706954c31d776190b93 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 18 field(s)
- CustomerCreatedEvent.Firstname src/Samples/Sample.AsyncApi.Service/Messages/CustomerCreatedEvent.cs:9
- CustomerCreatedEvent.Lastname src/Samples/Sample.AsyncApi.Service/Messages/CustomerCreatedEvent.cs:9
- Customer.Firstname src/Samples/Sample.DomainEvents.Domain/Customer.cs:9
- Customer.Lastname src/Samples/Sample.DomainEvents.Domain/Customer.cs:10
- Customer.Firstname src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:11
- Customer.Lastname src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:12
- CreateCustomerCommand.Firstname src/Samples/Sample.OutboxWebApi/Application/CreateCustomerCommand.cs:3
- CreateCustomerCommand.Lastname src/Samples/Sample.OutboxWebApi/Application/CreateCustomerCommand.cs:3
- CustomerCreatedEvent.Firstname src/Samples/Sample.OutboxWebApi/Application/CustomerCreatedEvent.cs:3
- CustomerCreatedEvent.Lastname src/Samples/Sample.OutboxWebApi/Application/CustomerCreatedEvent.cs:3
- Customer.Firstname src/Samples/Sample.OutboxWebApi/DataAccess/Customer.cs:6
- Customer.Lastname src/Samples/Sample.OutboxWebApi/DataAccess/Customer.cs:7
- CreateCustomerCommand.FirstName src/Samples/Sample.ValidatingWebApi/Commands/CreateCustomerCommand.cs:6
- CreateCustomerCommand.LastName src/Samples/Sample.ValidatingWebApi/Commands/CreateCustomerCommand.cs:7
- CustomerModel.FirstName src/Samples/Sample.ValidatingWebApi/Model/CustomerModel.cs:3
- CustomerModel.LastName src/Samples/Sample.ValidatingWebApi/Model/CustomerModel.cs:3
- SearchCustomerQuery.FirstName src/Samples/Sample.ValidatingWebApi/Queries/SearchCustomerQuery.cs:6
- SearchCustomerQuery.LastName src/Samples/Sample.ValidatingWebApi/Queries/SearchCustomerQuery.cs:7
Email — 4 field(s)
- Customer.Email src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/Customer.cs:14
- CustomerEmailChangedEvent.OldEmail src/Samples/Sample.Hybrid.ConsoleApp/DomainModelLayer/CustomerEmailChangedEvent.cs:10
- CreateCustomerCommand.Email src/Samples/Sample.ValidatingWebApi/Commands/CreateCustomerCommand.cs:8
- CustomerModel.Email src/Samples/Sample.ValidatingWebApi/Model/CustomerModel.cs:3
Phone — 2 field(s)
- CreateCustomerCommand.Phone src/Samples/Sample.ValidatingWebApi/Commands/CreateCustomerCommand.cs:9
- CustomerModel.Phone src/Samples/Sample.ValidatingWebApi/Model/CustomerModel.cs:3