Executive summary
Elders/Cronus falls short of our standard for production, in part because it has data fields that are written but never read. It scores 49 out of 100 and is rated Weak, and five of its 325 critical findings are security problems.
Code Health, at 35, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the two comments that repeat the code, or contradict it, worth about 5 points. Handling the discarded errors would lift Code Health itself, worth about 8 points. Raising Code Health to 70 would lift the score to about 58.
Thirteen errors are caught and ignored, so failures can go unnoticed. Two known security holes in the packages the code depends on can be used by attackers. Handling or logging the ignored errors and updating the vulnerable packages would close both risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The 305 data fields that are written but never read need removing.
The product code is 12,337 lines, about €26,000 to rebuild.
If Code Health rose from 35 to 70, the lowest score rated Strong, the score would rise from 49 to about 58.
New since the last survey: 1 finding
- Stateful singletons · Process-global static state: CronusLogger src/Elders.Cronus/Userfull/CronusLogger.cs
Fixed since the last survey: 22 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Cancellation propagation · Async method without CancellationToken: SaveInternalAsync src/Elders.Cronus/EventStore/AggregateRepository.cs
- Cancellation propagation · Async method without CancellationToken: OnAppendAsync src/Elders.Cronus/EventStore/CronusAggregateCommitInterceptor.cs
- Cancellation propagation · Async method without CancellationToken: OnAppendingAsync src/Elders.Cronus/EventStore/CronusAggregateCommitInterceptor.cs
- Cancellation propagation · Async method without CancellationToken: AppendAsync src/Elders.Cronus/EventStore/CronusEventStore.cs
- Cancellation propagation · Async method without CancellationToken: AppendAsync src/Elders.Cronus/EventStore/CronusEventStore.cs
- Cancellation propagation · Async method without CancellationToken: DeleteAsync src/Elders.Cronus/EventStore/CronusEventStore.cs
- Cancellation propagation · Async method without CancellationToken: LoadAggregateEventRaw src/Elders.Cronus/EventStore/CronusEventStore.cs
- Cancellation propagation · Async method without CancellationToken: LoadAsync src/Elders.Cronus/EventStore/CronusEventStore.cs
- Cancellation propagation · Async method without CancellationToken: LoadWithPagingAsync src/Elders.Cronus/EventStore/CronusEventStore.cs
- Cancellation propagation · Async method without CancellationToken: MigrateAsync src/Elders.Cronus/Migrations/CronusMigrator.cs
- Cancellation propagation · Async method without CancellationToken: SaveAsync src/Elders.Cronus/Projections/ProjectionRepository.cs
- Cancellation propagation · Async method without CancellationToken: SaveAsync src/Elders.Cronus/Projections/ProjectionRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetProjectionVersionsAsync src/Elders.Cronus/Projections/ProjectionRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetProjectionVersionsFromStoreAsync src/Elders.Cronus/Projections/ProjectionRepository.cs
- Cancellation propagation · Async method without CancellationToken: LoadProjectionStreamAsync src/Elders.Cronus/Projections/ProjectionRepository.cs
- Cancellation propagation · Async method without CancellationToken: LoadLiveProjectionVersion src/Elders.Cronus/Projections/ProjectionRepository.cs
- Cancellation propagation · Async method without CancellationToken: SaveAsync src/Elders.Cronus/Projections/ProjectionRepositoryWithFallback.cs
- Cancellation propagation · Async method without CancellationToken: InitializeAsync src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs
- Cancellation propagation · Async method without CancellationToken: ShouldBeRetriedAsync src/Elders.Cronus/Projections/Rebuilding/ProjectionVersionHelper.cs
- Cancellation propagation · Async method without CancellationToken: ShouldBeCanceledAsync src/Elders.Cronus/Projections/Rebuilding/ProjectionVersionHelper.cs
- Cancellation propagation · Async method without CancellationToken: AbstractRunAsync src/Elders.Cronus/Workflow/Workflow.cs
Rebuild cost: about €26,000 · Estimate
| Cost to rebuild | €8,700 to €44,000, for 145 to 465 hours of work, about 0.2 person-years for one engineer |
|---|---|
| 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.7 at a score of 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,337 lines of product code, of which 40% is declarations and boilerplate, 33% straight logic and 27% logic with branches |
| Comment lines | The estimate prices 11,306 lines. Comment lines count towards the size of 12,337 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Elders.Cronus.AspNetCore.Exceptions | 2 Elders.Cronus.Hosting | 3 Elders.Cronus.Projections.Cassandra.EventSourcing | 4 Elders.Cronus.Userfull | 5 Elders.Cronus.Workflow | 6 System | 7 Elders.Cronus.AtomicAction | 8 Elders.Cronus.EventStore.Players | 9 Elders.Cronus.FaultHandling | 10 Elders.Cronus.IntegrityValidation | 11 Elders.Cronus.Migrations | 12 Elders.Cronus.Projections.Cassandra | 13 Elders.Cronus.Discoveries | 14 Elders.Cronus.FaultHandling.Strategies | 15 Elders.Cronus.Projections.Rebuilding | 16 Elders.Cronus.Multitenancy | 17 Elders.Cronus.Projections.Versioning | 18 Elders.Cronus.Projections | 19 Elders.Cronus.EventStore.Index | 20 Elders.Cronus.EventStore | 21 Elders.Cronus.EventStore.Integrity | 22 Elders.Cronus.MessageProcessing | 23 Elders.Cronus.Cluster.Job | 24 Elders.Cronus | 25 Elders.Cronus.Cluster.Job.InMemory | 26 Elders.Cronus.DangerZone | 27 Elders.Cronus.EventStore.AutoUpdater.Commands | 28 Elders.Cronus.EventStore.AutoUpdater.Events | 29 Elders.Cronus.EventStore.Index.Handlers | 30 Elders.Cronus.Hosting.Heartbeat | 31 Elders.Cronus.AutoUpdates | 32 Elders.Cronus.EventStore.AutoUpdater | 33 (global) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Elders.Cronus.AspNetCore.Exceptions | |||||||||||||||||||||||||||||||||
| 2 Elders.Cronus.Hosting | |||||||||||||||||||||||||||||||||
| 3 Elders.Cronus.Projections.Cassandra.EventSourcing | |||||||||||||||||||||||||||||||||
| 4 Elders.Cronus.Userfull | |||||||||||||||||||||||||||||||||
| 5 Elders.Cronus.Workflow | |||||||||||||||||||||||||||||||||
| 6 System | |||||||||||||||||||||||||||||||||
| 7 Elders.Cronus.AtomicAction | 2 | ||||||||||||||||||||||||||||||||
| 8 Elders.Cronus.EventStore.Players | 1 | 2 | 5 | 3 | |||||||||||||||||||||||||||||
| 9 Elders.Cronus.FaultHandling | 2 | ||||||||||||||||||||||||||||||||
| 10 Elders.Cronus.IntegrityValidation | 1 | ||||||||||||||||||||||||||||||||
| 11 Elders.Cronus.Migrations | 3 | 1 | 13 | ||||||||||||||||||||||||||||||
| 12 Elders.Cronus.Projections.Cassandra | 1 | 1 | |||||||||||||||||||||||||||||||
| 13 Elders.Cronus.Discoveries | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||
| 14 Elders.Cronus.FaultHandling.Strategies | 6 | ||||||||||||||||||||||||||||||||
| 15 Elders.Cronus.Projections.Rebuilding | 3 | 4 | 16 | 2 | 3 | 6 | 11 | 7 | |||||||||||||||||||||||||
| 16 Elders.Cronus.Multitenancy | 4 | 1 | 2 | ||||||||||||||||||||||||||||||
| 17 Elders.Cronus.Projections.Versioning | 1 | 6 | 2 | 1 | 14 | 2 | 3 | 18 | |||||||||||||||||||||||||
| 18 Elders.Cronus.Projections | 2 | 1 | 4 | 1 | 2 | 5 | |||||||||||||||||||||||||||
| 19 Elders.Cronus.EventStore.Index | 6 | 1 | 3 | 2 | 11 | 16 | |||||||||||||||||||||||||||
| 20 Elders.Cronus.EventStore | 1 | 1 | 5 | ||||||||||||||||||||||||||||||
| 21 Elders.Cronus.EventStore.Integrity | 12 | 6 | |||||||||||||||||||||||||||||||
| 22 Elders.Cronus.MessageProcessing | 21 | 2 | 4 | 11 | |||||||||||||||||||||||||||||
| 23 Elders.Cronus.Cluster.Job | 1 | 1 | |||||||||||||||||||||||||||||||
| 24 Elders.Cronus | 1 | 1 | 2 | 3 | 2 | 4 | 1 | 1 | |||||||||||||||||||||||||
| 25 Elders.Cronus.Cluster.Job.InMemory | 4 | 6 | |||||||||||||||||||||||||||||||
| 26 Elders.Cronus.DangerZone | 1 | ||||||||||||||||||||||||||||||||
| 27 Elders.Cronus.EventStore.AutoUpdater.Commands | 4 | 4 | |||||||||||||||||||||||||||||||
| 28 Elders.Cronus.EventStore.AutoUpdater.Events | 5 | 5 | |||||||||||||||||||||||||||||||
| 29 Elders.Cronus.EventStore.Index.Handlers | 9 | 1 | 5 | ||||||||||||||||||||||||||||||
| 30 Elders.Cronus.Hosting.Heartbeat | 1 | 2 | |||||||||||||||||||||||||||||||
| 31 Elders.Cronus.AutoUpdates | 1 | 1 | |||||||||||||||||||||||||||||||
| 32 Elders.Cronus.EventStore.AutoUpdater | 1 | 5 | 5 | 2 | |||||||||||||||||||||||||||||
| 33 (global) | 1 |
7→4 Elders.Cronus.AtomicAction uses Elders.Cronus.Userfull✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.AtomicAction uses a type in Elders.Cronus.Userfull.
- The types involved
Elders.Cronus.AtomicAction.IAggregateRootAtomicAction→Elders.Cronus.Userfull.ResultElders.Cronus.AtomicAction.MissingAggregateRootAtomicAction→Elders.Cronus.Userfull.Result
- Direction
- Elders.Cronus.AtomicAction uses Elders.Cronus.Userfull, so a change to Elders.Cronus.Userfull can break Elders.Cronus.AtomicAction, while a change to Elders.Cronus.AtomicAction can't break Elders.Cronus.Userfull.
- Position
- Below the diagonal: Elders.Cronus.AtomicAction uses a module listed above it, which is the healthy direction.
8→20 Elders.Cronus.EventStore.Players uses Elders.Cronus.EventStore part of a loop✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.EventStore.Players uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.EventStore.Players.ReplayPublicEvents_Job→Elders.Cronus.EventStore.IEventStorePlayer
- Direction
- Elders.Cronus.EventStore.Players uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.EventStore.Players, while a change to Elders.Cronus.EventStore.Players can't break Elders.Cronus.EventStore.
- 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 Elders.Cronus.EventStore.Players uses Elders.Cronus.MessageProcessing part of a loop✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.EventStore.Players uses a type in Elders.Cronus.MessageProcessing.
- The types involved
Elders.Cronus.EventStore.Players.ReplayPublicEvents_Job→Elders.Cronus.MessageProcessing.ICronusContextAccessorElders.Cronus.EventStore.Players.ReplayPublicEvents_JobFactory→Elders.Cronus.MessageProcessing.ICronusContextAccessor
- Direction
- Elders.Cronus.EventStore.Players uses Elders.Cronus.MessageProcessing, so a change to Elders.Cronus.MessageProcessing can break Elders.Cronus.EventStore.Players, while a change to Elders.Cronus.EventStore.Players can't break Elders.Cronus.MessageProcessing.
- 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→23 Elders.Cronus.EventStore.Players uses Elders.Cronus.Cluster.Job part of a loop✕
- Connections
- 5 pairs of types, where a type in Elders.Cronus.EventStore.Players uses a type in Elders.Cronus.Cluster.Job.
- The types involved
Elders.Cronus.EventStore.Players.PublicEventsPlayer→Elders.Cronus.Cluster.Job.ICronusJobRunnerElders.Cronus.EventStore.Players.ReplayPublicEvents_Job→Elders.Cronus.Cluster.Job.CronusJobElders.Cronus.EventStore.Players.ReplayPublicEvents_Job→Elders.Cronus.Cluster.Job.IClusterOperationsElders.Cronus.EventStore.Players.ReplayPublicEvents_Job→Elders.Cronus.Cluster.Job.JobExecutionStatusElders.Cronus.EventStore.Players.ReplayPublicEvents_JobData→Elders.Cronus.Cluster.Job.IJobData
- Direction
- Elders.Cronus.EventStore.Players uses Elders.Cronus.Cluster.Job, so a change to Elders.Cronus.Cluster.Job can break Elders.Cronus.EventStore.Players, while a change to Elders.Cronus.EventStore.Players can't break Elders.Cronus.Cluster.Job.
- 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→24 Elders.Cronus.EventStore.Players uses Elders.Cronus part of a loop✕
- Connections
- 3 pairs of types, where a type in Elders.Cronus.EventStore.Players uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.EventStore.Players.PublicEventsPlayer→Elders.Cronus.ISystemTriggerElders.Cronus.EventStore.Players.ReplayPublicEventsRequested→Elders.Cronus.ISystemSignalElders.Cronus.EventStore.Players.ReplayPublicEvents_JobFactory→Elders.Cronus.BoundedContext
- Direction
- Elders.Cronus.EventStore.Players uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.EventStore.Players, while a change to Elders.Cronus.EventStore.Players can't break Elders.Cronus.
- 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→5 Elders.Cronus.FaultHandling uses Elders.Cronus.Workflow✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.FaultHandling uses a type in Elders.Cronus.Workflow.
- The types involved
Elders.Cronus.FaultHandling.InMemoryRetryWorkflow→Elders.Cronus.Workflow.ExecutionElders.Cronus.FaultHandling.InMemoryRetryWorkflow→Elders.Cronus.Workflow.Workflow
- Direction
- Elders.Cronus.FaultHandling uses Elders.Cronus.Workflow, so a change to Elders.Cronus.Workflow can break Elders.Cronus.FaultHandling, while a change to Elders.Cronus.FaultHandling can't break Elders.Cronus.Workflow.
- Position
- Below the diagonal: Elders.Cronus.FaultHandling uses a module listed above it, which is the healthy direction.
10→20 Elders.Cronus.IntegrityValidation uses Elders.Cronus.EventStore part of a loop✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.IntegrityValidation uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.IntegrityValidation.EmptyResolver→Elders.Cronus.EventStore.EventStream
- Direction
- Elders.Cronus.IntegrityValidation uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.IntegrityValidation, while a change to Elders.Cronus.IntegrityValidation can't break Elders.Cronus.EventStore.
- 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→5 Elders.Cronus.Migrations uses Elders.Cronus.Workflow✕
- Connections
- 3 pairs of types, where a type in Elders.Cronus.Migrations uses a type in Elders.Cronus.Workflow.
- The types involved
Elders.Cronus.Migrations.AggregateCommitMigrationWorkflow→Elders.Cronus.Workflow.ExecutionElders.Cronus.Migrations.MigrationWorkflowBase→Elders.Cronus.Workflow.ExecutionElders.Cronus.Migrations.MigrationWorkflowBase→Elders.Cronus.Workflow.Workflow
- Direction
- Elders.Cronus.Migrations uses Elders.Cronus.Workflow, so a change to Elders.Cronus.Workflow can break Elders.Cronus.Migrations, while a change to Elders.Cronus.Migrations can't break Elders.Cronus.Workflow.
- Position
- Below the diagonal: Elders.Cronus.Migrations uses a module listed above it, which is the healthy direction.
11→19 Elders.Cronus.Migrations uses Elders.Cronus.EventStore.Index part of a loop✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Migrations uses a type in Elders.Cronus.EventStore.Index.
- The types involved
Elders.Cronus.Migrations.MigrationHandler→Elders.Cronus.EventStore.Index.IAggregateCommitHandle
- Direction
- Elders.Cronus.Migrations uses Elders.Cronus.EventStore.Index, so a change to Elders.Cronus.EventStore.Index can break Elders.Cronus.Migrations, while a change to Elders.Cronus.Migrations can't break Elders.Cronus.EventStore.Index.
- 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→20 Elders.Cronus.Migrations uses Elders.Cronus.EventStore part of a loop✕
- Connections
- 13 pairs of types, where a type in Elders.Cronus.Migrations uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.Migrations.AggregateCommitMigrationWorkflow→Elders.Cronus.EventStore.AggregateCommitElders.Cronus.Migrations.CopyEventStore→Elders.Cronus.EventStore.AggregateEventRawElders.Cronus.Migrations.CronusMigrator→Elders.Cronus.EventStore.AggregateCommitElders.Cronus.Migrations.DeleteEventStoreEvents→Elders.Cronus.EventStore.AggregateEventRawElders.Cronus.Migrations.DeleteEventStoreEvents→Elders.Cronus.EventStore.IEventStoreFactoryElders.Cronus.Migrations.ICronusMigrator→Elders.Cronus.EventStore.AggregateCommitElders.Cronus.Migrations.IMigrationCustomLogic→Elders.Cronus.EventStore.AggregateCommitElders.Cronus.Migrations.IMigrationEventStorePlayer→Elders.Cronus.EventStore.IEventStorePlayerElders.Cronus.Migrations.MigrationHandler→Elders.Cronus.EventStore.AggregateCommitElders.Cronus.Migrations.MigrationRunnerBase→Elders.Cronus.EventStore.IEventStoreElders.Cronus.Migrations.MigrationRunnerBase→Elders.Cronus.EventStore.IEventStorePlayerElders.Cronus.Migrations.NoCronusMigrator→Elders.Cronus.EventStore.AggregateCommitElders.Cronus.Migrations.ValidateEventStore→Elders.Cronus.EventStore.AggregateEventRaw
- Direction
- Elders.Cronus.Migrations uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.Migrations, while a change to Elders.Cronus.Migrations can't break Elders.Cronus.EventStore.
- 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→18 Elders.Cronus.Projections.Cassandra uses Elders.Cronus.Projections part of a loop✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Projections.Cassandra uses a type in Elders.Cronus.Projections.
- The types involved
Elders.Cronus.Projections.Cassandra.ProjectionQueryOptions→Elders.Cronus.Projections.ProjectionVersion
- Direction
- Elders.Cronus.Projections.Cassandra uses Elders.Cronus.Projections, so a change to Elders.Cronus.Projections can break Elders.Cronus.Projections.Cassandra, while a change to Elders.Cronus.Projections.Cassandra can't break Elders.Cronus.Projections.
- 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→20 Elders.Cronus.Projections.Cassandra uses Elders.Cronus.EventStore part of a loop✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Projections.Cassandra uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.Projections.Cassandra.ProjectionQueryOptions→Elders.Cronus.EventStore.PagingOptions
- Direction
- Elders.Cronus.Projections.Cassandra uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.Projections.Cassandra, while a change to Elders.Cronus.Projections.Cassandra can't break Elders.Cronus.EventStore.
- 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.
13→5 Elders.Cronus.Discoveries uses Elders.Cronus.Workflow✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Discoveries uses a type in Elders.Cronus.Workflow.
- The types involved
Elders.Cronus.Discoveries.CronusWorkflowsDiscovery→Elders.Cronus.Workflow.IWorkflow
- Direction
- Elders.Cronus.Discoveries uses Elders.Cronus.Workflow, so a change to Elders.Cronus.Workflow can break Elders.Cronus.Discoveries, while a change to Elders.Cronus.Discoveries can't break Elders.Cronus.Workflow.
- Position
- Below the diagonal: Elders.Cronus.Discoveries uses a module listed above it, which is the healthy direction.
13→11 Elders.Cronus.Discoveries uses Elders.Cronus.Migrations✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.Discoveries uses a type in Elders.Cronus.Migrations.
- The types involved
Elders.Cronus.Discoveries.MigrationsDiscovery→Elders.Cronus.Migrations.IMigrationHandlerElders.Cronus.Discoveries.NoCustomLogic→Elders.Cronus.Migrations.IMigrationCustomLogic
- Direction
- Elders.Cronus.Discoveries uses Elders.Cronus.Migrations, so a change to Elders.Cronus.Migrations can break Elders.Cronus.Discoveries, while a change to Elders.Cronus.Discoveries can't break Elders.Cronus.Migrations.
- Position
- Below the diagonal: Elders.Cronus.Discoveries uses a module listed above it, which is the healthy direction.
13→20 Elders.Cronus.Discoveries uses Elders.Cronus.EventStore part of a loop✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.Discoveries uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.Discoveries.EventStoreDiscovery→Elders.Cronus.EventStore.IEventStoreElders.Cronus.Discoveries.NoCustomLogic→Elders.Cronus.EventStore.AggregateCommit
- Direction
- Elders.Cronus.Discoveries uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.Discoveries, while a change to Elders.Cronus.Discoveries can't break Elders.Cronus.EventStore.
- 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.
13→24 Elders.Cronus.Discoveries uses Elders.Cronus part of a loop✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Discoveries uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.Discoveries.CronusHostDiscovery→Elders.Cronus.ICronusHost
- Direction
- Elders.Cronus.Discoveries uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.Discoveries, while a change to Elders.Cronus.Discoveries can't break Elders.Cronus.
- 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.
14→9 Elders.Cronus.FaultHandling.Strategies uses Elders.Cronus.FaultHandling✕
- Connections
- 6 pairs of types, where a type in Elders.Cronus.FaultHandling.Strategies uses a type in Elders.Cronus.FaultHandling.
- The types involved
Elders.Cronus.FaultHandling.Strategies.ExponentialBackoff→Elders.Cronus.FaultHandling.RetryStrategyElders.Cronus.FaultHandling.Strategies.ExponentialBackoff→Elders.Cronus.FaultHandling.ShouldRetryElders.Cronus.FaultHandling.Strategies.FixedInterval→Elders.Cronus.FaultHandling.RetryStrategyElders.Cronus.FaultHandling.Strategies.FixedInterval→Elders.Cronus.FaultHandling.ShouldRetryElders.Cronus.FaultHandling.Strategies.Incremental→Elders.Cronus.FaultHandling.RetryStrategyElders.Cronus.FaultHandling.Strategies.Incremental→Elders.Cronus.FaultHandling.ShouldRetry
- Direction
- Elders.Cronus.FaultHandling.Strategies uses Elders.Cronus.FaultHandling, so a change to Elders.Cronus.FaultHandling can break Elders.Cronus.FaultHandling.Strategies, while a change to Elders.Cronus.FaultHandling.Strategies can't break Elders.Cronus.FaultHandling.
- Position
- Below the diagonal: Elders.Cronus.FaultHandling.Strategies uses a module listed above it, which is the healthy direction.
15→8 Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.EventStore.Players✕
- Connections
- 3 pairs of types, where a type in Elders.Cronus.Projections.Rebuilding uses a type in Elders.Cronus.EventStore.Players.
- The types involved
Elders.Cronus.Projections.Rebuilding.IProjection_JobFactory→Elders.Cronus.EventStore.Players.ReplayEventsOptionsElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_JobFactory→Elders.Cronus.EventStore.Players.ReplayEventsOptionsElders.Cronus.Projections.Rebuilding.RebuildProjection_JobFactory→Elders.Cronus.EventStore.Players.ReplayEventsOptions
- Direction
- Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.EventStore.Players, so a change to Elders.Cronus.EventStore.Players can break Elders.Cronus.Projections.Rebuilding, while a change to Elders.Cronus.Projections.Rebuilding can't break Elders.Cronus.EventStore.Players.
- Position
- Below the diagonal: Elders.Cronus.Projections.Rebuilding uses a module listed above it, which is the healthy direction.
15→17 Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.Projections.Versioning part of a loop✕
- Connections
- 4 pairs of types, where a type in Elders.Cronus.Projections.Rebuilding uses a type in Elders.Cronus.Projections.Versioning.
- The types involved
Elders.Cronus.Projections.Rebuilding.IProjection_JobFactory→Elders.Cronus.Projections.Versioning.VersionRequestTimeboxElders.Cronus.Projections.Rebuilding.ProjectionVersionHelper→Elders.Cronus.Projections.Versioning.ProjectionHasherElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_JobFactory→Elders.Cronus.Projections.Versioning.VersionRequestTimeboxElders.Cronus.Projections.Rebuilding.RebuildProjection_JobFactory→Elders.Cronus.Projections.Versioning.VersionRequestTimebox
- Direction
- Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.Projections.Versioning, so a change to Elders.Cronus.Projections.Versioning can break Elders.Cronus.Projections.Rebuilding, while a change to Elders.Cronus.Projections.Rebuilding can't break Elders.Cronus.Projections.Versioning.
- 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.
15→18 Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.Projections part of a loop✕
- Connections
- 16 pairs of types, where a type in Elders.Cronus.Projections.Rebuilding uses a type in Elders.Cronus.Projections.
- The types involved
Elders.Cronus.Projections.Rebuilding.IProjection_JobFactory→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Rebuilding.ProgressTracker→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Rebuilding.ProgressTracker→Elders.Cronus.Projections.RebuildProjectionFinishedElders.Cronus.Projections.Rebuilding.ProgressTracker→Elders.Cronus.Projections.RebuildProjectionProgressElders.Cronus.Projections.Rebuilding.ProgressTracker→Elders.Cronus.Projections.RebuildProjectionStartedElders.Cronus.Projections.Rebuilding.ProjectionVersionHelper→Elders.Cronus.Projections.IInitializableProjectionStoreElders.Cronus.Projections.Rebuilding.ProjectionVersionHelper→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Rebuilding.ProjectionVersionHelper→Elders.Cronus.Projections.ProjectionVersionsElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job→Elders.Cronus.Projections.IInitializableProjectionStoreElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job→Elders.Cronus.Projections.IProjectionWriterElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_JobData→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_JobFactory→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Rebuilding.RebuildProjection_Job→Elders.Cronus.Projections.IInitializableProjectionStoreElders.Cronus.Projections.Rebuilding.RebuildProjection_Job→Elders.Cronus.Projections.IProjectionWriterElders.Cronus.Projections.Rebuilding.RebuildProjection_JobData→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Rebuilding.RebuildProjection_JobFactory→Elders.Cronus.Projections.ProjectionVersion
- Direction
- Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.Projections, so a change to Elders.Cronus.Projections can break Elders.Cronus.Projections.Rebuilding, while a change to Elders.Cronus.Projections.Rebuilding can't break Elders.Cronus.Projections.
- 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.
15→19 Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.EventStore.Index part of a loop✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.Projections.Rebuilding uses a type in Elders.Cronus.EventStore.Index.
- The types involved
Elders.Cronus.Projections.Rebuilding.ProjectionVersionHelper→Elders.Cronus.EventStore.Index.IndexStatusElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job→Elders.Cronus.EventStore.Index.EventLookupInByteArray
- Direction
- Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.EventStore.Index, so a change to Elders.Cronus.EventStore.Index can break Elders.Cronus.Projections.Rebuilding, while a change to Elders.Cronus.Projections.Rebuilding can't break Elders.Cronus.EventStore.Index.
- 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.
15→20 Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.EventStore part of a loop✕
- Connections
- 3 pairs of types, where a type in Elders.Cronus.Projections.Rebuilding uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.Projections.Rebuilding.ProgressTracker→Elders.Cronus.EventStore.IMessageCounterElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job→Elders.Cronus.EventStore.IEventStorePlayerElders.Cronus.Projections.Rebuilding.RebuildProjection_Job→Elders.Cronus.EventStore.IEventStorePlayer
- Direction
- Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.Projections.Rebuilding, while a change to Elders.Cronus.Projections.Rebuilding can't break Elders.Cronus.EventStore.
- 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.
15→22 Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.MessageProcessing part of a loop✕
- Connections
- 6 pairs of types, where a type in Elders.Cronus.Projections.Rebuilding uses a type in Elders.Cronus.MessageProcessing.
- The types involved
Elders.Cronus.Projections.Rebuilding.ProgressTracker→Elders.Cronus.MessageProcessing.ICronusContextAccessorElders.Cronus.Projections.Rebuilding.ProjectionVersionHelper→Elders.Cronus.MessageProcessing.ICronusContextAccessorElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job→Elders.Cronus.MessageProcessing.ICronusContextAccessorElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_JobFactory→Elders.Cronus.MessageProcessing.ICronusContextAccessorElders.Cronus.Projections.Rebuilding.RebuildProjection_Job→Elders.Cronus.MessageProcessing.ICronusContextAccessorElders.Cronus.Projections.Rebuilding.RebuildProjection_JobFactory→Elders.Cronus.MessageProcessing.ICronusContextAccessor
- Direction
- Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.MessageProcessing, so a change to Elders.Cronus.MessageProcessing can break Elders.Cronus.Projections.Rebuilding, while a change to Elders.Cronus.Projections.Rebuilding can't break Elders.Cronus.MessageProcessing.
- 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.
15→23 Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.Cluster.Job part of a loop✕
- Connections
- 11 pairs of types, where a type in Elders.Cronus.Projections.Rebuilding uses a type in Elders.Cronus.Cluster.Job.
- The types involved
Elders.Cronus.Projections.Rebuilding.IProjection_JobFactory→Elders.Cronus.Cluster.Job.ICronusJobElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job→Elders.Cronus.Cluster.Job.CronusJobElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job→Elders.Cronus.Cluster.Job.IClusterOperationsElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job→Elders.Cronus.Cluster.Job.JobExecutionStatusElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_JobData→Elders.Cronus.Cluster.Job.IJobDataElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_JobFactory→Elders.Cronus.Cluster.Job.ICronusJobElders.Cronus.Projections.Rebuilding.RebuildProjection_Job→Elders.Cronus.Cluster.Job.CronusJobElders.Cronus.Projections.Rebuilding.RebuildProjection_Job→Elders.Cronus.Cluster.Job.IClusterOperationsElders.Cronus.Projections.Rebuilding.RebuildProjection_Job→Elders.Cronus.Cluster.Job.JobExecutionStatusElders.Cronus.Projections.Rebuilding.RebuildProjection_JobData→Elders.Cronus.Cluster.Job.IJobDataElders.Cronus.Projections.Rebuilding.RebuildProjection_JobFactory→Elders.Cronus.Cluster.Job.ICronusJob
- Direction
- Elders.Cronus.Projections.Rebuilding uses Elders.Cronus.Cluster.Job, so a change to Elders.Cronus.Cluster.Job can break Elders.Cronus.Projections.Rebuilding, while a change to Elders.Cronus.Projections.Rebuilding can't break Elders.Cronus.Cluster.Job.
- 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.
15→24 Elders.Cronus.Projections.Rebuilding uses Elders.Cronus part of a loop✕
- Connections
- 7 pairs of types, where a type in Elders.Cronus.Projections.Rebuilding uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.Projections.Rebuilding.ProgressTracker→Elders.Cronus.ISystemSignalElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job→Elders.Cronus.ISerializerElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_Job→Elders.Cronus.ISystemSignalElders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_JobFactory→Elders.Cronus.BoundedContextElders.Cronus.Projections.Rebuilding.RebuildProjection_Job→Elders.Cronus.ISerializerElders.Cronus.Projections.Rebuilding.RebuildProjection_Job→Elders.Cronus.ISystemSignalElders.Cronus.Projections.Rebuilding.RebuildProjection_JobFactory→Elders.Cronus.BoundedContext
- Direction
- Elders.Cronus.Projections.Rebuilding uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.Projections.Rebuilding, while a change to Elders.Cronus.Projections.Rebuilding can't break Elders.Cronus.
- 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.
16→13 Elders.Cronus.Multitenancy uses Elders.Cronus.Discoveries✕
- Connections
- 4 pairs of types, where a type in Elders.Cronus.Multitenancy uses a type in Elders.Cronus.Discoveries.
- The types involved
Elders.Cronus.Multitenancy.MultitenancyDiscovery→Elders.Cronus.Discoveries.DiscoveredModelElders.Cronus.Multitenancy.MultitenancyDiscovery→Elders.Cronus.Discoveries.DiscoveryBaseElders.Cronus.Multitenancy.MultitenancyDiscovery→Elders.Cronus.Discoveries.DiscoveryContextElders.Cronus.Multitenancy.MultitenancyDiscovery→Elders.Cronus.Discoveries.DiscoveryResult
- Direction
- Elders.Cronus.Multitenancy uses Elders.Cronus.Discoveries, so a change to Elders.Cronus.Discoveries can break Elders.Cronus.Multitenancy, while a change to Elders.Cronus.Multitenancy can't break Elders.Cronus.Discoveries.
- Position
- Below the diagonal: Elders.Cronus.Multitenancy uses a module listed above it, which is the healthy direction.
16→20 Elders.Cronus.Multitenancy uses Elders.Cronus.EventStore part of a loop✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Multitenancy uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.Multitenancy.DefaultTenantResolver→Elders.Cronus.EventStore.AggregateCommit
- Direction
- Elders.Cronus.Multitenancy uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.Multitenancy, while a change to Elders.Cronus.Multitenancy can't break Elders.Cronus.EventStore.
- 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.
16→24 Elders.Cronus.Multitenancy uses Elders.Cronus part of a loop✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.Multitenancy uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.Multitenancy.DefaultTenantResolver→Elders.Cronus.CronusMessageElders.Cronus.Multitenancy.TenantsOptionsProvider→Elders.Cronus.CronusOptionsProviderBase
- Direction
- Elders.Cronus.Multitenancy uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.Multitenancy, while a change to Elders.Cronus.Multitenancy can't break Elders.Cronus.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→5 Elders.Cronus.Projections.Versioning uses Elders.Cronus.Workflow✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Projections.Versioning uses a type in Elders.Cronus.Workflow.
- The types involved
Elders.Cronus.Projections.Versioning.EventStoreIndexSubscriber→Elders.Cronus.Workflow.Workflow
- Direction
- Elders.Cronus.Projections.Versioning uses Elders.Cronus.Workflow, so a change to Elders.Cronus.Workflow can break Elders.Cronus.Projections.Versioning, while a change to Elders.Cronus.Projections.Versioning can't break Elders.Cronus.Workflow.
- Position
- Below the diagonal: Elders.Cronus.Projections.Versioning uses a module listed above it, which is the healthy direction.
17→8 Elders.Cronus.Projections.Versioning uses Elders.Cronus.EventStore.Players✕
- Connections
- 6 pairs of types, where a type in Elders.Cronus.Projections.Versioning uses a type in Elders.Cronus.EventStore.Players.
- The types involved
Elders.Cronus.Projections.Versioning.FixProjectionVersion→Elders.Cronus.EventStore.Players.ReplayEventsOptionsElders.Cronus.Projections.Versioning.NewProjectionVersion→Elders.Cronus.EventStore.Players.ReplayEventsOptionsElders.Cronus.Projections.Versioning.ProjectionBuilder→Elders.Cronus.EventStore.Players.ReplayEventsOptionsElders.Cronus.Projections.Versioning.ProjectionVersionManager→Elders.Cronus.EventStore.Players.ReplayEventsOptionsElders.Cronus.Projections.Versioning.ProjectionVersionRequested→Elders.Cronus.EventStore.Players.ReplayEventsOptionsElders.Cronus.Projections.Versioning.RegisterProjection→Elders.Cronus.EventStore.Players.ReplayEventsOptions
- Direction
- Elders.Cronus.Projections.Versioning uses Elders.Cronus.EventStore.Players, so a change to Elders.Cronus.EventStore.Players can break Elders.Cronus.Projections.Versioning, while a change to Elders.Cronus.Projections.Versioning can't break Elders.Cronus.EventStore.Players.
- Position
- Below the diagonal: Elders.Cronus.Projections.Versioning uses a module listed above it, which is the healthy direction.
17→15 Elders.Cronus.Projections.Versioning uses Elders.Cronus.Projections.Rebuilding✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.Projections.Versioning uses a type in Elders.Cronus.Projections.Rebuilding.
- The types involved
Elders.Cronus.Projections.Versioning.ProjectionBuilder→Elders.Cronus.Projections.Rebuilding.RebuildProjectionSequentially_JobFactoryElders.Cronus.Projections.Versioning.ProjectionBuilder→Elders.Cronus.Projections.Rebuilding.RebuildProjection_JobFactory
- Direction
- Elders.Cronus.Projections.Versioning uses Elders.Cronus.Projections.Rebuilding, so a change to Elders.Cronus.Projections.Rebuilding can break Elders.Cronus.Projections.Versioning, while a change to Elders.Cronus.Projections.Versioning can't break Elders.Cronus.Projections.Rebuilding.
- Position
- Below the diagonal: Elders.Cronus.Projections.Versioning uses a module listed above it, which is the healthy direction.
17→16 Elders.Cronus.Projections.Versioning uses Elders.Cronus.Multitenancy✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Projections.Versioning uses a type in Elders.Cronus.Multitenancy.
- The types involved
Elders.Cronus.Projections.Versioning.ProjectionBuilder→Elders.Cronus.Multitenancy.TenantsOptions
- Direction
- Elders.Cronus.Projections.Versioning uses Elders.Cronus.Multitenancy, so a change to Elders.Cronus.Multitenancy can break Elders.Cronus.Projections.Versioning, while a change to Elders.Cronus.Projections.Versioning can't break Elders.Cronus.Multitenancy.
- Position
- Below the diagonal: Elders.Cronus.Projections.Versioning uses a module listed above it, which is the healthy direction.
17→18 Elders.Cronus.Projections.Versioning uses Elders.Cronus.Projections part of a loop✕
- Connections
- 14 pairs of types, where a type in Elders.Cronus.Projections.Versioning uses a type in Elders.Cronus.Projections.
- The types involved
Elders.Cronus.Projections.Versioning.CancelProjectionVersionRequest→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.FinalizeProjectionVersionRequest→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.NewProjectionVersionIsNowLive→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.PauseProjectionVersion→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.ProjectionBuilder→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.ProjectionVersionManager→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.ProjectionVersionManagerState→Elders.Cronus.Projections.ProjectionVersionsElders.Cronus.Projections.Versioning.ProjectionVersionRequestCanceled→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.ProjectionVersionRequestPaused→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.ProjectionVersionRequestTimedout→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.ProjectionVersionRequested→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.ProjectionVersionsHandlerState→Elders.Cronus.Projections.ProjectionVersionElders.Cronus.Projections.Versioning.ProjectionVersionsHandlerState→Elders.Cronus.Projections.ProjectionVersionsElders.Cronus.Projections.Versioning.TimeoutProjectionVersionRequest→Elders.Cronus.Projections.ProjectionVersion
- Direction
- Elders.Cronus.Projections.Versioning uses Elders.Cronus.Projections, so a change to Elders.Cronus.Projections can break Elders.Cronus.Projections.Versioning, while a change to Elders.Cronus.Projections.Versioning can't break Elders.Cronus.Projections.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→22 Elders.Cronus.Projections.Versioning uses Elders.Cronus.MessageProcessing part of a loop✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.Projections.Versioning uses a type in Elders.Cronus.MessageProcessing.
- The types involved
Elders.Cronus.Projections.Versioning.EventStoreIndexSubscriber→Elders.Cronus.MessageProcessing.HandleContextElders.Cronus.Projections.Versioning.EventStoreIndexSubscriber→Elders.Cronus.MessageProcessing.SubscriberBase
- Direction
- Elders.Cronus.Projections.Versioning uses Elders.Cronus.MessageProcessing, so a change to Elders.Cronus.MessageProcessing can break Elders.Cronus.Projections.Versioning, while a change to Elders.Cronus.Projections.Versioning can't break Elders.Cronus.MessageProcessing.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→23 Elders.Cronus.Projections.Versioning uses Elders.Cronus.Cluster.Job part of a loop✕
- Connections
- 3 pairs of types, where a type in Elders.Cronus.Projections.Versioning uses a type in Elders.Cronus.Cluster.Job.
- The types involved
Elders.Cronus.Projections.Versioning.ProjectionBuilder→Elders.Cronus.Cluster.Job.ICronusJobElders.Cronus.Projections.Versioning.ProjectionBuilder→Elders.Cronus.Cluster.Job.ICronusJobRunnerElders.Cronus.Projections.Versioning.ProjectionBuilder→Elders.Cronus.Cluster.Job.JobExecutionStatus
- Direction
- Elders.Cronus.Projections.Versioning uses Elders.Cronus.Cluster.Job, so a change to Elders.Cronus.Cluster.Job can break Elders.Cronus.Projections.Versioning, while a change to Elders.Cronus.Projections.Versioning can't break Elders.Cronus.Cluster.Job.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→24 Elders.Cronus.Projections.Versioning uses Elders.Cronus part of a loop✕
- Connections
- 18 pairs of types, where a type in Elders.Cronus.Projections.Versioning uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.Projections.Versioning.CancelProjectionVersionRequest→Elders.Cronus.ISystemCommandElders.Cronus.Projections.Versioning.CreateNewProjectionVersion→Elders.Cronus.ISystemScheduledMessageElders.Cronus.Projections.Versioning.FinalizeProjectionVersionRequest→Elders.Cronus.ISystemCommandElders.Cronus.Projections.Versioning.FixProjectionVersion→Elders.Cronus.ISystemCommandElders.Cronus.Projections.Versioning.NewProjectionVersion→Elders.Cronus.ISystemCommandElders.Cronus.Projections.Versioning.NewProjectionVersionIsNowLive→Elders.Cronus.ISystemEventElders.Cronus.Projections.Versioning.PauseProjectionVersion→Elders.Cronus.ISystemCommandElders.Cronus.Projections.Versioning.ProjectionBuilder→Elders.Cronus.ISystemSagaElders.Cronus.Projections.Versioning.ProjectionVersionManagerAppService→Elders.Cronus.ISystemAppServiceElders.Cronus.Projections.Versioning.ProjectionVersionRequestCanceled→Elders.Cronus.ISystemEventElders.Cronus.Projections.Versioning.ProjectionVersionRequestHeartbeat→Elders.Cronus.ISystemScheduledMessageElders.Cronus.Projections.Versioning.ProjectionVersionRequestPaused→Elders.Cronus.ISystemEventElders.Cronus.Projections.Versioning.ProjectionVersionRequestTimedout→Elders.Cronus.ISystemEventElders.Cronus.Projections.Versioning.ProjectionVersionRequested→Elders.Cronus.ISystemEventElders.Cronus.Projections.Versioning.ProjectionVersionsHandler→Elders.Cronus.INonVersionableProjectionElders.Cronus.Projections.Versioning.ProjectionVersionsHandler→Elders.Cronus.ISystemProjectionElders.Cronus.Projections.Versioning.RegisterProjection→Elders.Cronus.ISystemCommandElders.Cronus.Projections.Versioning.TimeoutProjectionVersionRequest→Elders.Cronus.ISystemCommand
- Direction
- Elders.Cronus.Projections.Versioning uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.Projections.Versioning, while a change to Elders.Cronus.Projections.Versioning can't break Elders.Cronus.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→12 Elders.Cronus.Projections uses Elders.Cronus.Projections.Cassandra✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.Projections uses a type in Elders.Cronus.Projections.Cassandra.
- The types involved
Elders.Cronus.Projections.IProjectionStore→Elders.Cronus.Projections.Cassandra.ProjectionQueryOptionsElders.Cronus.Projections.MissingProjections→Elders.Cronus.Projections.Cassandra.ProjectionQueryOptions
- Direction
- Elders.Cronus.Projections uses Elders.Cronus.Projections.Cassandra, so a change to Elders.Cronus.Projections.Cassandra can break Elders.Cronus.Projections, while a change to Elders.Cronus.Projections can't break Elders.Cronus.Projections.Cassandra.
- Position
- Below the diagonal: Elders.Cronus.Projections uses a module listed above it, which is the healthy direction.
18→16 Elders.Cronus.Projections uses Elders.Cronus.Multitenancy✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Projections uses a type in Elders.Cronus.Multitenancy.
- The types involved
Elders.Cronus.Projections.CronusProjectionBootstrapper→Elders.Cronus.Multitenancy.TenantsOptions
- Direction
- Elders.Cronus.Projections uses Elders.Cronus.Multitenancy, so a change to Elders.Cronus.Multitenancy can break Elders.Cronus.Projections, while a change to Elders.Cronus.Projections can't break Elders.Cronus.Multitenancy.
- Position
- Below the diagonal: Elders.Cronus.Projections uses a module listed above it, which is the healthy direction.
18→17 Elders.Cronus.Projections uses Elders.Cronus.Projections.Versioning✕
- Connections
- 4 pairs of types, where a type in Elders.Cronus.Projections uses a type in Elders.Cronus.Projections.Versioning.
- The types involved
Elders.Cronus.Projections.ProjectionFinderViaReflection→Elders.Cronus.Projections.Versioning.ProjectionHasherElders.Cronus.Projections.ProjectionRepository→Elders.Cronus.Projections.Versioning.ProjectionHasherElders.Cronus.Projections.ProjectionRepository→Elders.Cronus.Projections.Versioning.ProjectionVersionsHandlerElders.Cronus.Projections.ProjectionVersions→Elders.Cronus.Projections.Versioning.IProjectionVersioningPolicy
- Direction
- Elders.Cronus.Projections uses Elders.Cronus.Projections.Versioning, so a change to Elders.Cronus.Projections.Versioning can break Elders.Cronus.Projections, while a change to Elders.Cronus.Projections can't break Elders.Cronus.Projections.Versioning.
- Position
- Below the diagonal: Elders.Cronus.Projections uses a module listed above it, which is the healthy direction.
18→20 Elders.Cronus.Projections uses Elders.Cronus.EventStore part of a loop✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Projections uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.Projections.ProjectionsOperator→Elders.Cronus.EventStore.PagingOptions
- Direction
- Elders.Cronus.Projections uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.Projections, while a change to Elders.Cronus.Projections can't break Elders.Cronus.EventStore.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→22 Elders.Cronus.Projections uses Elders.Cronus.MessageProcessing part of a loop✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.Projections uses a type in Elders.Cronus.MessageProcessing.
- The types involved
Elders.Cronus.Projections.ProjectionRepository→Elders.Cronus.MessageProcessing.ICronusContextAccessorElders.Cronus.Projections.ProjectionRepository→Elders.Cronus.MessageProcessing.IHandlerFactory
- Direction
- Elders.Cronus.Projections uses Elders.Cronus.MessageProcessing, so a change to Elders.Cronus.MessageProcessing can break Elders.Cronus.Projections, while a change to Elders.Cronus.Projections can't break Elders.Cronus.MessageProcessing.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→24 Elders.Cronus.Projections uses Elders.Cronus part of a loop✕
- Connections
- 5 pairs of types, where a type in Elders.Cronus.Projections uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.Projections.CronusProjectionBootstrapper→Elders.Cronus.CronusHostOptionsElders.Cronus.Projections.ProjectionFinderViaReflection→Elders.Cronus.TypeContainerElders.Cronus.Projections.RebuildProjectionFinished→Elders.Cronus.ISystemSignalElders.Cronus.Projections.RebuildProjectionProgress→Elders.Cronus.ISystemSignalElders.Cronus.Projections.RebuildProjectionStarted→Elders.Cronus.ISystemSignal
- Direction
- Elders.Cronus.Projections uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.Projections, while a change to Elders.Cronus.Projections can't break Elders.Cronus.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→17 Elders.Cronus.EventStore.Index uses Elders.Cronus.Projections.Versioning✕
- Connections
- 6 pairs of types, where a type in Elders.Cronus.EventStore.Index uses a type in Elders.Cronus.Projections.Versioning.
- The types involved
Elders.Cronus.EventStore.Index.EventStoreIndexManager→Elders.Cronus.Projections.Versioning.VersionRequestTimeboxElders.Cronus.EventStore.Index.EventStoreIndexManagerState→Elders.Cronus.Projections.Versioning.VersionRequestTimeboxElders.Cronus.EventStore.Index.EventStoreIndexRequested→Elders.Cronus.Projections.Versioning.VersionRequestTimeboxElders.Cronus.EventStore.Index.IRebuildIndex_EventToAggregateRootId_JobFactory→Elders.Cronus.Projections.Versioning.VersionRequestTimeboxElders.Cronus.EventStore.Index.RebuildIndex_EventToAggregateRootId_JobFactory→Elders.Cronus.Projections.Versioning.VersionRequestTimeboxElders.Cronus.EventStore.Index.RebuildIndex_MessageCounter_JobFactory→Elders.Cronus.Projections.Versioning.VersionRequestTimebox
- Direction
- Elders.Cronus.EventStore.Index uses Elders.Cronus.Projections.Versioning, so a change to Elders.Cronus.Projections.Versioning can break Elders.Cronus.EventStore.Index, while a change to Elders.Cronus.EventStore.Index can't break Elders.Cronus.Projections.Versioning.
- Position
- Below the diagonal: Elders.Cronus.EventStore.Index uses a module listed above it, which is the healthy direction.
19→18 Elders.Cronus.EventStore.Index uses Elders.Cronus.Projections✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.EventStore.Index uses a type in Elders.Cronus.Projections.
- The types involved
Elders.Cronus.EventStore.Index.ProjectionIndex→Elders.Cronus.Projections.IProjectionWriter
- Direction
- Elders.Cronus.EventStore.Index uses Elders.Cronus.Projections, so a change to Elders.Cronus.Projections can break Elders.Cronus.EventStore.Index, while a change to Elders.Cronus.EventStore.Index can't break Elders.Cronus.Projections.
- Position
- Below the diagonal: Elders.Cronus.EventStore.Index uses a module listed above it, which is the healthy direction.
19→20 Elders.Cronus.EventStore.Index uses Elders.Cronus.EventStore part of a loop✕
- Connections
- 3 pairs of types, where a type in Elders.Cronus.EventStore.Index uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.EventStore.Index.MessageCounterIndex→Elders.Cronus.EventStore.IMessageCounterElders.Cronus.EventStore.Index.RebuildIndex_EventToAggregateRootId_Job→Elders.Cronus.EventStore.IEventStorePlayerElders.Cronus.EventStore.Index.RebuildIndex_MessageCounter_Job→Elders.Cronus.EventStore.IMessageCounter
- Direction
- Elders.Cronus.EventStore.Index uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.EventStore.Index, while a change to Elders.Cronus.EventStore.Index can't break Elders.Cronus.EventStore.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→22 Elders.Cronus.EventStore.Index uses Elders.Cronus.MessageProcessing part of a loop✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.EventStore.Index uses a type in Elders.Cronus.MessageProcessing.
- The types involved
Elders.Cronus.EventStore.Index.RebuildIndex_MessageCounter_Job→Elders.Cronus.MessageProcessing.ICronusContextAccessorElders.Cronus.EventStore.Index.RebuildIndex_MessageCounter_JobFactory→Elders.Cronus.MessageProcessing.ICronusContextAccessor
- Direction
- Elders.Cronus.EventStore.Index uses Elders.Cronus.MessageProcessing, so a change to Elders.Cronus.MessageProcessing can break Elders.Cronus.EventStore.Index, while a change to Elders.Cronus.EventStore.Index can't break Elders.Cronus.MessageProcessing.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→23 Elders.Cronus.EventStore.Index uses Elders.Cronus.Cluster.Job part of a loop✕
- Connections
- 11 pairs of types, where a type in Elders.Cronus.EventStore.Index uses a type in Elders.Cronus.Cluster.Job.
- The types involved
Elders.Cronus.EventStore.Index.IRebuildIndex_EventToAggregateRootId_JobFactory→Elders.Cronus.Cluster.Job.ICronusJobElders.Cronus.EventStore.Index.RebuildEventCounterIndex_JobData→Elders.Cronus.Cluster.Job.IJobDataElders.Cronus.EventStore.Index.RebuildIndex_EventToAggregateRootId_Job→Elders.Cronus.Cluster.Job.CronusJobElders.Cronus.EventStore.Index.RebuildIndex_EventToAggregateRootId_Job→Elders.Cronus.Cluster.Job.IClusterOperationsElders.Cronus.EventStore.Index.RebuildIndex_EventToAggregateRootId_Job→Elders.Cronus.Cluster.Job.JobExecutionStatusElders.Cronus.EventStore.Index.RebuildIndex_EventToAggregateRootId_JobFactory→Elders.Cronus.Cluster.Job.ICronusJobElders.Cronus.EventStore.Index.RebuildIndex_EventToAggregateRootId_JobFactory→Elders.Cronus.Cluster.Job.IJobNameBuilderElders.Cronus.EventStore.Index.RebuildIndex_JobData→Elders.Cronus.Cluster.Job.IJobDataElders.Cronus.EventStore.Index.RebuildIndex_MessageCounter_Job→Elders.Cronus.Cluster.Job.CronusJobElders.Cronus.EventStore.Index.RebuildIndex_MessageCounter_Job→Elders.Cronus.Cluster.Job.IClusterOperationsElders.Cronus.EventStore.Index.RebuildIndex_MessageCounter_Job→Elders.Cronus.Cluster.Job.JobExecutionStatus
- Direction
- Elders.Cronus.EventStore.Index uses Elders.Cronus.Cluster.Job, so a change to Elders.Cronus.Cluster.Job can break Elders.Cronus.EventStore.Index, while a change to Elders.Cronus.EventStore.Index can't break Elders.Cronus.Cluster.Job.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→24 Elders.Cronus.EventStore.Index uses Elders.Cronus part of a loop✕
- Connections
- 16 pairs of types, where a type in Elders.Cronus.EventStore.Index uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.EventStore.Index.EventLookupInByteArray→Elders.Cronus.TypeContainerElders.Cronus.EventStore.Index.EventStoreIndexIsNowPresent→Elders.Cronus.ISystemEventElders.Cronus.EventStore.Index.EventStoreIndexManagerAppService→Elders.Cronus.ISystemAppServiceElders.Cronus.EventStore.Index.EventStoreIndexRequested→Elders.Cronus.ISystemEventElders.Cronus.EventStore.Index.EventToAggregateRootId→Elders.Cronus.BoundedContextElders.Cronus.EventStore.Index.EventToAggregateRootId→Elders.Cronus.CronusMessageElders.Cronus.EventStore.Index.FinalizeEventStoreIndexRequest→Elders.Cronus.ISystemCommandElders.Cronus.EventStore.Index.ICronusEventStoreIndex→Elders.Cronus.ISystemHandlerElders.Cronus.EventStore.Index.IEventStoreIndex→Elders.Cronus.CronusMessageElders.Cronus.EventStore.Index.MessageCounterIndex→Elders.Cronus.CronusMessageElders.Cronus.EventStore.Index.ProjectionIndex→Elders.Cronus.CronusMessageElders.Cronus.EventStore.Index.ProjectionIndex→Elders.Cronus.TypeContainerElders.Cronus.EventStore.Index.RebuildIndexCommand→Elders.Cronus.ISystemCommandElders.Cronus.EventStore.Index.RebuildIndex_MessageCounter_Job→Elders.Cronus.TypeContainerElders.Cronus.EventStore.Index.RebuildIndex_MessageCounter_JobFactory→Elders.Cronus.BoundedContextElders.Cronus.EventStore.Index.RegisterIndex→Elders.Cronus.ISystemCommand
- Direction
- Elders.Cronus.EventStore.Index uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.EventStore.Index, while a change to Elders.Cronus.EventStore.Index can't break Elders.Cronus.
- 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→7 Elders.Cronus.EventStore uses Elders.Cronus.AtomicAction✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.EventStore uses a type in Elders.Cronus.AtomicAction.
- The types involved
Elders.Cronus.EventStore.AggregateRepository→Elders.Cronus.AtomicAction.IAggregateRootAtomicAction
- Direction
- Elders.Cronus.EventStore uses Elders.Cronus.AtomicAction, so a change to Elders.Cronus.AtomicAction can break Elders.Cronus.EventStore, while a change to Elders.Cronus.EventStore can't break Elders.Cronus.AtomicAction.
- Position
- Below the diagonal: Elders.Cronus.EventStore uses a module listed above it, which is the healthy direction.
20→10 Elders.Cronus.EventStore uses Elders.Cronus.IntegrityValidation✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.EventStore uses a type in Elders.Cronus.IntegrityValidation.
- The types involved
Elders.Cronus.EventStore.AggregateRepository→Elders.Cronus.IntegrityValidation.IIntegrityPolicy
- Direction
- Elders.Cronus.EventStore uses Elders.Cronus.IntegrityValidation, so a change to Elders.Cronus.IntegrityValidation can break Elders.Cronus.EventStore, while a change to Elders.Cronus.EventStore can't break Elders.Cronus.IntegrityValidation.
- Position
- Below the diagonal: Elders.Cronus.EventStore uses a module listed above it, which is the healthy direction.
20→19 Elders.Cronus.EventStore uses Elders.Cronus.EventStore.Index✕
- Connections
- 5 pairs of types, where a type in Elders.Cronus.EventStore uses a type in Elders.Cronus.EventStore.Index.
- The types involved
Elders.Cronus.EventStore.CronusEventStore→Elders.Cronus.EventStore.Index.IndexRecordElders.Cronus.EventStore.IEventStore→Elders.Cronus.EventStore.Index.IndexRecordElders.Cronus.EventStore.MissingPersistence→Elders.Cronus.EventStore.Index.IIndexStoreElders.Cronus.EventStore.MissingPersistence→Elders.Cronus.EventStore.Index.IndexRecordElders.Cronus.EventStore.MissingPersistence→Elders.Cronus.EventStore.Index.LoadIndexRecordsResult
- Direction
- Elders.Cronus.EventStore uses Elders.Cronus.EventStore.Index, so a change to Elders.Cronus.EventStore.Index can break Elders.Cronus.EventStore, while a change to Elders.Cronus.EventStore can't break Elders.Cronus.EventStore.Index.
- Position
- Below the diagonal: Elders.Cronus.EventStore uses a module listed above it, which is the healthy direction.
21→10 Elders.Cronus.EventStore.Integrity uses Elders.Cronus.IntegrityValidation✕
- Connections
- 12 pairs of types, where a type in Elders.Cronus.EventStore.Integrity uses a type in Elders.Cronus.IntegrityValidation.
- The types involved
Elders.Cronus.EventStore.Integrity.DuplicateRevisionsValidator→Elders.Cronus.IntegrityValidation.IValidatorElders.Cronus.EventStore.Integrity.DuplicateRevisionsValidator→Elders.Cronus.IntegrityValidation.IValidatorResultElders.Cronus.EventStore.Integrity.EventStreamIntegrityPolicy→Elders.Cronus.IntegrityValidation.IIntegrityPolicyElders.Cronus.EventStore.Integrity.EventStreamIntegrityPolicy→Elders.Cronus.IntegrityValidation.IntegrityResultElders.Cronus.EventStore.Integrity.EventStreamIntegrityPolicy→Elders.Cronus.IntegrityValidation.IntegrityRuleElders.Cronus.EventStore.Integrity.MissingRevisionsValidator→Elders.Cronus.IntegrityValidation.IValidatorElders.Cronus.EventStore.Integrity.MissingRevisionsValidator→Elders.Cronus.IntegrityValidation.IValidatorResultElders.Cronus.EventStore.Integrity.OrderedRevisionsValidator→Elders.Cronus.IntegrityValidation.IValidatorElders.Cronus.EventStore.Integrity.OrderedRevisionsValidator→Elders.Cronus.IntegrityValidation.IValidatorResultElders.Cronus.EventStore.Integrity.UnorderedRevisionsResolver→Elders.Cronus.IntegrityValidation.IResolverElders.Cronus.EventStore.Integrity.UnorderedRevisionsResolver→Elders.Cronus.IntegrityValidation.IValidatorResultElders.Cronus.EventStore.Integrity.UnorderedRevisionsResolver→Elders.Cronus.IntegrityValidation.IntegrityResult
- Direction
- Elders.Cronus.EventStore.Integrity uses Elders.Cronus.IntegrityValidation, so a change to Elders.Cronus.IntegrityValidation can break Elders.Cronus.EventStore.Integrity, while a change to Elders.Cronus.EventStore.Integrity can't break Elders.Cronus.IntegrityValidation.
- Position
- Below the diagonal: Elders.Cronus.EventStore.Integrity uses a module listed above it, which is the healthy direction.
21→20 Elders.Cronus.EventStore.Integrity uses Elders.Cronus.EventStore✕
- Connections
- 6 pairs of types, where a type in Elders.Cronus.EventStore.Integrity uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.EventStore.Integrity.DuplicateRevisionsValidator→Elders.Cronus.EventStore.AggregateCommitElders.Cronus.EventStore.Integrity.DuplicateRevisionsValidator→Elders.Cronus.EventStore.EventStreamElders.Cronus.EventStore.Integrity.EventStreamIntegrityPolicy→Elders.Cronus.EventStore.EventStreamElders.Cronus.EventStore.Integrity.MissingRevisionsValidator→Elders.Cronus.EventStore.EventStreamElders.Cronus.EventStore.Integrity.OrderedRevisionsValidator→Elders.Cronus.EventStore.EventStreamElders.Cronus.EventStore.Integrity.UnorderedRevisionsResolver→Elders.Cronus.EventStore.EventStream
- Direction
- Elders.Cronus.EventStore.Integrity uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.EventStore.Integrity, while a change to Elders.Cronus.EventStore.Integrity can't break Elders.Cronus.EventStore.
- Position
- Below the diagonal: Elders.Cronus.EventStore.Integrity uses a module listed above it, which is the healthy direction.
22→5 Elders.Cronus.MessageProcessing uses Elders.Cronus.Workflow✕
- Connections
- 21 pairs of types, where a type in Elders.Cronus.MessageProcessing uses a type in Elders.Cronus.Workflow.
- The types involved
Elders.Cronus.MessageProcessing.ApplicationServiceSubscriberWorkflow→Elders.Cronus.Workflow.IWorkflowElders.Cronus.MessageProcessing.CreateScopedHandlerWorkflow→Elders.Cronus.Workflow.ExecutionElders.Cronus.MessageProcessing.CreateScopedHandlerWorkflow→Elders.Cronus.Workflow.WorkflowElders.Cronus.MessageProcessing.DefaultSubscriberWorkflow→Elders.Cronus.Workflow.IWorkflowElders.Cronus.MessageProcessing.DynamicMessageHandle→Elders.Cronus.Workflow.ExecutionElders.Cronus.MessageProcessing.DynamicMessageHandle→Elders.Cronus.Workflow.WorkflowElders.Cronus.MessageProcessing.DynamicMessageIndex→Elders.Cronus.Workflow.ExecutionElders.Cronus.MessageProcessing.DynamicMessageIndex→Elders.Cronus.Workflow.WorkflowElders.Cronus.MessageProcessing.EventStoreIndexSubscriberFactory→Elders.Cronus.Workflow.WorkflowElders.Cronus.MessageProcessing.EventStoreIndexSubscriberWorkflow→Elders.Cronus.Workflow.IWorkflowElders.Cronus.MessageProcessing.HandlerSubscriber→Elders.Cronus.Workflow.WorkflowElders.Cronus.MessageProcessing.HandlerSubscriberFactory→Elders.Cronus.Workflow.WorkflowElders.Cronus.MessageProcessing.ISubscriberWorkflowFactory→Elders.Cronus.Workflow.IWorkflowElders.Cronus.MessageProcessing.LogExceptionOnHandleError→Elders.Cronus.Workflow.ExecutionElders.Cronus.MessageProcessing.LogExceptionOnHandleError→Elders.Cronus.Workflow.WorkflowElders.Cronus.MessageProcessing.MessageHandleWorkflow→Elders.Cronus.Workflow.ExecutionElders.Cronus.MessageProcessing.MessageHandleWorkflow→Elders.Cronus.Workflow.WorkflowElders.Cronus.MessageProcessing.ScopedMessageWorkflow→Elders.Cronus.Workflow.ExecutionElders.Cronus.MessageProcessing.ScopedMessageWorkflow→Elders.Cronus.Workflow.WorkflowElders.Cronus.MessageProcessing.SubscriberBase→Elders.Cronus.Workflow.WorkflowElders.Cronus.MessageProcessing.TriggersSubscriberWorkflow→Elders.Cronus.Workflow.IWorkflow
- Direction
- Elders.Cronus.MessageProcessing uses Elders.Cronus.Workflow, so a change to Elders.Cronus.Workflow can break Elders.Cronus.MessageProcessing, while a change to Elders.Cronus.MessageProcessing can't break Elders.Cronus.Workflow.
- Position
- Below the diagonal: Elders.Cronus.MessageProcessing uses a module listed above it, which is the healthy direction.
22→16 Elders.Cronus.MessageProcessing uses Elders.Cronus.Multitenancy✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.MessageProcessing uses a type in Elders.Cronus.Multitenancy.
- The types involved
Elders.Cronus.MessageProcessing.DefaultCronusContextFactory→Elders.Cronus.Multitenancy.ITenantResolverElders.Cronus.MessageProcessing.DefaultCronusContextFactory→Elders.Cronus.Multitenancy.TenantsOptions
- Direction
- Elders.Cronus.MessageProcessing uses Elders.Cronus.Multitenancy, so a change to Elders.Cronus.Multitenancy can break Elders.Cronus.MessageProcessing, while a change to Elders.Cronus.MessageProcessing can't break Elders.Cronus.Multitenancy.
- Position
- Below the diagonal: Elders.Cronus.MessageProcessing uses a module listed above it, which is the healthy direction.
22→20 Elders.Cronus.MessageProcessing uses Elders.Cronus.EventStore✕
- Connections
- 4 pairs of types, where a type in Elders.Cronus.MessageProcessing uses a type in Elders.Cronus.EventStore.
- The types involved
Elders.Cronus.MessageProcessing.AggregateCommitPublisher→Elders.Cronus.EventStore.AggregateCommitElders.Cronus.MessageProcessing.AggregateCommitPublisher→Elders.Cronus.EventStore.IAggregateCommitInterceptorElders.Cronus.MessageProcessing.AggregateRepositoryAndEventPublisher→Elders.Cronus.EventStore.AggregateCommitElders.Cronus.MessageProcessing.AggregateRepositoryAndEventPublisher→Elders.Cronus.EventStore.AggregateRepository
- Direction
- Elders.Cronus.MessageProcessing uses Elders.Cronus.EventStore, so a change to Elders.Cronus.EventStore can break Elders.Cronus.MessageProcessing, while a change to Elders.Cronus.MessageProcessing can't break Elders.Cronus.EventStore.
- Position
- Below the diagonal: Elders.Cronus.MessageProcessing uses a module listed above it, which is the healthy direction.
22→24 Elders.Cronus.MessageProcessing uses Elders.Cronus part of a loop✕
- Connections
- 11 pairs of types, where a type in Elders.Cronus.MessageProcessing uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.MessageProcessing.ErrorContext→Elders.Cronus.CronusMessageElders.Cronus.MessageProcessing.EventStoreIndexSubscriberFactory→Elders.Cronus.BoundedContextElders.Cronus.MessageProcessing.EventStoreIndexSubscriberFactory→Elders.Cronus.TypeContainerElders.Cronus.MessageProcessing.HandleContext→Elders.Cronus.CronusMessageElders.Cronus.MessageProcessing.HandlerContext→Elders.Cronus.CronusMessageElders.Cronus.MessageProcessing.ISubscriber→Elders.Cronus.CronusMessageElders.Cronus.MessageProcessing.ISubscriberCollection→Elders.Cronus.CronusMessageElders.Cronus.MessageProcessing.ProjectionSubscriberFinder→Elders.Cronus.TypeContainerElders.Cronus.MessageProcessing.SubscriberBase→Elders.Cronus.CronusMessageElders.Cronus.MessageProcessing.SubscriberCollection→Elders.Cronus.CronusMessageElders.Cronus.MessageProcessing.SubscriberFinder→Elders.Cronus.TypeContainer
- Direction
- Elders.Cronus.MessageProcessing uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.MessageProcessing, while a change to Elders.Cronus.MessageProcessing can't break Elders.Cronus.
- 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.
23→22 Elders.Cronus.Cluster.Job uses Elders.Cronus.MessageProcessing✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Cluster.Job uses a type in Elders.Cronus.MessageProcessing.
- The types involved
Elders.Cronus.Cluster.Job.DefaultJobNameBuilder→Elders.Cronus.MessageProcessing.ICronusContextAccessor
- Direction
- Elders.Cronus.Cluster.Job uses Elders.Cronus.MessageProcessing, so a change to Elders.Cronus.MessageProcessing can break Elders.Cronus.Cluster.Job, while a change to Elders.Cronus.Cluster.Job can't break Elders.Cronus.MessageProcessing.
- Position
- Below the diagonal: Elders.Cronus.Cluster.Job uses a module listed above it, which is the healthy direction.
23→24 Elders.Cronus.Cluster.Job uses Elders.Cronus part of a loop✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Cluster.Job uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.Cluster.Job.DefaultJobNameBuilder→Elders.Cronus.BoundedContext
- Direction
- Elders.Cronus.Cluster.Job uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.Cluster.Job, while a change to Elders.Cronus.Cluster.Job can't break Elders.Cronus.
- 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.
24→2 Elders.Cronus uses Elders.Cronus.Hosting✕
- Connections
- 1 pair of types, where a type in Elders.Cronus uses a type in Elders.Cronus.Hosting.
- The types involved
Elders.Cronus.CronusHost→Elders.Cronus.Hosting.IRpcHost
- Direction
- Elders.Cronus uses Elders.Cronus.Hosting, so a change to Elders.Cronus.Hosting can break Elders.Cronus, while a change to Elders.Cronus can't break Elders.Cronus.Hosting.
- Position
- Below the diagonal: Elders.Cronus uses a module listed above it, which is the healthy direction.
24→11 Elders.Cronus uses Elders.Cronus.Migrations✕
- Connections
- 1 pair of types, where a type in Elders.Cronus uses a type in Elders.Cronus.Migrations.
- The types involved
Elders.Cronus.CronusHost→Elders.Cronus.Migrations.IMigrationHandler
- Direction
- Elders.Cronus uses Elders.Cronus.Migrations, so a change to Elders.Cronus.Migrations can break Elders.Cronus, while a change to Elders.Cronus can't break Elders.Cronus.Migrations.
- Position
- Below the diagonal: Elders.Cronus uses a module listed above it, which is the healthy direction.
24→13 Elders.Cronus uses Elders.Cronus.Discoveries✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus uses a type in Elders.Cronus.Discoveries.
- The types involved
Elders.Cronus.CronusServiceCollectionExtensions→Elders.Cronus.Discoveries.CronusServicesProviderElders.Cronus.SubscriberCollectionServiceCollectionExtensions→Elders.Cronus.Discoveries.CronusServicesProvider
- Direction
- Elders.Cronus uses Elders.Cronus.Discoveries, so a change to Elders.Cronus.Discoveries can break Elders.Cronus, while a change to Elders.Cronus can't break Elders.Cronus.Discoveries.
- Position
- Below the diagonal: Elders.Cronus uses a module listed above it, which is the healthy direction.
24→16 Elders.Cronus uses Elders.Cronus.Multitenancy✕
- Connections
- 3 pairs of types, where a type in Elders.Cronus uses a type in Elders.Cronus.Multitenancy.
- The types involved
Elders.Cronus.CronusBooter→Elders.Cronus.Multitenancy.TenantsOptionsElders.Cronus.CronusHeadersPublishHandler→Elders.Cronus.Multitenancy.ITenantResolverElders.Cronus.EventStoreIndicesStartup→Elders.Cronus.Multitenancy.TenantsOptions
- Direction
- Elders.Cronus uses Elders.Cronus.Multitenancy, so a change to Elders.Cronus.Multitenancy can break Elders.Cronus, while a change to Elders.Cronus can't break Elders.Cronus.Multitenancy.
- Position
- Below the diagonal: Elders.Cronus uses a module listed above it, which is the healthy direction.
24→18 Elders.Cronus uses Elders.Cronus.Projections✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus uses a type in Elders.Cronus.Projections.
- The types involved
Elders.Cronus.CronusMessageExtensions→Elders.Cronus.Projections.EventOriginElders.Cronus.ProjectionsStartup→Elders.Cronus.Projections.CronusProjectionBootstrapper
- Direction
- Elders.Cronus uses Elders.Cronus.Projections, so a change to Elders.Cronus.Projections can break Elders.Cronus, while a change to Elders.Cronus can't break Elders.Cronus.Projections.
- Position
- Below the diagonal: Elders.Cronus uses a module listed above it, which is the healthy direction.
24→19 Elders.Cronus uses Elders.Cronus.EventStore.Index✕
- Connections
- 4 pairs of types, where a type in Elders.Cronus uses a type in Elders.Cronus.EventStore.Index.
- The types involved
Elders.Cronus.CronusHost→Elders.Cronus.EventStore.Index.ICronusEventStoreIndexElders.Cronus.CronusHost→Elders.Cronus.EventStore.Index.IEventStoreIndexElders.Cronus.CronusMessageExtensions→Elders.Cronus.EventStore.Index.IndexRecordElders.Cronus.EventStoreIndicesStartup→Elders.Cronus.EventStore.Index.IEventStoreIndex
- Direction
- Elders.Cronus uses Elders.Cronus.EventStore.Index, so a change to Elders.Cronus.EventStore.Index can break Elders.Cronus, while a change to Elders.Cronus can't break Elders.Cronus.EventStore.Index.
- Position
- Below the diagonal: Elders.Cronus uses a module listed above it, which is the healthy direction.
24→22 Elders.Cronus uses Elders.Cronus.MessageProcessing✕
- Connections
- 1 pair of types, where a type in Elders.Cronus uses a type in Elders.Cronus.MessageProcessing.
- The types involved
Elders.Cronus.SingletonPerTenant→Elders.Cronus.MessageProcessing.ICronusContextAccessor
- Direction
- Elders.Cronus uses Elders.Cronus.MessageProcessing, so a change to Elders.Cronus.MessageProcessing can break Elders.Cronus, while a change to Elders.Cronus can't break Elders.Cronus.MessageProcessing.
- Position
- Below the diagonal: Elders.Cronus uses a module listed above it, which is the healthy direction.
24→23 Elders.Cronus uses Elders.Cronus.Cluster.Job✕
- Connections
- 1 pair of types, where a type in Elders.Cronus uses a type in Elders.Cronus.Cluster.Job.
- The types involved
Elders.Cronus.CronusHost→Elders.Cronus.Cluster.Job.JobManager
- Direction
- Elders.Cronus uses Elders.Cronus.Cluster.Job, so a change to Elders.Cronus.Cluster.Job can break Elders.Cronus, while a change to Elders.Cronus can't break Elders.Cronus.Cluster.Job.
- Position
- Below the diagonal: Elders.Cronus uses a module listed above it, which is the healthy direction.
25→13 Elders.Cronus.Cluster.Job.InMemory uses Elders.Cronus.Discoveries✕
- Connections
- 4 pairs of types, where a type in Elders.Cronus.Cluster.Job.InMemory uses a type in Elders.Cronus.Discoveries.
- The types involved
Elders.Cronus.Cluster.Job.InMemory.JobDiscovery→Elders.Cronus.Discoveries.DiscoveredModelElders.Cronus.Cluster.Job.InMemory.JobDiscovery→Elders.Cronus.Discoveries.DiscoveryBaseElders.Cronus.Cluster.Job.InMemory.JobDiscovery→Elders.Cronus.Discoveries.DiscoveryContextElders.Cronus.Cluster.Job.InMemory.JobDiscovery→Elders.Cronus.Discoveries.DiscoveryResult
- Direction
- Elders.Cronus.Cluster.Job.InMemory uses Elders.Cronus.Discoveries, so a change to Elders.Cronus.Discoveries can break Elders.Cronus.Cluster.Job.InMemory, while a change to Elders.Cronus.Cluster.Job.InMemory can't break Elders.Cronus.Discoveries.
- Position
- Below the diagonal: Elders.Cronus.Cluster.Job.InMemory uses a module listed above it, which is the healthy direction.
25→23 Elders.Cronus.Cluster.Job.InMemory uses Elders.Cronus.Cluster.Job✕
- Connections
- 6 pairs of types, where a type in Elders.Cronus.Cluster.Job.InMemory uses a type in Elders.Cronus.Cluster.Job.
- The types involved
Elders.Cronus.Cluster.Job.InMemory.InMemoryCronusJobRunner→Elders.Cronus.Cluster.Job.ICronusJobElders.Cronus.Cluster.Job.InMemory.InMemoryCronusJobRunner→Elders.Cronus.Cluster.Job.ICronusJobRunnerElders.Cronus.Cluster.Job.InMemory.InMemoryCronusJobRunner→Elders.Cronus.Cluster.Job.JobExecutionStatusElders.Cronus.Cluster.Job.InMemory.InMemoryCronusJobRunner→Elders.Cronus.Cluster.Job.JobManagerElders.Cronus.Cluster.Job.InMemory.JobDiscovery→Elders.Cronus.Cluster.Job.ICronusJobElders.Cronus.Cluster.Job.InMemory.NoClusterOperations→Elders.Cronus.Cluster.Job.IClusterOperations
- Direction
- Elders.Cronus.Cluster.Job.InMemory uses Elders.Cronus.Cluster.Job, so a change to Elders.Cronus.Cluster.Job can break Elders.Cronus.Cluster.Job.InMemory, while a change to Elders.Cronus.Cluster.Job.InMemory can't break Elders.Cronus.Cluster.Job.
- Position
- Below the diagonal: Elders.Cronus.Cluster.Job.InMemory uses a module listed above it, which is the healthy direction.
26→24 Elders.Cronus.DangerZone uses Elders.Cronus✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.DangerZone uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.DangerZone.CronusDangerZoneOptionsProvider→Elders.Cronus.CronusOptionsProviderBase
- Direction
- Elders.Cronus.DangerZone uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.DangerZone, while a change to Elders.Cronus.DangerZone can't break Elders.Cronus.
- Position
- Below the diagonal: Elders.Cronus.DangerZone uses a module listed above it, which is the healthy direction.
27→24 Elders.Cronus.EventStore.AutoUpdater.Commands uses Elders.Cronus✕
- Connections
- 4 pairs of types, where a type in Elders.Cronus.EventStore.AutoUpdater.Commands uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.EventStore.AutoUpdater.Commands.BulkRequestAutoUpdate→Elders.Cronus.ISystemCommandElders.Cronus.EventStore.AutoUpdater.Commands.FailAutoUpdate→Elders.Cronus.ISystemCommandElders.Cronus.EventStore.AutoUpdater.Commands.FinishAutoUpdate→Elders.Cronus.ISystemCommandElders.Cronus.EventStore.AutoUpdater.Commands.RequestAutoUpdate→Elders.Cronus.ISystemCommand
- Direction
- Elders.Cronus.EventStore.AutoUpdater.Commands uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.EventStore.AutoUpdater.Commands, while a change to Elders.Cronus.EventStore.AutoUpdater.Commands can't break Elders.Cronus.
- Position
- Below the diagonal: Elders.Cronus.EventStore.AutoUpdater.Commands uses a module listed above it, which is the healthy direction.
27→32 Elders.Cronus.EventStore.AutoUpdater.Commands uses Elders.Cronus.EventStore.AutoUpdater part of a loop✕
- Connections
- 4 pairs of types, where a type in Elders.Cronus.EventStore.AutoUpdater.Commands uses a type in Elders.Cronus.EventStore.AutoUpdater.
- The types involved
Elders.Cronus.EventStore.AutoUpdater.Commands.BulkRequestAutoUpdate→Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterIdElders.Cronus.EventStore.AutoUpdater.Commands.FailAutoUpdate→Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterIdElders.Cronus.EventStore.AutoUpdater.Commands.FinishAutoUpdate→Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterIdElders.Cronus.EventStore.AutoUpdater.Commands.RequestAutoUpdate→Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterId
- Direction
- Elders.Cronus.EventStore.AutoUpdater.Commands uses Elders.Cronus.EventStore.AutoUpdater, so a change to Elders.Cronus.EventStore.AutoUpdater can break Elders.Cronus.EventStore.AutoUpdater.Commands, while a change to Elders.Cronus.EventStore.AutoUpdater.Commands can't break Elders.Cronus.EventStore.AutoUpdater.
- 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.
28→24 Elders.Cronus.EventStore.AutoUpdater.Events uses Elders.Cronus✕
- Connections
- 5 pairs of types, where a type in Elders.Cronus.EventStore.AutoUpdater.Events uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateFailed→Elders.Cronus.ISystemEventElders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateFinished→Elders.Cronus.ISystemEventElders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateRequested→Elders.Cronus.ISystemEventElders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateTriggered→Elders.Cronus.ISystemEventElders.Cronus.EventStore.AutoUpdater.Events.AutoUpdaterInitialized→Elders.Cronus.ISystemEvent
- Direction
- Elders.Cronus.EventStore.AutoUpdater.Events uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.EventStore.AutoUpdater.Events, while a change to Elders.Cronus.EventStore.AutoUpdater.Events can't break Elders.Cronus.
- Position
- Below the diagonal: Elders.Cronus.EventStore.AutoUpdater.Events uses a module listed above it, which is the healthy direction.
28→32 Elders.Cronus.EventStore.AutoUpdater.Events uses Elders.Cronus.EventStore.AutoUpdater part of a loop✕
- Connections
- 5 pairs of types, where a type in Elders.Cronus.EventStore.AutoUpdater.Events uses a type in Elders.Cronus.EventStore.AutoUpdater.
- The types involved
Elders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateFailed→Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterIdElders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateFinished→Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterIdElders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateRequested→Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterIdElders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateTriggered→Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterIdElders.Cronus.EventStore.AutoUpdater.Events.AutoUpdaterInitialized→Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterId
- Direction
- Elders.Cronus.EventStore.AutoUpdater.Events uses Elders.Cronus.EventStore.AutoUpdater, so a change to Elders.Cronus.EventStore.AutoUpdater can break Elders.Cronus.EventStore.AutoUpdater.Events, while a change to Elders.Cronus.EventStore.AutoUpdater.Events can't break Elders.Cronus.EventStore.AutoUpdater.
- 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.
29→19 Elders.Cronus.EventStore.Index.Handlers uses Elders.Cronus.EventStore.Index✕
- Connections
- 9 pairs of types, where a type in Elders.Cronus.EventStore.Index.Handlers uses a type in Elders.Cronus.EventStore.Index.
- The types involved
Elders.Cronus.EventStore.Index.Handlers.EventStoreIndexBuilder→Elders.Cronus.EventStore.Index.EventStoreIndexRequestedElders.Cronus.EventStore.Index.Handlers.EventStoreIndexBuilder→Elders.Cronus.EventStore.Index.IRebuildIndex_EventToAggregateRootId_JobFactoryElders.Cronus.EventStore.Index.Handlers.EventStoreIndexBuilder→Elders.Cronus.EventStore.Index.RebuildIndex_MessageCounter_JobFactoryElders.Cronus.EventStore.Index.Handlers.EventStoreIndexRebuildTimedout→Elders.Cronus.EventStore.Index.EventStoreIndexRequestedElders.Cronus.EventStore.Index.Handlers.EventStoreIndexStatus→Elders.Cronus.EventStore.Index.EventStoreIndexIsNowPresentElders.Cronus.EventStore.Index.Handlers.EventStoreIndexStatus→Elders.Cronus.EventStore.Index.EventStoreIndexRequestedElders.Cronus.EventStore.Index.Handlers.EventStoreIndexStatusState→Elders.Cronus.EventStore.Index.EventStoreIndexManagerIdElders.Cronus.EventStore.Index.Handlers.EventStoreIndexStatusState→Elders.Cronus.EventStore.Index.IndexStatusElders.Cronus.EventStore.Index.Handlers.RebuildIndexInternal→Elders.Cronus.EventStore.Index.EventStoreIndexRequested
- Direction
- Elders.Cronus.EventStore.Index.Handlers uses Elders.Cronus.EventStore.Index, so a change to Elders.Cronus.EventStore.Index can break Elders.Cronus.EventStore.Index.Handlers, while a change to Elders.Cronus.EventStore.Index.Handlers can't break Elders.Cronus.EventStore.Index.
- Position
- Below the diagonal: Elders.Cronus.EventStore.Index.Handlers uses a module listed above it, which is the healthy direction.
29→23 Elders.Cronus.EventStore.Index.Handlers uses Elders.Cronus.Cluster.Job✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.EventStore.Index.Handlers uses a type in Elders.Cronus.Cluster.Job.
- The types involved
Elders.Cronus.EventStore.Index.Handlers.EventStoreIndexBuilder→Elders.Cronus.Cluster.Job.ICronusJobRunner
- Direction
- Elders.Cronus.EventStore.Index.Handlers uses Elders.Cronus.Cluster.Job, so a change to Elders.Cronus.Cluster.Job can break Elders.Cronus.EventStore.Index.Handlers, while a change to Elders.Cronus.EventStore.Index.Handlers can't break Elders.Cronus.Cluster.Job.
- Position
- Below the diagonal: Elders.Cronus.EventStore.Index.Handlers uses a module listed above it, which is the healthy direction.
29→24 Elders.Cronus.EventStore.Index.Handlers uses Elders.Cronus✕
- Connections
- 5 pairs of types, where a type in Elders.Cronus.EventStore.Index.Handlers uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.EventStore.Index.Handlers.EventStoreIndexBuilder→Elders.Cronus.ISystemSagaElders.Cronus.EventStore.Index.Handlers.EventStoreIndexRebuildTimedout→Elders.Cronus.ISystemScheduledMessageElders.Cronus.EventStore.Index.Handlers.EventStoreIndexStatus→Elders.Cronus.ISystemEventStoreIndexHandlerElders.Cronus.EventStore.Index.Handlers.EventStoreIndexStatus→Elders.Cronus.ISystemProjectionElders.Cronus.EventStore.Index.Handlers.RebuildIndexInternal→Elders.Cronus.ISystemScheduledMessage
- Direction
- Elders.Cronus.EventStore.Index.Handlers uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.EventStore.Index.Handlers, while a change to Elders.Cronus.EventStore.Index.Handlers can't break Elders.Cronus.
- Position
- Below the diagonal: Elders.Cronus.EventStore.Index.Handlers uses a module listed above it, which is the healthy direction.
30→16 Elders.Cronus.Hosting.Heartbeat uses Elders.Cronus.Multitenancy✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.Hosting.Heartbeat uses a type in Elders.Cronus.Multitenancy.
- The types involved
Elders.Cronus.Hosting.Heartbeat.CronusHeartbeat→Elders.Cronus.Multitenancy.TenantsOptions
- Direction
- Elders.Cronus.Hosting.Heartbeat uses Elders.Cronus.Multitenancy, so a change to Elders.Cronus.Multitenancy can break Elders.Cronus.Hosting.Heartbeat, while a change to Elders.Cronus.Hosting.Heartbeat can't break Elders.Cronus.Multitenancy.
- Position
- Below the diagonal: Elders.Cronus.Hosting.Heartbeat uses a module listed above it, which is the healthy direction.
30→24 Elders.Cronus.Hosting.Heartbeat uses Elders.Cronus✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.Hosting.Heartbeat uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.Hosting.Heartbeat.CronusHeartbeat→Elders.Cronus.BoundedContextElders.Cronus.Hosting.Heartbeat.HeartbeaOptionsProvider→Elders.Cronus.CronusOptionsProviderBase
- Direction
- Elders.Cronus.Hosting.Heartbeat uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.Hosting.Heartbeat, while a change to Elders.Cronus.Hosting.Heartbeat can't break Elders.Cronus.
- Position
- Below the diagonal: Elders.Cronus.Hosting.Heartbeat uses a module listed above it, which is the healthy direction.
31→24 Elders.Cronus.AutoUpdates uses Elders.Cronus✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.AutoUpdates uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.AutoUpdates.AutoUpdateSaga→Elders.Cronus.ISystemSaga
- Direction
- Elders.Cronus.AutoUpdates uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.AutoUpdates, while a change to Elders.Cronus.AutoUpdates can't break Elders.Cronus.
- Position
- Below the diagonal: Elders.Cronus.AutoUpdates uses a module listed above it, which is the healthy direction.
31→28 Elders.Cronus.AutoUpdates uses Elders.Cronus.EventStore.AutoUpdater.Events✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.AutoUpdates uses a type in Elders.Cronus.EventStore.AutoUpdater.Events.
- The types involved
Elders.Cronus.AutoUpdates.AutoUpdateSaga→Elders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateTriggered
- Direction
- Elders.Cronus.AutoUpdates uses Elders.Cronus.EventStore.AutoUpdater.Events, so a change to Elders.Cronus.EventStore.AutoUpdater.Events can break Elders.Cronus.AutoUpdates, while a change to Elders.Cronus.AutoUpdates can't break Elders.Cronus.EventStore.AutoUpdater.Events.
- Position
- Below the diagonal: Elders.Cronus.AutoUpdates uses a module listed above it, which is the healthy direction.
32→24 Elders.Cronus.EventStore.AutoUpdater uses Elders.Cronus✕
- Connections
- 1 pair of types, where a type in Elders.Cronus.EventStore.AutoUpdater uses a type in Elders.Cronus.
- The types involved
Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterApplicationService→Elders.Cronus.ISystemAppService
- Direction
- Elders.Cronus.EventStore.AutoUpdater uses Elders.Cronus, so a change to Elders.Cronus can break Elders.Cronus.EventStore.AutoUpdater, while a change to Elders.Cronus.EventStore.AutoUpdater can't break Elders.Cronus.
- Position
- Below the diagonal: Elders.Cronus.EventStore.AutoUpdater uses a module listed above it, which is the healthy direction.
32→27 Elders.Cronus.EventStore.AutoUpdater uses Elders.Cronus.EventStore.AutoUpdater.Commands✕
- Connections
- 5 pairs of types, where a type in Elders.Cronus.EventStore.AutoUpdater uses a type in Elders.Cronus.EventStore.AutoUpdater.Commands.
- The types involved
Elders.Cronus.EventStore.AutoUpdater.AutoUpdater→Elders.Cronus.EventStore.AutoUpdater.Commands.SingleAutoUpdateElders.Cronus.EventStore.AutoUpdater.AutoUpdaterApplicationService→Elders.Cronus.EventStore.AutoUpdater.Commands.BulkRequestAutoUpdateElders.Cronus.EventStore.AutoUpdater.AutoUpdaterApplicationService→Elders.Cronus.EventStore.AutoUpdater.Commands.FailAutoUpdateElders.Cronus.EventStore.AutoUpdater.AutoUpdaterApplicationService→Elders.Cronus.EventStore.AutoUpdater.Commands.FinishAutoUpdateElders.Cronus.EventStore.AutoUpdater.AutoUpdaterApplicationService→Elders.Cronus.EventStore.AutoUpdater.Commands.RequestAutoUpdate
- Direction
- Elders.Cronus.EventStore.AutoUpdater uses Elders.Cronus.EventStore.AutoUpdater.Commands, so a change to Elders.Cronus.EventStore.AutoUpdater.Commands can break Elders.Cronus.EventStore.AutoUpdater, while a change to Elders.Cronus.EventStore.AutoUpdater can't break Elders.Cronus.EventStore.AutoUpdater.Commands.
- Position
- Below the diagonal: Elders.Cronus.EventStore.AutoUpdater uses a module listed above it, which is the healthy direction.
32→28 Elders.Cronus.EventStore.AutoUpdater uses Elders.Cronus.EventStore.AutoUpdater.Events✕
- Connections
- 5 pairs of types, where a type in Elders.Cronus.EventStore.AutoUpdater uses a type in Elders.Cronus.EventStore.AutoUpdater.Events.
- The types involved
Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterState→Elders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateFailedElders.Cronus.EventStore.AutoUpdater.AutoUpdaterState→Elders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateFinishedElders.Cronus.EventStore.AutoUpdater.AutoUpdaterState→Elders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateRequestedElders.Cronus.EventStore.AutoUpdater.AutoUpdaterState→Elders.Cronus.EventStore.AutoUpdater.Events.AutoUpdateTriggeredElders.Cronus.EventStore.AutoUpdater.AutoUpdaterState→Elders.Cronus.EventStore.AutoUpdater.Events.AutoUpdaterInitialized
- Direction
- Elders.Cronus.EventStore.AutoUpdater uses Elders.Cronus.EventStore.AutoUpdater.Events, so a change to Elders.Cronus.EventStore.AutoUpdater.Events can break Elders.Cronus.EventStore.AutoUpdater, while a change to Elders.Cronus.EventStore.AutoUpdater can't break Elders.Cronus.EventStore.AutoUpdater.Events.
- Position
- Below the diagonal: Elders.Cronus.EventStore.AutoUpdater uses a module listed above it, which is the healthy direction.
32→33 Elders.Cronus.EventStore.AutoUpdater uses (global) part of a loop✕
- Connections
- 2 pairs of types, where a type in Elders.Cronus.EventStore.AutoUpdater uses a type in (global).
- The types involved
Elders.Cronus.EventStore.AutoUpdater.AutoUpdater→AutoUpdateElders.Cronus.EventStore.AutoUpdater.AutoUpdaterState→AutoUpdate
- Direction
- Elders.Cronus.EventStore.AutoUpdater uses (global), so a change to (global) can break Elders.Cronus.EventStore.AutoUpdater, while a change to Elders.Cronus.EventStore.AutoUpdater can't break (global).
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→32 (global) uses Elders.Cronus.EventStore.AutoUpdater✕
- Connections
- 1 pair of types, where a type in (global) uses a type in Elders.Cronus.EventStore.AutoUpdater.
- The types involved
AutoUpdate→Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterStatus
- Direction
- (global) uses Elders.Cronus.EventStore.AutoUpdater, so a change to Elders.Cronus.EventStore.AutoUpdater can break (global), while a change to (global) can't break Elders.Cronus.EventStore.AutoUpdater.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 3 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 305 WriteOnlyPrivateField finding(s) in Explicit Debt — start with PublisherTestsCollection.cs (26), When_switching_a_projection_to_non_versionable.cs (12), When_service_is_registered_via_discovery.cs (10); Resolve the 13 EmptyCatchBlock finding(s) in Explicit Debt — start with ProgressTracker.cs (2), CronusJob.cs, PublicEventsPlayer.cs; Resolve the 2 redundant comment finding(s) in Comment Value — start with EventStoreIndicesStartup.cs, CronusProjectionBootstrapper.cs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 redundant comment finding(s) in Comment Value — start with EventStoreIndicesStartup.cs, CronusProjectionBootstrapper.cs. | +5.4 pts | Low | Comment Value |
| Resolve the 13 EmptyCatchBlock finding(s) in Explicit Debt — start with ProgressTracker.cs (2), CronusJob.cs, PublicEventsPlayer.cs. | +7.6 pts | Medium | Explicit Debt |
| Resolve the 305 WriteOnlyPrivateField finding(s) in Explicit Debt — start with PublisherTestsCollection.cs (26), When_switching_a_projection_to_non_versionable.cs (12), When_service_is_registered_via_discovery.cs (10). | +11.5 pts | High | Explicit Debt |
| Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with ProjectionRepository.cs, PublisherBase.cs, RetryPolicy.cs. | +5.2 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.5 pts | Medium | Architecture documentation |
| Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`. | +4.5 pts | Medium | Nullable reference types |
| Expand the README with getting-started, architecture overview and a project map. | +2.4 pts | Medium | Documentation (README) |
| Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers. | +2.1 pts | Medium | Library API & versioning |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/Elders.Cronus.Tests/SingletonPerTenantTests.cs | 2.5 | Slop | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus/Projections/ProjectionRepository.cs | 3.0 | Slop | Explicit Debt: EmptyCatchBlock |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/Elders.Cronus.Tests/Projections/When_projection_version_with_status_building_is_outside_of_the_timebox.cs | 4.0 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Discoveries/When_service_is_registered_via_discovery.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Discoveries/When_service_overrides_already_registered_via_discovery.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Middleware/When_transfering_to_another_middleware.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Projections/When_switching_a_projection_to_non_versionable.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/PublisherTests/PublisherTestsCollection.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Projections/When_projection_hash_is_calculated.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/EventStream.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/InMemoryEventStoreSuite/When_loading_aggregate_root_from_event_store.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Projections/When_adding_a_building_version_to_a_live_collection.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Projections/When_adding_a_live_version.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Projections/When_adding_a_live_version_to_a_versions_collection.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Projections/When_adding_a_live_version_twice.cs | 5.2 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Projections/When_adding_a_building_verrsion.cs | 5.3 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Projections/When_adding_a_canceled_version.cs | 5.3 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Projections/When_adding_a_live_version_to_a_versions_collectionth.cs | 5.3 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/Elders.Cronus.Tests/Projections/When_adding_a_timedout_version.cs | 5.3 | Mixed | Explicit Debt: WriteOnlyPrivateField |
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 75 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 — 75 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, 621 of 633 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — 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: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference 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 `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D19 Documentation Quality — 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D19 Documentation Quality — 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 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.
- D39 IL Efficiency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- 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.
- ES3 PII in the event store — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — 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. 36 further occurrence(s) are not listed individually; the score already reflects all 76.
- 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.
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- 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.
- 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".
- 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
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RebuildProjection_Job.RunJobAsync at 18.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RebuildProjection_Job.RunJobAsync (cyclomatic 18), ProjectionVersions.Add (cyclomatic 17), RebuildProjectionSequentially_Job.RunJobAsync (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was CronusOptionsProviderBase.TryValidateObjectRecursive at 36.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cognitive Complexity — start with CronusOptionsProviderBase.TryValidateObjectRecursive (cognitive 36), RebuildProjectionSequentially_Job.RunJobAsync (cognitive 32), ProjectionRepository.SaveAsync (cognitive 29). — 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 7 together lifts Cognitive Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
19 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with RebuildProjectionSequentially_Job.cs, CronusOptionsProviderBase.cs, ProjectionRepository.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with RebuildProjectionSequentially_Job.cs, EventStoreIndexManagerAppService.cs, PublisherBase.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with RebuildIndex_MessageCounter_Job.cs, RebuildProjectionSequentially_JobData.cs, RebuildProjectionSequentially_Job.cs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
6 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 57 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 136 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 12 direct `PackageReference`(s), and 123 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 64 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
371 deducted debt markers + 10 dead symbols across 12337 LoC in the .NET projects (23.1/KLoC) → score 0.0.
What to do
- Resolve the 305 WriteOnlyPrivateField finding(s) in Explicit Debt — start with PublisherTestsCollection.cs (26), When_switching_a_projection_to_non_versionable.cs (12), When_service_is_registered_via_discovery.cs (10). — One of this dimension's main actionable groups (305 issue-level).
- Resolve the 13 EmptyCatchBlock finding(s) in Explicit Debt — start with ProgressTracker.cs (2), CronusJob.cs, PublicEventsPlayer.cs. — One of this dimension's main actionable groups (13 issue-level).
- Resolve the 15 Whole file has no live code finding(s) in Explicit Debt — start with InMemoryIndexStore.cs, InMemoryPublisher.cs, When_loading_aggregate_root_with_entity_from_event_store.cs. — One of this dimension's main actionable groups (15 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
6 projects, 840 source files, 16001 hand-written lines of code (12337 production / 3664 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), 4 inter-project edges.
D24 · Comment Value
2 of 52 judged comments only repeat the code they sit on (3.8 %). 5 comment(s) in another language or script were not judged.
What to do
- Resolve the 2 redundant comment finding(s) in Comment Value — start with EventStoreIndicesStartup.cs, CronusProjectionBootstrapper.cs. — One of this dimension's main actionable groups (2 recommendation-level).
D26 · Project Cohesion
1 of 3 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Elders.Cronus.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
73 % of calls cross a namespace and 15 % go through an interface, but 99 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What to do
- Resolve the 1 Pass-through layer finding(s) in Navigability — start with DiscoveryContext.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 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).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 2 high, 1 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 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).
D34 · Knowledge Freshness
64 of 64 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Elders.Cronus/Projections/ProjectionRepository.cs. Counted over 64 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with ProjectionRepository.cs, PublisherBase.cs, RetryPolicy.cs. — One of this dimension's main actionable groups (64 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 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
- `CronusHeartbeat` is a singleton (one shared instance) but mutates instance state outside any lock (options, tenants; e.g. `options` at line 63). — src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:12
- `CronusBooter` is a singleton (one shared instance) but mutates instance state outside any lock (tenantOptions; e.g. `tenantOptions` at line 59). — src/Elders.Cronus/Hosting/CronusBooter.cs:11
- `DefaultCronusContextFactory` is a singleton (one shared instance) but mutates instance state outside any lock (tenantsOptions; e.g. `tenantsOptions` at line 80). — src/Elders.Cronus/MessageProcessing/CronusContextFactory.cs:15
- `CronusLogger` 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 (startupLogger, factory; e.g. `startupLogger` at line 40). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Elders.Cronus/Userfull/CronusLogger.cs:29
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 Elders.Cronus ↔ Elders.Cronus.Cluster.Job ↔ Elders.Cronus.Discoveries ↔ Elders.Cronus.EventStore ↔ Elders.Cronus.EventStore.Index ↔ Elders.Cronus.EventStore.Players ↔ Elders.Cronus.IntegrityValidation ↔ Elders.Cronus.MessageProcessing ↔ Elders.Cronus.Migrations ↔ Elders.Cronus.Multitenancy ↔ Elders.Cronus.Projections ↔ Elders.Cronus.Projections.Cassandra ↔ Elders.Cronus.Projections.Rebuilding ↔ Elders.Cronus.Projections.Versioning depend on each other. The lightest dependency in the cycle is Elders.Cronus → Elders.Cronus.Cluster.Job (Elders.Cronus.CronusHost → Elders.Cronus.Cluster.Job.JobManager, 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/Elders.Cronus/Hosting/CronusHost.cs:4
- The namespaces (global) ↔ Elders.Cronus.EventStore.AutoUpdater ↔ Elders.Cronus.EventStore.AutoUpdater.Commands ↔ Elders.Cronus.EventStore.AutoUpdater.Events depend on each other. The lightest dependency in the cycle is (global) → Elders.Cronus.EventStore.AutoUpdater (AutoUpdate → Elders.Cronus.EventStore.AutoUpdater.AutoUpdaterStatus, 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/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterState.cs:1
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `AutoUpdater`'s public constructor takes `bc` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AutoUpdater` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdater.cs:13
- `ProjectionVersionManager`'s public constructor takes `hash` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `ProjectionVersionManager` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Elders.Cronus/Projections/Versioning/ProjectionVersionManager.cs:11
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM5 · Encapsulated state
DM9 · Scattered domain decisions
- Elders.Cronus.Projections.ProjectionStatus's [Fixing, New] are judged in Elders.Cronus.Projections.ProjectionVersions, Elders.Cronus.Projections.Versioning.ProjectionVersionManager — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
What to do
- Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
ES2 · Immutable events
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — src/Elders.Cronus/Cluster/Job/InMemory/InMemoryCronusJobRunner.cs:10, src/Elders.Cronus/PublisherBase.cs:80, src/Elders.Cronus.Performance/LoggingBenchmark.cs:54
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `MyLogger` has 3 unfinished members out of 4 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented. — src/Elders.Cronus.Performance/LoggingBenchmark.cs:52
- `BeginScope` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Elders.Cronus.Performance/LoggingBenchmark.cs:54
- `IsEnabled` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/Elders.Cronus.Performance/LoggingBenchmark.cs:55
- `LogCore` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/Elders.Cronus.Performance/LoggingBenchmark.cs:59
- `JobManager` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Elders.Cronus/Cluster/Job/InMemory/InMemoryCronusJobRunner.cs:10
- `PingAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/Elders.Cronus/Cluster/Job/InMemory/NoClusterOperations.cs:8
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×34) — src/Elders.Cronus.Performance/LoggingBenchmark.cs:5, src/Elders.Cronus.Performance/Program.cs:4, src/Elders.Cronus.Performance/Program.cs:5, …
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)
- The root README is 119 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- 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 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 762/798 types (95%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
- No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
What to do
- Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
- Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
P2 · Observability
What to do
- Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
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 867 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:2
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:7
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.
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
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/Elders.Cronus/Hosting/CronusHost.cs:172, src/Elders.Cronus/Hosting/ProjectionsStartup.cs:17
- `await updater.ApplyAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/AutoUpdates/AutoUpdateSaga.cs:24
- `await repository.LoadAsync<AutoUpdater>(command.Id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×4) — src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:16, src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:32, src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:48, …
- `await indexStore.ApendAsync(indexRecord)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/EventStore/Index/EventToAggregateRootId/RebuildIndex_EventToAggregateRootId_Job.cs:48
- `await countTask` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:71
- `await resetTask` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:72
- `await retryPolicy.ExecuteActionAsync(() => workflow.RunAsync(execution.Context))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/FaultHandling/InMemoryRetryWorkflow.cs:26
- `await func()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/FaultHandling/RetryPolicy.cs:165
- `await Task.Delay(delay)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/FaultHandling/RetryPolicy.cs:207
- `await rpcHost.StartAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/Hosting/CronusHost.cs:120
- `await Task.Delay(TimeSpan.FromSeconds(options.IntervalInSeconds), stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:45
- `await base.StopAsync(stoppingToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeatService.cs:49
- `await source.EnumerateEventStore(@operator, playerOptions)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Elders.Cronus/Migrations/CopyEventStore.cs:24, src/Elders.Cronus/Migrations/ValidateEventStore.cs:27
- `await OptionsChangedBootstrapProjectionsForTenantAsync(newOptions)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:35
- `await Task.WhenAll(tenantBootstrapTasks)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:51, src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:103
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
X1 · Async correctness
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. — src/Elders.Cronus/Hosting/CronusHost.cs:172
- 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. — src/Elders.Cronus/Hosting/ProjectionsStartup.cs:17
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
- `pingSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 41). Every use of it in `RunJobAsync` 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 pingSource = …;`), which releases it at the end of the scope on every path including a throw. — src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:41
- `handlerInstance` is a `IHandlerInstance`, which implements `IDisposable`, and it is created here (line 45). Every use of it in `SaveAsync` 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 handlerInstance = …;`), which releases it at the end of the scope on every path including a throw. — src/Elders.Cronus/Projections/ProjectionRepository.cs:45
- `handlerInstance` is a `IHandlerInstance`, which implements `IDisposable`, and it is created here (line 122). Every use of it in `SaveAsync` 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 handlerInstance = …;`), which releases it at the end of the scope on every path including a throw. — src/Elders.Cronus/Projections/ProjectionRepository.cs:122
- `projectionInstance` is a `IHandlerInstance`, which implements `IDisposable`, and it is created here (line 209). Every use of it in `GetInternalAsync` 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 projectionInstance = …;`), which releases it at the end of the scope on every path including a throw. — src/Elders.Cronus/Projections/ProjectionRepository.cs:209
- `projectionInstance` is a `IHandlerInstance`, which implements `IDisposable`, and it is created here (line 251). Every use of it in `GetAsOfInternalAsync` 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 projectionInstance = …;`), which releases it at the end of the scope on every path including a throw. — src/Elders.Cronus/Projections/ProjectionRepository.cs:251
- `pingSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 91). Every use of it in `RunJobAsync` 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 pingSource = …;`), which releases it at the end of the scope on every path including a throw. — src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:91
- `pingSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 93). Every use of it in `RunJobAsync` 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 pingSource = …;`), which releases it at the end of the scope on every path including a throw. — src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:93
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 9/36 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. (×27) — src/Elders.Cronus/DangerZone/DangerZoneExecutor.cs:26, src/Elders.Cronus/EventStore/Index/ProjectionIndex.cs:22, src/Elders.Cronus/FaultHandling/InMemoryRetryWorkflow.cs:22, …
- 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
- Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). — src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:35
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
- The guard on line 13 rejects `status` and line 14 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(status)` is true of a value that is NOT null: it is satisfied by an EMPTY `status`, and on that path `status` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterStatus.cs:14
- The guard on line 61 rejects `value` and line 62 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(value)` is true of a value that is NOT null: it is satisfied by an EMPTY `value`, and on that path `value` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Elders.Cronus/EventStore/PagingOptions.cs:62
- The guard on line 69 rejects `tenant` and line 69 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(tenant)` is true of a value that is NOT null: it is satisfied by an EMPTY `tenant`, and on that path `tenant` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Elders.Cronus/MessageProcessing/CronusContextFactory.cs:69
- The guard on line 13 rejects `aggregateRootId` and line 13 reports that rejection as `ArgumentNullException` — but the condition's own test `aggregateRootId.IsEmpty` is true of a value that is NOT null: it reads a member of `aggregateRootId`, so it can only be evaluated on a non-null `aggregateRootId` (a null one would throw `NullReferenceException` before the guard decided anything). So a caller whose `aggregateRootId` 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. — src/Elders.Cronus/Projections/EventOrigin.cs:13
- The guard on line 17 rejects `contractId` and line 17 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(contractId)` is true of a value that is NOT null: it is satisfied by an EMPTY `contractId`, and on that path `contractId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Elders.Cronus/Projections/EventStoreIndexEventTypeId.cs:17
- The guard on line 47 rejects `contractId` and line 47 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(contractId)` is true of a value that is NOT null: it is satisfied by an EMPTY `contractId`, and on that path `contractId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Elders.Cronus/Projections/EventStoreIndexEventTypeId.cs:47
- The guard on line 188 rejects `projectionName` and line 188 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(projectionName)` is true of a value that is NOT null: it is satisfied by an EMPTY `projectionName`, and on that path `projectionName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Elders.Cronus/Projections/ProjectionRepository.cs:188
- The guard on line 15 rejects `status` and line 16 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(status)` is true of a value that is NOT null: it is satisfied by an EMPTY `status`, and on that path `status` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Elders.Cronus/Projections/ProjectionStatus.cs:16
- The guard on line 18 rejects `hash` and line 18 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(hash)` is true of a value that is NOT null: it is satisfied by an EMPTY `hash`, and on that path `hash` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. (×2) — src/Elders.Cronus/Projections/Versioning/Commands/FixProjectionVersion.cs:18, src/Elders.Cronus/Projections/Versioning/Commands/NewProjectionVersion.cs:18
What to do
- Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×13) — src/Elders.Cronus/Cluster/Job/CronusJob.cs:77, src/Elders.Cronus/EventStore/Players/PublicEventsPlayer.cs:34, src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:51, …
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×4) — src/Elders.Cronus/EventStore/Index/EventToAggregateRootId/RebuildIndex_EventToAggregateRootId_Job.cs:43, src/Elders.Cronus/EventStore/LoggingAggregateRepository.cs:51, src/Elders.Cronus/Migrations/CronusMigrator.cs:35, …
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- This method contradicts itself about `projection`: line 123 assigns it with `as IProjectionDefinition`, which hands back null rather than throwing when the value is not a `IProjectionDefinition`, but line 125 then dereferences it directly as `projection.GetProjectionIds` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `projection` once before the first use and handle the null case, or cast with `(IProjectionDefinition)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Elders.Cronus/Projections/ProjectionRepository.cs:125
- This method contradicts itself about `iterator`: line 58 assigns it with `as IEnumerator<WorkflowBase<TContext>>`, which hands back null rather than throwing when the value is not a `IEnumerator<WorkflowBase<TContext>>`, but line 63 then dereferences it directly as `iterator.MoveNext` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `iterator` once before the first use and handle the null case, or cast with `(IEnumerator<WorkflowBase<TContext>>)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/Elders.Cronus/Workflow/WorkflowBase.cs:63
- 0/2 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 35% | Weak — gated by D17, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 82% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 48% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56% | Adequate — gated by P10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 86% | Strong | Solid. |
| Domain Modelling | 83% | Strong | Solid. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 78% | Strong | Solid. |
Unscored — 4 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 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.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- 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.
- D10 Test Quality — ~4032 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D19 Documentation Quality — D19 withholds "Documentation: empty section": 4 candidate(s) were measured and not published.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- 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.
- D23 Boundary Type-Coupling — small single-context codebase (12,337 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Elders.Cronus), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- D9 Test Distribution — 1 test project(s) found on disk but excluded from the analyzed solution.
- DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 12 event handler(s); 16 CQRS handler(s)
- ED5 Idempotency — not scored — 26 of 38 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Fold determinism — no Apply/When folds detected — fold-determinism check not applicable
- ES3 PII in the event store — This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P8 Schema migrations — no EF Core usage detected
- 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.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 325 finding(s)
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Discoveries/When_discoving_jobs_from_discoveryContext.cs:17
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Discoveries/When_service_is_registered_via_discovery.cs:13
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Discoveries/When_service_is_registered_via_discovery.cs:42
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Discoveries/When_service_overrides_already_registered_via_discovery.cs:13
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Discoveries/When_service_overrides_already_registered_via_discovery.cs:49
- WriteOnlyPrivateField src/Elders.Cronus.Tests/EventStream.cs:12
- WriteOnlyPrivateField src/Elders.Cronus.Tests/EventStream.cs:36
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Hosting/When_adding_event_to_aggregateCommit.cs:11
- WriteOnlyPrivateField src/Elders.Cronus.Tests/InMemoryEventStoreSuite/When_loading_aggregate_root_from_event_store.cs:20
- WriteOnlyPrivateField src/Elders.Cronus.Tests/InMemoryEventStoreSuite/When_saving_aggregate_root_in_event_store.cs:15
- WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When__AggregateCommit__has_duplicate_revisions.cs:13
- WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When__AggregateCommit__has_missing_revisions.cs:14
- WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When__AggregateCommit__has_unordered_revisions.cs:13
- WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When__AggregateCommit__has_unordered_revisions_and_resolving_them.cs:13
- WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When__EventStreamPolicy_is_applied_to_a_correct__EventStream__.cs:13
- WriteOnlyPrivateField src/Elders.Cronus.Tests/IntegrityValidation/When_comparing_two__IntegrityRules__are_identical.cs:11
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_attaching_multiple_middlewares.cs:10
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_breaking_middleware.cs:11
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_executing_middleware_tree.cs:9
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_executing_single_middleware.cs:9
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_transfering_to_another_middleware.cs:11
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_transfering_to_another_middleware.cs:59
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Middleware/When_transfering_to_another_middleware_and_there_is_no_followup_middleware.cs:11
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Migrations/When_adding_event_to_aggregateCommit.cs:14
- WriteOnlyPrivateField src/Elders.Cronus.Tests/Migrations/When_evalueting_if_migration_should_apply.cs:14
- EmptyCatchBlock src/Elders.Cronus/Cluster/Job/CronusJob.cs:77
- EmptyCatchBlock src/Elders.Cronus/EventStore/Players/PublicEventsPlayer.cs:34
- EmptyCatchBlock src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:51
- EmptyCatchBlock src/Elders.Cronus/MessageProcessing/AggregateCommitPublisher.cs:34
- EmptyCatchBlock src/Elders.Cronus/MessageProcessing/ErrorContext.cs:45
- EmptyCatchBlock src/Elders.Cronus/Migrations/AggregateCommitMigrationWorkflow.cs:30
- EmptyCatchBlock src/Elders.Cronus/Migrations/CronusMigrator.cs:35
- EmptyCatchBlock src/Elders.Cronus/Migrations/DeleteEventStoreEvents.cs:38
- EmptyCatchBlock src/Elders.Cronus/Migrations/MigrationWorkflowBase.cs:32
- EmptyCatchBlock src/Elders.Cronus/Projections/ProjectionRepository.cs:162
- EmptyCatchBlock src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs:143
- EmptyCatchBlock src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs:170
- EmptyCatchBlock src/Elders.Cronus/Workflow/ExceptionEaterWorkflow.cs:21
- Namespace dependency cycle src/Elders.Cronus/Hosting/CronusHost.cs:4
- Namespace dependency cycle src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterState.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 181 finding(s)
- Async method without CancellationToken: WipeDataAsync src/Elders.Cronus/DangerZone/DangerZoneExecutor.cs:26
- Async method without CancellationToken: IndexAsync src/Elders.Cronus/EventStore/Index/ProjectionIndex.cs:22
- Async method without CancellationToken: RunAsync src/Elders.Cronus/FaultHandling/InMemoryRetryWorkflow.cs:22
- Async method without CancellationToken: ExecuteActionAsync src/Elders.Cronus/FaultHandling/RetryPolicy.cs:149
- Async method without CancellationToken: StartAsync src/Elders.Cronus/Hosting/CronusHost.cs:85
- Async method without CancellationToken: StopAsync src/Elders.Cronus/Hosting/CronusHost.cs:131
- Async method without CancellationToken: RunAsync src/Elders.Cronus/MessageProcessing/DynamicMessageHandle.cs:12
- Async method without CancellationToken: RunAsync src/Elders.Cronus/MessageProcessing/DynamicMessageIndex.cs:12
- Async method without CancellationToken: RunAsync src/Elders.Cronus/MessageProcessing/MessageHandleWorkflow.cs:63
- Async method without CancellationToken: RunAsync src/Elders.Cronus/Migrations/CopyEventStore.cs:16
- Async method without CancellationToken: RunAsync src/Elders.Cronus/Migrations/DeleteEventStoreEvents.cs:15
- Async method without CancellationToken: RunAsync src/Elders.Cronus/Migrations/ValidateEventStore.cs:19
- Async method without CancellationToken: BootstrapAsync src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:39
- Async method without CancellationToken: BootstrapProjectionsForTenantAsync src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:54
- Async method without CancellationToken: OptionsChangedBootstrapProjectionsForTenantAsync src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:86
- Async method without CancellationToken: GetInternalAsync src/Elders.Cronus/Projections/ProjectionRepository.cs:197
- Async method without CancellationToken: GetAsOfInternalAsync src/Elders.Cronus/Projections/ProjectionRepository.cs:223
- Async method without CancellationToken: LoadProjectionStreamAsync src/Elders.Cronus/Projections/ProjectionRepository.cs:318
- Async method without CancellationToken: SaveAsync src/Elders.Cronus/Projections/ProjectionRepositoryWithFallback.cs:72
- Async method without CancellationToken: CancelJobAsync src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:216
- Async method without CancellationToken: CancelJobAsync src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:199
- Async method without CancellationToken: RunAsync src/Elders.Cronus/Workflow/DiagnosticsWorkflow.cs:49
- Async method without CancellationToken: RunAsync src/Elders.Cronus/Workflow/ExceptionEaterWorkflow.cs:18
- Async method without CancellationToken: AbstractRunAsync src/Elders.Cronus/Workflow/Workflow.cs:7
- Async method without CancellationToken: RunAsync src/Elders.Cronus/Workflow/Workflow.cs:23
- Awaits without ConfigureAwait(false) src/Elders.Cronus/AutoUpdates/AutoUpdateSaga.cs:24
- Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:16
- Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:32
- Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:48
- Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterApplicationService.cs:58
- Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/Index/EventToAggregateRootId/RebuildIndex_EventToAggregateRootId_Job.cs:48
- Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:71
- Awaits without ConfigureAwait(false) src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:72
- Awaits without ConfigureAwait(false) src/Elders.Cronus/FaultHandling/InMemoryRetryWorkflow.cs:26
- Awaits without ConfigureAwait(false) src/Elders.Cronus/FaultHandling/RetryPolicy.cs:165
- Awaits without ConfigureAwait(false) src/Elders.Cronus/FaultHandling/RetryPolicy.cs:207
- Awaits without ConfigureAwait(false) src/Elders.Cronus/Hosting/CronusHost.cs:120
- Awaits without ConfigureAwait(false) src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:45
- Awaits without ConfigureAwait(false) src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeatService.cs:49
- Awaits without ConfigureAwait(false) src/Elders.Cronus/Migrations/CopyEventStore.cs:24
- Awaits without ConfigureAwait(false) src/Elders.Cronus/Migrations/ValidateEventStore.cs:27
- Awaits without ConfigureAwait(false) src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:35
- Awaits without ConfigureAwait(false) src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:51
- Awaits without ConfigureAwait(false) src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:103
- Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemory/InMemoryIndexStore.cs:1
- Whole file has no live code — 5 debt markers inside it src/Elders.Cronus.Tests/InMemory/InMemoryPublisher.cs:1
- Whole file has no live code — 3 debt markers inside it src/Elders.Cronus.Tests/InMemoryEventStoreSuite/When_loading_aggregate_root_with_entity_from_event_store.cs:1
- Whole file has no live code — 2 debt markers inside it src/Elders.Cronus.Tests/InMemoryEventStoreSuite/When_loading_events_for_replay.cs:1
- Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_checking_a_locked_resource.cs:1
- Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_checking_a_not_locked_resource.cs:1
- Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_checking_for_expired_locked_resource.cs:1
- Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_locking_resource.cs:1
- Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_unlocking_a_locked_resource.cs:1
- Whole file has no live code — 1 debt marker inside it src/Elders.Cronus.Tests/InMemoryLock/When_unlocking_a_specific_locked_resource.cs:1
- Whole file has no live code — 6 debt markers inside it src/Elders.Cronus.Tests/When_resolve_scoped_component_out_of_scope.cs:1
- Whole file has no live code — 1 debt marker inside it src/Elders.Cronus/Discoveries/ProjectionPlayerDiscovery.cs:1
- Whole file has no live code — 4 debt markers inside it src/Elders.Cronus/MessageProcessing/CronusPublisher.cs:11
- Whole file has no live code — 2 debt markers inside it src/Elders.Cronus/Projections/InMemory/InMemoryProjectionStore.cs:1
- Whole file has no live code — 1 debt marker inside it src/Elders.Cronus/Projections/Versioning/InMemoryProjectionVersionStore.cs:10
- TodoComment src/Elders.Cronus/AutoUpdates/AutoUpdateSaga.cs:11
- TodoComment src/Elders.Cronus/Discoveries/CronusHostDiscovery.cs:42
- TodoComment src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdater.cs:56
- TodoComment src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterState.cs:72
- TodoComment src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterState.cs:80
- TodoComment src/Elders.Cronus/EventStore/Players/ReplayPublicEvents_Job.cs:48
- TodoComment src/Elders.Cronus/Hosting/ICronusStartup.cs:8
- TodoComment src/Elders.Cronus/Hosting/ICronusStartup.cs:15
- TodoComment src/Elders.Cronus/Hosting/SingletonPerTenantContainer.cs:29
- TodoComment src/Elders.Cronus/Projections/ProjectionRepository.cs:44
- TodoComment src/Elders.Cronus/Projections/ProjectionVersions.cs:152
- TodoComment src/Elders.Cronus/Projections/ProjectionVersions.cs:164
- TodoComment src/Elders.Cronus/Projections/Versioning/ProjectionVersionManager.cs:94
- Swallowed exception (empty catch) src/Elders.Cronus/Cluster/Job/CronusJob.cs:77
- Swallowed exception (empty catch) src/Elders.Cronus/EventStore/Players/PublicEventsPlayer.cs:34
- Swallowed exception (empty catch) src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:51
- Swallowed exception (empty catch) src/Elders.Cronus/MessageProcessing/AggregateCommitPublisher.cs:34
- Swallowed exception (empty catch) src/Elders.Cronus/MessageProcessing/ErrorContext.cs:45
- Swallowed exception (empty catch) src/Elders.Cronus/Migrations/AggregateCommitMigrationWorkflow.cs:30
- Swallowed exception (empty catch) src/Elders.Cronus/Migrations/CronusMigrator.cs:35
- Swallowed exception (empty catch) src/Elders.Cronus/Migrations/DeleteEventStoreEvents.cs:38
- Swallowed exception (empty catch) src/Elders.Cronus/Migrations/MigrationWorkflowBase.cs:32
- Swallowed exception (empty catch) src/Elders.Cronus/Projections/ProjectionRepository.cs:162
- Swallowed exception (empty catch) src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs:143
- Swallowed exception (empty catch) src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs:170
- Swallowed exception (empty catch) src/Elders.Cronus/Workflow/ExceptionEaterWorkflow.cs:21
- Dead code: OneHour src/Elders.Cronus/Projections/Versioning/VersionRequestTimebox.cs:12
- Dead code: EightHours src/Elders.Cronus/Projections/Versioning/VersionRequestTimebox.cs:14
- Dead code: RealyLongTime src/Elders.Cronus/Projections/Versioning/VersionRequestTimebox.cs:16
- Dead code: DiagnosticsUnhandledExceptionKey src/Elders.Cronus/Workflow/DiagnosticsWorkflow.cs:36
- Dead code: OverriderDiscoveredModel src/Elders.Cronus.Tests/Discoveries/Models.cs:13
- Dead code: LoadAggregateCommitsAsync src/Elders.Cronus.Tests/InMemory/InMemoryEventStorePlayer.cs:27
- Dead code: TestEventStorePlayer src/Elders.Cronus.Tests/Migrations/TestModel/TestEventStorePlayer.cs:9
- Dead code: Class1 src/Elders.Cronus.Tests/Performance/Class1.cs:3
- Dead code: When__SingletonPerTenantContainer__is_used src/Elders.Cronus.Tests/SingletonPerTenantTests.cs:9
- Dead code: When__SingletonPerTenantContainer__is_disposed src/Elders.Cronus.Tests/SingletonPerTenantTests.cs:31
- Argument guard throws the exception its own condition disproves src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdaterStatus.cs:14
- Argument guard throws the exception its own condition disproves src/Elders.Cronus/EventStore/PagingOptions.cs:62
- Argument guard throws the exception its own condition disproves src/Elders.Cronus/MessageProcessing/CronusContextFactory.cs:69
- Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/EventOrigin.cs:13
- Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/EventStoreIndexEventTypeId.cs:17
- Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/EventStoreIndexEventTypeId.cs:47
- Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/ProjectionRepository.cs:188
- Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/ProjectionStatus.cs:16
- Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/Versioning/Commands/FixProjectionVersion.cs:18
- Argument guard throws the exception its own condition disproves src/Elders.Cronus/Projections/Versioning/Commands/NewProjectionVersion.cs:18
- CommentedOutCode src/Elders.Cronus.Tests/Projections/When_projection_version_with_status_building_is_outside_of_the_timebox.cs:74
- CommentedOutCode src/Elders.Cronus/EventStore/Integrity/EventStreamIntegrityPolicy.cs:44
- CommentedOutCode src/Elders.Cronus/EventStore/Integrity/EventStreamIntegrityPolicy.cs:51
- CommentedOutCode src/Elders.Cronus/Projections/ProjectionVersion.cs:36
- CommentedOutCode src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:63
- CommentedOutCode src/Elders.Cronus/FaultHandling/Strategies/Incremental.cs:56
- CommentedOutCode src/Elders.Cronus/Hosting/AssemblyLoader.cs:53
- CommentedOutCode src/Elders.Cronus/Multitenancy/DefaultTenantResolver.cs:19
- Disposable created and abandoned in the method that made it src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:41
- Disposable created and abandoned in the method that made it src/Elders.Cronus/Projections/ProjectionRepository.cs:45
- Disposable created and abandoned in the method that made it src/Elders.Cronus/Projections/ProjectionRepository.cs:122
- Disposable created and abandoned in the method that made it src/Elders.Cronus/Projections/ProjectionRepository.cs:209
- Disposable created and abandoned in the method that made it src/Elders.Cronus/Projections/ProjectionRepository.cs:251
- Disposable created and abandoned in the method that made it src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:91
- Disposable created and abandoned in the method that made it src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:93
- Stateful singleton: CronusHeartbeat src/Elders.Cronus/Hosting/Heartbeat/CronusHeartbeat.cs:12
- Stateful singleton: CronusBooter src/Elders.Cronus/Hosting/CronusBooter.cs:11
- Stateful singleton: DefaultCronusContextFactory src/Elders.Cronus/MessageProcessing/CronusContextFactory.cs:15
- Duplicated block (13 lines × 2) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:24
- Duplicated block (13 lines × 2) src/Elders.Cronus/Hosting/CronusOptionsProviderBase.cs:95
- Duplicated block (13 lines × 2) src/Elders.Cronus/Projections/ProjectionRepository.cs:209
- Duplicated block (12 lines × 2) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:74
- Duplicated block (12 lines × 2) src/Elders.Cronus/EventStore/Index/EventStoreIndexManagerAppService.cs:32
- Duplicated block (12 lines × 2) src/Elders.Cronus/PublisherBase.cs:221
- Duplicated block (7 lines × 2) src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:88
- Duplicated block (7 lines × 2) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_JobData.cs:20
- Duplicated block (7 lines × 2) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:218
- Unfinished stub — throws NotImplementedException src/Elders.Cronus/Cluster/Job/InMemory/InMemoryCronusJobRunner.cs:10
- Unfinished stub — throws NotImplementedException src/Elders.Cronus/PublisherBase.cs:80
- Unfinished stub — throws NotImplementedException src/Elders.Cronus.Performance/LoggingBenchmark.cs:54
- Sync-over-async blocking
- Sync-over-async blocking src/Elders.Cronus/Hosting/CronusHost.cs:172
- Sync-over-async blocking src/Elders.Cronus/Hosting/ProjectionsStartup.cs:17
- Constructible in an invalid state: AutoUpdater src/Elders.Cronus/EventStore/AutoUpdater/AutoUpdater.cs:13
- Constructible in an invalid state: ProjectionVersionManager src/Elders.Cronus/Projections/Versioning/ProjectionVersionManager.cs:11
- Unfinished stub — throws NotImplementedException src/Elders.Cronus.Performance/LoggingBenchmark.cs:54
- Unfinished stub — throws NotImplementedException src/Elders.Cronus/Cluster/Job/InMemory/InMemoryCronusJobRunner.cs:10
- Hollow method — returns a constant without doing the work src/Elders.Cronus.Performance/LoggingBenchmark.cs:55
- Hollow method — returns a constant without doing the work src/Elders.Cronus/Cluster/Job/InMemory/NoClusterOperations.cs:8
- Sync-over-async (deadlock risk) src/Elders.Cronus/Hosting/CronusHost.cs:172
- Sync-over-async (deadlock risk) src/Elders.Cronus/Hosting/ProjectionsStartup.cs:17
- Symbol treated as nullable, then dereferenced unguarded src/Elders.Cronus/Projections/ProjectionRepository.cs:125
- Symbol treated as nullable, then dereferenced unguarded src/Elders.Cronus/Workflow/WorkflowBase.cs:63
- Process-global static state: CronusLogger src/Elders.Cronus/Userfull/CronusLogger.cs:29
- RebuildProjection_Job.RunJobAsync (cyclomatic 18) src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:60
- ProjectionVersions.Add (cyclomatic 17) src/Elders.Cronus/Projections/ProjectionVersions.cs:58
- RebuildProjectionSequentially_Job.RunJobAsync (cyclomatic 17) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:64
- CronusHost.Start (cyclomatic 16) src/Elders.Cronus/Hosting/CronusHost.cs:187
- CronusHost.Stop (cyclomatic 16) src/Elders.Cronus/Hosting/CronusHost.cs:206
- HackComment src/Elders.Cronus.Tests/Migrations/TestModel/TestEventStorePlayer.cs:30
- CronusOptionsProviderBase.TryValidateObjectRecursive (cognitive 36) src/Elders.Cronus/Hosting/CronusOptionsProviderBase.cs:69
- RebuildProjectionSequentially_Job.RunJobAsync (cognitive 32) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:64
- ProjectionRepository.SaveAsync (cognitive 29) src/Elders.Cronus/Projections/ProjectionRepository.cs:38
- RebuildProjection_Job.RunJobAsync (cognitive 27) src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:60
- RetryableOperation.TryExecute (cognitive 21) src/Elders.Cronus/Userfull/RetryableOperation.cs:32
- RetryPolicy.ExecuteActionAsync (cognitive 20) src/Elders.Cronus/FaultHandling/RetryPolicy.cs:149
- ProjectionRepository.SaveAsync (cognitive 20) src/Elders.Cronus/Projections/ProjectionRepository.cs:104
- REDACTED
- REDACTED
- Duplicated block (20 lines × 2) src/Elders.Cronus/PublisherBase.cs:288
- Duplicated block (14 lines × 2) src/Elders.Cronus/Projections/ProjectionRepository.cs:79
- Duplicated block (17 lines × 4) src/Elders.Cronus/EventStore/AutoUpdater/Events/AutoUpdateFailed.cs:21
- Duplicated block (12–13 lines × 2) src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:18
- Duplicated block (10 lines × 2) src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:192
- Duplicated block (9 lines × 2) src/Elders.Cronus/Userfull/LateBoundMethod.cs:14
- Duplicated block (11 lines × 3) src/Elders.Cronus/Projections/Versioning/Commands/FixProjectionVersion.cs:25
- Duplicated block (11 lines × 2) src/Elders.Cronus/Projections/Versioning/Events/ProjectionVersionRequestTimedout.cs:19
- Duplicated block (6 lines × 2) src/Elders.Cronus/MessageProcessing/ApplicationServiceSubscriberWorkflow.cs:25
- Duplicated block (5 lines × 2) src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:34
- Tests outside the analyzed solution
- Skeleton type — most members are unfinished src/Elders.Cronus.Performance/LoggingBenchmark.cs:52
- Empty method body — does nothing with its inputs src/Elders.Cronus.Performance/LoggingBenchmark.cs:59
- NuGet dependencies are not locked
- Async method drops its CancellationToken: RunJobAsync src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:35
Minor — 125 finding(s)
- Orphaned file src/Elders.Cronus/Projections/ProjectionRepository.cs:1
- Orphaned file src/Elders.Cronus/PublisherBase.cs:1
- Orphaned file src/Elders.Cronus/FaultHandling/RetryPolicy.cs:1
- Orphaned file src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:1
- Orphaned file src/Elders.Cronus/Projections/Versioning/HashCodeUtility.cs:1
- Orphaned file src/Elders.Cronus/Hosting/CronusHost.cs:1
- Orphaned file src/Elders.Cronus/Projections/Rebuilding/RebuildProjection_Job.cs:1
- Orphaned file src/Elders.Cronus/Projections/Versioning/ProjectionVersionManager.cs:1
- Orphaned file src/Elders.Cronus/Projections/ProjectionRepositoryWithFallback.cs:1
- Orphaned file src/Elders.Cronus/Projections/ProjectionVersions.cs:1
- Orphaned file src/Elders.Cronus/Projections/Versioning/Handlers/ProjectionBuilder.cs:1
- Orphaned file src/Elders.Cronus/Discoveries/CronusHostDiscovery.cs:1
- Orphaned file src/Elders.Cronus/Hosting/CronusServiceCollectionExtensions.cs:1
- Orphaned file src/Elders.Cronus/Projections/Rebuilding/ProgressTracker.cs:1
- Orphaned file src/Elders.Cronus/EventStore/Players/ReplayPublicEvents_Job.cs:1
- Orphaned file src/Elders.Cronus/EventStore/AggregateRepository.cs:1
- Orphaned file src/Elders.Cronus/EventStore/Index/RebuildIndex_MessageCounter_Job.cs:1
- Orphaned file src/Elders.Cronus/Hosting/SubscriberCollectionServiceCollectionExtensions.cs:1
- Orphaned file src/Elders.Cronus/Workflow/DiagnosticsWorkflow.cs:1
- Orphaned file src/Elders.Cronus/Discoveries/ProjectionsDiscovery.cs:1
- Orphaned file src/Elders.Cronus/Projections/Rebuilding/ProjectionVersionHelper.cs:1
- Orphaned file src/Elders.Cronus/Projections/ProjectionVersion.cs:1
- Orphaned file src/Elders.Cronus/FaultHandling/RetryStrategy.cs:1
- Orphaned file src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs:1
- Orphaned file src/Elders.Cronus/Hosting/CronusOptionsProviderBase.cs:1
- Commented-out code src/Elders.Cronus.Performance/LoggingBenchmark.cs:5
- Commented-out code src/Elders.Cronus.Performance/Program.cs:4
- Commented-out code src/Elders.Cronus.Performance/Program.cs:5
- Commented-out code src/Elders.Cronus.Performance/Program.cs:7
- Commented-out code src/Elders.Cronus.Performance/Program.cs:12
- Commented-out code src/Elders.Cronus/Cluster/Job/ICronusJob.cs:13
- Commented-out code src/Elders.Cronus/Cluster/Job/ICronusJob.cs:14
- Commented-out code src/Elders.Cronus/Discoveries/ProjectionPlayerDiscovery.cs:11
- Commented-out code src/Elders.Cronus/Discoveries/ProjectionPlayerDiscovery.cs:16
- Commented-out code src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs:32
- Commented-out code src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs:73
- Commented-out code src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs:74
- Commented-out code src/Elders.Cronus/FaultHandling/RetryPolicy.cs:48
- Commented-out code src/Elders.Cronus/FaultHandling/RetryPolicy.cs:49
- Commented-out code src/Elders.Cronus/FaultHandling/RetryPolicy.cs:68
- Commented-out code src/Elders.Cronus/FaultHandling/RetryPolicy.cs:69
- Commented-out code src/Elders.Cronus/FaultHandling/RetryPolicy.cs:151
- Commented-out code src/Elders.Cronus/FaultHandling/RetryingEventArgs.cs:18
- Commented-out code src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:63
- Commented-out code src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:64
- Commented-out code src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:65
- Commented-out code src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:66
- Commented-out code src/Elders.Cronus/FaultHandling/Strategies/ExponentialBackoff.cs:67
- Commented-out code src/Elders.Cronus/FaultHandling/Strategies/FixedInterval.cs:61
- Commented-out code src/Elders.Cronus/FaultHandling/Strategies/FixedInterval.cs:62
- Duplicated predicate src/Elders.Cronus/EventStore/AggregateRepository.cs:69
- Duplicated predicate src/Elders.Cronus/Projections/Rebuilding/RebuildProjectionSequentially_Job.cs:210
- Duplicated predicate src/Elders.Cronus/EventStore/Index/Handlers/EventStoreIndexBuilder.cs:29
- Duplicated predicate src/Elders.Cronus/Projections/ProjectionVersions.cs:82
- Duplicated predicate src/Elders.Cronus/Projections/Rebuilding/ProjectionVersionHelper.cs:87
- Interpolated log message defeats structured logging src/Elders.Cronus/EventStore/Index/EventToAggregateRootId/RebuildIndex_EventToAggregateRootId_Job.cs:43
- Interpolated log message defeats structured logging src/Elders.Cronus/EventStore/LoggingAggregateRepository.cs:51
- Interpolated log message defeats structured logging src/Elders.Cronus/Migrations/CronusMigrator.cs:35
- Interpolated log message defeats structured logging src/Elders.Cronus/Projections/ProjectionRepository.cs:74
- redundant comment src/Elders.Cronus/Hosting/EventStoreIndicesStartup.cs:57
- redundant comment src/Elders.Cronus/Projections/CronusProjectionBootstrapper.cs:88
- Silent fallback default in catch src/Elders.Cronus/Projections/ProjectionVersions.cs:177
- Silent fallback default in catch src/Elders.Cronus/Projections/Versioning/MarkupInterfaceProjectionVersioningPolicy.cs:13
- Projects may be oversized for their cohesion src/Elders.Cronus/Elders.Cronus.csproj:1
- Pass-through layer src/Elders.Cronus/Discoveries/DiscoveryContext.cs:9
- Dormant codebase
- Rule about [Fixing, New] decided in 2 places
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- Large public API surface
- No explicit versioning
- No SAST REDACTED:2
- Dependabot does not watch github-actions REDACTED:7
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
- Nullable reference types not enabled everywhere
Minor — 2 finding(s)
- doc comments repeat the names src/Elders.Cronus/AtomicAction/AggregateStateFirstLevelConcurrencyException.cs:12
- doc comments repeat the names src/Elders.Cronus.Tests/InMemory/InMemoryEventStorePersister.cs:14
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-22e66a1b06af4337b575a2bfe6e0d842/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-22e66a1b06af4337b575a2bfe6e0d842/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 . | 3 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/Elders.Cronus.sln package --vulnerable --include-transitive --format json | 3 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: 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. | 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-444cab28cd454e308b3fcce4df5a36c4 | 0 | artifacts/raw/osv-scanner.json |