Executive summary
logicblocks/event.store is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because we found no recorded design decisions and no architecture document or diagram. It scores 65 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Maturity, at 57, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Fixing the package under a licence on your banned list comes next, worth about 3 points. Raising Maturity to 62 would lift the score to about 66.
Twelve pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four known security holes in the packages the code depends on can be used by attackers, and one package carries licence risk. Pinning each tool to an exact version, updating the vulnerable packages and replacing or clearing the banned-licence packages would close these risks.
The product code is 11,701 lines, about €49,000 to rebuild.
If Maturity rose from 57 to 62, the lowest score rated Strong, the score would rise from 65 to about 66.
New since the last survey: 1 finding
- Dependency Vulnerabilities · REDACTED
Rebuild cost: about €49,000 · Estimate
| Cost to rebuild | €16,000 to €82,000, for 271 to 861 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. 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: 11,701 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 persistence.postgres.settings | 2 processing.broker.types | 3 processing.locks.base | 4 processing.process.base | 5 query.utilities | 6 sources.base | 7 sources.constraints | 8 store.conditions | 9 types.functions | 10 types.identifier | 11 persistence.converter | 12 persistence.postgres.query | 13 processing.broker.base | 14 processing.broker.strategies.distributed.subscriptions.stores.state.base | 15 query.clauses | 16 query.functions | 17 store.adapters.base | 18 persistence.memory.converters.clause | 19 persistence.memory.converters.function | 20 persistence.memory.converters.query | 21 persistence.postgres.converters | 22 persistence.postgres.converters.clause | 23 persistence.postgres.converters.function | 24 persistence.postgres.converters.query | 25 processing.broker.strategies.distributed.difference | 26 processing.broker.strategies.distributed.subscribers.stores.state.base | 27 store.adapters.memory.adapter | 28 store.adapters.memory.converters | 29 store.adapters.postgres.adapter | 30 store.adapters.postgres.converters | 31 store.store | 32 processing.broker.strategies.distributed.coordinator | 33 processing.broker.strategies.distributed.observer | 34 processing.broker.strategies.distributed.subscribers.stores.state | 35 processing.broker.strategies.distributed.subscribers.stores.state.postgres | 36 processing.consumers.state.base | 37 store | 38 store.adapters.postgres | 39 processing.broker.strategies.distributed.broker | 40 processing.consumers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 persistence.postgres.settings | ||||||||||||||||||||||||||||||||||||||||
| 2 processing.broker.types | ||||||||||||||||||||||||||||||||||||||||
| 3 processing.locks.base | ||||||||||||||||||||||||||||||||||||||||
| 4 processing.process.base | ||||||||||||||||||||||||||||||||||||||||
| 5 query.utilities | ||||||||||||||||||||||||||||||||||||||||
| 6 sources.base | ||||||||||||||||||||||||||||||||||||||||
| 7 sources.constraints | ||||||||||||||||||||||||||||||||||||||||
| 8 store.conditions | ||||||||||||||||||||||||||||||||||||||||
| 9 types.functions | ||||||||||||||||||||||||||||||||||||||||
| 10 types.identifier | ||||||||||||||||||||||||||||||||||||||||
| 11 persistence.converter | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 persistence.postgres.query | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 processing.broker.base | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 processing.broker.strategies.distributed.subscriptions.stores.state.base | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 query.clauses | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 query.functions | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 store.adapters.base | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 18 persistence.memory.converters.clause | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 19 persistence.memory.converters.function | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 persistence.memory.converters.query | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 persistence.postgres.converters | 1 | 1 | 8 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 persistence.postgres.converters.clause | 2 | 1 | 16 | 10 | ||||||||||||||||||||||||||||||||||||
| 23 persistence.postgres.converters.function | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 persistence.postgres.converters.query | 3 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 processing.broker.strategies.distributed.difference | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 processing.broker.strategies.distributed.subscribers.stores.state.base | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 store.adapters.memory.adapter | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 store.adapters.memory.converters | 1 | 5 | 6 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 29 store.adapters.postgres.adapter | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 store.adapters.postgres.converters | 1 | 5 | 6 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||
| 31 store.store | 3 | 1 | 3 | 4 | ||||||||||||||||||||||||||||||||||||
| 32 processing.broker.strategies.distributed.coordinator | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 processing.broker.strategies.distributed.observer | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 processing.broker.strategies.distributed.subscribers.stores.state | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 processing.broker.strategies.distributed.subscribers.stores.state.postgres | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 processing.consumers.state.base | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 store | 1 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 38 store.adapters.postgres | 1 | 2 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 39 processing.broker.strategies.distributed.broker | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 processing.consumers | 1 | 1 | 1 |
11→9 persistence.converter uses types.functions✕
- Connections
- 1 pair of types, where a type in persistence.converter uses a type in types.functions.
- The types involved
src.logicblocks.event.persistence.converter.TypeRegistryConverter→src.logicblocks.event.types.functions.Converter
- Direction
- persistence.converter uses types.functions, so a change to types.functions can break persistence.converter, while a change to persistence.converter can't break types.functions.
- Position
- Below the diagonal: persistence.converter uses a module listed above it, which is the healthy direction.
12→9 persistence.postgres.query uses types.functions✕
- Connections
- 1 pair of types, where a type in persistence.postgres.query uses a type in types.functions.
- The types involved
src.logicblocks.event.persistence.postgres.query.QueryApplier→src.logicblocks.event.types.functions.Applier
- Direction
- persistence.postgres.query uses types.functions, so a change to types.functions can break persistence.postgres.query, while a change to persistence.postgres.query can't break types.functions.
- Position
- Below the diagonal: persistence.postgres.query uses a module listed above it, which is the healthy direction.
13→4 processing.broker.base uses processing.process.base✕
- Connections
- 1 pair of types, where a type in processing.broker.base uses a type in processing.process.base.
- The types involved
src.logicblocks.event.processing.broker.base.EventBroker→src.logicblocks.event.processing.process.base.Process
- Direction
- processing.broker.base uses processing.process.base, so a change to processing.process.base can break processing.broker.base, while a change to processing.broker.base can't break processing.process.base.
- Position
- Below the diagonal: processing.broker.base uses a module listed above it, which is the healthy direction.
14→2 processing.broker.strategies.distributed.subscriptions.stores.state.base uses processing.broker.types✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.subscriptions.stores.state.base uses a type in processing.broker.types.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.subscriptions.stores.state.base.EventSubscriptionState→src.logicblocks.event.processing.broker.types.EventSubscriberKey
- Direction
- processing.broker.strategies.distributed.subscriptions.stores.state.base uses processing.broker.types, so a change to processing.broker.types can break processing.broker.strategies.distributed.subscriptions.stores.state.base, while a change to processing.broker.strategies.distributed.subscriptions.stores.state.base can't break processing.broker.types.
- Position
- Below the diagonal: processing.broker.strategies.distributed.subscriptions.stores.state.base uses a module listed above it, which is the healthy direction.
15→5 query.clauses uses query.utilities✕
- Connections
- 1 pair of types, where a type in query.clauses uses a type in query.utilities.
- The types involved
src.logicblocks.event.query.clauses.FilterClause→src.logicblocks.event.query.utilities.Path
- Direction
- query.clauses uses query.utilities, so a change to query.utilities can break query.clauses, while a change to query.clauses can't break query.utilities.
- Position
- Below the diagonal: query.clauses uses a module listed above it, which is the healthy direction.
16→5 query.functions uses query.utilities✕
- Connections
- 1 pair of types, where a type in query.functions uses a type in query.utilities.
- The types involved
src.logicblocks.event.query.functions.Similarity→src.logicblocks.event.query.utilities.Path
- Direction
- query.functions uses query.utilities, so a change to query.utilities can break query.functions, while a change to query.functions can't break query.utilities.
- Position
- Below the diagonal: query.functions uses a module listed above it, which is the healthy direction.
17→8 store.adapters.base uses store.conditions✕
- Connections
- 1 pair of types, where a type in store.adapters.base uses a type in store.conditions.
- The types involved
src.logicblocks.event.store.adapters.base.EventStorageAdapter→src.logicblocks.event.store.conditions.WriteCondition
- Direction
- store.adapters.base uses store.conditions, so a change to store.conditions can break store.adapters.base, while a change to store.adapters.base can't break store.conditions.
- Position
- Below the diagonal: store.adapters.base uses a module listed above it, which is the healthy direction.
17→10 store.adapters.base uses types.identifier✕
- Connections
- 3 pairs of types, where a type in store.adapters.base uses a type in types.identifier.
- The types involved
src.logicblocks.event.store.adapters.base.EventStorageAdapter→src.logicblocks.event.types.identifier.CategoryIdentifiersrc.logicblocks.event.store.adapters.base.EventStorageAdapter→src.logicblocks.event.types.identifier.StreamIdentifiersrc.logicblocks.event.store.adapters.base.StreamEventSerialisationGuarantee→src.logicblocks.event.types.identifier.StreamIdentifier
- Direction
- store.adapters.base uses types.identifier, so a change to types.identifier can break store.adapters.base, while a change to store.adapters.base can't break types.identifier.
- Position
- Below the diagonal: store.adapters.base uses a module listed above it, which is the healthy direction.
18→11 persistence.memory.converters.clause uses persistence.converter✕
- Connections
- 1 pair of types, where a type in persistence.memory.converters.clause uses a type in persistence.converter.
- The types involved
src.logicblocks.event.persistence.memory.converters.clause.TypeRegistryClauseConverter→src.logicblocks.event.persistence.converter.TypeRegistryConverter
- Direction
- persistence.memory.converters.clause uses persistence.converter, so a change to persistence.converter can break persistence.memory.converters.clause, while a change to persistence.memory.converters.clause can't break persistence.converter.
- Position
- Below the diagonal: persistence.memory.converters.clause uses a module listed above it, which is the healthy direction.
18→15 persistence.memory.converters.clause uses query.clauses✕
- Connections
- 5 pairs of types, where a type in persistence.memory.converters.clause uses a type in query.clauses.
- The types involved
src.logicblocks.event.persistence.memory.converters.clause.FilterClauseConverter→src.logicblocks.event.query.clauses.FilterClausesrc.logicblocks.event.persistence.memory.converters.clause.KeySetPagingClauseConverter→src.logicblocks.event.query.clauses.KeySetPagingClausesrc.logicblocks.event.persistence.memory.converters.clause.OffsetPagingClauseConverter→src.logicblocks.event.query.clauses.OffsetPagingClausesrc.logicblocks.event.persistence.memory.converters.clause.SortClauseConverter→src.logicblocks.event.query.clauses.SortClausesrc.logicblocks.event.persistence.memory.converters.clause.SortClauseConverter→src.logicblocks.event.query.clauses.SortField
- Direction
- persistence.memory.converters.clause uses query.clauses, so a change to query.clauses can break persistence.memory.converters.clause, while a change to persistence.memory.converters.clause can't break query.clauses.
- Position
- Below the diagonal: persistence.memory.converters.clause uses a module listed above it, which is the healthy direction.
19→11 persistence.memory.converters.function uses persistence.converter✕
- Connections
- 1 pair of types, where a type in persistence.memory.converters.function uses a type in persistence.converter.
- The types involved
src.logicblocks.event.persistence.memory.converters.function.TypeRegistryFunctionConverter→src.logicblocks.event.persistence.converter.TypeRegistryConverter
- Direction
- persistence.memory.converters.function uses persistence.converter, so a change to persistence.converter can break persistence.memory.converters.function, while a change to persistence.memory.converters.function can't break persistence.converter.
- Position
- Below the diagonal: persistence.memory.converters.function uses a module listed above it, which is the healthy direction.
19→16 persistence.memory.converters.function uses query.functions✕
- Connections
- 1 pair of types, where a type in persistence.memory.converters.function uses a type in query.functions.
- The types involved
src.logicblocks.event.persistence.memory.converters.function.SimilarityFunctionConverter→src.logicblocks.event.query.functions.Similarity
- Direction
- persistence.memory.converters.function uses query.functions, so a change to query.functions can break persistence.memory.converters.function, while a change to persistence.memory.converters.function can't break query.functions.
- Position
- Below the diagonal: persistence.memory.converters.function uses a module listed above it, which is the healthy direction.
20→9 persistence.memory.converters.query uses types.functions✕
- Connections
- 1 pair of types, where a type in persistence.memory.converters.query uses a type in types.functions.
- The types involved
src.logicblocks.event.persistence.memory.converters.query.DelegatingQueryConverter→src.logicblocks.event.types.functions.Converter
- Direction
- persistence.memory.converters.query uses types.functions, so a change to types.functions can break persistence.memory.converters.query, while a change to persistence.memory.converters.query can't break types.functions.
- Position
- Below the diagonal: persistence.memory.converters.query uses a module listed above it, which is the healthy direction.
20→11 persistence.memory.converters.query uses persistence.converter✕
- Connections
- 1 pair of types, where a type in persistence.memory.converters.query uses a type in persistence.converter.
- The types involved
src.logicblocks.event.persistence.memory.converters.query.TypeRegistryQueryConverter→src.logicblocks.event.persistence.converter.TypeRegistryConverter
- Direction
- persistence.memory.converters.query uses persistence.converter, so a change to persistence.converter can break persistence.memory.converters.query, while a change to persistence.memory.converters.query can't break persistence.converter.
- Position
- Below the diagonal: persistence.memory.converters.query uses a module listed above it, which is the healthy direction.
20→15 persistence.memory.converters.query uses query.clauses✕
- Connections
- 1 pair of types, where a type in persistence.memory.converters.query uses a type in query.clauses.
- The types involved
src.logicblocks.event.persistence.memory.converters.query.DelegatingQueryConverter→src.logicblocks.event.query.clauses.Clause
- Direction
- persistence.memory.converters.query uses query.clauses, so a change to query.clauses can break persistence.memory.converters.query, while a change to persistence.memory.converters.query can't break query.clauses.
- Position
- Below the diagonal: persistence.memory.converters.query uses a module listed above it, which is the healthy direction.
20→16 persistence.memory.converters.query uses query.functions✕
- Connections
- 1 pair of types, where a type in persistence.memory.converters.query uses a type in query.functions.
- The types involved
src.logicblocks.event.persistence.memory.converters.query.DelegatingQueryConverter→src.logicblocks.event.query.functions.Function
- Direction
- persistence.memory.converters.query uses query.functions, so a change to query.functions can break persistence.memory.converters.query, while a change to persistence.memory.converters.query can't break query.functions.
- Position
- Below the diagonal: persistence.memory.converters.query uses a module listed above it, which is the healthy direction.
21→1 persistence.postgres.converters uses persistence.postgres.settings✕
- Connections
- 1 pair of types, where a type in persistence.postgres.converters uses a type in persistence.postgres.settings.
- The types involved
src.logicblocks.event.persistence.postgres.converters.clause→src.logicblocks.event.persistence.postgres.settings.TableSettings
- Direction
- persistence.postgres.converters uses persistence.postgres.settings, so a change to persistence.postgres.settings can break persistence.postgres.converters, while a change to persistence.postgres.converters can't break persistence.postgres.settings.
- Position
- Below the diagonal: persistence.postgres.converters uses a module listed above it, which is the healthy direction.
21→5 persistence.postgres.converters uses query.utilities✕
- Connections
- 1 pair of types, where a type in persistence.postgres.converters uses a type in query.utilities.
- The types involved
src.logicblocks.event.persistence.postgres.converters.helpers→src.logicblocks.event.query.utilities.Path
- Direction
- persistence.postgres.converters uses query.utilities, so a change to query.utilities can break persistence.postgres.converters, while a change to persistence.postgres.converters can't break query.utilities.
- Position
- Below the diagonal: persistence.postgres.converters uses a module listed above it, which is the healthy direction.
21→12 persistence.postgres.converters uses persistence.postgres.query✕
- Connections
- 8 pairs of types, where a type in persistence.postgres.converters uses a type in persistence.postgres.query.
- The types involved
src.logicblocks.event.persistence.postgres.converters.clause→src.logicblocks.event.persistence.postgres.query.Conditionsrc.logicblocks.event.persistence.postgres.converters.clause→src.logicblocks.event.persistence.postgres.query.Constantsrc.logicblocks.event.persistence.postgres.converters.clause→src.logicblocks.event.persistence.postgres.query.Expressionsrc.logicblocks.event.persistence.postgres.converters.clause→src.logicblocks.event.persistence.postgres.query.Operatorsrc.logicblocks.event.persistence.postgres.converters.clause→src.logicblocks.event.persistence.postgres.query.Querysrc.logicblocks.event.persistence.postgres.converters.clause→src.logicblocks.event.persistence.postgres.query.SortDirectionsrc.logicblocks.event.persistence.postgres.converters.helpers→src.logicblocks.event.persistence.postgres.query.Expressionsrc.logicblocks.event.persistence.postgres.converters.helpers→src.logicblocks.event.persistence.postgres.query.Operator
- Direction
- persistence.postgres.converters uses persistence.postgres.query, so a change to persistence.postgres.query can break persistence.postgres.converters, while a change to persistence.postgres.converters can't break persistence.postgres.query.
- Position
- Below the diagonal: persistence.postgres.converters uses a module listed above it, which is the healthy direction.
21→15 persistence.postgres.converters uses query.clauses✕
- Connections
- 1 pair of types, where a type in persistence.postgres.converters uses a type in query.clauses.
- The types involved
src.logicblocks.event.persistence.postgres.converters.clause→src.logicblocks.event.query.clauses.KeySetPagingClause
- Direction
- persistence.postgres.converters uses query.clauses, so a change to query.clauses can break persistence.postgres.converters, while a change to persistence.postgres.converters can't break query.clauses.
- Position
- Below the diagonal: persistence.postgres.converters uses a module listed above it, which is the healthy direction.
21→16 persistence.postgres.converters uses query.functions✕
- Connections
- 1 pair of types, where a type in persistence.postgres.converters uses a type in query.functions.
- The types involved
src.logicblocks.event.persistence.postgres.converters.helpers→src.logicblocks.event.query.functions.Function
- Direction
- persistence.postgres.converters uses query.functions, so a change to query.functions can break persistence.postgres.converters, while a change to persistence.postgres.converters can't break query.functions.
- Position
- Below the diagonal: persistence.postgres.converters uses a module listed above it, which is the healthy direction.
22→1 persistence.postgres.converters.clause uses persistence.postgres.settings✕
- Connections
- 2 pairs of types, where a type in persistence.postgres.converters.clause uses a type in persistence.postgres.settings.
- The types involved
src.logicblocks.event.persistence.postgres.converters.clause.KeySetPagingClauseConverter→src.logicblocks.event.persistence.postgres.settings.TableSettingssrc.logicblocks.event.persistence.postgres.converters.clause.KeySetPagingClauseQueryApplier→src.logicblocks.event.persistence.postgres.settings.TableSettings
- Direction
- persistence.postgres.converters.clause uses persistence.postgres.settings, so a change to persistence.postgres.settings can break persistence.postgres.converters.clause, while a change to persistence.postgres.converters.clause can't break persistence.postgres.settings.
- Position
- Below the diagonal: persistence.postgres.converters.clause uses a module listed above it, which is the healthy direction.
22→11 persistence.postgres.converters.clause uses persistence.converter✕
- Connections
- 1 pair of types, where a type in persistence.postgres.converters.clause uses a type in persistence.converter.
- The types involved
src.logicblocks.event.persistence.postgres.converters.clause.TypeRegistryClauseConverter→src.logicblocks.event.persistence.converter.TypeRegistryConverter
- Direction
- persistence.postgres.converters.clause uses persistence.converter, so a change to persistence.converter can break persistence.postgres.converters.clause, while a change to persistence.postgres.converters.clause can't break persistence.converter.
- Position
- Below the diagonal: persistence.postgres.converters.clause uses a module listed above it, which is the healthy direction.
22→12 persistence.postgres.converters.clause uses persistence.postgres.query✕
- Connections
- 16 pairs of types, where a type in persistence.postgres.converters.clause uses a type in persistence.postgres.query.
- The types involved
src.logicblocks.event.persistence.postgres.converters.clause.FilterClauseConverter→src.logicblocks.event.persistence.postgres.query.QueryAppliersrc.logicblocks.event.persistence.postgres.converters.clause.FilterClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.Expressionsrc.logicblocks.event.persistence.postgres.converters.clause.FilterClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.Operatorsrc.logicblocks.event.persistence.postgres.converters.clause.FilterClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.Querysrc.logicblocks.event.persistence.postgres.converters.clause.FilterClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.QueryAppliersrc.logicblocks.event.persistence.postgres.converters.clause.KeySetPagingClauseConverter→src.logicblocks.event.persistence.postgres.query.QueryAppliersrc.logicblocks.event.persistence.postgres.converters.clause.KeySetPagingClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.Querysrc.logicblocks.event.persistence.postgres.converters.clause.KeySetPagingClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.QueryAppliersrc.logicblocks.event.persistence.postgres.converters.clause.OffsetPagingClauseConverter→src.logicblocks.event.persistence.postgres.query.QueryAppliersrc.logicblocks.event.persistence.postgres.converters.clause.OffsetPagingClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.Querysrc.logicblocks.event.persistence.postgres.converters.clause.OffsetPagingClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.QueryAppliersrc.logicblocks.event.persistence.postgres.converters.clause.SortClauseConverter→src.logicblocks.event.persistence.postgres.query.QueryAppliersrc.logicblocks.event.persistence.postgres.converters.clause.SortClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.Querysrc.logicblocks.event.persistence.postgres.converters.clause.SortClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.QueryAppliersrc.logicblocks.event.persistence.postgres.converters.clause.SortClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.SortBysrc.logicblocks.event.persistence.postgres.converters.clause.SortClauseQueryApplier→src.logicblocks.event.persistence.postgres.query.SortDirection
- Direction
- persistence.postgres.converters.clause uses persistence.postgres.query, so a change to persistence.postgres.query can break persistence.postgres.converters.clause, while a change to persistence.postgres.converters.clause can't break persistence.postgres.query.
- Position
- Below the diagonal: persistence.postgres.converters.clause uses a module listed above it, which is the healthy direction.
22→15 persistence.postgres.converters.clause uses query.clauses✕
- Connections
- 10 pairs of types, where a type in persistence.postgres.converters.clause uses a type in query.clauses.
- The types involved
src.logicblocks.event.persistence.postgres.converters.clause.FilterClauseConverter→src.logicblocks.event.query.clauses.FilterClausesrc.logicblocks.event.persistence.postgres.converters.clause.FilterClauseQueryApplier→src.logicblocks.event.query.clauses.FilterClausesrc.logicblocks.event.persistence.postgres.converters.clause.KeySetPagingClauseConverter→src.logicblocks.event.query.clauses.KeySetPagingClausesrc.logicblocks.event.persistence.postgres.converters.clause.KeySetPagingClauseQueryApplier→src.logicblocks.event.query.clauses.KeySetPagingClausesrc.logicblocks.event.persistence.postgres.converters.clause.OffsetPagingClauseConverter→src.logicblocks.event.query.clauses.OffsetPagingClausesrc.logicblocks.event.persistence.postgres.converters.clause.OffsetPagingClauseQueryApplier→src.logicblocks.event.query.clauses.OffsetPagingClausesrc.logicblocks.event.persistence.postgres.converters.clause.SortClauseConverter→src.logicblocks.event.query.clauses.SortClausesrc.logicblocks.event.persistence.postgres.converters.clause.SortClauseQueryApplier→src.logicblocks.event.query.clauses.SortClausesrc.logicblocks.event.persistence.postgres.converters.clause.SortClauseQueryApplier→src.logicblocks.event.query.clauses.SortFieldsrc.logicblocks.event.persistence.postgres.converters.clause.SortClauseQueryApplier→src.logicblocks.event.query.clauses.SortOrder
- Direction
- persistence.postgres.converters.clause uses query.clauses, so a change to query.clauses can break persistence.postgres.converters.clause, while a change to persistence.postgres.converters.clause can't break query.clauses.
- Position
- Below the diagonal: persistence.postgres.converters.clause uses a module listed above it, which is the healthy direction.
23→11 persistence.postgres.converters.function uses persistence.converter✕
- Connections
- 1 pair of types, where a type in persistence.postgres.converters.function uses a type in persistence.converter.
- The types involved
src.logicblocks.event.persistence.postgres.converters.function.TypeRegistryFunctionConverter→src.logicblocks.event.persistence.converter.TypeRegistryConverter
- Direction
- persistence.postgres.converters.function uses persistence.converter, so a change to persistence.converter can break persistence.postgres.converters.function, while a change to persistence.postgres.converters.function can't break persistence.converter.
- Position
- Below the diagonal: persistence.postgres.converters.function uses a module listed above it, which is the healthy direction.
23→12 persistence.postgres.converters.function uses persistence.postgres.query✕
- Connections
- 3 pairs of types, where a type in persistence.postgres.converters.function uses a type in persistence.postgres.query.
- The types involved
src.logicblocks.event.persistence.postgres.converters.function.SimilarityFunctionConverter→src.logicblocks.event.persistence.postgres.query.QueryAppliersrc.logicblocks.event.persistence.postgres.converters.function.SimilarityFunctionQueryApplier→src.logicblocks.event.persistence.postgres.query.Querysrc.logicblocks.event.persistence.postgres.converters.function.SimilarityFunctionQueryApplier→src.logicblocks.event.persistence.postgres.query.QueryApplier
- Direction
- persistence.postgres.converters.function uses persistence.postgres.query, so a change to persistence.postgres.query can break persistence.postgres.converters.function, while a change to persistence.postgres.converters.function can't break persistence.postgres.query.
- Position
- Below the diagonal: persistence.postgres.converters.function uses a module listed above it, which is the healthy direction.
23→16 persistence.postgres.converters.function uses query.functions✕
- Connections
- 2 pairs of types, where a type in persistence.postgres.converters.function uses a type in query.functions.
- The types involved
src.logicblocks.event.persistence.postgres.converters.function.SimilarityFunctionConverter→src.logicblocks.event.query.functions.Similaritysrc.logicblocks.event.persistence.postgres.converters.function.SimilarityFunctionQueryApplier→src.logicblocks.event.query.functions.Similarity
- Direction
- persistence.postgres.converters.function uses query.functions, so a change to query.functions can break persistence.postgres.converters.function, while a change to persistence.postgres.converters.function can't break query.functions.
- Position
- Below the diagonal: persistence.postgres.converters.function uses a module listed above it, which is the healthy direction.
24→1 persistence.postgres.converters.query uses persistence.postgres.settings✕
- Connections
- 3 pairs of types, where a type in persistence.postgres.converters.query uses a type in persistence.postgres.settings.
- The types involved
src.logicblocks.event.persistence.postgres.converters.query.DelegatingQueryConverter→src.logicblocks.event.persistence.postgres.settings.TableSettingssrc.logicblocks.event.persistence.postgres.converters.query.LookupQueryConverter→src.logicblocks.event.persistence.postgres.settings.TableSettingssrc.logicblocks.event.persistence.postgres.converters.query.SearchQueryConverter→src.logicblocks.event.persistence.postgres.settings.TableSettings
- Direction
- persistence.postgres.converters.query uses persistence.postgres.settings, so a change to persistence.postgres.settings can break persistence.postgres.converters.query, while a change to persistence.postgres.converters.query can't break persistence.postgres.settings.
- Position
- Below the diagonal: persistence.postgres.converters.query uses a module listed above it, which is the healthy direction.
24→9 persistence.postgres.converters.query uses types.functions✕
- Connections
- 1 pair of types, where a type in persistence.postgres.converters.query uses a type in types.functions.
- The types involved
src.logicblocks.event.persistence.postgres.converters.query.DelegatingQueryConverter→src.logicblocks.event.types.functions.Converter
- Direction
- persistence.postgres.converters.query uses types.functions, so a change to types.functions can break persistence.postgres.converters.query, while a change to persistence.postgres.converters.query can't break types.functions.
- Position
- Below the diagonal: persistence.postgres.converters.query uses a module listed above it, which is the healthy direction.
24→11 persistence.postgres.converters.query uses persistence.converter✕
- Connections
- 1 pair of types, where a type in persistence.postgres.converters.query uses a type in persistence.converter.
- The types involved
src.logicblocks.event.persistence.postgres.converters.query.TypeRegistryQueryConverter→src.logicblocks.event.persistence.converter.TypeRegistryConverter
- Direction
- persistence.postgres.converters.query uses persistence.converter, so a change to persistence.converter can break persistence.postgres.converters.query, while a change to persistence.postgres.converters.query can't break persistence.converter.
- Position
- Below the diagonal: persistence.postgres.converters.query uses a module listed above it, which is the healthy direction.
24→12 persistence.postgres.converters.query uses persistence.postgres.query✕
- Connections
- 1 pair of types, where a type in persistence.postgres.converters.query uses a type in persistence.postgres.query.
- The types involved
src.logicblocks.event.persistence.postgres.converters.query.DelegatingQueryConverter→src.logicblocks.event.persistence.postgres.query.Query
- Direction
- persistence.postgres.converters.query uses persistence.postgres.query, so a change to persistence.postgres.query can break persistence.postgres.converters.query, while a change to persistence.postgres.converters.query can't break persistence.postgres.query.
- Position
- Below the diagonal: persistence.postgres.converters.query uses a module listed above it, which is the healthy direction.
24→15 persistence.postgres.converters.query uses query.clauses✕
- Connections
- 1 pair of types, where a type in persistence.postgres.converters.query uses a type in query.clauses.
- The types involved
src.logicblocks.event.persistence.postgres.converters.query.DelegatingQueryConverter→src.logicblocks.event.query.clauses.Clause
- Direction
- persistence.postgres.converters.query uses query.clauses, so a change to query.clauses can break persistence.postgres.converters.query, while a change to persistence.postgres.converters.query can't break query.clauses.
- Position
- Below the diagonal: persistence.postgres.converters.query uses a module listed above it, which is the healthy direction.
25→2 processing.broker.strategies.distributed.difference uses processing.broker.types✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.difference uses a type in processing.broker.types.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.difference.EventSubscriptionChange→src.logicblocks.event.processing.broker.types.EventSubscriberKey
- Direction
- processing.broker.strategies.distributed.difference uses processing.broker.types, so a change to processing.broker.types can break processing.broker.strategies.distributed.difference, while a change to processing.broker.strategies.distributed.difference can't break processing.broker.types.
- Position
- Below the diagonal: processing.broker.strategies.distributed.difference uses a module listed above it, which is the healthy direction.
25→10 processing.broker.strategies.distributed.difference uses types.identifier✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.difference uses a type in types.identifier.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.difference.EventSubscriptionChange→src.logicblocks.event.types.identifier.EventSourceIdentifier
- Direction
- processing.broker.strategies.distributed.difference uses types.identifier, so a change to types.identifier can break processing.broker.strategies.distributed.difference, while a change to processing.broker.strategies.distributed.difference can't break types.identifier.
- Position
- Below the diagonal: processing.broker.strategies.distributed.difference uses a module listed above it, which is the healthy direction.
25→14 processing.broker.strategies.distributed.difference uses processing.broker.strategies.distributed.subscriptions.stores.state.base✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.difference uses a type in processing.broker.strategies.distributed.subscriptions.stores.state.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.difference.EventSubscriptionChange→src.logicblocks.event.processing.broker.strategies.distributed.subscriptions.stores.state.base.EventSubscriptionKey
- Direction
- processing.broker.strategies.distributed.difference uses processing.broker.strategies.distributed.subscriptions.stores.state.base, so a change to processing.broker.strategies.distributed.subscriptions.stores.state.base can break processing.broker.strategies.distributed.difference, while a change to processing.broker.strategies.distributed.difference can't break processing.broker.strategies.distributed.subscriptions.stores.state.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.difference uses a module listed above it, which is the healthy direction.
26→2 processing.broker.strategies.distributed.subscribers.stores.state.base uses processing.broker.types✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.subscribers.stores.state.base uses a type in processing.broker.types.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.subscribers.stores.state.base.EventSubscriberState→src.logicblocks.event.processing.broker.types.EventSubscriberKey
- Direction
- processing.broker.strategies.distributed.subscribers.stores.state.base uses processing.broker.types, so a change to processing.broker.types can break processing.broker.strategies.distributed.subscribers.stores.state.base, while a change to processing.broker.strategies.distributed.subscribers.stores.state.base can't break processing.broker.types.
- Position
- Below the diagonal: processing.broker.strategies.distributed.subscribers.stores.state.base uses a module listed above it, which is the healthy direction.
26→14 processing.broker.strategies.distributed.subscribers.stores.state.base uses processing.broker.strategies.distributed.subscriptions.stores.state.base✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.subscribers.stores.state.base uses a type in processing.broker.strategies.distributed.subscriptions.stores.state.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.subscribers.stores.state.base.EventSubscriberState→src.logicblocks.event.processing.broker.strategies.distributed.subscriptions.stores.state.base.EventSubscriptionKey
- Direction
- processing.broker.strategies.distributed.subscribers.stores.state.base uses processing.broker.strategies.distributed.subscriptions.stores.state.base, so a change to processing.broker.strategies.distributed.subscriptions.stores.state.base can break processing.broker.strategies.distributed.subscribers.stores.state.base, while a change to processing.broker.strategies.distributed.subscribers.stores.state.base can't break processing.broker.strategies.distributed.subscriptions.stores.state.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.subscribers.stores.state.base uses a module listed above it, which is the healthy direction.
27→8 store.adapters.memory.adapter uses store.conditions✕
- Connections
- 1 pair of types, where a type in store.adapters.memory.adapter uses a type in store.conditions.
- The types involved
src.logicblocks.event.store.adapters.memory.adapter.InMemoryEventStorageAdapter→src.logicblocks.event.store.conditions.WriteCondition
- Direction
- store.adapters.memory.adapter uses store.conditions, so a change to store.conditions can break store.adapters.memory.adapter, while a change to store.adapters.memory.adapter can't break store.conditions.
- Position
- Below the diagonal: store.adapters.memory.adapter uses a module listed above it, which is the healthy direction.
27→10 store.adapters.memory.adapter uses types.identifier✕
- Connections
- 2 pairs of types, where a type in store.adapters.memory.adapter uses a type in types.identifier.
- The types involved
src.logicblocks.event.store.adapters.memory.adapter.InMemoryEventStorageAdapter→src.logicblocks.event.types.identifier.CategoryIdentifiersrc.logicblocks.event.store.adapters.memory.adapter.InMemoryEventStorageAdapter→src.logicblocks.event.types.identifier.StreamIdentifier
- Direction
- store.adapters.memory.adapter uses types.identifier, so a change to types.identifier can break store.adapters.memory.adapter, while a change to store.adapters.memory.adapter can't break types.identifier.
- Position
- Below the diagonal: store.adapters.memory.adapter uses a module listed above it, which is the healthy direction.
27→17 store.adapters.memory.adapter uses store.adapters.base✕
- Connections
- 1 pair of types, where a type in store.adapters.memory.adapter uses a type in store.adapters.base.
- The types involved
src.logicblocks.event.store.adapters.memory.adapter.InMemoryEventStorageAdapter→src.logicblocks.event.store.adapters.base.EventStorageAdapter
- Direction
- store.adapters.memory.adapter uses store.adapters.base, so a change to store.adapters.base can break store.adapters.memory.adapter, while a change to store.adapters.memory.adapter can't break store.adapters.base.
- Position
- Below the diagonal: store.adapters.memory.adapter uses a module listed above it, which is the healthy direction.
28→7 store.adapters.memory.converters uses sources.constraints✕
- Connections
- 1 pair of types, where a type in store.adapters.memory.converters uses a type in sources.constraints.
- The types involved
src.logicblocks.event.store.adapters.memory.converters.SequenceNumberAfterConstraintConverter→src.logicblocks.event.sources.constraints.SequenceNumberAfterConstraint
- Direction
- store.adapters.memory.converters uses sources.constraints, so a change to sources.constraints can break store.adapters.memory.converters, while a change to store.adapters.memory.converters can't break sources.constraints.
- Position
- Below the diagonal: store.adapters.memory.converters uses a module listed above it, which is the healthy direction.
28→8 store.adapters.memory.converters uses store.conditions✕
- Connections
- 5 pairs of types, where a type in store.adapters.memory.converters uses a type in store.conditions.
- The types involved
src.logicblocks.event.store.adapters.memory.converters.AndConditionConverter→src.logicblocks.event.store.conditions.AndConditionsrc.logicblocks.event.store.adapters.memory.converters.EmptyStreamConditionConverter→src.logicblocks.event.store.conditions.EmptyStreamConditionsrc.logicblocks.event.store.adapters.memory.converters.NoConditionConverter→src.logicblocks.event.store.conditions.NoConditionsrc.logicblocks.event.store.adapters.memory.converters.OrConditionConverter→src.logicblocks.event.store.conditions.OrConditionsrc.logicblocks.event.store.adapters.memory.converters.PositionIsConditionConverter→src.logicblocks.event.store.conditions.PositionIsCondition
- Direction
- store.adapters.memory.converters uses store.conditions, so a change to store.conditions can break store.adapters.memory.converters, while a change to store.adapters.memory.converters can't break store.conditions.
- Position
- Below the diagonal: store.adapters.memory.converters uses a module listed above it, which is the healthy direction.
28→9 store.adapters.memory.converters uses types.functions✕
- Connections
- 6 pairs of types, where a type in store.adapters.memory.converters uses a type in types.functions.
- The types involved
src.logicblocks.event.store.adapters.memory.converters.AndConditionConverter→src.logicblocks.event.types.functions.Convertersrc.logicblocks.event.store.adapters.memory.converters.EmptyStreamConditionConverter→src.logicblocks.event.types.functions.Convertersrc.logicblocks.event.store.adapters.memory.converters.NoConditionConverter→src.logicblocks.event.types.functions.Convertersrc.logicblocks.event.store.adapters.memory.converters.OrConditionConverter→src.logicblocks.event.types.functions.Convertersrc.logicblocks.event.store.adapters.memory.converters.PositionIsConditionConverter→src.logicblocks.event.types.functions.Convertersrc.logicblocks.event.store.adapters.memory.converters.SequenceNumberAfterConstraintConverter→src.logicblocks.event.types.functions.Converter
- Direction
- store.adapters.memory.converters uses types.functions, so a change to types.functions can break store.adapters.memory.converters, while a change to store.adapters.memory.converters can't break types.functions.
- Position
- Below the diagonal: store.adapters.memory.converters uses a module listed above it, which is the healthy direction.
28→10 store.adapters.memory.converters uses types.identifier✕
- Connections
- 1 pair of types, where a type in store.adapters.memory.converters uses a type in types.identifier.
- The types involved
src.logicblocks.event.store.adapters.memory.converters.WriteConditionEnforcerContext→src.logicblocks.event.types.identifier.StreamIdentifier
- Direction
- store.adapters.memory.converters uses types.identifier, so a change to types.identifier can break store.adapters.memory.converters, while a change to store.adapters.memory.converters can't break types.identifier.
- Position
- Below the diagonal: store.adapters.memory.converters uses a module listed above it, which is the healthy direction.
28→11 store.adapters.memory.converters uses persistence.converter✕
- Connections
- 2 pairs of types, where a type in store.adapters.memory.converters uses a type in persistence.converter.
- The types involved
src.logicblocks.event.store.adapters.memory.converters.TypeRegistryConditionConverter→src.logicblocks.event.persistence.converter.TypeRegistryConvertersrc.logicblocks.event.store.adapters.memory.converters.TypeRegistryConstraintConverter→src.logicblocks.event.persistence.converter.TypeRegistryConverter
- Direction
- store.adapters.memory.converters uses persistence.converter, so a change to persistence.converter can break store.adapters.memory.converters, while a change to store.adapters.memory.converters can't break persistence.converter.
- Position
- Below the diagonal: store.adapters.memory.converters uses a module listed above it, which is the healthy direction.
29→1 store.adapters.postgres.adapter uses persistence.postgres.settings✕
- Connections
- 1 pair of types, where a type in store.adapters.postgres.adapter uses a type in persistence.postgres.settings.
- The types involved
src.logicblocks.event.store.adapters.postgres.adapter.PostgresEventStorageAdapter→src.logicblocks.event.persistence.postgres.settings.TableSettings
- Direction
- store.adapters.postgres.adapter uses persistence.postgres.settings, so a change to persistence.postgres.settings can break store.adapters.postgres.adapter, while a change to store.adapters.postgres.adapter can't break persistence.postgres.settings.
- Position
- Below the diagonal: store.adapters.postgres.adapter uses a module listed above it, which is the healthy direction.
29→8 store.adapters.postgres.adapter uses store.conditions✕
- Connections
- 1 pair of types, where a type in store.adapters.postgres.adapter uses a type in store.conditions.
- The types involved
src.logicblocks.event.store.adapters.postgres.adapter.PostgresEventStorageAdapter→src.logicblocks.event.store.conditions.WriteCondition
- Direction
- store.adapters.postgres.adapter uses store.conditions, so a change to store.conditions can break store.adapters.postgres.adapter, while a change to store.adapters.postgres.adapter can't break store.conditions.
- Position
- Below the diagonal: store.adapters.postgres.adapter uses a module listed above it, which is the healthy direction.
29→10 store.adapters.postgres.adapter uses types.identifier✕
- Connections
- 3 pairs of types, where a type in store.adapters.postgres.adapter uses a type in types.identifier.
- The types involved
src.logicblocks.event.store.adapters.postgres.adapter.CategoryStreamsLatestQueryParameters→src.logicblocks.event.types.identifier.CategoryIdentifiersrc.logicblocks.event.store.adapters.postgres.adapter.PostgresEventStorageAdapter→src.logicblocks.event.types.identifier.CategoryIdentifiersrc.logicblocks.event.store.adapters.postgres.adapter.PostgresEventStorageAdapter→src.logicblocks.event.types.identifier.StreamIdentifier
- Direction
- store.adapters.postgres.adapter uses types.identifier, so a change to types.identifier can break store.adapters.postgres.adapter, while a change to store.adapters.postgres.adapter can't break types.identifier.
- Position
- Below the diagonal: store.adapters.postgres.adapter uses a module listed above it, which is the healthy direction.
29→17 store.adapters.postgres.adapter uses store.adapters.base✕
- Connections
- 1 pair of types, where a type in store.adapters.postgres.adapter uses a type in store.adapters.base.
- The types involved
src.logicblocks.event.store.adapters.postgres.adapter.PostgresEventStorageAdapter→src.logicblocks.event.store.adapters.base.EventStorageAdapter
- Direction
- store.adapters.postgres.adapter uses store.adapters.base, so a change to store.adapters.base can break store.adapters.postgres.adapter, while a change to store.adapters.postgres.adapter can't break store.adapters.base.
- Position
- Below the diagonal: store.adapters.postgres.adapter uses a module listed above it, which is the healthy direction.
30→7 store.adapters.postgres.converters uses sources.constraints✕
- Connections
- 1 pair of types, where a type in store.adapters.postgres.converters uses a type in sources.constraints.
- The types involved
src.logicblocks.event.store.adapters.postgres.converters.SequenceNumberAfterConstraintConverter→src.logicblocks.event.sources.constraints.SequenceNumberAfterConstraint
- Direction
- store.adapters.postgres.converters uses sources.constraints, so a change to sources.constraints can break store.adapters.postgres.converters, while a change to store.adapters.postgres.converters can't break sources.constraints.
- Position
- Below the diagonal: store.adapters.postgres.converters uses a module listed above it, which is the healthy direction.
30→8 store.adapters.postgres.converters uses store.conditions✕
- Connections
- 5 pairs of types, where a type in store.adapters.postgres.converters uses a type in store.conditions.
- The types involved
src.logicblocks.event.store.adapters.postgres.converters.AndConditionConverter→src.logicblocks.event.store.conditions.AndConditionsrc.logicblocks.event.store.adapters.postgres.converters.EmptyStreamConditionConverter→src.logicblocks.event.store.conditions.EmptyStreamConditionsrc.logicblocks.event.store.adapters.postgres.converters.NoConditionConverter→src.logicblocks.event.store.conditions.NoConditionsrc.logicblocks.event.store.adapters.postgres.converters.OrConditionConverter→src.logicblocks.event.store.conditions.OrConditionsrc.logicblocks.event.store.adapters.postgres.converters.PositionIsConditionConverter→src.logicblocks.event.store.conditions.PositionIsCondition
- Direction
- store.adapters.postgres.converters uses store.conditions, so a change to store.conditions can break store.adapters.postgres.converters, while a change to store.adapters.postgres.converters can't break store.conditions.
- Position
- Below the diagonal: store.adapters.postgres.converters uses a module listed above it, which is the healthy direction.
30→9 store.adapters.postgres.converters uses types.functions✕
- Connections
- 6 pairs of types, where a type in store.adapters.postgres.converters uses a type in types.functions.
- The types involved
src.logicblocks.event.store.adapters.postgres.converters.AndConditionConverter→src.logicblocks.event.types.functions.Convertersrc.logicblocks.event.store.adapters.postgres.converters.EmptyStreamConditionConverter→src.logicblocks.event.types.functions.Convertersrc.logicblocks.event.store.adapters.postgres.converters.NoConditionConverter→src.logicblocks.event.types.functions.Convertersrc.logicblocks.event.store.adapters.postgres.converters.OrConditionConverter→src.logicblocks.event.types.functions.Convertersrc.logicblocks.event.store.adapters.postgres.converters.PositionIsConditionConverter→src.logicblocks.event.types.functions.Convertersrc.logicblocks.event.store.adapters.postgres.converters.SequenceNumberAfterConstraintConverter→src.logicblocks.event.types.functions.Converter
- Direction
- store.adapters.postgres.converters uses types.functions, so a change to types.functions can break store.adapters.postgres.converters, while a change to store.adapters.postgres.converters can't break types.functions.
- Position
- Below the diagonal: store.adapters.postgres.converters uses a module listed above it, which is the healthy direction.
30→10 store.adapters.postgres.converters uses types.identifier✕
- Connections
- 1 pair of types, where a type in store.adapters.postgres.converters uses a type in types.identifier.
- The types involved
src.logicblocks.event.store.adapters.postgres.converters.WriteConditionEnforcerContext→src.logicblocks.event.types.identifier.StreamIdentifier
- Direction
- store.adapters.postgres.converters uses types.identifier, so a change to types.identifier can break store.adapters.postgres.converters, while a change to store.adapters.postgres.converters can't break types.identifier.
- Position
- Below the diagonal: store.adapters.postgres.converters uses a module listed above it, which is the healthy direction.
30→11 store.adapters.postgres.converters uses persistence.converter✕
- Connections
- 2 pairs of types, where a type in store.adapters.postgres.converters uses a type in persistence.converter.
- The types involved
src.logicblocks.event.store.adapters.postgres.converters.TypeRegistryConditionConverter→src.logicblocks.event.persistence.converter.TypeRegistryConvertersrc.logicblocks.event.store.adapters.postgres.converters.TypeRegistryConstraintConverter→src.logicblocks.event.persistence.converter.TypeRegistryConverter
- Direction
- store.adapters.postgres.converters uses persistence.converter, so a change to persistence.converter can break store.adapters.postgres.converters, while a change to store.adapters.postgres.converters can't break persistence.converter.
- Position
- Below the diagonal: store.adapters.postgres.converters uses a module listed above it, which is the healthy direction.
30→12 store.adapters.postgres.converters uses persistence.postgres.query✕
- Connections
- 3 pairs of types, where a type in store.adapters.postgres.converters uses a type in persistence.postgres.query.
- The types involved
src.logicblocks.event.store.adapters.postgres.converters.SequenceNumberAfterConstraintConverter→src.logicblocks.event.persistence.postgres.query.QueryAppliersrc.logicblocks.event.store.adapters.postgres.converters.SequenceNumberAfterConstraintQueryApplier→src.logicblocks.event.persistence.postgres.query.Querysrc.logicblocks.event.store.adapters.postgres.converters.SequenceNumberAfterConstraintQueryApplier→src.logicblocks.event.persistence.postgres.query.QueryApplier
- Direction
- store.adapters.postgres.converters uses persistence.postgres.query, so a change to persistence.postgres.query can break store.adapters.postgres.converters, while a change to store.adapters.postgres.converters can't break persistence.postgres.query.
- Position
- Below the diagonal: store.adapters.postgres.converters uses a module listed above it, which is the healthy direction.
31→6 store.store uses sources.base✕
- Connections
- 3 pairs of types, where a type in store.store uses a type in sources.base.
- The types involved
src.logicblocks.event.store.store.EventCategory→src.logicblocks.event.sources.base.EventSourcesrc.logicblocks.event.store.store.EventLog→src.logicblocks.event.sources.base.EventSourcesrc.logicblocks.event.store.store.EventStream→src.logicblocks.event.sources.base.EventSource
- Direction
- store.store uses sources.base, so a change to sources.base can break store.store, while a change to store.store can't break sources.base.
- Position
- Below the diagonal: store.store uses a module listed above it, which is the healthy direction.
31→8 store.store uses store.conditions✕
- Connections
- 1 pair of types, where a type in store.store uses a type in store.conditions.
- The types involved
src.logicblocks.event.store.store.EventStream→src.logicblocks.event.store.conditions.WriteCondition
- Direction
- store.store uses store.conditions, so a change to store.conditions can break store.store, while a change to store.store can't break store.conditions.
- Position
- Below the diagonal: store.store uses a module listed above it, which is the healthy direction.
31→10 store.store uses types.identifier✕
- Connections
- 3 pairs of types, where a type in store.store uses a type in types.identifier.
- The types involved
src.logicblocks.event.store.store.EventCategory→src.logicblocks.event.types.identifier.CategoryIdentifiersrc.logicblocks.event.store.store.EventLog→src.logicblocks.event.types.identifier.LogIdentifiersrc.logicblocks.event.store.store.EventStream→src.logicblocks.event.types.identifier.StreamIdentifier
- Direction
- store.store uses types.identifier, so a change to types.identifier can break store.store, while a change to store.store can't break types.identifier.
- Position
- Below the diagonal: store.store uses a module listed above it, which is the healthy direction.
31→17 store.store uses store.adapters.base✕
- Connections
- 4 pairs of types, where a type in store.store uses a type in store.adapters.base.
- The types involved
src.logicblocks.event.store.store.EventCategory→src.logicblocks.event.store.adapters.base.EventStorageAdaptersrc.logicblocks.event.store.store.EventLog→src.logicblocks.event.store.adapters.base.EventStorageAdaptersrc.logicblocks.event.store.store.EventStore→src.logicblocks.event.store.adapters.base.EventStorageAdaptersrc.logicblocks.event.store.store.EventStream→src.logicblocks.event.store.adapters.base.EventStorageAdapter
- Direction
- store.store uses store.adapters.base, so a change to store.adapters.base can break store.store, while a change to store.store can't break store.adapters.base.
- Position
- Below the diagonal: store.store uses a module listed above it, which is the healthy direction.
32→3 processing.broker.strategies.distributed.coordinator uses processing.locks.base✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.coordinator uses a type in processing.locks.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.coordinator.DefaultEventSubscriptionCoordinator→src.logicblocks.event.processing.locks.base.LockManager
- Direction
- processing.broker.strategies.distributed.coordinator uses processing.locks.base, so a change to processing.locks.base can break processing.broker.strategies.distributed.coordinator, while a change to processing.broker.strategies.distributed.coordinator can't break processing.locks.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.coordinator uses a module listed above it, which is the healthy direction.
32→4 processing.broker.strategies.distributed.coordinator uses processing.process.base✕
- Connections
- 2 pairs of types, where a type in processing.broker.strategies.distributed.coordinator uses a type in processing.process.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.coordinator.DefaultEventSubscriptionCoordinator→src.logicblocks.event.processing.process.base.ProcessStatussrc.logicblocks.event.processing.broker.strategies.distributed.coordinator.EventSubscriptionCoordinator→src.logicblocks.event.processing.process.base.Process
- Direction
- processing.broker.strategies.distributed.coordinator uses processing.process.base, so a change to processing.process.base can break processing.broker.strategies.distributed.coordinator, while a change to processing.broker.strategies.distributed.coordinator can't break processing.process.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.coordinator uses a module listed above it, which is the healthy direction.
32→14 processing.broker.strategies.distributed.coordinator uses processing.broker.strategies.distributed.subscriptions.stores.state.base✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.coordinator uses a type in processing.broker.strategies.distributed.subscriptions.stores.state.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.coordinator.DefaultEventSubscriptionCoordinator→src.logicblocks.event.processing.broker.strategies.distributed.subscriptions.stores.state.base.EventSubscriptionStateStore
- Direction
- processing.broker.strategies.distributed.coordinator uses processing.broker.strategies.distributed.subscriptions.stores.state.base, so a change to processing.broker.strategies.distributed.subscriptions.stores.state.base can break processing.broker.strategies.distributed.coordinator, while a change to processing.broker.strategies.distributed.coordinator can't break processing.broker.strategies.distributed.subscriptions.stores.state.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.coordinator uses a module listed above it, which is the healthy direction.
32→26 processing.broker.strategies.distributed.coordinator uses processing.broker.strategies.distributed.subscribers.stores.state.base✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.coordinator uses a type in processing.broker.strategies.distributed.subscribers.stores.state.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.coordinator.DefaultEventSubscriptionCoordinator→src.logicblocks.event.processing.broker.strategies.distributed.subscribers.stores.state.base.EventSubscriberStateStore
- Direction
- processing.broker.strategies.distributed.coordinator uses processing.broker.strategies.distributed.subscribers.stores.state.base, so a change to processing.broker.strategies.distributed.subscribers.stores.state.base can break processing.broker.strategies.distributed.coordinator, while a change to processing.broker.strategies.distributed.coordinator can't break processing.broker.strategies.distributed.subscribers.stores.state.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.coordinator uses a module listed above it, which is the healthy direction.
33→4 processing.broker.strategies.distributed.observer uses processing.process.base✕
- Connections
- 2 pairs of types, where a type in processing.broker.strategies.distributed.observer uses a type in processing.process.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.observer.DefaultEventSubscriptionObserver→src.logicblocks.event.processing.process.base.ProcessStatussrc.logicblocks.event.processing.broker.strategies.distributed.observer.EventSubscriptionObserver→src.logicblocks.event.processing.process.base.Process
- Direction
- processing.broker.strategies.distributed.observer uses processing.process.base, so a change to processing.process.base can break processing.broker.strategies.distributed.observer, while a change to processing.broker.strategies.distributed.observer can't break processing.process.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.observer uses a module listed above it, which is the healthy direction.
33→14 processing.broker.strategies.distributed.observer uses processing.broker.strategies.distributed.subscriptions.stores.state.base✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.observer uses a type in processing.broker.strategies.distributed.subscriptions.stores.state.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.observer.DefaultEventSubscriptionObserver→src.logicblocks.event.processing.broker.strategies.distributed.subscriptions.stores.state.base.EventSubscriptionStateStore
- Direction
- processing.broker.strategies.distributed.observer uses processing.broker.strategies.distributed.subscriptions.stores.state.base, so a change to processing.broker.strategies.distributed.subscriptions.stores.state.base can break processing.broker.strategies.distributed.observer, while a change to processing.broker.strategies.distributed.observer can't break processing.broker.strategies.distributed.subscriptions.stores.state.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.observer uses a module listed above it, which is the healthy direction.
33→25 processing.broker.strategies.distributed.observer uses processing.broker.strategies.distributed.difference✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.observer uses a type in processing.broker.strategies.distributed.difference.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.observer.DefaultEventSubscriptionObserver→src.logicblocks.event.processing.broker.strategies.distributed.difference.EventSubscriptionDifference
- Direction
- processing.broker.strategies.distributed.observer uses processing.broker.strategies.distributed.difference, so a change to processing.broker.strategies.distributed.difference can break processing.broker.strategies.distributed.observer, while a change to processing.broker.strategies.distributed.observer can't break processing.broker.strategies.distributed.difference.
- Position
- Below the diagonal: processing.broker.strategies.distributed.observer uses a module listed above it, which is the healthy direction.
34→1 processing.broker.strategies.distributed.subscribers.stores.state uses persistence.postgres.settings✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.subscribers.stores.state uses a type in persistence.postgres.settings.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.subscribers.stores.state.postgres→src.logicblocks.event.persistence.postgres.settings.TableSettings
- Direction
- processing.broker.strategies.distributed.subscribers.stores.state uses persistence.postgres.settings, so a change to persistence.postgres.settings can break processing.broker.strategies.distributed.subscribers.stores.state, while a change to processing.broker.strategies.distributed.subscribers.stores.state can't break persistence.postgres.settings.
- Position
- Below the diagonal: processing.broker.strategies.distributed.subscribers.stores.state uses a module listed above it, which is the healthy direction.
34→2 processing.broker.strategies.distributed.subscribers.stores.state uses processing.broker.types✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.subscribers.stores.state uses a type in processing.broker.types.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.subscribers.stores.state.postgres→src.logicblocks.event.processing.broker.types.EventSubscriberKey
- Direction
- processing.broker.strategies.distributed.subscribers.stores.state uses processing.broker.types, so a change to processing.broker.types can break processing.broker.strategies.distributed.subscribers.stores.state, while a change to processing.broker.strategies.distributed.subscribers.stores.state can't break processing.broker.types.
- Position
- Below the diagonal: processing.broker.strategies.distributed.subscribers.stores.state uses a module listed above it, which is the healthy direction.
34→26 processing.broker.strategies.distributed.subscribers.stores.state uses processing.broker.strategies.distributed.subscribers.stores.state.base✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.subscribers.stores.state uses a type in processing.broker.strategies.distributed.subscribers.stores.state.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.subscribers.stores.state.postgres→src.logicblocks.event.processing.broker.strategies.distributed.subscribers.stores.state.base.EventSubscriberState
- Direction
- processing.broker.strategies.distributed.subscribers.stores.state uses processing.broker.strategies.distributed.subscribers.stores.state.base, so a change to processing.broker.strategies.distributed.subscribers.stores.state.base can break processing.broker.strategies.distributed.subscribers.stores.state, while a change to processing.broker.strategies.distributed.subscribers.stores.state can't break processing.broker.strategies.distributed.subscribers.stores.state.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.subscribers.stores.state uses a module listed above it, which is the healthy direction.
35→1 processing.broker.strategies.distributed.subscribers.stores.state.postgres uses persistence.postgres.settings✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.subscribers.stores.state.postgres uses a type in persistence.postgres.settings.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.subscribers.stores.state.postgres.PostgresEventSubscriberStateStore→src.logicblocks.event.persistence.postgres.settings.TableSettings
- Direction
- processing.broker.strategies.distributed.subscribers.stores.state.postgres uses persistence.postgres.settings, so a change to persistence.postgres.settings can break processing.broker.strategies.distributed.subscribers.stores.state.postgres, while a change to processing.broker.strategies.distributed.subscribers.stores.state.postgres can't break persistence.postgres.settings.
- Position
- Below the diagonal: processing.broker.strategies.distributed.subscribers.stores.state.postgres uses a module listed above it, which is the healthy direction.
35→26 processing.broker.strategies.distributed.subscribers.stores.state.postgres uses processing.broker.strategies.distributed.subscribers.stores.state.base✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.subscribers.stores.state.postgres uses a type in processing.broker.strategies.distributed.subscribers.stores.state.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.subscribers.stores.state.postgres.PostgresEventSubscriberStateStore→src.logicblocks.event.processing.broker.strategies.distributed.subscribers.stores.state.base.EventSubscriberStateStore
- Direction
- processing.broker.strategies.distributed.subscribers.stores.state.postgres uses processing.broker.strategies.distributed.subscribers.stores.state.base, so a change to processing.broker.strategies.distributed.subscribers.stores.state.base can break processing.broker.strategies.distributed.subscribers.stores.state.postgres, while a change to processing.broker.strategies.distributed.subscribers.stores.state.postgres can't break processing.broker.strategies.distributed.subscribers.stores.state.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.subscribers.stores.state.postgres uses a module listed above it, which is the healthy direction.
36→31 processing.consumers.state.base uses store.store✕
- Connections
- 1 pair of types, where a type in processing.consumers.state.base uses a type in store.store.
- The types involved
src.logicblocks.event.processing.consumers.state.base.EventConsumerStateStore→src.logicblocks.event.store.store.EventCategory
- Direction
- processing.consumers.state.base uses store.store, so a change to store.store can break processing.consumers.state.base, while a change to processing.consumers.state.base can't break store.store.
- Position
- Below the diagonal: processing.consumers.state.base uses a module listed above it, which is the healthy direction.
37→8 store uses store.conditions✕
- Connections
- 1 pair of types, where a type in store uses a type in store.conditions.
- The types involved
src.logicblocks.event.store.conditions→src.logicblocks.event.store.conditions.WriteCondition
- Direction
- store uses store.conditions, so a change to store.conditions can break store, while a change to store can't break store.conditions.
- Position
- Below the diagonal: store uses a module listed above it, which is the healthy direction.
37→10 store uses types.identifier✕
- Connections
- 3 pairs of types, where a type in store uses a type in types.identifier.
- The types involved
src.logicblocks.event.store.source_factories→src.logicblocks.event.types.identifier.CategoryIdentifiersrc.logicblocks.event.store.source_factories→src.logicblocks.event.types.identifier.LogIdentifiersrc.logicblocks.event.store.source_factories→src.logicblocks.event.types.identifier.StreamIdentifier
- Direction
- store uses types.identifier, so a change to types.identifier can break store, while a change to store can't break types.identifier.
- Position
- Below the diagonal: store uses a module listed above it, which is the healthy direction.
37→17 store uses store.adapters.base✕
- Connections
- 1 pair of types, where a type in store uses a type in store.adapters.base.
- The types involved
src.logicblocks.event.store.source_factories→src.logicblocks.event.store.adapters.base.EventStorageAdapter
- Direction
- store uses store.adapters.base, so a change to store.adapters.base can break store, while a change to store can't break store.adapters.base.
- Position
- Below the diagonal: store uses a module listed above it, which is the healthy direction.
37→31 store uses store.store✕
- Connections
- 3 pairs of types, where a type in store uses a type in store.store.
- The types involved
src.logicblocks.event.store.source_factories→src.logicblocks.event.store.store.EventCategorysrc.logicblocks.event.store.source_factories→src.logicblocks.event.store.store.EventLogsrc.logicblocks.event.store.source_factories→src.logicblocks.event.store.store.EventStream
- Direction
- store uses store.store, so a change to store.store can break store, while a change to store can't break store.store.
- Position
- Below the diagonal: store uses a module listed above it, which is the healthy direction.
38→1 store.adapters.postgres uses persistence.postgres.settings✕
- Connections
- 1 pair of types, where a type in store.adapters.postgres uses a type in persistence.postgres.settings.
- The types involved
src.logicblocks.event.store.adapters.postgres.adapter→src.logicblocks.event.persistence.postgres.settings.TableSettings
- Direction
- store.adapters.postgres uses persistence.postgres.settings, so a change to persistence.postgres.settings can break store.adapters.postgres, while a change to store.adapters.postgres can't break persistence.postgres.settings.
- Position
- Below the diagonal: store.adapters.postgres uses a module listed above it, which is the healthy direction.
38→10 store.adapters.postgres uses types.identifier✕
- Connections
- 2 pairs of types, where a type in store.adapters.postgres uses a type in types.identifier.
- The types involved
src.logicblocks.event.store.adapters.postgres.adapter→src.logicblocks.event.types.identifier.CategoryIdentifiersrc.logicblocks.event.store.adapters.postgres.adapter→src.logicblocks.event.types.identifier.StreamIdentifier
- Direction
- store.adapters.postgres uses types.identifier, so a change to types.identifier can break store.adapters.postgres, while a change to store.adapters.postgres can't break types.identifier.
- Position
- Below the diagonal: store.adapters.postgres uses a module listed above it, which is the healthy direction.
38→17 store.adapters.postgres uses store.adapters.base✕
- Connections
- 3 pairs of types, where a type in store.adapters.postgres uses a type in store.adapters.base.
- The types involved
src.logicblocks.event.store.adapters.postgres.adapter→src.logicblocks.event.store.adapters.base.CategoryEventSerialisationGuaranteesrc.logicblocks.event.store.adapters.postgres.adapter→src.logicblocks.event.store.adapters.base.LogEventSerialisationGuaranteesrc.logicblocks.event.store.adapters.postgres.adapter→src.logicblocks.event.store.adapters.base.StreamEventSerialisationGuarantee
- Direction
- store.adapters.postgres uses store.adapters.base, so a change to store.adapters.base can break store.adapters.postgres, while a change to store.adapters.postgres can't break store.adapters.base.
- Position
- Below the diagonal: store.adapters.postgres uses a module listed above it, which is the healthy direction.
38→29 store.adapters.postgres uses store.adapters.postgres.adapter✕
- Connections
- 3 pairs of types, where a type in store.adapters.postgres uses a type in store.adapters.postgres.adapter.
- The types involved
src.logicblocks.event.store.adapters.postgres.adapter→src.logicblocks.event.store.adapters.postgres.adapter.CategoryStreamsLatestQueryParameterssrc.logicblocks.event.store.adapters.postgres.adapter→src.logicblocks.event.store.adapters.postgres.adapter.LatestQueryParameterssrc.logicblocks.event.store.adapters.postgres.adapter→src.logicblocks.event.store.adapters.postgres.adapter.ScanQueryParameters
- Direction
- store.adapters.postgres uses store.adapters.postgres.adapter, so a change to store.adapters.postgres.adapter can break store.adapters.postgres, while a change to store.adapters.postgres can't break store.adapters.postgres.adapter.
- Position
- Below the diagonal: store.adapters.postgres uses a module listed above it, which is the healthy direction.
39→4 processing.broker.strategies.distributed.broker uses processing.process.base✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.broker uses a type in processing.process.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.broker.DistributedEventBroker→src.logicblocks.event.processing.process.base.ProcessStatus
- Direction
- processing.broker.strategies.distributed.broker uses processing.process.base, so a change to processing.process.base can break processing.broker.strategies.distributed.broker, while a change to processing.broker.strategies.distributed.broker can't break processing.process.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.broker uses a module listed above it, which is the healthy direction.
39→13 processing.broker.strategies.distributed.broker uses processing.broker.base✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.broker uses a type in processing.broker.base.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.broker.DistributedEventBroker→src.logicblocks.event.processing.broker.base.EventBroker
- Direction
- processing.broker.strategies.distributed.broker uses processing.broker.base, so a change to processing.broker.base can break processing.broker.strategies.distributed.broker, while a change to processing.broker.strategies.distributed.broker can't break processing.broker.base.
- Position
- Below the diagonal: processing.broker.strategies.distributed.broker uses a module listed above it, which is the healthy direction.
39→32 processing.broker.strategies.distributed.broker uses processing.broker.strategies.distributed.coordinator✕
- Connections
- 1 pair of types, where a type in processing.broker.strategies.distributed.broker uses a type in processing.broker.strategies.distributed.coordinator.
- The types involved
src.logicblocks.event.processing.broker.strategies.distributed.broker.DistributedEventBroker→src.logicblocks.event.processing.broker.strategies.distributed.coordinator.EventSubscriptionCoordinator
- Direction
- processing.broker.strategies.distributed.broker uses processing.broker.strategies.distributed.coordinator, so a change to processing.broker.strategies.distributed.coordinator can break processing.broker.strategies.distributed.broker, while a change to processing.broker.strategies.distributed.broker can't break processing.broker.strategies.distributed.coordinator.
- Position
- Below the diagonal: processing.broker.strategies.distributed.broker uses a module listed above it, which is the healthy direction.
40→10 processing.consumers uses types.identifier✕
- Connections
- 1 pair of types, where a type in processing.consumers uses a type in types.identifier.
- The types involved
src.logicblocks.event.processing.consumers.subscription→src.logicblocks.event.types.identifier.EventSourceIdentifier
- Direction
- processing.consumers uses types.identifier, so a change to types.identifier can break processing.consumers, while a change to processing.consumers can't break types.identifier.
- Position
- Below the diagonal: processing.consumers uses a module listed above it, which is the healthy direction.
40→31 processing.consumers uses store.store✕
- Connections
- 1 pair of types, where a type in processing.consumers uses a type in store.store.
- The types involved
src.logicblocks.event.processing.consumers.subscription→src.logicblocks.event.store.store.EventCategory
- Direction
- processing.consumers uses store.store, so a change to store.store can break processing.consumers, while a change to processing.consumers can't break store.store.
- Position
- Below the diagonal: processing.consumers uses a module listed above it, which is the healthy direction.
40→36 processing.consumers uses processing.consumers.state.base✕
- Connections
- 1 pair of types, where a type in processing.consumers uses a type in processing.consumers.state.base.
- The types involved
src.logicblocks.event.processing.consumers.subscription→src.logicblocks.event.processing.consumers.state.base.EventCount
- Direction
- processing.consumers uses processing.consumers.state.base, so a change to processing.consumers.state.base can break processing.consumers, while a change to processing.consumers can't break processing.consumers.state.base.
- Position
- Below the diagonal: processing.consumers uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 14 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 12 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; 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; Resolve the 1 Banned license finding(s) in License Compliance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +6.5 pts | Medium | Architecture documentation |
| Resolve the 1 Banned license finding(s) in License Compliance. | +2.5 pts | Low | License Compliance |
| 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.6 pts | Medium | Security & performance tooling |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +2.1 pts | Low | Project Cohesion |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.8 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.8 pts | Low | Bus Factor |
| 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. | +1.3 pts | Medium | Code composition |
| Consider OpenTelemetry tracing/metrics (opentelemetry-sdk) and a health-check endpoint (a /health route) for operability. | +1.1 pts | Medium | Observability |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Dependency Vulnerabilities: Critical vulnerability: REDACTED |
| src/logicblocks/event/store/adapters/memory/adapter.py | 6.3 | Mixed | Code Duplication: Duplicated block (39–45 lines × 2) |
| tests/shared/logicblocks/event/testcases/store/adapters.py | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/logicblocks/event/persistence/postgres/converters/clause.py | 7.1 | Near-clean | Cognitive Complexity: KeySetPagingClauseQueryApplier.apply (cognitive 19) |
| src/logicblocks/event/types/conversion.py | 7.8 | Near-clean | Cyclomatic Complexity: conversion.deserialise_from_json_value (cyclomatic 34) |
| src/logicblocks/event/persistence/postgres/query.py | 7.8 | Near-clean | God Classes: FileTooLong: postgres/query.py |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Near-clean | Supply-chain Provenance & Signing: REDACTED |
| src/logicblocks/event/processing/broker/strategies/distributed/coordinator.py | 8.5 | Near-clean | Cognitive Complexity: DefaultEventSubscriptionCoordinator.distribute (cognitive 28) |
| src/logicblocks/event/processing/broker/strategies/distributed/subscribers/stores/state/postgres.py | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| src/logicblocks/event/store/adapters/memory/converters.py | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
| src/logicblocks/event/projection/store/adapters/memory.py | 8.5 | Near-clean | Change Coupling: Change coupling: memory.py ↔ postgres.py |
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 57 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 — 57 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, 46 of 59 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 MEASURED: test source is present (.py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage 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, 62 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 1 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.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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/logicblocks/event/persistence/converter.py`, `src/logicblocks/event/persistence/memory/converters/clause.py`, `src/logicblocks/event/persistence/memory/converters/function.py`, `src/logicblocks/event/persistence/memory/converters/helpers.py`, `src/logicblocks/event/persistence/memory/converters/query.py`, … (+62 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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 defines its own container in src/logicblocks/event/processing/broker/__init__.py, 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.
- 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 this repository's Python is most of its product and 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 this repository's Python is most of its product and 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.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was conversion.deserialise_from_json_value at 34.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with conversion.deserialise_from_json_value (cyclomatic 34). — Refactoring it lifts Cyclomatic Complexity from 9.1 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was conversion.deserialise_from_json_value at 59.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with conversion.deserialise_from_json_value (cognitive 59). — Refactoring it lifts Cognitive Complexity from 8.3 to about 9.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
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with query.py, clause.py. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
8 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (39–45 lines × 2) finding(s) in Code Duplication — start with adapter.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (43–44 lines × 2) finding(s) in Code Duplication — start with clause.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (21 lines × 2) finding(s) in Code Duplication — start with adapter.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 41 classes have LCOM4 above 3.
D9 · Test Distribution
1047 test methods: 1031 unit, 16 integration, 0 BDD, 0 e2e. The Python suite contributes 1047 test function(s) across 54 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
1 of 3 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 1 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.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
- Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/logicblocks/event/processing/broker/strategies/distributed/coordinator.py. Counted over 47 of the 155 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
3 deducted task-comment markers across 11701 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with adapters.py (3). — One of this dimension's main actionable groups (3 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. 3 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
78 % of calls cross a namespace and 0 % go through an interface, but 100 % 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)
14 finding(s): 0 critical, 12 high, 2 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 68 file(s) — `src/logicblocks/event/persistence/converter.py` (lines 1–34), `src/logicblocks/event/persistence/memory/converters/clause.py` (lines 1–245), `src/logicblocks/event/persistence/memory/converters/function.py` (lines 1–70), `src/logicblocks/event/persistence/memory/converters/helpers.py` (line 7), `src/logicblocks/event/persistence/memory/converters/query.py` (lines 1–172), … (+63 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 12 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (12 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 1 critical, 3 high, 1 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 vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 47 of the 155 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: adapter.py↔adapter.py 62%; memory.py↔postgres.py 60%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with adapter.py, memory.py. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
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 1 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)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
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 2946 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: 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
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 122 is called with an argument built by `list(constraints)` (line 123), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — src/logicblocks/event/store/store.py:122
- `debug` at line 197 is called with an argument built by `list(constraints)` (line 198), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — src/logicblocks/event/store/store.py:197
- `debug` at line 267 is called with an argument built by `list(constraints)` (line 268), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — src/logicblocks/event/store/store.py:267
What to do
- In Python, put the construction behind the logger's own check (`if logger.isEnabledFor(logging.DEBUG):`), or pass the collection itself with a `%s` placeholder (`logger.debug("Items %s", items)`) so the logging module renders it only when the record is emitted. The placeholder alone is not the fix when the argument is still built first: it defers the formatting, not a `json.dumps`, a `join` or a comprehension in the argument, and an f-string defers nothing at all.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 97% | Exemplary | Solid. |
| Architecture | 74% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 57% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 60% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 78% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 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 — 61 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (3 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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 — This repository has nothing the runtime tiers could boot or serve — 1 markup document under demonstration, documentation or developer-tool trees (or modules the build marks non-production) but none in the product; no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — those pages are demos or docs for the code, not something this tier can boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — 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 — ~30268 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
- 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; JavaScript, 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. 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; comments in this repository's .py source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 67 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 (2 of 3 signals for this style — below the bar we score at): 26 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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 none of the 3 signals this lens looks for
- 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 3 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`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.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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.
- 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 — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: psycopg
- REDACTED
Serious — 26 finding(s)
- TodoComment tests/shared/logicblocks/event/testcases/store/adapters.py:961
- TodoComment tests/shared/logicblocks/event/testcases/store/adapters.py:1966
- TodoComment tests/shared/logicblocks/event/testcases/store/adapters.py:2085
- FileTooLong: postgres/query.py src/logicblocks/event/persistence/postgres/query.py
- FileTooLong: converters/clause.py src/logicblocks/event/persistence/postgres/converters/clause.py
- Change coupling: adapter.py ↔ adapter.py src/logicblocks/event/store/adapters/memory/adapter.py:1
- Change coupling: memory.py ↔ postgres.py src/logicblocks/event/projection/store/adapters/memory.py:1
- conversion.deserialise_from_json_value (cyclomatic 34) src/logicblocks/event/types/conversion.py:66
- conversion.deserialise_from_json_value (cognitive 59) src/logicblocks/event/types/conversion.py:66
- DefaultEventSubscriptionCoordinator.distribute (cognitive 28) src/logicblocks/event/processing/broker/strategies/distributed/coordinator.py:199
- KeySetPagingClauseQueryApplier.apply (cognitive 19) src/logicblocks/event/persistence/postgres/converters/clause.py:606
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (39–45 lines × 2) src/logicblocks/event/store/adapters/memory/adapter.py:211
- Duplicated block (43–44 lines × 2) src/logicblocks/event/persistence/postgres/converters/clause.py:470
- Duplicated block (21 lines × 2) src/logicblocks/event/store/adapters/memory/adapter.py:164
- Duplicated block (19 lines × 2) src/logicblocks/event/persistence/postgres/converters/clause.py:300
- Duplicated block (16 lines × 2) src/logicblocks/event/persistence/postgres/converters/clause.py:347
- Duplicated block (10 lines × 2) src/logicblocks/event/persistence/postgres/query.py:80
- Duplicated block (8 lines × 2) src/logicblocks/event/processing/broker/strategies/distributed/subscribers/stores/state/postgres.py:195
- Duplicated block (7 lines × 2) src/logicblocks/event/store/adapters/memory/converters.py:228
Minor — 15 finding(s)
- Diagnostic log message is built whether or not it is wanted src/logicblocks/event/store/store.py:122
- Diagnostic log message is built whether or not it is wanted src/logicblocks/event/store/store.py:197
- Diagnostic log message is built whether or not it is wanted src/logicblocks/event/store/store.py:267
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- No rollback/health safety
- Duplicated predicate src/logicblocks/event/processing/broker/strategies/distributed/factories.py:65
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-40a7fd20561f468e92a1032e83ba19d9/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-40a7fd20561f468e92a1032e83ba19d9/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 . | 14 | 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 . | 5 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | 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 67 file(s) — `src/logicblocks/event/persistence/converter.py`, `src/logicblocks/event/persistence/memory/converters/clause.py`, `src/logicblocks/event/persistence/memory/converters/function.py`, `src/logicblocks/event/persistence/memory/converters/helpers.py`, `src/logicblocks/event/persistence/memory/converters/query.py`, … (+62 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |