Executive summary
roger-castaldo/MQContract falls short of our standard for production because we found no encryption of stored data, no key vault and no enforced HTTPS. It scores 47 out of 100 and is rated Weak, and eight of its 18 critical findings are security problems in the build pipeline and in the packages it uses.
Security and Compliance, at 35, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 11 points. Fixing the four places where personal data leaves where it belongs comes next, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 57.
Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and eight errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, limiting each secret to its own step and handling or logging the ignored errors would close these risks. Updating the vulnerable packages would fix the package with a known security hole. The two loops of parts of the code that depend on each other need breaking by moving the shared parts into a project of their own.
The product code is 15,180 lines, about €47,000 to rebuild.
If Security and Compliance rose from 35 to 70, the lowest score rated Strong, the score would rise from 47 to about 57.
New since the last survey: 3 findings
- Cancellation propagation · Async delegate without CancellationToken: Start Core/Middleware/MetricsMiddleware.cs
- Stateful singletons · Process-global static state: ConsumerConnectionHelper Core/Helpers/ConsumerConnectionHelper.cs
- Stateful singletons · Process-global static state: CreateUserProcessor Samples/CQRSSample/CreateUserProcessor.cs
Fixed since the last survey: 69 findings
- Code Coverage · Low coverage: Abstractions/MQContractMessageContext.cs Abstractions/MQContractMessageContext.cs
- Cancellation propagation · Async method without CancellationToken: GetConnectionsAsync Core/Connections/AMappableConnection.cs
- Cancellation propagation · Async method without CancellationToken: GetConnectionsAsync Core/Connections/AMappableConnection.cs
- Cancellation propagation · Async method without CancellationToken: InternalDisposeAsync Core/Connections/MappedConnection.cs
- Cancellation propagation · Async method without CancellationToken: GetConnectionAsync Core/Connections/MappedConnection.cs
- Cancellation propagation · Async method without CancellationToken: GetConnectionAsync Core/Connections/MappedConnection.cs
- Cancellation propagation · Async method without CancellationToken: EncodeAsync Core/Defaults/ABitEncoder.cs
- Cancellation propagation · Async method without CancellationToken: MapChannel Core/Middleware/ChannelMappingMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: BeforeMessageEncodeAsync Core/Middleware/ChannelMappingMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: AfterMessageEncodeAsync Core/Middleware/EncryptionMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: AfterMessageEncodeAsync Connectors/Kafka/Middleware/SchemaValidationMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: GetSchemaIdFromCacheAsync Connectors/Kafka/Middleware/SchemaValidationMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: BeforeMessageDecodeAsync Connectors/Kafka/Middleware/SchemaValidationMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: ValidateSchemaAsync Connectors/Kafka/Middleware/SchemaValidationMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: ProcessMessagesFromMessageContextAsync Connectors/Kafka/Middleware/SchemaValidationMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: CleanupAsync Connectors/ActiveMQ/Subscription.cs
- Cancellation propagation · Async method without CancellationToken: QueueDeclareAsync Connectors/RabbitMQ/Connection.cs
- Cancellation propagation · Async method without CancellationToken: ExchangeDeclareAsync Connectors/RabbitMQ/Connection.cs
- Cancellation propagation · Async method without CancellationToken: QueueDeleteAsync Connectors/RabbitMQ/Connection.cs
- Cancellation propagation · Async method without CancellationToken: ProduceSubscriptionAsync Connectors/RabbitMQ/Connection.cs
- Cancellation propagation · Async method without CancellationToken: PingAsync Connectors/RabbitMQ/Connection.cs
- Cancellation propagation · Async method without CancellationToken: ProduceInstanceAsync Connectors/RabbitMQ/Subscription.cs
- Cancellation propagation · Async method without CancellationToken: EndAsync Connectors/RabbitMQ/Subscription.cs
- Cancellation propagation · Async method without CancellationToken: ProcessMessage Connectors/Redis/Subscriptions/PubSubscription.cs
- Cancellation propagation · Async method without CancellationToken: ProcessMessage Connectors/Redis/Subscriptions/QueryResponseSubscription.cs
- Cancellation propagation · Async method without CancellationToken: CloseAsync Connectors/HiveMQ/Connection.cs
- Cancellation propagation · Async method without CancellationToken: PingAsync Connectors/AzureServiceBus/Connection.cs
- Cancellation propagation · Async method without CancellationToken: PreStartAsync Connectors/AzureServiceBus/Subscription.cs
- Cancellation propagation · Async method without CancellationToken: PingAsync Connectors/ApachePulsar/Connection.cs
- Cancellation propagation · Async method without CancellationToken: PreStartAsync Connectors/ApachePulsar/Subscription.cs
- Cancellation propagation · Async method without CancellationToken: CleanupAsync Connectors/ApachePulsar/Subscription.cs
- Cancellation propagation · Async method without CancellationToken: PingAsync Connectors/ZeroMQ/Connection.cs
- Cancellation propagation · Async method without CancellationToken: CloseAsync Connectors/AmazonSNQS/Connection.cs
- Cancellation propagation · Async method without CancellationToken: PingAsync Connectors/AmazonSNQS/Connection.cs
- Cancellation propagation · Async method without CancellationToken: DecodeAsync BenchMark/Encoders/EncodedAnnouncementEncoder.cs
- Cancellation propagation · Async method without CancellationToken: ReadAllSubscriptionMessages BenchMark/InMemoryBenchmarks/SubscribingInMemory.cs
- Cancellation propagation · Async method without CancellationToken: RunAsSubscription BenchMark/InMemoryBenchmarks/SubscriptionBenchmarks.cs
- Cancellation propagation · Async method without CancellationToken: RunAsConsumer BenchMark/InMemoryBenchmarks/SubscriptionBenchmarks.cs
- Cancellation propagation · Async method without CancellationToken: RunAsCommand BenchMark/InMemoryBenchmarks/SubscriptionBenchmarks.cs
- Cancellation propagation · Async method without CancellationToken: RunAsSubscriptionWithContext BenchMark/InMemoryBenchmarks/SubscriptionBenchmarks.cs
- Cancellation propagation · Async method without CancellationToken: RunAsConsumerWithContext BenchMark/InMemoryBenchmarks/SubscriptionBenchmarks.cs
- Cancellation propagation · Async method without CancellationToken: RunAsCommandWithContext BenchMark/InMemoryBenchmarks/SubscriptionBenchmarks.cs
- Cancellation propagation · Async method without CancellationToken: PublishDirectlyToConnection BenchMark/PublishBenchmarks/Publishing.cs
- Cancellation propagation · Async method without CancellationToken: PublishBasicEncodedMessage BenchMark/PublishBenchmarks/Publishing.cs
- Cancellation propagation · Async method without CancellationToken: PublishDefaultEncodedMessage BenchMark/PublishBenchmarks/Publishing.cs
- Cancellation propagation · Async method without CancellationToken: PublishCustomEncodedMessage BenchMark/PublishBenchmarks/Publishing.cs
- Cancellation propagation · Async method without CancellationToken: PublishBasicEncodedMessageWithContext BenchMark/PublishBenchmarks/Publishing.cs
- Cancellation propagation · Async method without CancellationToken: PublishDefaultEncodedMessageWithContext BenchMark/PublishBenchmarks/Publishing.cs
- Cancellation propagation · Async method without CancellationToken: PublishCustomEncodedMessageWithContext BenchMark/PublishBenchmarks/Publishing.cs
- Cancellation propagation · Async method without CancellationToken: PublishWithNoMiddleware BenchMark/PublishBenchmarks/PublishingWithMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: PublishWithMetrics BenchMark/PublishBenchmarks/PublishingWithMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: PublishWithOtel BenchMark/PublishBenchmarks/PublishingWithMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: PublishWithResilience BenchMark/PublishBenchmarks/PublishingWithMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: PublishWithMetricsAndOtel BenchMark/PublishBenchmarks/PublishingWithMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: PublishWithMetricsAndResilience BenchMark/PublishBenchmarks/PublishingWithMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: PublishWithOtelAndResilience BenchMark/PublishBenchmarks/PublishingWithMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: PublishWithAll BenchMark/PublishBenchmarks/PublishingWithMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: PublishBasicEncodedMessageMultipleTimes BenchMark/PublishBenchmarks/PublishingWithMiddleware.cs
- Cancellation propagation · Async method without CancellationToken: RegisterCommandProcessorAsync CQRS/CqrsConnection.cs
- Cancellation propagation · Async method without CancellationToken: RegisterCommandProcessorAsync CQRS/CqrsConnection.cs
- Cancellation propagation · Async method without CancellationToken: RegisterQueryProcessorAsync CQRS/CqrsConnection.cs
- Cancellation propagation · Async method without CancellationToken: RegisterCommandProcessorAsync CQRS/Registrars/ContractedConnectionRegistrar.cs
- Cancellation propagation · Async method without CancellationToken: RegisterCommandProcessorAsync CQRS/Registrars/ContractedConnectionRegistrar.cs
- Cancellation propagation · Async method without CancellationToken: RegisterQueryProcessorAsync CQRS/Registrars/ContractedConnectionRegistrar.cs
- Cancellation propagation · Async method without CancellationToken: RegisterCommandProcessorAsync CQRS/Registrars/MappedConnectionRegistrar.cs
- Cancellation propagation · Async method without CancellationToken: RegisterCommandProcessorAsync CQRS/Registrars/MappedConnectionRegistrar.cs
- Cancellation propagation · Async method without CancellationToken: RegisterQueryProcessorAsync CQRS/Registrars/MappedConnectionRegistrar.cs
- Cancellation propagation · Async method drops its CancellationToken: SubscribeQueryAsync Connectors/RabbitMQ/Connection.cs
- Cancellation propagation · Async method drops its CancellationToken: RecieveMessageAsync Connectors/Redis/Subscriptions/SubscriptionBase.cs
Rebuild cost: about €47,000 · Estimate
| Cost to rebuild | €15,000 to €78,000, for 258 to 821 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, 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 47. 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 | Small: 15,180 lines of product code, of which 40% is declarations and boilerplate, 23% straight logic and 37% logic with branches |
| Comment lines | The estimate prices 11,677 lines. Comment lines count towards the size of 15,180 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 Attributes | 2 Interfaces.Encoding | 3 Interfaces.Messages | 4 Messages | 5 Interfaces.Encrypting | 6 Interfaces.Factories | 7 Interfaces.Middleware | 8 Interfaces.Service | 9 Interfaces | 10 Kafka.Middleware | 11 NATS.Subscriptions | 12 MQContract | 13 ActiveMQ | 14 AmazonSNQS | 15 ApachePulsar | 16 AzureServiceBus | 17 CQRS.Interfaces.Command | 18 CQRS.Interfaces.Query | 19 Defaults | 20 Extensions | 21 Factories | 22 GooglePubSub | 23 HiveMQ | 24 InMemory | 25 Interfaces.Consumers | 26 Kafka | 27 Middleware.Metrics | 28 NATS | 29 RabbitMQ | 30 Redis | 31 ZeroMQ | 32 CQRS.Consumers | 33 Middleware | 34 CQRS.Interfaces | 35 Connections | 36 CQRS | 37 CQRS.Extensions | 38 CQRS.Registrars | 39 Subscriptions | 40 CQRS.Contexts |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Attributes | ||||||||||||||||||||||||||||||||||||||||
| 2 Interfaces.Encoding | ||||||||||||||||||||||||||||||||||||||||
| 3 Interfaces.Messages | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 Messages | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 5 Interfaces.Encrypting | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 Interfaces.Factories | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 7 Interfaces.Middleware | 4 | |||||||||||||||||||||||||||||||||||||||
| 8 Interfaces.Service | 11 | |||||||||||||||||||||||||||||||||||||||
| 9 Interfaces | 15 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 10 Kafka.Middleware | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 11 NATS.Subscriptions | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 MQContract | 1 | 3 | 2 | 7 | 3 | 1 | 2 | 7 | ||||||||||||||||||||||||||||||||
| 13 ActiveMQ | 6 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 14 AmazonSNQS | 7 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 15 ApachePulsar | 5 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 16 AzureServiceBus | 5 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 CQRS.Interfaces.Command | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 CQRS.Interfaces.Query | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 Defaults | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 Extensions | 3 | 6 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 21 Factories | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 GooglePubSub | 5 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 HiveMQ | 5 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 InMemory | 11 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 Interfaces.Consumers | 4 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 26 Kafka | 6 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 27 Middleware.Metrics | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 NATS | 6 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 RabbitMQ | 5 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 Redis | 5 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 ZeroMQ | 9 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 CQRS.Consumers | 2 | 4 | 2 | 1 | 4 | 4 | ||||||||||||||||||||||||||||||||||
| 33 Middleware | 7 | 4 | 29 | 1 | 1 | 7 | 3 | |||||||||||||||||||||||||||||||||
| 34 CQRS.Interfaces | 1 | 1 | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 35 Connections | 5 | 44 | 5 | 2 | 6 | 11 | 15 | 12 | 3 | |||||||||||||||||||||||||||||||
| 36 CQRS | 4 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 37 CQRS.Extensions | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 CQRS.Registrars | 2 | 2 | 6 | 2 | ||||||||||||||||||||||||||||||||||||
| 39 Subscriptions | 6 | 4 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 40 CQRS.Contexts | 3 | 1 | 1 | 2 | 4 |
3→4 Interfaces.Messages uses Messages part of a loop✕
- Connections
- 1 pair of types, where a type in Interfaces.Messages uses a type in Messages.
- The types involved
MQContract.Interfaces.Messages.IEncodedMessage→MQContract.Messages.MessageHeader
- Direction
- Interfaces.Messages uses Messages, so a change to Messages can break Interfaces.Messages, while a change to Interfaces.Messages can't break Messages.
- 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.
4→3 Messages uses Interfaces.Messages✕
- Connections
- 1 pair of types, where a type in Messages uses a type in Interfaces.Messages.
- The types involved
MQContract.Messages.EncodedMessage→MQContract.Interfaces.Messages.IEncodedMessage
- Direction
- Messages uses Interfaces.Messages, so a change to Interfaces.Messages can break Messages, while a change to Messages can't break Interfaces.Messages.
- Position
- Below the diagonal: Messages uses a module listed above it, which is the healthy direction.
4→9 Messages uses Interfaces part of a loop✕
- Connections
- 1 pair of types, where a type in Messages uses a type in Interfaces.
- The types involved
MQContract.Messages.ReceivedMessage→MQContract.Interfaces.IReceivedMessage
- Direction
- Messages uses Interfaces, so a change to Interfaces can break Messages, while a change to Messages can't break Interfaces.
- 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.
4→12 Messages uses MQContract part of a loop✕
- Connections
- 2 pairs of types, where a type in Messages uses a type in MQContract.
- The types involved
MQContract.Messages.ErrorServiceMessage→MQContract.QueryResponseExceptionMQContract.Messages.MessageFilters→MQContract.MessageFilterResult
- Direction
- Messages uses MQContract, so a change to MQContract can break Messages, while a change to Messages can't break MQContract.
- 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→4 Interfaces.Encrypting uses Messages✕
- Connections
- 1 pair of types, where a type in Interfaces.Encrypting uses a type in Messages.
- The types involved
MQContract.Interfaces.Encrypting.IMessageEncryptor→MQContract.Messages.MessageHeader
- Direction
- Interfaces.Encrypting uses Messages, so a change to Messages can break Interfaces.Encrypting, while a change to Interfaces.Encrypting can't break Messages.
- Position
- Below the diagonal: Interfaces.Encrypting uses a module listed above it, which is the healthy direction.
6→3 Interfaces.Factories uses Interfaces.Messages✕
- Connections
- 1 pair of types, where a type in Interfaces.Factories uses a type in Interfaces.Messages.
- The types involved
MQContract.Interfaces.Factories.IMessageFactory→MQContract.Interfaces.Messages.IEncodedMessage
- Direction
- Interfaces.Factories uses Interfaces.Messages, so a change to Interfaces.Messages can break Interfaces.Factories, while a change to Interfaces.Factories can't break Interfaces.Messages.
- Position
- Below the diagonal: Interfaces.Factories uses a module listed above it, which is the healthy direction.
6→4 Interfaces.Factories uses Messages✕
- Connections
- 2 pairs of types, where a type in Interfaces.Factories uses a type in Messages.
- The types involved
MQContract.Interfaces.Factories.IMessageFactory→MQContract.Messages.MessageHeaderMQContract.Interfaces.Factories.IMessageFactory→MQContract.Messages.ServiceMessage
- Direction
- Interfaces.Factories uses Messages, so a change to Messages can break Interfaces.Factories, while a change to Interfaces.Factories can't break Messages.
- Position
- Below the diagonal: Interfaces.Factories uses a module listed above it, which is the healthy direction.
7→4 Interfaces.Middleware uses Messages✕
- Connections
- 4 pairs of types, where a type in Interfaces.Middleware uses a type in Messages.
- The types involved
MQContract.Interfaces.Middleware.DecodableMessage→MQContract.Messages.MessageHeaderMQContract.Interfaces.Middleware.DecodedMessage→MQContract.Messages.MessageHeaderMQContract.Interfaces.Middleware.EncodableMessage→MQContract.Messages.MessageHeaderMQContract.Interfaces.Middleware.IAfterEncodeMiddleware→MQContract.Messages.ServiceMessage
- Direction
- Interfaces.Middleware uses Messages, so a change to Messages can break Interfaces.Middleware, while a change to Interfaces.Middleware can't break Messages.
- Position
- Below the diagonal: Interfaces.Middleware uses a module listed above it, which is the healthy direction.
8→4 Interfaces.Service uses Messages✕
- Connections
- 11 pairs of types, where a type in Interfaces.Service uses a type in Messages.
- The types involved
MQContract.Interfaces.Service.IInboxQueryableMessageServiceConnection→MQContract.Messages.ReceivedInboxServiceMessageMQContract.Interfaces.Service.IInboxQueryableMessageServiceConnection→MQContract.Messages.ServiceMessageMQContract.Interfaces.Service.IInboxQueryableMessageServiceConnection→MQContract.Messages.TransmissionResultMQContract.Interfaces.Service.IMessageServiceConnection→MQContract.Messages.ReceivedServiceMessageMQContract.Interfaces.Service.IMessageServiceConnection→MQContract.Messages.ServiceMessageMQContract.Interfaces.Service.IMessageServiceConnection→MQContract.Messages.TransmissionResultMQContract.Interfaces.Service.IPingableMessageServiceConnection→MQContract.Messages.PingResultMQContract.Interfaces.Service.IQueryResponseMessageServiceConnection→MQContract.Messages.ServiceMessageMQContract.Interfaces.Service.IQueryResponseMessageServiceConnection→MQContract.Messages.ServiceQueryResultMQContract.Interfaces.Service.IQueryableMessageServiceConnection→MQContract.Messages.ReceivedServiceMessageMQContract.Interfaces.Service.IQueryableMessageServiceConnection→MQContract.Messages.ServiceMessage
- Direction
- Interfaces.Service uses Messages, so a change to Messages can break Interfaces.Service, while a change to Interfaces.Service can't break Messages.
- Position
- Below the diagonal: Interfaces.Service uses a module listed above it, which is the healthy direction.
9→4 Interfaces uses Messages✕
- Connections
- 15 pairs of types, where a type in Interfaces uses a type in Messages.
- The types involved
MQContract.Interfaces.IBaseContractConnection→MQContract.Messages.MessageFiltersMQContract.Interfaces.IBaseContractConnection→MQContract.Messages.QueryResponseMessageMQContract.Interfaces.IConsumerContractConnection→MQContract.Messages.MessageFiltersMQContract.Interfaces.IContractConnection→MQContract.Messages.MessageHeaderMQContract.Interfaces.IContractConnection→MQContract.Messages.PingResultMQContract.Interfaces.IContractConnection→MQContract.Messages.QueryResultMQContract.Interfaces.IContractConnection→MQContract.Messages.TransmissionMessageMQContract.Interfaces.IContractConnection→MQContract.Messages.TransmissionResultMQContract.Interfaces.IMappableContractConnection→MQContract.Messages.MessageHeaderMQContract.Interfaces.IMultiServiceContractConnection→MQContract.Messages.MessageHeaderMQContract.Interfaces.IMultiServiceContractConnection→MQContract.Messages.MultiTransmissionResultMQContract.Interfaces.IMultiServiceContractConnection→MQContract.Messages.PingResultMQContract.Interfaces.IMultiServiceContractConnection→MQContract.Messages.QueryResultMQContract.Interfaces.IMultiServiceContractConnection→MQContract.Messages.TransmissionMessageMQContract.Interfaces.IReceivedMessage→MQContract.Messages.MessageHeader
- Direction
- Interfaces uses Messages, so a change to Messages can break Interfaces, while a change to Interfaces can't break Messages.
- Position
- Below the diagonal: Interfaces uses a module listed above it, which is the healthy direction.
9→7 Interfaces uses Interfaces.Middleware✕
- Connections
- 2 pairs of types, where a type in Interfaces uses a type in Interfaces.Middleware.
- The types involved
MQContract.Interfaces.IMiddlewareContractConnection→MQContract.Interfaces.Middleware.IMiddlewareMQContract.Interfaces.IMiddlewareContractConnection→MQContract.Interfaces.Middleware.ISpecificTypeMiddleware
- Direction
- Interfaces uses Interfaces.Middleware, so a change to Interfaces.Middleware can break Interfaces, while a change to Interfaces can't break Interfaces.Middleware.
- Position
- Below the diagonal: Interfaces uses a module listed above it, which is the healthy direction.
9→8 Interfaces uses Interfaces.Service✕
- Connections
- 2 pairs of types, where a type in Interfaces uses a type in Interfaces.Service.
- The types involved
MQContract.Interfaces.IMappableContractConnection→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Interfaces.IMultiServiceContractConnection→MQContract.Interfaces.Service.IMessageServiceConnection
- Direction
- Interfaces uses Interfaces.Service, so a change to Interfaces.Service can break Interfaces, while a change to Interfaces can't break Interfaces.Service.
- Position
- Below the diagonal: Interfaces uses a module listed above it, which is the healthy direction.
9→12 Interfaces uses MQContract part of a loop✕
- Connections
- 1 pair of types, where a type in Interfaces uses a type in MQContract.
- The types involved
MQContract.Interfaces.IMessageContextContractConnection→MQContract.MQContractMessageContext
- Direction
- Interfaces uses MQContract, so a change to MQContract can break Interfaces, while a change to Interfaces can't break MQContract.
- 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.
10→4 Kafka.Middleware uses Messages✕
- Connections
- 1 pair of types, where a type in Kafka.Middleware uses a type in Messages.
- The types involved
MQContract.Kafka.Middleware.SchemaValidationMiddleware→MQContract.Messages.ServiceMessage
- Direction
- Kafka.Middleware uses Messages, so a change to Messages can break Kafka.Middleware, while a change to Kafka.Middleware can't break Messages.
- Position
- Below the diagonal: Kafka.Middleware uses a module listed above it, which is the healthy direction.
10→7 Kafka.Middleware uses Interfaces.Middleware✕
- Connections
- 6 pairs of types, where a type in Kafka.Middleware uses a type in Interfaces.Middleware.
- The types involved
MQContract.Kafka.Middleware.SchemaValidationMiddleware→MQContract.Interfaces.Middleware.DecodableMessageMQContract.Kafka.Middleware.SchemaValidationMiddleware→MQContract.Interfaces.Middleware.IAfterEncodeMiddlewareMQContract.Kafka.Middleware.SchemaValidationMiddleware→MQContract.Interfaces.Middleware.IBeforeDecodeMiddlewareMQContract.Kafka.Middleware.SchemaValidationMiddleware→MQContract.Interfaces.Middleware.IContextMQContract.Kafka.Middleware.SchemaValidationMiddleware→MQContract.Interfaces.Middleware.IMessageContextAwareMiddlewareMQContract.Kafka.Middleware.SchemaValidationMiddleware→MQContract.Interfaces.Middleware.MessageContextDefintion
- Direction
- Kafka.Middleware uses Interfaces.Middleware, so a change to Interfaces.Middleware can break Kafka.Middleware, while a change to Kafka.Middleware can't break Interfaces.Middleware.
- Position
- Below the diagonal: Kafka.Middleware uses a module listed above it, which is the healthy direction.
11→4 NATS.Subscriptions uses Messages✕
- Connections
- 5 pairs of types, where a type in NATS.Subscriptions uses a type in Messages.
- The types involved
MQContract.NATS.Subscriptions.PublishSubscription→MQContract.Messages.ReceivedServiceMessageMQContract.NATS.Subscriptions.QuerySubscription→MQContract.Messages.ReceivedServiceMessageMQContract.NATS.Subscriptions.QuerySubscription→MQContract.Messages.ServiceMessageMQContract.NATS.Subscriptions.StreamSubscription→MQContract.Messages.ReceivedServiceMessageMQContract.NATS.Subscriptions.SubscriptionBase→MQContract.Messages.ReceivedServiceMessage
- Direction
- NATS.Subscriptions uses Messages, so a change to Messages can break NATS.Subscriptions, while a change to NATS.Subscriptions can't break Messages.
- Position
- Below the diagonal: NATS.Subscriptions uses a module listed above it, which is the healthy direction.
11→8 NATS.Subscriptions uses Interfaces.Service✕
- Connections
- 1 pair of types, where a type in NATS.Subscriptions uses a type in Interfaces.Service.
- The types involved
MQContract.NATS.Subscriptions.IInternalServiceSubscription→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- NATS.Subscriptions uses Interfaces.Service, so a change to Interfaces.Service can break NATS.Subscriptions, while a change to NATS.Subscriptions can't break Interfaces.Service.
- Position
- Below the diagonal: NATS.Subscriptions uses a module listed above it, which is the healthy direction.
12→1 MQContract uses Attributes✕
- Connections
- 1 pair of types, where a type in MQContract uses a type in Attributes.
- The types involved
MQContract.MessageContext→MQContract.Attributes.MessageAttribute
- Direction
- MQContract uses Attributes, so a change to Attributes can break MQContract, while a change to MQContract can't break Attributes.
- Position
- Below the diagonal: MQContract uses a module listed above it, which is the healthy direction.
12→2 MQContract uses Interfaces.Encoding✕
- Connections
- 3 pairs of types, where a type in MQContract uses a type in Interfaces.Encoding.
- The types involved
MQContract.ContractConnection→MQContract.Interfaces.Encoding.IMessageEncoderMQContract.MQContractMessageContext→MQContract.Interfaces.Encoding.IMessageEncoderMQContract.MessageContext→MQContract.Interfaces.Encoding.IMessageEncoder
- Direction
- MQContract uses Interfaces.Encoding, so a change to Interfaces.Encoding can break MQContract, while a change to MQContract can't break Interfaces.Encoding.
- Position
- Below the diagonal: MQContract uses a module listed above it, which is the healthy direction.
12→3 MQContract uses Interfaces.Messages✕
- Connections
- 2 pairs of types, where a type in MQContract uses a type in Interfaces.Messages.
- The types involved
MQContract.MQContractMessageContext→MQContract.Interfaces.Messages.IEncodedMessageMQContract.MessageContext→MQContract.Interfaces.Messages.IEncodedMessage
- Direction
- MQContract uses Interfaces.Messages, so a change to Interfaces.Messages can break MQContract, while a change to MQContract can't break Interfaces.Messages.
- Position
- Below the diagonal: MQContract uses a module listed above it, which is the healthy direction.
12→4 MQContract uses Messages✕
- Connections
- 7 pairs of types, where a type in MQContract uses a type in Messages.
- The types involved
MQContract.BatchedMessageStream→MQContract.Messages.ServiceMessageMQContract.BatchedMessageStream→MQContract.Messages.TransmissionResultMQContract.MQContractMessageContext→MQContract.Messages.QueryResultMQContract.MessageBatch→MQContract.Messages.TransmissionResultMQContract.MessageContext→MQContract.Messages.QueryResultMQContract.MessageContext→MQContract.Messages.TransmissionMessageMQContract.delProduceServiceMessage→MQContract.Messages.ServiceMessage
- Direction
- MQContract uses Messages, so a change to Messages can break MQContract, while a change to MQContract can't break Messages.
- Position
- Below the diagonal: MQContract uses a module listed above it, which is the healthy direction.
12→5 MQContract uses Interfaces.Encrypting✕
- Connections
- 3 pairs of types, where a type in MQContract uses a type in Interfaces.Encrypting.
- The types involved
MQContract.ContractConnection→MQContract.Interfaces.Encrypting.IMessageEncryptorMQContract.MQContractMessageContext→MQContract.Interfaces.Encrypting.IMessageEncryptorMQContract.MessageContext→MQContract.Interfaces.Encrypting.IMessageEncryptor
- Direction
- MQContract uses Interfaces.Encrypting, so a change to Interfaces.Encrypting can break MQContract, while a change to MQContract can't break Interfaces.Encrypting.
- Position
- Below the diagonal: MQContract uses a module listed above it, which is the healthy direction.
12→7 MQContract uses Interfaces.Middleware✕
- Connections
- 1 pair of types, where a type in MQContract uses a type in Interfaces.Middleware.
- The types involved
MQContract.MQContractMessageContext→MQContract.Interfaces.Middleware.MessageContextDefintion
- Direction
- MQContract uses Interfaces.Middleware, so a change to Interfaces.Middleware can break MQContract, while a change to MQContract can't break Interfaces.Middleware.
- Position
- Below the diagonal: MQContract uses a module listed above it, which is the healthy direction.
12→8 MQContract uses Interfaces.Service✕
- Connections
- 2 pairs of types, where a type in MQContract uses a type in Interfaces.Service.
- The types involved
MQContract.BaseLoopSubscription→MQContract.Interfaces.Service.IServiceSubscriptionMQContract.ContractConnection→MQContract.Interfaces.Service.IMessageServiceConnection
- Direction
- MQContract uses Interfaces.Service, so a change to Interfaces.Service can break MQContract, while a change to MQContract can't break Interfaces.Service.
- Position
- Below the diagonal: MQContract uses a module listed above it, which is the healthy direction.
12→9 MQContract uses Interfaces✕
- Connections
- 7 pairs of types, where a type in MQContract uses a type in Interfaces.
- The types involved
MQContract.ContractConnection→MQContract.Interfaces.IContractedConnectionMQContract.ContractConnection→MQContract.Interfaces.IMappedContractConnectionMQContract.ContractConnection→MQContract.Interfaces.IMultiServiceContractConnectionMQContract.MQContractMessageContext→MQContract.Interfaces.IContractConnectionMQContract.MQContractMessageContext→MQContract.Interfaces.IMultiServiceContractConnectionMQContract.MessageContext→MQContract.Interfaces.IContractConnectionMQContract.MessageContext→MQContract.Interfaces.IMultiServiceContractConnection
- Direction
- MQContract uses Interfaces, so a change to Interfaces can break MQContract, while a change to MQContract can't break Interfaces.
- Position
- Below the diagonal: MQContract uses a module listed above it, which is the healthy direction.
13→4 ActiveMQ uses Messages✕
- Connections
- 6 pairs of types, where a type in ActiveMQ uses a type in Messages.
- The types involved
MQContract.ActiveMQ.Connection→MQContract.Messages.MessageHeaderMQContract.ActiveMQ.Connection→MQContract.Messages.PingResultMQContract.ActiveMQ.Connection→MQContract.Messages.ReceivedInboxServiceMessageMQContract.ActiveMQ.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.ActiveMQ.Connection→MQContract.Messages.ServiceMessageMQContract.ActiveMQ.Connection→MQContract.Messages.TransmissionResult
- Direction
- ActiveMQ uses Messages, so a change to Messages can break ActiveMQ, while a change to ActiveMQ can't break Messages.
- Position
- Below the diagonal: ActiveMQ uses a module listed above it, which is the healthy direction.
13→8 ActiveMQ uses Interfaces.Service✕
- Connections
- 3 pairs of types, where a type in ActiveMQ uses a type in Interfaces.Service.
- The types involved
MQContract.ActiveMQ.Connection→MQContract.Interfaces.Service.IInboxQueryableMessageServiceConnectionMQContract.ActiveMQ.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.ActiveMQ.Connection→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- ActiveMQ uses Interfaces.Service, so a change to Interfaces.Service can break ActiveMQ, while a change to ActiveMQ can't break Interfaces.Service.
- Position
- Below the diagonal: ActiveMQ uses a module listed above it, which is the healthy direction.
13→12 ActiveMQ uses MQContract✕
- Connections
- 2 pairs of types, where a type in ActiveMQ uses a type in MQContract.
- The types involved
MQContract.ActiveMQ.Connection→MQContract.BatchedMessageStreamMQContract.ActiveMQ.Subscription→MQContract.BaseLoopSubscription
- Direction
- ActiveMQ uses MQContract, so a change to MQContract can break ActiveMQ, while a change to ActiveMQ can't break MQContract.
- Position
- Below the diagonal: ActiveMQ uses a module listed above it, which is the healthy direction.
14→4 AmazonSNQS uses Messages✕
- Connections
- 7 pairs of types, where a type in AmazonSNQS uses a type in Messages.
- The types involved
MQContract.AmazonSNQS.Connection→MQContract.Messages.PingResultMQContract.AmazonSNQS.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.AmazonSNQS.Connection→MQContract.Messages.ServiceMessageMQContract.AmazonSNQS.Connection→MQContract.Messages.TransmissionResultMQContract.AmazonSNQS.MessageMapper→MQContract.Messages.ReceivedServiceMessageMQContract.AmazonSNQS.MessageMapper→MQContract.Messages.ServiceMessageMQContract.AmazonSNQS.Subscription→MQContract.Messages.ReceivedServiceMessage
- Direction
- AmazonSNQS uses Messages, so a change to Messages can break AmazonSNQS, while a change to AmazonSNQS can't break Messages.
- Position
- Below the diagonal: AmazonSNQS uses a module listed above it, which is the healthy direction.
14→8 AmazonSNQS uses Interfaces.Service✕
- Connections
- 2 pairs of types, where a type in AmazonSNQS uses a type in Interfaces.Service.
- The types involved
MQContract.AmazonSNQS.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.AmazonSNQS.Connection→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- AmazonSNQS uses Interfaces.Service, so a change to Interfaces.Service can break AmazonSNQS, while a change to AmazonSNQS can't break Interfaces.Service.
- Position
- Below the diagonal: AmazonSNQS uses a module listed above it, which is the healthy direction.
14→12 AmazonSNQS uses MQContract✕
- Connections
- 2 pairs of types, where a type in AmazonSNQS uses a type in MQContract.
- The types involved
MQContract.AmazonSNQS.Connection→MQContract.BatchedMessageStreamMQContract.AmazonSNQS.Subscription→MQContract.BaseLoopSubscription
- Direction
- AmazonSNQS uses MQContract, so a change to MQContract can break AmazonSNQS, while a change to AmazonSNQS can't break MQContract.
- Position
- Below the diagonal: AmazonSNQS uses a module listed above it, which is the healthy direction.
15→4 ApachePulsar uses Messages✕
- Connections
- 5 pairs of types, where a type in ApachePulsar uses a type in Messages.
- The types involved
MQContract.ApachePulsar.Connection→MQContract.Messages.PingResultMQContract.ApachePulsar.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.ApachePulsar.Connection→MQContract.Messages.ServiceMessageMQContract.ApachePulsar.Connection→MQContract.Messages.TransmissionResultMQContract.ApachePulsar.Subscription→MQContract.Messages.ReceivedServiceMessage
- Direction
- ApachePulsar uses Messages, so a change to Messages can break ApachePulsar, while a change to ApachePulsar can't break Messages.
- Position
- Below the diagonal: ApachePulsar uses a module listed above it, which is the healthy direction.
15→8 ApachePulsar uses Interfaces.Service✕
- Connections
- 2 pairs of types, where a type in ApachePulsar uses a type in Interfaces.Service.
- The types involved
MQContract.ApachePulsar.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.ApachePulsar.Connection→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- ApachePulsar uses Interfaces.Service, so a change to Interfaces.Service can break ApachePulsar, while a change to ApachePulsar can't break Interfaces.Service.
- Position
- Below the diagonal: ApachePulsar uses a module listed above it, which is the healthy direction.
15→12 ApachePulsar uses MQContract✕
- Connections
- 2 pairs of types, where a type in ApachePulsar uses a type in MQContract.
- The types involved
MQContract.ApachePulsar.Connection→MQContract.BatchedMessageStreamMQContract.ApachePulsar.Subscription→MQContract.BaseLoopSubscription
- Direction
- ApachePulsar uses MQContract, so a change to MQContract can break ApachePulsar, while a change to ApachePulsar can't break MQContract.
- Position
- Below the diagonal: ApachePulsar uses a module listed above it, which is the healthy direction.
16→4 AzureServiceBus uses Messages✕
- Connections
- 5 pairs of types, where a type in AzureServiceBus uses a type in Messages.
- The types involved
MQContract.AzureServiceBus.Connection→MQContract.Messages.PingResultMQContract.AzureServiceBus.Connection→MQContract.Messages.ReceivedInboxServiceMessageMQContract.AzureServiceBus.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.AzureServiceBus.Connection→MQContract.Messages.ServiceMessageMQContract.AzureServiceBus.Connection→MQContract.Messages.TransmissionResult
- Direction
- AzureServiceBus uses Messages, so a change to Messages can break AzureServiceBus, while a change to AzureServiceBus can't break Messages.
- Position
- Below the diagonal: AzureServiceBus uses a module listed above it, which is the healthy direction.
16→8 AzureServiceBus uses Interfaces.Service✕
- Connections
- 3 pairs of types, where a type in AzureServiceBus uses a type in Interfaces.Service.
- The types involved
MQContract.AzureServiceBus.Connection→MQContract.Interfaces.Service.IInboxQueryableMessageServiceConnectionMQContract.AzureServiceBus.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.AzureServiceBus.Connection→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- AzureServiceBus uses Interfaces.Service, so a change to Interfaces.Service can break AzureServiceBus, while a change to AzureServiceBus can't break Interfaces.Service.
- Position
- Below the diagonal: AzureServiceBus uses a module listed above it, which is the healthy direction.
16→12 AzureServiceBus uses MQContract✕
- Connections
- 1 pair of types, where a type in AzureServiceBus uses a type in MQContract.
- The types involved
MQContract.AzureServiceBus.Subscription→MQContract.BaseLoopSubscription
- Direction
- AzureServiceBus uses MQContract, so a change to MQContract can break AzureServiceBus, while a change to AzureServiceBus can't break MQContract.
- Position
- Below the diagonal: AzureServiceBus uses a module listed above it, which is the healthy direction.
17→12 CQRS.Interfaces.Command uses MQContract✕
- Connections
- 1 pair of types, where a type in CQRS.Interfaces.Command uses a type in MQContract.
- The types involved
MQContract.CQRS.Interfaces.Command.IFilteredCommandProcessor→MQContract.MessageFilterResult
- Direction
- CQRS.Interfaces.Command uses MQContract, so a change to MQContract can break CQRS.Interfaces.Command, while a change to CQRS.Interfaces.Command can't break MQContract.
- Position
- Below the diagonal: CQRS.Interfaces.Command uses a module listed above it, which is the healthy direction.
17→34 CQRS.Interfaces.Command uses CQRS.Interfaces part of a loop✕
- Connections
- 2 pairs of types, where a type in CQRS.Interfaces.Command uses a type in CQRS.Interfaces.
- The types involved
MQContract.CQRS.Interfaces.Command.ICommandInvocationContext→MQContract.CQRS.Interfaces.IInvocationContextMQContract.CQRS.Interfaces.Command.ICommandProcessor→MQContract.CQRS.Interfaces.IProcessor
- Direction
- CQRS.Interfaces.Command uses CQRS.Interfaces, so a change to CQRS.Interfaces can break CQRS.Interfaces.Command, while a change to CQRS.Interfaces.Command can't break CQRS.Interfaces.
- 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.
17→36 CQRS.Interfaces.Command uses CQRS part of a loop✕
- Connections
- 1 pair of types, where a type in CQRS.Interfaces.Command uses a type in CQRS.
- The types involved
MQContract.CQRS.Interfaces.Command.IFilteredCommandProcessor→MQContract.CQRS.Context
- Direction
- CQRS.Interfaces.Command uses CQRS, so a change to CQRS can break CQRS.Interfaces.Command, while a change to CQRS.Interfaces.Command can't break CQRS.
- 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.
18→12 CQRS.Interfaces.Query uses MQContract✕
- Connections
- 1 pair of types, where a type in CQRS.Interfaces.Query uses a type in MQContract.
- The types involved
MQContract.CQRS.Interfaces.Query.IFilteredQueryProcessor→MQContract.MessageFilterResult
- Direction
- CQRS.Interfaces.Query uses MQContract, so a change to MQContract can break CQRS.Interfaces.Query, while a change to CQRS.Interfaces.Query can't break MQContract.
- Position
- Below the diagonal: CQRS.Interfaces.Query uses a module listed above it, which is the healthy direction.
18→34 CQRS.Interfaces.Query uses CQRS.Interfaces part of a loop✕
- Connections
- 2 pairs of types, where a type in CQRS.Interfaces.Query uses a type in CQRS.Interfaces.
- The types involved
MQContract.CQRS.Interfaces.Query.IQueryInvocationContext→MQContract.CQRS.Interfaces.IInvocationContextMQContract.CQRS.Interfaces.Query.IQueryProcessor→MQContract.CQRS.Interfaces.IProcessor
- Direction
- CQRS.Interfaces.Query uses CQRS.Interfaces, so a change to CQRS.Interfaces can break CQRS.Interfaces.Query, while a change to CQRS.Interfaces.Query can't break CQRS.Interfaces.
- 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.
18→36 CQRS.Interfaces.Query uses CQRS part of a loop✕
- Connections
- 1 pair of types, where a type in CQRS.Interfaces.Query uses a type in CQRS.
- The types involved
MQContract.CQRS.Interfaces.Query.IFilteredQueryProcessor→MQContract.CQRS.Context
- Direction
- CQRS.Interfaces.Query uses CQRS, so a change to CQRS can break CQRS.Interfaces.Query, while a change to CQRS.Interfaces.Query can't break CQRS.
- 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.
19→2 Defaults uses Interfaces.Encoding✕
- Connections
- 6 pairs of types, where a type in Defaults uses a type in Interfaces.Encoding.
- The types involved
MQContract.Defaults.ABitEncoder→MQContract.Interfaces.Encoding.IMessageTypeEncoderMQContract.Defaults.ByteArrayEncoder→MQContract.Interfaces.Encoding.IMessageTypeEncoderMQContract.Defaults.ByteEncoder→MQContract.Interfaces.Encoding.IMessageTypeEncoderMQContract.Defaults.CharEncoder→MQContract.Interfaces.Encoding.IMessageTypeEncoderMQContract.Defaults.JsonEncoder→MQContract.Interfaces.Encoding.IMessageTypeEncoderMQContract.Defaults.StringEncoder→MQContract.Interfaces.Encoding.IMessageTypeEncoder
- Direction
- Defaults uses Interfaces.Encoding, so a change to Interfaces.Encoding can break Defaults, while a change to Defaults can't break Interfaces.Encoding.
- Position
- Below the diagonal: Defaults uses a module listed above it, which is the healthy direction.
19→12 Defaults uses MQContract✕
- Connections
- 1 pair of types, where a type in Defaults uses a type in MQContract.
- The types involved
MQContract.Defaults.DefaultMessageContext→MQContract.MQContractMessageContext
- Direction
- Defaults uses MQContract, so a change to MQContract can break Defaults, while a change to Defaults can't break MQContract.
- Position
- Below the diagonal: Defaults uses a module listed above it, which is the healthy direction.
20→4 Extensions uses Messages✕
- Connections
- 3 pairs of types, where a type in Extensions uses a type in Messages.
- The types involved
MQContract.Extensions.ContractedConnectionExtensions→MQContract.Messages.MessageFiltersMQContract.Extensions.MappedConnectionExtensions→MQContract.Messages.MessageFiltersMQContract.Extensions.MultiServiceConnectionExtensions→MQContract.Messages.MessageFilters
- Direction
- Extensions uses Messages, so a change to Messages can break Extensions, while a change to Extensions can't break Messages.
- Position
- Below the diagonal: Extensions uses a module listed above it, which is the healthy direction.
20→7 Extensions uses Interfaces.Middleware✕
- Connections
- 6 pairs of types, where a type in Extensions uses a type in Interfaces.Middleware.
- The types involved
MQContract.Extensions.ContractedConnectionExtensions→MQContract.Interfaces.Middleware.IMiddlewareMQContract.Extensions.ContractedConnectionExtensions→MQContract.Interfaces.Middleware.ISpecificTypeMiddlewareMQContract.Extensions.MappedConnectionExtensions→MQContract.Interfaces.Middleware.IMiddlewareMQContract.Extensions.MappedConnectionExtensions→MQContract.Interfaces.Middleware.ISpecificTypeMiddlewareMQContract.Extensions.MultiServiceConnectionExtensions→MQContract.Interfaces.Middleware.IMiddlewareMQContract.Extensions.MultiServiceConnectionExtensions→MQContract.Interfaces.Middleware.ISpecificTypeMiddleware
- Direction
- Extensions uses Interfaces.Middleware, so a change to Interfaces.Middleware can break Extensions, while a change to Extensions can't break Interfaces.Middleware.
- Position
- Below the diagonal: Extensions uses a module listed above it, which is the healthy direction.
20→9 Extensions uses Interfaces✕
- Connections
- 3 pairs of types, where a type in Extensions uses a type in Interfaces.
- The types involved
MQContract.Extensions.ContractedConnectionExtensions→MQContract.Interfaces.IContractedConnectionMQContract.Extensions.MappedConnectionExtensions→MQContract.Interfaces.IMappedContractConnectionMQContract.Extensions.MultiServiceConnectionExtensions→MQContract.Interfaces.IMultiServiceContractConnection
- Direction
- Extensions uses Interfaces, so a change to Interfaces can break Extensions, while a change to Extensions can't break Interfaces.
- Position
- Below the diagonal: Extensions uses a module listed above it, which is the healthy direction.
20→12 Extensions uses MQContract✕
- Connections
- 3 pairs of types, where a type in Extensions uses a type in MQContract.
- The types involved
MQContract.Extensions.ContractedConnectionExtensions→MQContract.MQContractMessageContextMQContract.Extensions.MappedConnectionExtensions→MQContract.MQContractMessageContextMQContract.Extensions.MultiServiceConnectionExtensions→MQContract.MQContractMessageContext
- Direction
- Extensions uses MQContract, so a change to MQContract can break Extensions, while a change to Extensions can't break MQContract.
- Position
- Below the diagonal: Extensions uses a module listed above it, which is the healthy direction.
21→2 Factories uses Interfaces.Encoding✕
- Connections
- 1 pair of types, where a type in Factories uses a type in Interfaces.Encoding.
- The types involved
MQContract.Factories.MessageTypeFactory→MQContract.Interfaces.Encoding.IMessageEncoder
- Direction
- Factories uses Interfaces.Encoding, so a change to Interfaces.Encoding can break Factories, while a change to Factories can't break Interfaces.Encoding.
- Position
- Below the diagonal: Factories uses a module listed above it, which is the healthy direction.
21→3 Factories uses Interfaces.Messages✕
- Connections
- 1 pair of types, where a type in Factories uses a type in Interfaces.Messages.
- The types involved
MQContract.Factories.MessageTypeFactory→MQContract.Interfaces.Messages.IEncodedMessage
- Direction
- Factories uses Interfaces.Messages, so a change to Interfaces.Messages can break Factories, while a change to Factories can't break Interfaces.Messages.
- Position
- Below the diagonal: Factories uses a module listed above it, which is the healthy direction.
21→4 Factories uses Messages✕
- Connections
- 2 pairs of types, where a type in Factories uses a type in Messages.
- The types involved
MQContract.Factories.MessageTypeFactory→MQContract.Messages.MessageHeaderMQContract.Factories.MessageTypeFactory→MQContract.Messages.ServiceMessage
- Direction
- Factories uses Messages, so a change to Messages can break Factories, while a change to Factories can't break Messages.
- Position
- Below the diagonal: Factories uses a module listed above it, which is the healthy direction.
21→6 Factories uses Interfaces.Factories✕
- Connections
- 1 pair of types, where a type in Factories uses a type in Interfaces.Factories.
- The types involved
MQContract.Factories.MessageTypeFactory→MQContract.Interfaces.Factories.IMessageFactory
- Direction
- Factories uses Interfaces.Factories, so a change to Interfaces.Factories can break Factories, while a change to Factories can't break Interfaces.Factories.
- Position
- Below the diagonal: Factories uses a module listed above it, which is the healthy direction.
21→12 Factories uses MQContract✕
- Connections
- 1 pair of types, where a type in Factories uses a type in MQContract.
- The types involved
MQContract.Factories.MessageTypeFactory→MQContract.MessageContext
- Direction
- Factories uses MQContract, so a change to MQContract can break Factories, while a change to Factories can't break MQContract.
- Position
- Below the diagonal: Factories uses a module listed above it, which is the healthy direction.
22→4 GooglePubSub uses Messages✕
- Connections
- 5 pairs of types, where a type in GooglePubSub uses a type in Messages.
- The types involved
MQContract.GooglePubSub.Connection→MQContract.Messages.PingResultMQContract.GooglePubSub.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.GooglePubSub.Connection→MQContract.Messages.ServiceMessageMQContract.GooglePubSub.Connection→MQContract.Messages.TransmissionResultMQContract.GooglePubSub.Subscription→MQContract.Messages.ReceivedServiceMessage
- Direction
- GooglePubSub uses Messages, so a change to Messages can break GooglePubSub, while a change to GooglePubSub can't break Messages.
- Position
- Below the diagonal: GooglePubSub uses a module listed above it, which is the healthy direction.
22→8 GooglePubSub uses Interfaces.Service✕
- Connections
- 2 pairs of types, where a type in GooglePubSub uses a type in Interfaces.Service.
- The types involved
MQContract.GooglePubSub.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.GooglePubSub.Connection→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- GooglePubSub uses Interfaces.Service, so a change to Interfaces.Service can break GooglePubSub, while a change to GooglePubSub can't break Interfaces.Service.
- Position
- Below the diagonal: GooglePubSub uses a module listed above it, which is the healthy direction.
22→12 GooglePubSub uses MQContract✕
- Connections
- 2 pairs of types, where a type in GooglePubSub uses a type in MQContract.
- The types involved
MQContract.GooglePubSub.Connection→MQContract.BatchedMessageStreamMQContract.GooglePubSub.Subscription→MQContract.BaseLoopSubscription
- Direction
- GooglePubSub uses MQContract, so a change to MQContract can break GooglePubSub, while a change to GooglePubSub can't break MQContract.
- Position
- Below the diagonal: GooglePubSub uses a module listed above it, which is the healthy direction.
23→4 HiveMQ uses Messages✕
- Connections
- 5 pairs of types, where a type in HiveMQ uses a type in Messages.
- The types involved
MQContract.HiveMQ.Connection→MQContract.Messages.PingResultMQContract.HiveMQ.Connection→MQContract.Messages.ReceivedInboxServiceMessageMQContract.HiveMQ.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.HiveMQ.Connection→MQContract.Messages.ServiceMessageMQContract.HiveMQ.Connection→MQContract.Messages.TransmissionResult
- Direction
- HiveMQ uses Messages, so a change to Messages can break HiveMQ, while a change to HiveMQ can't break Messages.
- Position
- Below the diagonal: HiveMQ uses a module listed above it, which is the healthy direction.
23→8 HiveMQ uses Interfaces.Service✕
- Connections
- 4 pairs of types, where a type in HiveMQ uses a type in Interfaces.Service.
- The types involved
MQContract.HiveMQ.Connection→MQContract.Interfaces.Service.IInboxQueryableMessageServiceConnectionMQContract.HiveMQ.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.HiveMQ.Connection→MQContract.Interfaces.Service.IServiceSubscriptionMQContract.HiveMQ.Subscription→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- HiveMQ uses Interfaces.Service, so a change to Interfaces.Service can break HiveMQ, while a change to HiveMQ can't break Interfaces.Service.
- Position
- Below the diagonal: HiveMQ uses a module listed above it, which is the healthy direction.
23→12 HiveMQ uses MQContract✕
- Connections
- 1 pair of types, where a type in HiveMQ uses a type in MQContract.
- The types involved
MQContract.HiveMQ.Connection→MQContract.BatchedMessageStream
- Direction
- HiveMQ uses MQContract, so a change to MQContract can break HiveMQ, while a change to HiveMQ can't break MQContract.
- Position
- Below the diagonal: HiveMQ uses a module listed above it, which is the healthy direction.
24→4 InMemory uses Messages✕
- Connections
- 11 pairs of types, where a type in InMemory uses a type in Messages.
- The types involved
MQContract.InMemory.Connection→MQContract.Messages.PingResultMQContract.InMemory.Connection→MQContract.Messages.ReceivedInboxServiceMessageMQContract.InMemory.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.InMemory.Connection→MQContract.Messages.ServiceMessageMQContract.InMemory.Connection→MQContract.Messages.TransmissionResultMQContract.InMemory.InternalServiceMessage→MQContract.Messages.MessageHeaderMQContract.InMemory.InternalServiceMessage→MQContract.Messages.ServiceMessageMQContract.InMemory.MessageChannel→MQContract.Messages.ReceivedInboxServiceMessageMQContract.InMemory.MessageChannel→MQContract.Messages.ReceivedServiceMessageMQContract.InMemory.MessageChannel→MQContract.Messages.ServiceMessageMQContract.InMemory.MessageChannel→MQContract.Messages.TransmissionResult
- Direction
- InMemory uses Messages, so a change to Messages can break InMemory, while a change to InMemory can't break Messages.
- Position
- Below the diagonal: InMemory uses a module listed above it, which is the healthy direction.
24→8 InMemory uses Interfaces.Service✕
- Connections
- 5 pairs of types, where a type in InMemory uses a type in Interfaces.Service.
- The types involved
MQContract.InMemory.Connection→MQContract.Interfaces.Service.IInboxQueryableMessageServiceConnectionMQContract.InMemory.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.InMemory.Connection→MQContract.Interfaces.Service.IServiceSubscriptionMQContract.InMemory.MessageChannel→MQContract.Interfaces.Service.IServiceSubscriptionMQContract.InMemory.Subscription→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- InMemory uses Interfaces.Service, so a change to Interfaces.Service can break InMemory, while a change to InMemory can't break Interfaces.Service.
- Position
- Below the diagonal: InMemory uses a module listed above it, which is the healthy direction.
24→12 InMemory uses MQContract✕
- Connections
- 1 pair of types, where a type in InMemory uses a type in MQContract.
- The types involved
MQContract.InMemory.Connection→MQContract.BatchedMessageStream
- Direction
- InMemory uses MQContract, so a change to MQContract can break InMemory, while a change to InMemory can't break MQContract.
- Position
- Below the diagonal: InMemory uses a module listed above it, which is the healthy direction.
25→4 Interfaces.Consumers uses Messages✕
- Connections
- 4 pairs of types, where a type in Interfaces.Consumers uses a type in Messages.
- The types involved
MQContract.Interfaces.Consumers.IHeaderFilteredConsumer→MQContract.Messages.MessageHeaderMQContract.Interfaces.Consumers.IMessageFilteredConsumer→MQContract.Messages.MessageHeaderMQContract.Interfaces.Consumers.IQueryResponseAsyncConsumer→MQContract.Messages.QueryResponseMessageMQContract.Interfaces.Consumers.IQueryResponseConsumer→MQContract.Messages.QueryResponseMessage
- Direction
- Interfaces.Consumers uses Messages, so a change to Messages can break Interfaces.Consumers, while a change to Interfaces.Consumers can't break Messages.
- Position
- Below the diagonal: Interfaces.Consumers uses a module listed above it, which is the healthy direction.
25→9 Interfaces.Consumers uses Interfaces✕
- Connections
- 4 pairs of types, where a type in Interfaces.Consumers uses a type in Interfaces.
- The types involved
MQContract.Interfaces.Consumers.IPubSubAsyncConsumer→MQContract.Interfaces.IReceivedMessageMQContract.Interfaces.Consumers.IPubSubConsumer→MQContract.Interfaces.IReceivedMessageMQContract.Interfaces.Consumers.IQueryResponseAsyncConsumer→MQContract.Interfaces.IReceivedMessageMQContract.Interfaces.Consumers.IQueryResponseConsumer→MQContract.Interfaces.IReceivedMessage
- Direction
- Interfaces.Consumers uses Interfaces, so a change to Interfaces can break Interfaces.Consumers, while a change to Interfaces.Consumers can't break Interfaces.
- Position
- Below the diagonal: Interfaces.Consumers uses a module listed above it, which is the healthy direction.
25→12 Interfaces.Consumers uses MQContract✕
- Connections
- 2 pairs of types, where a type in Interfaces.Consumers uses a type in MQContract.
- The types involved
MQContract.Interfaces.Consumers.IHeaderFilteredConsumer→MQContract.MessageFilterResultMQContract.Interfaces.Consumers.IMessageFilteredConsumer→MQContract.MessageFilterResult
- Direction
- Interfaces.Consumers uses MQContract, so a change to MQContract can break Interfaces.Consumers, while a change to Interfaces.Consumers can't break MQContract.
- Position
- Below the diagonal: Interfaces.Consumers uses a module listed above it, which is the healthy direction.
26→4 Kafka uses Messages✕
- Connections
- 6 pairs of types, where a type in Kafka uses a type in Messages.
- The types involved
MQContract.Kafka.Connection→MQContract.Messages.MessageHeaderMQContract.Kafka.Connection→MQContract.Messages.PingResultMQContract.Kafka.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.Kafka.Connection→MQContract.Messages.ServiceMessageMQContract.Kafka.Connection→MQContract.Messages.TransmissionResultMQContract.Kafka.Subscription→MQContract.Messages.ReceivedServiceMessage
- Direction
- Kafka uses Messages, so a change to Messages can break Kafka, while a change to Kafka can't break Messages.
- Position
- Below the diagonal: Kafka uses a module listed above it, which is the healthy direction.
26→8 Kafka uses Interfaces.Service✕
- Connections
- 2 pairs of types, where a type in Kafka uses a type in Interfaces.Service.
- The types involved
MQContract.Kafka.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.Kafka.Connection→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- Kafka uses Interfaces.Service, so a change to Interfaces.Service can break Kafka, while a change to Kafka can't break Interfaces.Service.
- Position
- Below the diagonal: Kafka uses a module listed above it, which is the healthy direction.
26→12 Kafka uses MQContract✕
- Connections
- 2 pairs of types, where a type in Kafka uses a type in MQContract.
- The types involved
MQContract.Kafka.Connection→MQContract.BatchedMessageStreamMQContract.Kafka.Subscription→MQContract.BaseLoopSubscription
- Direction
- Kafka uses MQContract, so a change to MQContract can break Kafka, while a change to Kafka can't break MQContract.
- Position
- Below the diagonal: Kafka uses a module listed above it, which is the healthy direction.
27→9 Middleware.Metrics uses Interfaces✕
- Connections
- 3 pairs of types, where a type in Middleware.Metrics uses a type in Interfaces.
- The types involved
MQContract.Middleware.Metrics.ContractMetric→MQContract.Interfaces.IContractMetricMQContract.Middleware.Metrics.InternalMetricTracker→MQContract.Interfaces.IContractMetricMQContract.Middleware.Metrics.ReadonlyContractMetric→MQContract.Interfaces.IContractMetric
- Direction
- Middleware.Metrics uses Interfaces, so a change to Interfaces can break Middleware.Metrics, while a change to Middleware.Metrics can't break Interfaces.
- Position
- Below the diagonal: Middleware.Metrics uses a module listed above it, which is the healthy direction.
27→12 Middleware.Metrics uses MQContract✕
- Connections
- 1 pair of types, where a type in Middleware.Metrics uses a type in MQContract.
- The types involved
MQContract.Middleware.Metrics.SystemMetricTracker→MQContract.MessageContext
- Direction
- Middleware.Metrics uses MQContract, so a change to MQContract can break Middleware.Metrics, while a change to Middleware.Metrics can't break MQContract.
- Position
- Below the diagonal: Middleware.Metrics uses a module listed above it, which is the healthy direction.
28→4 NATS uses Messages✕
- Connections
- 6 pairs of types, where a type in NATS uses a type in Messages.
- The types involved
MQContract.NATS.Connection→MQContract.Messages.MessageHeaderMQContract.NATS.Connection→MQContract.Messages.PingResultMQContract.NATS.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.NATS.Connection→MQContract.Messages.ServiceMessageMQContract.NATS.Connection→MQContract.Messages.ServiceQueryResultMQContract.NATS.Connection→MQContract.Messages.TransmissionResult
- Direction
- NATS uses Messages, so a change to Messages can break NATS, while a change to NATS can't break Messages.
- Position
- Below the diagonal: NATS uses a module listed above it, which is the healthy direction.
28→8 NATS uses Interfaces.Service✕
- Connections
- 3 pairs of types, where a type in NATS uses a type in Interfaces.Service.
- The types involved
MQContract.NATS.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.NATS.Connection→MQContract.Interfaces.Service.IQueryResponseMessageServiceConnectionMQContract.NATS.Connection→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- NATS uses Interfaces.Service, so a change to Interfaces.Service can break NATS, while a change to NATS can't break Interfaces.Service.
- Position
- Below the diagonal: NATS uses a module listed above it, which is the healthy direction.
28→12 NATS uses MQContract✕
- Connections
- 1 pair of types, where a type in NATS uses a type in MQContract.
- The types involved
MQContract.NATS.Connection→MQContract.BatchedMessageStream
- Direction
- NATS uses MQContract, so a change to MQContract can break NATS, while a change to NATS can't break MQContract.
- Position
- Below the diagonal: NATS uses a module listed above it, which is the healthy direction.
29→4 RabbitMQ uses Messages✕
- Connections
- 5 pairs of types, where a type in RabbitMQ uses a type in Messages.
- The types involved
MQContract.RabbitMQ.Connection→MQContract.Messages.PingResultMQContract.RabbitMQ.Connection→MQContract.Messages.ReceivedInboxServiceMessageMQContract.RabbitMQ.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.RabbitMQ.Connection→MQContract.Messages.ServiceMessageMQContract.RabbitMQ.Connection→MQContract.Messages.TransmissionResult
- Direction
- RabbitMQ uses Messages, so a change to Messages can break RabbitMQ, while a change to RabbitMQ can't break Messages.
- Position
- Below the diagonal: RabbitMQ uses a module listed above it, which is the healthy direction.
29→8 RabbitMQ uses Interfaces.Service✕
- Connections
- 4 pairs of types, where a type in RabbitMQ uses a type in Interfaces.Service.
- The types involved
MQContract.RabbitMQ.Connection→MQContract.Interfaces.Service.IInboxQueryableMessageServiceConnectionMQContract.RabbitMQ.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.RabbitMQ.Connection→MQContract.Interfaces.Service.IServiceSubscriptionMQContract.RabbitMQ.Subscription→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- RabbitMQ uses Interfaces.Service, so a change to Interfaces.Service can break RabbitMQ, while a change to RabbitMQ can't break Interfaces.Service.
- Position
- Below the diagonal: RabbitMQ uses a module listed above it, which is the healthy direction.
29→12 RabbitMQ uses MQContract✕
- Connections
- 1 pair of types, where a type in RabbitMQ uses a type in MQContract.
- The types involved
MQContract.RabbitMQ.Connection→MQContract.BatchedMessageStream
- Direction
- RabbitMQ uses MQContract, so a change to MQContract can break RabbitMQ, while a change to RabbitMQ can't break MQContract.
- Position
- Below the diagonal: RabbitMQ uses a module listed above it, which is the healthy direction.
30→4 Redis uses Messages✕
- Connections
- 5 pairs of types, where a type in Redis uses a type in Messages.
- The types involved
MQContract.Redis.Connection→MQContract.Messages.PingResultMQContract.Redis.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.Redis.Connection→MQContract.Messages.ServiceMessageMQContract.Redis.Connection→MQContract.Messages.ServiceQueryResultMQContract.Redis.Connection→MQContract.Messages.TransmissionResult
- Direction
- Redis uses Messages, so a change to Messages can break Redis, while a change to Redis can't break Messages.
- Position
- Below the diagonal: Redis uses a module listed above it, which is the healthy direction.
30→8 Redis uses Interfaces.Service✕
- Connections
- 3 pairs of types, where a type in Redis uses a type in Interfaces.Service.
- The types involved
MQContract.Redis.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.Redis.Connection→MQContract.Interfaces.Service.IQueryResponseMessageServiceConnectionMQContract.Redis.Connection→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- Redis uses Interfaces.Service, so a change to Interfaces.Service can break Redis, while a change to Redis can't break Interfaces.Service.
- Position
- Below the diagonal: Redis uses a module listed above it, which is the healthy direction.
30→12 Redis uses MQContract✕
- Connections
- 1 pair of types, where a type in Redis uses a type in MQContract.
- The types involved
MQContract.Redis.Connection→MQContract.BatchedMessageStream
- Direction
- Redis uses MQContract, so a change to MQContract can break Redis, while a change to Redis can't break MQContract.
- Position
- Below the diagonal: Redis uses a module listed above it, which is the healthy direction.
31→4 ZeroMQ uses Messages✕
- Connections
- 9 pairs of types, where a type in ZeroMQ uses a type in Messages.
- The types involved
MQContract.ZeroMQ.Connection→MQContract.Messages.ErrorMessageMQContract.ZeroMQ.Connection→MQContract.Messages.PingResultMQContract.ZeroMQ.Connection→MQContract.Messages.ReceivedInboxServiceMessageMQContract.ZeroMQ.Connection→MQContract.Messages.ReceivedServiceMessageMQContract.ZeroMQ.Connection→MQContract.Messages.ServiceMessageMQContract.ZeroMQ.Connection→MQContract.Messages.TransmissionResultMQContract.ZeroMQ.MessageMapper→MQContract.Messages.ReceivedInboxServiceMessageMQContract.ZeroMQ.MessageMapper→MQContract.Messages.ServiceMessageMQContract.ZeroMQ.Subscription→MQContract.Messages.ReceivedInboxServiceMessage
- Direction
- ZeroMQ uses Messages, so a change to Messages can break ZeroMQ, while a change to ZeroMQ can't break Messages.
- Position
- Below the diagonal: ZeroMQ uses a module listed above it, which is the healthy direction.
31→8 ZeroMQ uses Interfaces.Service✕
- Connections
- 4 pairs of types, where a type in ZeroMQ uses a type in Interfaces.Service.
- The types involved
MQContract.ZeroMQ.Connection→MQContract.Interfaces.Service.IInboxQueryableMessageServiceConnectionMQContract.ZeroMQ.Connection→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.ZeroMQ.Connection→MQContract.Interfaces.Service.IServiceSubscriptionMQContract.ZeroMQ.Subscription→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- ZeroMQ uses Interfaces.Service, so a change to Interfaces.Service can break ZeroMQ, while a change to ZeroMQ can't break Interfaces.Service.
- Position
- Below the diagonal: ZeroMQ uses a module listed above it, which is the healthy direction.
31→12 ZeroMQ uses MQContract✕
- Connections
- 1 pair of types, where a type in ZeroMQ uses a type in MQContract.
- The types involved
MQContract.ZeroMQ.Connection→MQContract.BatchedMessageStream
- Direction
- ZeroMQ uses MQContract, so a change to MQContract can break ZeroMQ, while a change to ZeroMQ can't break MQContract.
- Position
- Below the diagonal: ZeroMQ uses a module listed above it, which is the healthy direction.
32→4 CQRS.Consumers uses Messages✕
- Connections
- 2 pairs of types, where a type in CQRS.Consumers uses a type in Messages.
- The types involved
MQContract.CQRS.Consumers.CommandResponseConsumer→MQContract.Messages.QueryResponseMessageMQContract.CQRS.Consumers.QueryResponseConsumer→MQContract.Messages.QueryResponseMessage
- Direction
- CQRS.Consumers uses Messages, so a change to Messages can break CQRS.Consumers, while a change to CQRS.Consumers can't break Messages.
- Position
- Below the diagonal: CQRS.Consumers uses a module listed above it, which is the healthy direction.
32→9 CQRS.Consumers uses Interfaces✕
- Connections
- 4 pairs of types, where a type in CQRS.Consumers uses a type in Interfaces.
- The types involved
MQContract.CQRS.Consumers.CancellationRequestConsumer→MQContract.Interfaces.IReceivedMessageMQContract.CQRS.Consumers.CommandConsumer→MQContract.Interfaces.IReceivedMessageMQContract.CQRS.Consumers.CommandResponseConsumer→MQContract.Interfaces.IReceivedMessageMQContract.CQRS.Consumers.QueryResponseConsumer→MQContract.Interfaces.IReceivedMessage
- Direction
- CQRS.Consumers uses Interfaces, so a change to Interfaces can break CQRS.Consumers, while a change to CQRS.Consumers can't break Interfaces.
- Position
- Below the diagonal: CQRS.Consumers uses a module listed above it, which is the healthy direction.
32→17 CQRS.Consumers uses CQRS.Interfaces.Command✕
- Connections
- 2 pairs of types, where a type in CQRS.Consumers uses a type in CQRS.Interfaces.Command.
- The types involved
MQContract.CQRS.Consumers.CommandConsumer→MQContract.CQRS.Interfaces.Command.ICommandProcessorMQContract.CQRS.Consumers.CommandResponseConsumer→MQContract.CQRS.Interfaces.Command.ICommandProcessor
- Direction
- CQRS.Consumers uses CQRS.Interfaces.Command, so a change to CQRS.Interfaces.Command can break CQRS.Consumers, while a change to CQRS.Consumers can't break CQRS.Interfaces.Command.
- Position
- Below the diagonal: CQRS.Consumers uses a module listed above it, which is the healthy direction.
32→18 CQRS.Consumers uses CQRS.Interfaces.Query✕
- Connections
- 1 pair of types, where a type in CQRS.Consumers uses a type in CQRS.Interfaces.Query.
- The types involved
MQContract.CQRS.Consumers.QueryResponseConsumer→MQContract.CQRS.Interfaces.Query.IQueryProcessor
- Direction
- CQRS.Consumers uses CQRS.Interfaces.Query, so a change to CQRS.Interfaces.Query can break CQRS.Consumers, while a change to CQRS.Consumers can't break CQRS.Interfaces.Query.
- Position
- Below the diagonal: CQRS.Consumers uses a module listed above it, which is the healthy direction.
32→25 CQRS.Consumers uses Interfaces.Consumers✕
- Connections
- 4 pairs of types, where a type in CQRS.Consumers uses a type in Interfaces.Consumers.
- The types involved
MQContract.CQRS.Consumers.CancellationRequestConsumer→MQContract.Interfaces.Consumers.IPubSubAsyncConsumerMQContract.CQRS.Consumers.CommandConsumer→MQContract.Interfaces.Consumers.IPubSubAsyncConsumerMQContract.CQRS.Consumers.CommandResponseConsumer→MQContract.Interfaces.Consumers.IQueryResponseAsyncConsumerMQContract.CQRS.Consumers.QueryResponseConsumer→MQContract.Interfaces.Consumers.IQueryResponseAsyncConsumer
- Direction
- CQRS.Consumers uses Interfaces.Consumers, so a change to Interfaces.Consumers can break CQRS.Consumers, while a change to CQRS.Consumers can't break Interfaces.Consumers.
- Position
- Below the diagonal: CQRS.Consumers uses a module listed above it, which is the healthy direction.
32→36 CQRS.Consumers uses CQRS part of a loop✕
- Connections
- 4 pairs of types, where a type in CQRS.Consumers uses a type in CQRS.
- The types involved
MQContract.CQRS.Consumers.CancellationRequestConsumer→MQContract.CQRS.CancellationRequestMQContract.CQRS.Consumers.CommandConsumer→MQContract.CQRS.CqrsConnectionMQContract.CQRS.Consumers.CommandResponseConsumer→MQContract.CQRS.CqrsConnectionMQContract.CQRS.Consumers.QueryResponseConsumer→MQContract.CQRS.CqrsConnection
- Direction
- CQRS.Consumers uses CQRS, so a change to CQRS can break CQRS.Consumers, while a change to CQRS.Consumers can't break CQRS.
- 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.
33→4 Middleware uses Messages✕
- Connections
- 7 pairs of types, where a type in Middleware uses a type in Messages.
- The types involved
MQContract.Middleware.CompressionMiddleware→MQContract.Messages.ServiceMessageMQContract.Middleware.EncryptionMiddleware→MQContract.Messages.ServiceMessageMQContract.Middleware.MetricsMiddleware→MQContract.Messages.ServiceMessageMQContract.Middleware.NonEncryptor→MQContract.Messages.MessageHeaderMQContract.Middleware.OpenTelemetryMiddleware→MQContract.Messages.MessageHeaderMQContract.Middleware.OpenTelemetryMiddleware→MQContract.Messages.ServiceMessageMQContract.Middleware.OpenTelemetryMiddleware→MQContract.Messages.TransmissionResult
- Direction
- Middleware uses Messages, so a change to Messages can break Middleware, while a change to Middleware can't break Messages.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
33→5 Middleware uses Interfaces.Encrypting✕
- Connections
- 4 pairs of types, where a type in Middleware uses a type in Interfaces.Encrypting.
- The types involved
MQContract.Middleware.EncryptionMiddleware→MQContract.Interfaces.Encrypting.IMessageEncryptorMQContract.Middleware.MiddlewareCollection→MQContract.Interfaces.Encrypting.IMessageEncryptorMQContract.Middleware.NonEncryptor→MQContract.Interfaces.Encrypting.EncryptionResultMQContract.Middleware.NonEncryptor→MQContract.Interfaces.Encrypting.IMessageEncryptor
- Direction
- Middleware uses Interfaces.Encrypting, so a change to Interfaces.Encrypting can break Middleware, while a change to Middleware can't break Interfaces.Encrypting.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
33→7 Middleware uses Interfaces.Middleware✕
- Connections
- 29 pairs of types, where a type in Middleware uses a type in Interfaces.Middleware. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
MQContract.Middleware.ChannelMappingMiddleware→MQContract.Interfaces.Middleware.EncodableMessageMQContract.Middleware.ChannelMappingMiddleware→MQContract.Interfaces.Middleware.IBeforeEncodeMiddlewareMQContract.Middleware.ChannelMappingMiddleware→MQContract.Interfaces.Middleware.IContextMQContract.Middleware.CompressionMiddleware→MQContract.Interfaces.Middleware.DecodableMessageMQContract.Middleware.CompressionMiddleware→MQContract.Interfaces.Middleware.IAfterEncodeMiddlewareMQContract.Middleware.CompressionMiddleware→MQContract.Interfaces.Middleware.IBeforeDecodeMiddlewareMQContract.Middleware.CompressionMiddleware→MQContract.Interfaces.Middleware.IContextMQContract.Middleware.Context→MQContract.Interfaces.Middleware.IContextMQContract.Middleware.EncryptionMiddleware→MQContract.Interfaces.Middleware.DecodableMessageMQContract.Middleware.EncryptionMiddleware→MQContract.Interfaces.Middleware.IAfterEncodeMiddlewareMQContract.Middleware.EncryptionMiddleware→MQContract.Interfaces.Middleware.IBeforeDecodeMiddlewareMQContract.Middleware.EncryptionMiddleware→MQContract.Interfaces.Middleware.IContextMQContract.Middleware.MetricsMiddleware→MQContract.Interfaces.Middleware.DecodableMessageMQContract.Middleware.MetricsMiddleware→MQContract.Interfaces.Middleware.DecodedMessageMQContract.Middleware.MetricsMiddleware→MQContract.Interfaces.Middleware.EncodableMessageMQContract.Middleware.MetricsMiddleware→MQContract.Interfaces.Middleware.IAfterDecodeMiddlewareMQContract.Middleware.MetricsMiddleware→MQContract.Interfaces.Middleware.IAfterEncodeMiddlewareMQContract.Middleware.MetricsMiddleware→MQContract.Interfaces.Middleware.IBeforeDecodeMiddlewareMQContract.Middleware.MetricsMiddleware→MQContract.Interfaces.Middleware.IBeforeEncodeMiddlewareMQContract.Middleware.MetricsMiddleware→MQContract.Interfaces.Middleware.IContextMQContract.Middleware.MiddlewareCollection→MQContract.Interfaces.Middleware.IMiddlewareMQContract.Middleware.OpenTelemetryMiddleware→MQContract.Interfaces.Middleware.DecodableMessageMQContract.Middleware.OpenTelemetryMiddleware→MQContract.Interfaces.Middleware.DecodedMessageMQContract.Middleware.OpenTelemetryMiddleware→MQContract.Interfaces.Middleware.EncodableMessageMQContract.Middleware.OpenTelemetryMiddleware→MQContract.Interfaces.Middleware.IAfterDecodeMiddleware
- Direction
- Middleware uses Interfaces.Middleware, so a change to Interfaces.Middleware can break Middleware, while a change to Middleware can't break Interfaces.Middleware.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
33→8 Middleware uses Interfaces.Service✕
- Connections
- 1 pair of types, where a type in Middleware uses a type in Interfaces.Service.
- The types involved
MQContract.Middleware.OpenTelemetryMiddleware→MQContract.Interfaces.Service.IMessageServiceConnection
- Direction
- Middleware uses Interfaces.Service, so a change to Interfaces.Service can break Middleware, while a change to Middleware can't break Interfaces.Service.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
33→9 Middleware uses Interfaces✕
- Connections
- 1 pair of types, where a type in Middleware uses a type in Interfaces.
- The types involved
MQContract.Middleware.MetricsMiddleware→MQContract.Interfaces.IContractMetric
- Direction
- Middleware uses Interfaces, so a change to Interfaces can break Middleware, while a change to Middleware can't break Interfaces.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
33→12 Middleware uses MQContract✕
- Connections
- 7 pairs of types, where a type in Middleware uses a type in MQContract.
- The types involved
MQContract.Middleware.ChannelMappingMiddleware→MQContract.ChannelMapperMQContract.Middleware.Context→MQContract.MapTypesMQContract.Middleware.EncryptionMiddleware→MQContract.MessageContextMQContract.Middleware.MetricsMiddleware→MQContract.MessageContextMQContract.Middleware.MiddlewareCollection→MQContract.ChannelMapperMQContract.Middleware.MiddlewareCollection→MQContract.MQContractMessageContextMQContract.Middleware.MiddlewareCollection→MQContract.MessageContext
- Direction
- Middleware uses MQContract, so a change to MQContract can break Middleware, while a change to Middleware can't break MQContract.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
33→27 Middleware uses Middleware.Metrics✕
- Connections
- 3 pairs of types, where a type in Middleware uses a type in Middleware.Metrics.
- The types involved
MQContract.Middleware.MetricsMiddleware→MQContract.Middleware.Metrics.InternalMetricTrackerMQContract.Middleware.MetricsMiddleware→MQContract.Middleware.Metrics.MetricEntryValueMQContract.Middleware.MetricsMiddleware→MQContract.Middleware.Metrics.SystemMetricTracker
- Direction
- Middleware uses Middleware.Metrics, so a change to Middleware.Metrics can break Middleware, while a change to Middleware can't break Middleware.Metrics.
- Position
- Below the diagonal: Middleware uses a module listed above it, which is the healthy direction.
34→4 CQRS.Interfaces uses Messages✕
- Connections
- 1 pair of types, where a type in CQRS.Interfaces uses a type in Messages.
- The types involved
MQContract.CQRS.Interfaces.IProcessorRegistrar→MQContract.Messages.MessageFilters
- Direction
- CQRS.Interfaces uses Messages, so a change to Messages can break CQRS.Interfaces, while a change to CQRS.Interfaces can't break Messages.
- Position
- Below the diagonal: CQRS.Interfaces uses a module listed above it, which is the healthy direction.
34→12 CQRS.Interfaces uses MQContract✕
- Connections
- 1 pair of types, where a type in CQRS.Interfaces uses a type in MQContract.
- The types involved
MQContract.CQRS.Interfaces.IContextFilteredProcessor→MQContract.MessageFilterResult
- Direction
- CQRS.Interfaces uses MQContract, so a change to MQContract can break CQRS.Interfaces, while a change to CQRS.Interfaces can't break MQContract.
- Position
- Below the diagonal: CQRS.Interfaces uses a module listed above it, which is the healthy direction.
34→17 CQRS.Interfaces uses CQRS.Interfaces.Command✕
- Connections
- 1 pair of types, where a type in CQRS.Interfaces uses a type in CQRS.Interfaces.Command.
- The types involved
MQContract.CQRS.Interfaces.ICQRSConnection→MQContract.CQRS.Interfaces.Command.ICommandProcessor
- Direction
- CQRS.Interfaces uses CQRS.Interfaces.Command, so a change to CQRS.Interfaces.Command can break CQRS.Interfaces, while a change to CQRS.Interfaces can't break CQRS.Interfaces.Command.
- Position
- Below the diagonal: CQRS.Interfaces uses a module listed above it, which is the healthy direction.
34→18 CQRS.Interfaces uses CQRS.Interfaces.Query✕
- Connections
- 1 pair of types, where a type in CQRS.Interfaces uses a type in CQRS.Interfaces.Query.
- The types involved
MQContract.CQRS.Interfaces.ICQRSConnection→MQContract.CQRS.Interfaces.Query.IQueryProcessor
- Direction
- CQRS.Interfaces uses CQRS.Interfaces.Query, so a change to CQRS.Interfaces.Query can break CQRS.Interfaces, while a change to CQRS.Interfaces can't break CQRS.Interfaces.Query.
- Position
- Below the diagonal: CQRS.Interfaces uses a module listed above it, which is the healthy direction.
34→32 CQRS.Interfaces uses CQRS.Consumers✕
- Connections
- 3 pairs of types, where a type in CQRS.Interfaces uses a type in CQRS.Consumers.
- The types involved
MQContract.CQRS.Interfaces.IProcessorRegistrar→MQContract.CQRS.Consumers.CommandConsumerMQContract.CQRS.Interfaces.IProcessorRegistrar→MQContract.CQRS.Consumers.CommandResponseConsumerMQContract.CQRS.Interfaces.IProcessorRegistrar→MQContract.CQRS.Consumers.QueryResponseConsumer
- Direction
- CQRS.Interfaces uses CQRS.Consumers, so a change to CQRS.Consumers can break CQRS.Interfaces, while a change to CQRS.Interfaces can't break CQRS.Consumers.
- Position
- Below the diagonal: CQRS.Interfaces uses a module listed above it, which is the healthy direction.
34→36 CQRS.Interfaces uses CQRS part of a loop✕
- Connections
- 2 pairs of types, where a type in CQRS.Interfaces uses a type in CQRS.
- The types involved
MQContract.CQRS.Interfaces.ICQRSConnection→MQContract.CQRS.ContextMQContract.CQRS.Interfaces.IContextFilteredProcessor→MQContract.CQRS.Context
- Direction
- CQRS.Interfaces uses CQRS, so a change to CQRS can break CQRS.Interfaces, while a change to CQRS.Interfaces can't break CQRS.
- 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.
35→2 Connections uses Interfaces.Encoding✕
- Connections
- 5 pairs of types, where a type in Connections uses a type in Interfaces.Encoding.
- The types involved
MQContract.Connections.AConnection→MQContract.Interfaces.Encoding.IMessageEncoderMQContract.Connections.AMappableConnection→MQContract.Interfaces.Encoding.IMessageEncoderMQContract.Connections.Connection→MQContract.Interfaces.Encoding.IMessageEncoderMQContract.Connections.MappedConnection→MQContract.Interfaces.Encoding.IMessageEncoderMQContract.Connections.MultiServiceConnection→MQContract.Interfaces.Encoding.IMessageEncoder
- Direction
- Connections uses Interfaces.Encoding, so a change to Interfaces.Encoding can break Connections, while a change to Connections can't break Interfaces.Encoding.
- Position
- Below the diagonal: Connections uses a module listed above it, which is the healthy direction.
35→4 Connections uses Messages✕
- Connections
- 44 pairs of types, where a type in Connections uses a type in Messages. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
MQContract.Connections.AConnection→MQContract.Messages.MessageFiltersMQContract.Connections.AConnection→MQContract.Messages.MessageHeaderMQContract.Connections.AConnection→MQContract.Messages.QueryResponseMessageMQContract.Connections.AConnection→MQContract.Messages.QueryResultMQContract.Connections.AConnection→MQContract.Messages.ReceivedServiceMessageMQContract.Connections.AConnection→MQContract.Messages.ServiceMessageMQContract.Connections.AConnection→MQContract.Messages.ServiceQueryResultMQContract.Connections.AConnection→MQContract.Messages.TransmissionMessageMQContract.Connections.AConnection→MQContract.Messages.TransmissionResultMQContract.Connections.AMappableConnection→MQContract.Messages.MessageHeaderMQContract.Connections.Connection→MQContract.Messages.MessageFiltersMQContract.Connections.Connection→MQContract.Messages.MessageHeaderMQContract.Connections.Connection→MQContract.Messages.PingResultMQContract.Connections.Connection→MQContract.Messages.QueryResponseMessageMQContract.Connections.Connection→MQContract.Messages.QueryResultMQContract.Connections.Connection→MQContract.Messages.TransmissionMessageMQContract.Connections.Connection→MQContract.Messages.TransmissionResultMQContract.Connections.ConnectionHealthCheck→MQContract.Messages.PingResultMQContract.Connections.DecodeServiceMessageResult→MQContract.Messages.MessageHeaderMQContract.Connections.FilteredServiceMessage→MQContract.Messages.ServiceMessageMQContract.Connections.InboxMessageResult→MQContract.Messages.ErrorMessageMQContract.Connections.InboxMessageResult→MQContract.Messages.ServiceQueryResultMQContract.Connections.MappedConnection→MQContract.Messages.MessageFiltersMQContract.Connections.MappedConnection→MQContract.Messages.MessageHeaderMQContract.Connections.MappedConnection→MQContract.Messages.PingResult
- Direction
- Connections uses Messages, so a change to Messages can break Connections, while a change to Connections can't break Messages.
- Position
- Below the diagonal: Connections uses a module listed above it, which is the healthy direction.
35→5 Connections uses Interfaces.Encrypting✕
- Connections
- 5 pairs of types, where a type in Connections uses a type in Interfaces.Encrypting.
- The types involved
MQContract.Connections.AConnection→MQContract.Interfaces.Encrypting.IMessageEncryptorMQContract.Connections.AMappableConnection→MQContract.Interfaces.Encrypting.IMessageEncryptorMQContract.Connections.Connection→MQContract.Interfaces.Encrypting.IMessageEncryptorMQContract.Connections.MappedConnection→MQContract.Interfaces.Encrypting.IMessageEncryptorMQContract.Connections.MultiServiceConnection→MQContract.Interfaces.Encrypting.IMessageEncryptor
- Direction
- Connections uses Interfaces.Encrypting, so a change to Interfaces.Encrypting can break Connections, while a change to Connections can't break Interfaces.Encrypting.
- Position
- Below the diagonal: Connections uses a module listed above it, which is the healthy direction.
35→6 Connections uses Interfaces.Factories✕
- Connections
- 2 pairs of types, where a type in Connections uses a type in Interfaces.Factories.
- The types involved
MQContract.Connections.AConnection→MQContract.Interfaces.Factories.IMessageFactoryMQContract.Connections.AConnection→MQContract.Interfaces.Factories.IMessageTypeFactory
- Direction
- Connections uses Interfaces.Factories, so a change to Interfaces.Factories can break Connections, while a change to Connections can't break Interfaces.Factories.
- Position
- Below the diagonal: Connections uses a module listed above it, which is the healthy direction.
35→7 Connections uses Interfaces.Middleware✕
- Connections
- 6 pairs of types, where a type in Connections uses a type in Interfaces.Middleware.
- The types involved
MQContract.Connections.AConnection→MQContract.Interfaces.Middleware.DecodableMessageMQContract.Connections.AConnection→MQContract.Interfaces.Middleware.DecodedMessageMQContract.Connections.AConnection→MQContract.Interfaces.Middleware.EncodableMessageMQContract.Connections.AConnection→MQContract.Interfaces.Middleware.IContextMQContract.Connections.AConnection→MQContract.Interfaces.Middleware.IMiddlewareMQContract.Connections.AConnection→MQContract.Interfaces.Middleware.ISpecificTypeMiddleware
- Direction
- Connections uses Interfaces.Middleware, so a change to Interfaces.Middleware can break Connections, while a change to Connections can't break Interfaces.Middleware.
- Position
- Below the diagonal: Connections uses a module listed above it, which is the healthy direction.
35→8 Connections uses Interfaces.Service✕
- Connections
- 11 pairs of types, where a type in Connections uses a type in Interfaces.Service.
- The types involved
MQContract.Connections.AConnection→MQContract.Interfaces.Service.IInboxQueryableMessageServiceConnectionMQContract.Connections.AConnection→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Connections.AConnection→MQContract.Interfaces.Service.IServiceSubscriptionMQContract.Connections.AMappableConnection→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Connections.Connection→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Connections.ConnectionHealthCheck→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Connections.ConnectionHealthCheck→MQContract.Interfaces.Service.IPingableMessageServiceConnectionMQContract.Connections.MultiServiceConnection→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Connections.ServiceConnection→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Connections.ServiceConnectionEntry→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Connections.ServiceConnectionList→MQContract.Interfaces.Service.IMessageServiceConnection
- Direction
- Connections uses Interfaces.Service, so a change to Interfaces.Service can break Connections, while a change to Connections can't break Interfaces.Service.
- Position
- Below the diagonal: Connections uses a module listed above it, which is the healthy direction.
35→9 Connections uses Interfaces✕
- Connections
- 15 pairs of types, where a type in Connections uses a type in Interfaces.
- The types involved
MQContract.Connections.AConnection→MQContract.Interfaces.IContractMetricMQContract.Connections.AConnection→MQContract.Interfaces.IInternalSubscriptionMQContract.Connections.AConnection→MQContract.Interfaces.IMetricContractConnectionMQContract.Connections.AConnection→MQContract.Interfaces.IReceivedMessageMQContract.Connections.AConnection→MQContract.Interfaces.ISubscriptionMQContract.Connections.AMappableConnection→MQContract.Interfaces.IMappableContractConnectionMQContract.Connections.Connection→MQContract.Interfaces.IContractedConnectionMQContract.Connections.Connection→MQContract.Interfaces.IReceivedMessageMQContract.Connections.Connection→MQContract.Interfaces.ISubscriptionMQContract.Connections.MappedConnection→MQContract.Interfaces.IMappedContractConnectionMQContract.Connections.MappedConnection→MQContract.Interfaces.IReceivedMessageMQContract.Connections.MappedConnection→MQContract.Interfaces.ISubscriptionMQContract.Connections.MultiServiceConnection→MQContract.Interfaces.IMultiServiceContractConnectionMQContract.Connections.MultiServiceConnection→MQContract.Interfaces.IReceivedMessageMQContract.Connections.MultiServiceConnection→MQContract.Interfaces.ISubscription
- Direction
- Connections uses Interfaces, so a change to Interfaces can break Connections, while a change to Connections can't break Interfaces.
- Position
- Below the diagonal: Connections uses a module listed above it, which is the healthy direction.
35→12 Connections uses MQContract✕
- Connections
- 12 pairs of types, where a type in Connections uses a type in MQContract.
- The types involved
MQContract.Connections.AConnection→MQContract.ChannelMapperMQContract.Connections.AConnection→MQContract.MQContractMessageContextMQContract.Connections.AConnection→MQContract.MapTypesMQContract.Connections.AConnection→MQContract.MessageContextMQContract.Connections.AMappableConnection→MQContract.ChannelMapperMQContract.Connections.AMappableConnection→MQContract.MapTypesMQContract.Connections.Connection→MQContract.ChannelMapperMQContract.Connections.DecodeServiceMessageResult→MQContract.MessageFilterResultMQContract.Connections.FilteredServiceMessage→MQContract.MessageFilterResultMQContract.Connections.MappedConnection→MQContract.ChannelMapperMQContract.Connections.MappedConnection→MQContract.MapTypesMQContract.Connections.MultiServiceConnection→MQContract.ChannelMapper
- Direction
- Connections uses MQContract, so a change to MQContract can break Connections, while a change to Connections can't break MQContract.
- Position
- Below the diagonal: Connections uses a module listed above it, which is the healthy direction.
35→33 Connections uses Middleware✕
- Connections
- 3 pairs of types, where a type in Connections uses a type in Middleware.
- The types involved
MQContract.Connections.AConnection→MQContract.Middleware.MetricsMiddlewareMQContract.Connections.AConnection→MQContract.Middleware.MiddlewareCollectionMQContract.Connections.AConnection→MQContract.Middleware.OpenTelemetryMiddleware
- Direction
- Connections uses Middleware, so a change to Middleware can break Connections, while a change to Connections can't break Middleware.
- Position
- Below the diagonal: Connections uses a module listed above it, which is the healthy direction.
36→4 CQRS uses Messages✕
- Connections
- 4 pairs of types, where a type in CQRS uses a type in Messages.
- The types involved
MQContract.CQRS.CommandCallException→MQContract.Messages.ErrorMessageMQContract.CQRS.Context→MQContract.Messages.MessageHeaderMQContract.CQRS.CqrsConnection→MQContract.Messages.MessageFiltersMQContract.CQRS.QueryCallException→MQContract.Messages.ErrorMessage
- Direction
- CQRS uses Messages, so a change to Messages can break CQRS, while a change to CQRS can't break Messages.
- Position
- Below the diagonal: CQRS uses a module listed above it, which is the healthy direction.
36→9 CQRS uses Interfaces✕
- Connections
- 1 pair of types, where a type in CQRS uses a type in Interfaces.
- The types involved
MQContract.CQRS.CqrsConnection→MQContract.Interfaces.IContractConnection
- Direction
- CQRS uses Interfaces, so a change to Interfaces can break CQRS, while a change to CQRS can't break Interfaces.
- Position
- Below the diagonal: CQRS uses a module listed above it, which is the healthy direction.
36→17 CQRS uses CQRS.Interfaces.Command✕
- Connections
- 1 pair of types, where a type in CQRS uses a type in CQRS.Interfaces.Command.
- The types involved
MQContract.CQRS.CqrsConnection→MQContract.CQRS.Interfaces.Command.ICommandProcessor
- Direction
- CQRS uses CQRS.Interfaces.Command, so a change to CQRS.Interfaces.Command can break CQRS, while a change to CQRS can't break CQRS.Interfaces.Command.
- Position
- Below the diagonal: CQRS uses a module listed above it, which is the healthy direction.
36→18 CQRS uses CQRS.Interfaces.Query✕
- Connections
- 1 pair of types, where a type in CQRS uses a type in CQRS.Interfaces.Query.
- The types involved
MQContract.CQRS.CqrsConnection→MQContract.CQRS.Interfaces.Query.IQueryProcessor
- Direction
- CQRS uses CQRS.Interfaces.Query, so a change to CQRS.Interfaces.Query can break CQRS, while a change to CQRS can't break CQRS.Interfaces.Query.
- Position
- Below the diagonal: CQRS uses a module listed above it, which is the healthy direction.
36→34 CQRS uses CQRS.Interfaces✕
- Connections
- 2 pairs of types, where a type in CQRS uses a type in CQRS.Interfaces.
- The types involved
MQContract.CQRS.CqrsConnection→MQContract.CQRS.Interfaces.ICQRSConnectionMQContract.CQRS.CqrsConnection→MQContract.CQRS.Interfaces.IProcessorRegistrar
- Direction
- CQRS uses CQRS.Interfaces, so a change to CQRS.Interfaces can break CQRS, while a change to CQRS can't break CQRS.Interfaces.
- Position
- Below the diagonal: CQRS uses a module listed above it, which is the healthy direction.
37→9 CQRS.Extensions uses Interfaces✕
- Connections
- 1 pair of types, where a type in CQRS.Extensions uses a type in Interfaces.
- The types involved
MQContract.CQRS.Extensions.IContractConnectionExtension→MQContract.Interfaces.IContractConnection
- Direction
- CQRS.Extensions uses Interfaces, so a change to Interfaces can break CQRS.Extensions, while a change to CQRS.Extensions can't break Interfaces.
- Position
- Below the diagonal: CQRS.Extensions uses a module listed above it, which is the healthy direction.
37→17 CQRS.Extensions uses CQRS.Interfaces.Command✕
- Connections
- 1 pair of types, where a type in CQRS.Extensions uses a type in CQRS.Interfaces.Command.
- The types involved
MQContract.CQRS.Extensions.ICQRSConnectionExtension→MQContract.CQRS.Interfaces.Command.ICommandProcessor
- Direction
- CQRS.Extensions uses CQRS.Interfaces.Command, so a change to CQRS.Interfaces.Command can break CQRS.Extensions, while a change to CQRS.Extensions can't break CQRS.Interfaces.Command.
- Position
- Below the diagonal: CQRS.Extensions uses a module listed above it, which is the healthy direction.
37→18 CQRS.Extensions uses CQRS.Interfaces.Query✕
- Connections
- 1 pair of types, where a type in CQRS.Extensions uses a type in CQRS.Interfaces.Query.
- The types involved
MQContract.CQRS.Extensions.ICQRSConnectionExtension→MQContract.CQRS.Interfaces.Query.IQueryProcessor
- Direction
- CQRS.Extensions uses CQRS.Interfaces.Query, so a change to CQRS.Interfaces.Query can break CQRS.Extensions, while a change to CQRS.Extensions can't break CQRS.Interfaces.Query.
- Position
- Below the diagonal: CQRS.Extensions uses a module listed above it, which is the healthy direction.
37→34 CQRS.Extensions uses CQRS.Interfaces✕
- Connections
- 2 pairs of types, where a type in CQRS.Extensions uses a type in CQRS.Interfaces.
- The types involved
MQContract.CQRS.Extensions.ICQRSConnectionExtension→MQContract.CQRS.Interfaces.ICQRSConnectionMQContract.CQRS.Extensions.IContractConnectionExtension→MQContract.CQRS.Interfaces.ICQRSConnection
- Direction
- CQRS.Extensions uses CQRS.Interfaces, so a change to CQRS.Interfaces can break CQRS.Extensions, while a change to CQRS.Extensions can't break CQRS.Interfaces.
- Position
- Below the diagonal: CQRS.Extensions uses a module listed above it, which is the healthy direction.
38→4 CQRS.Registrars uses Messages✕
- Connections
- 2 pairs of types, where a type in CQRS.Registrars uses a type in Messages.
- The types involved
MQContract.CQRS.Registrars.ContractedConnectionRegistrar→MQContract.Messages.MessageFiltersMQContract.CQRS.Registrars.MappedConnectionRegistrar→MQContract.Messages.MessageFilters
- Direction
- CQRS.Registrars uses Messages, so a change to Messages can break CQRS.Registrars, while a change to CQRS.Registrars can't break Messages.
- Position
- Below the diagonal: CQRS.Registrars uses a module listed above it, which is the healthy direction.
38→9 CQRS.Registrars uses Interfaces✕
- Connections
- 2 pairs of types, where a type in CQRS.Registrars uses a type in Interfaces.
- The types involved
MQContract.CQRS.Registrars.ContractedConnectionRegistrar→MQContract.Interfaces.IContractedConnectionMQContract.CQRS.Registrars.MappedConnectionRegistrar→MQContract.Interfaces.IMappedContractConnection
- Direction
- CQRS.Registrars uses Interfaces, so a change to Interfaces can break CQRS.Registrars, while a change to CQRS.Registrars can't break Interfaces.
- Position
- Below the diagonal: CQRS.Registrars uses a module listed above it, which is the healthy direction.
38→32 CQRS.Registrars uses CQRS.Consumers✕
- Connections
- 6 pairs of types, where a type in CQRS.Registrars uses a type in CQRS.Consumers.
- The types involved
MQContract.CQRS.Registrars.ContractedConnectionRegistrar→MQContract.CQRS.Consumers.CommandConsumerMQContract.CQRS.Registrars.ContractedConnectionRegistrar→MQContract.CQRS.Consumers.CommandResponseConsumerMQContract.CQRS.Registrars.ContractedConnectionRegistrar→MQContract.CQRS.Consumers.QueryResponseConsumerMQContract.CQRS.Registrars.MappedConnectionRegistrar→MQContract.CQRS.Consumers.CommandConsumerMQContract.CQRS.Registrars.MappedConnectionRegistrar→MQContract.CQRS.Consumers.CommandResponseConsumerMQContract.CQRS.Registrars.MappedConnectionRegistrar→MQContract.CQRS.Consumers.QueryResponseConsumer
- Direction
- CQRS.Registrars uses CQRS.Consumers, so a change to CQRS.Consumers can break CQRS.Registrars, while a change to CQRS.Registrars can't break CQRS.Consumers.
- Position
- Below the diagonal: CQRS.Registrars uses a module listed above it, which is the healthy direction.
38→34 CQRS.Registrars uses CQRS.Interfaces✕
- Connections
- 2 pairs of types, where a type in CQRS.Registrars uses a type in CQRS.Interfaces.
- The types involved
MQContract.CQRS.Registrars.ContractedConnectionRegistrar→MQContract.CQRS.Interfaces.IProcessorRegistrarMQContract.CQRS.Registrars.MappedConnectionRegistrar→MQContract.CQRS.Interfaces.IProcessorRegistrar
- Direction
- CQRS.Registrars uses CQRS.Interfaces, so a change to CQRS.Interfaces can break CQRS.Registrars, while a change to CQRS.Registrars can't break CQRS.Interfaces.
- Position
- Below the diagonal: CQRS.Registrars uses a module listed above it, which is the healthy direction.
39→4 Subscriptions uses Messages✕
- Connections
- 6 pairs of types, where a type in Subscriptions uses a type in Messages.
- The types involved
MQContract.Subscriptions.ProcessedServiceResponse→MQContract.Messages.ServiceMessageMQContract.Subscriptions.PubSubSubscription→MQContract.Messages.ReceivedServiceMessageMQContract.Subscriptions.QueryResponseHelper→MQContract.Messages.ReceivedServiceMessageMQContract.Subscriptions.QueryResponseHelper→MQContract.Messages.ServiceMessageMQContract.Subscriptions.QueryResponseHelper→MQContract.Messages.ServiceQueryResultMQContract.Subscriptions.QueryResponseSubscription→MQContract.Messages.ReceivedServiceMessage
- Direction
- Subscriptions uses Messages, so a change to Messages can break Subscriptions, while a change to Subscriptions can't break Messages.
- Position
- Below the diagonal: Subscriptions uses a module listed above it, which is the healthy direction.
39→8 Subscriptions uses Interfaces.Service✕
- Connections
- 4 pairs of types, where a type in Subscriptions uses a type in Interfaces.Service.
- The types involved
MQContract.Subscriptions.PubSubSubscription→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Subscriptions.QueryResponseHelper→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Subscriptions.QueryResponseSubscription→MQContract.Interfaces.Service.IMessageServiceConnectionMQContract.Subscriptions.SubscriptionBase→MQContract.Interfaces.Service.IServiceSubscription
- Direction
- Subscriptions uses Interfaces.Service, so a change to Interfaces.Service can break Subscriptions, while a change to Subscriptions can't break Interfaces.Service.
- Position
- Below the diagonal: Subscriptions uses a module listed above it, which is the healthy direction.
39→9 Subscriptions uses Interfaces✕
- Connections
- 2 pairs of types, where a type in Subscriptions uses a type in Interfaces.
- The types involved
MQContract.Subscriptions.SubscriptionBase→MQContract.Interfaces.IInternalSubscriptionMQContract.Subscriptions.SubscriptionCollection→MQContract.Interfaces.ISubscription
- Direction
- Subscriptions uses Interfaces, so a change to Interfaces can break Subscriptions, while a change to Subscriptions can't break Interfaces.
- Position
- Below the diagonal: Subscriptions uses a module listed above it, which is the healthy direction.
39→12 Subscriptions uses MQContract✕
- Connections
- 3 pairs of types, where a type in Subscriptions uses a type in MQContract.
- The types involved
MQContract.Subscriptions.PubSubSubscription→MQContract.MessageContextMQContract.Subscriptions.QueryResponseSubscription→MQContract.MessageContextMQContract.Subscriptions.SubscriptionBase→MQContract.MessageContext
- Direction
- Subscriptions uses MQContract, so a change to MQContract can break Subscriptions, while a change to Subscriptions can't break MQContract.
- Position
- Below the diagonal: Subscriptions uses a module listed above it, which is the healthy direction.
39→35 Subscriptions uses Connections✕
- Connections
- 1 pair of types, where a type in Subscriptions uses a type in Connections.
- The types involved
MQContract.Subscriptions.QueryResponseSubscription→MQContract.Connections.FilteredServiceMessage
- Direction
- Subscriptions uses Connections, so a change to Connections can break Subscriptions, while a change to Subscriptions can't break Connections.
- Position
- Below the diagonal: Subscriptions uses a module listed above it, which is the healthy direction.
40→9 CQRS.Contexts uses Interfaces✕
- Connections
- 3 pairs of types, where a type in CQRS.Contexts uses a type in Interfaces.
- The types involved
MQContract.CQRS.Contexts.AInvocationContext→MQContract.Interfaces.IReceivedMessageMQContract.CQRS.Contexts.CommandInvocationContext→MQContract.Interfaces.IReceivedMessageMQContract.CQRS.Contexts.QueryInvocationContext→MQContract.Interfaces.IReceivedMessage
- Direction
- CQRS.Contexts uses Interfaces, so a change to Interfaces can break CQRS.Contexts, while a change to CQRS.Contexts can't break Interfaces.
- Position
- Below the diagonal: CQRS.Contexts uses a module listed above it, which is the healthy direction.
40→17 CQRS.Contexts uses CQRS.Interfaces.Command✕
- Connections
- 1 pair of types, where a type in CQRS.Contexts uses a type in CQRS.Interfaces.Command.
- The types involved
MQContract.CQRS.Contexts.CommandInvocationContext→MQContract.CQRS.Interfaces.Command.ICommandInvocationContext
- Direction
- CQRS.Contexts uses CQRS.Interfaces.Command, so a change to CQRS.Interfaces.Command can break CQRS.Contexts, while a change to CQRS.Contexts can't break CQRS.Interfaces.Command.
- Position
- Below the diagonal: CQRS.Contexts uses a module listed above it, which is the healthy direction.
40→18 CQRS.Contexts uses CQRS.Interfaces.Query✕
- Connections
- 1 pair of types, where a type in CQRS.Contexts uses a type in CQRS.Interfaces.Query.
- The types involved
MQContract.CQRS.Contexts.QueryInvocationContext→MQContract.CQRS.Interfaces.Query.IQueryInvocationContext
- Direction
- CQRS.Contexts uses CQRS.Interfaces.Query, so a change to CQRS.Interfaces.Query can break CQRS.Contexts, while a change to CQRS.Contexts can't break CQRS.Interfaces.Query.
- Position
- Below the diagonal: CQRS.Contexts uses a module listed above it, which is the healthy direction.
40→34 CQRS.Contexts uses CQRS.Interfaces✕
- Connections
- 2 pairs of types, where a type in CQRS.Contexts uses a type in CQRS.Interfaces.
- The types involved
MQContract.CQRS.Contexts.AInvocationContext→MQContract.CQRS.Interfaces.ICQRSConnectionMQContract.CQRS.Contexts.AInvocationContext→MQContract.CQRS.Interfaces.IInvocationContext
- Direction
- CQRS.Contexts uses CQRS.Interfaces, so a change to CQRS.Interfaces can break CQRS.Contexts, while a change to CQRS.Contexts can't break CQRS.Interfaces.
- Position
- Below the diagonal: CQRS.Contexts uses a module listed above it, which is the healthy direction.
40→36 CQRS.Contexts uses CQRS✕
- Connections
- 4 pairs of types, where a type in CQRS.Contexts uses a type in CQRS.
- The types involved
MQContract.CQRS.Contexts.AInvocationContext→MQContract.CQRS.ContextMQContract.CQRS.Contexts.AInvocationContext→MQContract.CQRS.CqrsConnectionMQContract.CQRS.Contexts.CommandInvocationContext→MQContract.CQRS.CqrsConnectionMQContract.CQRS.Contexts.QueryInvocationContext→MQContract.CQRS.CqrsConnection
- Direction
- CQRS.Contexts uses CQRS, so a change to CQRS can break CQRS.Contexts, while a change to CQRS.Contexts can't break CQRS.
- Position
- Below the diagonal: CQRS.Contexts 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 9 | High / Critical |
| A01:2025 — Broken Access Control | 4 | Medium |
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
Roadmap
Top priorities: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.); 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; Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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.). | +10.7 pts | Medium | Data Protection |
| Resolve the 4 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (3), REDACTED. | +2.6 pts | Low | Data Compliance (PII/GDPR) |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.5 pts | Medium | Architecture documentation |
| Resolve the 2 `TryExecuteQuery` returns an awaitable but lacks the `Async` suffix its… finding(s) in Naming Consistency — start with MQContractMessageContext.cs (2). | +1.6 pts | Low | Naming Consistency |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.5 pts | Low | Dependency Vulnerabilities |
| Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root. | +3.0 pts | Medium | Folder & project structure |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.3 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| Generators/MessageContextGenerator.cs | 7.4 | Mixed | Cyclomatic Complexity: MessageContextGenerator.Generate (cyclomatic 21) |
| Connectors/AmazonSNQS/MessageMapper.cs | 7.4 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| CQRS/Consumers/CancellationRequestConsumer.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Connectors/ActiveMQ/Connection.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Connectors/AmazonSNQS/Subscription.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Connectors/ApachePulsar/Subscription.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Connectors/Kafka/Subscription.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Connectors/NATS/Connection.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Connectors/RabbitMQ/Connection.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Core/Helpers/ConsumerConnectionHelper.cs | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Core/Connections/AConnection.cs | 7.8 | Mixed | God Classes: TooManyMethods: AConnection |
| Core/MessageContext.MessageTypes.cs | 7.8 | Mixed | God Classes: TooManyMethods: MessageContext |
| Core/MessageContext.QueryResponse.cs | 7.8 | Mixed | Code Duplication: Duplicated block (15 lines × 2) |
| Testing/Core/CoreTesting.csproj | 7.8 | Mixed | Dependency Hygiene: Deprecated: MSTest.TestAdapter |
| Testing/CQRSTesting/CQRSTesting.csproj | 7.8 | Mixed | Dependency Hygiene: Deprecated: MSTest.TestAdapter |
| Testing/CodeGenTesting/CodeGenTesting.csproj | 7.8 | Mixed | Dependency Hygiene: Deprecated: MSTest.TestAdapter |
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 73 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 73 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, 167 of 216 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. At least one `dotnet test` target was stopped at its time budget, so the gathered reports cover only part of the suite. The overall 95.4% is a FLOOR (everything the completed runs covered really is covered), but a per-file figure from a partial gather cannot tell an untested file from one whose test project never ran — so per-file and CRAP rows are withheld rather than published as measurements. You can widen what we reach: optional: commit the Cobertura/OpenCover/lcov report your CI already produces, and per-file rows can be read without a re-run.
- D11 Test Reliability — 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 MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 61 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- 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.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D32 Data Compliance (PII/GDPR) — 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. `Abstractions/Attributes/ConsumerAttribute.cs`, `Abstractions/Attributes/MQContractMessageContextAttribute.cs`, `Abstractions/Attributes/MessageAttribute.cs`, `Abstractions/Attributes/QueryMessageAttribute.cs`, `Abstractions/Exceptions.cs`, … (+47 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P10 Library API & versioning — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- P11 BDD / executable specs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- P7 Outbound HTTP resilience — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
- 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. 62 further occurrence(s) are not listed individually; the score already reflects all 102.
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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- 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.
- 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.
- 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.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MessageContextGenerator.Generate at 21. 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 Connection.Connection.ctor at 21 — 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: Connectors/GooglePubSub/Connection.cs (Connection.Connection.ctor at 21). 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 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with MessageContextGenerator.Generate (cyclomatic 21). — Refactoring it lifts Cyclomatic Complexity from 9.6 to about 10.0/10.
- 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
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was MessageContextGenerator.Generate at 66.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with MessageContextGenerator.Generate (cognitive 66). — Refactoring it lifts Cognitive Complexity from 8.4 to about 10.0/10.
- 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
3 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with AConnection.cs, MessageContext.MessageTypes.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with AConnection.cs. — One of this dimension's main actionable groups (1 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
13 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with MessageMapper.cs, MessageContextGenerator.cs, Connection.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with MappedConnection.cs, ResiliencePolicy.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with MessageMapper.cs (2). — One of this dimension's main actionable groups (2 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
76 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 55 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 95.4%.
D9 · Test Distribution
1442 test methods: 1362 unit, 80 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 3 mock references across 721 tests.
D12 · Dependency Hygiene
32 outdated, 0 vulnerable, 2 deprecated packages.
What to do
- Resolve the 10 Deprecated finding(s) in Dependency Hygiene — start with CoreTesting.csproj (2), CQRSTesting.csproj (2), CodeGenTesting.csproj (2). — One of this dimension's main actionable groups (10 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 329 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 43 direct `PackageReference`(s), and 207 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
8 deducted debt markers + 6 dead symbols across 15180 LoC in the .NET projects (0.6/KLoC) → score 8.9.
What to do
- Resolve the 8 EmptyCatchBlock finding(s) in Explicit Debt — start with Connection.cs (3), Subscription.cs (3), CancellationRequestConsumer.cs. — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 6 Dead code finding(s) in Explicit Debt — start with BasicMessageToNameAndVersionMessage.cs, NoChannelMessageToBasicMessage.cs, MoqExtensions.cs. — One of this dimension's main actionable groups (6 warning-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
76 projects, 1063 source files, 48207 hand-written lines of code (15180 production / 33027 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), 131 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 16 document(s) read across 18 unit(s).
D21 · Naming Consistency
2 naming inconsistencies among 159 declarations measured against a convention their peers follow.
What to do
- Resolve the 2 `TryExecuteQuery` returns an awaitable but lacks the `Async` suffix its… finding(s) in Naming Consistency — start with MQContractMessageContext.cs (2). — One of this dimension's main actionable groups (2 recommendation-level).
D26 · Project Cohesion
0 of 46 projects flagged as possibly oversized/incoherent.
D27 · Navigability
76 % of calls cross a namespace and 3 % go through an interface, but 75 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.
What to do
- Resolve the 2 Pass-through layer finding(s) in Navigability — start with ContractedConnectionRegistrar.cs, MappedConnectionRegistrar.cs. — One of this dimension's main actionable groups (2 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
9 finding(s): 0 critical, 7 high, 2 medium, 0 low. 5 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 57 file(s) — `Abstractions/Attributes/ConsumerAttribute.cs` (line 23), `Abstractions/Attributes/MQContractMessageContextAttribute.cs` (line 10), `Abstractions/Attributes/MessageAttribute.cs` (line 20), `Abstractions/Attributes/QueryMessageAttribute.cs` (lines 16–17, line 17, line 18), `Abstractions/Exceptions.cs` (lines 1–38, line 43, lines 49–50), … (+52 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 57 of those file(s) — `Abstractions/Attributes/ConsumerAttribute.cs`, `Abstractions/Attributes/MQContractMessageContextAttribute.cs`, `Abstractions/Attributes/MessageAttribute.cs`, `Abstractions/Attributes/QueryMessageAttribute.cs`, `Abstractions/Exceptions.cs`, … (+52 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.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 5 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 (5 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).
D32 · Data Compliance (PII/GDPR)
4 finding(s): 0 critical, 0 high, 4 medium, 0 low. semgrep could not parse 52 file(s) — `Abstractions/Attributes/ConsumerAttribute.cs`, `Abstractions/Attributes/MQContractMessageContextAttribute.cs`, `Abstractions/Attributes/MessageAttribute.cs`, `Abstractions/Attributes/QueryMessageAttribute.cs`, `Abstractions/Exceptions.cs`, … (+47 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 4 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 78 of the 238 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.
D39 · IL Efficiency
0 of 327 first-party methods have an oversized IL body.
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 31 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
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
- `ConsumerConnectionHelper` 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 (RegisterPubSubConsumerMethod, RegisterPubSubAsyncConsumerMethod, RegisterQueryResponseConsumerMethod, RegisterQueryResponseAsyncConsumerMethod; e.g. `RegisterPubSubConsumerMethod` at line 24). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Core/Helpers/ConsumerConnectionHelper.cs:8
- `CreateUserProcessor` 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 (_users; e.g. `_users` at line 14). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Samples/CQRSSample/CreateUserProcessor.cs:6
What to do
- 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 MQContract ↔ MQContract.Interfaces ↔ MQContract.Interfaces.Encrypting ↔ MQContract.Interfaces.Messages ↔ MQContract.Interfaces.Middleware ↔ MQContract.Interfaces.Service ↔ MQContract.Messages depend on each other. The lightest dependency in the cycle is MQContract → MQContract.Interfaces.Middleware (MQContract.MQContractMessageContext → MQContract.Interfaces.Middleware.MessageContextDefintion, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Abstractions/MQContractMessageContext.cs:5
- The namespaces MQContract.CQRS ↔ MQContract.CQRS.Consumers ↔ MQContract.CQRS.Interfaces ↔ MQContract.CQRS.Interfaces.Command ↔ MQContract.CQRS.Interfaces.Query depend on each other. The lightest dependency in the cycle is MQContract.CQRS → MQContract.CQRS.Interfaces.Command (MQContract.CQRS.CqrsConnection → MQContract.CQRS.Interfaces.Command.ICommandProcessor, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — CQRS/CqrsConnection.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
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.).
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `PublishMessageAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Connectors/ZeroMQ/Connection.cs:172
- `PingAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Connectors/ZeroMQ/Connection.cs:199
- `GetAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Core/Connections/ServiceConnectionList.cs:35
What to do
- Remove the dead code that still moves this score: delete dead if(false) / #if false branches and either do the real async work or drop the async keyword from fake-async methods.
M1 · Documentation (README)
- 320 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Add a README to the 15 of 30 project(s) that lack one — worth up to 1 pts.
- Review the README against recent changes; refresh the parts that drifted.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
- Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
- Only 16/46 projects share a common root namespace — the code's module identity is inconsistent.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
- Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6723 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `Abstractions/Abstractions.csproj` 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`. — Abstractions/Abstractions.csproj:12
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
- 9 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).
- `tsk.Wait()` 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). — Core/Utility.cs:35
- `.Wait()` 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). (×4) — Connectors/NATS/Connection.cs:46, BenchMark/InMemoryBenchmarks/SubscribingInMemory.cs:45, BenchMark/InMemoryBenchmarks/SubscribingInMemory.cs:46, …
- `connectionTask.Wait()` 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). — Connectors/RabbitMQ/Connection.cs:38
- `channelTask.Wait()` 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). — Connectors/RabbitMQ/Connection.cs:41
- `connectTask.Wait()` 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). — Connectors/HiveMQ/Connection.cs:37
- `subTask.Wait()` 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). — BenchMark/InMemoryBenchmarks/SubscribingInMemory.cs:38
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
X1 · Async 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) — Core/Connections/AConnection.cs:447, Core/Connections/AConnection.cs:611, Core/Utility.cs:25
- `ManualResetEventSlim.Wait` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`). (×2) — Core/Subscriptions/QueryResponseSubscription.cs:96, Connectors/ZeroMQ/Connection.cs:209
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×8) — Core/Utility.cs:35, Connectors/NATS/Connection.cs:46, Connectors/RabbitMQ/Connection.cs:38, …
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
- `len` is read from the stream being parsed at line 22 (`ReadInt32`), then read in bulk from that same stream at line 23 — and nowhere in this method is `len` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `len` against the bytes actually remaining in the stream before spending it. — Connectors/ZeroMQ/MessageMapper.cs:23
- `len` is read from the stream being parsed at line 25 (`ReadInt32`), then read in bulk from that same stream at line 26 — and nowhere in this method is `len` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `len` against the bytes actually remaining in the stream before spending it. — Connectors/AmazonSNQS/MessageMapper.cs:26
What to do
- Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `zip` is a `BrotliStream`, which implements `IDisposable`, and it is created here (line 18). Every use of it in `AfterMessageEncodeAsync` 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 zip = …;`), which releases it at the end of the scope on every path including a throw. — Core/Middleware/CompressionMiddleware.cs:18
- `ConsumerInstance` declares a finalizer (line 37), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — Connectors/ActiveMQ/ConsumerInstance.cs:37
- `messageConsumer` is never created by `ConsumerInstance` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 31). Its declared type `IMessageConsumer` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — Connectors/ActiveMQ/ConsumerInstance.cs:31
- `connectionTask` is a `Task`, which implements `IDisposable`, and it is created here (line 37). Every use of it in `Connection` 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 connectionTask = …;`), which releases it at the end of the scope on every path including a throw. — Connectors/RabbitMQ/Connection.cs:37
- `channelTask` is a `Task`, which implements `IDisposable`, and it is created here (line 40). Every use of it in `Connection` 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 channelTask = …;`), which releases it at the end of the scope on every path including a throw. — Connectors/RabbitMQ/Connection.cs:40
- `Connection` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `pingResponseEvent` itself (line 50), which makes that instance its own. But `pingResponseEvent` is named in none of the methods the disposal search covered: `DisposeAsync` (line 260) — 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` (`pingResponseEvent?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Connectors/ZeroMQ/Connection.cs:50
- `connectionMonitor` is a `NetMQMonitor`, which implements `IDisposable`, and it is created here (line 57). Every use of it in `SendMessageToDestination` 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 connectionMonitor = …;`), which releases it at the end of the scope on every path including a throw. — Connectors/ZeroMQ/Connection.cs:57
- `Connection` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `batchedMessageStream` itself (line 25), which makes that instance its own. But `batchedMessageStream` is named in none of the methods the disposal search covered: `DisposeAsync` (line 127) — 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` (`batchedMessageStream?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Connectors/AmazonSNQS/Connection.cs:25
- `cqrsConnection` is a `ICQRSConnection`, which implements `IDisposable`, and it is created here (line 68). Every use of it in `RunAsCommand` 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 cqrsConnection = …;`), which releases it at the end of the scope on every path including a throw. — BenchMark/InMemoryBenchmarks/SubscriptionBenchmarks.cs:68
- `cqrsConnection` is a `ICQRSConnection`, which implements `IDisposable`, and it is created here (line 135). Every use of it in `RunAsCommandWithContext` 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 cqrsConnection = …;`), which releases it at the end of the scope on every path including a throw. — BenchMark/InMemoryBenchmarks/SubscriptionBenchmarks.cs:135
- `contractConnection` is never created by `CqrsConnection` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 174). Its declared type `IContractConnection` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — CQRS/CqrsConnection.cs:174
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 118/216 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. (×33) — Core/Connections/AConnection.Consumers.cs:42, Core/Connections/AConnection.cs:67, Core/Connections/AConnection.cs:104, …
- Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`). — Core/Middleware/MetricsMiddleware.cs:36
- 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. (×5) — Core/Subscriptions/QueryResponseSubscription.cs:90, Connectors/NATS/Subscriptions/PublishSubscription.cs:10, Connectors/NATS/Subscriptions/QuerySubscription.cs:10, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
- `publishSemaphore.WaitAsync(cancellationToken)` runs INSIDE the `try` whose `finally` calls `publishSemaphore.Release()` unconditionally, so when the acquire is cancelled, times out or a statement before it throws, the `finally` gives back `publishSemaphore` although this method never took it. On a semaphore that raises the count past its limit (or throws `SemaphoreFullException`) and admits a caller the exclusion was there to keep out; on a lock it throws from the `finally` and hides the original exception. Take `publishSemaphore` immediately BEFORE the `try`, so the `finally` only runs once it is held. — Connectors/Redis/Connection.cs:61
What to do
- Each finding names the return, the `finally` guard it disagrees with, and the flag state the method's own assignments put it in at that point. Confirm from the three, then make the two statements of ownership agree: the flag and the returned value both say whether the caller now owns the primitive, so a return reporting success must leave the guard skipping the release, and a return reporting failure must leave it performing one. Setting the flag immediately before the return that reports success — never after it, and never on a path that goes on to report failure — is what keeps the pair readable.
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) — Core/Helpers/ConsumerConnectionHelper.cs:103, Connectors/Kafka/Subscription.cs:48, Connectors/RabbitMQ/Connection.cs:201, …
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). (×2) — Connectors/NATS/Connection.cs:279, Connectors/ActiveMQ/Connection.cs:209
- `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. (×2) — Connectors/Kafka/Middleware/SchemaValidationMiddleware.cs:155, Connectors/GooglePubSub/Connection.cs:138
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
- ~2.6 `!` suppressions per 1k syntax nodes — 200 suppression(s) across the 78405 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 | 70% | Strong | Solid. |
| Architecture | 73% | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 48% | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 58% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 35% | Weak — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 75% | Strong | Strongest area. |
Unscored — 4 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- 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 — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 40 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.
- AX1 Captive dependencies — no DI registrations detected
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (15,180 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (17 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (6 value object(s))
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (a message-bus package)
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P10 Library API & versioning — Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P11 BDD / executable specs — BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P7 Outbound HTTP resilience — Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P8 Schema migrations — Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- P9 Domain vs controller coverage — coverage data present for 122 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- 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 — 18 finding(s)
- EmptyCatchBlock CQRS/Consumers/CancellationRequestConsumer.cs:25
- EmptyCatchBlock Connectors/ActiveMQ/Connection.cs:209
- EmptyCatchBlock Connectors/AmazonSNQS/Subscription.cs:41
- EmptyCatchBlock Connectors/ApachePulsar/Subscription.cs:61
- EmptyCatchBlock Connectors/Kafka/Subscription.cs:48
- EmptyCatchBlock Connectors/NATS/Connection.cs:279
- EmptyCatchBlock Connectors/RabbitMQ/Connection.cs:201
- EmptyCatchBlock Core/Helpers/ConsumerConnectionHelper.cs:103
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle Abstractions/MQContractMessageContext.cs:5
- Namespace dependency cycle CQRS/CqrsConnection.cs:3
- REDACTED
- REDACTED
- REDACTED
Serious — 129 finding(s)
- Async method without CancellationToken: RegisterMessageContextAsync Core/Connections/AConnection.Consumers.cs:42
- Async method without CancellationToken: RegisterMiddlewareInstanceAsync Core/Connections/AConnection.cs:67
- Async method without CancellationToken: BeforeMessageEncodeAsync Core/Connections/AConnection.cs:104
- Async method without CancellationToken: AfterMessageEncodeAsync Core/Connections/AConnection.cs:118
- Async method without CancellationToken: BeforeMessageDecodeAsync Core/Connections/AConnection.cs:128
- Async method without CancellationToken: AfterMessageDecodeAsync Core/Connections/AConnection.cs:139
- Async method without CancellationToken: ProduceServiceMessageAsync Core/Connections/AConnection.cs:153
- Async method without CancellationToken: DecodeServiceMessageAsync Core/Connections/AConnection.cs:164
- Async method without CancellationToken: ProduceResultAsync Core/Connections/AConnection.cs:449
- Async method without CancellationToken: CloseAsync Core/Connections/AConnection.cs:690
- Async method without CancellationToken: CloseAsync Core/Connections/Connection.cs:28
- Async method without CancellationToken: PingAsync Core/Connections/MultiServiceConnection.cs:22
- Async method without CancellationToken: CloseAsync Core/Connections/ServiceConnectionList.cs:41
- Async method without CancellationToken: DecodeAsync Core/Defaults/ABitEncoder.cs:12
- Async method without CancellationToken: DecodeAsync Core/Defaults/ABitEncoder.cs:15
- Async method without CancellationToken: StreamToByteArray Core/Defaults/BitConverterHelper.cs:5
- Async method without CancellationToken: DecodeAsync Core/Defaults/ByteArrayEncoder.cs:7
- Async method without CancellationToken: DecodeAsync Core/Defaults/CharEncoder.cs:7
- Async method without CancellationToken: DecodeAsync Core/Defaults/JsonEncoder.cs:16
- Async method without CancellationToken: DecodeAsync Core/Defaults/StringEncoder.cs:8
- Async method without CancellationToken: AfterMessageEncodeAsync Core/Middleware/CompressionMiddleware.cs:13
- Async method without CancellationToken: BeforeMessageDecodeAsync Core/Middleware/CompressionMiddleware.cs:29
- Async method without CancellationToken: BeforeMessageDecodeAsync Core/Middleware/EncryptionMiddleware.cs:46
- Async method without CancellationToken: AddStat Core/Middleware/MetricsMiddleware.cs:57
- Async method without CancellationToken: AfterMessageDecodeAsync Core/Middleware/MetricsMiddleware.cs:68
- Deprecated: MSTest.TestAdapter Testing/Core/CoreTesting.csproj:17
- Deprecated: MSTest.TestAdapter Testing/CQRSTesting/CQRSTesting.csproj:17
- Deprecated: MSTest.TestAdapter Testing/CodeGenTesting/CodeGenTesting.csproj:19
- Deprecated: MSTest.TestAdapter Testing/ConnectorTesting/AmazonSQNS/AmazonSQNS.csproj:16
- Deprecated: MSTest.TestAdapter Testing/ConnectorTesting/Pulsar/Pulsar.csproj:16
- Deprecated: MSTest.TestFramework Testing/Core/CoreTesting.csproj:18
- Deprecated: MSTest.TestFramework Testing/CQRSTesting/CQRSTesting.csproj:18
- Deprecated: MSTest.TestFramework Testing/CodeGenTesting/CodeGenTesting.csproj:20
- Deprecated: MSTest.TestFramework Testing/ConnectorTesting/AmazonSQNS/AmazonSQNS.csproj:17
- Deprecated: MSTest.TestFramework Testing/ConnectorTesting/Pulsar/Pulsar.csproj:17
- Sync-over-async blocking
- Sync-over-async blocking Core/Utility.cs:35
- Sync-over-async blocking Connectors/NATS/Connection.cs:46
- Sync-over-async blocking Connectors/RabbitMQ/Connection.cs:38
- Sync-over-async blocking Connectors/RabbitMQ/Connection.cs:41
- Sync-over-async blocking Connectors/HiveMQ/Connection.cs:37
- Sync-over-async blocking BenchMark/InMemoryBenchmarks/SubscribingInMemory.cs:38
- Sync-over-async blocking BenchMark/InMemoryBenchmarks/SubscribingInMemory.cs:45
- Sync-over-async blocking BenchMark/InMemoryBenchmarks/SubscribingInMemory.cs:46
- Sync-over-async blocking CQRS/CqrsConnection.cs:45
- Sync-over-async (deadlock risk) Core/Utility.cs:35
- Sync-over-async (deadlock risk) Connectors/NATS/Connection.cs:46
- Sync-over-async (deadlock risk) Connectors/RabbitMQ/Connection.cs:38
- Sync-over-async (deadlock risk) Connectors/RabbitMQ/Connection.cs:41
- Sync-over-async (deadlock risk) Connectors/HiveMQ/Connection.cs:37
- Sync-over-async (deadlock risk) BenchMark/InMemoryBenchmarks/SubscribingInMemory.cs:38
- Sync-over-async (deadlock risk) BenchMark/InMemoryBenchmarks/SubscribingInMemory.cs:45
- Sync-over-async (deadlock risk) BenchMark/InMemoryBenchmarks/SubscribingInMemory.cs:46
- Swallowed exception (empty catch) Core/Helpers/ConsumerConnectionHelper.cs:103
- Swallowed exception (empty catch) Connectors/NATS/Connection.cs:279
- Swallowed exception (empty catch) Connectors/Kafka/Subscription.cs:48
- Swallowed exception (empty catch) Connectors/ActiveMQ/Connection.cs:209
- Swallowed exception (empty catch) Connectors/RabbitMQ/Connection.cs:201
- Swallowed exception (empty catch) Connectors/ApachePulsar/Subscription.cs:61
- Swallowed exception (empty catch) Connectors/AmazonSNQS/Subscription.cs:41
- Swallowed exception (empty catch) CQRS/Consumers/CancellationRequestConsumer.cs:25
- Dead code: BasicMessageToNameAndVersionMessage Testing/Core/Converters/BasicMessageToNameAndVersionMessage.cs:6
- Dead code: NoChannelMessageToBasicMessage Testing/Core/Converters/NoChannelMessageToBasicMessage.cs:6
- Dead code: ReturnsInOrder Testing/Core/MoqExtensions.cs:7
- Dead code: NonContextConverter Testing/CodeGenTesting/Converters/NonContextConverter.cs:6
- Dead code: NonContextMessageEncoder Testing/CodeGenTesting/Encoders/NonContextMessageEncoder.cs:6
- Dead code: NonContextMessageEncryptor Testing/CodeGenTesting/Encryptors/NonContextMessageEncryptor.cs:7
- Disposable created and abandoned in the method that made it Core/Middleware/CompressionMiddleware.cs:18
- Disposable created and abandoned in the method that made it Connectors/RabbitMQ/Connection.cs:37
- Disposable created and abandoned in the method that made it Connectors/RabbitMQ/Connection.cs:40
- Disposable created and abandoned in the method that made it Connectors/ZeroMQ/Connection.cs:57
- Disposable created and abandoned in the method that made it BenchMark/InMemoryBenchmarks/SubscriptionBenchmarks.cs:68
- Disposable created and abandoned in the method that made it BenchMark/InMemoryBenchmarks/SubscriptionBenchmarks.cs:135
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) Connectors/AmazonSNQS/MessageMapper.cs:68
- Duplicated block (5 lines × 2) Generators/MessageContextGenerator.cs:396
- Duplicated block (5 lines × 2) Core/Connections/Connection.cs:132
- Fake-async — async method never awaits Connectors/ZeroMQ/Connection.cs:172
- Fake-async — async method never awaits Connectors/ZeroMQ/Connection.cs:199
- Fake-async — async method never awaits Core/Connections/ServiceConnectionList.cs:35
- Sync-over-async (deadlock risk) through `.Result` Core/Connections/AConnection.cs:447
- Sync-over-async (deadlock risk) through `.Result` Core/Connections/AConnection.cs:611
- Sync-over-async (deadlock risk) through `.Result` Core/Utility.cs:25
- Process-global static state: ConsumerConnectionHelper Core/Helpers/ConsumerConnectionHelper.cs:8
- Process-global static state: CreateUserProcessor Samples/CQRSSample/CreateUserProcessor.cs:6
- TooManyMethods: AConnection Core/Connections/AConnection.cs
- TooManyMethods: MessageContext Core/MessageContext.MessageTypes.cs
- Duplicated block (12 lines × 2) Core/Connections/MappedConnection.cs:89
- Duplicated block (12 lines × 2) Core/Connections/ResiliencePolicy.cs:92
- Duplicated block (9 lines × 2) Connectors/AmazonSNQS/MessageMapper.cs:36
- Duplicated block (9 lines × 2) Connectors/AmazonSNQS/MessageMapper.cs:13
- Blocking `ManualResetEventSlim.Wait` inside an `async` method Core/Subscriptions/QueryResponseSubscription.cs:96
- Blocking `ManualResetEventSlim.Wait` inside an `async` method Connectors/ZeroMQ/Connection.cs:209
- Length read from the parsed input is spent without ever being bounded Connectors/ZeroMQ/MessageMapper.cs:23
- Length read from the parsed input is spent without ever being bounded Connectors/AmazonSNQS/MessageMapper.cs:26
- Disposes a dependency it does not own Connectors/ActiveMQ/ConsumerInstance.cs:31
- Disposes a dependency it does not own CQRS/CqrsConnection.cs:174
- Owned disposable field is never released Connectors/ZeroMQ/Connection.cs:50
- Owned disposable field is never released Connectors/AmazonSNQS/Connection.cs:25
- Swallowed exception (caught, then discarded) Connectors/Kafka/Middleware/SchemaValidationMiddleware.cs:155
- Swallowed exception (caught, then discarded) Connectors/GooglePubSub/Connection.cs:138
- No data-protection/encryption
- MessageContextGenerator.Generate (cyclomatic 21) Generators/MessageContextGenerator.cs:56
- MessageContextGenerator.Generate (cognitive 66) Generators/MessageContextGenerator.cs:56
- REDACTED
- REDACTED
- FileTooLong: Connections/AConnection.cs Core/Connections/AConnection.cs
- Duplicated block (17 lines × 2) Core/MessageContext.MessageTypes.cs:75
- Duplicated block (15 lines × 2) Core/MessageContext.QueryResponse.cs:56
- Duplicated block (14 lines × 2) Generators/EncodersHelper.cs:12
- Duplicated block (9 lines × 3) Generators/ConvertersHelper.cs:12
- Duplicated block (7 lines × 2) Core/MessageContext.QueryResponse.cs:11
- Duplicated block (18 lines × 2) CQRS/Registrars/ContractedConnectionRegistrar.cs:13
- README may be stale
- NuGet dependencies are not locked
- Finalizer on a type that owns no unmanaged resource Connectors/ActiveMQ/ConsumerInstance.cs:37
- Async delegate without CancellationToken: Start Core/Middleware/MetricsMiddleware.cs:36
- Release of a primitive the `try` may not have taken Connectors/Redis/Connection.cs:61
Minor — 34 finding(s)
- Mock-dominated test: CheckRegistrationUsingGenericsAndSuppliedInstanceWithParameters Testing/Core/ConnectionTests/Consumers/PubSubAsyncConsumerTests.cs:102
- Mock-dominated test: CheckRegistrationUsingGenericsAndSuppliedInstanceWithParameters Testing/Core/ConnectionTests/Consumers/PubSubConsumerTests.cs:101
- Mock-dominated test: CheckRegistrationUsingGenericsAndSuppliedInstanceWithParameters Testing/Core/ConnectionTests/Consumers/QueryResponseAsyncConsumerTests.cs:107
- Mock-dominated test: CheckRegistrationUsingGenericsAndSuppliedInstanceWithParameters Testing/Core/ConnectionTests/Consumers/QueryResponseConsumerTests.cs:107
- Mock-dominated test: TestRegisterContextInvokesMiddleware Testing/Core/ConnectionTests/MappedService/MessageContextTests.cs:42
- Mock-dominated test: TestRegisterMiddlewareInvokesContext Testing/Core/ConnectionTests/MappedService/MessageContextTests.cs:81
- Mock-dominated test: TestRegisterContextInvokesMiddleware Testing/Core/ConnectionTests/MultiService/MessageContextTests.cs:42
- Mock-dominated test: TestRegisterMiddlewareInvokesContext Testing/Core/ConnectionTests/MultiService/MessageContextTests.cs:81
- Mock-dominated test: TestRegisterContextInvokesMiddleware Testing/Core/ConnectionTests/SingleService/MessageContextTests.cs:40
- Mock-dominated test: TestRegisterMiddlewareInvokesContext Testing/Core/ConnectionTests/SingleService/MessageContextTests.cs:78
- Silent fallback default in catch Core/MessageContext.Converter.cs:55
- Silent fallback default in catch Core/MessageContext.Encoding.cs:32
- Silent fallback default in catch Core/MessageContext.Encoding.cs:140
- Silent fallback default in catch Core/MessageContext.Encryptors.cs:35
- Silent fallback default in catch Connectors/Kafka/Middleware/SchemaValidationMiddleware.cs:155
- Silent fallback default in catch Connectors/GooglePubSub/Connection.cs:138
- `TryExecuteQuery` returns an awaitable but lacks the `Async` suffix its 147 peers carry Abstractions/MQContractMessageContext.cs:118
- `TryExecuteQuery` returns an awaitable but lacks the `Async` suffix its 147 peers carry Abstractions/MQContractMessageContext.cs:133
- Pass-through layer CQRS/Registrars/ContractedConnectionRegistrar.cs:8
- Pass-through layer CQRS/Registrars/MappedConnectionRegistrar.cs:8
- Duplicated predicate Core/Connections/AConnection.Consumers.cs:83
- Duplicated predicate Generators/ConvertersHelper.cs:13
- REDACTED
- No ADRs
- No architecture diagram/doc
- No src/ separation
- No tests/ separation
- Inconsistent root namespaces
- Sleep-based test synchronization
- No SAST REDACTED:4
- No dependency-update automation Abstractions/Abstractions.csproj:12
- No changelog
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 35 finding(s)
- Outdated: Microsoft.CodeAnalysis.CSharp
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions
- Outdated: Microsoft.Extensions.Logging
- Outdated: Microsoft.Extensions.Logging.Abstractions
- Outdated: Polly
- Outdated: NATS.Net
- Outdated: Microsoft.Extensions.Diagnostics.HealthChecks.Abstractions
- Outdated: Microsoft.Extensions.Logging.Debug
- Outdated: OpenTelemetry
- Outdated: OpenTelemetry.Exporter.Console
- Outdated: OpenTelemetry.Exporter.OpenTelemetryProtocol
- Outdated: NJsonSchema
- Outdated: StackExchange.Redis
- Outdated: DotPulsar
- Outdated: System.Text.Json
- Outdated: coverlet.collector
- Outdated: coverlet.msbuild
- Outdated: Microsoft.Extensions.Diagnostics.Testing
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: Moq
- Outdated: MSTest.TestAdapter
- Outdated: MSTest.TestFramework
- Outdated: Testcontainers.ActiveMq
- Outdated: Testcontainers.LocalStack
- Outdated: Testcontainers.ServiceBus
- Mock framework: Moq
- Mock framework: Moq
- Mock framework: Moq
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-3bc558f11c464e5d891f1082772c2194/history.json --exit-code 0 --source . | 0 | 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-3bc558f11c464e5d891f1082772c2194/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 . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list MQContract.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --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 . | 4 | 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-4492f39da4644d84a66183144d708c9b | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 6 field(s)
- ArrivalAnnouncement.FirstName Samples/Messages/ArrivalAnnouncement.cs:6
- ArrivalAnnouncement.LastName Samples/Messages/ArrivalAnnouncement.cs:6
- Greeting.FirstName Samples/Messages/Greeting.cs:6
- Greeting.LastName Samples/Messages/Greeting.cs:6
- StoredArrivalAnnouncement.FirstName Samples/Messages/StoredArrivalAnnouncement.cs:6
- StoredArrivalAnnouncement.LastName Samples/Messages/StoredArrivalAnnouncement.cs:6
Email — 2 field(s)
- CreateUserCommand.Email Samples/CQRSSample/Messages/CreateUserCommand.cs:7
- User.Email Samples/CQRSSample/Messages/User.cs:3