Executive summary
patchlevel/event-sourcing falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 67 out of 100 and is rated Adequate, and 80 of its 82 critical findings are security problems.
Security and Compliance, at 61, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is fixing the eight pipeline jobs with more access than they need, worth about 2 points. Recording design decisions comes next, worth about 3 points.
Forty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-seven secrets can leak from the build pipeline, and four settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Updating the vulnerable packages would fix the package with a known security hole. The two sets of files in separate parts that keep changing together need that dependency made explicit.
The product code is 14,207 lines, about €54,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
Fixed since the last survey: 2 findings
- Secrets (history) · Secret: square-access-token REDACTED
- Documentation (README) · README may be stale
Rebuild cost: about €54,000 · Estimate
| Cost to rebuild | €18,000 to €90,000, for 300 to 952 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 67. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 14,207 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 Clock | 2 Metadata | 3 QueryBus | 4 Schema | 5 Serializer.Normalizer | 6 Serializer.Upcast | 7 Store.Criteria | 8 Store.Header | 9 Subscription | 10 Attribute | 11 Cryptography | 12 Message.Translator | 13 Metadata.AggregateRoot | 14 Metadata.Event | 15 Metadata.Message | 16 Metadata.Subscriber | 17 Snapshot.Adapter | 18 Subscription.Cleanup | 19 Subscription.RetryStrategy | 20 Subscription.Store | 21 Aggregate | 22 Message | 23 Serializer | 24 Subscription.Cleanup.Dbal | 25 Subscription.Subscriber | 26 EventBus | 27 Repository.MessageDecorator | 28 Serializer.Encoder | 29 Snapshot | 30 Message.Serializer | 31 Console | 32 Store | 33 Repository | 34 Subscription.Engine | 35 Subscription.Lookup | 36 CommandBus | 37 CommandBus.Handler | 38 Console.Command | 39 Subscription.Repository | 40 Subscription.Subscriber.ArgumentResolver |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Clock | ||||||||||||||||||||||||||||||||||||||||
| 2 Metadata | ||||||||||||||||||||||||||||||||||||||||
| 3 QueryBus | ||||||||||||||||||||||||||||||||||||||||
| 4 Schema | ||||||||||||||||||||||||||||||||||||||||
| 5 Serializer.Normalizer | ||||||||||||||||||||||||||||||||||||||||
| 6 Serializer.Upcast | ||||||||||||||||||||||||||||||||||||||||
| 7 Store.Criteria | ||||||||||||||||||||||||||||||||||||||||
| 8 Store.Header | ||||||||||||||||||||||||||||||||||||||||
| 9 Subscription | ||||||||||||||||||||||||||||||||||||||||
| 10 Attribute | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 Cryptography | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 Message.Translator | 12 | |||||||||||||||||||||||||||||||||||||||
| 13 Metadata.AggregateRoot | 15 | |||||||||||||||||||||||||||||||||||||||
| 14 Metadata.Event | 7 | |||||||||||||||||||||||||||||||||||||||
| 15 Metadata.Message | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 Metadata.Subscriber | 8 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 Snapshot.Adapter | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Subscription.Cleanup | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 Subscription.RetryStrategy | 4 | |||||||||||||||||||||||||||||||||||||||
| 20 Subscription.Store | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 21 Aggregate | 5 | |||||||||||||||||||||||||||||||||||||||
| 22 Message | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Serializer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Subscription.Cleanup.Dbal | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Subscription.Subscriber | 2 | 6 | ||||||||||||||||||||||||||||||||||||||
| 26 EventBus | 5 | |||||||||||||||||||||||||||||||||||||||
| 27 Repository.MessageDecorator | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 28 Serializer.Encoder | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 Snapshot | 1 | 3 | 5 | |||||||||||||||||||||||||||||||||||||
| 30 Message.Serializer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 Console | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 Store | 2 | 2 | 6 | 4 | 4 | |||||||||||||||||||||||||||||||||||
| 33 Repository | 3 | 11 | 3 | |||||||||||||||||||||||||||||||||||||
| 34 Subscription.Engine | 4 | 1 | 2 | 3 | 2 | 3 | 8 | |||||||||||||||||||||||||||||||||
| 35 Subscription.Lookup | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 36 CommandBus | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 CommandBus.Handler | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 Console.Command | 3 | 1 | 3 | 1 | 3 | 3 | 4 | 5 | 4 | |||||||||||||||||||||||||||||||
| 39 Subscription.Repository | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 40 Subscription.Subscriber.ArgumentResolver | 6 | 1 | 6 | 1 | 1 |
10→9 Attribute uses Subscription✕
- Connections
- 3 pairs of types, where a type in Attribute uses a type in Subscription.
- The types involved
Patchlevel.EventSourcing.Attribute.Processor→Patchlevel.EventSourcing.Subscription.RunModePatchlevel.EventSourcing.Attribute.Projector→Patchlevel.EventSourcing.Subscription.RunModePatchlevel.EventSourcing.Attribute.Subscriber→Patchlevel.EventSourcing.Subscription.RunMode
- Direction
- Attribute uses Subscription, so a change to Subscription can break Attribute, while a change to Attribute can't break Subscription.
- Position
- Below the diagonal: Attribute uses a module listed above it, which is the healthy direction.
11→4 Cryptography uses Schema✕
- Connections
- 2 pairs of types, where a type in Cryptography uses a type in Schema.
- The types involved
Patchlevel.EventSourcing.Cryptography.DoctrineCipherKeyStore→Patchlevel.EventSourcing.Schema.DoctrineSchemaConfiguratorPatchlevel.EventSourcing.Cryptography.ExtensionDoctrineCipherKeyStore→Patchlevel.EventSourcing.Schema.DoctrineSchemaConfigurator
- Direction
- Cryptography uses Schema, so a change to Schema can break Cryptography, while a change to Cryptography can't break Schema.
- Position
- Below the diagonal: Cryptography uses a module listed above it, which is the healthy direction.
12→22 Message.Translator uses Message part of a loop✕
- Connections
- 12 pairs of types, where a type in Message.Translator uses a type in Message.
- The types involved
Patchlevel.EventSourcing.Message.Translator.AggregateToStreamHeaderTranslator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.ChainTranslator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.ClosureMiddleware→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.ExcludeEventTranslator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.ExcludeEventWithHeaderTranslator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.FilterEventTranslator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.IncludeEventTranslator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.IncludeEventWithHeaderTranslator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.RecalculatePlayheadTranslator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.ReplaceEventTranslator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.Translator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Message.Translator.UntilEventTranslator→Patchlevel.EventSourcing.Message.Message
- Direction
- Message.Translator uses Message, so a change to Message can break Message.Translator, while a change to Message.Translator can't break Message.
- 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→2 Metadata.AggregateRoot uses Metadata✕
- Connections
- 15 pairs of types, where a type in Metadata.AggregateRoot uses a type in Metadata.
- The types involved
Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootAlreadyInRegistry→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootClassNotRegistered→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootNameNotRegistered→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.AggregateWithoutMetadataAware→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.ArgumentTypeIsMissing→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.ArgumentTypeIsNotAClass→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.ClassIsNotAnAggregate→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.DuplicateApplyMethod→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.DuplicateEmptyApplyAttribute→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.MissingAggregateIdForStreamName→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.MissingDataSubjectId→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.MixedApplyAttributeUsage→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.MultipleDataSubjectId→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.NoAggregateRoot→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.AggregateRoot.SubjectIdAndPersonalDataConflict→Patchlevel.EventSourcing.Metadata.MetadataException
- Direction
- Metadata.AggregateRoot uses Metadata, so a change to Metadata can break Metadata.AggregateRoot, while a change to Metadata.AggregateRoot can't break Metadata.
- Position
- Below the diagonal: Metadata.AggregateRoot uses a module listed above it, which is the healthy direction.
14→2 Metadata.Event uses Metadata✕
- Connections
- 7 pairs of types, where a type in Metadata.Event uses a type in Metadata.
- The types involved
Patchlevel.EventSourcing.Metadata.Event.ClassIsNotAnEvent→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Event.EventAlreadyInRegistry→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Event.EventClassNotRegistered→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Event.EventNameNotRegistered→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Event.MissingDataSubjectId→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Event.MultipleDataSubjectId→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Event.SubjectIdAndPersonalDataConflict→Patchlevel.EventSourcing.Metadata.MetadataException
- Direction
- Metadata.Event uses Metadata, so a change to Metadata can break Metadata.Event, while a change to Metadata.Event can't break Metadata.
- Position
- Below the diagonal: Metadata.Event uses a module listed above it, which is the healthy direction.
15→2 Metadata.Message uses Metadata✕
- Connections
- 3 pairs of types, where a type in Metadata.Message uses a type in Metadata.
- The types involved
Patchlevel.EventSourcing.Metadata.Message.HeaderAlreadyInRegistry→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Message.HeaderClassNotRegistered→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Message.HeaderNameNotRegistered→Patchlevel.EventSourcing.Metadata.MetadataException
- Direction
- Metadata.Message uses Metadata, so a change to Metadata can break Metadata.Message, while a change to Metadata.Message can't break Metadata.
- Position
- Below the diagonal: Metadata.Message uses a module listed above it, which is the healthy direction.
16→2 Metadata.Subscriber uses Metadata✕
- Connections
- 8 pairs of types, where a type in Metadata.Subscriber uses a type in Metadata.
- The types involved
Patchlevel.EventSourcing.Metadata.Subscriber.ArgumentTypeNotSupported→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Subscriber.ClassIsNotASubscriber→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Subscriber.DuplicateCleanupMethod→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Subscriber.DuplicateFailedMethod→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Subscriber.DuplicateSetupMethod→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Subscriber.DuplicateSubscribeMethod→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Subscriber.DuplicateTeardownMethod→Patchlevel.EventSourcing.Metadata.MetadataExceptionPatchlevel.EventSourcing.Metadata.Subscriber.MixedTeardownAndCleanupMethods→Patchlevel.EventSourcing.Metadata.MetadataException
- Direction
- Metadata.Subscriber uses Metadata, so a change to Metadata can break Metadata.Subscriber, while a change to Metadata.Subscriber can't break Metadata.
- Position
- Below the diagonal: Metadata.Subscriber uses a module listed above it, which is the healthy direction.
16→9 Metadata.Subscriber uses Subscription✕
- Connections
- 1 pair of types, where a type in Metadata.Subscriber uses a type in Subscription.
- The types involved
Patchlevel.EventSourcing.Metadata.Subscriber.SubscriberMetadata→Patchlevel.EventSourcing.Subscription.RunMode
- Direction
- Metadata.Subscriber uses Subscription, so a change to Subscription can break Metadata.Subscriber, while a change to Metadata.Subscriber can't break Subscription.
- Position
- Below the diagonal: Metadata.Subscriber uses a module listed above it, which is the healthy direction.
17→29 Snapshot.Adapter uses Snapshot part of a loop✕
- Connections
- 1 pair of types, where a type in Snapshot.Adapter uses a type in Snapshot.
- The types involved
Patchlevel.EventSourcing.Snapshot.Adapter.SnapshotNotFound→Patchlevel.EventSourcing.Snapshot.SnapshotException
- Direction
- Snapshot.Adapter uses Snapshot, so a change to Snapshot can break Snapshot.Adapter, while a change to Snapshot.Adapter can't break Snapshot.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→9 Subscription.Cleanup uses Subscription✕
- Connections
- 2 pairs of types, where a type in Subscription.Cleanup uses a type in Subscription.
- The types involved
Patchlevel.EventSourcing.Subscription.Cleanup.Cleaner→Patchlevel.EventSourcing.Subscription.SubscriptionPatchlevel.EventSourcing.Subscription.Cleanup.DefaultCleaner→Patchlevel.EventSourcing.Subscription.Subscription
- Direction
- Subscription.Cleanup uses Subscription, so a change to Subscription can break Subscription.Cleanup, while a change to Subscription.Cleanup can't break Subscription.
- Position
- Below the diagonal: Subscription.Cleanup uses a module listed above it, which is the healthy direction.
19→9 Subscription.RetryStrategy uses Subscription✕
- Connections
- 4 pairs of types, where a type in Subscription.RetryStrategy uses a type in Subscription.
- The types involved
Patchlevel.EventSourcing.Subscription.RetryStrategy.ClockBasedRetryStrategy→Patchlevel.EventSourcing.Subscription.SubscriptionPatchlevel.EventSourcing.Subscription.RetryStrategy.ConditionalRetryStrategy→Patchlevel.EventSourcing.Subscription.SubscriptionPatchlevel.EventSourcing.Subscription.RetryStrategy.NoRetryStrategy→Patchlevel.EventSourcing.Subscription.SubscriptionPatchlevel.EventSourcing.Subscription.RetryStrategy.RetryStrategy→Patchlevel.EventSourcing.Subscription.Subscription
- Direction
- Subscription.RetryStrategy uses Subscription, so a change to Subscription can break Subscription.RetryStrategy, while a change to Subscription.RetryStrategy can't break Subscription.
- Position
- Below the diagonal: Subscription.RetryStrategy uses a module listed above it, which is the healthy direction.
20→4 Subscription.Store uses Schema✕
- Connections
- 1 pair of types, where a type in Subscription.Store uses a type in Schema.
- The types involved
Patchlevel.EventSourcing.Subscription.Store.DoctrineSubscriptionStore→Patchlevel.EventSourcing.Schema.DoctrineSchemaConfigurator
- Direction
- Subscription.Store uses Schema, so a change to Schema can break Subscription.Store, while a change to Subscription.Store can't break Schema.
- Position
- Below the diagonal: Subscription.Store uses a module listed above it, which is the healthy direction.
20→9 Subscription.Store uses Subscription✕
- Connections
- 3 pairs of types, where a type in Subscription.Store uses a type in Subscription.
- The types involved
Patchlevel.EventSourcing.Subscription.Store.DoctrineSubscriptionStore→Patchlevel.EventSourcing.Subscription.SubscriptionPatchlevel.EventSourcing.Subscription.Store.InMemorySubscriptionStore→Patchlevel.EventSourcing.Subscription.SubscriptionPatchlevel.EventSourcing.Subscription.Store.SubscriptionStore→Patchlevel.EventSourcing.Subscription.Subscription
- Direction
- Subscription.Store uses Subscription, so a change to Subscription can break Subscription.Store, while a change to Subscription.Store can't break Subscription.
- Position
- Below the diagonal: Subscription.Store uses a module listed above it, which is the healthy direction.
21→13 Aggregate uses Metadata.AggregateRoot✕
- Connections
- 5 pairs of types, where a type in Aggregate uses a type in Metadata.AggregateRoot.
- The types involved
Patchlevel.EventSourcing.Aggregate.AggregateRootMetadataAware→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootMetadataPatchlevel.EventSourcing.Aggregate.AggregateRootMetadataAware→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootMetadataFactoryPatchlevel.EventSourcing.Aggregate.AggregateRootMetadataAwareBehaviour→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootMetadataPatchlevel.EventSourcing.Aggregate.AggregateRootMetadataAwareBehaviour→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootMetadataFactoryPatchlevel.EventSourcing.Aggregate.BasicAggregateRoot→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootMetadata
- Direction
- Aggregate uses Metadata.AggregateRoot, so a change to Metadata.AggregateRoot can break Aggregate, while a change to Aggregate can't break Metadata.AggregateRoot.
- Position
- Below the diagonal: Aggregate uses a module listed above it, which is the healthy direction.
22→12 Message uses Message.Translator✕
- Connections
- 1 pair of types, where a type in Message uses a type in Message.Translator.
- The types involved
Patchlevel.EventSourcing.Message.Pipe→Patchlevel.EventSourcing.Message.Translator.Translator
- Direction
- Message uses Message.Translator, so a change to Message.Translator can break Message, while a change to Message can't break Message.Translator.
- Position
- Below the diagonal: Message uses a module listed above it, which is the healthy direction.
23→14 Serializer uses Metadata.Event✕
- Connections
- 1 pair of types, where a type in Serializer uses a type in Metadata.Event.
- The types involved
Patchlevel.EventSourcing.Serializer.DefaultEventSerializer→Patchlevel.EventSourcing.Metadata.Event.EventRegistry
- Direction
- Serializer uses Metadata.Event, so a change to Metadata.Event can break Serializer, while a change to Serializer can't break Metadata.Event.
- Position
- Below the diagonal: Serializer uses a module listed above it, which is the healthy direction.
23→28 Serializer uses Serializer.Encoder part of a loop✕
- Connections
- 1 pair of types, where a type in Serializer uses a type in Serializer.Encoder.
- The types involved
Patchlevel.EventSourcing.Serializer.DefaultEventSerializer→Patchlevel.EventSourcing.Serializer.Encoder.Encoder
- Direction
- Serializer uses Serializer.Encoder, so a change to Serializer.Encoder can break Serializer, while a change to Serializer can't break Serializer.Encoder.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→18 Subscription.Cleanup.Dbal uses Subscription.Cleanup✕
- Connections
- 1 pair of types, where a type in Subscription.Cleanup.Dbal uses a type in Subscription.Cleanup.
- The types involved
Patchlevel.EventSourcing.Subscription.Cleanup.Dbal.DbalCleanupTaskHandler→Patchlevel.EventSourcing.Subscription.Cleanup.CleanupTaskHandler
- Direction
- Subscription.Cleanup.Dbal uses Subscription.Cleanup, so a change to Subscription.Cleanup can break Subscription.Cleanup.Dbal, while a change to Subscription.Cleanup.Dbal can't break Subscription.Cleanup.
- Position
- Below the diagonal: Subscription.Cleanup.Dbal uses a module listed above it, which is the healthy direction.
25→9 Subscription.Subscriber uses Subscription✕
- Connections
- 2 pairs of types, where a type in Subscription.Subscriber uses a type in Subscription.
- The types involved
Patchlevel.EventSourcing.Subscription.Subscriber.MetadataSubscriberAccessor→Patchlevel.EventSourcing.Subscription.RunModePatchlevel.EventSourcing.Subscription.Subscriber.SubscriberAccessor→Patchlevel.EventSourcing.Subscription.RunMode
- Direction
- Subscription.Subscriber uses Subscription, so a change to Subscription can break Subscription.Subscriber, while a change to Subscription.Subscriber can't break Subscription.
- Position
- Below the diagonal: Subscription.Subscriber uses a module listed above it, which is the healthy direction.
25→16 Subscription.Subscriber uses Metadata.Subscriber✕
- Connections
- 6 pairs of types, where a type in Subscription.Subscriber uses a type in Metadata.Subscriber.
- The types involved
Patchlevel.EventSourcing.Subscription.Subscriber.MetadataSubscriberAccessor→Patchlevel.EventSourcing.Metadata.Subscriber.SubscribeMethodMetadataPatchlevel.EventSourcing.Subscription.Subscriber.MetadataSubscriberAccessor→Patchlevel.EventSourcing.Metadata.Subscriber.SubscriberMetadataPatchlevel.EventSourcing.Subscription.Subscriber.MetadataSubscriberAccessorRepository→Patchlevel.EventSourcing.Metadata.Subscriber.SubscriberMetadataFactoryPatchlevel.EventSourcing.Subscription.Subscriber.SubscriberHelper→Patchlevel.EventSourcing.Metadata.Subscriber.SubscriberMetadataPatchlevel.EventSourcing.Subscription.Subscriber.SubscriberHelper→Patchlevel.EventSourcing.Metadata.Subscriber.SubscriberMetadataFactoryPatchlevel.EventSourcing.Subscription.Subscriber.SubscriberUtil→Patchlevel.EventSourcing.Metadata.Subscriber.SubscriberMetadataFactory
- Direction
- Subscription.Subscriber uses Metadata.Subscriber, so a change to Metadata.Subscriber can break Subscription.Subscriber, while a change to Subscription.Subscriber can't break Metadata.Subscriber.
- Position
- Below the diagonal: Subscription.Subscriber uses a module listed above it, which is the healthy direction.
26→22 EventBus uses Message✕
- Connections
- 5 pairs of types, where a type in EventBus uses a type in Message.
- The types involved
Patchlevel.EventSourcing.EventBus.Consumer→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.EventBus.DefaultConsumer→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.EventBus.DefaultEventBus→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.EventBus.EventBus→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.EventBus.Psr14EventBus→Patchlevel.EventSourcing.Message.Message
- Direction
- EventBus uses Message, so a change to Message can break EventBus, while a change to EventBus can't break Message.
- Position
- Below the diagonal: EventBus uses a module listed above it, which is the healthy direction.
27→14 Repository.MessageDecorator uses Metadata.Event✕
- Connections
- 1 pair of types, where a type in Repository.MessageDecorator uses a type in Metadata.Event.
- The types involved
Patchlevel.EventSourcing.Repository.MessageDecorator.SplitStreamDecorator→Patchlevel.EventSourcing.Metadata.Event.EventMetadataFactory
- Direction
- Repository.MessageDecorator uses Metadata.Event, so a change to Metadata.Event can break Repository.MessageDecorator, while a change to Repository.MessageDecorator can't break Metadata.Event.
- Position
- Below the diagonal: Repository.MessageDecorator uses a module listed above it, which is the healthy direction.
27→22 Repository.MessageDecorator uses Message✕
- Connections
- 3 pairs of types, where a type in Repository.MessageDecorator uses a type in Message.
- The types involved
Patchlevel.EventSourcing.Repository.MessageDecorator.ChainMessageDecorator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Repository.MessageDecorator.MessageDecorator→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Repository.MessageDecorator.SplitStreamDecorator→Patchlevel.EventSourcing.Message.Message
- Direction
- Repository.MessageDecorator uses Message, so a change to Message can break Repository.MessageDecorator, while a change to Repository.MessageDecorator can't break Message.
- Position
- Below the diagonal: Repository.MessageDecorator uses a module listed above it, which is the healthy direction.
28→23 Serializer.Encoder uses Serializer✕
- Connections
- 2 pairs of types, where a type in Serializer.Encoder uses a type in Serializer.
- The types involved
Patchlevel.EventSourcing.Serializer.Encoder.DecodeNotPossible→Patchlevel.EventSourcing.Serializer.SerializeExceptionPatchlevel.EventSourcing.Serializer.Encoder.EncodeNotPossible→Patchlevel.EventSourcing.Serializer.SerializeException
- Direction
- Serializer.Encoder uses Serializer, so a change to Serializer can break Serializer.Encoder, while a change to Serializer.Encoder can't break Serializer.
- Position
- Below the diagonal: Serializer.Encoder uses a module listed above it, which is the healthy direction.
29→13 Snapshot uses Metadata.AggregateRoot✕
- Connections
- 1 pair of types, where a type in Snapshot uses a type in Metadata.AggregateRoot.
- The types involved
Patchlevel.EventSourcing.Snapshot.DefaultSnapshotStore→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootMetadataFactory
- Direction
- Snapshot uses Metadata.AggregateRoot, so a change to Metadata.AggregateRoot can break Snapshot, while a change to Snapshot can't break Metadata.AggregateRoot.
- Position
- Below the diagonal: Snapshot uses a module listed above it, which is the healthy direction.
29→17 Snapshot uses Snapshot.Adapter✕
- Connections
- 3 pairs of types, where a type in Snapshot uses a type in Snapshot.Adapter.
- The types involved
Patchlevel.EventSourcing.Snapshot.AdapterRepository→Patchlevel.EventSourcing.Snapshot.Adapter.SnapshotAdapterPatchlevel.EventSourcing.Snapshot.ArrayAdapterRepository→Patchlevel.EventSourcing.Snapshot.Adapter.SnapshotAdapterPatchlevel.EventSourcing.Snapshot.DefaultSnapshotStore→Patchlevel.EventSourcing.Snapshot.Adapter.SnapshotAdapter
- Direction
- Snapshot uses Snapshot.Adapter, so a change to Snapshot.Adapter can break Snapshot, while a change to Snapshot can't break Snapshot.Adapter.
- Position
- Below the diagonal: Snapshot uses a module listed above it, which is the healthy direction.
29→21 Snapshot uses Aggregate✕
- Connections
- 5 pairs of types, where a type in Snapshot uses a type in Aggregate.
- The types involved
Patchlevel.EventSourcing.Snapshot.DefaultSnapshotStore→Patchlevel.EventSourcing.Aggregate.AggregateRootPatchlevel.EventSourcing.Snapshot.DefaultSnapshotStore→Patchlevel.EventSourcing.Aggregate.AggregateRootIdPatchlevel.EventSourcing.Snapshot.SnapshotNotFound→Patchlevel.EventSourcing.Aggregate.AggregateRootIdPatchlevel.EventSourcing.Snapshot.SnapshotStore→Patchlevel.EventSourcing.Aggregate.AggregateRootPatchlevel.EventSourcing.Snapshot.SnapshotStore→Patchlevel.EventSourcing.Aggregate.AggregateRootId
- Direction
- Snapshot uses Aggregate, so a change to Aggregate can break Snapshot, while a change to Snapshot can't break Aggregate.
- Position
- Below the diagonal: Snapshot uses a module listed above it, which is the healthy direction.
30→15 Message.Serializer uses Metadata.Message✕
- Connections
- 1 pair of types, where a type in Message.Serializer uses a type in Metadata.Message.
- The types involved
Patchlevel.EventSourcing.Message.Serializer.DefaultHeadersSerializer→Patchlevel.EventSourcing.Metadata.Message.MessageHeaderRegistry
- Direction
- Message.Serializer uses Metadata.Message, so a change to Metadata.Message can break Message.Serializer, while a change to Message.Serializer can't break Metadata.Message.
- Position
- Below the diagonal: Message.Serializer uses a module listed above it, which is the healthy direction.
30→28 Message.Serializer uses Serializer.Encoder✕
- Connections
- 1 pair of types, where a type in Message.Serializer uses a type in Serializer.Encoder.
- The types involved
Patchlevel.EventSourcing.Message.Serializer.DefaultHeadersSerializer→Patchlevel.EventSourcing.Serializer.Encoder.Encoder
- Direction
- Message.Serializer uses Serializer.Encoder, so a change to Serializer.Encoder can break Message.Serializer, while a change to Message.Serializer can't break Serializer.Encoder.
- Position
- Below the diagonal: Message.Serializer uses a module listed above it, which is the healthy direction.
31→22 Console uses Message✕
- Connections
- 1 pair of types, where a type in Console uses a type in Message.
- The types involved
Patchlevel.EventSourcing.Console.OutputStyle→Patchlevel.EventSourcing.Message.Message
- Direction
- Console uses Message, so a change to Message can break Console, while a change to Console can't break Message.
- Position
- Below the diagonal: Console uses a module listed above it, which is the healthy direction.
31→23 Console uses Serializer✕
- Connections
- 1 pair of types, where a type in Console uses a type in Serializer.
- The types involved
Patchlevel.EventSourcing.Console.OutputStyle→Patchlevel.EventSourcing.Serializer.EventSerializer
- Direction
- Console uses Serializer, so a change to Serializer can break Console, while a change to Console can't break Serializer.
- Position
- Below the diagonal: Console uses a module listed above it, which is the healthy direction.
31→30 Console uses Message.Serializer✕
- Connections
- 1 pair of types, where a type in Console uses a type in Message.Serializer.
- The types involved
Patchlevel.EventSourcing.Console.OutputStyle→Patchlevel.EventSourcing.Message.Serializer.HeadersSerializer
- Direction
- Console uses Message.Serializer, so a change to Message.Serializer can break Console, while a change to Console can't break Message.Serializer.
- Position
- Below the diagonal: Console uses a module listed above it, which is the healthy direction.
32→4 Store uses Schema✕
- Connections
- 2 pairs of types, where a type in Store uses a type in Schema.
- The types involved
Patchlevel.EventSourcing.Store.DoctrineDbalStore→Patchlevel.EventSourcing.Schema.DoctrineSchemaConfiguratorPatchlevel.EventSourcing.Store.StreamDoctrineDbalStore→Patchlevel.EventSourcing.Schema.DoctrineSchemaConfigurator
- Direction
- Store uses Schema, so a change to Schema can break Store, while a change to Store can't break Schema.
- Position
- Below the diagonal: Store uses a module listed above it, which is the healthy direction.
32→7 Store uses Store.Criteria✕
- Connections
- 2 pairs of types, where a type in Store uses a type in Store.Criteria.
- The types involved
Patchlevel.EventSourcing.Store.DoctrineDbalStore→Patchlevel.EventSourcing.Store.Criteria.CriteriaPatchlevel.EventSourcing.Store.StreamDoctrineDbalStore→Patchlevel.EventSourcing.Store.Criteria.Criteria
- Direction
- Store uses Store.Criteria, so a change to Store.Criteria can break Store, while a change to Store can't break Store.Criteria.
- Position
- Below the diagonal: Store uses a module listed above it, which is the healthy direction.
32→22 Store uses Message✕
- Connections
- 6 pairs of types, where a type in Store uses a type in Message.
- The types involved
Patchlevel.EventSourcing.Store.DoctrineDbalStore→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Store.InMemoryStore→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Store.ReadOnlyStore→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Store.Store→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Store.StreamDoctrineDbalStore→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Store.StreamReadOnlyStore→Patchlevel.EventSourcing.Message.Message
- Direction
- Store uses Message, so a change to Message can break Store, while a change to Store can't break Message.
- Position
- Below the diagonal: Store uses a module listed above it, which is the healthy direction.
32→23 Store uses Serializer✕
- Connections
- 4 pairs of types, where a type in Store uses a type in Serializer.
- The types involved
Patchlevel.EventSourcing.Store.DoctrineDbalStore→Patchlevel.EventSourcing.Serializer.EventSerializerPatchlevel.EventSourcing.Store.DoctrineDbalStoreStream→Patchlevel.EventSourcing.Serializer.EventSerializerPatchlevel.EventSourcing.Store.StreamDoctrineDbalStore→Patchlevel.EventSourcing.Serializer.EventSerializerPatchlevel.EventSourcing.Store.StreamDoctrineDbalStoreStream→Patchlevel.EventSourcing.Serializer.EventSerializer
- Direction
- Store uses Serializer, so a change to Serializer can break Store, while a change to Store can't break Serializer.
- Position
- Below the diagonal: Store uses a module listed above it, which is the healthy direction.
32→30 Store uses Message.Serializer✕
- Connections
- 4 pairs of types, where a type in Store uses a type in Message.Serializer.
- The types involved
Patchlevel.EventSourcing.Store.DoctrineDbalStore→Patchlevel.EventSourcing.Message.Serializer.HeadersSerializerPatchlevel.EventSourcing.Store.DoctrineDbalStoreStream→Patchlevel.EventSourcing.Message.Serializer.HeadersSerializerPatchlevel.EventSourcing.Store.StreamDoctrineDbalStore→Patchlevel.EventSourcing.Message.Serializer.HeadersSerializerPatchlevel.EventSourcing.Store.StreamDoctrineDbalStoreStream→Patchlevel.EventSourcing.Message.Serializer.HeadersSerializer
- Direction
- Store uses Message.Serializer, so a change to Message.Serializer can break Store, while a change to Store can't break Message.Serializer.
- Position
- Below the diagonal: Store uses a module listed above it, which is the healthy direction.
33→13 Repository uses Metadata.AggregateRoot✕
- Connections
- 3 pairs of types, where a type in Repository uses a type in Metadata.AggregateRoot.
- The types involved
Patchlevel.EventSourcing.Repository.DefaultRepository→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootMetadataPatchlevel.EventSourcing.Repository.DefaultRepositoryManager→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootMetadataFactoryPatchlevel.EventSourcing.Repository.DefaultRepositoryManager→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootRegistry
- Direction
- Repository uses Metadata.AggregateRoot, so a change to Metadata.AggregateRoot can break Repository, while a change to Repository can't break Metadata.AggregateRoot.
- Position
- Below the diagonal: Repository uses a module listed above it, which is the healthy direction.
33→21 Repository uses Aggregate✕
- Connections
- 11 pairs of types, where a type in Repository uses a type in Aggregate.
- The types involved
Patchlevel.EventSourcing.Repository.AggregateAlreadyExists→Patchlevel.EventSourcing.Aggregate.AggregateRootIdPatchlevel.EventSourcing.Repository.AggregateDetached→Patchlevel.EventSourcing.Aggregate.AggregateRootIdPatchlevel.EventSourcing.Repository.AggregateNotFound→Patchlevel.EventSourcing.Aggregate.AggregateRootIdPatchlevel.EventSourcing.Repository.AggregateOutdated→Patchlevel.EventSourcing.Aggregate.AggregateRootIdPatchlevel.EventSourcing.Repository.AggregateUnknown→Patchlevel.EventSourcing.Aggregate.AggregateRootIdPatchlevel.EventSourcing.Repository.DefaultRepository→Patchlevel.EventSourcing.Aggregate.AggregateRootPatchlevel.EventSourcing.Repository.DefaultRepository→Patchlevel.EventSourcing.Aggregate.AggregateRootIdPatchlevel.EventSourcing.Repository.PlayheadMismatch→Patchlevel.EventSourcing.Aggregate.AggregateRootIdPatchlevel.EventSourcing.Repository.Repository→Patchlevel.EventSourcing.Aggregate.AggregateRootPatchlevel.EventSourcing.Repository.Repository→Patchlevel.EventSourcing.Aggregate.AggregateRootIdPatchlevel.EventSourcing.Repository.SnapshotRebuildFailed→Patchlevel.EventSourcing.Aggregate.AggregateRootId
- Direction
- Repository uses Aggregate, so a change to Aggregate can break Repository, while a change to Repository can't break Aggregate.
- Position
- Below the diagonal: Repository uses a module listed above it, which is the healthy direction.
33→32 Repository uses Store✕
- Connections
- 3 pairs of types, where a type in Repository uses a type in Store.
- The types involved
Patchlevel.EventSourcing.Repository.DefaultRepository→Patchlevel.EventSourcing.Store.StorePatchlevel.EventSourcing.Repository.DefaultRepository→Patchlevel.EventSourcing.Store.StreamPatchlevel.EventSourcing.Repository.DefaultRepositoryManager→Patchlevel.EventSourcing.Store.Store
- Direction
- Repository uses Store, so a change to Store can break Repository, while a change to Repository can't break Store.
- Position
- Below the diagonal: Repository uses a module listed above it, which is the healthy direction.
34→9 Subscription.Engine uses Subscription✕
- Connections
- 4 pairs of types, where a type in Subscription.Engine uses a type in Subscription.
- The types involved
Patchlevel.EventSourcing.Subscription.Engine.DefaultSubscriptionEngine→Patchlevel.EventSourcing.Subscription.StatusPatchlevel.EventSourcing.Subscription.Engine.DefaultSubscriptionEngine→Patchlevel.EventSourcing.Subscription.SubscriptionPatchlevel.EventSourcing.Subscription.Engine.SubscriptionCollection→Patchlevel.EventSourcing.Subscription.SubscriptionPatchlevel.EventSourcing.Subscription.Engine.SubscriptionManager→Patchlevel.EventSourcing.Subscription.Subscription
- Direction
- Subscription.Engine uses Subscription, so a change to Subscription can break Subscription.Engine, while a change to Subscription.Engine can't break Subscription.
- Position
- Below the diagonal: Subscription.Engine uses a module listed above it, which is the healthy direction.
34→14 Subscription.Engine uses Metadata.Event✕
- Connections
- 1 pair of types, where a type in Subscription.Engine uses a type in Metadata.Event.
- The types involved
Patchlevel.EventSourcing.Subscription.Engine.EventFilteredStoreMessageLoader→Patchlevel.EventSourcing.Metadata.Event.EventMetadataFactory
- Direction
- Subscription.Engine uses Metadata.Event, so a change to Metadata.Event can break Subscription.Engine, while a change to Subscription.Engine can't break Metadata.Event.
- Position
- Below the diagonal: Subscription.Engine uses a module listed above it, which is the healthy direction.
34→19 Subscription.Engine uses Subscription.RetryStrategy✕
- Connections
- 2 pairs of types, where a type in Subscription.Engine uses a type in Subscription.RetryStrategy.
- The types involved
Patchlevel.EventSourcing.Subscription.Engine.DefaultSubscriptionEngine→Patchlevel.EventSourcing.Subscription.RetryStrategy.RetryStrategyPatchlevel.EventSourcing.Subscription.Engine.DefaultSubscriptionEngine→Patchlevel.EventSourcing.Subscription.RetryStrategy.RetryStrategyRepository
- Direction
- Subscription.Engine uses Subscription.RetryStrategy, so a change to Subscription.RetryStrategy can break Subscription.Engine, while a change to Subscription.Engine can't break Subscription.RetryStrategy.
- Position
- Below the diagonal: Subscription.Engine uses a module listed above it, which is the healthy direction.
34→20 Subscription.Engine uses Subscription.Store✕
- Connections
- 3 pairs of types, where a type in Subscription.Engine uses a type in Subscription.Store.
- The types involved
Patchlevel.EventSourcing.Subscription.Engine.DefaultSubscriptionEngine→Patchlevel.EventSourcing.Subscription.Store.SubscriptionStorePatchlevel.EventSourcing.Subscription.Engine.SubscriptionManager→Patchlevel.EventSourcing.Subscription.Store.SubscriptionCriteriaPatchlevel.EventSourcing.Subscription.Engine.SubscriptionManager→Patchlevel.EventSourcing.Subscription.Store.SubscriptionStore
- Direction
- Subscription.Engine uses Subscription.Store, so a change to Subscription.Store can break Subscription.Engine, while a change to Subscription.Engine can't break Subscription.Store.
- Position
- Below the diagonal: Subscription.Engine uses a module listed above it, which is the healthy direction.
34→22 Subscription.Engine uses Message✕
- Connections
- 2 pairs of types, where a type in Subscription.Engine uses a type in Message.
- The types involved
Patchlevel.EventSourcing.Subscription.Engine.DefaultSubscriptionEngine→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Subscription.Engine.GapResolverStoreMessageLoader→Patchlevel.EventSourcing.Message.Message
- Direction
- Subscription.Engine uses Message, so a change to Message can break Subscription.Engine, while a change to Subscription.Engine can't break Message.
- Position
- Below the diagonal: Subscription.Engine uses a module listed above it, which is the healthy direction.
34→25 Subscription.Engine uses Subscription.Subscriber✕
- Connections
- 3 pairs of types, where a type in Subscription.Engine uses a type in Subscription.Subscriber.
- The types involved
Patchlevel.EventSourcing.Subscription.Engine.DefaultSubscriptionEngine→Patchlevel.EventSourcing.Subscription.Subscriber.SubscriberAccessorPatchlevel.EventSourcing.Subscription.Engine.DefaultSubscriptionEngine→Patchlevel.EventSourcing.Subscription.Subscriber.SubscriberAccessorRepositoryPatchlevel.EventSourcing.Subscription.Engine.EventFilteredStoreMessageLoader→Patchlevel.EventSourcing.Subscription.Subscriber.SubscriberAccessorRepository
- Direction
- Subscription.Engine uses Subscription.Subscriber, so a change to Subscription.Subscriber can break Subscription.Engine, while a change to Subscription.Engine can't break Subscription.Subscriber.
- Position
- Below the diagonal: Subscription.Engine uses a module listed above it, which is the healthy direction.
34→32 Subscription.Engine uses Store✕
- Connections
- 8 pairs of types, where a type in Subscription.Engine uses a type in Store.
- The types involved
Patchlevel.EventSourcing.Subscription.Engine.EventFilteredStoreMessageLoader→Patchlevel.EventSourcing.Store.StorePatchlevel.EventSourcing.Subscription.Engine.EventFilteredStoreMessageLoader→Patchlevel.EventSourcing.Store.StreamPatchlevel.EventSourcing.Subscription.Engine.GapResolverStoreMessageLoader→Patchlevel.EventSourcing.Store.StorePatchlevel.EventSourcing.Subscription.Engine.GapResolverStoreMessageLoader→Patchlevel.EventSourcing.Store.StreamPatchlevel.EventSourcing.Subscription.Engine.GeneratorStream→Patchlevel.EventSourcing.Store.StreamPatchlevel.EventSourcing.Subscription.Engine.MessageLoader→Patchlevel.EventSourcing.Store.StreamPatchlevel.EventSourcing.Subscription.Engine.StoreMessageLoader→Patchlevel.EventSourcing.Store.StorePatchlevel.EventSourcing.Subscription.Engine.StoreMessageLoader→Patchlevel.EventSourcing.Store.Stream
- Direction
- Subscription.Engine uses Store, so a change to Store can break Subscription.Engine, while a change to Subscription.Engine can't break Store.
- Position
- Below the diagonal: Subscription.Engine uses a module listed above it, which is the healthy direction.
35→7 Subscription.Lookup uses Store.Criteria✕
- Connections
- 1 pair of types, where a type in Subscription.Lookup uses a type in Store.Criteria.
- The types involved
Patchlevel.EventSourcing.Subscription.Lookup.Lookup→Patchlevel.EventSourcing.Store.Criteria.Criteria
- Direction
- Subscription.Lookup uses Store.Criteria, so a change to Store.Criteria can break Subscription.Lookup, while a change to Subscription.Lookup can't break Store.Criteria.
- Position
- Below the diagonal: Subscription.Lookup uses a module listed above it, which is the healthy direction.
35→22 Subscription.Lookup uses Message✕
- Connections
- 1 pair of types, where a type in Subscription.Lookup uses a type in Message.
- The types involved
Patchlevel.EventSourcing.Subscription.Lookup.Lookup→Patchlevel.EventSourcing.Message.Message
- Direction
- Subscription.Lookup uses Message, so a change to Message can break Subscription.Lookup, while a change to Subscription.Lookup can't break Message.
- Position
- Below the diagonal: Subscription.Lookup uses a module listed above it, which is the healthy direction.
35→32 Subscription.Lookup uses Store✕
- Connections
- 2 pairs of types, where a type in Subscription.Lookup uses a type in Store.
- The types involved
Patchlevel.EventSourcing.Subscription.Lookup.Lookup→Patchlevel.EventSourcing.Store.StorePatchlevel.EventSourcing.Subscription.Lookup.Lookup→Patchlevel.EventSourcing.Store.Stream
- Direction
- Subscription.Lookup uses Store, so a change to Store can break Subscription.Lookup, while a change to Subscription.Lookup can't break Store.
- Position
- Below the diagonal: Subscription.Lookup uses a module listed above it, which is the healthy direction.
36→13 CommandBus uses Metadata.AggregateRoot✕
- Connections
- 2 pairs of types, where a type in CommandBus uses a type in Metadata.AggregateRoot.
- The types involved
Patchlevel.EventSourcing.CommandBus.AggregateHandlerProvider→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootRegistryPatchlevel.EventSourcing.CommandBus.SyncCommandBus→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootRegistry
- Direction
- CommandBus uses Metadata.AggregateRoot, so a change to Metadata.AggregateRoot can break CommandBus, while a change to CommandBus can't break Metadata.AggregateRoot.
- Position
- Below the diagonal: CommandBus uses a module listed above it, which is the healthy direction.
36→33 CommandBus uses Repository✕
- Connections
- 2 pairs of types, where a type in CommandBus uses a type in Repository.
- The types involved
Patchlevel.EventSourcing.CommandBus.AggregateHandlerProvider→Patchlevel.EventSourcing.Repository.RepositoryManagerPatchlevel.EventSourcing.CommandBus.SyncCommandBus→Patchlevel.EventSourcing.Repository.RepositoryManager
- Direction
- CommandBus uses Repository, so a change to Repository can break CommandBus, while a change to CommandBus can't break Repository.
- Position
- Below the diagonal: CommandBus uses a module listed above it, which is the healthy direction.
37→21 CommandBus.Handler uses Aggregate✕
- Connections
- 1 pair of types, where a type in CommandBus.Handler uses a type in Aggregate.
- The types involved
Patchlevel.EventSourcing.CommandBus.Handler.UpdateAggregateHandler→Patchlevel.EventSourcing.Aggregate.AggregateRootId
- Direction
- CommandBus.Handler uses Aggregate, so a change to Aggregate can break CommandBus.Handler, while a change to CommandBus.Handler can't break Aggregate.
- Position
- Below the diagonal: CommandBus.Handler uses a module listed above it, which is the healthy direction.
37→33 CommandBus.Handler uses Repository✕
- Connections
- 2 pairs of types, where a type in CommandBus.Handler uses a type in Repository.
- The types involved
Patchlevel.EventSourcing.CommandBus.Handler.CreateAggregateHandler→Patchlevel.EventSourcing.Repository.RepositoryManagerPatchlevel.EventSourcing.CommandBus.Handler.UpdateAggregateHandler→Patchlevel.EventSourcing.Repository.RepositoryManager
- Direction
- CommandBus.Handler uses Repository, so a change to Repository can break CommandBus.Handler, while a change to CommandBus.Handler can't break Repository.
- Position
- Below the diagonal: CommandBus.Handler uses a module listed above it, which is the healthy direction.
38→4 Console.Command uses Schema✕
- Connections
- 3 pairs of types, where a type in Console.Command uses a type in Schema.
- The types involved
Patchlevel.EventSourcing.Console.Command.SchemaCreateCommand→Patchlevel.EventSourcing.Schema.SchemaDirectorPatchlevel.EventSourcing.Console.Command.SchemaDropCommand→Patchlevel.EventSourcing.Schema.SchemaDirectorPatchlevel.EventSourcing.Console.Command.SchemaUpdateCommand→Patchlevel.EventSourcing.Schema.SchemaDirector
- Direction
- Console.Command uses Schema, so a change to Schema can break Console.Command, while a change to Console.Command can't break Schema.
- Position
- Below the diagonal: Console.Command uses a module listed above it, which is the healthy direction.
38→9 Console.Command uses Subscription✕
- Connections
- 1 pair of types, where a type in Console.Command uses a type in Subscription.
- The types involved
Patchlevel.EventSourcing.Console.Command.SubscriptionStatusCommand→Patchlevel.EventSourcing.Subscription.Subscription
- Direction
- Console.Command uses Subscription, so a change to Subscription can break Console.Command, while a change to Console.Command can't break Subscription.
- Position
- Below the diagonal: Console.Command uses a module listed above it, which is the healthy direction.
38→13 Console.Command uses Metadata.AggregateRoot✕
- Connections
- 3 pairs of types, where a type in Console.Command uses a type in Metadata.AggregateRoot.
- The types involved
Patchlevel.EventSourcing.Console.Command.DebugCommand→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootRegistryPatchlevel.EventSourcing.Console.Command.ShowAggregateCommand→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootMetadataFactoryPatchlevel.EventSourcing.Console.Command.ShowAggregateCommand→Patchlevel.EventSourcing.Metadata.AggregateRoot.AggregateRootRegistry
- Direction
- Console.Command uses Metadata.AggregateRoot, so a change to Metadata.AggregateRoot can break Console.Command, while a change to Console.Command can't break Metadata.AggregateRoot.
- Position
- Below the diagonal: Console.Command uses a module listed above it, which is the healthy direction.
38→14 Console.Command uses Metadata.Event✕
- Connections
- 1 pair of types, where a type in Console.Command uses a type in Metadata.Event.
- The types involved
Patchlevel.EventSourcing.Console.Command.DebugCommand→Patchlevel.EventSourcing.Metadata.Event.EventRegistry
- Direction
- Console.Command uses Metadata.Event, so a change to Metadata.Event can break Console.Command, while a change to Console.Command can't break Metadata.Event.
- Position
- Below the diagonal: Console.Command uses a module listed above it, which is the healthy direction.
38→23 Console.Command uses Serializer✕
- Connections
- 3 pairs of types, where a type in Console.Command uses a type in Serializer.
- The types involved
Patchlevel.EventSourcing.Console.Command.ShowAggregateCommand→Patchlevel.EventSourcing.Serializer.EventSerializerPatchlevel.EventSourcing.Console.Command.ShowCommand→Patchlevel.EventSourcing.Serializer.EventSerializerPatchlevel.EventSourcing.Console.Command.WatchCommand→Patchlevel.EventSourcing.Serializer.EventSerializer
- Direction
- Console.Command uses Serializer, so a change to Serializer can break Console.Command, while a change to Console.Command can't break Serializer.
- Position
- Below the diagonal: Console.Command uses a module listed above it, which is the healthy direction.
38→30 Console.Command uses Message.Serializer✕
- Connections
- 3 pairs of types, where a type in Console.Command uses a type in Message.Serializer.
- The types involved
Patchlevel.EventSourcing.Console.Command.ShowAggregateCommand→Patchlevel.EventSourcing.Message.Serializer.HeadersSerializerPatchlevel.EventSourcing.Console.Command.ShowCommand→Patchlevel.EventSourcing.Message.Serializer.HeadersSerializerPatchlevel.EventSourcing.Console.Command.WatchCommand→Patchlevel.EventSourcing.Message.Serializer.HeadersSerializer
- Direction
- Console.Command uses Message.Serializer, so a change to Message.Serializer can break Console.Command, while a change to Console.Command can't break Message.Serializer.
- Position
- Below the diagonal: Console.Command uses a module listed above it, which is the healthy direction.
38→31 Console.Command uses Console✕
- Connections
- 4 pairs of types, where a type in Console.Command uses a type in Console.
- The types involved
Patchlevel.EventSourcing.Console.Command.DatabaseCreateCommand→Patchlevel.EventSourcing.Console.DoctrineHelperPatchlevel.EventSourcing.Console.Command.DatabaseDropCommand→Patchlevel.EventSourcing.Console.DoctrineHelperPatchlevel.EventSourcing.Console.Command.DebugCommand→Patchlevel.EventSourcing.Console.OutputStylePatchlevel.EventSourcing.Console.Command.SubscriptionStatusCommand→Patchlevel.EventSourcing.Console.OutputStyle
- Direction
- Console.Command uses Console, so a change to Console can break Console.Command, while a change to Console.Command can't break Console.
- Position
- Below the diagonal: Console.Command uses a module listed above it, which is the healthy direction.
38→32 Console.Command uses Store✕
- Connections
- 5 pairs of types, where a type in Console.Command uses a type in Store.
- The types involved
Patchlevel.EventSourcing.Console.Command.ShowAggregateCommand→Patchlevel.EventSourcing.Store.StorePatchlevel.EventSourcing.Console.Command.ShowCommand→Patchlevel.EventSourcing.Store.StorePatchlevel.EventSourcing.Console.Command.StoreMigrateCommand→Patchlevel.EventSourcing.Store.StorePatchlevel.EventSourcing.Console.Command.SubscriptionRunCommand→Patchlevel.EventSourcing.Store.StorePatchlevel.EventSourcing.Console.Command.WatchCommand→Patchlevel.EventSourcing.Store.Store
- Direction
- Console.Command uses Store, so a change to Store can break Console.Command, while a change to Console.Command can't break Store.
- Position
- Below the diagonal: Console.Command uses a module listed above it, which is the healthy direction.
38→34 Console.Command uses Subscription.Engine✕
- Connections
- 4 pairs of types, where a type in Console.Command uses a type in Subscription.Engine.
- The types involved
Patchlevel.EventSourcing.Console.Command.SubscriptionBootCommand→Patchlevel.EventSourcing.Subscription.Engine.SubscriptionEnginePatchlevel.EventSourcing.Console.Command.SubscriptionCommand→Patchlevel.EventSourcing.Subscription.Engine.SubscriptionEnginePatchlevel.EventSourcing.Console.Command.SubscriptionCommand→Patchlevel.EventSourcing.Subscription.Engine.SubscriptionEngineCriteriaPatchlevel.EventSourcing.Console.Command.SubscriptionRunCommand→Patchlevel.EventSourcing.Subscription.Engine.SubscriptionEngine
- Direction
- Console.Command uses Subscription.Engine, so a change to Subscription.Engine can break Console.Command, while a change to Console.Command can't break Subscription.Engine.
- Position
- Below the diagonal: Console.Command uses a module listed above it, which is the healthy direction.
39→21 Subscription.Repository uses Aggregate✕
- Connections
- 2 pairs of types, where a type in Subscription.Repository uses a type in Aggregate.
- The types involved
Patchlevel.EventSourcing.Subscription.Repository.RunSubscriptionEngineRepository→Patchlevel.EventSourcing.Aggregate.AggregateRootPatchlevel.EventSourcing.Subscription.Repository.RunSubscriptionEngineRepository→Patchlevel.EventSourcing.Aggregate.AggregateRootId
- Direction
- Subscription.Repository uses Aggregate, so a change to Aggregate can break Subscription.Repository, while a change to Subscription.Repository can't break Aggregate.
- Position
- Below the diagonal: Subscription.Repository uses a module listed above it, which is the healthy direction.
39→33 Subscription.Repository uses Repository✕
- Connections
- 3 pairs of types, where a type in Subscription.Repository uses a type in Repository.
- The types involved
Patchlevel.EventSourcing.Subscription.Repository.RunSubscriptionEngineRepository→Patchlevel.EventSourcing.Repository.RepositoryPatchlevel.EventSourcing.Subscription.Repository.RunSubscriptionEngineRepositoryManager→Patchlevel.EventSourcing.Repository.RepositoryPatchlevel.EventSourcing.Subscription.Repository.RunSubscriptionEngineRepositoryManager→Patchlevel.EventSourcing.Repository.RepositoryManager
- Direction
- Subscription.Repository uses Repository, so a change to Repository can break Subscription.Repository, while a change to Subscription.Repository can't break Repository.
- Position
- Below the diagonal: Subscription.Repository uses a module listed above it, which is the healthy direction.
39→34 Subscription.Repository uses Subscription.Engine✕
- Connections
- 2 pairs of types, where a type in Subscription.Repository uses a type in Subscription.Engine.
- The types involved
Patchlevel.EventSourcing.Subscription.Repository.RunSubscriptionEngineRepository→Patchlevel.EventSourcing.Subscription.Engine.SubscriptionEnginePatchlevel.EventSourcing.Subscription.Repository.RunSubscriptionEngineRepositoryManager→Patchlevel.EventSourcing.Subscription.Engine.SubscriptionEngine
- Direction
- Subscription.Repository uses Subscription.Engine, so a change to Subscription.Engine can break Subscription.Repository, while a change to Subscription.Repository can't break Subscription.Engine.
- Position
- Below the diagonal: Subscription.Repository uses a module listed above it, which is the healthy direction.
40→16 Subscription.Subscriber.ArgumentResolver uses Metadata.Subscriber✕
- Connections
- 6 pairs of types, where a type in Subscription.Subscriber.ArgumentResolver uses a type in Metadata.Subscriber.
- The types involved
Patchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.AggregateIdArgumentResolver→Patchlevel.EventSourcing.Metadata.Subscriber.ArgumentMetadataPatchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.ArgumentResolver→Patchlevel.EventSourcing.Metadata.Subscriber.ArgumentMetadataPatchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.EventArgumentResolver→Patchlevel.EventSourcing.Metadata.Subscriber.ArgumentMetadataPatchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.LookupResolver→Patchlevel.EventSourcing.Metadata.Subscriber.ArgumentMetadataPatchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.MessageArgumentResolver→Patchlevel.EventSourcing.Metadata.Subscriber.ArgumentMetadataPatchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.RecordedOnArgumentResolver→Patchlevel.EventSourcing.Metadata.Subscriber.ArgumentMetadata
- Direction
- Subscription.Subscriber.ArgumentResolver uses Metadata.Subscriber, so a change to Metadata.Subscriber can break Subscription.Subscriber.ArgumentResolver, while a change to Subscription.Subscriber.ArgumentResolver can't break Metadata.Subscriber.
- Position
- Below the diagonal: Subscription.Subscriber.ArgumentResolver uses a module listed above it, which is the healthy direction.
40→21 Subscription.Subscriber.ArgumentResolver uses Aggregate✕
- Connections
- 1 pair of types, where a type in Subscription.Subscriber.ArgumentResolver uses a type in Aggregate.
- The types involved
Patchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.AggregateIdArgumentResolver→Patchlevel.EventSourcing.Aggregate.AggregateRootId
- Direction
- Subscription.Subscriber.ArgumentResolver uses Aggregate, so a change to Aggregate can break Subscription.Subscriber.ArgumentResolver, while a change to Subscription.Subscriber.ArgumentResolver can't break Aggregate.
- Position
- Below the diagonal: Subscription.Subscriber.ArgumentResolver uses a module listed above it, which is the healthy direction.
40→22 Subscription.Subscriber.ArgumentResolver uses Message✕
- Connections
- 6 pairs of types, where a type in Subscription.Subscriber.ArgumentResolver uses a type in Message.
- The types involved
Patchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.AggregateIdArgumentResolver→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.ArgumentResolver→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.EventArgumentResolver→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.LookupResolver→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.MessageArgumentResolver→Patchlevel.EventSourcing.Message.MessagePatchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.RecordedOnArgumentResolver→Patchlevel.EventSourcing.Message.Message
- Direction
- Subscription.Subscriber.ArgumentResolver uses Message, so a change to Message can break Subscription.Subscriber.ArgumentResolver, while a change to Subscription.Subscriber.ArgumentResolver can't break Message.
- Position
- Below the diagonal: Subscription.Subscriber.ArgumentResolver uses a module listed above it, which is the healthy direction.
40→32 Subscription.Subscriber.ArgumentResolver uses Store✕
- Connections
- 1 pair of types, where a type in Subscription.Subscriber.ArgumentResolver uses a type in Store.
- The types involved
Patchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.LookupResolver→Patchlevel.EventSourcing.Store.Store
- Direction
- Subscription.Subscriber.ArgumentResolver uses Store, so a change to Store can break Subscription.Subscriber.ArgumentResolver, while a change to Subscription.Subscriber.ArgumentResolver can't break Store.
- Position
- Below the diagonal: Subscription.Subscriber.ArgumentResolver uses a module listed above it, which is the healthy direction.
40→35 Subscription.Subscriber.ArgumentResolver uses Subscription.Lookup✕
- Connections
- 1 pair of types, where a type in Subscription.Subscriber.ArgumentResolver uses a type in Subscription.Lookup.
- The types involved
Patchlevel.EventSourcing.Subscription.Subscriber.ArgumentResolver.LookupResolver→Patchlevel.EventSourcing.Subscription.Lookup.Lookup
- Direction
- Subscription.Subscriber.ArgumentResolver uses Subscription.Lookup, so a change to Subscription.Lookup can break Subscription.Subscriber.ArgumentResolver, while a change to Subscription.Subscriber.ArgumentResolver can't break Subscription.Lookup.
- Position
- Below the diagonal: Subscription.Subscriber.ArgumentResolver uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 79 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 15 | High / Critical |
| A02:2025 — Security Misconfiguration | 9 | High / Critical |
Roadmap
Top priorities: 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; Resolve the 26 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (20), REDACTED (6); Resolve the 8 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.8 pts | Low | Supply-chain Provenance & Signing |
| 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.4 pts | Medium | Architecture documentation |
| Resolve the 26 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (20), REDACTED (6). | +2.6 pts | Medium | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.1 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.1 pts | Low | Dependency Vulnerabilities |
| Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). | +1.1 pts | Low | IaC & Container Security |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.0 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.0 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| src/Repository/DefaultRepository.php | 5.8 | Mixed | Change Coupling: Boundary-crossing change coupling: DefaultRepository.php ↔ DefaultSnapshotStore.php |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| tests/Unit/Subscription/Engine/DefaultSubscriptionEngineTest.php | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/Subscription/Engine/DefaultSubscriptionEngine.php | 7.0 | Mixed | Cyclomatic Complexity: DefaultSubscriptionEngine.boot (cyclomatic 19) |
| src/Store/DoctrineDbalStore.php | 7.0 | Mixed | Code Duplication: Duplicated block (50 lines × 2) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/Console/Command/SubscriptionBootCommand.php | 7.4 | Mixed | Code Duplication: Duplicated block (41 lines × 2) |
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 50 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 — 50 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, 172 of 189 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 coverage step in CI (`phpunit --testsuite=unit --coverage-clover=clover.xml --cove…`) 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.
- 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.
- D26 Project Cohesion — 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. `(repository root)` (14207 LoC, 373 module-visible types across 40 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Aggregate/AggregateHeader.php`, `src/Aggregate/AggregateRootAttributeBehaviour.php`, `src/Aggregate/CustomIdBehaviour.php`, `src/Aggregate/RamseyUuidV7Behaviour.php`, `src/Attribute/Aggregate.php`, … (+150 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 48 commits in the last 90 days, yet 29 of 46 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- 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 a PSR-11 container (Psr\Container), 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 REDACTED (REDACTED). docker build failed (exit 1) — -------------------- ERROR: failed to solve: process "/bin/sh -c mkdir -p /tmp/blackfire && architecture=$(uname -m) && curl -A \"Docker\" -L https://blackfire.io/api/v1/releases/cli/linux/$architecture | tar zxp -C /tmp/blackfire && mv /tmp/blackfire/blackfire /usr/bin/blackfire && rm -Rf /tmp/blackfire" did not complete successfully: exit code: 2; runtime evidence skipped.
- 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.
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was InMemoryStore.filter at 33.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with InMemoryStore.filter (cyclomatic 33), DefaultSubscriptionEngine.boot (cyclomatic 19), AttributeSubscriberMetadataFactory.metadata (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was InMemoryStore.filter at 78.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with InMemoryStore.filter (cognitive 78), AttributeSubscriberMetadataFactory.metadata (cognitive 34), DefaultSubscriptionEngine.boot (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 3 together lifts Cognitive Complexity from 7.5 to about 8.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with DefaultSubscriptionEngine.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with DefaultSubscriptionEngine.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Subscription.php. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
30 duplicated block group(s) detected.
What to do
- Resolve the 6 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with DoctrineDbalStore.php (3), HandlerFinder.php, DoctrineCipherKeyStore.php. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with DoctrineDbalStore.php, DoctrineDbalStoreStream.php, DefaultSubscriptionEngine.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with DoctrineDbalStore.php, Psr16AggregateRootRegistryFactory.php, Psr16EventMetadataFactory.php. — One of this dimension's main actionable groups (3 warning-level).
D6 · Cohesion (LCOM4)
2 of 72 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with Lookup.php, Message.php. — One of this dimension's main actionable groups (2 warning-level).
D9 · Test Distribution
961 test methods: 0 unit, 961 integration, 0 BDD, 0 e2e.
D10 · Test Quality
7 skipped (7 with a documented reason), 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 961 tests.
D12 · Dependency Hygiene
7 outdated, 0 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 29 locked Composer package(s) use a banned license. Licences were read from this repository's REDACTED, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 81 package(s) under `packages-dev` are not installed for a consumer and are excluded.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: src/Store/StreamDoctrineDbalStore.php (3 of 3 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with StreamDoctrineDbalStore.php. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Subscription/Engine/DefaultSubscriptionEngine.php. Counted over 46 of the 373 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
3 deducted task-comment markers across 14207 LoC (0.0/KLoC) → score 10.0. 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 3 TodoComment finding(s) in Explicit Debt — start with DefaultSubscriptionEngineTest.php (3). — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 25 document(s) read across 1 unit(s).
D27 · Navigability
58 % of calls cross a namespace and 24 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
79 finding(s): 0 critical, 75 high, 4 medium, 0 low. 48 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 155 file(s) — `src/Aggregate/AggregateHeader.php` (line 15, line 16, line 17, …), `src/Aggregate/AggregateRootAttributeBehaviour.php` (line 68), `src/Aggregate/CustomIdBehaviour.php` (line 10), `src/Aggregate/RamseyUuidV7Behaviour.php` (line 13), `src/Attribute/Aggregate.php` (line 13), … (+150 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 26 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (20), REDACTED (6). — One of this dimension's main actionable groups (26 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 48 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 (48 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
9 finding(s): 0 critical, 4 high, 5 medium, 0 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 warning-level).
D35 · Change Coupling
Strongest change-coupling: SubscriptionStatusCommand.php↔DoctrineSubscriptionStore.php 55%; DefaultRepository.php↔DefaultSnapshotStore.php 55%
What to do
- Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with SubscriptionStatusCommand.php, DefaultRepository.php. — One of this dimension's main actionable groups (2 issue-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 8 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 14 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 1 of 1 have no README of their own, in their folder or in their family's project (`tools`).
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
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
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
What to do
- 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.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
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
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/Schema/DoctrineHelper.php:32
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 87% | Strong | Solid. |
| Architecture | 96% | Exemplary | Solid. |
| Maturity | 63% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 66% | Adequate | Acceptable, with room to improve. |
| Security | 61% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 67 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
- 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 — docker build failed (exit 1) — -------------------- ERROR: failed to solve: process "/bin/sh -c mkdir -p /tmp/blackfire && architecture=$(uname -m) && curl -A \"Docker\" -L https://blackfire.io/api/v1/releases/cli/linux/$architecture | tar zxp -C /tmp/blackfire && mv /tmp/blackfire/blackfire /usr/bin/blackfire && rm -Rf /tmp/blackfire" did not complete successfully: exit code: 2; 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
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — 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.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — 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
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 155 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- 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.
- 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
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 23 value object(s); a Domain/Aggregates/ValueObjects layer
- 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 — not scored — this repository shows only 1 of the 3 signals this lens looks for (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
- M4 Documentation accuracy — Not applicable: the 25 current-state document(s) make no claim of a kind M4 checks.
- 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 — Doctrine is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
- 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
- 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
- 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 — 82 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: SubscriptionStatusCommand.php ↔ DoctrineSubscriptionStore.php src/Console/Command/SubscriptionStatusCommand.php:1
- Boundary-crossing change coupling: DefaultRepository.php ↔ DefaultSnapshotStore.php src/Repository/DefaultRepository.php:1
- REDACTED
- REDACTED
Serious — 77 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (17 lines × 2) src/CommandBus/HandlerFinder.php:61
- Duplicated block (17 lines × 2) src/Cryptography/DoctrineCipherKeyStore.php:84
- Duplicated block (17 lines × 2) src/Store/DoctrineDbalStore.php:130
- Duplicated block (17 lines × 2) src/Store/DoctrineDbalStore.php:166
- Duplicated block (17 lines × 2) src/Store/DoctrineDbalStore.php:215
- Duplicated block (17 lines × 2) src/Subscription/Engine/DefaultSubscriptionEngine.php:1231
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment tests/Unit/Subscription/Engine/DefaultSubscriptionEngineTest.php:943
- TodoComment tests/Unit/Subscription/Engine/DefaultSubscriptionEngineTest.php:948
- TodoComment tests/Unit/Subscription/Engine/DefaultSubscriptionEngineTest.php:953
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (15 lines × 2) src/Store/DoctrineDbalStore.php:412
- Duplicated block (15 lines × 2) src/Store/DoctrineDbalStoreStream.php:115
- Duplicated block (15 lines × 2) src/Subscription/Engine/DefaultSubscriptionEngine.php:110
- Duplicated block (11 lines × 2) src/Store/DoctrineDbalStore.php:365
- Duplicated block (11 lines × 2) src/Metadata/AggregateRoot/Psr16AggregateRootRegistryFactory.php:23
- Duplicated block (11 lines × 2) src/Metadata/Event/Psr16EventMetadataFactory.php:21
- Duplicated block (18 lines × 2) src/Store/DoctrineDbalStore.php:261
- Duplicated block (18 lines × 2) src/Subscription/Engine/DefaultSubscriptionEngine.php:302
- Duplicated block (13 lines × 2) src/CommandBus/HandlerDescriptor.php:33
- Duplicated block (13 lines × 2) src/Store/DoctrineDbalStore.php:390
- Duplicated block (7 lines × 2) src/CommandBus/AggregateHandlerProvider.php:38
- Duplicated block (7 lines × 2) src/Store/DoctrineDbalStore.php:468
- Low cohesion: Lookup (LCOM4 9) src/Subscription/Lookup/Lookup.php:25
- Low cohesion: Message (LCOM4 4) src/Message/Message.php:16
- InMemoryStore.filter (cyclomatic 33) src/Store/InMemoryStore.php:173
- DefaultSubscriptionEngine.boot (cyclomatic 19) src/Subscription/Engine/DefaultSubscriptionEngine.php:170
- AttributeSubscriberMetadataFactory.metadata (cyclomatic 18) src/Metadata/Subscriber/AttributeSubscriberMetadataFactory.php:28
- DefaultSubscriptionEngine.run (cyclomatic 17) src/Subscription/Engine/DefaultSubscriptionEngine.php:359
- Repeated repair: src/Store/StreamDoctrineDbalStore.php src/Store/StreamDoctrineDbalStore.php:162
- InMemoryStore.filter (cognitive 78) src/Store/InMemoryStore.php:173
- AttributeSubscriberMetadataFactory.metadata (cognitive 34) src/Metadata/Subscriber/AttributeSubscriberMetadataFactory.php:28
- DefaultSubscriptionEngine.boot (cognitive 32) src/Subscription/Engine/DefaultSubscriptionEngine.php:170
- DefaultSubscriptionEngine.setup (cognitive 29) src/Subscription/Engine/DefaultSubscriptionEngine.php:71
- DefaultSubscriptionEngine.run (cognitive 29) src/Subscription/Engine/DefaultSubscriptionEngine.php:359
- AttributeAggregateRootMetadataFactory.findApplyMethods (cognitive 26) src/Metadata/AggregateRoot/AttributeAggregateRootMetadataFactory.php:230
- StreamDoctrineDbalStore.save (cognitive 24) src/Store/StreamDoctrineDbalStore.php:226
- DefaultRepository.load (cognitive 21) src/Repository/DefaultRepository.php:78
- StreamDoctrineDbalStore.applyCriteria (cognitive 17) src/Store/StreamDoctrineDbalStore.php:162
- DefaultRepository.save (cognitive 16) src/Repository/DefaultRepository.php:226
- ClassTooLong: DefaultSubscriptionEngine src/Subscription/Engine/DefaultSubscriptionEngine.php:32
- FileTooLong: Engine/DefaultSubscriptionEngine.php src/Subscription/Engine/DefaultSubscriptionEngine.php
- TooManyMethods: Subscription src/Subscription/Subscription.php:10
- MethodTooLong: DefaultSubscriptionEngine.boot src/Subscription/Engine/DefaultSubscriptionEngine.php:170
- REDACTED
- Duplicated block (62–63 lines × 2) src/Subscription/Engine/DefaultSubscriptionEngine.php:221
- Duplicated block (50 lines × 2) src/Store/DoctrineDbalStore.php:506
- Duplicated block (41 lines × 2) src/Console/Command/SubscriptionBootCommand.php:33
- Duplicated block (32 lines × 2) src/Store/DoctrineDbalStore.php:560
- Duplicated block (30 lines × 3) src/Console/Command/SubscriptionBootCommand.php:36
- Duplicated block (30 lines × 2) src/Store/DoctrineDbalStore.php:313
- Duplicated block (28 lines × 2) src/Store/DoctrineDbalStore.php:431
- Duplicated block (11–13 lines × 2) src/Store/DoctrineDbalStore.php:347
- Duplicated block (12 lines × 3) src/CommandBus/HandlerDescriptor.php:36
- Duplicated block (9 lines × 2) src/Store/DoctrineDbalStore.php:106
- Duplicated block (4–6 lines × 3) src/Console/Command/SubscriptionBootCommand.php:81
- Duplicated block (12 lines × 2) src/Store/DoctrineDbalStore.php:490
- Coverage collected but not gated
- Swallowed exception (empty catch) src/Schema/DoctrineHelper.php:32
Minor — 12 finding(s)
- Duplicated predicate src/Store/DoctrineDbalStore.php:524
- Duplicated predicate src/Store/DoctrineDbalStore.php:321
- Duplicated predicate src/Store/DoctrineDbalStore.php:407
- Duplicated predicate src/Console/Command/SubscriptionRunCommand.php:120
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- REDACTED
- REDACTED
- No ADRs
- CI build step not evidenced
- No rollback/health safety
- No changelog
Minor — 18 finding(s)
- Skipped (documented): testSaveLockTimeout tests/Integration/Store/DoctrineDbalStoreTest.php:204
- Skipped (documented): testLockIsAcquiredAgainAfterTimeout tests/Integration/Store/DoctrineDbalStoreTest.php:243
- Skipped (documented): testSaveHoldsLockUntilCommit tests/Integration/Store/DoctrineDbalStoreTest.php:287
- Skipped (documented): testSaveHoldsLockUntilCommit tests/Integration/Store/StreamDoctrineDbalStoreTest.php:495
- Skipped (documented): testSetupSubscriptionCreatesTheNotifyTrigger tests/Integration/Store/StreamDoctrineDbalStoreTest.php:1207
- Skipped (documented): testLoadWithOffset tests/Unit/Store/DoctrineDbalStoreTest.php:170
- Skipped (documented): testLoadWithOffset tests/Unit/Store/StreamDoctrineDbalStoreTest.php:153
- Outdated: doctrine/dbal
- Outdated: doctrine/migrations
- Outdated: patchlevel/worker
- Outdated: ramsey/uuid
- Outdated: symfony/console
- Outdated: symfony/finder
- Outdated: symfony/type-info
- No assertions (declared): testInstantiate tests/Unit/Attribute/IdTest.php:16
- No assertions (declared): testInstantiate tests/Unit/Attribute/SetupTest.php:16
- No assertions (declared): testInstantiate tests/Unit/Attribute/SplitStreamTest.php:16
- No assertions (declared): testInstantiate tests/Unit/Attribute/TeardownTest.php:16
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-0e3a6bfaf59b4ab787082208c13b0a1d/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-0e3a6bfaf59b4ab787082208c13b0a1d/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 . | 79 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 9 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 155 file(s) — `src/Aggregate/AggregateHeader.php`, `src/Aggregate/AggregateRootAttributeBehaviour.php`, `src/Aggregate/CustomIdBehaviour.php`, `src/Aggregate/RamseyUuidV7Behaviour.php`, `src/Attribute/Aggregate.php`, … (+150 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |