Executive summary
streakphp/streak falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 56 out of 100 and is rated Adequate, and all 18 of its critical findings are security problems.
Production Readiness, at 44, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 6 points. Declaring the library's version and following semantic versioning would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 65.
Fifteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one secret can leak from the build pipeline. Pinning each tool to an exact version, setting a waiting period for automatic updates and limiting the secret to its own step would close these risks. The unsafe setting in infrastructure or container files needs changing to safe values.
The product code is 9,791 lines, about €33,000 to rebuild.
If Production Readiness rose from 44 to 70, the lowest score rated Strong, the score would rise from 56 to about 65.
Rebuild cost: about €33,000 · Estimate
| Cost to rebuild | €11,000 to €56,000, for 185 to 586 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.8 at a score of 56. 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: 9,791 lines of product code |
| 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: which parts of the code depend on which
| uses → | 1 Domain.Event.Subscription.Repository | 2 Infrastructure.Domain | 3 Domain.Event.Listener | 4 Domain.EventStore | 5 Domain.Id | 6 Domain.Event | 7 Domain.Event.Sourced | 8 Infrastructure.Domain.Event.Sourced.Subscription.Event | 9 Domain.Entity | 10 Domain.Event.Exception | 11 Domain.Aggregate | 12 Domain.AggregateRoot | 13 Domain | 14 Application.CommandHandler | 15 Application.Sensor | 16 Domain.Command | 17 Domain.Event.Subscription | 18 Domain.Exception | 19 Infrastructure.Domain.AggregateRoot | 20 Infrastructure.Domain.Event.Sourced | 21 Infrastructure.Domain.EventStore | 22 Application | 23 Application.QueryHandler | 24 Domain.Event.Subscription.Exception | 25 Infrastructure.Domain.AggregateRoot.Repository | 26 Infrastructure.Domain.AggregateRoot.Snapshotter | 27 Infrastructure.Domain.Event | 28 Infrastructure.Domain.Event.Sourced.Subscription | 29 Infrastructure.Domain.Event.Subscription | 30 Infrastructure.Domain.Event.Subscription.CommittingSubscription | 31 Infrastructure.Domain.Event.Subscription.DAO.Subscription | 32 Infrastructure.Domain.Testing.AggregateRoot | 33 Infrastructure.Application.CommandBus | 34 Infrastructure.Application.Sensor | 35 Infrastructure.Application.Sensor.CommittingSensor | 36 Infrastructure.Application.Testing.Sensor | 37 Infrastructure.Domain.AggregateRoot.Snapshotter.Storage | 38 Infrastructure.Domain.Event.Subscription.DAO | 39 Infrastructure.Domain.Testing.Listener | 40 Infrastructure.Domain.UnitOfWork |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Domain.Event.Subscription.Repository | ||||||||||||||||||||||||||||||||||||||||
| 2 Infrastructure.Domain | ||||||||||||||||||||||||||||||||||||||||
| 3 Domain.Event.Listener | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 4 Domain.EventStore | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 Domain.Id | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 Domain.Event | 2 | 1 | 1 | 8 | ||||||||||||||||||||||||||||||||||||
| 7 Domain.Event.Sourced | 8 | 5 | ||||||||||||||||||||||||||||||||||||||
| 8 Infrastructure.Domain.Event.Sourced.Subscription.Event | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 9 Domain.Entity | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 Domain.Event.Exception | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 Domain.Aggregate | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Domain.AggregateRoot | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 13 Domain | 1 | 2 | 4 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 14 Application.CommandHandler | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 Application.Sensor | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 Domain.Command | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 Domain.Event.Subscription | 1 | 1 | 5 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 Domain.Exception | 3 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 19 Infrastructure.Domain.AggregateRoot | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Infrastructure.Domain.Event.Sourced | 2 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 21 Infrastructure.Domain.EventStore | 3 | 3 | 7 | 6 | ||||||||||||||||||||||||||||||||||||
| 22 Application | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 Application.QueryHandler | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Domain.Event.Subscription.Exception | 1 | 6 | 5 | |||||||||||||||||||||||||||||||||||||
| 25 Infrastructure.Domain.AggregateRoot.Repository | 1 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 Infrastructure.Domain.AggregateRoot.Snapshotter | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 27 Infrastructure.Domain.Event | 6 | 10 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 28 Infrastructure.Domain.Event.Sourced.Subscription | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 Infrastructure.Domain.Event.Subscription | 1 | 2 | 6 | 11 | 1 | 4 | 6 | |||||||||||||||||||||||||||||||||
| 30 Infrastructure.Domain.Event.Subscription.CommittingSubscription | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 Infrastructure.Domain.Event.Subscription.DAO.Subscription | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 Infrastructure.Domain.Testing.AggregateRoot | 1 | 2 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 Infrastructure.Application.CommandBus | 1 | 7 | 6 | |||||||||||||||||||||||||||||||||||||
| 34 Infrastructure.Application.Sensor | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 Infrastructure.Application.Sensor.CommittingSensor | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 Infrastructure.Application.Testing.Sensor | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 Infrastructure.Domain.AggregateRoot.Snapshotter.Storage | 2 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 38 Infrastructure.Domain.Event.Subscription.DAO | 1 | 1 | 6 | 8 | 2 | 2 | 1 | 4 | ||||||||||||||||||||||||||||||||
| 39 Infrastructure.Domain.Testing.Listener | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 Infrastructure.Domain.UnitOfWork | 4 | 1 | 1 | 1 |
3→6 Domain.Event.Listener uses Domain.Event part of a loop✕
- Connections
- 4 pairs of types, where a type in Domain.Event.Listener uses a type in Domain.Event.
- The types involved
Streak.Domain.Event.Listener.Factory→Streak.Domain.Event.EnvelopeStreak.Domain.Event.Listener.Factory→Streak.Domain.Event.ListenerStreak.Domain.Event.Listener.Filtering→Streak.Domain.Event.StreamStreak.Domain.Event.Listener.Listening→Streak.Domain.Event.Envelope
- Direction
- Domain.Event.Listener uses Domain.Event, so a change to Domain.Event can break Domain.Event.Listener, while a change to Domain.Event.Listener can't break Domain.Event.
- 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.
3→13 Domain.Event.Listener uses Domain part of a loop✕
- Connections
- 4 pairs of types, where a type in Domain.Event.Listener uses a type in Domain.
- The types involved
Streak.Domain.Event.Listener.Id→Streak.Domain.IdStreak.Domain.Event.Listener.Listening→Streak.Domain.EventStreak.Domain.Event.Listener.Resettable→Streak.Domain.ResettableStreak.Domain.Event.Listener.State→Streak.Domain.ValueObject
- Direction
- Domain.Event.Listener uses Domain, so a change to Domain can break Domain.Event.Listener, while a change to Domain.Event.Listener can't break Domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→13 Domain.EventStore uses Domain part of a loop✕
- Connections
- 1 pair of types, where a type in Domain.EventStore uses a type in Domain.
- The types involved
Streak.Domain.EventStore.Filter→Streak.Domain.Id
- Direction
- Domain.EventStore uses Domain, so a change to Domain can break Domain.EventStore, while a change to Domain.EventStore can't break Domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→13 Domain.Id uses Domain part of a loop✕
- Connections
- 1 pair of types, where a type in Domain.Id uses a type in Domain.
- The types involved
Streak.Domain.Id.UUID→Streak.Domain.Id
- Direction
- Domain.Id uses Domain, so a change to Domain can break Domain.Id, while a change to Domain.Id can't break Domain.
- 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.
6→3 Domain.Event uses Domain.Event.Listener✕
- Connections
- 2 pairs of types, where a type in Domain.Event uses a type in Domain.Event.Listener.
- The types involved
Streak.Domain.Event.Listener→Streak.Domain.Event.Listener.IdStreak.Domain.Event.Subscription→Streak.Domain.Event.Listener.Id
- Direction
- Domain.Event uses Domain.Event.Listener, so a change to Domain.Event.Listener can break Domain.Event, while a change to Domain.Event can't break Domain.Event.Listener.
- Position
- Below the diagonal: Domain.Event uses a module listed above it, which is the healthy direction.
6→5 Domain.Event uses Domain.Id✕
- Connections
- 1 pair of types, where a type in Domain.Event uses a type in Domain.Id.
- The types involved
Streak.Domain.Event.Envelope→Streak.Domain.Id.UUID
- Direction
- Domain.Event uses Domain.Id, so a change to Domain.Id can break Domain.Event, while a change to Domain.Event can't break Domain.Id.
- Position
- Below the diagonal: Domain.Event uses a module listed above it, which is the healthy direction.
6→9 Domain.Event uses Domain.Entity part of a loop✕
- Connections
- 1 pair of types, where a type in Domain.Event uses a type in Domain.Entity.
- The types involved
Streak.Domain.Event.EntityEvent→Streak.Domain.Entity.Id
- Direction
- Domain.Event uses Domain.Entity, so a change to Domain.Entity can break Domain.Event, while a change to Domain.Event can't break Domain.Entity.
- 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.
6→13 Domain.Event uses Domain part of a loop✕
- Connections
- 8 pairs of types, where a type in Domain.Event uses a type in Domain.
- The types involved
Streak.Domain.Event.EntityEvent→Streak.Domain.EventStreak.Domain.Event.Envelope→Streak.Domain.EnvelopeStreak.Domain.Event.Envelope→Streak.Domain.EventStreak.Domain.Event.Envelope→Streak.Domain.IdStreak.Domain.Event.Listener→Streak.Domain.IdentifiableStreak.Domain.Event.Picker→Streak.Domain.EventStoreStreak.Domain.Event.Producer→Streak.Domain.IdStreak.Domain.Event.Subscription→Streak.Domain.EventStore
- Direction
- Domain.Event uses Domain, so a change to Domain can break Domain.Event, while a change to Domain.Event can't break Domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→6 Domain.Event.Sourced uses Domain.Event✕
- Connections
- 8 pairs of types, where a type in Domain.Event.Sourced uses a type in Domain.Event.
- The types involved
Streak.Domain.Event.Sourced.AggregateRoot→Streak.Domain.Event.ConsumerStreak.Domain.Event.Sourced.AggregateRoot→Streak.Domain.Event.EnvelopeStreak.Domain.Event.Sourced.AggregateRoot→Streak.Domain.Event.ProducerStreak.Domain.Event.Sourced.AggregateRoot→Streak.Domain.Event.ReplayableStreak.Domain.Event.Sourced.Entity→Streak.Domain.Event.ConsumerStreak.Domain.Event.Sourced.Subscription→Streak.Domain.Event.ProducerStreak.Domain.Event.Sourced.Subscription→Streak.Domain.Event.ReplayableStreak.Domain.Event.Sourced.Subscription→Streak.Domain.Event.Subscription
- Direction
- Domain.Event.Sourced uses Domain.Event, so a change to Domain.Event can break Domain.Event.Sourced, while a change to Domain.Event.Sourced can't break Domain.Event.
- Position
- Below the diagonal: Domain.Event.Sourced uses a module listed above it, which is the healthy direction.
7→13 Domain.Event.Sourced uses Domain part of a loop✕
- Connections
- 5 pairs of types, where a type in Domain.Event.Sourced uses a type in Domain.
- The types involved
Streak.Domain.Event.Sourced.Aggregate→Streak.Domain.AggregateStreak.Domain.Event.Sourced.AggregateRoot→Streak.Domain.AggregateRootStreak.Domain.Event.Sourced.AggregateRoot→Streak.Domain.VersionableStreak.Domain.Event.Sourced.Entity→Streak.Domain.EntityStreak.Domain.Event.Sourced.Subscription→Streak.Domain.Versionable
- Direction
- Domain.Event.Sourced uses Domain, so a change to Domain can break Domain.Event.Sourced, while a change to Domain.Event.Sourced can't break Domain.
- 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→3 Infrastructure.Domain.Event.Sourced.Subscription.Event uses Domain.Event.Listener✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Sourced.Subscription.Event uses a type in Domain.Event.Listener.
- The types involved
Streak.Infrastructure.Domain.Event.Sourced.Subscription.Event.SubscriptionListenersStateChanged→Streak.Domain.Event.Listener.State
- Direction
- Infrastructure.Domain.Event.Sourced.Subscription.Event uses Domain.Event.Listener, so a change to Domain.Event.Listener can break Infrastructure.Domain.Event.Sourced.Subscription.Event, while a change to Infrastructure.Domain.Event.Sourced.Subscription.Event can't break Domain.Event.Listener.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Sourced.Subscription.Event uses a module listed above it, which is the healthy direction.
8→6 Infrastructure.Domain.Event.Sourced.Subscription.Event uses Domain.Event✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Domain.Event.Sourced.Subscription.Event uses a type in Domain.Event.
- The types involved
Streak.Infrastructure.Domain.Event.Sourced.Subscription.Event.SubscriptionIgnoredEvent→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.Sourced.Subscription.Event.SubscriptionListenedToEvent→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.Sourced.Subscription.Event.SubscriptionRestarted→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.Sourced.Subscription.Event.SubscriptionStarted→Streak.Domain.Event.Envelope
- Direction
- Infrastructure.Domain.Event.Sourced.Subscription.Event uses Domain.Event, so a change to Domain.Event can break Infrastructure.Domain.Event.Sourced.Subscription.Event, while a change to Infrastructure.Domain.Event.Sourced.Subscription.Event can't break Domain.Event.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Sourced.Subscription.Event uses a module listed above it, which is the healthy direction.
9→6 Domain.Entity uses Domain.Event✕
- Connections
- 2 pairs of types, where a type in Domain.Entity uses a type in Domain.Event.
- The types involved
Streak.Domain.Entity.EventSourcing→Streak.Domain.Event.EntityEventStreak.Domain.Entity.EventSourcing→Streak.Domain.Event.Envelope
- Direction
- Domain.Entity uses Domain.Event, so a change to Domain.Event can break Domain.Entity, while a change to Domain.Entity can't break Domain.Event.
- Position
- Below the diagonal: Domain.Entity uses a module listed above it, which is the healthy direction.
9→7 Domain.Entity uses Domain.Event.Sourced✕
- Connections
- 2 pairs of types, where a type in Domain.Entity uses a type in Domain.Event.Sourced.
- The types involved
Streak.Domain.Entity.EventSourcing→Streak.Domain.Event.Sourced.AggregateStreak.Domain.Entity.EventSourcing→Streak.Domain.Event.Sourced.AggregateRoot
- Direction
- Domain.Entity uses Domain.Event.Sourced, so a change to Domain.Event.Sourced can break Domain.Entity, while a change to Domain.Entity can't break Domain.Event.Sourced.
- Position
- Below the diagonal: Domain.Entity uses a module listed above it, which is the healthy direction.
9→13 Domain.Entity uses Domain part of a loop✕
- Connections
- 1 pair of types, where a type in Domain.Entity uses a type in Domain.
- The types involved
Streak.Domain.Entity.Id→Streak.Domain.Id
- Direction
- Domain.Entity uses Domain, so a change to Domain can break Domain.Entity, while a change to Domain.Entity can't break Domain.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→6 Domain.Event.Exception uses Domain.Event✕
- Connections
- 5 pairs of types, where a type in Domain.Event.Exception uses a type in Domain.Event.
- The types involved
Streak.Domain.Event.Exception.EventNotSupported→Streak.Domain.Event.EnvelopeStreak.Domain.Event.Exception.InvalidEventGiven→Streak.Domain.Event.EnvelopeStreak.Domain.Event.Exception.NoEventApplyingMethodFound→Streak.Domain.Event.EnvelopeStreak.Domain.Event.Exception.SourcingObjectWithEventFailed→Streak.Domain.Event.EnvelopeStreak.Domain.Event.Exception.TooManyEventApplyingMethodsFound→Streak.Domain.Event.Envelope
- Direction
- Domain.Event.Exception uses Domain.Event, so a change to Domain.Event can break Domain.Event.Exception, while a change to Domain.Event.Exception can't break Domain.Event.
- Position
- Below the diagonal: Domain.Event.Exception uses a module listed above it, which is the healthy direction.
10→7 Domain.Event.Exception uses Domain.Event.Sourced✕
- Connections
- 1 pair of types, where a type in Domain.Event.Exception uses a type in Domain.Event.Sourced.
- The types involved
Streak.Domain.Event.Exception.AggregateAlreadyRegistered→Streak.Domain.Event.Sourced.Aggregate
- Direction
- Domain.Event.Exception uses Domain.Event.Sourced, so a change to Domain.Event.Sourced can break Domain.Event.Exception, while a change to Domain.Event.Exception can't break Domain.Event.Sourced.
- Position
- Below the diagonal: Domain.Event.Exception uses a module listed above it, which is the healthy direction.
11→9 Domain.Aggregate uses Domain.Entity✕
- Connections
- 1 pair of types, where a type in Domain.Aggregate uses a type in Domain.Entity.
- The types involved
Streak.Domain.Aggregate.Id→Streak.Domain.Entity.Id
- Direction
- Domain.Aggregate uses Domain.Entity, so a change to Domain.Entity can break Domain.Aggregate, while a change to Domain.Aggregate can't break Domain.Entity.
- Position
- Below the diagonal: Domain.Aggregate uses a module listed above it, which is the healthy direction.
12→6 Domain.AggregateRoot uses Domain.Event✕
- Connections
- 2 pairs of types, where a type in Domain.AggregateRoot uses a type in Domain.Event.
- The types involved
Streak.Domain.AggregateRoot.EventSourcing→Streak.Domain.Event.EnvelopeStreak.Domain.AggregateRoot.EventSourcing→Streak.Domain.Event.Stream
- Direction
- Domain.AggregateRoot uses Domain.Event, so a change to Domain.Event can break Domain.AggregateRoot, while a change to Domain.AggregateRoot can't break Domain.Event.
- Position
- Below the diagonal: Domain.AggregateRoot uses a module listed above it, which is the healthy direction.
12→11 Domain.AggregateRoot uses Domain.Aggregate✕
- Connections
- 1 pair of types, where a type in Domain.AggregateRoot uses a type in Domain.Aggregate.
- The types involved
Streak.Domain.AggregateRoot.Id→Streak.Domain.Aggregate.Id
- Direction
- Domain.AggregateRoot uses Domain.Aggregate, so a change to Domain.Aggregate can break Domain.AggregateRoot, while a change to Domain.AggregateRoot can't break Domain.Aggregate.
- Position
- Below the diagonal: Domain.AggregateRoot uses a module listed above it, which is the healthy direction.
12→13 Domain.AggregateRoot uses Domain part of a loop✕
- Connections
- 3 pairs of types, where a type in Domain.AggregateRoot uses a type in Domain.
- The types involved
Streak.Domain.AggregateRoot.EventSourcing→Streak.Domain.EventStreak.Domain.AggregateRoot.Factory→Streak.Domain.AggregateRootStreak.Domain.AggregateRoot.Repository→Streak.Domain.AggregateRoot
- Direction
- Domain.AggregateRoot uses Domain, so a change to Domain can break Domain.AggregateRoot, while a change to Domain.AggregateRoot can't break Domain.
- 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→4 Domain uses Domain.EventStore✕
- Connections
- 1 pair of types, where a type in Domain uses a type in Domain.EventStore.
- The types involved
Streak.Domain.EventStore→Streak.Domain.EventStore.Filter
- Direction
- Domain uses Domain.EventStore, so a change to Domain.EventStore can break Domain, while a change to Domain can't break Domain.EventStore.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
13→5 Domain uses Domain.Id✕
- Connections
- 2 pairs of types, where a type in Domain uses a type in Domain.Id.
- The types involved
Streak.Domain.Envelope→Streak.Domain.Id.UUIDStreak.Domain.EventStore→Streak.Domain.Id.UUID
- Direction
- Domain uses Domain.Id, so a change to Domain.Id can break Domain, while a change to Domain can't break Domain.Id.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
13→6 Domain uses Domain.Event✕
- Connections
- 4 pairs of types, where a type in Domain uses a type in Domain.Event.
- The types involved
Streak.Domain.EventBus→Streak.Domain.Event.EnvelopeStreak.Domain.EventBus→Streak.Domain.Event.ListenerStreak.Domain.EventStore→Streak.Domain.Event.EnvelopeStreak.Domain.EventStore→Streak.Domain.Event.Stream
- Direction
- Domain uses Domain.Event, so a change to Domain.Event can break Domain, while a change to Domain can't break Domain.Event.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
13→9 Domain uses Domain.Entity✕
- Connections
- 1 pair of types, where a type in Domain uses a type in Domain.Entity.
- The types involved
Streak.Domain.Entity→Streak.Domain.Entity.Id
- Direction
- Domain uses Domain.Entity, so a change to Domain.Entity can break Domain, while a change to Domain can't break Domain.Entity.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
13→11 Domain uses Domain.Aggregate✕
- Connections
- 1 pair of types, where a type in Domain uses a type in Domain.Aggregate.
- The types involved
Streak.Domain.Aggregate→Streak.Domain.Aggregate.Id
- Direction
- Domain uses Domain.Aggregate, so a change to Domain.Aggregate can break Domain, while a change to Domain can't break Domain.Aggregate.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
13→12 Domain uses Domain.AggregateRoot✕
- Connections
- 1 pair of types, where a type in Domain uses a type in Domain.AggregateRoot.
- The types involved
Streak.Domain.AggregateRoot→Streak.Domain.AggregateRoot.Id
- Direction
- Domain uses Domain.AggregateRoot, so a change to Domain.AggregateRoot can break Domain, while a change to Domain can't break Domain.AggregateRoot.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
14→12 Application.CommandHandler uses Domain.AggregateRoot✕
- Connections
- 1 pair of types, where a type in Application.CommandHandler uses a type in Domain.AggregateRoot.
- The types involved
Streak.Application.CommandHandler.AggregateRootHandler→Streak.Domain.AggregateRoot.Repository
- Direction
- Application.CommandHandler uses Domain.AggregateRoot, so a change to Domain.AggregateRoot can break Application.CommandHandler, while a change to Application.CommandHandler can't break Domain.AggregateRoot.
- Position
- Below the diagonal: Application.CommandHandler uses a module listed above it, which is the healthy direction.
14→13 Application.CommandHandler uses Domain✕
- Connections
- 2 pairs of types, where a type in Application.CommandHandler uses a type in Domain.
- The types involved
Streak.Application.CommandHandler.AggregateRootHandler→Streak.Domain.CommandStreak.Application.CommandHandler.AggregateRootHandler→Streak.Domain.CommandHandler
- Direction
- Application.CommandHandler uses Domain, so a change to Domain can break Application.CommandHandler, while a change to Application.CommandHandler can't break Domain.
- Position
- Below the diagonal: Application.CommandHandler uses a module listed above it, which is the healthy direction.
15→6 Application.Sensor uses Domain.Event✕
- Connections
- 1 pair of types, where a type in Application.Sensor uses a type in Domain.Event.
- The types involved
Streak.Application.Sensor.Processing→Streak.Domain.Event.Envelope
- Direction
- Application.Sensor uses Domain.Event, so a change to Domain.Event can break Application.Sensor, while a change to Application.Sensor can't break Domain.Event.
- Position
- Below the diagonal: Application.Sensor uses a module listed above it, which is the healthy direction.
15→13 Application.Sensor uses Domain✕
- Connections
- 2 pairs of types, where a type in Application.Sensor uses a type in Domain.
- The types involved
Streak.Application.Sensor.Id→Streak.Domain.IdStreak.Application.Sensor.Processing→Streak.Domain.Event
- Direction
- Application.Sensor uses Domain, so a change to Domain can break Application.Sensor, while a change to Application.Sensor can't break Domain.
- Position
- Below the diagonal: Application.Sensor uses a module listed above it, which is the healthy direction.
15→22 Application.Sensor uses Application part of a loop✕
- Connections
- 1 pair of types, where a type in Application.Sensor uses a type in Application.
- The types involved
Streak.Application.Sensor.Factory→Streak.Application.Sensor
- Direction
- Application.Sensor uses Application, so a change to Application can break Application.Sensor, while a change to Application.Sensor can't break Application.
- 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→12 Domain.Command uses Domain.AggregateRoot✕
- Connections
- 1 pair of types, where a type in Domain.Command uses a type in Domain.AggregateRoot.
- The types involved
Streak.Domain.Command.AggregateRootCommand→Streak.Domain.AggregateRoot.Id
- Direction
- Domain.Command uses Domain.AggregateRoot, so a change to Domain.AggregateRoot can break Domain.Command, while a change to Domain.Command can't break Domain.AggregateRoot.
- Position
- Below the diagonal: Domain.Command uses a module listed above it, which is the healthy direction.
16→13 Domain.Command uses Domain✕
- Connections
- 2 pairs of types, where a type in Domain.Command uses a type in Domain.
- The types involved
Streak.Domain.Command.AggregateRootCommand→Streak.Domain.CommandStreak.Domain.Command.Handling→Streak.Domain.Command
- Direction
- Domain.Command uses Domain, so a change to Domain can break Domain.Command, while a change to Domain.Command can't break Domain.
- Position
- Below the diagonal: Domain.Command uses a module listed above it, which is the healthy direction.
17→1 Domain.Event.Subscription uses Domain.Event.Subscription.Repository✕
- Connections
- 1 pair of types, where a type in Domain.Event.Subscription uses a type in Domain.Event.Subscription.Repository.
- The types involved
Streak.Domain.Event.Subscription.Repository→Streak.Domain.Event.Subscription.Repository.Filter
- Direction
- Domain.Event.Subscription uses Domain.Event.Subscription.Repository, so a change to Domain.Event.Subscription.Repository can break Domain.Event.Subscription, while a change to Domain.Event.Subscription can't break Domain.Event.Subscription.Repository.
- Position
- Below the diagonal: Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
17→3 Domain.Event.Subscription uses Domain.Event.Listener✕
- Connections
- 1 pair of types, where a type in Domain.Event.Subscription uses a type in Domain.Event.Listener.
- The types involved
Streak.Domain.Event.Subscription.Repository→Streak.Domain.Event.Listener.Id
- Direction
- Domain.Event.Subscription uses Domain.Event.Listener, so a change to Domain.Event.Listener can break Domain.Event.Subscription, while a change to Domain.Event.Subscription can't break Domain.Event.Listener.
- Position
- Below the diagonal: Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
17→6 Domain.Event.Subscription uses Domain.Event✕
- Connections
- 5 pairs of types, where a type in Domain.Event.Subscription uses a type in Domain.Event.
- The types involved
Streak.Domain.Event.Subscription.Decorator→Streak.Domain.Event.SubscriptionStreak.Domain.Event.Subscription.Exception→Streak.Domain.Event.SubscriptionStreak.Domain.Event.Subscription.Factory→Streak.Domain.Event.ListenerStreak.Domain.Event.Subscription.Factory→Streak.Domain.Event.SubscriptionStreak.Domain.Event.Subscription.Repository→Streak.Domain.Event.Subscription
- Direction
- Domain.Event.Subscription uses Domain.Event, so a change to Domain.Event can break Domain.Event.Subscription, while a change to Domain.Event.Subscription can't break Domain.Event.
- Position
- Below the diagonal: Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
17→13 Domain.Event.Subscription uses Domain✕
- Connections
- 1 pair of types, where a type in Domain.Event.Subscription uses a type in Domain.
- The types involved
Streak.Domain.Event.Subscription.Id→Streak.Domain.Id
- Direction
- Domain.Event.Subscription uses Domain, so a change to Domain can break Domain.Event.Subscription, while a change to Domain.Event.Subscription can't break Domain.
- Position
- Below the diagonal: Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
18→6 Domain.Exception uses Domain.Event✕
- Connections
- 3 pairs of types, where a type in Domain.Exception uses a type in Domain.Event.
- The types involved
Streak.Domain.Exception.EventAlreadyInStore→Streak.Domain.Event.EnvelopeStreak.Domain.Exception.EventMismatched→Streak.Domain.Event.EnvelopeStreak.Domain.Exception.EventNotInStore→Streak.Domain.Event.Envelope
- Direction
- Domain.Exception uses Domain.Event, so a change to Domain.Event can break Domain.Exception, while a change to Domain.Exception can't break Domain.Event.
- Position
- Below the diagonal: Domain.Exception uses a module listed above it, which is the healthy direction.
18→11 Domain.Exception uses Domain.Aggregate✕
- Connections
- 1 pair of types, where a type in Domain.Exception uses a type in Domain.Aggregate.
- The types involved
Streak.Domain.Exception.AggregateNotFound→Streak.Domain.Aggregate.Id
- Direction
- Domain.Exception uses Domain.Aggregate, so a change to Domain.Aggregate can break Domain.Exception, while a change to Domain.Exception can't break Domain.Aggregate.
- Position
- Below the diagonal: Domain.Exception uses a module listed above it, which is the healthy direction.
18→12 Domain.Exception uses Domain.AggregateRoot✕
- Connections
- 1 pair of types, where a type in Domain.Exception uses a type in Domain.AggregateRoot.
- The types involved
Streak.Domain.Exception.InvalidAggregateIdGiven→Streak.Domain.AggregateRoot.Id
- Direction
- Domain.Exception uses Domain.AggregateRoot, so a change to Domain.AggregateRoot can break Domain.Exception, while a change to Domain.Exception can't break Domain.AggregateRoot.
- Position
- Below the diagonal: Domain.Exception uses a module listed above it, which is the healthy direction.
18→13 Domain.Exception uses Domain✕
- Connections
- 6 pairs of types, where a type in Domain.Exception uses a type in Domain.
- The types involved
Streak.Domain.Exception.AggregateAlreadyExists→Streak.Domain.AggregateRootStreak.Domain.Exception.CommandNotSupported→Streak.Domain.CommandStreak.Domain.Exception.ConcurrentWriteDetected→Streak.Domain.IdStreak.Domain.Exception.InvalidAggregateGiven→Streak.Domain.AggregateRootStreak.Domain.Exception.InvalidIdGiven→Streak.Domain.IdStreak.Domain.Exception.QueryNotSupported→Streak.Domain.Query
- Direction
- Domain.Exception uses Domain, so a change to Domain can break Domain.Exception, while a change to Domain.Exception can't break Domain.
- Position
- Below the diagonal: Domain.Exception uses a module listed above it, which is the healthy direction.
19→13 Infrastructure.Domain.AggregateRoot uses Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.AggregateRoot uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Snapshotter→Streak.Domain.AggregateRoot
- Direction
- Infrastructure.Domain.AggregateRoot uses Domain, so a change to Domain can break Infrastructure.Domain.AggregateRoot, while a change to Infrastructure.Domain.AggregateRoot can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot uses a module listed above it, which is the healthy direction.
20→3 Infrastructure.Domain.Event.Sourced uses Domain.Event.Listener✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.Event.Sourced uses a type in Domain.Event.Listener.
- The types involved
Streak.Infrastructure.Domain.Event.Sourced.Subscription→Streak.Domain.Event.Listener.IdStreak.Infrastructure.Domain.Event.Sourced.Subscription→Streak.Domain.Event.Listener.State
- Direction
- Infrastructure.Domain.Event.Sourced uses Domain.Event.Listener, so a change to Domain.Event.Listener can break Infrastructure.Domain.Event.Sourced, while a change to Infrastructure.Domain.Event.Sourced can't break Domain.Event.Listener.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Sourced uses a module listed above it, which is the healthy direction.
20→6 Infrastructure.Domain.Event.Sourced uses Domain.Event✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.Event.Sourced uses a type in Domain.Event.
- The types involved
Streak.Infrastructure.Domain.Event.Sourced.Subscription→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.Sourced.Subscription→Streak.Domain.Event.ListenerStreak.Infrastructure.Domain.Event.Sourced.Subscription→Streak.Domain.Event.Stream
- Direction
- Infrastructure.Domain.Event.Sourced uses Domain.Event, so a change to Domain.Event can break Infrastructure.Domain.Event.Sourced, while a change to Infrastructure.Domain.Event.Sourced can't break Domain.Event.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Sourced uses a module listed above it, which is the healthy direction.
20→7 Infrastructure.Domain.Event.Sourced uses Domain.Event.Sourced✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Sourced uses a type in Domain.Event.Sourced.
- The types involved
Streak.Infrastructure.Domain.Event.Sourced.Subscription→Streak.Domain.Event.Sourced.Subscription
- Direction
- Infrastructure.Domain.Event.Sourced uses Domain.Event.Sourced, so a change to Domain.Event.Sourced can break Infrastructure.Domain.Event.Sourced, while a change to Infrastructure.Domain.Event.Sourced can't break Domain.Event.Sourced.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Sourced uses a module listed above it, which is the healthy direction.
20→13 Infrastructure.Domain.Event.Sourced uses Domain✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.Event.Sourced uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.Event.Sourced.Subscription→Streak.Domain.ClockStreak.Infrastructure.Domain.Event.Sourced.Subscription→Streak.Domain.EventStreak.Infrastructure.Domain.Event.Sourced.Subscription→Streak.Domain.EventStore
- Direction
- Infrastructure.Domain.Event.Sourced uses Domain, so a change to Domain can break Infrastructure.Domain.Event.Sourced, while a change to Infrastructure.Domain.Event.Sourced can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Sourced uses a module listed above it, which is the healthy direction.
21→4 Infrastructure.Domain.EventStore uses Domain.EventStore✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.EventStore uses a type in Domain.EventStore.
- The types involved
Streak.Infrastructure.Domain.EventStore.DbalPostgresEventStore→Streak.Domain.EventStore.FilterStreak.Infrastructure.Domain.EventStore.InMemoryEventStore→Streak.Domain.EventStore.FilterStreak.Infrastructure.Domain.EventStore.PublishingEventStore→Streak.Domain.EventStore.Filter
- Direction
- Infrastructure.Domain.EventStore uses Domain.EventStore, so a change to Domain.EventStore can break Infrastructure.Domain.EventStore, while a change to Infrastructure.Domain.EventStore can't break Domain.EventStore.
- Position
- Below the diagonal: Infrastructure.Domain.EventStore uses a module listed above it, which is the healthy direction.
21→5 Infrastructure.Domain.EventStore uses Domain.Id✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.EventStore uses a type in Domain.Id.
- The types involved
Streak.Infrastructure.Domain.EventStore.DbalPostgresEventStore→Streak.Domain.Id.UUIDStreak.Infrastructure.Domain.EventStore.InMemoryEventStore→Streak.Domain.Id.UUIDStreak.Infrastructure.Domain.EventStore.PublishingEventStore→Streak.Domain.Id.UUID
- Direction
- Infrastructure.Domain.EventStore uses Domain.Id, so a change to Domain.Id can break Infrastructure.Domain.EventStore, while a change to Infrastructure.Domain.EventStore can't break Domain.Id.
- Position
- Below the diagonal: Infrastructure.Domain.EventStore uses a module listed above it, which is the healthy direction.
21→6 Infrastructure.Domain.EventStore uses Domain.Event✕
- Connections
- 7 pairs of types, where a type in Infrastructure.Domain.EventStore uses a type in Domain.Event.
- The types involved
Streak.Infrastructure.Domain.EventStore.DbalPostgresEventStore→Streak.Domain.Event.ConverterStreak.Infrastructure.Domain.EventStore.DbalPostgresEventStore→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.EventStore.DbalPostgresEventStore→Streak.Domain.Event.StreamStreak.Infrastructure.Domain.EventStore.InMemoryEventStore→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.EventStore.InMemoryEventStore→Streak.Domain.Event.StreamStreak.Infrastructure.Domain.EventStore.PublishingEventStore→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.EventStore.PublishingEventStore→Streak.Domain.Event.Stream
- Direction
- Infrastructure.Domain.EventStore uses Domain.Event, so a change to Domain.Event can break Infrastructure.Domain.EventStore, while a change to Infrastructure.Domain.EventStore can't break Domain.Event.
- Position
- Below the diagonal: Infrastructure.Domain.EventStore uses a module listed above it, which is the healthy direction.
21→13 Infrastructure.Domain.EventStore uses Domain✕
- Connections
- 6 pairs of types, where a type in Infrastructure.Domain.EventStore uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.EventStore.DbalPostgresEventStore→Streak.Domain.EventStoreStreak.Infrastructure.Domain.EventStore.DbalPostgresEventStore→Streak.Domain.IdStreak.Infrastructure.Domain.EventStore.InMemoryEventStore→Streak.Domain.EventStoreStreak.Infrastructure.Domain.EventStore.InMemoryEventStore→Streak.Domain.IdStreak.Infrastructure.Domain.EventStore.PublishingEventStore→Streak.Domain.EventBusStreak.Infrastructure.Domain.EventStore.PublishingEventStore→Streak.Domain.EventStore
- Direction
- Infrastructure.Domain.EventStore uses Domain, so a change to Domain can break Infrastructure.Domain.EventStore, while a change to Infrastructure.Domain.EventStore can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.EventStore uses a module listed above it, which is the healthy direction.
22→6 Application uses Domain.Event✕
- Connections
- 1 pair of types, where a type in Application uses a type in Domain.Event.
- The types involved
Streak.Application.Sensor→Streak.Domain.Event.Producer
- Direction
- Application uses Domain.Event, so a change to Domain.Event can break Application, while a change to Application can't break Domain.Event.
- Position
- Below the diagonal: Application uses a module listed above it, which is the healthy direction.
22→13 Application uses Domain✕
- Connections
- 2 pairs of types, where a type in Application uses a type in Domain.
- The types involved
Streak.Application.CommandBus→Streak.Domain.CommandStreak.Application.QueryBus→Streak.Domain.Query
- Direction
- Application uses Domain, so a change to Domain can break Application, while a change to Application can't break Domain.
- Position
- Below the diagonal: Application uses a module listed above it, which is the healthy direction.
22→15 Application uses Application.Sensor✕
- Connections
- 1 pair of types, where a type in Application uses a type in Application.Sensor.
- The types involved
Streak.Application.Sensor→Streak.Application.Sensor.Id
- Direction
- Application uses Application.Sensor, so a change to Application.Sensor can break Application, while a change to Application can't break Application.Sensor.
- Position
- Below the diagonal: Application uses a module listed above it, which is the healthy direction.
23→13 Application.QueryHandler uses Domain✕
- Connections
- 2 pairs of types, where a type in Application.QueryHandler uses a type in Domain.
- The types involved
Streak.Application.QueryHandler.EventListenerHandler→Streak.Domain.QueryStreak.Application.QueryHandler.EventListenerHandler→Streak.Domain.QueryHandler
- Direction
- Application.QueryHandler uses Domain, so a change to Domain can break Application.QueryHandler, while a change to Application.QueryHandler can't break Domain.
- Position
- Below the diagonal: Application.QueryHandler uses a module listed above it, which is the healthy direction.
23→17 Application.QueryHandler uses Domain.Event.Subscription✕
- Connections
- 1 pair of types, where a type in Application.QueryHandler uses a type in Domain.Event.Subscription.
- The types involved
Streak.Application.QueryHandler.EventListenerHandler→Streak.Domain.Event.Subscription.Repository
- Direction
- Application.QueryHandler uses Domain.Event.Subscription, so a change to Domain.Event.Subscription can break Application.QueryHandler, while a change to Application.QueryHandler can't break Domain.Event.Subscription.
- Position
- Below the diagonal: Application.QueryHandler uses a module listed above it, which is the healthy direction.
24→3 Domain.Event.Subscription.Exception uses Domain.Event.Listener✕
- Connections
- 1 pair of types, where a type in Domain.Event.Subscription.Exception uses a type in Domain.Event.Listener.
- The types involved
Streak.Domain.Event.Subscription.Exception.ListenerNotFound→Streak.Domain.Event.Listener.Id
- Direction
- Domain.Event.Subscription.Exception uses Domain.Event.Listener, so a change to Domain.Event.Listener can break Domain.Event.Subscription.Exception, while a change to Domain.Event.Subscription.Exception can't break Domain.Event.Listener.
- Position
- Below the diagonal: Domain.Event.Subscription.Exception uses a module listed above it, which is the healthy direction.
24→6 Domain.Event.Subscription.Exception uses Domain.Event✕
- Connections
- 6 pairs of types, where a type in Domain.Event.Subscription.Exception uses a type in Domain.Event.
- The types involved
Streak.Domain.Event.Subscription.Exception.EventIgnored→Streak.Domain.Event.EnvelopeStreak.Domain.Event.Subscription.Exception.SubscriptionAlreadyCompleted→Streak.Domain.Event.SubscriptionStreak.Domain.Event.Subscription.Exception.SubscriptionAlreadyStarted→Streak.Domain.Event.SubscriptionStreak.Domain.Event.Subscription.Exception.SubscriptionNotStartedYet→Streak.Domain.Event.SubscriptionStreak.Domain.Event.Subscription.Exception.SubscriptionPaused→Streak.Domain.Event.SubscriptionStreak.Domain.Event.Subscription.Exception.SubscriptionRestartNotPossible→Streak.Domain.Event.Subscription
- Direction
- Domain.Event.Subscription.Exception uses Domain.Event, so a change to Domain.Event can break Domain.Event.Subscription.Exception, while a change to Domain.Event.Subscription.Exception can't break Domain.Event.
- Position
- Below the diagonal: Domain.Event.Subscription.Exception uses a module listed above it, which is the healthy direction.
24→17 Domain.Event.Subscription.Exception uses Domain.Event.Subscription✕
- Connections
- 5 pairs of types, where a type in Domain.Event.Subscription.Exception uses a type in Domain.Event.Subscription.
- The types involved
Streak.Domain.Event.Subscription.Exception.SubscriptionAlreadyCompleted→Streak.Domain.Event.Subscription.ExceptionStreak.Domain.Event.Subscription.Exception.SubscriptionAlreadyStarted→Streak.Domain.Event.Subscription.ExceptionStreak.Domain.Event.Subscription.Exception.SubscriptionNotStartedYet→Streak.Domain.Event.Subscription.ExceptionStreak.Domain.Event.Subscription.Exception.SubscriptionPaused→Streak.Domain.Event.Subscription.ExceptionStreak.Domain.Event.Subscription.Exception.SubscriptionRestartNotPossible→Streak.Domain.Event.Subscription.Exception
- Direction
- Domain.Event.Subscription.Exception uses Domain.Event.Subscription, so a change to Domain.Event.Subscription can break Domain.Event.Subscription.Exception, while a change to Domain.Event.Subscription.Exception can't break Domain.Event.Subscription.
- Position
- Below the diagonal: Domain.Event.Subscription.Exception uses a module listed above it, which is the healthy direction.
25→2 Infrastructure.Domain.AggregateRoot.Repository uses Infrastructure.Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.AggregateRoot.Repository uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Repository.EventSourcedRepository→Streak.Infrastructure.Domain.UnitOfWork
- Direction
- Infrastructure.Domain.AggregateRoot.Repository uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Domain.AggregateRoot.Repository, while a change to Infrastructure.Domain.AggregateRoot.Repository can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot.Repository uses a module listed above it, which is the healthy direction.
25→12 Infrastructure.Domain.AggregateRoot.Repository uses Domain.AggregateRoot✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.AggregateRoot.Repository uses a type in Domain.AggregateRoot.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Repository.EventSourcedRepository→Streak.Domain.AggregateRoot.FactoryStreak.Infrastructure.Domain.AggregateRoot.Repository.EventSourcedRepository→Streak.Domain.AggregateRoot.IdStreak.Infrastructure.Domain.AggregateRoot.Repository.EventSourcedRepository→Streak.Domain.AggregateRoot.Repository
- Direction
- Infrastructure.Domain.AggregateRoot.Repository uses Domain.AggregateRoot, so a change to Domain.AggregateRoot can break Infrastructure.Domain.AggregateRoot.Repository, while a change to Infrastructure.Domain.AggregateRoot.Repository can't break Domain.AggregateRoot.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot.Repository uses a module listed above it, which is the healthy direction.
25→13 Infrastructure.Domain.AggregateRoot.Repository uses Domain✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.AggregateRoot.Repository uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Repository.EventSourcedRepository→Streak.Domain.AggregateRootStreak.Infrastructure.Domain.AggregateRoot.Repository.EventSourcedRepository→Streak.Domain.EventStore
- Direction
- Infrastructure.Domain.AggregateRoot.Repository uses Domain, so a change to Domain can break Infrastructure.Domain.AggregateRoot.Repository, while a change to Infrastructure.Domain.AggregateRoot.Repository can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot.Repository uses a module listed above it, which is the healthy direction.
25→19 Infrastructure.Domain.AggregateRoot.Repository uses Infrastructure.Domain.AggregateRoot✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.AggregateRoot.Repository uses a type in Infrastructure.Domain.AggregateRoot.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Repository.EventSourcedRepository→Streak.Infrastructure.Domain.AggregateRoot.Snapshotter
- Direction
- Infrastructure.Domain.AggregateRoot.Repository uses Infrastructure.Domain.AggregateRoot, so a change to Infrastructure.Domain.AggregateRoot can break Infrastructure.Domain.AggregateRoot.Repository, while a change to Infrastructure.Domain.AggregateRoot.Repository can't break Infrastructure.Domain.AggregateRoot.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot.Repository uses a module listed above it, which is the healthy direction.
26→2 Infrastructure.Domain.AggregateRoot.Snapshotter uses Infrastructure.Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.AggregateRoot.Snapshotter uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Snapshotter.SnapshottableAggregatesSnapshotter→Streak.Infrastructure.Domain.Serializer
- Direction
- Infrastructure.Domain.AggregateRoot.Snapshotter uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Domain.AggregateRoot.Snapshotter, while a change to Infrastructure.Domain.AggregateRoot.Snapshotter can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot.Snapshotter uses a module listed above it, which is the healthy direction.
26→13 Infrastructure.Domain.AggregateRoot.Snapshotter uses Domain✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.AggregateRoot.Snapshotter uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Snapshotter.NullSnapshotter→Streak.Domain.AggregateRootStreak.Infrastructure.Domain.AggregateRoot.Snapshotter.SnapshottableAggregatesSnapshotter→Streak.Domain.AggregateRootStreak.Infrastructure.Domain.AggregateRoot.Snapshotter.Storage→Streak.Domain.AggregateRoot
- Direction
- Infrastructure.Domain.AggregateRoot.Snapshotter uses Domain, so a change to Domain can break Infrastructure.Domain.AggregateRoot.Snapshotter, while a change to Infrastructure.Domain.AggregateRoot.Snapshotter can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot.Snapshotter uses a module listed above it, which is the healthy direction.
26→19 Infrastructure.Domain.AggregateRoot.Snapshotter uses Infrastructure.Domain.AggregateRoot✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.AggregateRoot.Snapshotter uses a type in Infrastructure.Domain.AggregateRoot.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Snapshotter.NullSnapshotter→Streak.Infrastructure.Domain.AggregateRoot.SnapshotterStreak.Infrastructure.Domain.AggregateRoot.Snapshotter.SnapshottableAggregatesSnapshotter→Streak.Infrastructure.Domain.AggregateRoot.Snapshotter
- Direction
- Infrastructure.Domain.AggregateRoot.Snapshotter uses Infrastructure.Domain.AggregateRoot, so a change to Infrastructure.Domain.AggregateRoot can break Infrastructure.Domain.AggregateRoot.Snapshotter, while a change to Infrastructure.Domain.AggregateRoot.Snapshotter can't break Infrastructure.Domain.AggregateRoot.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot.Snapshotter uses a module listed above it, which is the healthy direction.
27→3 Infrastructure.Domain.Event uses Domain.Event.Listener✕
- Connections
- 6 pairs of types, where a type in Infrastructure.Domain.Event uses a type in Domain.Event.Listener.
- The types involved
Streak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.Event.Listener.CompletableStreak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.Event.Listener.IdStreak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.Event.Listener.ResettableStreak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.Event.Listener.StateStreak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.Event.Listener.StatefulStreak.Infrastructure.Domain.Event.Subscriber→Streak.Domain.Event.Listener.Factory
- Direction
- Infrastructure.Domain.Event uses Domain.Event.Listener, so a change to Domain.Event.Listener can break Infrastructure.Domain.Event, while a change to Infrastructure.Domain.Event can't break Domain.Event.Listener.
- Position
- Below the diagonal: Infrastructure.Domain.Event uses a module listed above it, which is the healthy direction.
27→6 Infrastructure.Domain.Event uses Domain.Event✕
- Connections
- 10 pairs of types, where a type in Infrastructure.Domain.Event uses a type in Domain.Event.
- The types involved
Streak.Infrastructure.Domain.Event.InMemoryStream→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.InMemoryStream→Streak.Domain.Event.StreamStreak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.Event.FiltererStreak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.Event.ListenerStreak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.Event.StreamStreak.Infrastructure.Domain.Event.NullListener→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.NullListener→Streak.Domain.Event.ListenerStreak.Infrastructure.Domain.Event.Subscriber→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.Subscriber→Streak.Domain.Event.Listener
- Direction
- Infrastructure.Domain.Event uses Domain.Event, so a change to Domain.Event can break Infrastructure.Domain.Event, while a change to Infrastructure.Domain.Event can't break Domain.Event.
- Position
- Below the diagonal: Infrastructure.Domain.Event uses a module listed above it, which is the healthy direction.
27→13 Infrastructure.Domain.Event uses Domain✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.Event uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.QueryStreak.Infrastructure.Domain.Event.LoggingListener→Streak.Domain.QueryHandlerStreak.Infrastructure.Domain.Event.Subscriber→Streak.Domain.EventBus
- Direction
- Infrastructure.Domain.Event uses Domain, so a change to Domain can break Infrastructure.Domain.Event, while a change to Infrastructure.Domain.Event can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Event uses a module listed above it, which is the healthy direction.
27→17 Infrastructure.Domain.Event uses Domain.Event.Subscription✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.Event uses a type in Domain.Event.Subscription.
- The types involved
Streak.Infrastructure.Domain.Event.Subscriber→Streak.Domain.Event.Subscription.FactoryStreak.Infrastructure.Domain.Event.Subscriber→Streak.Domain.Event.Subscription.Repository
- Direction
- Infrastructure.Domain.Event uses Domain.Event.Subscription, so a change to Domain.Event.Subscription can break Infrastructure.Domain.Event, while a change to Infrastructure.Domain.Event can't break Domain.Event.Subscription.
- Position
- Below the diagonal: Infrastructure.Domain.Event uses a module listed above it, which is the healthy direction.
28→3 Infrastructure.Domain.Event.Sourced.Subscription uses Domain.Event.Listener✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Sourced.Subscription uses a type in Domain.Event.Listener.
- The types involved
Streak.Infrastructure.Domain.Event.Sourced.Subscription.InMemoryState→Streak.Domain.Event.Listener.State
- Direction
- Infrastructure.Domain.Event.Sourced.Subscription uses Domain.Event.Listener, so a change to Domain.Event.Listener can break Infrastructure.Domain.Event.Sourced.Subscription, while a change to Infrastructure.Domain.Event.Sourced.Subscription can't break Domain.Event.Listener.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Sourced.Subscription uses a module listed above it, which is the healthy direction.
28→6 Infrastructure.Domain.Event.Sourced.Subscription uses Domain.Event✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.Event.Sourced.Subscription uses a type in Domain.Event.
- The types involved
Streak.Infrastructure.Domain.Event.Sourced.Subscription.Factory→Streak.Domain.Event.ListenerStreak.Infrastructure.Domain.Event.Sourced.Subscription.Factory→Streak.Domain.Event.Subscription
- Direction
- Infrastructure.Domain.Event.Sourced.Subscription uses Domain.Event, so a change to Domain.Event can break Infrastructure.Domain.Event.Sourced.Subscription, while a change to Infrastructure.Domain.Event.Sourced.Subscription can't break Domain.Event.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Sourced.Subscription uses a module listed above it, which is the healthy direction.
28→13 Infrastructure.Domain.Event.Sourced.Subscription uses Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Sourced.Subscription uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.Event.Sourced.Subscription.Factory→Streak.Domain.Clock
- Direction
- Infrastructure.Domain.Event.Sourced.Subscription uses Domain, so a change to Domain can break Infrastructure.Domain.Event.Sourced.Subscription, while a change to Infrastructure.Domain.Event.Sourced.Subscription can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Sourced.Subscription uses a module listed above it, which is the healthy direction.
28→17 Infrastructure.Domain.Event.Sourced.Subscription uses Domain.Event.Subscription✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Sourced.Subscription uses a type in Domain.Event.Subscription.
- The types involved
Streak.Infrastructure.Domain.Event.Sourced.Subscription.Factory→Streak.Domain.Event.Subscription.Factory
- Direction
- Infrastructure.Domain.Event.Sourced.Subscription uses Domain.Event.Subscription, so a change to Domain.Event.Subscription can break Infrastructure.Domain.Event.Sourced.Subscription, while a change to Infrastructure.Domain.Event.Sourced.Subscription can't break Domain.Event.Subscription.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Sourced.Subscription uses a module listed above it, which is the healthy direction.
29→1 Infrastructure.Domain.Event.Subscription uses Domain.Event.Subscription.Repository✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Subscription uses a type in Domain.Event.Subscription.Repository.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.EventSourcedRepository→Streak.Domain.Event.Subscription.Repository.Filter
- Direction
- Infrastructure.Domain.Event.Subscription uses Domain.Event.Subscription.Repository, so a change to Domain.Event.Subscription.Repository can break Infrastructure.Domain.Event.Subscription, while a change to Infrastructure.Domain.Event.Subscription can't break Domain.Event.Subscription.Repository.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
29→2 Infrastructure.Domain.Event.Subscription uses Infrastructure.Domain✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.Event.Subscription uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.CommittingSubscription→Streak.Infrastructure.Domain.UnitOfWorkStreak.Infrastructure.Domain.Event.Subscription.EventSourcedRepository→Streak.Infrastructure.Domain.UnitOfWork
- Direction
- Infrastructure.Domain.Event.Subscription uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Domain.Event.Subscription, while a change to Infrastructure.Domain.Event.Subscription can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
29→3 Infrastructure.Domain.Event.Subscription uses Domain.Event.Listener✕
- Connections
- 6 pairs of types, where a type in Infrastructure.Domain.Event.Subscription uses a type in Domain.Event.Listener.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.CommittingSubscription→Streak.Domain.Event.Listener.IdStreak.Infrastructure.Domain.Event.Subscription.DAO→Streak.Domain.Event.Listener.IdStreak.Infrastructure.Domain.Event.Subscription.DbalTransactionalSubscription→Streak.Domain.Event.Listener.IdStreak.Infrastructure.Domain.Event.Subscription.EventSourcedRepository→Streak.Domain.Event.Listener.FactoryStreak.Infrastructure.Domain.Event.Subscription.EventSourcedRepository→Streak.Domain.Event.Listener.IdStreak.Infrastructure.Domain.Event.Subscription.LazyLoadedSubscription→Streak.Domain.Event.Listener.Id
- Direction
- Infrastructure.Domain.Event.Subscription uses Domain.Event.Listener, so a change to Domain.Event.Listener can break Infrastructure.Domain.Event.Subscription, while a change to Infrastructure.Domain.Event.Subscription can't break Domain.Event.Listener.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
29→6 Infrastructure.Domain.Event.Subscription uses Domain.Event✕
- Connections
- 11 pairs of types, where a type in Infrastructure.Domain.Event.Subscription uses a type in Domain.Event.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.CommittingSubscription→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.Subscription.CommittingSubscription→Streak.Domain.Event.ListenerStreak.Infrastructure.Domain.Event.Subscription.CommittingSubscription→Streak.Domain.Event.SubscriptionStreak.Infrastructure.Domain.Event.Subscription.DAO→Streak.Domain.Event.SubscriptionStreak.Infrastructure.Domain.Event.Subscription.DbalTransactionalSubscription→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.Subscription.DbalTransactionalSubscription→Streak.Domain.Event.ListenerStreak.Infrastructure.Domain.Event.Subscription.DbalTransactionalSubscription→Streak.Domain.Event.SubscriptionStreak.Infrastructure.Domain.Event.Subscription.EventSourcedRepository→Streak.Domain.Event.SubscriptionStreak.Infrastructure.Domain.Event.Subscription.LazyLoadedSubscription→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.Subscription.LazyLoadedSubscription→Streak.Domain.Event.ListenerStreak.Infrastructure.Domain.Event.Subscription.LazyLoadedSubscription→Streak.Domain.Event.Subscription
- Direction
- Infrastructure.Domain.Event.Subscription uses Domain.Event, so a change to Domain.Event can break Infrastructure.Domain.Event.Subscription, while a change to Infrastructure.Domain.Event.Subscription can't break Domain.Event.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
29→7 Infrastructure.Domain.Event.Subscription uses Domain.Event.Sourced✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Subscription uses a type in Domain.Event.Sourced.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.EventSourcedRepository→Streak.Domain.Event.Sourced.Subscription
- Direction
- Infrastructure.Domain.Event.Subscription uses Domain.Event.Sourced, so a change to Domain.Event.Sourced can break Infrastructure.Domain.Event.Subscription, while a change to Infrastructure.Domain.Event.Subscription can't break Domain.Event.Sourced.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
29→13 Infrastructure.Domain.Event.Subscription uses Domain✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Domain.Event.Subscription uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.CommittingSubscription→Streak.Domain.EventStoreStreak.Infrastructure.Domain.Event.Subscription.DbalTransactionalSubscription→Streak.Domain.EventStoreStreak.Infrastructure.Domain.Event.Subscription.EventSourcedRepository→Streak.Domain.EventStoreStreak.Infrastructure.Domain.Event.Subscription.LazyLoadedSubscription→Streak.Domain.EventStore
- Direction
- Infrastructure.Domain.Event.Subscription uses Domain, so a change to Domain can break Infrastructure.Domain.Event.Subscription, while a change to Infrastructure.Domain.Event.Subscription can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
29→17 Infrastructure.Domain.Event.Subscription uses Domain.Event.Subscription✕
- Connections
- 6 pairs of types, where a type in Infrastructure.Domain.Event.Subscription uses a type in Domain.Event.Subscription.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.CommittingSubscription→Streak.Domain.Event.Subscription.DecoratorStreak.Infrastructure.Domain.Event.Subscription.DbalTransactionalSubscription→Streak.Domain.Event.Subscription.DecoratorStreak.Infrastructure.Domain.Event.Subscription.EventSourcedRepository→Streak.Domain.Event.Subscription.FactoryStreak.Infrastructure.Domain.Event.Subscription.EventSourcedRepository→Streak.Domain.Event.Subscription.RepositoryStreak.Infrastructure.Domain.Event.Subscription.LazyLoadedSubscription→Streak.Domain.Event.Subscription.DecoratorStreak.Infrastructure.Domain.Event.Subscription.LazyLoadedSubscription→Streak.Domain.Event.Subscription.Repository
- Direction
- Infrastructure.Domain.Event.Subscription uses Domain.Event.Subscription, so a change to Domain.Event.Subscription can break Infrastructure.Domain.Event.Subscription, while a change to Infrastructure.Domain.Event.Subscription can't break Domain.Event.Subscription.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription uses a module listed above it, which is the healthy direction.
30→2 Infrastructure.Domain.Event.Subscription.CommittingSubscription uses Infrastructure.Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Subscription.CommittingSubscription uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.CommittingSubscription.Factory→Streak.Infrastructure.Domain.UnitOfWork
- Direction
- Infrastructure.Domain.Event.Subscription.CommittingSubscription uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Domain.Event.Subscription.CommittingSubscription, while a change to Infrastructure.Domain.Event.Subscription.CommittingSubscription can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.CommittingSubscription uses a module listed above it, which is the healthy direction.
30→6 Infrastructure.Domain.Event.Subscription.CommittingSubscription uses Domain.Event✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.Event.Subscription.CommittingSubscription uses a type in Domain.Event.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.CommittingSubscription.Factory→Streak.Domain.Event.ListenerStreak.Infrastructure.Domain.Event.Subscription.CommittingSubscription.Factory→Streak.Domain.Event.Subscription
- Direction
- Infrastructure.Domain.Event.Subscription.CommittingSubscription uses Domain.Event, so a change to Domain.Event can break Infrastructure.Domain.Event.Subscription.CommittingSubscription, while a change to Infrastructure.Domain.Event.Subscription.CommittingSubscription can't break Domain.Event.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.CommittingSubscription uses a module listed above it, which is the healthy direction.
30→17 Infrastructure.Domain.Event.Subscription.CommittingSubscription uses Domain.Event.Subscription✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Subscription.CommittingSubscription uses a type in Domain.Event.Subscription.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.CommittingSubscription.Factory→Streak.Domain.Event.Subscription.Factory
- Direction
- Infrastructure.Domain.Event.Subscription.CommittingSubscription uses Domain.Event.Subscription, so a change to Domain.Event.Subscription can break Infrastructure.Domain.Event.Subscription.CommittingSubscription, while a change to Infrastructure.Domain.Event.Subscription.CommittingSubscription can't break Domain.Event.Subscription.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.CommittingSubscription uses a module listed above it, which is the healthy direction.
31→6 Infrastructure.Domain.Event.Subscription.DAO.Subscription uses Domain.Event✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.Event.Subscription.DAO.Subscription uses a type in Domain.Event.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.Subscription.Factory→Streak.Domain.Event.ListenerStreak.Infrastructure.Domain.Event.Subscription.DAO.Subscription.Factory→Streak.Domain.Event.Subscription
- Direction
- Infrastructure.Domain.Event.Subscription.DAO.Subscription uses Domain.Event, so a change to Domain.Event can break Infrastructure.Domain.Event.Subscription.DAO.Subscription, while a change to Infrastructure.Domain.Event.Subscription.DAO.Subscription can't break Domain.Event.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO.Subscription uses a module listed above it, which is the healthy direction.
31→13 Infrastructure.Domain.Event.Subscription.DAO.Subscription uses Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Subscription.DAO.Subscription uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.Subscription.Factory→Streak.Domain.Clock
- Direction
- Infrastructure.Domain.Event.Subscription.DAO.Subscription uses Domain, so a change to Domain can break Infrastructure.Domain.Event.Subscription.DAO.Subscription, while a change to Infrastructure.Domain.Event.Subscription.DAO.Subscription can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO.Subscription uses a module listed above it, which is the healthy direction.
31→17 Infrastructure.Domain.Event.Subscription.DAO.Subscription uses Domain.Event.Subscription✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Subscription.DAO.Subscription uses a type in Domain.Event.Subscription.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.Subscription.Factory→Streak.Domain.Event.Subscription.Factory
- Direction
- Infrastructure.Domain.Event.Subscription.DAO.Subscription uses Domain.Event.Subscription, so a change to Domain.Event.Subscription can break Infrastructure.Domain.Event.Subscription.DAO.Subscription, while a change to Infrastructure.Domain.Event.Subscription.DAO.Subscription can't break Domain.Event.Subscription.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO.Subscription uses a module listed above it, which is the healthy direction.
32→2 Infrastructure.Domain.Testing.AggregateRoot uses Infrastructure.Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Testing.AggregateRoot uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Domain.Testing.AggregateRoot.Scenario→Streak.Infrastructure.Domain.UnitOfWork
- Direction
- Infrastructure.Domain.Testing.AggregateRoot uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Domain.Testing.AggregateRoot, while a change to Infrastructure.Domain.Testing.AggregateRoot can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Testing.AggregateRoot uses a module listed above it, which is the healthy direction.
32→12 Infrastructure.Domain.Testing.AggregateRoot uses Domain.AggregateRoot✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.Testing.AggregateRoot uses a type in Domain.AggregateRoot.
- The types involved
Streak.Infrastructure.Domain.Testing.AggregateRoot.Scenario→Streak.Domain.AggregateRoot.FactoryStreak.Infrastructure.Domain.Testing.AggregateRoot.Scenario→Streak.Domain.AggregateRoot.Id
- Direction
- Infrastructure.Domain.Testing.AggregateRoot uses Domain.AggregateRoot, so a change to Domain.AggregateRoot can break Infrastructure.Domain.Testing.AggregateRoot, while a change to Infrastructure.Domain.Testing.AggregateRoot can't break Domain.AggregateRoot.
- Position
- Below the diagonal: Infrastructure.Domain.Testing.AggregateRoot uses a module listed above it, which is the healthy direction.
32→13 Infrastructure.Domain.Testing.AggregateRoot uses Domain✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.Testing.AggregateRoot uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.Testing.AggregateRoot.Scenario→Streak.Domain.CommandStreak.Infrastructure.Domain.Testing.AggregateRoot.Scenario→Streak.Domain.CommandHandlerStreak.Infrastructure.Domain.Testing.AggregateRoot.Scenario→Streak.Domain.Event
- Direction
- Infrastructure.Domain.Testing.AggregateRoot uses Domain, so a change to Domain can break Infrastructure.Domain.Testing.AggregateRoot, while a change to Infrastructure.Domain.Testing.AggregateRoot can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Testing.AggregateRoot uses a module listed above it, which is the healthy direction.
32→19 Infrastructure.Domain.Testing.AggregateRoot uses Infrastructure.Domain.AggregateRoot✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Testing.AggregateRoot uses a type in Infrastructure.Domain.AggregateRoot.
- The types involved
Streak.Infrastructure.Domain.Testing.AggregateRoot.Scenario→Streak.Infrastructure.Domain.AggregateRoot.Snapshotter
- Direction
- Infrastructure.Domain.Testing.AggregateRoot uses Infrastructure.Domain.AggregateRoot, so a change to Infrastructure.Domain.AggregateRoot can break Infrastructure.Domain.Testing.AggregateRoot, while a change to Infrastructure.Domain.Testing.AggregateRoot can't break Infrastructure.Domain.AggregateRoot.
- Position
- Below the diagonal: Infrastructure.Domain.Testing.AggregateRoot uses a module listed above it, which is the healthy direction.
32→21 Infrastructure.Domain.Testing.AggregateRoot uses Infrastructure.Domain.EventStore✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Testing.AggregateRoot uses a type in Infrastructure.Domain.EventStore.
- The types involved
Streak.Infrastructure.Domain.Testing.AggregateRoot.Scenario→Streak.Infrastructure.Domain.EventStore.InMemoryEventStore
- Direction
- Infrastructure.Domain.Testing.AggregateRoot uses Infrastructure.Domain.EventStore, so a change to Infrastructure.Domain.EventStore can break Infrastructure.Domain.Testing.AggregateRoot, while a change to Infrastructure.Domain.Testing.AggregateRoot can't break Infrastructure.Domain.EventStore.
- Position
- Below the diagonal: Infrastructure.Domain.Testing.AggregateRoot uses a module listed above it, which is the healthy direction.
33→2 Infrastructure.Application.CommandBus uses Infrastructure.Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Application.CommandBus uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Application.CommandBus.CommittingCommandBus→Streak.Infrastructure.Domain.UnitOfWork
- Direction
- Infrastructure.Application.CommandBus uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Application.CommandBus, while a change to Infrastructure.Application.CommandBus can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Application.CommandBus uses a module listed above it, which is the healthy direction.
33→13 Infrastructure.Application.CommandBus uses Domain✕
- Connections
- 7 pairs of types, where a type in Infrastructure.Application.CommandBus uses a type in Domain.
- The types involved
Streak.Infrastructure.Application.CommandBus.CommittingCommandBus→Streak.Domain.CommandStreak.Infrastructure.Application.CommandBus.DbalTransactionalCommandBus→Streak.Domain.CommandStreak.Infrastructure.Application.CommandBus.LockableCommandBus→Streak.Domain.CommandStreak.Infrastructure.Application.CommandBus.NullCommandBus→Streak.Domain.CommandStreak.Infrastructure.Application.CommandBus.RetryingCommandBus→Streak.Domain.CommandStreak.Infrastructure.Application.CommandBus.SynchronousCommandBus→Streak.Domain.CommandStreak.Infrastructure.Application.CommandBus.SynchronousCommandBus→Streak.Domain.CommandHandler
- Direction
- Infrastructure.Application.CommandBus uses Domain, so a change to Domain can break Infrastructure.Application.CommandBus, while a change to Infrastructure.Application.CommandBus can't break Domain.
- Position
- Below the diagonal: Infrastructure.Application.CommandBus uses a module listed above it, which is the healthy direction.
33→22 Infrastructure.Application.CommandBus uses Application✕
- Connections
- 6 pairs of types, where a type in Infrastructure.Application.CommandBus uses a type in Application.
- The types involved
Streak.Infrastructure.Application.CommandBus.CommittingCommandBus→Streak.Application.CommandBusStreak.Infrastructure.Application.CommandBus.DbalTransactionalCommandBus→Streak.Application.CommandBusStreak.Infrastructure.Application.CommandBus.LockableCommandBus→Streak.Application.CommandBusStreak.Infrastructure.Application.CommandBus.NullCommandBus→Streak.Application.CommandBusStreak.Infrastructure.Application.CommandBus.RetryingCommandBus→Streak.Application.CommandBusStreak.Infrastructure.Application.CommandBus.SynchronousCommandBus→Streak.Application.CommandBus
- Direction
- Infrastructure.Application.CommandBus uses Application, so a change to Application can break Infrastructure.Application.CommandBus, while a change to Infrastructure.Application.CommandBus can't break Application.
- Position
- Below the diagonal: Infrastructure.Application.CommandBus uses a module listed above it, which is the healthy direction.
34→2 Infrastructure.Application.Sensor uses Infrastructure.Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Application.Sensor uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Application.Sensor.CommittingSensor→Streak.Infrastructure.Domain.UnitOfWork
- Direction
- Infrastructure.Application.Sensor uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Application.Sensor, while a change to Infrastructure.Application.Sensor can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Application.Sensor uses a module listed above it, which is the healthy direction.
34→15 Infrastructure.Application.Sensor uses Application.Sensor✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Application.Sensor uses a type in Application.Sensor.
- The types involved
Streak.Infrastructure.Application.Sensor.CommittingSensor→Streak.Application.Sensor.IdStreak.Infrastructure.Application.Sensor.LoggingSensor→Streak.Application.Sensor.Id
- Direction
- Infrastructure.Application.Sensor uses Application.Sensor, so a change to Application.Sensor can break Infrastructure.Application.Sensor, while a change to Infrastructure.Application.Sensor can't break Application.Sensor.
- Position
- Below the diagonal: Infrastructure.Application.Sensor uses a module listed above it, which is the healthy direction.
34→22 Infrastructure.Application.Sensor uses Application✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Application.Sensor uses a type in Application.
- The types involved
Streak.Infrastructure.Application.Sensor.CommittingSensor→Streak.Application.SensorStreak.Infrastructure.Application.Sensor.LoggingSensor→Streak.Application.Sensor
- Direction
- Infrastructure.Application.Sensor uses Application, so a change to Application can break Infrastructure.Application.Sensor, while a change to Infrastructure.Application.Sensor can't break Application.
- Position
- Below the diagonal: Infrastructure.Application.Sensor uses a module listed above it, which is the healthy direction.
35→2 Infrastructure.Application.Sensor.CommittingSensor uses Infrastructure.Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Application.Sensor.CommittingSensor uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Application.Sensor.CommittingSensor.Factory→Streak.Infrastructure.Domain.UnitOfWork
- Direction
- Infrastructure.Application.Sensor.CommittingSensor uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Application.Sensor.CommittingSensor, while a change to Infrastructure.Application.Sensor.CommittingSensor can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Application.Sensor.CommittingSensor uses a module listed above it, which is the healthy direction.
35→15 Infrastructure.Application.Sensor.CommittingSensor uses Application.Sensor✕
- Connections
- 1 pair of types, where a type in Infrastructure.Application.Sensor.CommittingSensor uses a type in Application.Sensor.
- The types involved
Streak.Infrastructure.Application.Sensor.CommittingSensor.Factory→Streak.Application.Sensor.Factory
- Direction
- Infrastructure.Application.Sensor.CommittingSensor uses Application.Sensor, so a change to Application.Sensor can break Infrastructure.Application.Sensor.CommittingSensor, while a change to Infrastructure.Application.Sensor.CommittingSensor can't break Application.Sensor.
- Position
- Below the diagonal: Infrastructure.Application.Sensor.CommittingSensor uses a module listed above it, which is the healthy direction.
35→22 Infrastructure.Application.Sensor.CommittingSensor uses Application✕
- Connections
- 1 pair of types, where a type in Infrastructure.Application.Sensor.CommittingSensor uses a type in Application.
- The types involved
Streak.Infrastructure.Application.Sensor.CommittingSensor.Factory→Streak.Application.Sensor
- Direction
- Infrastructure.Application.Sensor.CommittingSensor uses Application, so a change to Application can break Infrastructure.Application.Sensor.CommittingSensor, while a change to Infrastructure.Application.Sensor.CommittingSensor can't break Application.
- Position
- Below the diagonal: Infrastructure.Application.Sensor.CommittingSensor uses a module listed above it, which is the healthy direction.
36→13 Infrastructure.Application.Testing.Sensor uses Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Application.Testing.Sensor uses a type in Domain.
- The types involved
Streak.Infrastructure.Application.Testing.Sensor.Scenario→Streak.Domain.Event
- Direction
- Infrastructure.Application.Testing.Sensor uses Domain, so a change to Domain can break Infrastructure.Application.Testing.Sensor, while a change to Infrastructure.Application.Testing.Sensor can't break Domain.
- Position
- Below the diagonal: Infrastructure.Application.Testing.Sensor uses a module listed above it, which is the healthy direction.
36→15 Infrastructure.Application.Testing.Sensor uses Application.Sensor✕
- Connections
- 1 pair of types, where a type in Infrastructure.Application.Testing.Sensor uses a type in Application.Sensor.
- The types involved
Streak.Infrastructure.Application.Testing.Sensor.Scenario→Streak.Application.Sensor.Factory
- Direction
- Infrastructure.Application.Testing.Sensor uses Application.Sensor, so a change to Application.Sensor can break Infrastructure.Application.Testing.Sensor, while a change to Infrastructure.Application.Testing.Sensor can't break Application.Sensor.
- Position
- Below the diagonal: Infrastructure.Application.Testing.Sensor uses a module listed above it, which is the healthy direction.
36→22 Infrastructure.Application.Testing.Sensor uses Application✕
- Connections
- 1 pair of types, where a type in Infrastructure.Application.Testing.Sensor uses a type in Application.
- The types involved
Streak.Infrastructure.Application.Testing.Sensor.Scenario→Streak.Application.Sensor
- Direction
- Infrastructure.Application.Testing.Sensor uses Application, so a change to Application can break Infrastructure.Application.Testing.Sensor, while a change to Infrastructure.Application.Testing.Sensor can't break Application.
- Position
- Below the diagonal: Infrastructure.Application.Testing.Sensor uses a module listed above it, which is the healthy direction.
37→2 Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses Infrastructure.Domain✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Snapshotter.Storage.PostgresStorage→Streak.Infrastructure.Domain.ResettableStreak.Infrastructure.Domain.AggregateRoot.Snapshotter.Storage.RedisStorage→Streak.Infrastructure.Domain.Resettable
- Direction
- Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Domain.AggregateRoot.Snapshotter.Storage, while a change to Infrastructure.Domain.AggregateRoot.Snapshotter.Storage can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses a module listed above it, which is the healthy direction.
37→13 Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses Domain✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Snapshotter.Storage.InMemoryStorage→Streak.Domain.AggregateRootStreak.Infrastructure.Domain.AggregateRoot.Snapshotter.Storage.PostgresStorage→Streak.Domain.AggregateRootStreak.Infrastructure.Domain.AggregateRoot.Snapshotter.Storage.RedisStorage→Streak.Domain.AggregateRoot
- Direction
- Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses Domain, so a change to Domain can break Infrastructure.Domain.AggregateRoot.Snapshotter.Storage, while a change to Infrastructure.Domain.AggregateRoot.Snapshotter.Storage can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses a module listed above it, which is the healthy direction.
37→26 Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses Infrastructure.Domain.AggregateRoot.Snapshotter✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses a type in Infrastructure.Domain.AggregateRoot.Snapshotter.
- The types involved
Streak.Infrastructure.Domain.AggregateRoot.Snapshotter.Storage.InMemoryStorage→Streak.Infrastructure.Domain.AggregateRoot.Snapshotter.StorageStreak.Infrastructure.Domain.AggregateRoot.Snapshotter.Storage.PostgresStorage→Streak.Infrastructure.Domain.AggregateRoot.Snapshotter.StorageStreak.Infrastructure.Domain.AggregateRoot.Snapshotter.Storage.RedisStorage→Streak.Infrastructure.Domain.AggregateRoot.Snapshotter.Storage
- Direction
- Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses Infrastructure.Domain.AggregateRoot.Snapshotter, so a change to Infrastructure.Domain.AggregateRoot.Snapshotter can break Infrastructure.Domain.AggregateRoot.Snapshotter.Storage, while a change to Infrastructure.Domain.AggregateRoot.Snapshotter.Storage can't break Infrastructure.Domain.AggregateRoot.Snapshotter.
- Position
- Below the diagonal: Infrastructure.Domain.AggregateRoot.Snapshotter.Storage uses a module listed above it, which is the healthy direction.
38→1 Infrastructure.Domain.Event.Subscription.DAO uses Domain.Event.Subscription.Repository✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Subscription.DAO uses a type in Domain.Event.Subscription.Repository.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.DAORepository→Streak.Domain.Event.Subscription.Repository.Filter
- Direction
- Infrastructure.Domain.Event.Subscription.DAO uses Domain.Event.Subscription.Repository, so a change to Domain.Event.Subscription.Repository can break Infrastructure.Domain.Event.Subscription.DAO, while a change to Infrastructure.Domain.Event.Subscription.DAO can't break Domain.Event.Subscription.Repository.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO uses a module listed above it, which is the healthy direction.
38→2 Infrastructure.Domain.Event.Subscription.DAO uses Infrastructure.Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Subscription.DAO uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.DAORepository→Streak.Infrastructure.Domain.UnitOfWork
- Direction
- Infrastructure.Domain.Event.Subscription.DAO uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Domain.Event.Subscription.DAO, while a change to Infrastructure.Domain.Event.Subscription.DAO can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO uses a module listed above it, which is the healthy direction.
38→3 Infrastructure.Domain.Event.Subscription.DAO uses Domain.Event.Listener✕
- Connections
- 6 pairs of types, where a type in Infrastructure.Domain.Event.Subscription.DAO uses a type in Domain.Event.Listener.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.DAORepository→Streak.Domain.Event.Listener.IdStreak.Infrastructure.Domain.Event.Subscription.DAO.DbalPostgresDAO→Streak.Domain.Event.Listener.FactoryStreak.Infrastructure.Domain.Event.Subscription.DAO.DbalPostgresDAO→Streak.Domain.Event.Listener.IdStreak.Infrastructure.Domain.Event.Subscription.DAO.IdentityMappingDao→Streak.Domain.Event.Listener.IdStreak.Infrastructure.Domain.Event.Subscription.DAO.InMemoryDAO→Streak.Domain.Event.Listener.IdStreak.Infrastructure.Domain.Event.Subscription.DAO.Subscription→Streak.Domain.Event.Listener.Id
- Direction
- Infrastructure.Domain.Event.Subscription.DAO uses Domain.Event.Listener, so a change to Domain.Event.Listener can break Infrastructure.Domain.Event.Subscription.DAO, while a change to Infrastructure.Domain.Event.Subscription.DAO can't break Domain.Event.Listener.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO uses a module listed above it, which is the healthy direction.
38→6 Infrastructure.Domain.Event.Subscription.DAO uses Domain.Event✕
- Connections
- 8 pairs of types, where a type in Infrastructure.Domain.Event.Subscription.DAO uses a type in Domain.Event.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.DAORepository→Streak.Domain.Event.SubscriptionStreak.Infrastructure.Domain.Event.Subscription.DAO.DbalPostgresDAO→Streak.Domain.Event.ConverterStreak.Infrastructure.Domain.Event.Subscription.DAO.DbalPostgresDAO→Streak.Domain.Event.SubscriptionStreak.Infrastructure.Domain.Event.Subscription.DAO.IdentityMappingDao→Streak.Domain.Event.SubscriptionStreak.Infrastructure.Domain.Event.Subscription.DAO.InMemoryDAO→Streak.Domain.Event.SubscriptionStreak.Infrastructure.Domain.Event.Subscription.DAO.Subscription→Streak.Domain.Event.EnvelopeStreak.Infrastructure.Domain.Event.Subscription.DAO.Subscription→Streak.Domain.Event.ListenerStreak.Infrastructure.Domain.Event.Subscription.DAO.Subscription→Streak.Domain.Event.Subscription
- Direction
- Infrastructure.Domain.Event.Subscription.DAO uses Domain.Event, so a change to Domain.Event can break Infrastructure.Domain.Event.Subscription.DAO, while a change to Infrastructure.Domain.Event.Subscription.DAO can't break Domain.Event.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO uses a module listed above it, which is the healthy direction.
38→13 Infrastructure.Domain.Event.Subscription.DAO uses Domain✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.Event.Subscription.DAO uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.Subscription→Streak.Domain.ClockStreak.Infrastructure.Domain.Event.Subscription.DAO.Subscription→Streak.Domain.EventStore
- Direction
- Infrastructure.Domain.Event.Subscription.DAO uses Domain, so a change to Domain can break Infrastructure.Domain.Event.Subscription.DAO, while a change to Infrastructure.Domain.Event.Subscription.DAO can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO uses a module listed above it, which is the healthy direction.
38→17 Infrastructure.Domain.Event.Subscription.DAO uses Domain.Event.Subscription✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Domain.Event.Subscription.DAO uses a type in Domain.Event.Subscription.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.DAORepository→Streak.Domain.Event.Subscription.RepositoryStreak.Infrastructure.Domain.Event.Subscription.DAO.DbalPostgresDAO→Streak.Domain.Event.Subscription.Factory
- Direction
- Infrastructure.Domain.Event.Subscription.DAO uses Domain.Event.Subscription, so a change to Domain.Event.Subscription can break Infrastructure.Domain.Event.Subscription.DAO, while a change to Infrastructure.Domain.Event.Subscription.DAO can't break Domain.Event.Subscription.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO uses a module listed above it, which is the healthy direction.
38→28 Infrastructure.Domain.Event.Subscription.DAO uses Infrastructure.Domain.Event.Sourced.Subscription✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Event.Subscription.DAO uses a type in Infrastructure.Domain.Event.Sourced.Subscription.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.Subscription→Streak.Infrastructure.Domain.Event.Sourced.Subscription.InMemoryState
- Direction
- Infrastructure.Domain.Event.Subscription.DAO uses Infrastructure.Domain.Event.Sourced.Subscription, so a change to Infrastructure.Domain.Event.Sourced.Subscription can break Infrastructure.Domain.Event.Subscription.DAO, while a change to Infrastructure.Domain.Event.Subscription.DAO can't break Infrastructure.Domain.Event.Sourced.Subscription.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO uses a module listed above it, which is the healthy direction.
38→29 Infrastructure.Domain.Event.Subscription.DAO uses Infrastructure.Domain.Event.Subscription✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Domain.Event.Subscription.DAO uses a type in Infrastructure.Domain.Event.Subscription.
- The types involved
Streak.Infrastructure.Domain.Event.Subscription.DAO.DAORepository→Streak.Infrastructure.Domain.Event.Subscription.DAOStreak.Infrastructure.Domain.Event.Subscription.DAO.DbalPostgresDAO→Streak.Infrastructure.Domain.Event.Subscription.DAOStreak.Infrastructure.Domain.Event.Subscription.DAO.IdentityMappingDao→Streak.Infrastructure.Domain.Event.Subscription.DAOStreak.Infrastructure.Domain.Event.Subscription.DAO.InMemoryDAO→Streak.Infrastructure.Domain.Event.Subscription.DAO
- Direction
- Infrastructure.Domain.Event.Subscription.DAO uses Infrastructure.Domain.Event.Subscription, so a change to Infrastructure.Domain.Event.Subscription can break Infrastructure.Domain.Event.Subscription.DAO, while a change to Infrastructure.Domain.Event.Subscription.DAO can't break Infrastructure.Domain.Event.Subscription.
- Position
- Below the diagonal: Infrastructure.Domain.Event.Subscription.DAO uses a module listed above it, which is the healthy direction.
39→3 Infrastructure.Domain.Testing.Listener uses Domain.Event.Listener✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Testing.Listener uses a type in Domain.Event.Listener.
- The types involved
Streak.Infrastructure.Domain.Testing.Listener.Scenario→Streak.Domain.Event.Listener.Factory
- Direction
- Infrastructure.Domain.Testing.Listener uses Domain.Event.Listener, so a change to Domain.Event.Listener can break Infrastructure.Domain.Testing.Listener, while a change to Infrastructure.Domain.Testing.Listener can't break Domain.Event.Listener.
- Position
- Below the diagonal: Infrastructure.Domain.Testing.Listener uses a module listed above it, which is the healthy direction.
39→6 Infrastructure.Domain.Testing.Listener uses Domain.Event✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Testing.Listener uses a type in Domain.Event.
- The types involved
Streak.Infrastructure.Domain.Testing.Listener.Scenario→Streak.Domain.Event.Envelope
- Direction
- Infrastructure.Domain.Testing.Listener uses Domain.Event, so a change to Domain.Event can break Infrastructure.Domain.Testing.Listener, while a change to Infrastructure.Domain.Testing.Listener can't break Domain.Event.
- Position
- Below the diagonal: Infrastructure.Domain.Testing.Listener uses a module listed above it, which is the healthy direction.
39→13 Infrastructure.Domain.Testing.Listener uses Domain✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Domain.Testing.Listener uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.Testing.Listener.Scenario→Streak.Domain.CommandStreak.Infrastructure.Domain.Testing.Listener.Scenario→Streak.Domain.CommandHandlerStreak.Infrastructure.Domain.Testing.Listener.Scenario→Streak.Domain.Event
- Direction
- Infrastructure.Domain.Testing.Listener uses Domain, so a change to Domain can break Infrastructure.Domain.Testing.Listener, while a change to Infrastructure.Domain.Testing.Listener can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.Testing.Listener uses a module listed above it, which is the healthy direction.
39→22 Infrastructure.Domain.Testing.Listener uses Application✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Testing.Listener uses a type in Application.
- The types involved
Streak.Infrastructure.Domain.Testing.Listener.Scenario→Streak.Application.CommandBus
- Direction
- Infrastructure.Domain.Testing.Listener uses Application, so a change to Application can break Infrastructure.Domain.Testing.Listener, while a change to Infrastructure.Domain.Testing.Listener can't break Application.
- Position
- Below the diagonal: Infrastructure.Domain.Testing.Listener uses a module listed above it, which is the healthy direction.
40→2 Infrastructure.Domain.UnitOfWork uses Infrastructure.Domain✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Domain.UnitOfWork uses a type in Infrastructure.Domain.
- The types involved
Streak.Infrastructure.Domain.UnitOfWork.CompositeUnitOfWork→Streak.Infrastructure.Domain.UnitOfWorkStreak.Infrastructure.Domain.UnitOfWork.EventStoreUnitOfWork→Streak.Infrastructure.Domain.UnitOfWorkStreak.Infrastructure.Domain.UnitOfWork.SnapshottingUnitOfWork→Streak.Infrastructure.Domain.UnitOfWorkStreak.Infrastructure.Domain.UnitOfWork.SubscriptionDAOUnitOfWork→Streak.Infrastructure.Domain.UnitOfWork
- Direction
- Infrastructure.Domain.UnitOfWork uses Infrastructure.Domain, so a change to Infrastructure.Domain can break Infrastructure.Domain.UnitOfWork, while a change to Infrastructure.Domain.UnitOfWork can't break Infrastructure.Domain.
- Position
- Below the diagonal: Infrastructure.Domain.UnitOfWork uses a module listed above it, which is the healthy direction.
40→13 Infrastructure.Domain.UnitOfWork uses Domain✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.UnitOfWork uses a type in Domain.
- The types involved
Streak.Infrastructure.Domain.UnitOfWork.EventStoreUnitOfWork→Streak.Domain.EventStore
- Direction
- Infrastructure.Domain.UnitOfWork uses Domain, so a change to Domain can break Infrastructure.Domain.UnitOfWork, while a change to Infrastructure.Domain.UnitOfWork can't break Domain.
- Position
- Below the diagonal: Infrastructure.Domain.UnitOfWork uses a module listed above it, which is the healthy direction.
40→19 Infrastructure.Domain.UnitOfWork uses Infrastructure.Domain.AggregateRoot✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.UnitOfWork uses a type in Infrastructure.Domain.AggregateRoot.
- The types involved
Streak.Infrastructure.Domain.UnitOfWork.SnapshottingUnitOfWork→Streak.Infrastructure.Domain.AggregateRoot.Snapshotter
- Direction
- Infrastructure.Domain.UnitOfWork uses Infrastructure.Domain.AggregateRoot, so a change to Infrastructure.Domain.AggregateRoot can break Infrastructure.Domain.UnitOfWork, while a change to Infrastructure.Domain.UnitOfWork can't break Infrastructure.Domain.AggregateRoot.
- Position
- Below the diagonal: Infrastructure.Domain.UnitOfWork uses a module listed above it, which is the healthy direction.
40→29 Infrastructure.Domain.UnitOfWork uses Infrastructure.Domain.Event.Subscription✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.UnitOfWork uses a type in Infrastructure.Domain.Event.Subscription.
- The types involved
Streak.Infrastructure.Domain.UnitOfWork.SubscriptionDAOUnitOfWork→Streak.Infrastructure.Domain.Event.Subscription.DAO
- Direction
- Infrastructure.Domain.UnitOfWork uses Infrastructure.Domain.Event.Subscription, so a change to Infrastructure.Domain.Event.Subscription can break Infrastructure.Domain.UnitOfWork, while a change to Infrastructure.Domain.UnitOfWork can't break Infrastructure.Domain.Event.Subscription.
- Position
- Below the diagonal: Infrastructure.Domain.UnitOfWork 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 17 | High / Critical |
| A02:2025 — Security Misconfiguration | 3 | High / Critical |
Roadmap
Top priorities: Declare the version where the ecosystem expects it, or keep a CHANGELOG with semver release headings, and follow semver for breaking changes; Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with Subscription.php (2), Scenario.php (2), EventSourcedRepository.php (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.6 pts | Low | ADR Quality |
| Declare the version where the ecosystem expects it, or keep a CHANGELOG with semver release headings, and follow semver for breaking changes. | +7.6 pts | Medium | Library API & versioning |
| Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with Subscription.php (2), Scenario.php (2), EventSourcedRepository.php (2). | +5.6 pts | Medium | Knowledge Freshness |
| Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +5.2 pts | Medium | Security & performance tooling |
| 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. | +3.7 pts | Medium | Architecture documentation |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +3.2 pts | Medium | Nullable reference types |
| Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding. | +3.2 pts | Medium | Deployment & Rollback |
| Consider OpenTelemetry tracing/metrics (opentelemetry-php) and a health-check endpoint (Laravel's /up health route or a /health route) for operability. | +1.7 pts | Medium | Observability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/Infrastructure/Domain/Event/InMemoryStream.php | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/Infrastructure/Domain/Event/Sourced/Subscription.php | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/Domain/Event/Sourced/Entity/Helper.php | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/Domain/Command/Handling.php | 7.1 | Mixed | Cognitive Complexity: Handling.handleCommand (cognitive 28) |
| src/Application/Sensor/Processing.php | 7.1 | Mixed | Cyclomatic Complexity: Processing.process (cyclomatic 20) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Domain/Event/Listener/Listening.php | 7.4 | Mixed | Cyclomatic Complexity: Listening.on (cyclomatic 17) |
| src/Infrastructure/Domain/Event/Subscription/DAO/DbalPostgresDAO.php | 7.4 | Mixed | Code Duplication: Duplicated block (9 lines × 3) |
| src/Infrastructure/Domain/Event/Subscription/DAO/Subscription.php | 7.8 | Mixed | Cyclomatic Complexity: Subscription.subscribeTo (cyclomatic 16) |
| src/Domain/Event/Listener/Filtering.php | 7.8 | Mixed | Cognitive Complexity: Filtering.filter (cognitive 17) |
| src/Infrastructure/Domain/Event/Subscriber.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/Domain/Exception/ConcurrentWriteDetected.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/Domain/Event/Replayable.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/Infrastructure/Domain/Event/Converter/NestedObjectConverter.php | 8.5 | Near-clean | Cognitive Complexity: NestedObjectConverter.toArray (cognitive 32) |
| src/Infrastructure/Domain/Event/Subscription/EventSourcedRepository.php | 8.5 | Near-clean | Cognitive Complexity: EventSourcedRepository.all (cognitive 28) |
| src/Domain/Query/Handling.php | 8.5 | Near-clean | Cognitive Complexity: Handling.handleQuery (cognitive 20) |
| src/Infrastructure/Domain/EventStore/InMemoryEventStore.php | 8.5 | Near-clean | Cognitive Complexity: InMemoryEventStore.stream (cognitive 16) |
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 55 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 55 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, 110 of 119 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (codecov.yml) and a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.php), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) 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. You can widen what we reach: optional: produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) 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 — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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. Not scored — 3 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — 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. Not scored — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 142 commit(s) sampled, automation and bot accounts excluded). One of them holds 94% of the history; the other 2 hold 3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API 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. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AX1 Captive dependencies — 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 reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Symfony DependencyInjection, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container streak-php-1 exited (0); runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- GD1 Unfinished & placeholder code — 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 reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — 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 reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — 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 reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — 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 reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — 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 reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- 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").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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".
Dimensions
D1 · Cyclomatic Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DbalPostgresEventStore.select at 24.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with DbalPostgresEventStore.select (cyclomatic 24), Processing.process (cyclomatic 20), Listening.on (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 6 together lifts Cyclomatic Complexity from 9.0 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
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was Processing.process at 52.
What to do
- Bring the 15 bodies over 15 down to 15 or less in Cognitive Complexity — start with Processing.process (cognitive 52), Listening.on (cognitive 34), NestedObjectConverter.toArray (cognitive 32). — 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 15 together lifts Cognitive Complexity from 7.3 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
3 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with Subscription.php, DbalPostgresEventStore.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with DbalPostgresEventStore.php. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
17 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 2 Duplicated block (21 lines × 2) finding(s) in Code Duplication — start with Handling.php (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Near-duplicate member family (4 members, 33 shared lines) finding(s) in Code Duplication — start with Handling.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (59–63 lines × 2) finding(s) in Code Duplication — start with Subscription.php. — One of this dimension's main actionable groups (1 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.
D6 · Cohesion (LCOM4)
0 of 40 classes have LCOM4 above 3.
D9 · Test Distribution
343 test methods: 343 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 343 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
11 deducted task-comment markers across 9791 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 11 TodoComment finding(s) in Explicit Debt — start with DbalPostgresEventStore.php (3), InMemoryStream.php (2), Subscription.php (2). — One of this dimension's main actionable groups (11 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 19 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (2 contexts). Contexts: Domain, Infrastructure.
D26 · Project Cohesion
1 of 1 build units (Composer) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
54 % of calls cross a namespace and 40 % go through an interface, but 42 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — 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)
17 finding(s): 0 critical, 17 high, 0 medium, 0 low. 15 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 15 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (15 issue-level, 0 of them charged here).
D31 · IaC & Container Security
3 finding(s): 0 critical, 1 high, 2 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
28 of 28 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php. Counted over 28 of the 206 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 27 Orphaned file finding(s) in Knowledge Freshness — start with Subscription.php (2), Scenario.php (2), EventSourcedRepository.php (2). — One of this dimension's main actionable groups (27 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with DbalPostgresEventStore.php. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 3 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `ListenerNotFound` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Domain/Event/Subscription/Exception/ListenerNotFound.php:23
- `AggregateNotFound` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Domain/Exception/AggregateNotFound.php:23
- `ConcurrentWriteDetected` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Domain/Exception/ConcurrentWriteDetected.php:23
- `InvalidAggregateIdGiven` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Domain/Exception/InvalidAggregateIdGiven.php:23
- `InvalidIdGiven` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Domain/Exception/InvalidIdGiven.php:23
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- No explicit version was found for the Composer library declared by `composer.json`. This check read a `version` in composer.json, and a CHANGELOG/CHANGES/HISTORY/NEWS/RELEASES file with a semver heading, or release tooling (changesets, release-please, semantic-release, goreleaser, cargo-release, bump2version, standard-version, git-cliff) in the library's directory or at the repository root, or a semver release tag (or a Drupal `8.x-1.2` release tag) in the repository. A version computed where none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes. — composer.json
What to do
- Declare the version where the ecosystem expects it, or keep a CHANGELOG with semver release headings, and follow semver for breaking changes.
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-php) and a health-check endpoint (Laravel's /up health route or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add phpstan or psalm (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 4049 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` 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:2
What to do
- Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — 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
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/Infrastructure/Interfaces/RabbitMQ/SensorConsumer.php:46
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 64% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 89% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 57% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 44% | Weak — gated by P3, P10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 91% | Exemplary | Strongest area. |
| Domain Modelling | 89% | Strong | Solid. |
Unscored — 1 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.
Not evidenced — 2 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
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container streak-php-1 exited (0); runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, 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 a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 3 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; PHP not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed PHP surface was not measured.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- 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 — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- 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
- 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)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): an append-only event-store seam (IEventStore/Append-of-events); 1 PHP aggregate(s) recording domain events (recordThat/apply)
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — not applicable — no HTTP server, API framework or worker entry point was found in the PHP source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- 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.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 62 finding(s)
- TodoComment src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php:270
- TodoComment src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php:281
- TodoComment src/Infrastructure/Domain/Event/InMemoryStream.php:99
- TodoComment src/Infrastructure/Domain/Event/InMemoryStream.php:110
- TodoComment src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php:460
- TodoComment src/Infrastructure/Domain/Event/Subscriber.php:44
- TodoComment src/Infrastructure/Domain/Event/Sourced/Subscription.php:118
- TodoComment src/Infrastructure/Domain/Event/Sourced/Subscription.php:263
- TodoComment src/Domain/Exception/ConcurrentWriteDetected.php:27
- TodoComment src/Domain/Event/Replayable.php:21
- TodoComment src/Domain/Event/Sourced/Entity/Helper.php:107
- Anemic entity: ListenerNotFound src/Domain/Event/Subscription/Exception/ListenerNotFound.php:23
- Anemic entity: AggregateNotFound src/Domain/Exception/AggregateNotFound.php:23
- Anemic entity: ConcurrentWriteDetected src/Domain/Exception/ConcurrentWriteDetected.php:23
- Anemic entity: InvalidAggregateIdGiven src/Domain/Exception/InvalidAggregateIdGiven.php:23
- Anemic entity: InvalidIdGiven src/Domain/Exception/InvalidIdGiven.php:23
- Subscription.subscribeTo (cyclomatic 16) src/Infrastructure/Domain/Event/Sourced/Subscription.php:73
- Subscription.subscribeTo (cyclomatic 16) src/Infrastructure/Domain/Event/Subscription/DAO/Subscription.php:55
- Subscription.subscribeTo (cognitive 18) src/Infrastructure/Domain/Event/Sourced/Subscription.php:73
- Subscription.subscribeTo (cognitive 18) src/Infrastructure/Domain/Event/Subscription/DAO/Subscription.php:55
- TooManyMethods: Subscription src/Infrastructure/Domain/Event/Sourced/Subscription.php:38
- TooManyMethods: DbalPostgresEventStore src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php:31
- REDACTED
- REDACTED
- Duplicated block (21 lines × 2) src/Domain/Command/Handling.php:32
- Duplicated block (21 lines × 2) src/Domain/Command/Handling.php:55
- DbalPostgresEventStore.select (cyclomatic 24) src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php:506
- Processing.process (cyclomatic 20) src/Application/Sensor/Processing.php:48
- Listening.on (cyclomatic 17) src/Domain/Event/Listener/Listening.php:25
- InMemoryStream.filter (cyclomatic 16) src/Infrastructure/Domain/Event/InMemoryStream.php:170
- Processing.process (cognitive 52) src/Application/Sensor/Processing.php:48
- Listening.on (cognitive 34) src/Domain/Event/Listener/Listening.php:25
- NestedObjectConverter.toArray (cognitive 32) src/Infrastructure/Domain/Event/Converter/NestedObjectConverter.php:54
- DbalPostgresEventStore.select (cognitive 32) src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php:506
- Handling.handleCommand (cognitive 28) src/Domain/Command/Handling.php:26
- EventSourcedRepository.all (cognitive 28) src/Infrastructure/Domain/Event/Subscription/EventSourcedRepository.php:93
- Helper.doExtractEventSourcedEntities (cognitive 25) src/Domain/Event/Sourced/Entity/Helper.php:132
- InMemoryStream.filter (cognitive 25) src/Infrastructure/Domain/Event/InMemoryStream.php:170
- DbalPostgresEventStore.add (cognitive 23) src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php:141
- Helper.applyEventByArgumentType (cognitive 20) src/Domain/Event/Sourced/Entity/Helper.php:52
- Handling.handleQuery (cognitive 20) src/Domain/Query/Handling.php:26
- Filtering.filter (cognitive 17) src/Domain/Event/Listener/Filtering.php:25
- InMemoryEventStore.stream (cognitive 16) src/Infrastructure/Domain/EventStore/InMemoryEventStore.php:95
- ClassTooLong: DbalPostgresEventStore src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php:31
- REDACTED
- Near-duplicate member family (4 members, 33 shared lines) src/Domain/Command/Handling.php:28
- Duplicated block (59–63 lines × 2) src/Infrastructure/Domain/Event/Sourced/Subscription.php:98
- Duplicated block (30 lines × 2) src/Domain/Event/Listener/Filtering.php:33
- Duplicated block (19 lines × 2) src/Infrastructure/Domain/Event/Sourced/Subscription.php:75
- Duplicated block (18 lines × 4) src/Domain/Command/Handling.php:60
- Duplicated block (18 lines × 3) src/Application/Sensor/Processing.php:58
- Duplicated block (16 lines × 3) src/Domain/Command/Handling.php:28
- Duplicated block (15 lines × 5) src/Application/Sensor/Processing.php:56
- Duplicated block (15 lines × 2) src/Application/Sensor/Processing.php:68
- Duplicated block (13–14 lines × 2) src/Domain/Event/Listener/Listening.php:78
- Duplicated block (9 lines × 3) src/Infrastructure/Domain/Event/Subscription/DAO/DbalPostgresDAO.php:110
- Duplicated block (7–8 lines × 4) src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php:572
- Duplicated block (7 lines × 2) src/Infrastructure/Domain/Event/Subscription/DAO/DbalPostgresDAO.php:199
- Duplicated block (8 lines × 4) src/Domain/Event/Subscription/Exception/SubscriptionAlreadyCompleted.php:27
- Duplicated block (11 lines × 3) src/Infrastructure/Domain/Event/Sourced/Subscription/Event/SubscriptionIgnoredEvent.php:31
- Duplicated block (5 lines × 2) src/Infrastructure/Domain/Event/Subscription/DAO/DbalPostgresDAO.php:103
- Swallowed exception (caught, then discarded) src/Infrastructure/Interfaces/RabbitMQ/SensorConsumer.php:46
Minor — 39 finding(s)
- Orphaned file src/Infrastructure/Domain/Event/Sourced/Subscription.php:1
- Orphaned file src/Infrastructure/Domain/Event/Subscription/DAO/DbalPostgresDAO.php:1
- Orphaned file src/Infrastructure/Domain/Event/Subscription/DAO/Subscription.php:1
- Orphaned file src/Infrastructure/Domain/Event/InMemoryStream.php:1
- Orphaned file src/Infrastructure/Domain/Testing/Listener/Scenario.php:1
- Orphaned file src/Domain/Event/Sourced/Entity/Helper.php:1
- Orphaned file src/Infrastructure/Domain/Event/Subscription/EventSourcedRepository.php:1
- Orphaned file src/Application/Sensor/Processing.php:1
- Orphaned file src/Infrastructure/Domain/Event/Converter/NestedObjectConverter.php:1
- Orphaned file src/Infrastructure/Domain/AggregateRoot/Snapshotter/Storage/PostgresStorage.php:1
- Orphaned file src/Domain/Event/Envelope.php:1
- Orphaned file src/Infrastructure/Domain/EventStore/InMemoryEventStore.php:1
- Orphaned file src/Domain/AggregateRoot/EventSourcing.php:1
- Orphaned file src/Domain/Event/Listener/Listening.php:1
- Orphaned file src/Infrastructure/Domain/UnitOfWork/EventStoreUnitOfWork.php:1
- Orphaned file src/Infrastructure/Domain/UnitOfWork/SubscriptionDAOUnitOfWork.php:1
- Orphaned file src/Infrastructure/Domain/Event/Subscription/CommittingSubscription.php:1
- Orphaned file src/Infrastructure/Domain/UnitOfWork/SnapshottingUnitOfWork.php:1
- Orphaned file src/Infrastructure/Domain/Testing/AggregateRoot/Scenario.php:1
- Orphaned file src/Infrastructure/Domain/Event/LoggingListener.php:1
- Orphaned file src/Infrastructure/Domain/Event/Sourced/Subscription/InMemoryState.php:1
- Orphaned file src/Infrastructure/Domain/Event/Subscription/DbalTransactionalSubscription.php:1
- Orphaned file src/Infrastructure/Domain/Testing/AggregateRoot/TestCase.php:1
- Orphaned file src/Domain/Command/Handling.php:1
- Orphaned file src/Infrastructure/Domain/Event/Subscription/DAO/IdentityMappingDao.php:1
- No ADRs found
- Projects may be oversized for their cohesion
- High interface indirection
- Scattered collaborators
- Dormant codebase
- Most significant orphaned file src/Infrastructure/Domain/EventStore/DbalPostgresEventStore.php:1
- No ADRs
- No explicit versioning composer.json
- No SAST
- Dependabot does not watch github-actions REDACTED:2
- No rollback/health safety
- PHP static analysis does not check null everywhere
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-c175cff67ecf4a99ae29ebd501f8db86/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-c175cff67ecf4a99ae29ebd501f8db86/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 . | 17 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |