Executive summary
waku-py/waku is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 70 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is having someone learn and document the 39 files no active contributor knows, worth about 7 points. Adding automated security scanning comes next, worth about 5 points.
Five known security holes in the packages the code depends on can be used by attackers. Two secrets can leak from the build pipeline, and one weakness in the code could be used by an attacker. Updating the vulnerable packages, limiting each secret to its own step and fixing the weaknesses the scanner points to would close these risks. Giving the pull-request workflow read-only access would fix the pipeline that outsiders can trigger with write access.
The product code is 8,817 lines, about €26,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Rebuild cost: about €26,000 · Estimate
| Cost to rebuild | €8,700 to €43,000, for 144 to 458 hours of work, about 0.2 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 | ×1.0 at a score of 70. 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: 8,817 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 eventsourcing.contracts.stream | 2 eventsourcing.projection.checkpoint | 3 eventsourcing.projection.lock.interfaces | 4 eventsourcing.serialization.registry | 5 eventsourcing.snapshot.migration | 6 exceptions | 7 messaging.contracts.message | 8 messaging.registry | 9 modules._metadata | 10 eventsourcing.projection.interfaces | 11 eventsourcing.snapshot.interfaces | 12 eventsourcing.store.interfaces | 13 messaging.contracts.event | 14 messaging.interfaces | 15 modules._metadata_registry | 16 modules._module | 17 eventsourcing | 18 eventsourcing.contracts.event | 19 eventsourcing.projection.binding | 20 eventsourcing.repository | 21 eventsourcing.serialization.interfaces | 22 eventsourcing.snapshot | 23 eventsourcing.snapshot.registry | 24 eventsourcing.store.in_memory | 25 messaging.impl | 26 modules._registry | 27 application | 28 eventsourcing.decider.repository | 29 eventsourcing.projection.processor | 30 eventsourcing.serialization.json | 31 eventsourcing.snapshot.manager | 32 eventsourcing.snapshot.repository | 33 eventsourcing.store.sqlalchemy.store | 34 eventsourcing.projection.runner | 35 eventsourcing.store.sqlalchemy | 36 extensions.protocols | 37 eventsourcing.modules | 38 messaging.modules | 39 validation._extension | 40 validation.rules.dependency_accessible |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 eventsourcing.contracts.stream | ||||||||||||||||||||||||||||||||||||||||
| 2 eventsourcing.projection.checkpoint | ||||||||||||||||||||||||||||||||||||||||
| 3 eventsourcing.projection.lock.interfaces | ||||||||||||||||||||||||||||||||||||||||
| 4 eventsourcing.serialization.registry | ||||||||||||||||||||||||||||||||||||||||
| 5 eventsourcing.snapshot.migration | ||||||||||||||||||||||||||||||||||||||||
| 6 exceptions | ||||||||||||||||||||||||||||||||||||||||
| 7 messaging.contracts.message | ||||||||||||||||||||||||||||||||||||||||
| 8 messaging.registry | ||||||||||||||||||||||||||||||||||||||||
| 9 modules._metadata | ||||||||||||||||||||||||||||||||||||||||
| 10 eventsourcing.projection.interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 eventsourcing.snapshot.interfaces | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 eventsourcing.store.interfaces | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 messaging.contracts.event | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 messaging.interfaces | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 modules._metadata_registry | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 modules._module | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 eventsourcing | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 18 eventsourcing.contracts.event | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 eventsourcing.projection.binding | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 eventsourcing.repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 eventsourcing.serialization.interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 eventsourcing.snapshot | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 eventsourcing.snapshot.registry | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 eventsourcing.store.in_memory | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 messaging.impl | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 modules._registry | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 application | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 eventsourcing.decider.repository | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 eventsourcing.projection.processor | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 eventsourcing.serialization.json | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 eventsourcing.snapshot.manager | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 eventsourcing.snapshot.repository | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 eventsourcing.store.sqlalchemy.store | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 eventsourcing.projection.runner | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 eventsourcing.store.sqlalchemy | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 extensions.protocols | 1 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 37 eventsourcing.modules | 1 | 2 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 38 messaging.modules | 2 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||||
| 39 validation._extension | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 validation.rules.dependency_accessible | 7 | 2 | 1 |
10→2 eventsourcing.projection.interfaces uses eventsourcing.projection.checkpoint✕
- Connections
- 1 pair of types, where a type in eventsourcing.projection.interfaces uses a type in eventsourcing.projection.checkpoint.
- The types involved
src.waku.eventsourcing.projection.interfaces.ICheckpointStore→src.waku.eventsourcing.projection.checkpoint.Checkpoint
- Direction
- eventsourcing.projection.interfaces uses eventsourcing.projection.checkpoint, so a change to eventsourcing.projection.checkpoint can break eventsourcing.projection.interfaces, while a change to eventsourcing.projection.interfaces can't break eventsourcing.projection.checkpoint.
- Position
- Below the diagonal: eventsourcing.projection.interfaces uses a module listed above it, which is the healthy direction.
11→1 eventsourcing.snapshot.interfaces uses eventsourcing.contracts.stream✕
- Connections
- 2 pairs of types, where a type in eventsourcing.snapshot.interfaces uses a type in eventsourcing.contracts.stream.
- The types involved
src.waku.eventsourcing.snapshot.interfaces.ISnapshotStore→src.waku.eventsourcing.contracts.stream.StreamIdsrc.waku.eventsourcing.snapshot.interfaces.Snapshot→src.waku.eventsourcing.contracts.stream.StreamId
- Direction
- eventsourcing.snapshot.interfaces uses eventsourcing.contracts.stream, so a change to eventsourcing.contracts.stream can break eventsourcing.snapshot.interfaces, while a change to eventsourcing.snapshot.interfaces can't break eventsourcing.contracts.stream.
- Position
- Below the diagonal: eventsourcing.snapshot.interfaces uses a module listed above it, which is the healthy direction.
12→1 eventsourcing.store.interfaces uses eventsourcing.contracts.stream✕
- Connections
- 2 pairs of types, where a type in eventsourcing.store.interfaces uses a type in eventsourcing.contracts.stream.
- The types involved
src.waku.eventsourcing.store.interfaces.IEventReader→src.waku.eventsourcing.contracts.stream.StreamIdsrc.waku.eventsourcing.store.interfaces.IEventWriter→src.waku.eventsourcing.contracts.stream.StreamId
- Direction
- eventsourcing.store.interfaces uses eventsourcing.contracts.stream, so a change to eventsourcing.contracts.stream can break eventsourcing.store.interfaces, while a change to eventsourcing.store.interfaces can't break eventsourcing.contracts.stream.
- Position
- Below the diagonal: eventsourcing.store.interfaces uses a module listed above it, which is the healthy direction.
13→7 messaging.contracts.event uses messaging.contracts.message✕
- Connections
- 1 pair of types, where a type in messaging.contracts.event uses a type in messaging.contracts.message.
- The types involved
src.waku.messaging.contracts.event.IEvent→src.waku.messaging.contracts.message.IMessage
- Direction
- messaging.contracts.event uses messaging.contracts.message, so a change to messaging.contracts.message can break messaging.contracts.event, while a change to messaging.contracts.event can't break messaging.contracts.message.
- Position
- Below the diagonal: messaging.contracts.event uses a module listed above it, which is the healthy direction.
14→7 messaging.interfaces uses messaging.contracts.message✕
- Connections
- 2 pairs of types, where a type in messaging.interfaces uses a type in messaging.contracts.message.
- The types involved
src.waku.messaging.interfaces.IPublisher→src.waku.messaging.contracts.message.IMessagesrc.waku.messaging.interfaces.ISender→src.waku.messaging.contracts.message.IMessage
- Direction
- messaging.interfaces uses messaging.contracts.message, so a change to messaging.contracts.message can break messaging.interfaces, while a change to messaging.interfaces can't break messaging.contracts.message.
- Position
- Below the diagonal: messaging.interfaces uses a module listed above it, which is the healthy direction.
15→9 modules._metadata_registry uses modules._metadata✕
- Connections
- 1 pair of types, where a type in modules._metadata_registry uses a type in modules._metadata.
- The types involved
src.waku.modules._metadata_registry.ModuleMetadataRegistry→src.waku.modules._metadata.ModuleMetadata
- Direction
- modules._metadata_registry uses modules._metadata, so a change to modules._metadata can break modules._metadata_registry, while a change to modules._metadata_registry can't break modules._metadata.
- Position
- Below the diagonal: modules._metadata_registry uses a module listed above it, which is the healthy direction.
16→9 modules._module uses modules._metadata✕
- Connections
- 1 pair of types, where a type in modules._module uses a type in modules._metadata.
- The types involved
src.waku.modules._module.Module→src.waku.modules._metadata.ModuleMetadata
- Direction
- modules._module uses modules._metadata, so a change to modules._metadata can break modules._module, while a change to modules._module can't break modules._metadata.
- Position
- Below the diagonal: modules._module uses a module listed above it, which is the healthy direction.
17→1 eventsourcing uses eventsourcing.contracts.stream✕
- Connections
- 1 pair of types, where a type in eventsourcing uses a type in eventsourcing.contracts.stream.
- The types involved
src.waku.eventsourcing._stream_helpers→src.waku.eventsourcing.contracts.stream.StreamId
- Direction
- eventsourcing uses eventsourcing.contracts.stream, so a change to eventsourcing.contracts.stream can break eventsourcing, while a change to eventsourcing can't break eventsourcing.contracts.stream.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
17→5 eventsourcing uses eventsourcing.snapshot.migration✕
- Connections
- 1 pair of types, where a type in eventsourcing uses a type in eventsourcing.snapshot.migration.
- The types involved
src.waku.eventsourcing.modules→src.waku.eventsourcing.snapshot.migration.SnapshotMigrationChain
- Direction
- eventsourcing uses eventsourcing.snapshot.migration, so a change to eventsourcing.snapshot.migration can break eventsourcing, while a change to eventsourcing can't break eventsourcing.snapshot.migration.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
17→10 eventsourcing uses eventsourcing.projection.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing uses a type in eventsourcing.projection.interfaces.
- The types involved
src.waku.eventsourcing.testing→src.waku.eventsourcing.projection.interfaces.ICheckpointStore
- Direction
- eventsourcing uses eventsourcing.projection.interfaces, so a change to eventsourcing.projection.interfaces can break eventsourcing, while a change to eventsourcing can't break eventsourcing.projection.interfaces.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
17→12 eventsourcing uses eventsourcing.store.interfaces✕
- Connections
- 2 pairs of types, where a type in eventsourcing uses a type in eventsourcing.store.interfaces.
- The types involved
src.waku.eventsourcing._stream_helpers→src.waku.eventsourcing.store.interfaces.IEventStoresrc.waku.eventsourcing.testing→src.waku.eventsourcing.store.interfaces.IEventReader
- Direction
- eventsourcing uses eventsourcing.store.interfaces, so a change to eventsourcing.store.interfaces can break eventsourcing, while a change to eventsourcing can't break eventsourcing.store.interfaces.
- Position
- Below the diagonal: eventsourcing uses a module listed above it, which is the healthy direction.
18→1 eventsourcing.contracts.event uses eventsourcing.contracts.stream✕
- Connections
- 1 pair of types, where a type in eventsourcing.contracts.event uses a type in eventsourcing.contracts.stream.
- The types involved
src.waku.eventsourcing.contracts.event.StoredEvent→src.waku.eventsourcing.contracts.stream.StreamId
- Direction
- eventsourcing.contracts.event uses eventsourcing.contracts.stream, so a change to eventsourcing.contracts.stream can break eventsourcing.contracts.event, while a change to eventsourcing.contracts.event can't break eventsourcing.contracts.stream.
- Position
- Below the diagonal: eventsourcing.contracts.event uses a module listed above it, which is the healthy direction.
18→13 eventsourcing.contracts.event uses messaging.contracts.event✕
- Connections
- 1 pair of types, where a type in eventsourcing.contracts.event uses a type in messaging.contracts.event.
- The types involved
src.waku.eventsourcing.contracts.event.EventEnvelope→src.waku.messaging.contracts.event.IEvent
- Direction
- eventsourcing.contracts.event uses messaging.contracts.event, so a change to messaging.contracts.event can break eventsourcing.contracts.event, while a change to eventsourcing.contracts.event can't break messaging.contracts.event.
- Position
- Below the diagonal: eventsourcing.contracts.event uses a module listed above it, which is the healthy direction.
19→10 eventsourcing.projection.binding uses eventsourcing.projection.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.projection.binding uses a type in eventsourcing.projection.interfaces.
- The types involved
src.waku.eventsourcing.projection.binding.CatchUpProjectionBinding→src.waku.eventsourcing.projection.interfaces.ErrorPolicy
- Direction
- eventsourcing.projection.binding uses eventsourcing.projection.interfaces, so a change to eventsourcing.projection.interfaces can break eventsourcing.projection.binding, while a change to eventsourcing.projection.binding can't break eventsourcing.projection.interfaces.
- Position
- Below the diagonal: eventsourcing.projection.binding uses a module listed above it, which is the healthy direction.
20→1 eventsourcing.repository uses eventsourcing.contracts.stream✕
- Connections
- 1 pair of types, where a type in eventsourcing.repository uses a type in eventsourcing.contracts.stream.
- The types involved
src.waku.eventsourcing.repository.EventSourcedRepository→src.waku.eventsourcing.contracts.stream.StreamId
- Direction
- eventsourcing.repository uses eventsourcing.contracts.stream, so a change to eventsourcing.contracts.stream can break eventsourcing.repository, while a change to eventsourcing.repository can't break eventsourcing.contracts.stream.
- Position
- Below the diagonal: eventsourcing.repository uses a module listed above it, which is the healthy direction.
20→12 eventsourcing.repository uses eventsourcing.store.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.repository uses a type in eventsourcing.store.interfaces.
- The types involved
src.waku.eventsourcing.repository.EventSourcedRepository→src.waku.eventsourcing.store.interfaces.IEventStore
- Direction
- eventsourcing.repository uses eventsourcing.store.interfaces, so a change to eventsourcing.store.interfaces can break eventsourcing.repository, while a change to eventsourcing.repository can't break eventsourcing.store.interfaces.
- Position
- Below the diagonal: eventsourcing.repository uses a module listed above it, which is the healthy direction.
21→13 eventsourcing.serialization.interfaces uses messaging.contracts.event✕
- Connections
- 1 pair of types, where a type in eventsourcing.serialization.interfaces uses a type in messaging.contracts.event.
- The types involved
src.waku.eventsourcing.serialization.interfaces.IEventSerializer→src.waku.messaging.contracts.event.IEvent
- Direction
- eventsourcing.serialization.interfaces uses messaging.contracts.event, so a change to messaging.contracts.event can break eventsourcing.serialization.interfaces, while a change to eventsourcing.serialization.interfaces can't break messaging.contracts.event.
- Position
- Below the diagonal: eventsourcing.serialization.interfaces uses a module listed above it, which is the healthy direction.
22→1 eventsourcing.snapshot uses eventsourcing.contracts.stream✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot uses a type in eventsourcing.contracts.stream.
- The types involved
src.waku.eventsourcing.snapshot.migration→src.waku.eventsourcing.contracts.stream.StreamId
- Direction
- eventsourcing.snapshot uses eventsourcing.contracts.stream, so a change to eventsourcing.contracts.stream can break eventsourcing.snapshot, while a change to eventsourcing.snapshot can't break eventsourcing.contracts.stream.
- Position
- Below the diagonal: eventsourcing.snapshot uses a module listed above it, which is the healthy direction.
22→5 eventsourcing.snapshot uses eventsourcing.snapshot.migration✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot uses a type in eventsourcing.snapshot.migration.
- The types involved
src.waku.eventsourcing.snapshot.migration→src.waku.eventsourcing.snapshot.migration.SnapshotMigrationChain
- Direction
- eventsourcing.snapshot uses eventsourcing.snapshot.migration, so a change to eventsourcing.snapshot.migration can break eventsourcing.snapshot, while a change to eventsourcing.snapshot can't break eventsourcing.snapshot.migration.
- Position
- Below the diagonal: eventsourcing.snapshot uses a module listed above it, which is the healthy direction.
22→11 eventsourcing.snapshot uses eventsourcing.snapshot.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot uses a type in eventsourcing.snapshot.interfaces.
- The types involved
src.waku.eventsourcing.snapshot.migration→src.waku.eventsourcing.snapshot.interfaces.Snapshot
- Direction
- eventsourcing.snapshot uses eventsourcing.snapshot.interfaces, so a change to eventsourcing.snapshot.interfaces can break eventsourcing.snapshot, while a change to eventsourcing.snapshot can't break eventsourcing.snapshot.interfaces.
- Position
- Below the diagonal: eventsourcing.snapshot uses a module listed above it, which is the healthy direction.
23→5 eventsourcing.snapshot.registry uses eventsourcing.snapshot.migration✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot.registry uses a type in eventsourcing.snapshot.migration.
- The types involved
src.waku.eventsourcing.snapshot.registry.SnapshotConfig→src.waku.eventsourcing.snapshot.migration.SnapshotMigrationChain
- Direction
- eventsourcing.snapshot.registry uses eventsourcing.snapshot.migration, so a change to eventsourcing.snapshot.migration can break eventsourcing.snapshot.registry, while a change to eventsourcing.snapshot.registry can't break eventsourcing.snapshot.migration.
- Position
- Below the diagonal: eventsourcing.snapshot.registry uses a module listed above it, which is the healthy direction.
23→11 eventsourcing.snapshot.registry uses eventsourcing.snapshot.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot.registry uses a type in eventsourcing.snapshot.interfaces.
- The types involved
src.waku.eventsourcing.snapshot.registry.SnapshotConfig→src.waku.eventsourcing.snapshot.interfaces.ISnapshotStrategy
- Direction
- eventsourcing.snapshot.registry uses eventsourcing.snapshot.interfaces, so a change to eventsourcing.snapshot.interfaces can break eventsourcing.snapshot.registry, while a change to eventsourcing.snapshot.registry can't break eventsourcing.snapshot.interfaces.
- Position
- Below the diagonal: eventsourcing.snapshot.registry uses a module listed above it, which is the healthy direction.
24→1 eventsourcing.store.in_memory uses eventsourcing.contracts.stream✕
- Connections
- 1 pair of types, where a type in eventsourcing.store.in_memory uses a type in eventsourcing.contracts.stream.
- The types involved
src.waku.eventsourcing.store.in_memory.InMemoryEventStore→src.waku.eventsourcing.contracts.stream.StreamId
- Direction
- eventsourcing.store.in_memory uses eventsourcing.contracts.stream, so a change to eventsourcing.contracts.stream can break eventsourcing.store.in_memory, while a change to eventsourcing.store.in_memory can't break eventsourcing.contracts.stream.
- Position
- Below the diagonal: eventsourcing.store.in_memory uses a module listed above it, which is the healthy direction.
24→4 eventsourcing.store.in_memory uses eventsourcing.serialization.registry✕
- Connections
- 1 pair of types, where a type in eventsourcing.store.in_memory uses a type in eventsourcing.serialization.registry.
- The types involved
src.waku.eventsourcing.store.in_memory.InMemoryEventStore→src.waku.eventsourcing.serialization.registry.EventTypeRegistry
- Direction
- eventsourcing.store.in_memory uses eventsourcing.serialization.registry, so a change to eventsourcing.serialization.registry can break eventsourcing.store.in_memory, while a change to eventsourcing.store.in_memory can't break eventsourcing.serialization.registry.
- Position
- Below the diagonal: eventsourcing.store.in_memory uses a module listed above it, which is the healthy direction.
24→12 eventsourcing.store.in_memory uses eventsourcing.store.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.store.in_memory uses a type in eventsourcing.store.interfaces.
- The types involved
src.waku.eventsourcing.store.in_memory.InMemoryEventStore→src.waku.eventsourcing.store.interfaces.IEventStore
- Direction
- eventsourcing.store.in_memory uses eventsourcing.store.interfaces, so a change to eventsourcing.store.interfaces can break eventsourcing.store.in_memory, while a change to eventsourcing.store.in_memory can't break eventsourcing.store.interfaces.
- Position
- Below the diagonal: eventsourcing.store.in_memory uses a module listed above it, which is the healthy direction.
25→7 messaging.impl uses messaging.contracts.message✕
- Connections
- 1 pair of types, where a type in messaging.impl uses a type in messaging.contracts.message.
- The types involved
src.waku.messaging.impl.MessageBus→src.waku.messaging.contracts.message.IMessage
- Direction
- messaging.impl uses messaging.contracts.message, so a change to messaging.contracts.message can break messaging.impl, while a change to messaging.impl can't break messaging.contracts.message.
- Position
- Below the diagonal: messaging.impl uses a module listed above it, which is the healthy direction.
25→14 messaging.impl uses messaging.interfaces✕
- Connections
- 1 pair of types, where a type in messaging.impl uses a type in messaging.interfaces.
- The types involved
src.waku.messaging.impl.MessageBus→src.waku.messaging.interfaces.IMessageBus
- Direction
- messaging.impl uses messaging.interfaces, so a change to messaging.interfaces can break messaging.impl, while a change to messaging.impl can't break messaging.interfaces.
- Position
- Below the diagonal: messaging.impl uses a module listed above it, which is the healthy direction.
26→9 modules._registry uses modules._metadata✕
- Connections
- 1 pair of types, where a type in modules._registry uses a type in modules._metadata.
- The types involved
src.waku.modules._registry.ModuleRegistry→src.waku.modules._metadata.ModuleCompiler
- Direction
- modules._registry uses modules._metadata, so a change to modules._metadata can break modules._registry, while a change to modules._registry can't break modules._metadata.
- Position
- Below the diagonal: modules._registry uses a module listed above it, which is the healthy direction.
26→16 modules._registry uses modules._module✕
- Connections
- 1 pair of types, where a type in modules._registry uses a type in modules._module.
- The types involved
src.waku.modules._registry.ModuleRegistry→src.waku.modules._module.Module
- Direction
- modules._registry uses modules._module, so a change to modules._module can break modules._registry, while a change to modules._registry can't break modules._module.
- Position
- Below the diagonal: modules._registry uses a module listed above it, which is the healthy direction.
27→26 application uses modules._registry✕
- Connections
- 1 pair of types, where a type in application uses a type in modules._registry.
- The types involved
src.waku.application.WakuApplication→src.waku.modules._registry.ModuleRegistry
- Direction
- application uses modules._registry, so a change to modules._registry can break application, while a change to application can't break modules._registry.
- Position
- Below the diagonal: application uses a module listed above it, which is the healthy direction.
28→1 eventsourcing.decider.repository uses eventsourcing.contracts.stream✕
- Connections
- 1 pair of types, where a type in eventsourcing.decider.repository uses a type in eventsourcing.contracts.stream.
- The types involved
src.waku.eventsourcing.decider.repository.DeciderRepository→src.waku.eventsourcing.contracts.stream.StreamId
- Direction
- eventsourcing.decider.repository uses eventsourcing.contracts.stream, so a change to eventsourcing.contracts.stream can break eventsourcing.decider.repository, while a change to eventsourcing.decider.repository can't break eventsourcing.contracts.stream.
- Position
- Below the diagonal: eventsourcing.decider.repository uses a module listed above it, which is the healthy direction.
28→11 eventsourcing.decider.repository uses eventsourcing.snapshot.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.decider.repository uses a type in eventsourcing.snapshot.interfaces.
- The types involved
src.waku.eventsourcing.decider.repository.SnapshotDeciderRepository→src.waku.eventsourcing.snapshot.interfaces.ISnapshotStore
- Direction
- eventsourcing.decider.repository uses eventsourcing.snapshot.interfaces, so a change to eventsourcing.snapshot.interfaces can break eventsourcing.decider.repository, while a change to eventsourcing.decider.repository can't break eventsourcing.snapshot.interfaces.
- Position
- Below the diagonal: eventsourcing.decider.repository uses a module listed above it, which is the healthy direction.
28→12 eventsourcing.decider.repository uses eventsourcing.store.interfaces✕
- Connections
- 2 pairs of types, where a type in eventsourcing.decider.repository uses a type in eventsourcing.store.interfaces.
- The types involved
src.waku.eventsourcing.decider.repository.DeciderRepository→src.waku.eventsourcing.store.interfaces.IEventStoresrc.waku.eventsourcing.decider.repository.SnapshotDeciderRepository→src.waku.eventsourcing.store.interfaces.IEventStore
- Direction
- eventsourcing.decider.repository uses eventsourcing.store.interfaces, so a change to eventsourcing.store.interfaces can break eventsourcing.decider.repository, while a change to eventsourcing.decider.repository can't break eventsourcing.store.interfaces.
- Position
- Below the diagonal: eventsourcing.decider.repository uses a module listed above it, which is the healthy direction.
28→21 eventsourcing.decider.repository uses eventsourcing.serialization.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.decider.repository uses a type in eventsourcing.serialization.interfaces.
- The types involved
src.waku.eventsourcing.decider.repository.SnapshotDeciderRepository→src.waku.eventsourcing.serialization.interfaces.ISnapshotStateSerializer
- Direction
- eventsourcing.decider.repository uses eventsourcing.serialization.interfaces, so a change to eventsourcing.serialization.interfaces can break eventsourcing.decider.repository, while a change to eventsourcing.decider.repository can't break eventsourcing.serialization.interfaces.
- Position
- Below the diagonal: eventsourcing.decider.repository uses a module listed above it, which is the healthy direction.
28→23 eventsourcing.decider.repository uses eventsourcing.snapshot.registry✕
- Connections
- 1 pair of types, where a type in eventsourcing.decider.repository uses a type in eventsourcing.snapshot.registry.
- The types involved
src.waku.eventsourcing.decider.repository.SnapshotDeciderRepository→src.waku.eventsourcing.snapshot.registry.SnapshotConfigRegistry
- Direction
- eventsourcing.decider.repository uses eventsourcing.snapshot.registry, so a change to eventsourcing.snapshot.registry can break eventsourcing.decider.repository, while a change to eventsourcing.decider.repository can't break eventsourcing.snapshot.registry.
- Position
- Below the diagonal: eventsourcing.decider.repository uses a module listed above it, which is the healthy direction.
29→10 eventsourcing.projection.processor uses eventsourcing.projection.interfaces✕
- Connections
- 2 pairs of types, where a type in eventsourcing.projection.processor uses a type in eventsourcing.projection.interfaces.
- The types involved
src.waku.eventsourcing.projection.processor.ProjectionProcessor→src.waku.eventsourcing.projection.interfaces.ICatchUpProjectionsrc.waku.eventsourcing.projection.processor.ProjectionProcessor→src.waku.eventsourcing.projection.interfaces.ICheckpointStore
- Direction
- eventsourcing.projection.processor uses eventsourcing.projection.interfaces, so a change to eventsourcing.projection.interfaces can break eventsourcing.projection.processor, while a change to eventsourcing.projection.processor can't break eventsourcing.projection.interfaces.
- Position
- Below the diagonal: eventsourcing.projection.processor uses a module listed above it, which is the healthy direction.
29→12 eventsourcing.projection.processor uses eventsourcing.store.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.projection.processor uses a type in eventsourcing.store.interfaces.
- The types involved
src.waku.eventsourcing.projection.processor.ProjectionProcessor→src.waku.eventsourcing.store.interfaces.IEventReader
- Direction
- eventsourcing.projection.processor uses eventsourcing.store.interfaces, so a change to eventsourcing.store.interfaces can break eventsourcing.projection.processor, while a change to eventsourcing.projection.processor can't break eventsourcing.store.interfaces.
- Position
- Below the diagonal: eventsourcing.projection.processor uses a module listed above it, which is the healthy direction.
29→19 eventsourcing.projection.processor uses eventsourcing.projection.binding✕
- Connections
- 1 pair of types, where a type in eventsourcing.projection.processor uses a type in eventsourcing.projection.binding.
- The types involved
src.waku.eventsourcing.projection.processor.ProjectionProcessor→src.waku.eventsourcing.projection.binding.CatchUpProjectionBinding
- Direction
- eventsourcing.projection.processor uses eventsourcing.projection.binding, so a change to eventsourcing.projection.binding can break eventsourcing.projection.processor, while a change to eventsourcing.projection.processor can't break eventsourcing.projection.binding.
- Position
- Below the diagonal: eventsourcing.projection.processor uses a module listed above it, which is the healthy direction.
30→4 eventsourcing.serialization.json uses eventsourcing.serialization.registry✕
- Connections
- 1 pair of types, where a type in eventsourcing.serialization.json uses a type in eventsourcing.serialization.registry.
- The types involved
src.waku.eventsourcing.serialization.json.JsonEventSerializer→src.waku.eventsourcing.serialization.registry.EventTypeRegistry
- Direction
- eventsourcing.serialization.json uses eventsourcing.serialization.registry, so a change to eventsourcing.serialization.registry can break eventsourcing.serialization.json, while a change to eventsourcing.serialization.json can't break eventsourcing.serialization.registry.
- Position
- Below the diagonal: eventsourcing.serialization.json uses a module listed above it, which is the healthy direction.
30→13 eventsourcing.serialization.json uses messaging.contracts.event✕
- Connections
- 1 pair of types, where a type in eventsourcing.serialization.json uses a type in messaging.contracts.event.
- The types involved
src.waku.eventsourcing.serialization.json.JsonEventSerializer→src.waku.messaging.contracts.event.IEvent
- Direction
- eventsourcing.serialization.json uses messaging.contracts.event, so a change to messaging.contracts.event can break eventsourcing.serialization.json, while a change to eventsourcing.serialization.json can't break messaging.contracts.event.
- Position
- Below the diagonal: eventsourcing.serialization.json uses a module listed above it, which is the healthy direction.
30→21 eventsourcing.serialization.json uses eventsourcing.serialization.interfaces✕
- Connections
- 2 pairs of types, where a type in eventsourcing.serialization.json uses a type in eventsourcing.serialization.interfaces.
- The types involved
src.waku.eventsourcing.serialization.json.JsonEventSerializer→src.waku.eventsourcing.serialization.interfaces.IEventSerializersrc.waku.eventsourcing.serialization.json.JsonSnapshotStateSerializer→src.waku.eventsourcing.serialization.interfaces.ISnapshotStateSerializer
- Direction
- eventsourcing.serialization.json uses eventsourcing.serialization.interfaces, so a change to eventsourcing.serialization.interfaces can break eventsourcing.serialization.json, while a change to eventsourcing.serialization.json can't break eventsourcing.serialization.interfaces.
- Position
- Below the diagonal: eventsourcing.serialization.json uses a module listed above it, which is the healthy direction.
31→1 eventsourcing.snapshot.manager uses eventsourcing.contracts.stream✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot.manager uses a type in eventsourcing.contracts.stream.
- The types involved
src.waku.eventsourcing.snapshot.manager.SnapshotManager→src.waku.eventsourcing.contracts.stream.StreamId
- Direction
- eventsourcing.snapshot.manager uses eventsourcing.contracts.stream, so a change to eventsourcing.contracts.stream can break eventsourcing.snapshot.manager, while a change to eventsourcing.snapshot.manager can't break eventsourcing.contracts.stream.
- Position
- Below the diagonal: eventsourcing.snapshot.manager uses a module listed above it, which is the healthy direction.
31→11 eventsourcing.snapshot.manager uses eventsourcing.snapshot.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot.manager uses a type in eventsourcing.snapshot.interfaces.
- The types involved
src.waku.eventsourcing.snapshot.manager.SnapshotManager→src.waku.eventsourcing.snapshot.interfaces.ISnapshotStore
- Direction
- eventsourcing.snapshot.manager uses eventsourcing.snapshot.interfaces, so a change to eventsourcing.snapshot.interfaces can break eventsourcing.snapshot.manager, while a change to eventsourcing.snapshot.manager can't break eventsourcing.snapshot.interfaces.
- Position
- Below the diagonal: eventsourcing.snapshot.manager uses a module listed above it, which is the healthy direction.
31→23 eventsourcing.snapshot.manager uses eventsourcing.snapshot.registry✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot.manager uses a type in eventsourcing.snapshot.registry.
- The types involved
src.waku.eventsourcing.snapshot.manager.SnapshotManager→src.waku.eventsourcing.snapshot.registry.SnapshotConfig
- Direction
- eventsourcing.snapshot.manager uses eventsourcing.snapshot.registry, so a change to eventsourcing.snapshot.registry can break eventsourcing.snapshot.manager, while a change to eventsourcing.snapshot.manager can't break eventsourcing.snapshot.registry.
- Position
- Below the diagonal: eventsourcing.snapshot.manager uses a module listed above it, which is the healthy direction.
32→11 eventsourcing.snapshot.repository uses eventsourcing.snapshot.interfaces✕
- Connections
- 2 pairs of types, where a type in eventsourcing.snapshot.repository uses a type in eventsourcing.snapshot.interfaces.
- The types involved
src.waku.eventsourcing.snapshot.repository.SnapshotEventSourcedRepository→src.waku.eventsourcing.snapshot.interfaces.ISnapshotStoresrc.waku.eventsourcing.snapshot.repository.SnapshotEventSourcedRepository→src.waku.eventsourcing.snapshot.interfaces.Snapshot
- Direction
- eventsourcing.snapshot.repository uses eventsourcing.snapshot.interfaces, so a change to eventsourcing.snapshot.interfaces can break eventsourcing.snapshot.repository, while a change to eventsourcing.snapshot.repository can't break eventsourcing.snapshot.interfaces.
- Position
- Below the diagonal: eventsourcing.snapshot.repository uses a module listed above it, which is the healthy direction.
32→12 eventsourcing.snapshot.repository uses eventsourcing.store.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot.repository uses a type in eventsourcing.store.interfaces.
- The types involved
src.waku.eventsourcing.snapshot.repository.SnapshotEventSourcedRepository→src.waku.eventsourcing.store.interfaces.IEventStore
- Direction
- eventsourcing.snapshot.repository uses eventsourcing.store.interfaces, so a change to eventsourcing.store.interfaces can break eventsourcing.snapshot.repository, while a change to eventsourcing.snapshot.repository can't break eventsourcing.store.interfaces.
- Position
- Below the diagonal: eventsourcing.snapshot.repository uses a module listed above it, which is the healthy direction.
32→20 eventsourcing.snapshot.repository uses eventsourcing.repository✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot.repository uses a type in eventsourcing.repository.
- The types involved
src.waku.eventsourcing.snapshot.repository.SnapshotEventSourcedRepository→src.waku.eventsourcing.repository.EventSourcedRepository
- Direction
- eventsourcing.snapshot.repository uses eventsourcing.repository, so a change to eventsourcing.repository can break eventsourcing.snapshot.repository, while a change to eventsourcing.snapshot.repository can't break eventsourcing.repository.
- Position
- Below the diagonal: eventsourcing.snapshot.repository uses a module listed above it, which is the healthy direction.
32→21 eventsourcing.snapshot.repository uses eventsourcing.serialization.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot.repository uses a type in eventsourcing.serialization.interfaces.
- The types involved
src.waku.eventsourcing.snapshot.repository.SnapshotEventSourcedRepository→src.waku.eventsourcing.serialization.interfaces.ISnapshotStateSerializer
- Direction
- eventsourcing.snapshot.repository uses eventsourcing.serialization.interfaces, so a change to eventsourcing.serialization.interfaces can break eventsourcing.snapshot.repository, while a change to eventsourcing.snapshot.repository can't break eventsourcing.serialization.interfaces.
- Position
- Below the diagonal: eventsourcing.snapshot.repository uses a module listed above it, which is the healthy direction.
32→23 eventsourcing.snapshot.repository uses eventsourcing.snapshot.registry✕
- Connections
- 1 pair of types, where a type in eventsourcing.snapshot.repository uses a type in eventsourcing.snapshot.registry.
- The types involved
src.waku.eventsourcing.snapshot.repository.SnapshotEventSourcedRepository→src.waku.eventsourcing.snapshot.registry.SnapshotConfigRegistry
- Direction
- eventsourcing.snapshot.repository uses eventsourcing.snapshot.registry, so a change to eventsourcing.snapshot.registry can break eventsourcing.snapshot.repository, while a change to eventsourcing.snapshot.repository can't break eventsourcing.snapshot.registry.
- Position
- Below the diagonal: eventsourcing.snapshot.repository uses a module listed above it, which is the healthy direction.
33→1 eventsourcing.store.sqlalchemy.store uses eventsourcing.contracts.stream✕
- Connections
- 1 pair of types, where a type in eventsourcing.store.sqlalchemy.store uses a type in eventsourcing.contracts.stream.
- The types involved
src.waku.eventsourcing.store.sqlalchemy.store.SqlAlchemyEventStore→src.waku.eventsourcing.contracts.stream.StreamId
- Direction
- eventsourcing.store.sqlalchemy.store uses eventsourcing.contracts.stream, so a change to eventsourcing.contracts.stream can break eventsourcing.store.sqlalchemy.store, while a change to eventsourcing.store.sqlalchemy.store can't break eventsourcing.contracts.stream.
- Position
- Below the diagonal: eventsourcing.store.sqlalchemy.store uses a module listed above it, which is the healthy direction.
33→4 eventsourcing.store.sqlalchemy.store uses eventsourcing.serialization.registry✕
- Connections
- 2 pairs of types, where a type in eventsourcing.store.sqlalchemy.store uses a type in eventsourcing.serialization.registry.
- The types involved
src.waku.eventsourcing.store.sqlalchemy.store.SqlAlchemyEventStore→src.waku.eventsourcing.serialization.registry.EventTypeRegistrysrc.waku.eventsourcing.store.sqlalchemy.store.SqlAlchemyEventStoreFactory→src.waku.eventsourcing.serialization.registry.EventTypeRegistry
- Direction
- eventsourcing.store.sqlalchemy.store uses eventsourcing.serialization.registry, so a change to eventsourcing.serialization.registry can break eventsourcing.store.sqlalchemy.store, while a change to eventsourcing.store.sqlalchemy.store can't break eventsourcing.serialization.registry.
- Position
- Below the diagonal: eventsourcing.store.sqlalchemy.store uses a module listed above it, which is the healthy direction.
33→12 eventsourcing.store.sqlalchemy.store uses eventsourcing.store.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.store.sqlalchemy.store uses a type in eventsourcing.store.interfaces.
- The types involved
src.waku.eventsourcing.store.sqlalchemy.store.SqlAlchemyEventStore→src.waku.eventsourcing.store.interfaces.IEventStore
- Direction
- eventsourcing.store.sqlalchemy.store uses eventsourcing.store.interfaces, so a change to eventsourcing.store.interfaces can break eventsourcing.store.sqlalchemy.store, while a change to eventsourcing.store.sqlalchemy.store can't break eventsourcing.store.interfaces.
- Position
- Below the diagonal: eventsourcing.store.sqlalchemy.store uses a module listed above it, which is the healthy direction.
33→21 eventsourcing.store.sqlalchemy.store uses eventsourcing.serialization.interfaces✕
- Connections
- 2 pairs of types, where a type in eventsourcing.store.sqlalchemy.store uses a type in eventsourcing.serialization.interfaces.
- The types involved
src.waku.eventsourcing.store.sqlalchemy.store.SqlAlchemyEventStore→src.waku.eventsourcing.serialization.interfaces.IEventSerializersrc.waku.eventsourcing.store.sqlalchemy.store.SqlAlchemyEventStoreFactory→src.waku.eventsourcing.serialization.interfaces.IEventSerializer
- Direction
- eventsourcing.store.sqlalchemy.store uses eventsourcing.serialization.interfaces, so a change to eventsourcing.serialization.interfaces can break eventsourcing.store.sqlalchemy.store, while a change to eventsourcing.store.sqlalchemy.store can't break eventsourcing.serialization.interfaces.
- Position
- Below the diagonal: eventsourcing.store.sqlalchemy.store uses a module listed above it, which is the healthy direction.
34→3 eventsourcing.projection.runner uses eventsourcing.projection.lock.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.projection.runner uses a type in eventsourcing.projection.lock.interfaces.
- The types involved
src.waku.eventsourcing.projection.runner.CatchUpProjectionRunner→src.waku.eventsourcing.projection.lock.interfaces.IProjectionLock
- Direction
- eventsourcing.projection.runner uses eventsourcing.projection.lock.interfaces, so a change to eventsourcing.projection.lock.interfaces can break eventsourcing.projection.runner, while a change to eventsourcing.projection.runner can't break eventsourcing.projection.lock.interfaces.
- Position
- Below the diagonal: eventsourcing.projection.runner uses a module listed above it, which is the healthy direction.
34→19 eventsourcing.projection.runner uses eventsourcing.projection.binding✕
- Connections
- 1 pair of types, where a type in eventsourcing.projection.runner uses a type in eventsourcing.projection.binding.
- The types involved
src.waku.eventsourcing.projection.runner.CatchUpProjectionRunner→src.waku.eventsourcing.projection.binding.CatchUpProjectionBinding
- Direction
- eventsourcing.projection.runner uses eventsourcing.projection.binding, so a change to eventsourcing.projection.binding can break eventsourcing.projection.runner, while a change to eventsourcing.projection.runner can't break eventsourcing.projection.binding.
- Position
- Below the diagonal: eventsourcing.projection.runner uses a module listed above it, which is the healthy direction.
34→29 eventsourcing.projection.runner uses eventsourcing.projection.processor✕
- Connections
- 1 pair of types, where a type in eventsourcing.projection.runner uses a type in eventsourcing.projection.processor.
- The types involved
src.waku.eventsourcing.projection.runner.CatchUpProjectionRunner→src.waku.eventsourcing.projection.processor.ProjectionProcessor
- Direction
- eventsourcing.projection.runner uses eventsourcing.projection.processor, so a change to eventsourcing.projection.processor can break eventsourcing.projection.runner, while a change to eventsourcing.projection.runner can't break eventsourcing.projection.processor.
- Position
- Below the diagonal: eventsourcing.projection.runner uses a module listed above it, which is the healthy direction.
35→4 eventsourcing.store.sqlalchemy uses eventsourcing.serialization.registry✕
- Connections
- 1 pair of types, where a type in eventsourcing.store.sqlalchemy uses a type in eventsourcing.serialization.registry.
- The types involved
src.waku.eventsourcing.store.sqlalchemy._serialization→src.waku.eventsourcing.serialization.registry.EventTypeRegistry
- Direction
- eventsourcing.store.sqlalchemy uses eventsourcing.serialization.registry, so a change to eventsourcing.serialization.registry can break eventsourcing.store.sqlalchemy, while a change to eventsourcing.store.sqlalchemy can't break eventsourcing.serialization.registry.
- Position
- Below the diagonal: eventsourcing.store.sqlalchemy uses a module listed above it, which is the healthy direction.
35→18 eventsourcing.store.sqlalchemy uses eventsourcing.contracts.event✕
- Connections
- 2 pairs of types, where a type in eventsourcing.store.sqlalchemy uses a type in eventsourcing.contracts.event.
- The types involved
src.waku.eventsourcing.store.sqlalchemy._serialization→src.waku.eventsourcing.contracts.event.EventMetadatasrc.waku.eventsourcing.store.sqlalchemy._serialization→src.waku.eventsourcing.contracts.event.StoredEvent
- Direction
- eventsourcing.store.sqlalchemy uses eventsourcing.contracts.event, so a change to eventsourcing.contracts.event can break eventsourcing.store.sqlalchemy, while a change to eventsourcing.store.sqlalchemy can't break eventsourcing.contracts.event.
- Position
- Below the diagonal: eventsourcing.store.sqlalchemy uses a module listed above it, which is the healthy direction.
35→21 eventsourcing.store.sqlalchemy uses eventsourcing.serialization.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.store.sqlalchemy uses a type in eventsourcing.serialization.interfaces.
- The types involved
src.waku.eventsourcing.store.sqlalchemy._serialization→src.waku.eventsourcing.serialization.interfaces.IEventSerializer
- Direction
- eventsourcing.store.sqlalchemy uses eventsourcing.serialization.interfaces, so a change to eventsourcing.serialization.interfaces can break eventsourcing.store.sqlalchemy, while a change to eventsourcing.store.sqlalchemy can't break eventsourcing.serialization.interfaces.
- Position
- Below the diagonal: eventsourcing.store.sqlalchemy uses a module listed above it, which is the healthy direction.
35→33 eventsourcing.store.sqlalchemy uses eventsourcing.store.sqlalchemy.store✕
- Connections
- 1 pair of types, where a type in eventsourcing.store.sqlalchemy uses a type in eventsourcing.store.sqlalchemy.store.
- The types involved
src.waku.eventsourcing.store.sqlalchemy.store→src.waku.eventsourcing.store.sqlalchemy.store.SqlAlchemyEventStoreFactory
- Direction
- eventsourcing.store.sqlalchemy uses eventsourcing.store.sqlalchemy.store, so a change to eventsourcing.store.sqlalchemy.store can break eventsourcing.store.sqlalchemy, while a change to eventsourcing.store.sqlalchemy can't break eventsourcing.store.sqlalchemy.store.
- Position
- Below the diagonal: eventsourcing.store.sqlalchemy uses a module listed above it, which is the healthy direction.
36→9 extensions.protocols uses modules._metadata✕
- Connections
- 1 pair of types, where a type in extensions.protocols uses a type in modules._metadata.
- The types involved
src.waku.extensions.protocols.OnModuleConfigure→src.waku.modules._metadata.ModuleMetadata
- Direction
- extensions.protocols uses modules._metadata, so a change to modules._metadata can break extensions.protocols, while a change to extensions.protocols can't break modules._metadata.
- Position
- Below the diagonal: extensions.protocols uses a module listed above it, which is the healthy direction.
36→15 extensions.protocols uses modules._metadata_registry✕
- Connections
- 1 pair of types, where a type in extensions.protocols uses a type in modules._metadata_registry.
- The types involved
src.waku.extensions.protocols.OnModuleRegistration→src.waku.modules._metadata_registry.ModuleMetadataRegistry
- Direction
- extensions.protocols uses modules._metadata_registry, so a change to modules._metadata_registry can break extensions.protocols, while a change to extensions.protocols can't break modules._metadata_registry.
- Position
- Below the diagonal: extensions.protocols uses a module listed above it, which is the healthy direction.
36→16 extensions.protocols uses modules._module✕
- Connections
- 2 pairs of types, where a type in extensions.protocols uses a type in modules._module.
- The types involved
src.waku.extensions.protocols.OnModuleDestroy→src.waku.modules._module.Modulesrc.waku.extensions.protocols.OnModuleInit→src.waku.modules._module.Module
- Direction
- extensions.protocols uses modules._module, so a change to modules._module can break extensions.protocols, while a change to extensions.protocols can't break modules._module.
- Position
- Below the diagonal: extensions.protocols uses a module listed above it, which is the healthy direction.
36→27 extensions.protocols uses application✕
- Connections
- 3 pairs of types, where a type in extensions.protocols uses a type in application.
- The types involved
src.waku.extensions.protocols.AfterApplicationInit→src.waku.application.WakuApplicationsrc.waku.extensions.protocols.OnApplicationInit→src.waku.application.WakuApplicationsrc.waku.extensions.protocols.OnApplicationShutdown→src.waku.application.WakuApplication
- Direction
- extensions.protocols uses application, so a change to application can break extensions.protocols, while a change to extensions.protocols can't break application.
- Position
- Below the diagonal: extensions.protocols uses a module listed above it, which is the healthy direction.
37→4 eventsourcing.modules uses eventsourcing.serialization.registry✕
- Connections
- 1 pair of types, where a type in eventsourcing.modules uses a type in eventsourcing.serialization.registry.
- The types involved
src.waku.eventsourcing.modules.EventSourcingRegistryAggregator→src.waku.eventsourcing.serialization.registry.EventTypeRegistry
- Direction
- eventsourcing.modules uses eventsourcing.serialization.registry, so a change to eventsourcing.serialization.registry can break eventsourcing.modules, while a change to eventsourcing.modules can't break eventsourcing.serialization.registry.
- Position
- Below the diagonal: eventsourcing.modules uses a module listed above it, which is the healthy direction.
37→9 eventsourcing.modules uses modules._metadata✕
- Connections
- 2 pairs of types, where a type in eventsourcing.modules uses a type in modules._metadata.
- The types involved
src.waku.eventsourcing.modules.EventSourcingExtension→src.waku.modules._metadata.ModuleMetadatasrc.waku.eventsourcing.modules.EventSourcingModule→src.waku.modules._metadata.DynamicModule
- Direction
- eventsourcing.modules uses modules._metadata, so a change to modules._metadata can break eventsourcing.modules, while a change to eventsourcing.modules can't break modules._metadata.
- Position
- Below the diagonal: eventsourcing.modules uses a module listed above it, which is the healthy direction.
37→10 eventsourcing.modules uses eventsourcing.projection.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.modules uses a type in eventsourcing.projection.interfaces.
- The types involved
src.waku.eventsourcing.modules.EventSourcingExtension→src.waku.eventsourcing.projection.interfaces.ErrorPolicy
- Direction
- eventsourcing.modules uses eventsourcing.projection.interfaces, so a change to eventsourcing.projection.interfaces can break eventsourcing.modules, while a change to eventsourcing.modules can't break eventsourcing.projection.interfaces.
- Position
- Below the diagonal: eventsourcing.modules uses a module listed above it, which is the healthy direction.
37→11 eventsourcing.modules uses eventsourcing.snapshot.interfaces✕
- Connections
- 1 pair of types, where a type in eventsourcing.modules uses a type in eventsourcing.snapshot.interfaces.
- The types involved
src.waku.eventsourcing.modules.SnapshotOptions→src.waku.eventsourcing.snapshot.interfaces.ISnapshotStrategy
- Direction
- eventsourcing.modules uses eventsourcing.snapshot.interfaces, so a change to eventsourcing.snapshot.interfaces can break eventsourcing.modules, while a change to eventsourcing.modules can't break eventsourcing.snapshot.interfaces.
- Position
- Below the diagonal: eventsourcing.modules uses a module listed above it, which is the healthy direction.
37→15 eventsourcing.modules uses modules._metadata_registry✕
- Connections
- 1 pair of types, where a type in eventsourcing.modules uses a type in modules._metadata_registry.
- The types involved
src.waku.eventsourcing.modules.EventSourcingRegistryAggregator→src.waku.modules._metadata_registry.ModuleMetadataRegistry
- Direction
- eventsourcing.modules uses modules._metadata_registry, so a change to modules._metadata_registry can break eventsourcing.modules, while a change to eventsourcing.modules can't break modules._metadata_registry.
- Position
- Below the diagonal: eventsourcing.modules uses a module listed above it, which is the healthy direction.
37→23 eventsourcing.modules uses eventsourcing.snapshot.registry✕
- Connections
- 1 pair of types, where a type in eventsourcing.modules uses a type in eventsourcing.snapshot.registry.
- The types involved
src.waku.eventsourcing.modules.EventSourcingRegistryAggregator→src.waku.eventsourcing.snapshot.registry.SnapshotConfigRegistry
- Direction
- eventsourcing.modules uses eventsourcing.snapshot.registry, so a change to eventsourcing.snapshot.registry can break eventsourcing.modules, while a change to eventsourcing.modules can't break eventsourcing.snapshot.registry.
- Position
- Below the diagonal: eventsourcing.modules uses a module listed above it, which is the healthy direction.
37→36 eventsourcing.modules uses extensions.protocols✕
- Connections
- 2 pairs of types, where a type in eventsourcing.modules uses a type in extensions.protocols.
- The types involved
src.waku.eventsourcing.modules.EventSourcingExtension→src.waku.extensions.protocols.OnModuleConfiguresrc.waku.eventsourcing.modules.EventSourcingRegistryAggregator→src.waku.extensions.protocols.OnModuleRegistration
- Direction
- eventsourcing.modules uses extensions.protocols, so a change to extensions.protocols can break eventsourcing.modules, while a change to eventsourcing.modules can't break extensions.protocols.
- Position
- Below the diagonal: eventsourcing.modules uses a module listed above it, which is the healthy direction.
38→8 messaging.modules uses messaging.registry✕
- Connections
- 2 pairs of types, where a type in messaging.modules uses a type in messaging.registry.
- The types involved
src.waku.messaging.modules.MessageRegistryAggregator→src.waku.messaging.registry.MessageRegistrysrc.waku.messaging.modules.MessagingExtension→src.waku.messaging.registry.MessageRegistry
- Direction
- messaging.modules uses messaging.registry, so a change to messaging.registry can break messaging.modules, while a change to messaging.modules can't break messaging.registry.
- Position
- Below the diagonal: messaging.modules uses a module listed above it, which is the healthy direction.
38→9 messaging.modules uses modules._metadata✕
- Connections
- 1 pair of types, where a type in messaging.modules uses a type in modules._metadata.
- The types involved
src.waku.messaging.modules.MessagingModule→src.waku.modules._metadata.DynamicModule
- Direction
- messaging.modules uses modules._metadata, so a change to modules._metadata can break messaging.modules, while a change to messaging.modules can't break modules._metadata.
- Position
- Below the diagonal: messaging.modules uses a module listed above it, which is the healthy direction.
38→15 messaging.modules uses modules._metadata_registry✕
- Connections
- 1 pair of types, where a type in messaging.modules uses a type in modules._metadata_registry.
- The types involved
src.waku.messaging.modules.MessageRegistryAggregator→src.waku.modules._metadata_registry.ModuleMetadataRegistry
- Direction
- messaging.modules uses modules._metadata_registry, so a change to modules._metadata_registry can break messaging.modules, while a change to messaging.modules can't break modules._metadata_registry.
- Position
- Below the diagonal: messaging.modules uses a module listed above it, which is the healthy direction.
38→36 messaging.modules uses extensions.protocols✕
- Connections
- 4 pairs of types, where a type in messaging.modules uses a type in extensions.protocols.
- The types involved
src.waku.messaging.modules.EndpointLifecycleExtension→src.waku.extensions.protocols.AfterApplicationInitsrc.waku.messaging.modules.EndpointLifecycleExtension→src.waku.extensions.protocols.OnApplicationShutdownsrc.waku.messaging.modules.MessageRegistryAggregator→src.waku.extensions.protocols.OnModuleRegistrationsrc.waku.messaging.modules.MessagingExtension→src.waku.extensions.protocols.OnModuleConfigure
- Direction
- messaging.modules uses extensions.protocols, so a change to extensions.protocols can break messaging.modules, while a change to messaging.modules can't break extensions.protocols.
- Position
- Below the diagonal: messaging.modules uses a module listed above it, which is the healthy direction.
39→27 validation._extension uses application✕
- Connections
- 2 pairs of types, where a type in validation._extension uses a type in application.
- The types involved
src.waku.validation._extension.ValidationContext→src.waku.application.WakuApplicationsrc.waku.validation._extension.ValidationExtension→src.waku.application.WakuApplication
- Direction
- validation._extension uses application, so a change to application can break validation._extension, while a change to validation._extension can't break application.
- Position
- Below the diagonal: validation._extension uses a module listed above it, which is the healthy direction.
39→36 validation._extension uses extensions.protocols✕
- Connections
- 1 pair of types, where a type in validation._extension uses a type in extensions.protocols.
- The types involved
src.waku.validation._extension.ValidationExtension→src.waku.extensions.protocols.AfterApplicationInit
- Direction
- validation._extension uses extensions.protocols, so a change to extensions.protocols can break validation._extension, while a change to validation._extension can't break extensions.protocols.
- Position
- Below the diagonal: validation._extension uses a module listed above it, which is the healthy direction.
40→16 validation.rules.dependency_accessible uses modules._module✕
- Connections
- 7 pairs of types, where a type in validation.rules.dependency_accessible uses a type in modules._module.
- The types involved
src.waku.validation.rules.dependency_accessible.AccessibilityStrategy→src.waku.modules._module.Modulesrc.waku.validation.rules.dependency_accessible.ContextVarsStrategy→src.waku.modules._module.Modulesrc.waku.validation.rules.dependency_accessible.DependencyAccessChecker→src.waku.modules._module.Modulesrc.waku.validation.rules.dependency_accessible.DependencyInaccessibleError→src.waku.modules._module.Modulesrc.waku.validation.rules.dependency_accessible.GlobalProvidersStrategy→src.waku.modules._module.Modulesrc.waku.validation.rules.dependency_accessible.ImportedModulesStrategy→src.waku.modules._module.Modulesrc.waku.validation.rules.dependency_accessible.LocalProvidersStrategy→src.waku.modules._module.Module
- Direction
- validation.rules.dependency_accessible uses modules._module, so a change to modules._module can break validation.rules.dependency_accessible, while a change to validation.rules.dependency_accessible can't break modules._module.
- Position
- Below the diagonal: validation.rules.dependency_accessible uses a module listed above it, which is the healthy direction.
40→26 validation.rules.dependency_accessible uses modules._registry✕
- Connections
- 2 pairs of types, where a type in validation.rules.dependency_accessible uses a type in modules._registry.
- The types involved
src.waku.validation.rules.dependency_accessible.GlobalProvidersStrategy→src.waku.modules._registry.ModuleRegistrysrc.waku.validation.rules.dependency_accessible.ImportedModulesStrategy→src.waku.modules._registry.ModuleRegistry
- Direction
- validation.rules.dependency_accessible uses modules._registry, so a change to modules._registry can break validation.rules.dependency_accessible, while a change to validation.rules.dependency_accessible can't break modules._registry.
- Position
- Below the diagonal: validation.rules.dependency_accessible uses a module listed above it, which is the healthy direction.
40→39 validation.rules.dependency_accessible uses validation._extension✕
- Connections
- 1 pair of types, where a type in validation.rules.dependency_accessible uses a type in validation._extension.
- The types involved
src.waku.validation.rules.dependency_accessible.DependenciesAccessibleRule→src.waku.validation._extension.ValidationContext
- Direction
- validation.rules.dependency_accessible uses validation._extension, so a change to validation._extension can break validation.rules.dependency_accessible, while a change to validation.rules.dependency_accessible can't break validation._extension.
- Position
- Below the diagonal: validation.rules.dependency_accessible 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
| A05:2025 — Injection | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 39 Orphaned file finding(s) in Knowledge Freshness — start with repository.py (3), modules.py (2), store.py (2); Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 39 Orphaned file finding(s) in Knowledge Freshness — start with repository.py (3), modules.py (2), store.py (2). | +6.8 pts | Medium | Knowledge Freshness |
| Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing. | +4.5 pts | Medium | Security & performance tooling |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.8 pts | Medium | Architecture documentation |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +1.8 pts | Low | Project Cohesion |
| 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. | +2.1 pts | Medium | Documentation (README) |
| Consider OpenTelemetry tracing/metrics (opentelemetry-sdk) and a health-check endpoint (a /health route) for operability. | +1.6 pts | Medium | Observability |
| Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. | +0.6 pts | Low | Knowledge Freshness |
| 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. | +0.8 pts | Medium | Code composition |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Supply-chain Provenance & Signing: REDACTED |
| src/waku/messaging/modules.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/waku/messaging/endpoints/local_queue.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/waku/eventsourcing/_introspection.py | 8.5 | Near-clean | Cognitive Complexity: _introspection.resolve_generic_args (cognitive 17) |
| docs/code/eventsourcing/quickstart/aggregate.py | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 3) |
| examples/eventsourcing/basic_usage.py | 8.5 | Near-clean | Code Duplication: Duplicated block (13–16 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 54 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 — 54 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, 60 of 65 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 (`coverage xml`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.py), 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 (`coverage run -m pytest` then `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 (`coverage run -m pytest` then `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 (.py) and this repository declares a Python test suite (repository root, 90 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's 3 shipped Python distribution(s) across 1 manifest(s) WERE read; what went unanswered is the currency half, because it grades an EXACT pin against the newest release and every declaration here is a floor or a range — which installs the newest release it admits and so cannot be behind one. So pypi.org was never asked. This is a true statement about the repository, and the healthy one, NOT a gap on our side: no reader we could write would find a currency question here.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 629 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 2 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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/waku/eventsourcing/store/in_memory.py`, `src/waku/eventsourcing/store/sqlalchemy/store.py` 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.
- 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 dishka, 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — 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 personal data 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 personal data controls.
- 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 Python 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 Python 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.
- X16 Unfloored truncation loop — 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, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, 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.
- X18 Disposal-pattern 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, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP 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.
- 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.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python 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.
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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was _introspection.resolve_generic_args at 17.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with _introspection.resolve_generic_args (cognitive 17). — Refactoring it lifts Cognitive Complexity from 9.8 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
2 duplicated block group(s) detected. 1 of the 2 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 1 Duplicated block (8 lines × 3) finding(s) in Code Duplication — start with aggregate.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (13–16 lines × 2) finding(s) in Code Duplication — start with basic_usage.py. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 51 classes have LCOM4 above 3.
D9 · Test Distribution
701 test methods: 676 unit, 25 integration, 0 BDD, 0 e2e. The Python suite contributes 701 test function(s) across 88 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 5 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 3 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (2 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
2 deducted task-comment markers across 8817 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 2 TodoComment finding(s) in Explicit Debt — start with modules.py, local_queue.py. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 36 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 1 build units (Python) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
69 % of calls cross a namespace and 7 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. 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)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. semgrep hit a parse error in 2 file(s) — `src/waku/eventsourcing/store/in_memory.py`, `src/waku/eventsourcing/store/sqlalchemy/store.py` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. 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 4 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
8 finding(s): 2 critical, 3 high, 3 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
39 of 39 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/waku/eventsourcing/modules.py. Counted over 39 of the 128 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 39 Orphaned file finding(s) in Knowledge Freshness — start with repository.py (3), modules.py (2), store.py (2). — One of this dimension's main actionable groups (39 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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 1 platform declaration(s) and 3 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
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 a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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
P10 · Library API & versioning
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-sdk) and a health-check endpoint (a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 32573 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:5
What to do
- Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `https://context7.com/widget.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — overrides/main.html:5
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 100% | Exemplary | Solid. |
| Architecture | 79% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 62% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 66% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 83% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data 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 personal data 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.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves 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, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store 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 on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported 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 on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~11225 lines of test source are present (.py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .py suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — no declaration carries an exact pin to grade
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- 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; Python not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Python 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. Aggregate roots were found in only one source directory (docs), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, 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
- D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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 Python 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 (5 signals for this style, 3 needed — the count is met but a required primary signal is absent): 3 aggregate root(s) (entities that raise its domain events); 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 56 value object(s); 25 domain event(s); a Domain/Aggregates/ValueObjects layer; 2 repository port(s) loading or saving an aggregate/entity; a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- 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 (an append-only event-store seam (IEventStore/Append-of-events))
- 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 36 current-state document(s) make no claim of a kind M4 checks. 5 claim(s) of kinds M4 does not check were not checked (environment variable 5); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Python source (service entry point: docs/code/providers/scopes/contextual_real.py:1 (from fastapi))
- P8 Schema migrations — SQLAlchemy 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 (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X16 Unfloored truncation loop — 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
- X18 Disposal-pattern 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
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- 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.
- 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.
- X5 Nullable reference types — 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
- 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 — 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- TodoComment src/waku/messaging/modules.py:190
- TodoComment src/waku/messaging/endpoints/local_queue.py:111
- _introspection.resolve_generic_args (cognitive 17) src/waku/eventsourcing/_introspection.py:20
- Duplicated block (8 lines × 3) docs/code/eventsourcing/quickstart/aggregate.py:33
- Duplicated block (13–16 lines × 2) examples/eventsourcing/basic_usage.py:215
- Third-party script without Subresource Integrity overrides/main.html:5
Minor — 46 finding(s)
- Orphaned file src/waku/eventsourcing/modules.py:1
- Orphaned file src/waku/eventsourcing/store/sqlalchemy/store.py:1
- Orphaned file src/waku/messaging/modules.py:1
- Orphaned file src/waku/eventsourcing/store/in_memory.py:1
- Orphaned file src/waku/validation/rules/dependency_accessible.py:1
- Orphaned file src/waku/eventsourcing/testing.py:1
- Orphaned file src/waku/testing.py:1
- Orphaned file src/waku/eventsourcing/decider/repository.py:1
- Orphaned file src/waku/eventsourcing/projection/runner.py:1
- Orphaned file src/waku/messaging/routing_builder.py:1
- Orphaned file src/waku/di/_providers.py:1
- Orphaned file src/waku/eventsourcing/exceptions.py:1
- Orphaned file src/waku/modules/_registry_builder.py:1
- Orphaned file src/waku/eventsourcing/projection/processor.py:1
- Orphaned file gitlint_plugins.py:1
- Orphaned file src/waku/modules/_metadata.py:1
- Orphaned file src/waku/messaging/endpoints/local_queue.py:1
- Orphaned file src/waku/eventsourcing/decider/handler.py:1
- Orphaned file src/waku/application.py:1
- Orphaned file src/waku/eventsourcing/repository.py:1
- Orphaned file src/waku/eventsourcing/handler.py:1
- Orphaned file src/waku/eventsourcing/projection/lock/sqlalchemy/lock.py:1
- Orphaned file src/waku/eventsourcing/snapshot/repository.py:1
- Orphaned file src/waku/extensions/protocols.py:1
- Orphaned file src/waku/eventsourcing/__init__.py:1
- Duplicated predicate src/waku/eventsourcing/decider/handler.py:40
- Duplicated predicate src/waku/eventsourcing/decider/repository.py:183
- Projects may be oversized for their cohesion
- Dormant codebase
- REDACTED
- No ADRs
- No SAST REDACTED:5
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — Python dependencies read, no exact pin to grade for currency
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-835b11cd285f40308e45acea28162f21/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-835b11cd285f40308e45acea28162f21/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 3 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 8 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | 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 2 file(s) — `src/waku/eventsourcing/store/in_memory.py`, `src/waku/eventsourcing/store/sqlalchemy/store.py` — so the PII/GDPR sweep did not cover them at all. | 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 |