Executive summary
Eventuous/eventuous meets our standard for a preview release. It scores 67 out of 100 and is rated Strong, and 34 of its 50 critical findings are security problems.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is moving to stable dependency versions, worth about 4 points. Replacing each deprecated dependency comes next, worth about 3 points.
Eighteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and five settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Updating the vulnerable packages would fix the four packages with a known security hole, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The six sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 22,436 lines, about €83,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
New since the last survey: 23 findings
- Documentation (README) · README may be stale
- Stateful singletons · Stateful shared instance: TypeMapper src/Core/src/Eventuous.Shared/TypeMap/TypeMapper.cs
- Stateful singletons · Stateful shared instance: LoggingEventListener src/Diagnostics/src/Eventuous.Diagnostics.Logging/LoggingEventListener.cs
- Stateful singletons · Process-global static state: EventuousDiagnostics src/Core/src/Eventuous.Diagnostics/EventuousDiagnostics.cs
- Stateful singletons · Process-global static state: DefaultMetadataSerializer src/Core/src/Eventuous.Serialization/DefaultMetadataSerializer.cs
- Stateful singletons · Process-global static state: EventSerializer src/Core/src/Eventuous.Serialization/EventSerializer.cs
- Stateful singletons · Process-global static state: LoggerFactoryExtensions src/Extensions/src/Eventuous.Extensions.Logging/LoggerFactoryExtensions.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Eventuous.Application.csproj
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/AggregateService/CommandHandlerBuilder.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/AggregateService/CommandService.Async.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/AggregateService/CommandService.Sync.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/AggregateService/CommandService.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Diagnostics/ApplicationEventSource.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Diagnostics/CommandServiceActivity.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Diagnostics/CommandServiceMetrics.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/FunctionalService/CommandHandlerBuilder.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/FunctionalService/CommandService.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/FunctionalService/FuncHandlerDelegateExtensions.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/FunctionalService/FuncServiceDelegates.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/FunctionalService/HandlersMap.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Persistence/ProposedAppend.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Persistence/WriterExtensions.cs
- Dependency direction · Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Result.cs
Fixed since the last survey: 39 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Churn × Complexity Hotspots · Hotspot: src/Core/gen/Eventuous.Shared.Generators/EventUsageAnalyzer.cs src/Core/gen/Eventuous.Shared.Generators/EventUsageAnalyzer.cs
- Churn × Complexity Hotspots · Repeated repair: src/Core/src/Eventuous.Subscriptions/Channels/ChannelWorkerBase.cs src/Core/src/Eventuous.Subscriptions/Channels/ChannelWorkerBase.cs
- Explicit Debt · CommentedOutCode src/Diagnostics/test/Eventuous.Tests.OpenTelemetry/MetricsTests.cs
- Explicit Debt · Dead code: ClearChanges src/Core/src/Eventuous.Domain/Aggregate.cs
- Cancellation propagation · Async method without CancellationToken: Seed src/Experimental/src/ElasticPlayground/ConnectorAndArchive.cs
- Cancellation propagation · Async method without CancellationToken: Execute src/Experimental/src/ElasticPlayground/ElasticOnly.cs
- Cancellation propagation · Async method without CancellationToken: Execute src/Experimental/src/ElasticPlayground/OnlyArchive.cs
- Cancellation propagation · Async method without CancellationToken: CreateIndexIfNecessary src/Experimental/src/Eventuous.ElasticSearch/Index/IndexSetup.cs
- Cancellation propagation · Async local function without CancellationToken: CreateLifecycle src/Experimental/src/Eventuous.ElasticSearch/Index/IndexSetup.cs
- Cancellation propagation · Async local function without CancellationToken: CreateTemplate src/Experimental/src/Eventuous.ElasticSearch/Index/IndexSetup.cs
- Cancellation propagation · Async method without CancellationToken: LoadModule src/Redis/src/Eventuous.Redis/Module.cs
- Cancellation propagation · Async method without CancellationToken: ReadEvents src/Redis/src/Eventuous.Redis/Subscriptions/RedisAllStreamSubscription.cs
- Cancellation propagation · Async method without CancellationToken: ReadEvents src/Redis/src/Eventuous.Redis/Subscriptions/RedisStreamSubscription.cs
- Cancellation propagation · Async method without CancellationToken: HandleEvent src/Extensions/src/Eventuous.Subscriptions.Polly/PollyEventHandler.cs
- Cancellation propagation · Async local function without CancellationToken: Execute src/Extensions/src/Eventuous.Subscriptions.Polly/PollyEventHandler.cs
- Cancellation propagation · Async method without CancellationToken: TryExecute src/KurrentDB/src/Eventuous.KurrentDB/KurrentDBEventStore.cs
- Cancellation propagation · Async method without CancellationToken: Ack src/KurrentDB/src/Eventuous.KurrentDB/Subscriptions/PersistentSubscriptionBase.cs
- Cancellation propagation · Async method without CancellationToken: Nack src/KurrentDB/src/Eventuous.KurrentDB/Subscriptions/PersistentSubscriptionBase.cs
- Cancellation propagation · Async local function without CancellationToken: HandleTypedEvent src/Mongo/src/Eventuous.Projections.MongoDB/MongoProjector.cs
- Cancellation propagation · Async method without CancellationToken: GetUpdateWithOptions src/Mongo/src/Eventuous.Projections.MongoDB/Operations/UpdateBuilder.cs
- Cancellation propagation · Async method without CancellationToken: CreateDocumentIndex src/Mongo/src/Eventuous.Projections.MongoDB/Tools/MongoCollectionExtensions.cs
- Cancellation propagation · Async method without CancellationToken: CreateDocumentIndex src/Mongo/src/Eventuous.Projections.MongoDB/Tools/MongoDatabaseExtensions.cs
- Cancellation propagation · Async method without CancellationToken: BookRoom samples/kurrentdb/Bookings.Domain/Bookings/Booking.cs
- Cancellation propagation · Async method without CancellationToken: EnsureRoomAvailable samples/kurrentdb/Bookings.Domain/Bookings/Booking.cs
- Cancellation propagation · Async method without CancellationToken: GetUserBookings samples/kurrentdb/Bookings/Application/BookingsQueryService.cs
- Cancellation propagation · Async endpoint handler without CancellationToken: /bookings/my/{userId} samples/kurrentdb/Bookings/Program.cs
- Cancellation propagation · Async local function without CancellationToken: InitialiseSchema samples/postgres/Bookings.Payments/Program.cs
- Cancellation propagation · Async local function without CancellationToken: InitialiseSchema samples/postgres/Bookings/Program.cs
- Cancellation propagation · Async method without CancellationToken: UnsubscribeAsync src/SignalR/src/Eventuous.SignalR.Client/SignalRSubscriptionClient.cs
- Cancellation propagation · Async method without CancellationToken: OnReconnected src/SignalR/src/Eventuous.SignalR.Client/SignalRSubscriptionClient.cs
- Cancellation propagation · Async method without CancellationToken: UnsubscribeAsync src/SignalR/src/Eventuous.SignalR.Server/SubscriptionGateway.cs
- Cancellation propagation · Async method without CancellationToken: RemoveConnectionAsync src/SignalR/src/Eventuous.SignalR.Server/SubscriptionGateway.cs
- Cancellation propagation · Async method without CancellationToken: StopSubscription src/SignalR/src/Eventuous.SignalR.Server/SubscriptionGateway.cs
- Cancellation propagation · Async method drops its CancellationToken: AppendEvents src/Redis/src/Eventuous.Redis/RedisStore.cs
- Cancellation propagation · Async method drops its CancellationToken: StreamExists src/Redis/src/Eventuous.Redis/RedisStore.cs
- Cancellation propagation · Async method drops its CancellationToken: GetLastCheckpoint src/Redis/src/Eventuous.Redis/Subscriptions/RedisCheckpointStore.cs
- Cancellation propagation · Async method drops its CancellationToken: StoreCheckpoint src/Redis/src/Eventuous.Redis/Subscriptions/RedisCheckpointStore.cs
- Cancellation propagation · Async method drops its CancellationToken: BeforeSubscribe src/Redis/src/Eventuous.Redis/Subscriptions/RedisStreamSubscription.cs
Rebuild cost: about €83,000 · Estimate
| Cost to rebuild | €27,000 to €140,000, for 452 to 1,452 hours of work, about 0.6 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 67. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 22,436 lines of product code, of which 39% is declarations and boilerplate, 30% straight logic and 31% logic with branches |
| Comment lines | The estimate prices 18,987 lines. Comment lines count towards the size of 22,436 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 Eventuous | 2 Eventuous.GooglePubSub | 3 ElasticPlayground | 4 Eventuous.Diagnostics.Metrics | 5 Eventuous.Extensions.AspNetCore.Http | 6 Eventuous.Producers.Diagnostics | 7 Eventuous.Sql.Base | 8 Eventuous.Subscriptions.Context | 9 Eventuous.Diagnostics | 10 Eventuous.Producers | 11 Eventuous.Subscriptions.Logging | 12 Eventuous.Azure.ServiceBus.Producers | 13 Eventuous.ElasticSearch.Producers | 14 Eventuous.GooglePubSub.Producers | 15 Eventuous.Kafka.Producers | 16 Eventuous.KurrentDB.Producers | 17 Eventuous.RabbitMq.Producers | 18 Eventuous.Subscriptions.Checkpoints | 19 Eventuous.Subscriptions.Consumers | 20 Eventuous.Subscriptions.Diagnostics | 21 Eventuous.Subscriptions.Filters | 22 Eventuous.Subscriptions | 23 Eventuous.Azure.ServiceBus.Subscriptions | 24 Eventuous.Azure.Storage.Blobs | 25 Eventuous.Gateway | 26 Eventuous.GooglePubSub.CloudRun | 27 Eventuous.GooglePubSub.Subscriptions | 28 Eventuous.Kafka.Subscriptions | 29 Eventuous.KurrentDB.Subscriptions | 30 Eventuous.Projections.MongoDB | 31 Eventuous.RabbitMq.Subscriptions | 32 Eventuous.Redis.Subscriptions | 33 Eventuous.Sql.Base.Subscriptions | 34 Eventuous.SqlServer.Projections | 35 Eventuous.Sqlite.Projections | 36 Eventuous.Subscriptions.Registrations | 37 Eventuous.Postgresql.Subscriptions | 38 Eventuous.SignalR.Server | 39 Eventuous.SqlServer.Subscriptions | 40 Eventuous.Sqlite.Subscriptions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Eventuous | ||||||||||||||||||||||||||||||||||||||||
| 2 Eventuous.GooglePubSub | ||||||||||||||||||||||||||||||||||||||||
| 3 ElasticPlayground | 7 | |||||||||||||||||||||||||||||||||||||||
| 4 Eventuous.Diagnostics.Metrics | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 Eventuous.Extensions.AspNetCore.Http | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 Eventuous.Producers.Diagnostics | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 7 Eventuous.Sql.Base | 11 | |||||||||||||||||||||||||||||||||||||||
| 8 Eventuous.Subscriptions.Context | 6 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 9 Eventuous.Diagnostics | 6 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 Eventuous.Producers | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 Eventuous.Subscriptions.Logging | 1 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 Eventuous.Azure.ServiceBus.Producers | 5 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 13 Eventuous.ElasticSearch.Producers | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 14 Eventuous.GooglePubSub.Producers | 2 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 15 Eventuous.Kafka.Producers | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 16 Eventuous.KurrentDB.Producers | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 Eventuous.RabbitMq.Producers | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 18 Eventuous.Subscriptions.Checkpoints | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Eventuous.Subscriptions.Consumers | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 Eventuous.Subscriptions.Diagnostics | 1 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 21 Eventuous.Subscriptions.Filters | 10 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 Eventuous.Subscriptions | 6 | 11 | 3 | 4 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 23 Eventuous.Azure.ServiceBus.Subscriptions | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 24 Eventuous.Azure.Storage.Blobs | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 25 Eventuous.Gateway | 8 | 4 | 6 | 3 | ||||||||||||||||||||||||||||||||||||
| 26 Eventuous.GooglePubSub.CloudRun | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 27 Eventuous.GooglePubSub.Subscriptions | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 28 Eventuous.Kafka.Subscriptions | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 29 Eventuous.KurrentDB.Subscriptions | 16 | 3 | 3 | 4 | 7 | 14 | ||||||||||||||||||||||||||||||||||
| 30 Eventuous.Projections.MongoDB | 4 | 12 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 31 Eventuous.RabbitMq.Subscriptions | 1 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 32 Eventuous.Redis.Subscriptions | 4 | 1 | 5 | 3 | 4 | |||||||||||||||||||||||||||||||||||
| 33 Eventuous.Sql.Base.Subscriptions | 3 | 1 | 1 | 1 | 2 | 1 | 5 | |||||||||||||||||||||||||||||||||
| 34 Eventuous.SqlServer.Projections | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 Eventuous.Sqlite.Projections | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 Eventuous.Subscriptions.Registrations | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 Eventuous.Postgresql.Subscriptions | 7 | 1 | 5 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 38 Eventuous.SignalR.Server | 4 | 2 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 39 Eventuous.SqlServer.Subscriptions | 7 | 5 | 3 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||
| 40 Eventuous.Sqlite.Subscriptions | 7 | 5 | 3 | 1 | 2 | 3 |
3→1 ElasticPlayground uses Eventuous✕
- Connections
- 7 pairs of types, where a type in ElasticPlayground uses a type in Eventuous.
- The types involved
ElasticPlayground.CombinedStore→Eventuous.IEventStoreElasticPlayground.CombinedStore→Eventuous.TieredEventStoreElasticPlayground.ConnectorAndArchive→Eventuous.IEventStoreElasticPlayground.ConnectorAndArchive→Eventuous.TieredEventStoreElasticPlayground.ElasticOnly→Eventuous.ICommandServiceElasticPlayground.OnlyArchive→Eventuous.TieredEventStoreElasticPlayground.ResultExtensions→Eventuous.Result
- Direction
- ElasticPlayground uses Eventuous, so a change to Eventuous can break ElasticPlayground, while a change to ElasticPlayground can't break Eventuous.
- Position
- Below the diagonal: ElasticPlayground uses a module listed above it, which is the healthy direction.
4→9 Eventuous.Diagnostics.Metrics uses Eventuous.Diagnostics part of a loop✕
- Connections
- 1 pair of types, where a type in Eventuous.Diagnostics.Metrics uses a type in Eventuous.Diagnostics.
- The types involved
Eventuous.Diagnostics.Metrics.MetricsListener→Eventuous.Diagnostics.GenericListener
- Direction
- Eventuous.Diagnostics.Metrics uses Eventuous.Diagnostics, so a change to Eventuous.Diagnostics can break Eventuous.Diagnostics.Metrics, while a change to Eventuous.Diagnostics.Metrics can't break Eventuous.Diagnostics.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→1 Eventuous.Extensions.AspNetCore.Http uses Eventuous✕
- Connections
- 2 pairs of types, where a type in Eventuous.Extensions.AspNetCore.Http uses a type in Eventuous.
- The types involved
Eventuous.Extensions.AspNetCore.Http.CommandHttpApiBase→Eventuous.CommandMapEventuous.Extensions.AspNetCore.Http.CommandHttpApiBase→Eventuous.ICommandService
- Direction
- Eventuous.Extensions.AspNetCore.Http uses Eventuous, so a change to Eventuous can break Eventuous.Extensions.AspNetCore.Http, while a change to Eventuous.Extensions.AspNetCore.Http can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Extensions.AspNetCore.Http uses a module listed above it, which is the healthy direction.
6→1 Eventuous.Producers.Diagnostics uses Eventuous✕
- Connections
- 1 pair of types, where a type in Eventuous.Producers.Diagnostics uses a type in Eventuous.
- The types involved
Eventuous.Producers.Diagnostics.ProducerActivity→Eventuous.Metadata
- Direction
- Eventuous.Producers.Diagnostics uses Eventuous, so a change to Eventuous can break Eventuous.Producers.Diagnostics, while a change to Eventuous.Producers.Diagnostics can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Producers.Diagnostics uses a module listed above it, which is the healthy direction.
6→10 Eventuous.Producers.Diagnostics uses Eventuous.Producers part of a loop✕
- Connections
- 2 pairs of types, where a type in Eventuous.Producers.Diagnostics uses a type in Eventuous.Producers.
- The types involved
Eventuous.Producers.Diagnostics.ProducerActivity→Eventuous.Producers.ProducedMessageEventuous.Producers.Diagnostics.ProducerEventSource→Eventuous.Producers.ProducedMessage
- Direction
- Eventuous.Producers.Diagnostics uses Eventuous.Producers, so a change to Eventuous.Producers can break Eventuous.Producers.Diagnostics, while a change to Eventuous.Producers.Diagnostics can't break Eventuous.Producers.
- 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.
7→1 Eventuous.Sql.Base uses Eventuous✕
- Connections
- 11 pairs of types, where a type in Eventuous.Sql.Base uses a type in Eventuous.
- The types involved
Eventuous.Sql.Base.SqlEventStoreBase→Eventuous.AppendEventsResultEventuous.Sql.Base.SqlEventStoreBase→Eventuous.ExpectedStreamVersionEventuous.Sql.Base.SqlEventStoreBase→Eventuous.IEventSerializerEventuous.Sql.Base.SqlEventStoreBase→Eventuous.IEventStoreEventuous.Sql.Base.SqlEventStoreBase→Eventuous.IMetadataSerializerEventuous.Sql.Base.SqlEventStoreBase→Eventuous.NewStreamAppendEventuous.Sql.Base.SqlEventStoreBase→Eventuous.NewStreamEventEventuous.Sql.Base.SqlEventStoreBase→Eventuous.StreamEventEventuous.Sql.Base.SqlEventStoreBase→Eventuous.StreamNameEventuous.Sql.Base.SqlEventStoreBase→Eventuous.StreamReadPositionEventuous.Sql.Base.SqlEventStoreBase→Eventuous.StreamTruncatePosition
- Direction
- Eventuous.Sql.Base uses Eventuous, so a change to Eventuous can break Eventuous.Sql.Base, while a change to Eventuous.Sql.Base can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Sql.Base uses a module listed above it, which is the healthy direction.
8→1 Eventuous.Subscriptions.Context uses Eventuous✕
- Connections
- 6 pairs of types, where a type in Eventuous.Subscriptions.Context uses a type in Eventuous.
- The types involved
Eventuous.Subscriptions.Context.IBaseConsumeContext→Eventuous.MetadataEventuous.Subscriptions.Context.IBaseConsumeContext→Eventuous.StreamNameEventuous.Subscriptions.Context.MessageConsumeContext→Eventuous.MetadataEventuous.Subscriptions.Context.MessageConsumeContext→Eventuous.StreamNameEventuous.Subscriptions.Context.WrappedConsumeContext→Eventuous.MetadataEventuous.Subscriptions.Context.WrappedConsumeContext→Eventuous.StreamName
- Direction
- Eventuous.Subscriptions.Context uses Eventuous, so a change to Eventuous can break Eventuous.Subscriptions.Context, while a change to Eventuous.Subscriptions.Context can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Subscriptions.Context uses a module listed above it, which is the healthy direction.
8→11 Eventuous.Subscriptions.Context uses Eventuous.Subscriptions.Logging part of a loop✕
- Connections
- 3 pairs of types, where a type in Eventuous.Subscriptions.Context uses a type in Eventuous.Subscriptions.Logging.
- The types involved
Eventuous.Subscriptions.Context.IBaseConsumeContext→Eventuous.Subscriptions.Logging.LogContextEventuous.Subscriptions.Context.MessageConsumeContext→Eventuous.Subscriptions.Logging.LogContextEventuous.Subscriptions.Context.WrappedConsumeContext→Eventuous.Subscriptions.Logging.LogContext
- Direction
- Eventuous.Subscriptions.Context uses Eventuous.Subscriptions.Logging, so a change to Eventuous.Subscriptions.Logging can break Eventuous.Subscriptions.Context, while a change to Eventuous.Subscriptions.Context can't break Eventuous.Subscriptions.Logging.
- 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.
8→22 Eventuous.Subscriptions.Context uses Eventuous.Subscriptions part of a loop✕
- Connections
- 3 pairs of types, where a type in Eventuous.Subscriptions.Context uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Subscriptions.Context.IBaseConsumeContext→Eventuous.Subscriptions.HandlingResultsEventuous.Subscriptions.Context.MessageConsumeContext→Eventuous.Subscriptions.HandlingResultsEventuous.Subscriptions.Context.WrappedConsumeContext→Eventuous.Subscriptions.HandlingResults
- Direction
- Eventuous.Subscriptions.Context uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Subscriptions.Context, while a change to Eventuous.Subscriptions.Context can't break Eventuous.Subscriptions.
- 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.
9→1 Eventuous.Diagnostics uses Eventuous✕
- Connections
- 6 pairs of types, where a type in Eventuous.Diagnostics uses a type in Eventuous.
- The types involved
Eventuous.Diagnostics.CommandServiceActivity→Eventuous.ResultEventuous.Diagnostics.HandleCommand→Eventuous.ResultEventuous.Diagnostics.MetadataExtensions→Eventuous.MetadataEventuous.Diagnostics.PersistenceEventSource→Eventuous.StreamNameEventuous.Diagnostics.TracedCommandService→Eventuous.ICommandServiceEventuous.Diagnostics.TracedCommandService→Eventuous.Result
- Direction
- Eventuous.Diagnostics uses Eventuous, so a change to Eventuous can break Eventuous.Diagnostics, while a change to Eventuous.Diagnostics can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Diagnostics uses a module listed above it, which is the healthy direction.
9→4 Eventuous.Diagnostics uses Eventuous.Diagnostics.Metrics✕
- Connections
- 2 pairs of types, where a type in Eventuous.Diagnostics uses a type in Eventuous.Diagnostics.Metrics.
- The types involved
Eventuous.Diagnostics.CommandServiceMetrics→Eventuous.Diagnostics.Metrics.MetricsListenerEventuous.Diagnostics.PersistenceMetrics→Eventuous.Diagnostics.Metrics.MetricsListener
- Direction
- Eventuous.Diagnostics uses Eventuous.Diagnostics.Metrics, so a change to Eventuous.Diagnostics.Metrics can break Eventuous.Diagnostics, while a change to Eventuous.Diagnostics can't break Eventuous.Diagnostics.Metrics.
- Position
- Below the diagonal: Eventuous.Diagnostics uses a module listed above it, which is the healthy direction.
10→1 Eventuous.Producers uses Eventuous✕
- Connections
- 6 pairs of types, where a type in Eventuous.Producers uses a type in Eventuous.
- The types involved
Eventuous.Producers.BaseProducer→Eventuous.StreamNameEventuous.Producers.IProducer→Eventuous.StreamNameEventuous.Producers.ProduceRequest→Eventuous.StreamNameEventuous.Producers.ProducedMessage→Eventuous.MetadataEventuous.Producers.ProducerExtensions→Eventuous.MetadataEventuous.Producers.ProducerExtensions→Eventuous.StreamName
- Direction
- Eventuous.Producers uses Eventuous, so a change to Eventuous can break Eventuous.Producers, while a change to Eventuous.Producers can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Producers uses a module listed above it, which is the healthy direction.
10→6 Eventuous.Producers uses Eventuous.Producers.Diagnostics✕
- Connections
- 1 pair of types, where a type in Eventuous.Producers uses a type in Eventuous.Producers.Diagnostics.
- The types involved
Eventuous.Producers.BaseProducer→Eventuous.Producers.Diagnostics.ProducerTracingOptions
- Direction
- Eventuous.Producers uses Eventuous.Producers.Diagnostics, so a change to Eventuous.Producers.Diagnostics can break Eventuous.Producers, while a change to Eventuous.Producers can't break Eventuous.Producers.Diagnostics.
- Position
- Below the diagonal: Eventuous.Producers uses a module listed above it, which is the healthy direction.
11→1 Eventuous.Subscriptions.Logging uses Eventuous✕
- Connections
- 1 pair of types, where a type in Eventuous.Subscriptions.Logging uses a type in Eventuous.
- The types involved
Eventuous.Subscriptions.Logging.LoggingExtensions→Eventuous.DeserializationError
- Direction
- Eventuous.Subscriptions.Logging uses Eventuous, so a change to Eventuous can break Eventuous.Subscriptions.Logging, while a change to Eventuous.Subscriptions.Logging can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Subscriptions.Logging uses a module listed above it, which is the healthy direction.
11→8 Eventuous.Subscriptions.Logging uses Eventuous.Subscriptions.Context✕
- Connections
- 2 pairs of types, where a type in Eventuous.Subscriptions.Logging uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Subscriptions.Logging.LoggingExtensions→Eventuous.Subscriptions.Context.IBaseConsumeContextEventuous.Subscriptions.Logging.LoggingExtensions→Eventuous.Subscriptions.Context.IMessageConsumeContext
- Direction
- Eventuous.Subscriptions.Logging uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Subscriptions.Logging, while a change to Eventuous.Subscriptions.Logging can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Subscriptions.Logging uses a module listed above it, which is the healthy direction.
11→18 Eventuous.Subscriptions.Logging uses Eventuous.Subscriptions.Checkpoints part of a loop✕
- Connections
- 4 pairs of types, where a type in Eventuous.Subscriptions.Logging uses a type in Eventuous.Subscriptions.Checkpoints.
- The types involved
Eventuous.Subscriptions.Logging.→Eventuous.Subscriptions.Checkpoints.CommitPositionEventuous.Subscriptions.Logging.CheckpointLogging→Eventuous.Subscriptions.Checkpoints.CheckpointEventuous.Subscriptions.Logging.CheckpointLogging→Eventuous.Subscriptions.Checkpoints.CommitPositionEventuous.Subscriptions.Logging.CheckpointLogging→Eventuous.Subscriptions.Checkpoints.ICheckpointStore
- Direction
- Eventuous.Subscriptions.Logging uses Eventuous.Subscriptions.Checkpoints, so a change to Eventuous.Subscriptions.Checkpoints can break Eventuous.Subscriptions.Logging, while a change to Eventuous.Subscriptions.Logging can't break Eventuous.Subscriptions.Checkpoints.
- 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.
11→22 Eventuous.Subscriptions.Logging uses Eventuous.Subscriptions part of a loop✕
- Connections
- 1 pair of types, where a type in Eventuous.Subscriptions.Logging uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Subscriptions.Logging.LoggingExtensions→Eventuous.Subscriptions.DropReason
- Direction
- Eventuous.Subscriptions.Logging uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Subscriptions.Logging, while a change to Eventuous.Subscriptions.Logging can't break Eventuous.Subscriptions.
- 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.
12→1 Eventuous.Azure.ServiceBus.Producers uses Eventuous✕
- Connections
- 5 pairs of types, where a type in Eventuous.Azure.ServiceBus.Producers uses a type in Eventuous.
- The types involved
Eventuous.Azure.ServiceBus.Producers.ServiceBusMessageBatchBuilder→Eventuous.IEventSerializerEventuous.Azure.ServiceBus.Producers.ServiceBusMessageBatchBuilder→Eventuous.StreamNameEventuous.Azure.ServiceBus.Producers.ServiceBusMessageBuilder→Eventuous.IEventSerializerEventuous.Azure.ServiceBus.Producers.ServiceBusProducer→Eventuous.IEventSerializerEventuous.Azure.ServiceBus.Producers.ServiceBusProducer→Eventuous.StreamName
- Direction
- Eventuous.Azure.ServiceBus.Producers uses Eventuous, so a change to Eventuous can break Eventuous.Azure.ServiceBus.Producers, while a change to Eventuous.Azure.ServiceBus.Producers can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Azure.ServiceBus.Producers uses a module listed above it, which is the healthy direction.
12→6 Eventuous.Azure.ServiceBus.Producers uses Eventuous.Producers.Diagnostics✕
- Connections
- 1 pair of types, where a type in Eventuous.Azure.ServiceBus.Producers uses a type in Eventuous.Producers.Diagnostics.
- The types involved
Eventuous.Azure.ServiceBus.Producers.ServiceBusProducer→Eventuous.Producers.Diagnostics.ProducerTracingOptions
- Direction
- Eventuous.Azure.ServiceBus.Producers uses Eventuous.Producers.Diagnostics, so a change to Eventuous.Producers.Diagnostics can break Eventuous.Azure.ServiceBus.Producers, while a change to Eventuous.Azure.ServiceBus.Producers can't break Eventuous.Producers.Diagnostics.
- Position
- Below the diagonal: Eventuous.Azure.ServiceBus.Producers uses a module listed above it, which is the healthy direction.
12→10 Eventuous.Azure.ServiceBus.Producers uses Eventuous.Producers✕
- Connections
- 5 pairs of types, where a type in Eventuous.Azure.ServiceBus.Producers uses a type in Eventuous.Producers.
- The types involved
Eventuous.Azure.ServiceBus.Producers.ServiceBusMessageBatchBuilder→Eventuous.Producers.ProducedMessageEventuous.Azure.ServiceBus.Producers.ServiceBusMessageBuilder→Eventuous.Producers.ProducedMessageEventuous.Azure.ServiceBus.Producers.ServiceBusProducer→Eventuous.Producers.BaseProducerEventuous.Azure.ServiceBus.Producers.ServiceBusProducer→Eventuous.Producers.IHostedProducerEventuous.Azure.ServiceBus.Producers.ServiceBusProducer→Eventuous.Producers.ProducedMessage
- Direction
- Eventuous.Azure.ServiceBus.Producers uses Eventuous.Producers, so a change to Eventuous.Producers can break Eventuous.Azure.ServiceBus.Producers, while a change to Eventuous.Azure.ServiceBus.Producers can't break Eventuous.Producers.
- Position
- Below the diagonal: Eventuous.Azure.ServiceBus.Producers uses a module listed above it, which is the healthy direction.
13→1 Eventuous.ElasticSearch.Producers uses Eventuous✕
- Connections
- 1 pair of types, where a type in Eventuous.ElasticSearch.Producers uses a type in Eventuous.
- The types involved
Eventuous.ElasticSearch.Producers.ElasticProducer→Eventuous.StreamName
- Direction
- Eventuous.ElasticSearch.Producers uses Eventuous, so a change to Eventuous can break Eventuous.ElasticSearch.Producers, while a change to Eventuous.ElasticSearch.Producers can't break Eventuous.
- Position
- Below the diagonal: Eventuous.ElasticSearch.Producers uses a module listed above it, which is the healthy direction.
13→6 Eventuous.ElasticSearch.Producers uses Eventuous.Producers.Diagnostics✕
- Connections
- 1 pair of types, where a type in Eventuous.ElasticSearch.Producers uses a type in Eventuous.Producers.Diagnostics.
- The types involved
Eventuous.ElasticSearch.Producers.ElasticProducer→Eventuous.Producers.Diagnostics.ProducerTracingOptions
- Direction
- Eventuous.ElasticSearch.Producers uses Eventuous.Producers.Diagnostics, so a change to Eventuous.Producers.Diagnostics can break Eventuous.ElasticSearch.Producers, while a change to Eventuous.ElasticSearch.Producers can't break Eventuous.Producers.Diagnostics.
- Position
- Below the diagonal: Eventuous.ElasticSearch.Producers uses a module listed above it, which is the healthy direction.
13→10 Eventuous.ElasticSearch.Producers uses Eventuous.Producers✕
- Connections
- 2 pairs of types, where a type in Eventuous.ElasticSearch.Producers uses a type in Eventuous.Producers.
- The types involved
Eventuous.ElasticSearch.Producers.ElasticProducer→Eventuous.Producers.BaseProducerEventuous.ElasticSearch.Producers.ElasticProducer→Eventuous.Producers.ProducedMessage
- Direction
- Eventuous.ElasticSearch.Producers uses Eventuous.Producers, so a change to Eventuous.Producers can break Eventuous.ElasticSearch.Producers, while a change to Eventuous.ElasticSearch.Producers can't break Eventuous.Producers.
- Position
- Below the diagonal: Eventuous.ElasticSearch.Producers uses a module listed above it, which is the healthy direction.
14→1 Eventuous.GooglePubSub.Producers uses Eventuous✕
- Connections
- 2 pairs of types, where a type in Eventuous.GooglePubSub.Producers uses a type in Eventuous.
- The types involved
Eventuous.GooglePubSub.Producers.GooglePubSubProducer→Eventuous.IEventSerializerEventuous.GooglePubSub.Producers.GooglePubSubProducer→Eventuous.StreamName
- Direction
- Eventuous.GooglePubSub.Producers uses Eventuous, so a change to Eventuous can break Eventuous.GooglePubSub.Producers, while a change to Eventuous.GooglePubSub.Producers can't break Eventuous.
- Position
- Below the diagonal: Eventuous.GooglePubSub.Producers uses a module listed above it, which is the healthy direction.
14→2 Eventuous.GooglePubSub.Producers uses Eventuous.GooglePubSub✕
- Connections
- 2 pairs of types, where a type in Eventuous.GooglePubSub.Producers uses a type in Eventuous.GooglePubSub.
- The types involved
Eventuous.GooglePubSub.Producers.GooglePubSubProducer→Eventuous.GooglePubSub.PubSubAttributesEventuous.GooglePubSub.Producers.PubSubProducerOptions→Eventuous.GooglePubSub.PubSubAttributes
- Direction
- Eventuous.GooglePubSub.Producers uses Eventuous.GooglePubSub, so a change to Eventuous.GooglePubSub can break Eventuous.GooglePubSub.Producers, while a change to Eventuous.GooglePubSub.Producers can't break Eventuous.GooglePubSub.
- Position
- Below the diagonal: Eventuous.GooglePubSub.Producers uses a module listed above it, which is the healthy direction.
14→6 Eventuous.GooglePubSub.Producers uses Eventuous.Producers.Diagnostics✕
- Connections
- 1 pair of types, where a type in Eventuous.GooglePubSub.Producers uses a type in Eventuous.Producers.Diagnostics.
- The types involved
Eventuous.GooglePubSub.Producers.GooglePubSubProducer→Eventuous.Producers.Diagnostics.ProducerTracingOptions
- Direction
- Eventuous.GooglePubSub.Producers uses Eventuous.Producers.Diagnostics, so a change to Eventuous.Producers.Diagnostics can break Eventuous.GooglePubSub.Producers, while a change to Eventuous.GooglePubSub.Producers can't break Eventuous.Producers.Diagnostics.
- Position
- Below the diagonal: Eventuous.GooglePubSub.Producers uses a module listed above it, which is the healthy direction.
14→10 Eventuous.GooglePubSub.Producers uses Eventuous.Producers✕
- Connections
- 3 pairs of types, where a type in Eventuous.GooglePubSub.Producers uses a type in Eventuous.Producers.
- The types involved
Eventuous.GooglePubSub.Producers.GooglePubSubProducer→Eventuous.Producers.BaseProducerEventuous.GooglePubSub.Producers.GooglePubSubProducer→Eventuous.Producers.IHostedProducerEventuous.GooglePubSub.Producers.GooglePubSubProducer→Eventuous.Producers.ProducedMessage
- Direction
- Eventuous.GooglePubSub.Producers uses Eventuous.Producers, so a change to Eventuous.Producers can break Eventuous.GooglePubSub.Producers, while a change to Eventuous.GooglePubSub.Producers can't break Eventuous.Producers.
- Position
- Below the diagonal: Eventuous.GooglePubSub.Producers uses a module listed above it, which is the healthy direction.
15→1 Eventuous.Kafka.Producers uses Eventuous✕
- Connections
- 2 pairs of types, where a type in Eventuous.Kafka.Producers uses a type in Eventuous.
- The types involved
Eventuous.Kafka.Producers.KafkaBasicProducer→Eventuous.IEventSerializerEventuous.Kafka.Producers.KafkaBasicProducer→Eventuous.StreamName
- Direction
- Eventuous.Kafka.Producers uses Eventuous, so a change to Eventuous can break Eventuous.Kafka.Producers, while a change to Eventuous.Kafka.Producers can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Kafka.Producers uses a module listed above it, which is the healthy direction.
15→6 Eventuous.Kafka.Producers uses Eventuous.Producers.Diagnostics✕
- Connections
- 1 pair of types, where a type in Eventuous.Kafka.Producers uses a type in Eventuous.Producers.Diagnostics.
- The types involved
Eventuous.Kafka.Producers.KafkaBasicProducer→Eventuous.Producers.Diagnostics.ProducerTracingOptions
- Direction
- Eventuous.Kafka.Producers uses Eventuous.Producers.Diagnostics, so a change to Eventuous.Producers.Diagnostics can break Eventuous.Kafka.Producers, while a change to Eventuous.Kafka.Producers can't break Eventuous.Producers.Diagnostics.
- Position
- Below the diagonal: Eventuous.Kafka.Producers uses a module listed above it, which is the healthy direction.
15→10 Eventuous.Kafka.Producers uses Eventuous.Producers✕
- Connections
- 3 pairs of types, where a type in Eventuous.Kafka.Producers uses a type in Eventuous.Producers.
- The types involved
Eventuous.Kafka.Producers.KafkaBasicProducer→Eventuous.Producers.BaseProducerEventuous.Kafka.Producers.KafkaBasicProducer→Eventuous.Producers.IHostedProducerEventuous.Kafka.Producers.KafkaBasicProducer→Eventuous.Producers.ProducedMessage
- Direction
- Eventuous.Kafka.Producers uses Eventuous.Producers, so a change to Eventuous.Producers can break Eventuous.Kafka.Producers, while a change to Eventuous.Kafka.Producers can't break Eventuous.Producers.
- Position
- Below the diagonal: Eventuous.Kafka.Producers uses a module listed above it, which is the healthy direction.
16→1 Eventuous.KurrentDB.Producers uses Eventuous✕
- Connections
- 3 pairs of types, where a type in Eventuous.KurrentDB.Producers uses a type in Eventuous.
- The types involved
Eventuous.KurrentDB.Producers.KurrentDBProducer→Eventuous.IEventSerializerEventuous.KurrentDB.Producers.KurrentDBProducer→Eventuous.IMetadataSerializerEventuous.KurrentDB.Producers.KurrentDBProducer→Eventuous.StreamName
- Direction
- Eventuous.KurrentDB.Producers uses Eventuous, so a change to Eventuous can break Eventuous.KurrentDB.Producers, while a change to Eventuous.KurrentDB.Producers can't break Eventuous.
- Position
- Below the diagonal: Eventuous.KurrentDB.Producers uses a module listed above it, which is the healthy direction.
16→6 Eventuous.KurrentDB.Producers uses Eventuous.Producers.Diagnostics✕
- Connections
- 1 pair of types, where a type in Eventuous.KurrentDB.Producers uses a type in Eventuous.Producers.Diagnostics.
- The types involved
Eventuous.KurrentDB.Producers.KurrentDBProducer→Eventuous.Producers.Diagnostics.ProducerTracingOptions
- Direction
- Eventuous.KurrentDB.Producers uses Eventuous.Producers.Diagnostics, so a change to Eventuous.Producers.Diagnostics can break Eventuous.KurrentDB.Producers, while a change to Eventuous.KurrentDB.Producers can't break Eventuous.Producers.Diagnostics.
- Position
- Below the diagonal: Eventuous.KurrentDB.Producers uses a module listed above it, which is the healthy direction.
16→10 Eventuous.KurrentDB.Producers uses Eventuous.Producers✕
- Connections
- 2 pairs of types, where a type in Eventuous.KurrentDB.Producers uses a type in Eventuous.Producers.
- The types involved
Eventuous.KurrentDB.Producers.KurrentDBProducer→Eventuous.Producers.BaseProducerEventuous.KurrentDB.Producers.KurrentDBProducer→Eventuous.Producers.ProducedMessage
- Direction
- Eventuous.KurrentDB.Producers uses Eventuous.Producers, so a change to Eventuous.Producers can break Eventuous.KurrentDB.Producers, while a change to Eventuous.KurrentDB.Producers can't break Eventuous.Producers.
- Position
- Below the diagonal: Eventuous.KurrentDB.Producers uses a module listed above it, which is the healthy direction.
17→1 Eventuous.RabbitMq.Producers uses Eventuous✕
- Connections
- 2 pairs of types, where a type in Eventuous.RabbitMq.Producers uses a type in Eventuous.
- The types involved
Eventuous.RabbitMq.Producers.RabbitMqProducer→Eventuous.IEventSerializerEventuous.RabbitMq.Producers.RabbitMqProducer→Eventuous.StreamName
- Direction
- Eventuous.RabbitMq.Producers uses Eventuous, so a change to Eventuous can break Eventuous.RabbitMq.Producers, while a change to Eventuous.RabbitMq.Producers can't break Eventuous.
- Position
- Below the diagonal: Eventuous.RabbitMq.Producers uses a module listed above it, which is the healthy direction.
17→6 Eventuous.RabbitMq.Producers uses Eventuous.Producers.Diagnostics✕
- Connections
- 1 pair of types, where a type in Eventuous.RabbitMq.Producers uses a type in Eventuous.Producers.Diagnostics.
- The types involved
Eventuous.RabbitMq.Producers.RabbitMqProducer→Eventuous.Producers.Diagnostics.ProducerTracingOptions
- Direction
- Eventuous.RabbitMq.Producers uses Eventuous.Producers.Diagnostics, so a change to Eventuous.Producers.Diagnostics can break Eventuous.RabbitMq.Producers, while a change to Eventuous.RabbitMq.Producers can't break Eventuous.Producers.Diagnostics.
- Position
- Below the diagonal: Eventuous.RabbitMq.Producers uses a module listed above it, which is the healthy direction.
17→10 Eventuous.RabbitMq.Producers uses Eventuous.Producers✕
- Connections
- 3 pairs of types, where a type in Eventuous.RabbitMq.Producers uses a type in Eventuous.Producers.
- The types involved
Eventuous.RabbitMq.Producers.RabbitMqProducer→Eventuous.Producers.BaseProducerEventuous.RabbitMq.Producers.RabbitMqProducer→Eventuous.Producers.IHostedProducerEventuous.RabbitMq.Producers.RabbitMqProducer→Eventuous.Producers.ProducedMessage
- Direction
- Eventuous.RabbitMq.Producers uses Eventuous.Producers, so a change to Eventuous.Producers can break Eventuous.RabbitMq.Producers, while a change to Eventuous.RabbitMq.Producers can't break Eventuous.Producers.
- Position
- Below the diagonal: Eventuous.RabbitMq.Producers uses a module listed above it, which is the healthy direction.
18→11 Eventuous.Subscriptions.Checkpoints uses Eventuous.Subscriptions.Logging✕
- Connections
- 1 pair of types, where a type in Eventuous.Subscriptions.Checkpoints uses a type in Eventuous.Subscriptions.Logging.
- The types involved
Eventuous.Subscriptions.Checkpoints.CommitPosition→Eventuous.Subscriptions.Logging.LogContext
- Direction
- Eventuous.Subscriptions.Checkpoints uses Eventuous.Subscriptions.Logging, so a change to Eventuous.Subscriptions.Logging can break Eventuous.Subscriptions.Checkpoints, while a change to Eventuous.Subscriptions.Checkpoints can't break Eventuous.Subscriptions.Logging.
- Position
- Below the diagonal: Eventuous.Subscriptions.Checkpoints uses a module listed above it, which is the healthy direction.
19→8 Eventuous.Subscriptions.Consumers uses Eventuous.Subscriptions.Context✕
- Connections
- 2 pairs of types, where a type in Eventuous.Subscriptions.Consumers uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Subscriptions.Consumers.DefaultConsumer→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.Consumers.MessageConsumeContextConverter→Eventuous.Subscriptions.Context.IMessageConsumeContext
- Direction
- Eventuous.Subscriptions.Consumers uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Subscriptions.Consumers, while a change to Eventuous.Subscriptions.Consumers can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Subscriptions.Consumers uses a module listed above it, which is the healthy direction.
19→11 Eventuous.Subscriptions.Consumers uses Eventuous.Subscriptions.Logging✕
- Connections
- 1 pair of types, where a type in Eventuous.Subscriptions.Consumers uses a type in Eventuous.Subscriptions.Logging.
- The types involved
Eventuous.Subscriptions.Consumers.MessageConsumeContextConverter→Eventuous.Subscriptions.Logging.InternalLogger
- Direction
- Eventuous.Subscriptions.Consumers uses Eventuous.Subscriptions.Logging, so a change to Eventuous.Subscriptions.Logging can break Eventuous.Subscriptions.Consumers, while a change to Eventuous.Subscriptions.Consumers can't break Eventuous.Subscriptions.Logging.
- Position
- Below the diagonal: Eventuous.Subscriptions.Consumers uses a module listed above it, which is the healthy direction.
19→22 Eventuous.Subscriptions.Consumers uses Eventuous.Subscriptions part of a loop✕
- Connections
- 1 pair of types, where a type in Eventuous.Subscriptions.Consumers uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Subscriptions.Consumers.DefaultConsumer→Eventuous.Subscriptions.IEventHandler
- Direction
- Eventuous.Subscriptions.Consumers uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Subscriptions.Consumers, while a change to Eventuous.Subscriptions.Consumers can't break Eventuous.Subscriptions.
- 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.
20→4 Eventuous.Subscriptions.Diagnostics uses Eventuous.Diagnostics.Metrics✕
- Connections
- 1 pair of types, where a type in Eventuous.Subscriptions.Diagnostics uses a type in Eventuous.Diagnostics.Metrics.
- The types involved
Eventuous.Subscriptions.Diagnostics.SubscriptionMetrics→Eventuous.Diagnostics.Metrics.MetricsListener
- Direction
- Eventuous.Subscriptions.Diagnostics uses Eventuous.Diagnostics.Metrics, so a change to Eventuous.Diagnostics.Metrics can break Eventuous.Subscriptions.Diagnostics, while a change to Eventuous.Subscriptions.Diagnostics can't break Eventuous.Diagnostics.Metrics.
- Position
- Below the diagonal: Eventuous.Subscriptions.Diagnostics uses a module listed above it, which is the healthy direction.
20→8 Eventuous.Subscriptions.Diagnostics uses Eventuous.Subscriptions.Context✕
- Connections
- 3 pairs of types, where a type in Eventuous.Subscriptions.Diagnostics uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Subscriptions.Diagnostics.SubscriptionActivity→Eventuous.Subscriptions.Context.IBaseConsumeContextEventuous.Subscriptions.Diagnostics.SubscriptionActivity→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.Diagnostics.SubscriptionMetricsContext→Eventuous.Subscriptions.Context.IMessageConsumeContext
- Direction
- Eventuous.Subscriptions.Diagnostics uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Subscriptions.Diagnostics, while a change to Eventuous.Subscriptions.Diagnostics can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Subscriptions.Diagnostics uses a module listed above it, which is the healthy direction.
20→9 Eventuous.Subscriptions.Diagnostics uses Eventuous.Diagnostics✕
- Connections
- 2 pairs of types, where a type in Eventuous.Subscriptions.Diagnostics uses a type in Eventuous.Diagnostics.
- The types involved
Eventuous.Subscriptions.Diagnostics.CheckpointCommitMetrics→Eventuous.Diagnostics.GenericListenerEventuous.Subscriptions.Diagnostics.SubscriptionMetrics→Eventuous.Diagnostics.IWithCustomTags
- Direction
- Eventuous.Subscriptions.Diagnostics uses Eventuous.Diagnostics, so a change to Eventuous.Diagnostics can break Eventuous.Subscriptions.Diagnostics, while a change to Eventuous.Subscriptions.Diagnostics can't break Eventuous.Diagnostics.
- Position
- Below the diagonal: Eventuous.Subscriptions.Diagnostics uses a module listed above it, which is the healthy direction.
20→18 Eventuous.Subscriptions.Diagnostics uses Eventuous.Subscriptions.Checkpoints✕
- Connections
- 2 pairs of types, where a type in Eventuous.Subscriptions.Diagnostics uses a type in Eventuous.Subscriptions.Checkpoints.
- The types involved
Eventuous.Subscriptions.Diagnostics.CheckpointCommitMetrics→Eventuous.Subscriptions.Checkpoints.CommitEventEventuous.Subscriptions.Diagnostics.SubscriptionsEventSource→Eventuous.Subscriptions.Checkpoints.CommitPosition
- Direction
- Eventuous.Subscriptions.Diagnostics uses Eventuous.Subscriptions.Checkpoints, so a change to Eventuous.Subscriptions.Checkpoints can break Eventuous.Subscriptions.Diagnostics, while a change to Eventuous.Subscriptions.Diagnostics can't break Eventuous.Subscriptions.Checkpoints.
- Position
- Below the diagonal: Eventuous.Subscriptions.Diagnostics uses a module listed above it, which is the healthy direction.
21→8 Eventuous.Subscriptions.Filters uses Eventuous.Subscriptions.Context✕
- Connections
- 10 pairs of types, where a type in Eventuous.Subscriptions.Filters uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Subscriptions.Filters.AsyncHandlingFilter→Eventuous.Subscriptions.Context.AsyncConsumeContextEventuous.Subscriptions.Filters.ConsumeFilter→Eventuous.Subscriptions.Context.IBaseConsumeContextEventuous.Subscriptions.Filters.ConsumePipe→Eventuous.Subscriptions.Context.IBaseConsumeContextEventuous.Subscriptions.Filters.ConsumerFilter→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.Filters.FilterMessage→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.Filters.IConsumeFilter→Eventuous.Subscriptions.Context.IBaseConsumeContextEventuous.Subscriptions.Filters.MessageFilter→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.Filters.PartitioningFilter→Eventuous.Subscriptions.Context.AsyncConsumeContextEventuous.Subscriptions.Filters.TracingFilter→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.Filters.WorkerTask→Eventuous.Subscriptions.Context.AsyncConsumeContext
- Direction
- Eventuous.Subscriptions.Filters uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Subscriptions.Filters, while a change to Eventuous.Subscriptions.Filters can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Subscriptions.Filters uses a module listed above it, which is the healthy direction.
21→19 Eventuous.Subscriptions.Filters uses Eventuous.Subscriptions.Consumers✕
- Connections
- 1 pair of types, where a type in Eventuous.Subscriptions.Filters uses a type in Eventuous.Subscriptions.Consumers.
- The types involved
Eventuous.Subscriptions.Filters.ConsumerFilter→Eventuous.Subscriptions.Consumers.IMessageConsumer
- Direction
- Eventuous.Subscriptions.Filters uses Eventuous.Subscriptions.Consumers, so a change to Eventuous.Subscriptions.Consumers can break Eventuous.Subscriptions.Filters, while a change to Eventuous.Subscriptions.Filters can't break Eventuous.Subscriptions.Consumers.
- Position
- Below the diagonal: Eventuous.Subscriptions.Filters uses a module listed above it, which is the healthy direction.
21→22 Eventuous.Subscriptions.Filters uses Eventuous.Subscriptions part of a loop✕
- Connections
- 1 pair of types, where a type in Eventuous.Subscriptions.Filters uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Subscriptions.Filters.ConsumePipeExtensions→Eventuous.Subscriptions.IEventHandler
- Direction
- Eventuous.Subscriptions.Filters uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Subscriptions.Filters, while a change to Eventuous.Subscriptions.Filters can't break Eventuous.Subscriptions.
- 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.
22→1 Eventuous.Subscriptions uses Eventuous✕
- Connections
- 6 pairs of types, where a type in Eventuous.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.Subscriptions.EventHandler→Eventuous.ITypeMapperEventuous.Subscriptions.EventSubscription→Eventuous.IEventSerializerEventuous.Subscriptions.EventSubscriptionWithCheckpoint→Eventuous.IEventSerializerEventuous.Subscriptions.EventSubscriptionWithCheckpoint→Eventuous.IMetadataSerializerEventuous.Subscriptions.MetaSerializerExtensions→Eventuous.IMetadataSerializerEventuous.Subscriptions.MetaSerializerExtensions→Eventuous.Metadata
- Direction
- Eventuous.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.Subscriptions, while a change to Eventuous.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Subscriptions uses a module listed above it, which is the healthy direction.
22→8 Eventuous.Subscriptions uses Eventuous.Subscriptions.Context✕
- Connections
- 11 pairs of types, where a type in Eventuous.Subscriptions uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Subscriptions.BaseEventHandler→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.CheckpointedRun→Eventuous.Subscriptions.Context.AcknowledgeEventuous.Subscriptions.CheckpointedRun→Eventuous.Subscriptions.Context.FailEventuous.Subscriptions.EventHandler→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.EventPosition→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.EventSubscription→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.EventSubscriptionWithCheckpoint→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.HandleTypedEvent→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.Subscriptions.HandleUntypedEvent→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.IEventHandler→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Subscriptions.TracedEventHandler→Eventuous.Subscriptions.Context.IMessageConsumeContext
- Direction
- Eventuous.Subscriptions uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Subscriptions, while a change to Eventuous.Subscriptions can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Subscriptions uses a module listed above it, which is the healthy direction.
22→11 Eventuous.Subscriptions uses Eventuous.Subscriptions.Logging✕
- Connections
- 3 pairs of types, where a type in Eventuous.Subscriptions uses a type in Eventuous.Subscriptions.Logging.
- The types involved
Eventuous.Subscriptions.EventSubscription→Eventuous.Subscriptions.Logging.LogContextEventuous.Subscriptions.SubscriptionRun→Eventuous.Subscriptions.Logging.LogContextEventuous.Subscriptions.SupervisorSettings→Eventuous.Subscriptions.Logging.LogContext
- Direction
- Eventuous.Subscriptions uses Eventuous.Subscriptions.Logging, so a change to Eventuous.Subscriptions.Logging can break Eventuous.Subscriptions, while a change to Eventuous.Subscriptions can't break Eventuous.Subscriptions.Logging.
- Position
- Below the diagonal: Eventuous.Subscriptions uses a module listed above it, which is the healthy direction.
22→18 Eventuous.Subscriptions uses Eventuous.Subscriptions.Checkpoints✕
- Connections
- 4 pairs of types, where a type in Eventuous.Subscriptions uses a type in Eventuous.Subscriptions.Checkpoints.
- The types involved
Eventuous.Subscriptions.CheckpointedRun→Eventuous.Subscriptions.Checkpoints.CheckpointCommitHandlerEventuous.Subscriptions.EventSubscriptionWithCheckpoint→Eventuous.Subscriptions.Checkpoints.CheckpointEventuous.Subscriptions.EventSubscriptionWithCheckpoint→Eventuous.Subscriptions.Checkpoints.CheckpointCommitHandlerEventuous.Subscriptions.EventSubscriptionWithCheckpoint→Eventuous.Subscriptions.Checkpoints.ICheckpointStore
- Direction
- Eventuous.Subscriptions uses Eventuous.Subscriptions.Checkpoints, so a change to Eventuous.Subscriptions.Checkpoints can break Eventuous.Subscriptions, while a change to Eventuous.Subscriptions can't break Eventuous.Subscriptions.Checkpoints.
- Position
- Below the diagonal: Eventuous.Subscriptions uses a module listed above it, which is the healthy direction.
22→20 Eventuous.Subscriptions uses Eventuous.Subscriptions.Diagnostics✕
- Connections
- 2 pairs of types, where a type in Eventuous.Subscriptions uses a type in Eventuous.Subscriptions.Diagnostics.
- The types involved
Eventuous.Subscriptions.IMeasuredSubscription→Eventuous.Subscriptions.Diagnostics.GetSubscriptionEndOfStreamEventuous.Subscriptions.SubscriptionHostedService→Eventuous.Subscriptions.Diagnostics.ISubscriptionHealth
- Direction
- Eventuous.Subscriptions uses Eventuous.Subscriptions.Diagnostics, so a change to Eventuous.Subscriptions.Diagnostics can break Eventuous.Subscriptions, while a change to Eventuous.Subscriptions can't break Eventuous.Subscriptions.Diagnostics.
- Position
- Below the diagonal: Eventuous.Subscriptions uses a module listed above it, which is the healthy direction.
22→21 Eventuous.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 2 pairs of types, where a type in Eventuous.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.Subscriptions.EventSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.Subscriptions.EventSubscriptionWithCheckpoint→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.Subscriptions, while a change to Eventuous.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.Subscriptions uses a module listed above it, which is the healthy direction.
23→1 Eventuous.Azure.ServiceBus.Subscriptions uses Eventuous✕
- Connections
- 2 pairs of types, where a type in Eventuous.Azure.ServiceBus.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.Azure.ServiceBus.Subscriptions.ServiceBusSubscription→Eventuous.IEventSerializerEventuous.Azure.ServiceBus.Subscriptions.ServiceBusSubscription→Eventuous.Metadata
- Direction
- Eventuous.Azure.ServiceBus.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.Azure.ServiceBus.Subscriptions, while a change to Eventuous.Azure.ServiceBus.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Azure.ServiceBus.Subscriptions uses a module listed above it, which is the healthy direction.
23→21 Eventuous.Azure.ServiceBus.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 1 pair of types, where a type in Eventuous.Azure.ServiceBus.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.Azure.ServiceBus.Subscriptions.ServiceBusSubscription→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.Azure.ServiceBus.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.Azure.ServiceBus.Subscriptions, while a change to Eventuous.Azure.ServiceBus.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.Azure.ServiceBus.Subscriptions uses a module listed above it, which is the healthy direction.
23→22 Eventuous.Azure.ServiceBus.Subscriptions uses Eventuous.Subscriptions✕
- Connections
- 6 pairs of types, where a type in Eventuous.Azure.ServiceBus.Subscriptions uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Azure.ServiceBus.Subscriptions.IServiceBusProcessorStrategy→Eventuous.Subscriptions.SubscriptionRunEventuous.Azure.ServiceBus.Subscriptions.ServiceBusSubscription→Eventuous.Subscriptions.EventSubscriptionEventuous.Azure.ServiceBus.Subscriptions.ServiceBusSubscription→Eventuous.Subscriptions.SubscriptionRunEventuous.Azure.ServiceBus.Subscriptions.ServiceBusSubscriptionOptions→Eventuous.Subscriptions.SubscriptionOptionsEventuous.Azure.ServiceBus.Subscriptions.SessionProcessorStrategy→Eventuous.Subscriptions.SubscriptionRunEventuous.Azure.ServiceBus.Subscriptions.StandardProcessorStrategy→Eventuous.Subscriptions.SubscriptionRun
- Direction
- Eventuous.Azure.ServiceBus.Subscriptions uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Azure.ServiceBus.Subscriptions, while a change to Eventuous.Azure.ServiceBus.Subscriptions can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Azure.ServiceBus.Subscriptions uses a module listed above it, which is the healthy direction.
24→1 Eventuous.Azure.Storage.Blobs uses Eventuous✕
- Connections
- 1 pair of types, where a type in Eventuous.Azure.Storage.Blobs uses a type in Eventuous.
- The types involved
Eventuous.Azure.Storage.Blobs.BlobStorageProjector→Eventuous.ITypeMapper
- Direction
- Eventuous.Azure.Storage.Blobs uses Eventuous, so a change to Eventuous can break Eventuous.Azure.Storage.Blobs, while a change to Eventuous.Azure.Storage.Blobs can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Azure.Storage.Blobs uses a module listed above it, which is the healthy direction.
24→8 Eventuous.Azure.Storage.Blobs uses Eventuous.Subscriptions.Context✕
- Connections
- 3 pairs of types, where a type in Eventuous.Azure.Storage.Blobs uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Azure.Storage.Blobs.BlobStorageProjector→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Azure.Storage.Blobs.GetBlobId→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Azure.Storage.Blobs.Handler→Eventuous.Subscriptions.Context.IMessageConsumeContext
- Direction
- Eventuous.Azure.Storage.Blobs uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Azure.Storage.Blobs, while a change to Eventuous.Azure.Storage.Blobs can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Azure.Storage.Blobs uses a module listed above it, which is the healthy direction.
24→22 Eventuous.Azure.Storage.Blobs uses Eventuous.Subscriptions✕
- Connections
- 3 pairs of types, where a type in Eventuous.Azure.Storage.Blobs uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Azure.Storage.Blobs.BlobStorageProjector→Eventuous.Subscriptions.BaseEventHandlerEventuous.Azure.Storage.Blobs.BlobStorageProjector→Eventuous.Subscriptions.EventHandlingStatusEventuous.Azure.Storage.Blobs.Handler→Eventuous.Subscriptions.EventHandlingStatus
- Direction
- Eventuous.Azure.Storage.Blobs uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Azure.Storage.Blobs, while a change to Eventuous.Azure.Storage.Blobs can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Azure.Storage.Blobs uses a module listed above it, which is the healthy direction.
25→1 Eventuous.Gateway uses Eventuous✕
- Connections
- 8 pairs of types, where a type in Eventuous.Gateway uses a type in Eventuous.
- The types involved
Eventuous.Gateway.→Eventuous.MetadataEventuous.Gateway.→Eventuous.StreamNameEventuous.Gateway.GatewayMessage→Eventuous.MetadataEventuous.Gateway.GatewayMessage→Eventuous.StreamNameEventuous.Gateway.GatewayMetaHelper→Eventuous.MetadataEventuous.Gateway.GatewayProducer→Eventuous.StreamNameEventuous.Gateway.ProducedMessageExtensions→Eventuous.MetadataEventuous.Gateway.ProducedMessageExtensions→Eventuous.StreamName
- Direction
- Eventuous.Gateway uses Eventuous, so a change to Eventuous can break Eventuous.Gateway, while a change to Eventuous.Gateway can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Gateway uses a module listed above it, which is the healthy direction.
25→8 Eventuous.Gateway uses Eventuous.Subscriptions.Context✕
- Connections
- 4 pairs of types, where a type in Eventuous.Gateway uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Gateway.GatewayHandler→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Gateway.GatewayMetaHelper→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Gateway.IGatewayTransform→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Gateway.RouteAndTransform→Eventuous.Subscriptions.Context.IMessageConsumeContext
- Direction
- Eventuous.Gateway uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Gateway, while a change to Eventuous.Gateway can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Gateway uses a module listed above it, which is the healthy direction.
25→10 Eventuous.Gateway uses Eventuous.Producers✕
- Connections
- 6 pairs of types, where a type in Eventuous.Gateway uses a type in Eventuous.Producers.
- The types involved
Eventuous.Gateway.GatewayHandler→Eventuous.Producers.IProducerEventuous.Gateway.GatewayHandlerFactory→Eventuous.Producers.IProducerEventuous.Gateway.GatewayProducer→Eventuous.Producers.IProducerEventuous.Gateway.GatewayProducer→Eventuous.Producers.ProduceRequestEventuous.Gateway.GatewayProducer→Eventuous.Producers.ProducedMessageEventuous.Gateway.ProducedMessageExtensions→Eventuous.Producers.ProducedMessage
- Direction
- Eventuous.Gateway uses Eventuous.Producers, so a change to Eventuous.Producers can break Eventuous.Gateway, while a change to Eventuous.Gateway can't break Eventuous.Producers.
- Position
- Below the diagonal: Eventuous.Gateway uses a module listed above it, which is the healthy direction.
25→22 Eventuous.Gateway uses Eventuous.Subscriptions✕
- Connections
- 3 pairs of types, where a type in Eventuous.Gateway uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Gateway.GatewayHandler→Eventuous.Subscriptions.BaseEventHandlerEventuous.Gateway.GatewayHandler→Eventuous.Subscriptions.EventHandlingStatusEventuous.Gateway.GatewayHandlerFactory→Eventuous.Subscriptions.IEventHandler
- Direction
- Eventuous.Gateway uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Gateway, while a change to Eventuous.Gateway can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Gateway uses a module listed above it, which is the healthy direction.
26→1 Eventuous.GooglePubSub.CloudRun uses Eventuous✕
- Connections
- 1 pair of types, where a type in Eventuous.GooglePubSub.CloudRun uses a type in Eventuous.
- The types involved
Eventuous.GooglePubSub.CloudRun.CloudRunPubSubSubscription→Eventuous.IEventSerializer
- Direction
- Eventuous.GooglePubSub.CloudRun uses Eventuous, so a change to Eventuous can break Eventuous.GooglePubSub.CloudRun, while a change to Eventuous.GooglePubSub.CloudRun can't break Eventuous.
- Position
- Below the diagonal: Eventuous.GooglePubSub.CloudRun uses a module listed above it, which is the healthy direction.
26→2 Eventuous.GooglePubSub.CloudRun uses Eventuous.GooglePubSub✕
- Connections
- 1 pair of types, where a type in Eventuous.GooglePubSub.CloudRun uses a type in Eventuous.GooglePubSub.
- The types involved
Eventuous.GooglePubSub.CloudRun.CloudRunPubSubSubscriptionOptions→Eventuous.GooglePubSub.PubSubAttributes
- Direction
- Eventuous.GooglePubSub.CloudRun uses Eventuous.GooglePubSub, so a change to Eventuous.GooglePubSub can break Eventuous.GooglePubSub.CloudRun, while a change to Eventuous.GooglePubSub.CloudRun can't break Eventuous.GooglePubSub.
- Position
- Below the diagonal: Eventuous.GooglePubSub.CloudRun uses a module listed above it, which is the healthy direction.
26→21 Eventuous.GooglePubSub.CloudRun uses Eventuous.Subscriptions.Filters✕
- Connections
- 1 pair of types, where a type in Eventuous.GooglePubSub.CloudRun uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.GooglePubSub.CloudRun.CloudRunPubSubSubscription→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.GooglePubSub.CloudRun uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.GooglePubSub.CloudRun, while a change to Eventuous.GooglePubSub.CloudRun can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.GooglePubSub.CloudRun uses a module listed above it, which is the healthy direction.
26→22 Eventuous.GooglePubSub.CloudRun uses Eventuous.Subscriptions✕
- Connections
- 3 pairs of types, where a type in Eventuous.GooglePubSub.CloudRun uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.GooglePubSub.CloudRun.CloudRunPubSubSubscription→Eventuous.Subscriptions.EventSubscriptionEventuous.GooglePubSub.CloudRun.CloudRunPubSubSubscription→Eventuous.Subscriptions.SubscriptionRunEventuous.GooglePubSub.CloudRun.CloudRunPubSubSubscriptionOptions→Eventuous.Subscriptions.SubscriptionOptions
- Direction
- Eventuous.GooglePubSub.CloudRun uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.GooglePubSub.CloudRun, while a change to Eventuous.GooglePubSub.CloudRun can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.GooglePubSub.CloudRun uses a module listed above it, which is the healthy direction.
27→1 Eventuous.GooglePubSub.Subscriptions uses Eventuous✕
- Connections
- 1 pair of types, where a type in Eventuous.GooglePubSub.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.GooglePubSub.Subscriptions.GooglePubSubSubscription→Eventuous.IEventSerializer
- Direction
- Eventuous.GooglePubSub.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.GooglePubSub.Subscriptions, while a change to Eventuous.GooglePubSub.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.GooglePubSub.Subscriptions uses a module listed above it, which is the healthy direction.
27→2 Eventuous.GooglePubSub.Subscriptions uses Eventuous.GooglePubSub✕
- Connections
- 1 pair of types, where a type in Eventuous.GooglePubSub.Subscriptions uses a type in Eventuous.GooglePubSub.
- The types involved
Eventuous.GooglePubSub.Subscriptions.PubSubSubscriptionOptions→Eventuous.GooglePubSub.PubSubAttributes
- Direction
- Eventuous.GooglePubSub.Subscriptions uses Eventuous.GooglePubSub, so a change to Eventuous.GooglePubSub can break Eventuous.GooglePubSub.Subscriptions, while a change to Eventuous.GooglePubSub.Subscriptions can't break Eventuous.GooglePubSub.
- Position
- Below the diagonal: Eventuous.GooglePubSub.Subscriptions uses a module listed above it, which is the healthy direction.
27→21 Eventuous.GooglePubSub.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 1 pair of types, where a type in Eventuous.GooglePubSub.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.GooglePubSub.Subscriptions.GooglePubSubSubscription→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.GooglePubSub.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.GooglePubSub.Subscriptions, while a change to Eventuous.GooglePubSub.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.GooglePubSub.Subscriptions uses a module listed above it, which is the healthy direction.
27→22 Eventuous.GooglePubSub.Subscriptions uses Eventuous.Subscriptions✕
- Connections
- 3 pairs of types, where a type in Eventuous.GooglePubSub.Subscriptions uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.GooglePubSub.Subscriptions.GooglePubSubSubscription→Eventuous.Subscriptions.EventSubscriptionEventuous.GooglePubSub.Subscriptions.GooglePubSubSubscription→Eventuous.Subscriptions.SubscriptionRunEventuous.GooglePubSub.Subscriptions.PubSubSubscriptionOptions→Eventuous.Subscriptions.SubscriptionOptions
- Direction
- Eventuous.GooglePubSub.Subscriptions uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.GooglePubSub.Subscriptions, while a change to Eventuous.GooglePubSub.Subscriptions can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.GooglePubSub.Subscriptions uses a module listed above it, which is the healthy direction.
28→1 Eventuous.Kafka.Subscriptions uses Eventuous✕
- Connections
- 1 pair of types, where a type in Eventuous.Kafka.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.Kafka.Subscriptions.KafkaBasicSubscription→Eventuous.IEventSerializer
- Direction
- Eventuous.Kafka.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.Kafka.Subscriptions, while a change to Eventuous.Kafka.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Kafka.Subscriptions uses a module listed above it, which is the healthy direction.
28→21 Eventuous.Kafka.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 1 pair of types, where a type in Eventuous.Kafka.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.Kafka.Subscriptions.KafkaBasicSubscription→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.Kafka.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.Kafka.Subscriptions, while a change to Eventuous.Kafka.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.Kafka.Subscriptions uses a module listed above it, which is the healthy direction.
28→22 Eventuous.Kafka.Subscriptions uses Eventuous.Subscriptions✕
- Connections
- 3 pairs of types, where a type in Eventuous.Kafka.Subscriptions uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Kafka.Subscriptions.KafkaBasicSubscription→Eventuous.Subscriptions.EventSubscriptionEventuous.Kafka.Subscriptions.KafkaBasicSubscription→Eventuous.Subscriptions.SubscriptionRunEventuous.Kafka.Subscriptions.KafkaSubscriptionOptions→Eventuous.Subscriptions.SubscriptionOptions
- Direction
- Eventuous.Kafka.Subscriptions uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Kafka.Subscriptions, while a change to Eventuous.Kafka.Subscriptions can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Kafka.Subscriptions uses a module listed above it, which is the healthy direction.
29→1 Eventuous.KurrentDB.Subscriptions uses Eventuous✕
- Connections
- 16 pairs of types, where a type in Eventuous.KurrentDB.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.KurrentDB.Subscriptions.AllPersistentSubscription→Eventuous.IEventSerializerEventuous.KurrentDB.Subscriptions.AllPersistentSubscription→Eventuous.IMetadataSerializerEventuous.KurrentDB.Subscriptions.AllStreamSubscription→Eventuous.IEventSerializerEventuous.KurrentDB.Subscriptions.AllStreamSubscription→Eventuous.IMetadataSerializerEventuous.KurrentDB.Subscriptions.KurrentDBCatchUpSubscriptionBase→Eventuous.IEventSerializerEventuous.KurrentDB.Subscriptions.KurrentDBCatchUpSubscriptionBase→Eventuous.IMetadataSerializerEventuous.KurrentDB.Subscriptions.PersistentSubscriptionBase→Eventuous.IEventSerializerEventuous.KurrentDB.Subscriptions.PersistentSubscriptionBase→Eventuous.IMetadataSerializerEventuous.KurrentDB.Subscriptions.StreamPersistentSubscription→Eventuous.IEventSerializerEventuous.KurrentDB.Subscriptions.StreamPersistentSubscription→Eventuous.IMetadataSerializerEventuous.KurrentDB.Subscriptions.StreamPersistentSubscription→Eventuous.StreamNameEventuous.KurrentDB.Subscriptions.StreamPersistentSubscriptionOptions→Eventuous.StreamNameEventuous.KurrentDB.Subscriptions.StreamSubscription→Eventuous.IEventSerializerEventuous.KurrentDB.Subscriptions.StreamSubscription→Eventuous.IMetadataSerializerEventuous.KurrentDB.Subscriptions.StreamSubscription→Eventuous.StreamNameEventuous.KurrentDB.Subscriptions.StreamSubscriptionOptions→Eventuous.StreamName
- Direction
- Eventuous.KurrentDB.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.KurrentDB.Subscriptions, while a change to Eventuous.KurrentDB.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.KurrentDB.Subscriptions uses a module listed above it, which is the healthy direction.
29→8 Eventuous.KurrentDB.Subscriptions uses Eventuous.Subscriptions.Context✕
- Connections
- 3 pairs of types, where a type in Eventuous.KurrentDB.Subscriptions uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.KurrentDB.Subscriptions.AllStreamSubscription→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.KurrentDB.Subscriptions.PersistentSubscriptionBase→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.KurrentDB.Subscriptions.StreamSubscription→Eventuous.Subscriptions.Context.MessageConsumeContext
- Direction
- Eventuous.KurrentDB.Subscriptions uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.KurrentDB.Subscriptions, while a change to Eventuous.KurrentDB.Subscriptions can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.KurrentDB.Subscriptions uses a module listed above it, which is the healthy direction.
29→18 Eventuous.KurrentDB.Subscriptions uses Eventuous.Subscriptions.Checkpoints✕
- Connections
- 3 pairs of types, where a type in Eventuous.KurrentDB.Subscriptions uses a type in Eventuous.Subscriptions.Checkpoints.
- The types involved
Eventuous.KurrentDB.Subscriptions.AllStreamSubscription→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.KurrentDB.Subscriptions.KurrentDBCatchUpSubscriptionBase→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.KurrentDB.Subscriptions.StreamSubscription→Eventuous.Subscriptions.Checkpoints.ICheckpointStore
- Direction
- Eventuous.KurrentDB.Subscriptions uses Eventuous.Subscriptions.Checkpoints, so a change to Eventuous.Subscriptions.Checkpoints can break Eventuous.KurrentDB.Subscriptions, while a change to Eventuous.KurrentDB.Subscriptions can't break Eventuous.Subscriptions.Checkpoints.
- Position
- Below the diagonal: Eventuous.KurrentDB.Subscriptions uses a module listed above it, which is the healthy direction.
29→20 Eventuous.KurrentDB.Subscriptions uses Eventuous.Subscriptions.Diagnostics✕
- Connections
- 4 pairs of types, where a type in Eventuous.KurrentDB.Subscriptions uses a type in Eventuous.Subscriptions.Diagnostics.
- The types involved
Eventuous.KurrentDB.Subscriptions.AllPersistentSubscription→Eventuous.Subscriptions.Diagnostics.GetSubscriptionEndOfStreamEventuous.KurrentDB.Subscriptions.AllStreamSubscription→Eventuous.Subscriptions.Diagnostics.GetSubscriptionEndOfStreamEventuous.KurrentDB.Subscriptions.StreamPersistentSubscription→Eventuous.Subscriptions.Diagnostics.GetSubscriptionEndOfStreamEventuous.KurrentDB.Subscriptions.StreamSubscription→Eventuous.Subscriptions.Diagnostics.GetSubscriptionEndOfStream
- Direction
- Eventuous.KurrentDB.Subscriptions uses Eventuous.Subscriptions.Diagnostics, so a change to Eventuous.Subscriptions.Diagnostics can break Eventuous.KurrentDB.Subscriptions, while a change to Eventuous.KurrentDB.Subscriptions can't break Eventuous.Subscriptions.Diagnostics.
- Position
- Below the diagonal: Eventuous.KurrentDB.Subscriptions uses a module listed above it, which is the healthy direction.
29→21 Eventuous.KurrentDB.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 7 pairs of types, where a type in Eventuous.KurrentDB.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.KurrentDB.Subscriptions.AllPersistentSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.KurrentDB.Subscriptions.AllStreamSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.KurrentDB.Subscriptions.ConsumePipeExtensions→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.KurrentDB.Subscriptions.KurrentDBCatchUpSubscriptionBase→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.KurrentDB.Subscriptions.PersistentSubscriptionBase→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.KurrentDB.Subscriptions.StreamPersistentSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.KurrentDB.Subscriptions.StreamSubscription→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.KurrentDB.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.KurrentDB.Subscriptions, while a change to Eventuous.KurrentDB.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.KurrentDB.Subscriptions uses a module listed above it, which is the healthy direction.
29→22 Eventuous.KurrentDB.Subscriptions uses Eventuous.Subscriptions✕
- Connections
- 14 pairs of types, where a type in Eventuous.KurrentDB.Subscriptions uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.KurrentDB.Subscriptions.AllPersistentSubscription→Eventuous.Subscriptions.IMeasuredSubscriptionEventuous.KurrentDB.Subscriptions.AllStreamSubscription→Eventuous.Subscriptions.IMeasuredSubscriptionEventuous.KurrentDB.Subscriptions.AllStreamSubscription→Eventuous.Subscriptions.SubscriptionRunEventuous.KurrentDB.Subscriptions.KurrentDBCatchUpSubscriptionBase→Eventuous.Subscriptions.EventSubscriptionWithCheckpointEventuous.KurrentDB.Subscriptions.KurrentDBCatchUpSubscriptionBase→Eventuous.Subscriptions.SubscriptionKindEventuous.KurrentDB.Subscriptions.KurrentDBMappings→Eventuous.Subscriptions.DropReasonEventuous.KurrentDB.Subscriptions.KurrentDBSubscriptionOptions→Eventuous.Subscriptions.SubscriptionOptionsEventuous.KurrentDB.Subscriptions.KurrentDBSubscriptionWithCheckpointOptions→Eventuous.Subscriptions.SubscriptionWithCheckpointOptionsEventuous.KurrentDB.Subscriptions.PersistentSubscriptionBase→Eventuous.Subscriptions.EventPositionEventuous.KurrentDB.Subscriptions.PersistentSubscriptionBase→Eventuous.Subscriptions.EventSubscriptionEventuous.KurrentDB.Subscriptions.PersistentSubscriptionBase→Eventuous.Subscriptions.SubscriptionRunEventuous.KurrentDB.Subscriptions.StreamPersistentSubscription→Eventuous.Subscriptions.IMeasuredSubscriptionEventuous.KurrentDB.Subscriptions.StreamSubscription→Eventuous.Subscriptions.IMeasuredSubscriptionEventuous.KurrentDB.Subscriptions.StreamSubscription→Eventuous.Subscriptions.SubscriptionRun
- Direction
- Eventuous.KurrentDB.Subscriptions uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.KurrentDB.Subscriptions, while a change to Eventuous.KurrentDB.Subscriptions can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.KurrentDB.Subscriptions uses a module listed above it, which is the healthy direction.
30→1 Eventuous.Projections.MongoDB uses Eventuous✕
- Connections
- 4 pairs of types, where a type in Eventuous.Projections.MongoDB uses a type in Eventuous.
- The types involved
Eventuous.Projections.MongoDB.GetDocumentIdFromStream→Eventuous.StreamNameEventuous.Projections.MongoDB.InsertOneBuilder→Eventuous.StreamNameEventuous.Projections.MongoDB.MongoProjection→Eventuous.ITypeMapperEventuous.Projections.MongoDB.MongoProjector→Eventuous.ITypeMapper
- Direction
- Eventuous.Projections.MongoDB uses Eventuous, so a change to Eventuous can break Eventuous.Projections.MongoDB, while a change to Eventuous.Projections.MongoDB can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Projections.MongoDB uses a module listed above it, which is the healthy direction.
30→8 Eventuous.Projections.MongoDB uses Eventuous.Subscriptions.Context✕
- Connections
- 12 pairs of types, where a type in Eventuous.Projections.MongoDB uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Projections.MongoDB.BuildUpdateAsync→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Projections.MongoDB.BuildWriteModel→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.Projections.MongoDB.DeleteBuilder→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Projections.MongoDB.FilterBuilder→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Projections.MongoDB.GetDocumentIdFromContext→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Projections.MongoDB.InsertManyBuilder→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.Projections.MongoDB.InsertOneBuilder→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.Projections.MongoDB.MongoOperationBuilder→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.Projections.MongoDB.MongoProjector→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Projections.MongoDB.ProjectTypedEvent→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.Projections.MongoDB.ProjectUntypedEvent→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.Projections.MongoDB.UpdateBuilder→Eventuous.Subscriptions.Context.IMessageConsumeContext
- Direction
- Eventuous.Projections.MongoDB uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Projections.MongoDB, while a change to Eventuous.Projections.MongoDB can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Projections.MongoDB uses a module listed above it, which is the healthy direction.
30→18 Eventuous.Projections.MongoDB uses Eventuous.Subscriptions.Checkpoints✕
- Connections
- 3 pairs of types, where a type in Eventuous.Projections.MongoDB uses a type in Eventuous.Subscriptions.Checkpoints.
- The types involved
Eventuous.Projections.MongoDB.Checkpoint→Eventuous.Subscriptions.Checkpoints.CheckpointEventuous.Projections.MongoDB.MongoCheckpointStore→Eventuous.Subscriptions.Checkpoints.CheckpointEventuous.Projections.MongoDB.MongoCheckpointStore→Eventuous.Subscriptions.Checkpoints.ICheckpointStore
- Direction
- Eventuous.Projections.MongoDB uses Eventuous.Subscriptions.Checkpoints, so a change to Eventuous.Subscriptions.Checkpoints can break Eventuous.Projections.MongoDB, while a change to Eventuous.Projections.MongoDB can't break Eventuous.Subscriptions.Checkpoints.
- Position
- Below the diagonal: Eventuous.Projections.MongoDB uses a module listed above it, which is the healthy direction.
30→22 Eventuous.Projections.MongoDB uses Eventuous.Subscriptions✕
- Connections
- 2 pairs of types, where a type in Eventuous.Projections.MongoDB uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Projections.MongoDB.MongoProjector→Eventuous.Subscriptions.BaseEventHandlerEventuous.Projections.MongoDB.MongoProjector→Eventuous.Subscriptions.EventHandlingStatus
- Direction
- Eventuous.Projections.MongoDB uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Projections.MongoDB, while a change to Eventuous.Projections.MongoDB can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Projections.MongoDB uses a module listed above it, which is the healthy direction.
31→1 Eventuous.RabbitMq.Subscriptions uses Eventuous✕
- Connections
- 1 pair of types, where a type in Eventuous.RabbitMq.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.RabbitMq.Subscriptions.RabbitMqSubscription→Eventuous.IEventSerializer
- Direction
- Eventuous.RabbitMq.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.RabbitMq.Subscriptions, while a change to Eventuous.RabbitMq.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.RabbitMq.Subscriptions uses a module listed above it, which is the healthy direction.
31→8 Eventuous.RabbitMq.Subscriptions uses Eventuous.Subscriptions.Context✕
- Connections
- 2 pairs of types, where a type in Eventuous.RabbitMq.Subscriptions uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.RabbitMq.Subscriptions.Event→Eventuous.Subscriptions.Context.IMessageConsumeContextEventuous.RabbitMq.Subscriptions.RabbitMqSubscription→Eventuous.Subscriptions.Context.MessageConsumeContext
- Direction
- Eventuous.RabbitMq.Subscriptions uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.RabbitMq.Subscriptions, while a change to Eventuous.RabbitMq.Subscriptions can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.RabbitMq.Subscriptions uses a module listed above it, which is the healthy direction.
31→21 Eventuous.RabbitMq.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 1 pair of types, where a type in Eventuous.RabbitMq.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.RabbitMq.Subscriptions.RabbitMqSubscription→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.RabbitMq.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.RabbitMq.Subscriptions, while a change to Eventuous.RabbitMq.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.RabbitMq.Subscriptions uses a module listed above it, which is the healthy direction.
31→22 Eventuous.RabbitMq.Subscriptions uses Eventuous.Subscriptions✕
- Connections
- 3 pairs of types, where a type in Eventuous.RabbitMq.Subscriptions uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.RabbitMq.Subscriptions.RabbitMqSubscription→Eventuous.Subscriptions.EventSubscriptionEventuous.RabbitMq.Subscriptions.RabbitMqSubscription→Eventuous.Subscriptions.SubscriptionRunEventuous.RabbitMq.Subscriptions.RabbitMqSubscriptionOptions→Eventuous.Subscriptions.SubscriptionOptions
- Direction
- Eventuous.RabbitMq.Subscriptions uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.RabbitMq.Subscriptions, while a change to Eventuous.RabbitMq.Subscriptions can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.RabbitMq.Subscriptions uses a module listed above it, which is the healthy direction.
32→1 Eventuous.Redis.Subscriptions uses Eventuous✕
- Connections
- 4 pairs of types, where a type in Eventuous.Redis.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.Redis.Subscriptions.RedisStreamSubscriptionOptions→Eventuous.StreamNameEventuous.Redis.Subscriptions.RedisSubscriptionBase→Eventuous.IEventSerializerEventuous.Redis.Subscriptions.RedisSubscriptionBase→Eventuous.IMetadataSerializerEventuous.Redis.Subscriptions.RedisSubscriptionBase→Eventuous.Metadata
- Direction
- Eventuous.Redis.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.Redis.Subscriptions, while a change to Eventuous.Redis.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Redis.Subscriptions uses a module listed above it, which is the healthy direction.
32→8 Eventuous.Redis.Subscriptions uses Eventuous.Subscriptions.Context✕
- Connections
- 1 pair of types, where a type in Eventuous.Redis.Subscriptions uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Redis.Subscriptions.RedisSubscriptionBase→Eventuous.Subscriptions.Context.MessageConsumeContext
- Direction
- Eventuous.Redis.Subscriptions uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Redis.Subscriptions, while a change to Eventuous.Redis.Subscriptions can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Redis.Subscriptions uses a module listed above it, which is the healthy direction.
32→18 Eventuous.Redis.Subscriptions uses Eventuous.Subscriptions.Checkpoints✕
- Connections
- 5 pairs of types, where a type in Eventuous.Redis.Subscriptions uses a type in Eventuous.Subscriptions.Checkpoints.
- The types involved
Eventuous.Redis.Subscriptions.RedisAllStreamSubscription→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.Redis.Subscriptions.RedisCheckpointStore→Eventuous.Subscriptions.Checkpoints.CheckpointEventuous.Redis.Subscriptions.RedisCheckpointStore→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.Redis.Subscriptions.RedisStreamSubscription→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.Redis.Subscriptions.RedisSubscriptionBase→Eventuous.Subscriptions.Checkpoints.ICheckpointStore
- Direction
- Eventuous.Redis.Subscriptions uses Eventuous.Subscriptions.Checkpoints, so a change to Eventuous.Subscriptions.Checkpoints can break Eventuous.Redis.Subscriptions, while a change to Eventuous.Redis.Subscriptions can't break Eventuous.Subscriptions.Checkpoints.
- Position
- Below the diagonal: Eventuous.Redis.Subscriptions uses a module listed above it, which is the healthy direction.
32→21 Eventuous.Redis.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 3 pairs of types, where a type in Eventuous.Redis.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.Redis.Subscriptions.RedisAllStreamSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.Redis.Subscriptions.RedisStreamSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.Redis.Subscriptions.RedisSubscriptionBase→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.Redis.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.Redis.Subscriptions, while a change to Eventuous.Redis.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.Redis.Subscriptions uses a module listed above it, which is the healthy direction.
32→22 Eventuous.Redis.Subscriptions uses Eventuous.Subscriptions✕
- Connections
- 4 pairs of types, where a type in Eventuous.Redis.Subscriptions uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Redis.Subscriptions.RedisSubscriptionBase→Eventuous.Subscriptions.EventSubscriptionWithCheckpointEventuous.Redis.Subscriptions.RedisSubscriptionBase→Eventuous.Subscriptions.SubscriptionKindEventuous.Redis.Subscriptions.RedisSubscriptionBase→Eventuous.Subscriptions.SubscriptionRunEventuous.Redis.Subscriptions.RedisSubscriptionBaseOptions→Eventuous.Subscriptions.SubscriptionWithCheckpointOptions
- Direction
- Eventuous.Redis.Subscriptions uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Redis.Subscriptions, while a change to Eventuous.Redis.Subscriptions can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Redis.Subscriptions uses a module listed above it, which is the healthy direction.
33→1 Eventuous.Sql.Base.Subscriptions uses Eventuous✕
- Connections
- 3 pairs of types, where a type in Eventuous.Sql.Base.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.IEventSerializerEventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.IMetadataSerializerEventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Metadata
- Direction
- Eventuous.Sql.Base.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.Sql.Base.Subscriptions, while a change to Eventuous.Sql.Base.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Sql.Base.Subscriptions uses a module listed above it, which is the healthy direction.
33→7 Eventuous.Sql.Base.Subscriptions uses Eventuous.Sql.Base✕
- Connections
- 1 pair of types, where a type in Eventuous.Sql.Base.Subscriptions uses a type in Eventuous.Sql.Base.
- The types involved
Eventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Sql.Base.PersistedEvent
- Direction
- Eventuous.Sql.Base.Subscriptions uses Eventuous.Sql.Base, so a change to Eventuous.Sql.Base can break Eventuous.Sql.Base.Subscriptions, while a change to Eventuous.Sql.Base.Subscriptions can't break Eventuous.Sql.Base.
- Position
- Below the diagonal: Eventuous.Sql.Base.Subscriptions uses a module listed above it, which is the healthy direction.
33→8 Eventuous.Sql.Base.Subscriptions uses Eventuous.Subscriptions.Context✕
- Connections
- 1 pair of types, where a type in Eventuous.Sql.Base.Subscriptions uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Subscriptions.Context.MessageConsumeContext
- Direction
- Eventuous.Sql.Base.Subscriptions uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Sql.Base.Subscriptions, while a change to Eventuous.Sql.Base.Subscriptions can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Sql.Base.Subscriptions uses a module listed above it, which is the healthy direction.
33→18 Eventuous.Sql.Base.Subscriptions uses Eventuous.Subscriptions.Checkpoints✕
- Connections
- 1 pair of types, where a type in Eventuous.Sql.Base.Subscriptions uses a type in Eventuous.Subscriptions.Checkpoints.
- The types involved
Eventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Subscriptions.Checkpoints.ICheckpointStore
- Direction
- Eventuous.Sql.Base.Subscriptions uses Eventuous.Subscriptions.Checkpoints, so a change to Eventuous.Subscriptions.Checkpoints can break Eventuous.Sql.Base.Subscriptions, while a change to Eventuous.Sql.Base.Subscriptions can't break Eventuous.Subscriptions.Checkpoints.
- Position
- Below the diagonal: Eventuous.Sql.Base.Subscriptions uses a module listed above it, which is the healthy direction.
33→20 Eventuous.Sql.Base.Subscriptions uses Eventuous.Subscriptions.Diagnostics✕
- Connections
- 2 pairs of types, where a type in Eventuous.Sql.Base.Subscriptions uses a type in Eventuous.Subscriptions.Diagnostics.
- The types involved
Eventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Subscriptions.Diagnostics.EndOfStreamEventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Subscriptions.Diagnostics.GetSubscriptionEndOfStream
- Direction
- Eventuous.Sql.Base.Subscriptions uses Eventuous.Subscriptions.Diagnostics, so a change to Eventuous.Subscriptions.Diagnostics can break Eventuous.Sql.Base.Subscriptions, while a change to Eventuous.Sql.Base.Subscriptions can't break Eventuous.Subscriptions.Diagnostics.
- Position
- Below the diagonal: Eventuous.Sql.Base.Subscriptions uses a module listed above it, which is the healthy direction.
33→21 Eventuous.Sql.Base.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 1 pair of types, where a type in Eventuous.Sql.Base.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.Sql.Base.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.Sql.Base.Subscriptions, while a change to Eventuous.Sql.Base.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.Sql.Base.Subscriptions uses a module listed above it, which is the healthy direction.
33→22 Eventuous.Sql.Base.Subscriptions uses Eventuous.Subscriptions✕
- Connections
- 5 pairs of types, where a type in Eventuous.Sql.Base.Subscriptions uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Subscriptions.EventSubscriptionWithCheckpointEventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Subscriptions.IMeasuredSubscriptionEventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Subscriptions.SubscriptionKindEventuous.Sql.Base.Subscriptions.SqlSubscriptionBase→Eventuous.Subscriptions.SubscriptionRunEventuous.Sql.Base.Subscriptions.SqlSubscriptionOptionsBase→Eventuous.Subscriptions.SubscriptionWithCheckpointOptions
- Direction
- Eventuous.Sql.Base.Subscriptions uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Sql.Base.Subscriptions, while a change to Eventuous.Sql.Base.Subscriptions can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Sql.Base.Subscriptions uses a module listed above it, which is the healthy direction.
34→1 Eventuous.SqlServer.Projections uses Eventuous✕
- Connections
- 1 pair of types, where a type in Eventuous.SqlServer.Projections uses a type in Eventuous.
- The types involved
Eventuous.SqlServer.Projections.SqlServerProjector→Eventuous.ITypeMapper
- Direction
- Eventuous.SqlServer.Projections uses Eventuous, so a change to Eventuous can break Eventuous.SqlServer.Projections, while a change to Eventuous.SqlServer.Projections can't break Eventuous.
- Position
- Below the diagonal: Eventuous.SqlServer.Projections uses a module listed above it, which is the healthy direction.
34→8 Eventuous.SqlServer.Projections uses Eventuous.Subscriptions.Context✕
- Connections
- 3 pairs of types, where a type in Eventuous.SqlServer.Projections uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.SqlServer.Projections.ProjectToSqlServer→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.SqlServer.Projections.ProjectToSqlServerAsync→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.SqlServer.Projections.SqlServerProjector→Eventuous.Subscriptions.Context.MessageConsumeContext
- Direction
- Eventuous.SqlServer.Projections uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.SqlServer.Projections, while a change to Eventuous.SqlServer.Projections can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.SqlServer.Projections uses a module listed above it, which is the healthy direction.
34→22 Eventuous.SqlServer.Projections uses Eventuous.Subscriptions✕
- Connections
- 1 pair of types, where a type in Eventuous.SqlServer.Projections uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.SqlServer.Projections.SqlServerProjector→Eventuous.Subscriptions.EventHandler
- Direction
- Eventuous.SqlServer.Projections uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.SqlServer.Projections, while a change to Eventuous.SqlServer.Projections can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.SqlServer.Projections uses a module listed above it, which is the healthy direction.
35→1 Eventuous.Sqlite.Projections uses Eventuous✕
- Connections
- 1 pair of types, where a type in Eventuous.Sqlite.Projections uses a type in Eventuous.
- The types involved
Eventuous.Sqlite.Projections.SqliteProjector→Eventuous.ITypeMapper
- Direction
- Eventuous.Sqlite.Projections uses Eventuous, so a change to Eventuous can break Eventuous.Sqlite.Projections, while a change to Eventuous.Sqlite.Projections can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Sqlite.Projections uses a module listed above it, which is the healthy direction.
35→8 Eventuous.Sqlite.Projections uses Eventuous.Subscriptions.Context✕
- Connections
- 3 pairs of types, where a type in Eventuous.Sqlite.Projections uses a type in Eventuous.Subscriptions.Context.
- The types involved
Eventuous.Sqlite.Projections.ProjectToSqlite→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.Sqlite.Projections.ProjectToSqliteAsync→Eventuous.Subscriptions.Context.MessageConsumeContextEventuous.Sqlite.Projections.SqliteProjector→Eventuous.Subscriptions.Context.MessageConsumeContext
- Direction
- Eventuous.Sqlite.Projections uses Eventuous.Subscriptions.Context, so a change to Eventuous.Subscriptions.Context can break Eventuous.Sqlite.Projections, while a change to Eventuous.Sqlite.Projections can't break Eventuous.Subscriptions.Context.
- Position
- Below the diagonal: Eventuous.Sqlite.Projections uses a module listed above it, which is the healthy direction.
35→22 Eventuous.Sqlite.Projections uses Eventuous.Subscriptions✕
- Connections
- 1 pair of types, where a type in Eventuous.Sqlite.Projections uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Sqlite.Projections.SqliteProjector→Eventuous.Subscriptions.EventHandler
- Direction
- Eventuous.Sqlite.Projections uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Sqlite.Projections, while a change to Eventuous.Sqlite.Projections can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Sqlite.Projections uses a module listed above it, which is the healthy direction.
36→19 Eventuous.Subscriptions.Registrations uses Eventuous.Subscriptions.Consumers✕
- Connections
- 2 pairs of types, where a type in Eventuous.Subscriptions.Registrations uses a type in Eventuous.Subscriptions.Consumers.
- The types involved
Eventuous.Subscriptions.Registrations.ResolveConsumer→Eventuous.Subscriptions.Consumers.IMessageConsumerEventuous.Subscriptions.Registrations.SubscriptionBuilder→Eventuous.Subscriptions.Consumers.IMessageConsumer
- Direction
- Eventuous.Subscriptions.Registrations uses Eventuous.Subscriptions.Consumers, so a change to Eventuous.Subscriptions.Consumers can break Eventuous.Subscriptions.Registrations, while a change to Eventuous.Subscriptions.Registrations can't break Eventuous.Subscriptions.Consumers.
- Position
- Below the diagonal: Eventuous.Subscriptions.Registrations uses a module listed above it, which is the healthy direction.
36→21 Eventuous.Subscriptions.Registrations uses Eventuous.Subscriptions.Filters✕
- Connections
- 2 pairs of types, where a type in Eventuous.Subscriptions.Registrations uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.Subscriptions.Registrations.SubscriptionBuilder→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.Subscriptions.Registrations.SubscriptionBuilder→Eventuous.Subscriptions.Filters.IConsumeFilter
- Direction
- Eventuous.Subscriptions.Registrations uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.Subscriptions.Registrations, while a change to Eventuous.Subscriptions.Registrations can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.Subscriptions.Registrations uses a module listed above it, which is the healthy direction.
36→22 Eventuous.Subscriptions.Registrations uses Eventuous.Subscriptions✕
- Connections
- 2 pairs of types, where a type in Eventuous.Subscriptions.Registrations uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Subscriptions.Registrations.ResolveHandler→Eventuous.Subscriptions.IEventHandlerEventuous.Subscriptions.Registrations.SubscriptionBuilder→Eventuous.Subscriptions.IEventHandler
- Direction
- Eventuous.Subscriptions.Registrations uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Subscriptions.Registrations, while a change to Eventuous.Subscriptions.Registrations can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Subscriptions.Registrations uses a module listed above it, which is the healthy direction.
37→1 Eventuous.Postgresql.Subscriptions uses Eventuous✕
- Connections
- 7 pairs of types, where a type in Eventuous.Postgresql.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.Postgresql.Subscriptions.PostgresAllStreamSubscription→Eventuous.IEventSerializerEventuous.Postgresql.Subscriptions.PostgresAllStreamSubscription→Eventuous.IMetadataSerializerEventuous.Postgresql.Subscriptions.PostgresStreamSubscription→Eventuous.IEventSerializerEventuous.Postgresql.Subscriptions.PostgresStreamSubscription→Eventuous.IMetadataSerializerEventuous.Postgresql.Subscriptions.PostgresStreamSubscriptionOptions→Eventuous.StreamNameEventuous.Postgresql.Subscriptions.PostgresSubscriptionBase→Eventuous.IEventSerializerEventuous.Postgresql.Subscriptions.PostgresSubscriptionBase→Eventuous.IMetadataSerializer
- Direction
- Eventuous.Postgresql.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.Postgresql.Subscriptions, while a change to Eventuous.Postgresql.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Postgresql.Subscriptions uses a module listed above it, which is the healthy direction.
37→7 Eventuous.Postgresql.Subscriptions uses Eventuous.Sql.Base✕
- Connections
- 1 pair of types, where a type in Eventuous.Postgresql.Subscriptions uses a type in Eventuous.Sql.Base.
- The types involved
Eventuous.Postgresql.Subscriptions.PostgresSubscriptionBase→Eventuous.Sql.Base.PersistedEvent
- Direction
- Eventuous.Postgresql.Subscriptions uses Eventuous.Sql.Base, so a change to Eventuous.Sql.Base can break Eventuous.Postgresql.Subscriptions, while a change to Eventuous.Postgresql.Subscriptions can't break Eventuous.Sql.Base.
- Position
- Below the diagonal: Eventuous.Postgresql.Subscriptions uses a module listed above it, which is the healthy direction.
37→18 Eventuous.Postgresql.Subscriptions uses Eventuous.Subscriptions.Checkpoints✕
- Connections
- 5 pairs of types, where a type in Eventuous.Postgresql.Subscriptions uses a type in Eventuous.Subscriptions.Checkpoints.
- The types involved
Eventuous.Postgresql.Subscriptions.PostgresAllStreamSubscription→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.Postgresql.Subscriptions.PostgresCheckpointStore→Eventuous.Subscriptions.Checkpoints.CheckpointEventuous.Postgresql.Subscriptions.PostgresCheckpointStore→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.Postgresql.Subscriptions.PostgresStreamSubscription→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.Postgresql.Subscriptions.PostgresSubscriptionBase→Eventuous.Subscriptions.Checkpoints.ICheckpointStore
- Direction
- Eventuous.Postgresql.Subscriptions uses Eventuous.Subscriptions.Checkpoints, so a change to Eventuous.Subscriptions.Checkpoints can break Eventuous.Postgresql.Subscriptions, while a change to Eventuous.Postgresql.Subscriptions can't break Eventuous.Subscriptions.Checkpoints.
- Position
- Below the diagonal: Eventuous.Postgresql.Subscriptions uses a module listed above it, which is the healthy direction.
37→21 Eventuous.Postgresql.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 3 pairs of types, where a type in Eventuous.Postgresql.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.Postgresql.Subscriptions.PostgresAllStreamSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.Postgresql.Subscriptions.PostgresStreamSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.Postgresql.Subscriptions.PostgresSubscriptionBase→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.Postgresql.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.Postgresql.Subscriptions, while a change to Eventuous.Postgresql.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.Postgresql.Subscriptions uses a module listed above it, which is the healthy direction.
37→22 Eventuous.Postgresql.Subscriptions uses Eventuous.Subscriptions✕
- Connections
- 1 pair of types, where a type in Eventuous.Postgresql.Subscriptions uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Postgresql.Subscriptions.PostgresSubscriptionBase→Eventuous.Subscriptions.SubscriptionKind
- Direction
- Eventuous.Postgresql.Subscriptions uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Postgresql.Subscriptions, while a change to Eventuous.Postgresql.Subscriptions can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Postgresql.Subscriptions uses a module listed above it, which is the healthy direction.
37→33 Eventuous.Postgresql.Subscriptions uses Eventuous.Sql.Base.Subscriptions✕
- Connections
- 2 pairs of types, where a type in Eventuous.Postgresql.Subscriptions uses a type in Eventuous.Sql.Base.Subscriptions.
- The types involved
Eventuous.Postgresql.Subscriptions.PostgresSubscriptionBase→Eventuous.Sql.Base.Subscriptions.SqlSubscriptionBaseEventuous.Postgresql.Subscriptions.PostgresSubscriptionBaseOptions→Eventuous.Sql.Base.Subscriptions.SqlSubscriptionOptionsBase
- Direction
- Eventuous.Postgresql.Subscriptions uses Eventuous.Sql.Base.Subscriptions, so a change to Eventuous.Sql.Base.Subscriptions can break Eventuous.Postgresql.Subscriptions, while a change to Eventuous.Postgresql.Subscriptions can't break Eventuous.Sql.Base.Subscriptions.
- Position
- Below the diagonal: Eventuous.Postgresql.Subscriptions uses a module listed above it, which is the healthy direction.
38→1 Eventuous.SignalR.Server uses Eventuous✕
- Connections
- 4 pairs of types, where a type in Eventuous.SignalR.Server uses a type in Eventuous.
- The types involved
Eventuous.SignalR.Server.SignalRProducer→Eventuous.StreamNameEventuous.SignalR.Server.SignalRTransform→Eventuous.IEventSerializerEventuous.SignalR.Server.SubscriptionFactory→Eventuous.StreamNameEventuous.SignalR.Server.SubscriptionGateway→Eventuous.IEventSerializer
- Direction
- Eventuous.SignalR.Server uses Eventuous, so a change to Eventuous can break Eventuous.SignalR.Server, while a change to Eventuous.SignalR.Server can't break Eventuous.
- Position
- Below the diagonal: Eventuous.SignalR.Server uses a module listed above it, which is the healthy direction.
38→10 Eventuous.SignalR.Server uses Eventuous.Producers✕
- Connections
- 2 pairs of types, where a type in Eventuous.SignalR.Server uses a type in Eventuous.Producers.
- The types involved
Eventuous.SignalR.Server.SignalRProducer→Eventuous.Producers.BaseProducerEventuous.SignalR.Server.SignalRProducer→Eventuous.Producers.ProducedMessage
- Direction
- Eventuous.SignalR.Server uses Eventuous.Producers, so a change to Eventuous.Producers can break Eventuous.SignalR.Server, while a change to Eventuous.SignalR.Server can't break Eventuous.Producers.
- Position
- Below the diagonal: Eventuous.SignalR.Server uses a module listed above it, which is the healthy direction.
38→21 Eventuous.SignalR.Server uses Eventuous.Subscriptions.Filters✕
- Connections
- 2 pairs of types, where a type in Eventuous.SignalR.Server uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.SignalR.Server.SubscriptionFactory→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.SignalR.Server.SubscriptionState→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.SignalR.Server uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.SignalR.Server, while a change to Eventuous.SignalR.Server can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.SignalR.Server uses a module listed above it, which is the healthy direction.
38→22 Eventuous.SignalR.Server uses Eventuous.Subscriptions✕
- Connections
- 2 pairs of types, where a type in Eventuous.SignalR.Server uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.SignalR.Server.SubscriptionFactory→Eventuous.Subscriptions.IMessageSubscriptionEventuous.SignalR.Server.SubscriptionState→Eventuous.Subscriptions.IMessageSubscription
- Direction
- Eventuous.SignalR.Server uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.SignalR.Server, while a change to Eventuous.SignalR.Server can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.SignalR.Server uses a module listed above it, which is the healthy direction.
38→25 Eventuous.SignalR.Server uses Eventuous.Gateway✕
- Connections
- 1 pair of types, where a type in Eventuous.SignalR.Server uses a type in Eventuous.Gateway.
- The types involved
Eventuous.SignalR.Server.SignalRTransform→Eventuous.Gateway.RouteAndTransform
- Direction
- Eventuous.SignalR.Server uses Eventuous.Gateway, so a change to Eventuous.Gateway can break Eventuous.SignalR.Server, while a change to Eventuous.SignalR.Server can't break Eventuous.Gateway.
- Position
- Below the diagonal: Eventuous.SignalR.Server uses a module listed above it, which is the healthy direction.
39→1 Eventuous.SqlServer.Subscriptions uses Eventuous✕
- Connections
- 7 pairs of types, where a type in Eventuous.SqlServer.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.SqlServer.Subscriptions.SqlServerAllStreamSubscription→Eventuous.IEventSerializerEventuous.SqlServer.Subscriptions.SqlServerAllStreamSubscription→Eventuous.IMetadataSerializerEventuous.SqlServer.Subscriptions.SqlServerStreamSubscription→Eventuous.IEventSerializerEventuous.SqlServer.Subscriptions.SqlServerStreamSubscription→Eventuous.IMetadataSerializerEventuous.SqlServer.Subscriptions.SqlServerStreamSubscriptionOptions→Eventuous.StreamNameEventuous.SqlServer.Subscriptions.SqlServerSubscriptionBase→Eventuous.IEventSerializerEventuous.SqlServer.Subscriptions.SqlServerSubscriptionBase→Eventuous.IMetadataSerializer
- Direction
- Eventuous.SqlServer.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.SqlServer.Subscriptions, while a change to Eventuous.SqlServer.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.SqlServer.Subscriptions uses a module listed above it, which is the healthy direction.
39→18 Eventuous.SqlServer.Subscriptions uses Eventuous.Subscriptions.Checkpoints✕
- Connections
- 5 pairs of types, where a type in Eventuous.SqlServer.Subscriptions uses a type in Eventuous.Subscriptions.Checkpoints.
- The types involved
Eventuous.SqlServer.Subscriptions.SqlServerAllStreamSubscription→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.SqlServer.Subscriptions.SqlServerCheckpointStore→Eventuous.Subscriptions.Checkpoints.CheckpointEventuous.SqlServer.Subscriptions.SqlServerCheckpointStore→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.SqlServer.Subscriptions.SqlServerStreamSubscription→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.SqlServer.Subscriptions.SqlServerSubscriptionBase→Eventuous.Subscriptions.Checkpoints.ICheckpointStore
- Direction
- Eventuous.SqlServer.Subscriptions uses Eventuous.Subscriptions.Checkpoints, so a change to Eventuous.Subscriptions.Checkpoints can break Eventuous.SqlServer.Subscriptions, while a change to Eventuous.SqlServer.Subscriptions can't break Eventuous.Subscriptions.Checkpoints.
- Position
- Below the diagonal: Eventuous.SqlServer.Subscriptions uses a module listed above it, which is the healthy direction.
39→21 Eventuous.SqlServer.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 3 pairs of types, where a type in Eventuous.SqlServer.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.SqlServer.Subscriptions.SqlServerAllStreamSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.SqlServer.Subscriptions.SqlServerStreamSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.SqlServer.Subscriptions.SqlServerSubscriptionBase→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.SqlServer.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.SqlServer.Subscriptions, while a change to Eventuous.SqlServer.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.SqlServer.Subscriptions uses a module listed above it, which is the healthy direction.
39→22 Eventuous.SqlServer.Subscriptions uses Eventuous.Subscriptions✕
- Connections
- 1 pair of types, where a type in Eventuous.SqlServer.Subscriptions uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.SqlServer.Subscriptions.SqlServerSubscriptionBase→Eventuous.Subscriptions.SubscriptionKind
- Direction
- Eventuous.SqlServer.Subscriptions uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.SqlServer.Subscriptions, while a change to Eventuous.SqlServer.Subscriptions can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.SqlServer.Subscriptions uses a module listed above it, which is the healthy direction.
39→33 Eventuous.SqlServer.Subscriptions uses Eventuous.Sql.Base.Subscriptions✕
- Connections
- 2 pairs of types, where a type in Eventuous.SqlServer.Subscriptions uses a type in Eventuous.Sql.Base.Subscriptions.
- The types involved
Eventuous.SqlServer.Subscriptions.SqlServerSubscriptionBase→Eventuous.Sql.Base.Subscriptions.SqlSubscriptionBaseEventuous.SqlServer.Subscriptions.SqlServerSubscriptionBaseOptions→Eventuous.Sql.Base.Subscriptions.SqlSubscriptionOptionsBase
- Direction
- Eventuous.SqlServer.Subscriptions uses Eventuous.Sql.Base.Subscriptions, so a change to Eventuous.Sql.Base.Subscriptions can break Eventuous.SqlServer.Subscriptions, while a change to Eventuous.SqlServer.Subscriptions can't break Eventuous.Sql.Base.Subscriptions.
- Position
- Below the diagonal: Eventuous.SqlServer.Subscriptions uses a module listed above it, which is the healthy direction.
39→34 Eventuous.SqlServer.Subscriptions uses Eventuous.SqlServer.Projections✕
- Connections
- 3 pairs of types, where a type in Eventuous.SqlServer.Subscriptions uses a type in Eventuous.SqlServer.Projections.
- The types involved
Eventuous.SqlServer.Subscriptions.SqlServerAllStreamSubscription→Eventuous.SqlServer.Projections.SqlServerConnectionOptionsEventuous.SqlServer.Subscriptions.SqlServerStreamSubscription→Eventuous.SqlServer.Projections.SqlServerConnectionOptionsEventuous.SqlServer.Subscriptions.SqlServerSubscriptionBase→Eventuous.SqlServer.Projections.SqlServerConnectionOptions
- Direction
- Eventuous.SqlServer.Subscriptions uses Eventuous.SqlServer.Projections, so a change to Eventuous.SqlServer.Projections can break Eventuous.SqlServer.Subscriptions, while a change to Eventuous.SqlServer.Subscriptions can't break Eventuous.SqlServer.Projections.
- Position
- Below the diagonal: Eventuous.SqlServer.Subscriptions uses a module listed above it, which is the healthy direction.
40→1 Eventuous.Sqlite.Subscriptions uses Eventuous✕
- Connections
- 7 pairs of types, where a type in Eventuous.Sqlite.Subscriptions uses a type in Eventuous.
- The types involved
Eventuous.Sqlite.Subscriptions.SqliteAllStreamSubscription→Eventuous.IEventSerializerEventuous.Sqlite.Subscriptions.SqliteAllStreamSubscription→Eventuous.IMetadataSerializerEventuous.Sqlite.Subscriptions.SqliteStreamSubscription→Eventuous.IEventSerializerEventuous.Sqlite.Subscriptions.SqliteStreamSubscription→Eventuous.IMetadataSerializerEventuous.Sqlite.Subscriptions.SqliteStreamSubscriptionOptions→Eventuous.StreamNameEventuous.Sqlite.Subscriptions.SqliteSubscriptionBase→Eventuous.IEventSerializerEventuous.Sqlite.Subscriptions.SqliteSubscriptionBase→Eventuous.IMetadataSerializer
- Direction
- Eventuous.Sqlite.Subscriptions uses Eventuous, so a change to Eventuous can break Eventuous.Sqlite.Subscriptions, while a change to Eventuous.Sqlite.Subscriptions can't break Eventuous.
- Position
- Below the diagonal: Eventuous.Sqlite.Subscriptions uses a module listed above it, which is the healthy direction.
40→18 Eventuous.Sqlite.Subscriptions uses Eventuous.Subscriptions.Checkpoints✕
- Connections
- 5 pairs of types, where a type in Eventuous.Sqlite.Subscriptions uses a type in Eventuous.Subscriptions.Checkpoints.
- The types involved
Eventuous.Sqlite.Subscriptions.SqliteAllStreamSubscription→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.Sqlite.Subscriptions.SqliteCheckpointStore→Eventuous.Subscriptions.Checkpoints.CheckpointEventuous.Sqlite.Subscriptions.SqliteCheckpointStore→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.Sqlite.Subscriptions.SqliteStreamSubscription→Eventuous.Subscriptions.Checkpoints.ICheckpointStoreEventuous.Sqlite.Subscriptions.SqliteSubscriptionBase→Eventuous.Subscriptions.Checkpoints.ICheckpointStore
- Direction
- Eventuous.Sqlite.Subscriptions uses Eventuous.Subscriptions.Checkpoints, so a change to Eventuous.Subscriptions.Checkpoints can break Eventuous.Sqlite.Subscriptions, while a change to Eventuous.Sqlite.Subscriptions can't break Eventuous.Subscriptions.Checkpoints.
- Position
- Below the diagonal: Eventuous.Sqlite.Subscriptions uses a module listed above it, which is the healthy direction.
40→21 Eventuous.Sqlite.Subscriptions uses Eventuous.Subscriptions.Filters✕
- Connections
- 3 pairs of types, where a type in Eventuous.Sqlite.Subscriptions uses a type in Eventuous.Subscriptions.Filters.
- The types involved
Eventuous.Sqlite.Subscriptions.SqliteAllStreamSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.Sqlite.Subscriptions.SqliteStreamSubscription→Eventuous.Subscriptions.Filters.ConsumePipeEventuous.Sqlite.Subscriptions.SqliteSubscriptionBase→Eventuous.Subscriptions.Filters.ConsumePipe
- Direction
- Eventuous.Sqlite.Subscriptions uses Eventuous.Subscriptions.Filters, so a change to Eventuous.Subscriptions.Filters can break Eventuous.Sqlite.Subscriptions, while a change to Eventuous.Sqlite.Subscriptions can't break Eventuous.Subscriptions.Filters.
- Position
- Below the diagonal: Eventuous.Sqlite.Subscriptions uses a module listed above it, which is the healthy direction.
40→22 Eventuous.Sqlite.Subscriptions uses Eventuous.Subscriptions✕
- Connections
- 1 pair of types, where a type in Eventuous.Sqlite.Subscriptions uses a type in Eventuous.Subscriptions.
- The types involved
Eventuous.Sqlite.Subscriptions.SqliteSubscriptionBase→Eventuous.Subscriptions.SubscriptionKind
- Direction
- Eventuous.Sqlite.Subscriptions uses Eventuous.Subscriptions, so a change to Eventuous.Subscriptions can break Eventuous.Sqlite.Subscriptions, while a change to Eventuous.Sqlite.Subscriptions can't break Eventuous.Subscriptions.
- Position
- Below the diagonal: Eventuous.Sqlite.Subscriptions uses a module listed above it, which is the healthy direction.
40→33 Eventuous.Sqlite.Subscriptions uses Eventuous.Sql.Base.Subscriptions✕
- Connections
- 2 pairs of types, where a type in Eventuous.Sqlite.Subscriptions uses a type in Eventuous.Sql.Base.Subscriptions.
- The types involved
Eventuous.Sqlite.Subscriptions.SqliteSubscriptionBase→Eventuous.Sql.Base.Subscriptions.SqlSubscriptionBaseEventuous.Sqlite.Subscriptions.SqliteSubscriptionBaseOptions→Eventuous.Sql.Base.Subscriptions.SqlSubscriptionOptionsBase
- Direction
- Eventuous.Sqlite.Subscriptions uses Eventuous.Sql.Base.Subscriptions, so a change to Eventuous.Sql.Base.Subscriptions can break Eventuous.Sqlite.Subscriptions, while a change to Eventuous.Sqlite.Subscriptions can't break Eventuous.Sql.Base.Subscriptions.
- Position
- Below the diagonal: Eventuous.Sqlite.Subscriptions uses a module listed above it, which is the healthy direction.
40→35 Eventuous.Sqlite.Subscriptions uses Eventuous.Sqlite.Projections✕
- Connections
- 3 pairs of types, where a type in Eventuous.Sqlite.Subscriptions uses a type in Eventuous.Sqlite.Projections.
- The types involved
Eventuous.Sqlite.Subscriptions.SqliteAllStreamSubscription→Eventuous.Sqlite.Projections.SqliteConnectionOptionsEventuous.Sqlite.Subscriptions.SqliteStreamSubscription→Eventuous.Sqlite.Projections.SqliteConnectionOptionsEventuous.Sqlite.Subscriptions.SqliteSubscriptionBase→Eventuous.Sqlite.Projections.SqliteConnectionOptions
- Direction
- Eventuous.Sqlite.Subscriptions uses Eventuous.Sqlite.Projections, so a change to Eventuous.Sqlite.Projections can break Eventuous.Sqlite.Subscriptions, while a change to Eventuous.Sqlite.Subscriptions can't break Eventuous.Sqlite.Projections.
- Position
- Below the diagonal: Eventuous.Sqlite.Subscriptions 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 | 29 | High / Critical |
| A02:2025 — Security Misconfiguration | 24 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 11 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Prerelease dependency finding(s) in Dependency Hygiene; Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Prerelease dependency finding(s) in Dependency Hygiene. | +4.0 pts | Low | Dependency Hygiene |
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props. | +3.2 pts | Low | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.9 pts | Low | ADR Quality |
| 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. | +3.1 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.7 pts | Medium | Release Hygiene |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +1.2 pts | Low | Documentation Quality |
| 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. | +1.3 pts | Medium | Architecture documentation |
| Resolve the 8 redundant comment finding(s) in Comment Value — start with TypeMappingsGenerator.cs (2), BlobStorageProjectorTests.cs, ContextAllocationBenchmarks.cs. | +0.7 pts | Low | Comment Value |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Core/src/Eventuous.Persistence/StateStore/StateStore.cs | 4.9 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/KurrentDB/src/Eventuous.KurrentDB/KurrentDBEventStore.cs | 6.0 | Mixed | Explicit Debt: BarePragmaDisable |
| src/Core/src/Eventuous.Producers/RegistrationExtensions.cs | 6.0 | Mixed | Explicit Debt: Dead code: AddEventProducer |
| src/Core/src/Eventuous.Diagnostics/EventuousDiagnostics.cs | 6.0 | Mixed | Explicit Debt: Dead code: Disable |
| REDACTED | 6.1 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/Directory.Build.props | 6.4 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/Extensions/src/Eventuous.Extensions.AspNetCore/Http/CommandMappingRegistry.cs | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/Core/src/Eventuous.Diagnostics/TelemetryTags.cs | 6.6 | Mixed | Explicit Debt: Dead code: Net |
| src/Experimental/src/ElasticPlayground/CombinedStore.cs | 6.7 | Mixed | Explicit Debt: Dead code: CombinedStore |
| src/Extensions/gen/Eventuous.Extensions.AspNetCore.Generators/HttpCommandMappingGenerator.cs | 6.8 | Mixed | Cognitive Complexity: HttpCommandMappingGenerator.Execute (cognitive 28) |
| src/Gateway/src/Eventuous.Gateway/GatewayMetaHelper.cs | 6.9 | Mixed | Explicit Debt: Dead code: GetOriginalMessage |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 79 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 — 79 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, 373 of 455 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — 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. Coverage NOT MEASURED: this repository runs its tests on Microsoft.Testing.Platform (its global.json opts in), where coverage comes from a coverage extension the test project references — and none is wired up: no build file names `Microsoft.Testing.Extensions.CodeCoverage` or `coverlet.MTP`. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment. Add one of those PackageReferences to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `Microsoft.Testing.Extensions.CodeCoverage` (or `coverlet.MTP`) package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- 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-maintainer repository — bus factor is not applicable (30 contributor(s) across 1053 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 29 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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) — 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. `src/Azure/src/Eventuous.Azure.ServiceBus/Producers/ServiceBusMessageBatchBuilder.cs`, `src/Azure/src/Eventuous.Azure.ServiceBus/Producers/ServiceBusMessageBuilder.cs`, `src/Azure/src/Eventuous.Azure.ServiceBus/Subscriptions/ServiceBusSubscription.cs`, `src/Azure/src/Eventuous.Azure.Storage.Blobs/BlobStorageProjector.cs`, `src/Core/gen/Eventuous.Shared.Generators/EventUsageAnalyzer.cs`, … (+103 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via AspireAppHost (REDACTED). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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. 56 further occurrence(s) are not listed individually; the score already reflects all 96.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HttpCommandStateMismatchAnalyzer.AnalyzeInvocation at 41.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with HttpCommandStateMismatchAnalyzer.AnalyzeInvocation (cyclomatic 41). — Refactoring it lifts Cyclomatic Complexity from 8.5 to about 8.8/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
12 method(s) exceeded the cognitive complexity threshold of 15; the worst was HttpCommandStateMismatchAnalyzer.AnalyzeInvocation at 81.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with HttpCommandStateMismatchAnalyzer.AnalyzeInvocation (cognitive 81), ConsumeContextConverterGenerator.TransformWithSymbol (cognitive 41). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.3 to about 8.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
26 duplicated block group(s) detected. 8 of the 26 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with EventUsageAnalyzer.cs, Stores.cs, CommandService.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Services.cs, RegistrationExtensions.cs, CombinedStore.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 SqlServerCheckpointStore.cs, BookingsCommandService.cs. — 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
219 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 1 Layer violation finding(s) in Coupling — start with Eventuous.Application.csproj. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Off the main sequence finding(s) in Coupling — start with Eventuous.Diagnostics.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 106 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with AllocationHotspotsBenchmarks.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
1541 test methods: 845 unit, 696 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 9 zero-assertion, 5 synchronised by a fixed sleep, 1 mock references across 517 tests.
What to do
- Resolve the 9 No assertions finding(s) in Test Quality — start with TwoAggregateOpsSpec.cs (3), OperateOnExistingSpec.cs (2), OperateOnAggregateWithId.cs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 5 Fixed-sleep synchronisation finding(s) in Test Quality — start with SubscriptionGatewayTests.cs (4), SignalREndToEndTests.cs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
63 outdated, 0 vulnerable, 1 deprecated, 2 prerelease packages.
What to do
- Resolve the 2 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props. — One of this dimension's main actionable groups (1 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 25 packages use a banned license. ★ DEPTH: every package graded here is one this repository's MSBuild projects declare as a direct `PackageReference` (78 declared), and nothing beyond them was reached — this is the DECLARATION-SITE set, NOT the transitive closure. .NET has no lockfile a checkout is guaranteed to carry and this pass grades an unrestored tree, so a banned licence that only a direct dependency's OWN dependencies pull in is outside this verdict, exactly as the JVM arm's declaration-site verdict is.
D15 · Churn × Complexity Hotspots
Top hotspots: src/Relational/src/Eventuous.Sql.Base/Subscriptions/SqlSubscriptionBase.cs (4×17=68); src/Core/src/Eventuous.Subscriptions/EventSubscription.cs (2×15=30)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with SqlSubscriptionBase.cs, EventSubscription.cs. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
58 deducted debt markers + 45 dead symbols across 22436 LoC in the .NET projects (1.5/KLoC) → score 6.9.
What to do
- Resolve the 6 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (2), Eventuous.KurrentDB.csproj, Eventuous.Tests.Postgres.csproj. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 FileScopedPragmaDisable finding(s) in Explicit Debt — start with Range.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with StateStore.cs. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
216 projects, 2220 source files, 38983 hand-written lines of code (22434 production / 16549 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), 472 inter-project edges.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 17 document(s) read across 42 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (20 contexts). Contexts: Azure, Core, Diagnostics, Eventuous.TestHelpers, Eventuous.TestHelpers.TUnit, Experimental, Extensions, Gateway, GooglePubSub, Kafka, KurrentDB, Mongo and 8 more.
D24 · Comment Value
8 of 620 judged comments only repeat the code they sit on (1.3 %). 6 comment(s) in another language or script were not judged.
What to do
- Resolve the 8 redundant comment finding(s) in Comment Value — start with TypeMappingsGenerator.cs (2), BlobStorageProjectorTests.cs, ContextAllocationBenchmarks.cs. — One of this dimension's main actionable groups (8 recommendation-level).
D26 · Project Cohesion
0 of 81 projects flagged as possibly oversized/incoherent.
D27 · Navigability
87 % of calls cross a namespace and 4 % go through an interface, but 94 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
29 finding(s): 0 critical, 25 high, 4 medium, 0 low. 18 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 119 file(s) — `samples/kurrentdb/Bookings.Payments/Application/CommandApi.cs` (line 10), `samples/kurrentdb/Bookings/Application/BookingsQueryService.cs` (line 10), `samples/kurrentdb/Bookings/HttpApi/Bookings/CommandApi.cs` (line 15), `samples/kurrentdb/Bookings/HttpApi/Bookings/CommandApiWithCustomResult.cs` (line 18), `samples/kurrentdb/Bookings/HttpApi/Bookings/QueryApi.cs` (line 8), … (+114 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 107 of those file(s) — `samples/kurrentdb/Bookings.Payments/Application/CommandApi.cs`, `samples/kurrentdb/Bookings/Application/BookingsQueryService.cs`, `samples/kurrentdb/Bookings/HttpApi/Bookings/CommandApi.cs`, `samples/kurrentdb/Bookings/HttpApi/Bookings/CommandApiWithCustomResult.cs`, `samples/kurrentdb/Bookings/HttpApi/Bookings/QueryApi.cs`, … (+102 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 18 of those file(s) — `src/Core/src/Eventuous.Application/AggregateService/CommandService.cs`, `src/Core/src/Eventuous.Application/Exceptions/Exceptions.cs`, `src/Core/src/Eventuous.Diagnostics/DummyActivityListener.cs`, `src/Core/src/Eventuous.Domain/Exceptions/DomainException.cs`, `src/Core/src/Eventuous.Domain/Exceptions/Exceptions.cs`, … (+13 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 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 18 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 (18 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 4 high, 1 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
24 finding(s): 0 critical, 5 high, 19 medium, 0 low.
What to do
- Resolve the 19 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (19). — One of this dimension's main actionable groups (19 warning-level).
- Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 152 of the 403 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: EventuousDiagnostics.cs↔MeterProviderBuilderExtensions.cs 55%; EventSubscription.cs↔AsyncHandlingFilter.cs 54%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with EventuousDiagnostics.cs, EventSubscription.cs. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D39 · IL Efficiency
5 of 2228 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 6 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
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
- `SubscriptionBuilder` is a singleton (one shared instance) but mutates instance state outside any lock (ConfigureOptions, _resolvedConsumer, _resolvedSubscription; e.g. `ConfigureOptions` at line 330). — src/Core/src/Eventuous.Subscriptions/Registrations/SubscriptionBuilder.cs:302
- `TypeMapper` is a singleton (one shared instance) but mutates instance state outside any lock (_reverseMap, _map; e.g. `_reverseMap` at line 85). — src/Core/src/Eventuous.Shared/TypeMap/TypeMapper.cs:37
- `AggregateFactoryRegistry` is a singleton (one shared instance) but mutates instance state outside any lock (Registry; e.g. `Registry` at line 36). — src/Core/src/Eventuous.Persistence/AggregateFactory.cs:10
- `TypeMapper` is not registered, but `TypeMap` creates it and keeps it in the static `Instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_reverseMap, _map; e.g. `_reverseMap` at line 85). — src/Core/src/Eventuous.Shared/TypeMap/TypeMapper.cs:37
- `LoggingEventListener` is not registered, but `LoggerFactoryExtensions` creates it and keeps it in the static `listener`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_eventSources; e.g. `_eventSources` at line 29). — src/Diagnostics/src/Eventuous.Diagnostics.Logging/LoggingEventListener.cs:6
- `EventuousDiagnostics` 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 (Tags, Enabled; e.g. `Tags` at line 24). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Core/src/Eventuous.Diagnostics/EventuousDiagnostics.cs:8
- `DefaultMetadataSerializer` 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 (Instance; e.g. `Instance` at line 13). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Core/src/Eventuous.Serialization/DefaultMetadataSerializer.cs:9
- `EventSerializer` 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 (_default; e.g. `_default` at line 28). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Core/src/Eventuous.Serialization/EventSerializer.cs:11
- `LoggerFactoryExtensions` 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 (listener; e.g. `listener` at line 19). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Extensions/src/Eventuous.Extensions.Logging/LoggerFactoryExtensions.cs:10
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces Eventuous ↔ Eventuous.Persistence ↔ Eventuous.Shared depend on each other. The lightest dependency in the cycle is Eventuous.Shared → Eventuous.Persistence (Eventuous.Shared.IDefineAppendAmendment → Eventuous.Persistence.AmendAppend, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Core/src/Eventuous.Application/Shared/IDefineAppendAmendment.cs:4
- The namespaces Eventuous.Producers ↔ Eventuous.Producers.Diagnostics depend on each other. The lightest dependency in the cycle is Eventuous.Producers → Eventuous.Producers.Diagnostics (Eventuous.Producers.BaseProducer → Eventuous.Producers.Diagnostics.ProducerTracingOptions, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Core/src/Eventuous.Producers/BaseProducer.cs:16
- The namespaces Eventuous.Diagnostics ↔ Eventuous.Diagnostics.Metrics depend on each other. The lightest dependency in the cycle is Eventuous.Diagnostics.Metrics → Eventuous.Diagnostics (Eventuous.Diagnostics.Metrics.MetricsListener → Eventuous.Diagnostics.GenericListener, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Core/src/Eventuous.Diagnostics/Metrics/MetricsListener.cs:8
- The namespaces Eventuous.Subscriptions ↔ Eventuous.Subscriptions.Checkpoints ↔ Eventuous.Subscriptions.Consumers ↔ Eventuous.Subscriptions.Context ↔ Eventuous.Subscriptions.Diagnostics ↔ Eventuous.Subscriptions.Filters ↔ Eventuous.Subscriptions.Filters.Partitioning ↔ Eventuous.Subscriptions.Logging depend on each other. The lightest dependency in the cycle is Eventuous.Subscriptions.Checkpoints → Eventuous.Subscriptions.Logging (Eventuous.Subscriptions.Checkpoints.CommitPosition → Eventuous.Subscriptions.Logging.LogContext, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Core/src/Eventuous.Subscriptions/Checkpoints/CheckpointCommitHandler.cs:164
- The namespaces Eventuous.Extensions.AspNetCore.Http ↔ Microsoft.AspNetCore.Routing depend on each other. The lightest dependency in the cycle is Eventuous.Extensions.AspNetCore.Http → Microsoft.AspNetCore.Routing (Eventuous.Extensions.AspNetCore.Http.CommandServiceRouteBuilder → Microsoft.AspNetCore.Routing.ConvertAndEnrichCommand, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Extensions/src/Eventuous.Extensions.AspNetCore/Http/CommandServiceRouteBuilder.cs:5
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
- `Eventuous.Application` is a Application project but references `Eventuous.Persistence`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/Core/src/Eventuous.Application/Eventuous.Application.csproj:8
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `IEventStore`, `IEventReader`, `IEventWriter`, `AmendEvent`, `TaskExtensions`. The inward dependency rule is broken here. It is named again on lines 66, 79, 91, 145, 146, 159, 160, 161, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/AggregateService/CommandHandlerBuilder.cs:53
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `IEventStore`. The inward dependency rule is broken here. It is named again on lines 40, 62, 84, 106. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/AggregateService/CommandService.Async.cs:18
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `IEventStore`. The inward dependency rule is broken here. It is named again on lines 39, 60. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/AggregateService/CommandService.Sync.cs:18
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `IEventReader`, `IEventWriter`, `AggregateFactoryRegistry`, `StreamNameMap`, `AmendEvent`, `IEventStore`, `TaskExtensions`, `AggregateStoreExtensions`, …. The inward dependency rule is broken here. It is named again on lines 19, 20, 21, 23, 30, 31, 32, 34, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/AggregateService/CommandService.cs:18
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `DiagnosticName`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. (×2) — src/Core/src/Eventuous.Application/Diagnostics/ApplicationEventSource.cs:10, src/Core/src/Eventuous.Application/Diagnostics/CommandServiceMetrics.cs:15
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `Eventuous.Diagnostics.Tracing`, `TaskExtensions`. The inward dependency rule is broken here. It is named again on line 31. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/Diagnostics/CommandServiceActivity.cs:9
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `IEventStore`, `IEventReader`, `IEventWriter`, `AmendEvent`, `TaskExtensions`. The inward dependency rule is broken here. It is named again on lines 52, 62, 73, 121, 131, 132, 133, 163, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/FunctionalService/CommandHandlerBuilder.cs:42
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `IEventReader`, `IEventWriter`, `AmendEvent`, `IEventStore`, `TaskExtensions`, `ExpectedStreamVersion`, `NewStreamEvent`. The inward dependency rule is broken here. It is named again on lines 13, 40, 52, 77, 83, 84, 85, 89, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/FunctionalService/CommandService.cs:11
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `TaskExtensions`, `IEventReader`, `IEventWriter`, `AmendEvent`. The inward dependency rule is broken here. It is named again on lines 11, 14, 17. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/FunctionalService/FuncHandlerDelegateExtensions.cs:9
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `IEventReader`, `IEventWriter`, `NewStreamEvent`. The inward dependency rule is broken here. It is named again on lines 15, 17. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/FunctionalService/FuncServiceDelegates.cs:13
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `Eventuous.Diagnostics`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/FunctionalService/HandlersMap.cs:4
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `ExpectedStreamVersion`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/Persistence/ProposedAppend.cs:12
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `IEventWriter`, `AppendEventsResult`, `AmendEvent`, `TaskExtensions`, `OptimisticConcurrencyException`, `NewStreamEvent`, `NewStreamAppend`. The inward dependency rule is broken here. It is named again on lines 8, 11, 20, 23, 27, 28, 34, 36, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/Persistence/WriterExtensions.cs:7
- This Application file depends on the Infrastructure project `Eventuous.Persistence`: it names `TaskExtensions`. The inward dependency rule is broken here. It is named again on line 132. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/Core/src/Eventuous.Application/Result.cs:131
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX5 · Architecture & structure
AX6 · Interface segregation
- `IBaseConsumeContext` declares 16 members: `MessageId`, `MessageType`, `ContentType`, `Stream`, `EventNumber`, `StreamPosition`, `GlobalPosition`, `Created`, `Metadata`, `Items`, `ParentContext`, `HandlingResults`, `CancellationToken`, `Sequence`, `SubscriptionId`, `LogContext`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Core/src/Eventuous.Subscriptions/Context/IMessageConsumeContext.cs:13
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
C2 · Access Controls
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×5) — src/Kafka/src/Eventuous.Kafka/Subscriptions/KafkaBasicSubscription.cs:12, src/Experimental/src/Eventuous.ElasticSearch/Store/ElasticEventStore.cs:107, src/Experimental/src/Eventuous.ElasticSearch/Store/ElasticEventStore.cs:114, …
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `TruncateStream` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Experimental/src/Eventuous.ElasticSearch/Store/ElasticEventStore.cs:107
- `DeleteStream` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/Experimental/src/Eventuous.ElasticSearch/Store/ElasticEventStore.cs:114, src/Relational/src/Eventuous.Sql.Base/SqlEventStoreBase.cs:261
- `Connect` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Kafka/src/Eventuous.Kafka/Subscriptions/KafkaBasicSubscription.cs:12
- `ReadEventsBackwards` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Redis/src/Eventuous.Redis/RedisStore.cs:93
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×13) — src/Core/src/Eventuous.Subscriptions/Filters/AsyncHandlingFilter.cs:114, src/Core/src/Eventuous.Subscriptions/Filters/AsyncHandlingFilter.cs:115, src/Core/src/Eventuous.Subscriptions/Filters/PartitioningFilter.cs:37, …
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
- 144 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 build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 33 of 52 project(s) that lack one — worth up to 1.3 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.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- src/Benchmarks/Benchmarks/README.md links to `../../Core/src/Eventuous.Subscriptions/PERFORMANCE_ANALYSIS.md`, but `src/Core/src/Eventuous.Subscriptions/PERFORMANCE_ANALYSIS.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Benchmarks/Benchmarks/README.md:3
What to do
- Reconcile the README with reality: src/Benchmarks/Benchmarks/README.md links to `../../Core/src/Eventuous.Subscriptions/PERFORMANCE_ANALYSIS.md`, but `src/Core/src/Eventuous.Subscriptions/PERFORMANCE_ANALYSIS.md` does not exist.
P1 · CI/CD gates
P2 · Observability
- Only 34/42 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 42, 6 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
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 11095 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
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
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
- 2 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — src/Kafka/src/Eventuous.Kafka/Producers/KafkaBasicProducer.cs:75, src/Core/src/Eventuous.Subscriptions/Diagnostics/SubscriptionMetrics.cs:115
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×4) — samples/kurrentdb/Bookings.Payments/Program.cs:9, samples/kurrentdb/Bookings/Program.cs:28, samples/postgres/Bookings.Payments/Program.cs:12, …
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. (×4) — samples/kurrentdb/Bookings.Payments/Program.cs:9, samples/kurrentdb/Bookings/Program.cs:28, samples/postgres/Bookings.Payments/Program.cs:12, …
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
- Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
X1 · Async correctness
- 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. (×2) — src/Kafka/src/Eventuous.Kafka/Producers/KafkaBasicProducer.cs:75, src/Core/src/Eventuous.Subscriptions/Diagnostics/SubscriptionMetrics.cs:115
What to do
- Sync-over-async (deadlock risk)
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 25). Every use of it in `StartAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cts = …;`), which releases it at the end of the scope on every path including a throw. — src/Core/src/Eventuous.Subscriptions/SubscriptionHostedService.cs:25
- `cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 38). Every use of it in `StopAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cts = …;`), which releases it at the end of the scope on every path including a throw. — src/Core/src/Eventuous.Subscriptions/SubscriptionHostedService.cs:38
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 159/247 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. (×17) — src/Benchmarks/Benchmarks/SubscriptionMessageProcessingBenchmarks.cs:70, src/Azure/src/Eventuous.Azure.Storage.Blobs/BlobStorageProjector.cs:112, src/RabbitMq/src/Eventuous.RabbitMq/Producers/ExchangeCache.cs:10, …
- No CancellationToken parameter, and the token `run.Token` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `run.Token` on, or take a CancellationToken. (×3) — src/Azure/src/Eventuous.Azure.ServiceBus/Subscriptions/ServiceBusSubscription.cs:42, src/Core/src/Eventuous.Subscriptions/EventSubscriptionWithCheckpoint.cs:111, src/Core/src/Eventuous.Subscriptions/EventSubscriptionWithCheckpoint.cs:141
- 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. (×11) — src/Azure/src/Eventuous.Azure.ServiceBus/Subscriptions/ServiceBusSubscription.cs:61, src/Azure/src/Eventuous.Azure.ServiceBus/Subscriptions/ServiceBusSubscription.cs:73, src/Azure/src/Eventuous.Azure.ServiceBus/Subscriptions/ServiceBusSubscription.cs:180, …
- Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. (×8) — src/GooglePubSub/src/Eventuous.GooglePubSub/Producers/GooglePubSubProducer.cs:87, src/Kafka/src/Eventuous.Kafka/Producers/KafkaBasicProducer.cs:50, src/Kafka/src/Eventuous.Kafka/Producers/KafkaBasicProducer.cs:116, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
- The guard on line 42 rejects `error` and line 43 reports that rejection as `ArgumentNullException` — but the condition's own test `error.Exception is not ValidationException exception` is true of a value that is NOT null: it reads a member of `error`, so it can only be evaluated on a non-null `error` (a null one would throw `NullReferenceException` before the guard decided anything). So a caller whose `error` is present but fails that test is told it was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — samples/kurrentdb/Bookings/HttpApi/Bookings/CommandApiWithCustomResult.cs:43
What to do
- Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (StreamNotFound) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Core/src/Eventuous.Persistence/EventStore/StoreFunctions.cs:229
- `catch (ChannelClosedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Core/src/Eventuous.Subscriptions/Channels/ChannelExtensions.cs:84
- 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. — src/Mongo/src/Eventuous.Projections.MongoDB/Tools/MongoCollectionExtensions.cs:209
What to do
- Swallowed exception (caught, then discarded)
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
- ~1.2 `!` suppressions per 1k syntax nodes — 145 suppression(s) across the 117750 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 | 75% | Strong | Solid. |
| Architecture | 78% | Strong | Solid. |
| Maturity | 68% | Strong | Solid. |
| Readiness | 63% | Strong | Largest drag on the score — prioritise here. |
| Security | 69% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 81% | Strong | Strongest area. |
Unscored — 3 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.
- X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D21 Naming Consistency — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 108 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — applicable but not scored (5 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (AggregateRoot/IAggregateRoot); 3 strongly-typed id(s); 94 value object(s); a Domain/Aggregates/ValueObjects layer; 60 aggregate-constrained repository/repositories (IRepository<T> where T : IAggregateRoot); a top-level samples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 67 event handler(s); a message-bus package
- ED5 Idempotency — not scored — 3 of 3 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an append-only event-store seam (IEventStore/Append-of-events))
- 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 — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 50 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj src/KurrentDB/src/Eventuous.KurrentDB/Eventuous.KurrentDB.csproj:3
- NoWarnInCsproj src/Postgres/test/Eventuous.Tests.Postgres/Eventuous.Tests.Postgres.csproj:7
- NoWarnInCsproj src/Sqlite/test/Eventuous.Tests.Sqlite/Eventuous.Tests.Sqlite.csproj:6
- NoWarnInCsproj src/Relational/src/Eventuous.Sql.Base/Eventuous.Sql.Base.csproj:3
- NoWarnInCsproj src/Directory.Build.props:5
- NoWarnInCsproj src/Directory.Build.props:5
- Namespace dependency cycle src/Core/src/Eventuous.Application/Shared/IDefineAppendAmendment.cs:4
- Namespace dependency cycle src/Core/src/Eventuous.Producers/BaseProducer.cs:16
- Namespace dependency cycle src/Core/src/Eventuous.Diagnostics/Metrics/MetricsListener.cs:8
- Namespace dependency cycle src/Core/src/Eventuous.Subscriptions/Checkpoints/CheckpointCommitHandler.cs:164
- Namespace dependency cycle src/Extensions/src/Eventuous.Extensions.AspNetCore/Http/CommandServiceRouteBuilder.cs:5
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Eventuous.Application.csproj:8
- FileScopedPragmaDisable src/Core/gen/Eventuous.Shared.Generators/Polyfills/Range.cs:7
- WriteOnlyPrivateField src/Core/src/Eventuous.Persistence/StateStore/StateStore.cs:12
- EmptyCatchBlock src/Mongo/src/Eventuous.Projections.MongoDB/Tools/MongoCollectionExtensions.cs:209
- REDACTED
- REDACTED
- REDACTED
- Layer violation: Application → Infrastructure src/Core/src/Eventuous.Application/Eventuous.Application.csproj:8
Serious — 240 finding(s)
- Dead code: GetResultsOf src/Benchmarks/Benchmarks/ImplementedOptimizationsValidationBenchmarks.cs:177
- Dead code: GetResultsOf src/Benchmarks/Benchmarks/OptimizationComparisonBenchmarks.cs:128
- Dead code: TestSetup src/Azure/test/Eventuous.Tests.Azure.ServiceBus/TestSetup.cs:7
- Dead code: GetStreamAsync src/Core/src/Eventuous.Application/FunctionalService/CommandHandlerBuilder.cs:32
- Dead code: MatchAsync src/Core/src/Eventuous.Application/Result.cs:130
- Dead code: Disable src/Core/src/Eventuous.Diagnostics/EventuousDiagnostics.cs:43
- Dead code: Enable src/Core/src/Eventuous.Diagnostics/EventuousDiagnostics.cs:45
- Dead code: Net src/Core/src/Eventuous.Diagnostics/TelemetryTags.cs:7
- Dead code: EndUser src/Core/src/Eventuous.Diagnostics/TelemetryTags.cs:17
- Dead code: Peer src/Core/src/Eventuous.Diagnostics/TelemetryTags.cs:23
- Dead code: Serverless src/Core/src/Eventuous.Diagnostics/TelemetryTags.cs:47
- Dead code: Deconstruct src/Core/src/Eventuous.Domain/Id.cs:27
- Dead code: GetRegisteredEventTypes src/Core/src/Eventuous.Domain/State.cs:39
- Dead code: CreateAggregateUsing src/Core/src/Eventuous.Persistence/AggregateFactory.cs:34
- Dead code: Deconstruct src/Core/src/Eventuous.Persistence/ExpectedStreamVersion.cs:25
- Dead code: PageSize src/Core/src/Eventuous.Persistence/StateStore/StateStore.cs:14
- Dead code: AddEventProducer src/Core/src/Eventuous.Producers/RegistrationExtensions.cs:17
- Dead code: AddEventProducer src/Core/src/Eventuous.Producers/RegistrationExtensions.cs:36
- Dead code: AddEventProducer src/Core/src/Eventuous.Producers/RegistrationExtensions.cs:53
- Dead code: SetDefaultSerializer src/Core/src/Eventuous.Serialization/DefaultMetadataSerializer.cs:13
- Dead code: GetCategory src/Core/src/Eventuous.Shared/Store/StreamName.cs:31
- Dead code: EnsureTypesRegistered src/Core/src/Eventuous.Shared/TypeMap/TypeMapperExtensions.cs:54
- Dead code: PrintMembers src/Core/src/Eventuous.Subscriptions/Checkpoints/CheckpointCommitHandler.cs:176
- Dead code: GetResultsOf src/Core/src/Eventuous.Subscriptions/Handlers/EventHandlingResult.cs:49
- Dead code: MessageTypeNotFound src/Core/src/Eventuous.Subscriptions/Logging/SubscriptionLogging.cs:148
- Async method without CancellationToken: ProcessMessageBatch src/Benchmarks/Benchmarks/SubscriptionMessageProcessingBenchmarks.cs:70
- Async method without CancellationToken: HandleError src/Azure/src/Eventuous.Azure.ServiceBus/Subscriptions/ServiceBusSubscription.cs:42
- Async method without CancellationToken: HandleEvent src/Azure/src/Eventuous.Azure.Storage.Blobs/BlobStorageProjector.cs:112
- Async method without CancellationToken: EnsureExchange src/RabbitMq/src/Eventuous.RabbitMq/Producers/ExchangeCache.cs:10
- Async method without CancellationToken: DefaultEventFailureHandler src/RabbitMq/src/Eventuous.RabbitMq/Subscriptions/RabbitMqSubscription.cs:249
- Async method without CancellationToken: MatchAsync src/Core/src/Eventuous.Application/Result.cs:130
- Async method without CancellationToken: Trace src/Core/src/Eventuous.Persistence/Diagnostics/Tracing/BaseTracer.cs:19
- Async method without CancellationToken: Trace src/Core/src/Eventuous.Persistence/Diagnostics/Tracing/BaseTracer.cs:36
- Async method without CancellationToken: StopWorker src/Core/src/Eventuous.Subscriptions/Channels/ChannelWorkerBase.cs:56
- Async method without CancellationToken: Consume src/Core/src/Eventuous.Subscriptions/Consumers/DefaultConsumer.cs:10
- Async method without CancellationToken: Handler src/Core/src/Eventuous.Subscriptions/EventSubscription.cs:242
- Async method without CancellationToken: HandleInternal src/Core/src/Eventuous.Subscriptions/EventSubscriptionWithCheckpoint.cs:111
- Async method without CancellationToken: Ack src/Core/src/Eventuous.Subscriptions/EventSubscriptionWithCheckpoint.cs:141
- Async method without CancellationToken: Send src/Core/src/Eventuous.Subscriptions/Filters/TracingFilter.cs:22
- Async method without CancellationToken: HandleEvent src/Core/src/Eventuous.Subscriptions/Handlers/EventHandler.cs:60
- Async method without CancellationToken: HandleEvent src/Core/src/Eventuous.Subscriptions/Handlers/TracedEventHandler.cs:26
- Async method without CancellationToken: Execute src/Experimental/src/ElasticPlayground/CombinedStore.cs:22
- Async method without CancellationToken: Seed src/Experimental/src/ElasticPlayground/CombinedStore.cs:39
- Async method without CancellationToken: ConfigureIndex src/Experimental/src/ElasticPlayground/ConfigureElastic.cs:8
- Async method without CancellationToken: Execute src/Experimental/src/ElasticPlayground/ConnectorAndArchive.cs:22
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/AggregateService/CommandHandlerBuilder.cs:53
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/AggregateService/CommandService.Async.cs:18
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/AggregateService/CommandService.Sync.cs:18
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/AggregateService/CommandService.cs:18
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Diagnostics/ApplicationEventSource.cs:10
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Diagnostics/CommandServiceActivity.cs:9
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Diagnostics/CommandServiceMetrics.cs:15
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/FunctionalService/CommandHandlerBuilder.cs:42
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/FunctionalService/CommandService.cs:11
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/FunctionalService/FuncHandlerDelegateExtensions.cs:9
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/FunctionalService/FuncServiceDelegates.cs:13
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/FunctionalService/HandlersMap.cs:4
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Persistence/ProposedAppend.cs:12
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Persistence/WriterExtensions.cs:7
- Dependency-rule violation: Eventuous.Application (Application) → Eventuous.Persistence (Infrastructure) src/Core/src/Eventuous.Application/Result.cs:131
- BarePragmaDisable src/Core/src/Eventuous.Subscriptions/EventSubscriptionWithCheckpoint.cs:44
- BarePragmaDisable src/Core/src/Eventuous.Subscriptions/Logging/InternalLogger.cs:11
- BarePragmaDisable src/Diagnostics/src/Eventuous.Diagnostics.Logging/LoggingEventListener.cs:48
- BarePragmaDisable src/KurrentDB/src/Eventuous.KurrentDB/KurrentDBEventStore.cs:286
- BarePragmaDisable src/KurrentDB/src/Eventuous.KurrentDB/KurrentDBEventStore.cs:361
- BarePragmaDisable src/Core/test/Eventuous.Tests.Subscriptions/CompositionHandlerTests.cs:117
- BarePragmaDisable src/KurrentDB/src/Eventuous.KurrentDB/Subscriptions/PersistentSubscriptionBase.cs:175
- BarePragmaDisable src/Core/test/Eventuous.Tests/ForgotToSetId.cs:25
- BarePragmaDisable src/Diagnostics/test/Eventuous.Tests.OpenTelemetry/Fakes/TestExporter.cs:13
- BarePragmaDisable src/Extensions/test/Eventuous.Sut.AspNetCore/Program.cs:22
- BarePragmaDisable src/Extensions/test/Eventuous.Tests.Extensions.AspNetCore/AggregateCommandsTests.cs:60
- BarePragmaDisable src/KurrentDB/src/Eventuous.KurrentDB/Subscriptions/StreamSubscription.cs:79
- BarePragmaDisable src/RabbitMq/test/Eventuous.Tests.RabbitMq/CustomQueueSubscriptionSpec.cs:17
- BarePragmaDisable src/RabbitMq/test/Eventuous.Tests.RabbitMq/HandlerFailureSpec.cs:28
- BarePragmaDisable src/RabbitMq/test/Eventuous.Tests.RabbitMq/SubscriptionSpec.cs:17
- No assertions: should_produce_payment_registered src/Core/test/Eventuous.Tests/Aggregates/OperateOnExistingSpec.cs:13
- No assertions: should_produce_outstanding_changed src/Core/test/Eventuous.Tests/Aggregates/OperateOnExistingSpec.cs:16
- No assertions: should_produce_fully_paid_event src/Core/test/Eventuous.Tests/Aggregates/TwoAggregateOpsSpec.cs:20
- No assertions: should_produce_payment_registered src/Core/test/Eventuous.Tests/Aggregates/TwoAggregateOpsSpec.cs:23
- No assertions: should_produce_outstanding_changed src/Core/test/Eventuous.Tests/Aggregates/TwoAggregateOpsSpec.cs:26
- No assertions: should_emit_event src/Core/test/Eventuous.Tests/AggregateWithId/OperateOnAggregateWithId.cs:12
- No assertions: Test src/Gateway/test/Eventuous.Tests.Gateway/RegistrationTests.cs:18
- No assertions: AppendedEventShouldBeTraced src/KurrentDB/test/Eventuous.Tests.KurrentDB/Store/AggregateStoreTests.cs:21
- No assertions: Sqlite_ShouldTolerateRepeatedUnsubscribe src/Sqlite/test/Eventuous.Tests.Sqlite/Subscriptions/SubscriptionRestartTests.cs:31
- BareSuppressMessage src/Azure/test/Eventuous.Tests.Azure.ServiceBus/TestSetup.cs:9
- BareSuppressMessage src/Core/src/Eventuous.Subscriptions/Logging/Logger.cs:34
- BareSuppressMessage src/Core/test/Eventuous.Tests.Subscriptions.Base/TestSetup.cs:9
- BareSuppressMessage src/Core/test/Eventuous.Tests.Subscriptions/DefaultConsumerTests.cs:9
- BareSuppressMessage src/Core/test/Eventuous.Tests.Subscriptions/TestSetup.cs:9
- BareSuppressMessage src/Gateway/test/Eventuous.Tests.Gateway/TestSetup.cs:9
- BareSuppressMessage src/SignalR/test/Eventuous.Tests.SignalR.Integration/TestSetup.cs:9
- BareSuppressMessage src/SignalR/test/Eventuous.Tests.SignalR/TestSetup.cs:9
- Async local function without CancellationToken: ProduceLocal src/GooglePubSub/src/Eventuous.GooglePubSub/Producers/GooglePubSubProducer.cs:87
- Async local function without CancellationToken: ProduceLocal src/Kafka/src/Eventuous.Kafka/Producers/KafkaBasicProducer.cs:50
- Async local function without CancellationToken: CastAndDispose src/Kafka/src/Eventuous.Kafka/Producers/KafkaBasicProducer.cs:116
- Async local function without CancellationToken: Ack src/RabbitMq/src/Eventuous.RabbitMq/Subscriptions/RabbitMqSubscription.cs:190
- Async local function without CancellationToken: Nack src/RabbitMq/src/Eventuous.RabbitMq/Subscriptions/RabbitMqSubscription.cs:196
- Async local function without CancellationToken: Handle src/Core/src/Eventuous.Subscriptions/Consumers/DefaultConsumer.cs:39
- Async local function without CancellationToken: Handle src/Core/src/Eventuous.Subscriptions/Handlers/EventHandler.cs:42
- Async local function without CancellationToken: HandleTypedEvent src/Core/src/Eventuous.Subscriptions/Handlers/EventHandler.cs:45
- Fixed-sleep synchronisation: LiveEvents_DeliveredAfterSubscribe src/SignalR/test/Eventuous.Tests.SignalR.Integration/SignalREndToEndTests.cs:169
- Fixed-sleep synchronisation: SubscribeAsync_CreatesSubscriptionViaFactory src/SignalR/test/Eventuous.Tests.SignalR/SubscriptionGatewayTests.cs:56
- Fixed-sleep synchronisation: UnsubscribeAsync_RemovesSubscription src/SignalR/test/Eventuous.Tests.SignalR/SubscriptionGatewayTests.cs:66
- Fixed-sleep synchronisation: RemoveConnectionAsync_CleansUpAllSubscriptions src/SignalR/test/Eventuous.Tests.SignalR/SubscriptionGatewayTests.cs:80
- Fixed-sleep synchronisation: DuplicateSubscribe_ReplacesPrevious src/SignalR/test/Eventuous.Tests.SignalR/SubscriptionGatewayTests.cs:102
- Unfinished stub — throws NotImplementedException src/Kafka/src/Eventuous.Kafka/Subscriptions/KafkaBasicSubscription.cs:12
- Unfinished stub — throws NotImplementedException src/Experimental/src/Eventuous.ElasticSearch/Store/ElasticEventStore.cs:107
- Unfinished stub — throws NotImplementedException src/Experimental/src/Eventuous.ElasticSearch/Store/ElasticEventStore.cs:114
- Unfinished stub — throws NotImplementedException src/Redis/src/Eventuous.Redis/RedisStore.cs:93
- Unfinished stub — throws NotImplementedException src/Relational/src/Eventuous.Sql.Base/SqlEventStoreBase.cs:261
- Unfinished stub — throws NotImplementedException src/Experimental/src/Eventuous.ElasticSearch/Store/ElasticEventStore.cs:107
- Unfinished stub — throws NotImplementedException src/Experimental/src/Eventuous.ElasticSearch/Store/ElasticEventStore.cs:114
- Unfinished stub — throws NotImplementedException src/Kafka/src/Eventuous.Kafka/Subscriptions/KafkaBasicSubscription.cs:12
- Unfinished stub — throws NotImplementedException src/Redis/src/Eventuous.Redis/RedisStore.cs:93
- Unfinished stub — throws NotImplementedException src/Relational/src/Eventuous.Sql.Base/SqlEventStoreBase.cs:261
- Process-global static state: EventuousDiagnostics src/Core/src/Eventuous.Diagnostics/EventuousDiagnostics.cs:8
- Process-global static state: DefaultMetadataSerializer src/Core/src/Eventuous.Serialization/DefaultMetadataSerializer.cs:9
- Process-global static state: EventSerializer src/Core/src/Eventuous.Serialization/EventSerializer.cs:11
- Process-global static state: LoggerFactoryExtensions src/Extensions/src/Eventuous.Extensions.Logging/LoggerFactoryExtensions.cs:10
- Duplicated block (5 lines × 2) src/Core/gen/Eventuous.Shared.Generators/EventUsageAnalyzer.cs:129
- Duplicated block (5 lines × 2) src/Extensions/src/Eventuous.Extensions.DependencyInjection/Registrations/Stores.cs:127
- Duplicated block (5 lines × 2) src/Core/src/Eventuous.Application/AggregateService/CommandService.cs:108
- Duplicated block (5 lines × 2) samples/kurrentdb/Bookings/HttpApi/Bookings/QueryApi.cs:13
- Stateful singleton: SubscriptionBuilder src/Core/src/Eventuous.Subscriptions/Registrations/SubscriptionBuilder.cs:302
- Stateful singleton: TypeMapper src/Core/src/Eventuous.Shared/TypeMap/TypeMapper.cs:37
- Stateful singleton: AggregateFactoryRegistry src/Core/src/Eventuous.Persistence/AggregateFactory.cs:10
- Duplicated block (9 lines × 2) src/Extensions/src/Eventuous.Extensions.DependencyInjection/Registrations/Services.cs:24
- Duplicated block (9 lines × 2) src/SqlServer/src/Eventuous.SqlServer/Extensions/RegistrationExtensions.cs:78
- Duplicated block (9 lines × 2) src/Experimental/src/ElasticPlayground/CombinedStore.cs:39
- Sync-over-async blocking
- Sync-over-async blocking src/Kafka/src/Eventuous.Kafka/Producers/KafkaBasicProducer.cs:75
- Sync-over-async blocking src/Core/src/Eventuous.Subscriptions/Diagnostics/SubscriptionMetrics.cs:115
- Stateful shared instance: TypeMapper src/Core/src/Eventuous.Shared/TypeMap/TypeMapper.cs:37
- Stateful shared instance: LoggingEventListener src/Diagnostics/src/Eventuous.Diagnostics.Logging/LoggingEventListener.cs:6
- Prerelease dependency: OpenTelemetry.Exporter.Prometheus.AspNetCore
- Prerelease dependency: OpenTelemetry.Instrumentation.GrpcNetClient
- Hotspot: src/Relational/src/Eventuous.Sql.Base/Subscriptions/SqlSubscriptionBase.cs src/Relational/src/Eventuous.Sql.Base/Subscriptions/SqlSubscriptionBase.cs:80
- Hotspot: src/Core/src/Eventuous.Subscriptions/EventSubscription.cs src/Core/src/Eventuous.Subscriptions/EventSubscription.cs:242
- TodoComment src/Extensions/src/Eventuous.Extensions.AspNetCore/Http/CommandMappingRegistry.cs:22
- TodoComment src/Mongo/src/Eventuous.Projections.MongoDB/Operations/UpdateBuilder.cs:28
- CommentedOutCode src/KurrentDB/test/Eventuous.Tests.KurrentDB/Subscriptions/StreamSubscriptionWithLinksTests.cs:85
- CommentedOutCode src/Mongo/src/Eventuous.Projections.MongoDB/Operations/UpdateBuilder.cs:29
- REDACTED
- REDACTED
- Change coupling: EventuousDiagnostics.cs ↔ MeterProviderBuilderExtensions.cs src/Core/src/Eventuous.Diagnostics/EventuousDiagnostics.cs:1
- Change coupling: EventSubscription.cs ↔ AsyncHandlingFilter.cs src/Core/src/Eventuous.Subscriptions/EventSubscription.cs:1
- Duplicated block (12 lines × 2) src/SqlServer/src/Eventuous.SqlServer/Subscriptions/SqlServerCheckpointStore.cs:43
- Duplicated block (12 lines × 2) samples/kurrentdb/Bookings/Application/BookingsCommandService.cs:19
- Duplicated block (6 lines × 2) src/Relational/src/Eventuous.Sql.Base/SqlEventStoreBase.cs:214
- Duplicated block (6 lines × 2) samples/postgres/Bookings.Payments/Program.cs:46
- Duplicated block (7 lines × 2) src/SqlServer/src/Eventuous.SqlServer/Subscriptions/SqlServerCheckpointStore.cs:24
- Duplicated block (7 lines × 2) samples/kurrentdb/Bookings/Integration/Payments.cs:14
- Sync-over-async (deadlock risk) src/Kafka/src/Eventuous.Kafka/Producers/KafkaBasicProducer.cs:75
- Sync-over-async (deadlock risk) src/Core/src/Eventuous.Subscriptions/Diagnostics/SubscriptionMetrics.cs:115
- Disposable created and abandoned in the method that made it src/Core/src/Eventuous.Subscriptions/SubscriptionHostedService.cs:25
- Disposable created and abandoned in the method that made it src/Core/src/Eventuous.Subscriptions/SubscriptionHostedService.cs:38
- Swallowed exception (caught, then discarded) src/Core/src/Eventuous.Persistence/EventStore/StoreFunctions.cs:229
- Swallowed exception (caught, then discarded) src/Core/src/Eventuous.Subscriptions/Channels/ChannelExtensions.cs:84
- HttpCommandStateMismatchAnalyzer.AnalyzeInvocation (cyclomatic 41) src/Extensions/gen/Eventuous.Extensions.AspNetCore.Generators/HttpCommandStateMismatchAnalyzer.cs:33
- EventUsageAnalyzer.AnalyzeInvocation (cyclomatic 30) src/Core/gen/Eventuous.Shared.Generators/EventUsageAnalyzer.cs:118
- ConsumeContextConverterGenerator.TransformWithSymbol (cyclomatic 20) src/Core/gen/Eventuous.Subscriptions.Generators/ConsumeContextConverterGenerator.cs:79
- Handler.Handle (cyclomatic 19) src/Azure/src/Eventuous.Azure.Storage.Blobs/BlobStorageProjector.cs:136
- SqlSubscriptionBase.Poll (cyclomatic 17) src/Relational/src/Eventuous.Sql.Base/Subscriptions/SqlSubscriptionBase.cs:80
- SetupIndex.AddTier (cyclomatic 16) src/Experimental/src/Eventuous.ElasticSearch/Index/IndexSetup.cs:91
- Deprecated: NEST Directory.Packages.props:61
- HttpCommandStateMismatchAnalyzer.AnalyzeInvocation (cognitive 81) src/Extensions/gen/Eventuous.Extensions.AspNetCore.Generators/HttpCommandStateMismatchAnalyzer.cs:33
- ConsumeContextConverterGenerator.TransformWithSymbol (cognitive 41) src/Core/gen/Eventuous.Subscriptions.Generators/ConsumeContextConverterGenerator.cs:79
- KurrentDBEventStore.EnumerateStream (cognitive 30) src/KurrentDB/src/Eventuous.KurrentDB/KurrentDBEventStore.cs:247
- HttpCommandMappingGenerator.Execute (cognitive 28) src/Extensions/gen/Eventuous.Extensions.AspNetCore.Generators/HttpCommandMappingGenerator.cs:116
- HttpCommandMappingGenerator.DiscoverStateTypes (cognitive 27) src/Extensions/gen/Eventuous.Extensions.AspNetCore.Generators/HttpCommandMappingGenerator.cs:71
- EventUsageAnalyzer.AnalyzeInvocation (cognitive 26) src/Core/gen/Eventuous.Shared.Generators/EventUsageAnalyzer.cs:118
- SqlSubscriptionBase.Poll (cognitive 25) src/Relational/src/Eventuous.Sql.Base/Subscriptions/SqlSubscriptionBase.cs:80
- Handler.Handle (cognitive 21) src/Azure/src/Eventuous.Azure.Storage.Blobs/BlobStorageProjector.cs:136
- ChannelExtensions.ReadAllBatches (cognitive 21) src/Core/src/Eventuous.Subscriptions/Channels/ChannelExtensions.cs:65
- EventSubscription.Handler (cognitive 20) src/Core/src/Eventuous.Subscriptions/EventSubscription.cs:242
- TypeMappingsGenerator.TryGetEventTypeName (cognitive 16) src/Core/gen/Eventuous.Shared.Generators/TypeMappingsGenerator.cs:120
- HttpCommandStateMismatchAnalyzer.GetHttpCommandStateTypeArg (cognitive 16) src/Extensions/gen/Eventuous.Extensions.AspNetCore.Generators/HttpCommandStateMismatchAnalyzer.cs:149
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (23 lines × 2) src/Core/src/Eventuous.Application/Persistence/WriterExtensions.cs:44
- Duplicated block (18 lines × 2) src/Redis/src/Eventuous.Redis/Subscriptions/RedisSubscriptionBase.cs:51
- Duplicated block (16–19 lines × 3) src/Extensions/gen/Eventuous.Extensions.AspNetCore.Generators/HttpCommandStateMismatchAnalyzer.cs:54
- Duplicated block (9–19 lines × 2) src/Relational/src/Eventuous.Sql.Base/SqlEventStoreBase.cs:230
- Duplicated block (11–16 lines × 3) src/Postgres/src/Eventuous.Postgresql/Schema.cs:42
- Duplicated block (13–15 lines × 2) src/Core/gen/Eventuous.Shared.Generators/TypeMappingsGenerator.cs:240
- Duplicated block (13 lines × 2) src/SqlServer/src/Eventuous.SqlServer/SchemaInitializer.cs:12
- Duplicated block (11–12 lines × 2) src/Core/gen/Eventuous.Subscriptions.Generators/ConsumeContextConverterGenerator.cs:83
- Duplicated block (8 lines × 2) src/Azure/src/Eventuous.Azure.ServiceBus/Subscriptions/ServiceBusSubscription.cs:181
- Duplicated block (29 lines × 2) samples/kurrentdb/Bookings/Application/Queries/MyBookingsProjection.cs:8
- Duplicated block (17–18 lines × 2) samples/kurrentdb/Bookings/Application/Queries/BookingStateProjection.cs:11
- Duplicated block (10–14 lines × 2) samples/kurrentdb/Bookings/Infrastructure/Mongo.cs:11
- Duplicated block (9–11 lines × 2) samples/kurrentdb/Bookings/Registrations.cs:32
- Off the main sequence: Eventuous.Diagnostics(net10.0) (src/Core/src/Eventuous.Diagnostics) src/Core/src/Eventuous.Diagnostics/Eventuous.Diagnostics.csproj:1
- Low cohesion: AllocationHotspotsBenchmarks (LCOM4 8) src/Benchmarks/Benchmarks/AllocationHotspotsBenchmarks.cs:11
- README may be stale
- Argument guard throws the exception its own condition disproves samples/kurrentdb/Bookings/HttpApi/Bookings/CommandApiWithCustomResult.cs:43
- Swallowed exception (empty catch) src/Mongo/src/Eventuous.Projections.MongoDB/Tools/MongoCollectionExtensions.cs:209
Minor — 80 finding(s)
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/AggregateService/CommandService.Async.cs:14
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/AggregateService/CommandService.Async.cs:35
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/AggregateService/CommandService.Async.cs:57
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/AggregateService/CommandService.Async.cs:79
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/AggregateService/CommandService.Async.cs:101
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/AggregateService/CommandService.Sync.cs:14
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/FunctionalService/CommandService.cs:16
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/AggregateService/CommandService.Sync.cs:35
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/FunctionalService/CommandService.cs:20
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/AggregateService/CommandService.Sync.cs:56
- ObsoleteWithoutCallers src/Core/src/Eventuous.Application/FunctionalService/CommandService.cs:25
- ObsoleteWithoutCallers src/Core/src/Eventuous.Persistence/AggregateStore/AggregateStoreExtensions.cs:19
- ObsoleteWithoutCallers src/Core/src/Eventuous.Persistence/AggregateStore/AggregateStoreExtensions.cs:39
- ObsoleteWithoutCallers src/Core/src/Eventuous.Persistence/AggregateStore/IAggregateStore.cs:76
- ObsoleteWithoutCallers src/Core/src/Eventuous.Persistence/StateStore/IStateStore.cs:20
- ObsoleteWithoutCallers src/Core/src/Eventuous.Persistence/StateStore/StateStore.cs:16
- ObsoleteWithoutCallers src/Core/src/Eventuous.Persistence/StateStore/StateStore.cs:9
- ObsoleteWithoutCallers src/Core/src/Eventuous.Producers/RegistrationExtensions.cs:17
- ObsoleteWithoutCallers src/Core/src/Eventuous.Producers/RegistrationExtensions.cs:36
- ObsoleteWithoutCallers src/Core/src/Eventuous.Producers/RegistrationExtensions.cs:53
- ObsoleteWithoutCallers src/Experimental/src/Eventuous.Spyglass/RegistrationExtensions.cs:13
- ObsoleteWithoutCallers src/Testing/src/Eventuous.Testing/AggregateFactoryExtensions.cs:17
- Commented-out code src/Core/src/Eventuous.Subscriptions/Filters/AsyncHandlingFilter.cs:114
- Commented-out code src/Core/src/Eventuous.Subscriptions/Filters/AsyncHandlingFilter.cs:115
- Commented-out code src/Core/src/Eventuous.Subscriptions/Filters/PartitioningFilter.cs:37
- Commented-out code src/Core/src/Eventuous.Subscriptions/Registrations/NamedRegistrations.cs:18
- Commented-out code src/Experimental/src/ElasticPlayground/Program.cs:31
- Commented-out code src/Experimental/src/ElasticPlayground/Program.cs:32
- Commented-out code src/Experimental/src/ElasticPlayground/Program.cs:34
- Commented-out code src/Experimental/src/ElasticPlayground/Program.cs:35
- Commented-out code src/Experimental/src/ElasticPlayground/Program.cs:37
- Commented-out code src/Experimental/src/ElasticPlayground/Program.cs:38
- Commented-out code src/Experimental/src/Eventuous.ElasticSearch/Index/IndexSetup.cs:14
- Commented-out code REDACTED:92
- Commented-out code src/Gateway/src/Eventuous.Gateway/GatewayProducer.cs:33
- redundant comment src/Azure/test/Eventuous.Tests.Azure.Storage.Blobs/BlobStorageProjectorTests.cs:472
- redundant comment src/Benchmarks/Benchmarks/ContextAllocationBenchmarks.cs:151
- redundant comment src/Core/gen/Eventuous.Shared.Generators/TypeMappingsGenerator.cs:20
- redundant comment src/Core/gen/Eventuous.Shared.Generators/TypeMappingsGenerator.cs:88
- redundant comment src/Core/gen/Eventuous.Subscriptions.Generators/ConsumeContextConverterGenerator.cs:28
- redundant comment src/Core/test/Eventuous.Tests/TypeRegistrationTests.cs:14
- redundant comment src/Extensions/gen/Eventuous.Extensions.AspNetCore.Generators/HttpCommandMappingGenerator.cs:52
- redundant comment src/SignalR/src/Eventuous.SignalR.Server/SubscriptionGateway.cs:39
- Duplicated predicate src/Benchmarks/Benchmarks/ImplementedOptimizationsValidationBenchmarks.cs:204
- Duplicated predicate src/Benchmarks/Benchmarks/ImplementedOptimizationsValidationBenchmarks.cs:201
- Duplicated predicate src/Benchmarks/Benchmarks/OptimizationComparisonBenchmarks.cs:113
- Duplicated predicate src/Benchmarks/Benchmarks/OptimizationComparisonBenchmarks.cs:106
- Duplicated predicate src/Sqlite/src/Eventuous.Sqlite/Extensions/RegistrationExtensions.cs:78
- Duplicated predicate src/Redis/src/Eventuous.Redis/RedisStore.cs:85
- Duplicated predicate src/Core/gen/Eventuous.Shared.Generators/TypeMappingsGenerator.cs:251
- No security response headers detected
- No security response headers detected samples/kurrentdb/Bookings.Payments/Program.cs:9
- No security response headers detected samples/kurrentdb/Bookings/Program.cs:28
- No security response headers detected samples/postgres/Bookings.Payments/Program.cs:12
- No security response headers detected samples/postgres/Bookings/Program.cs:14
- No app-layer HTTPS enforcement detected
- No app-layer HTTPS enforcement detected samples/kurrentdb/Bookings.Payments/Program.cs:9
- No app-layer HTTPS enforcement detected samples/kurrentdb/Bookings/Program.cs:28
- No app-layer HTTPS enforcement detected samples/postgres/Bookings.Payments/Program.cs:12
- No app-layer HTTPS enforcement detected samples/postgres/Bookings/Program.cs:14
- Silent fallback default in catch src/Core/src/Eventuous.Subscriptions/Channels/ChannelWorkerBase.cs:36
- Silent fallback default in catch src/SignalR/src/Eventuous.SignalR.Client/TypedStreamSubscription.cs:152
- Fat interface: IBaseConsumeContext (16 members) src/Core/src/Eventuous.Subscriptions/Context/IMessageConsumeContext.cs:13
- Shell project: Eventuous(net10.0) src/Core/src/Eventuous/Eventuous.csproj
- Documentation: no build, run or usage example README.md:1
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- IL efficiency: 5 authored method(s) exceed the IL budget src/Extensions/gen/Eventuous.Extensions.AspNetCore.Generators/HttpCommandMappingGenerator.cs:117
- No ADRs
- README/code drift src/Benchmarks/Benchmarks/README.md:3
- Sleep-based test synchronization
- Logging is not universal
- No SAST REDACTED:4
- No rollback/health safety
- No changelog
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
- Silent fallback default on parse failure src/Experimental/src/ElasticPlayground/ResultExtensions.cs:5
Minor — 85 finding(s)
- Outdated: Azure.Messaging.ServiceBus
- Outdated: Microsoft.SourceLink.GitHub
- Outdated: MinVer
- Outdated: Azure.Storage.Blobs
- Outdated: coverlet.collector
- Outdated: Microsoft.Testing.Extensions.TrxReport
- Outdated: Testcontainers.ServiceBus
- Outdated: TUnit
- Outdated: Testcontainers.Azurite
- Outdated: Google.Cloud.PubSub.V1
- Outdated: Testcontainers
- Outdated: Confluent.Kafka
- Outdated: Testcontainers.Kafka
- Outdated: RabbitMQ.Client
- Outdated: Testcontainers.RabbitMq
- Outdated: Microsoft.CodeAnalysis.Analyzers
- Outdated: Microsoft.CodeAnalysis.CSharp
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions
- Outdated: Microsoft.Extensions.Hosting.Abstractions
- Outdated: System.Diagnostics.DiagnosticSource
- Outdated: Microsoft.Extensions.Diagnostics.HealthChecks
- Outdated: Microsoft.Extensions.DependencyInjection
- Outdated: TUnit.Assertions
- Outdated: TUnit.Core
- Outdated: Microsoft.CodeAnalysis
- doc comments repeat the names src/Core/src/Eventuous.Application/AggregateService/CommandService.cs:59
- doc comments repeat the names src/Azure/src/Eventuous.Azure.ServiceBus/Subscriptions/ServiceBusSubscription.cs:23
- doc comments repeat the names src/Diagnostics/src/Eventuous.Diagnostics.OpenTelemetry/MeterProviderBuilderExtensions.cs:13
- doc comments repeat the names src/Extensions/src/Eventuous.Extensions.AspNetCore/Http/CommandHttpApiBase.cs:29
- doc comments repeat the names src/Extensions/src/Eventuous.Extensions.DependencyInjection/LoggingServiceProviderExtensions.cs:19
- doc comments repeat the names src/Extensions/src/Eventuous.Extensions.Logging/LoggerFactoryExtensions.cs:16
- doc comments repeat the names src/GooglePubSub/src/Eventuous.GooglePubSub/Producers/GooglePubSubProducer.cs:12
- doc comments repeat the names src/GooglePubSub/src/Eventuous.GooglePubSub.CloudRun/CloudRunPubSubSubscriptionOptions.cs:8
- doc comments repeat the names src/KurrentDB/src/Eventuous.KurrentDB/Subscriptions/AllPersistentSubscription.cs:56
- doc comments repeat the names src/Core/src/Eventuous.Persistence/AggregateStore/AggregatePersistenceExtensions.cs:16
- doc comments repeat the names src/Postgres/src/Eventuous.Postgresql/Extensions/RegistrationExtensions.cs:22
- doc comments repeat the names src/Core/src/Eventuous.Producers/BaseProducer.cs:12
- doc comments repeat the names src/RabbitMq/src/Eventuous.RabbitMq/Producers/RabbitMqProducer.cs:14
- doc comments repeat the names src/Core/src/Eventuous.Shared/Meta/MetadataExtensions.cs:7
- doc comments repeat the names src/Core/gen/Eventuous.Shared.Generators/Polyfills/Index.cs:95
- doc comments repeat the names src/Relational/src/Eventuous.Sql.Base/ReaderExtensions.cs:17
- doc comments repeat the names src/SqlServer/src/Eventuous.SqlServer/Extensions/RegistrationExtensions.cs:22
- doc comments repeat the names src/Sqlite/src/Eventuous.Sqlite/Extensions/RegistrationExtensions.cs:22
- doc comments repeat the names src/Core/src/Eventuous.Subscriptions/Checkpoints/CheckpointCommitHandler.cs:92
- doc comments repeat the names src/Testing/src/Eventuous.Testing/AggregateSpec.cs:29
- doc comments repeat the names src/Azure/test/Eventuous.Tests.Azure.ServiceBus/AzureServiceBusFixture.cs:52
- Mock framework: NSubstitute
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-ebdbd89ff30341cd9a5bc51ea9969d30/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ebdbd89ff30341cd9a5bc51ea9969d30/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/Redis/src/Eventuous.Redis/Scripts . | 29 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Eventuous.slnx package --vulnerable --include-transitive --format json | 5 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 24 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 108 file(s) — `src/Azure/src/Eventuous.Azure.ServiceBus/Producers/ServiceBusMessageBatchBuilder.cs`, `src/Azure/src/Eventuous.Azure.ServiceBus/Producers/ServiceBusMessageBuilder.cs`, `src/Azure/src/Eventuous.Azure.ServiceBus/Subscriptions/ServiceBusSubscription.cs`, `src/Azure/src/Eventuous.Azure.Storage.Blobs/BlobStorageProjector.cs`, `src/Core/gen/Eventuous.Shared.Generators/EventUsageAnalyzer.cs`, … (+103 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure 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-034fef65a02d44e9b087305fd4627182 | 0 | artifacts/raw/osv-scanner.json |