Executive summary
minos-framework/minos-python is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because six of the dependencies have a known vulnerability and it has pipeline tools referenced by a changeable name. It scores 47 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Security and Compliance, at 38, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 7 points. Fixing the 28 pipeline tools referenced by a changeable name would lift Security and Compliance itself, worth about 3 points. Raising Security and Compliance to 68 would lift the score to about 54.
Ninety-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-one settings leave the servers or containers unsafe, and twenty known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, correcting the unsafe settings and updating the vulnerable packages would close these risks. Limiting each secret to its own step would fix the 14 secrets exposed to more of the pipeline than needed, and the three passwords or keys in the code and the password or key in the code's history need replacing, with the old ones switched off. Referring to the other business object by its identifier would take care of the two business objects holding another business object directly.
The product code is 24,691 lines, about €49,000 to rebuild.
If Security and Compliance rose from 38 to 68, the lowest score rated Strong, the score would rise from 47 to about 54.
New since the last survey: 2 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 3 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Change Coupling · Change-coupling hub: impl.py → impl.py, impl.py, impl.py packages/core/minos-microservice-aggregate/minos/aggregate/transactions/repositories/database/impl.py
Rebuild cost: about €49,000 · Estimate
| Cost to rebuild | €16,000 to €81,000, for 270 to 857 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.7 at a score of 47. 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 | Medium: 24,691 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 minos-microservice-aggregate.minos.aggregate.actions | 2 minos-microservice-aggregate.minos.aggregate.queries | 3 minos-microservice-aggregate.minos.aggregate.transactions.entries | 4 minos-microservice-common.minos.common.config.abc | 5 minos-microservice-common.minos.common.database.operations | 6 minos-microservice-common.minos.common.model.serializers.abc | 7 minos-microservice-networks.minos.networks.brokers.messages.models.abc | 8 minos-microservice-networks.minos.networks.decorators.definitions.abc | 9 minos-microservice-networks.minos.networks.requests.abc | 10 minos-microservice-saga.minos.saga.context | 11 minos-microservice-aggregate.minos.aggregate.events.models | 12 minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc | 13 minos-microservice-common.minos.common.database.clients.abc | 14 minos-microservice-common.minos.common.model.types.model_types | 15 minos-microservice-common.minos.common.setup | 16 minos-microservice-networks.minos.networks.brokers.collections.queues.abc | 17 minos-microservice-networks.minos.networks.brokers.publishers.abc | 18 minos-microservice-networks.minos.networks.brokers.subscribers.abc | 19 minos-microservice-saga.minos.saga.definitions.steps.conditional | 20 minos-microservice-aggregate.minos.aggregate.events.entries | 21 minos-microservice-common.minos.common.model.abc | 22 minos-microservice-common.minos.common.pools | 23 minos-microservice-networks.minos.networks.brokers.clients | 24 minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl | 25 minos-microservice-networks.minos.networks.brokers.collections.queues.memory | 26 minos-microservice-networks.minos.networks.brokers.publishers.queued.queues.abc | 27 minos-microservice-saga.minos.saga.definitions.steps.abc | 28 minos-microservice-aggregate.minos.aggregate.events.repositories.abc | 29 minos-microservice-aggregate.minos.aggregate.snapshots.entries | 30 minos-microservice-common.minos.common.database.pools | 31 minos-microservice-common.minos.common.model.dynamic.abc | 32 minos-microservice-saga.minos.saga.definitions.saga | 33 minos-microservice-saga.minos.saga.executions.steps.abc | 34 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc | 35 minos-microservice-common.minos.common.database.mixins | 36 minos-microservice-saga.minos.saga.executions.saga | 37 minos-microservice-aggregate.minos.aggregate.entities.models | 38 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory | 39 minos-microservice-saga.minos.saga.manager | 40 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 minos-microservice-aggregate.minos.aggregate.actions | ||||||||||||||||||||||||||||||||||||||||
| 2 minos-microservice-aggregate.minos.aggregate.queries | ||||||||||||||||||||||||||||||||||||||||
| 3 minos-microservice-aggregate.minos.aggregate.transactions.entries | ||||||||||||||||||||||||||||||||||||||||
| 4 minos-microservice-common.minos.common.config.abc | ||||||||||||||||||||||||||||||||||||||||
| 5 minos-microservice-common.minos.common.database.operations | ||||||||||||||||||||||||||||||||||||||||
| 6 minos-microservice-common.minos.common.model.serializers.abc | ||||||||||||||||||||||||||||||||||||||||
| 7 minos-microservice-networks.minos.networks.brokers.messages.models.abc | ||||||||||||||||||||||||||||||||||||||||
| 8 minos-microservice-networks.minos.networks.decorators.definitions.abc | ||||||||||||||||||||||||||||||||||||||||
| 9 minos-microservice-networks.minos.networks.requests.abc | ||||||||||||||||||||||||||||||||||||||||
| 10 minos-microservice-saga.minos.saga.context | ||||||||||||||||||||||||||||||||||||||||
| 11 minos-microservice-aggregate.minos.aggregate.events.models | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 minos-microservice-common.minos.common.database.clients.abc | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 14 minos-microservice-common.minos.common.model.types.model_types | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 minos-microservice-common.minos.common.setup | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 minos-microservice-networks.minos.networks.brokers.collections.queues.abc | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 minos-microservice-networks.minos.networks.brokers.publishers.abc | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 minos-microservice-networks.minos.networks.brokers.subscribers.abc | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 minos-microservice-saga.minos.saga.definitions.steps.conditional | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 20 minos-microservice-aggregate.minos.aggregate.events.entries | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 minos-microservice-common.minos.common.model.abc | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 minos-microservice-common.minos.common.pools | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 minos-microservice-networks.minos.networks.brokers.clients | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 minos-microservice-networks.minos.networks.brokers.collections.queues.memory | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 minos-microservice-networks.minos.networks.brokers.publishers.queued.queues.abc | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 minos-microservice-saga.minos.saga.definitions.steps.abc | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 minos-microservice-aggregate.minos.aggregate.events.repositories.abc | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 minos-microservice-aggregate.minos.aggregate.snapshots.entries | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 minos-microservice-common.minos.common.database.pools | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 minos-microservice-common.minos.common.model.dynamic.abc | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 minos-microservice-saga.minos.saga.definitions.saga | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 minos-microservice-saga.minos.saga.executions.steps.abc | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 minos-microservice-common.minos.common.database.mixins | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 minos-microservice-saga.minos.saga.executions.saga | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 minos-microservice-aggregate.minos.aggregate.entities.models | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 minos-microservice-saga.minos.saga.manager | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
11→1 minos-microservice-aggregate.minos.aggregate.events.models uses minos-microservice-aggregate.minos.aggregate.actions✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.events.models uses a type in minos-microservice-aggregate.minos.aggregate.actions.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.events.models.Event→packages.core.minos-microservice-aggregate.minos.aggregate.actions.Action
- Direction
- minos-microservice-aggregate.minos.aggregate.events.models uses minos-microservice-aggregate.minos.aggregate.actions, so a change to minos-microservice-aggregate.minos.aggregate.actions can break minos-microservice-aggregate.minos.aggregate.events.models, while a change to minos-microservice-aggregate.minos.aggregate.events.models can't break minos-microservice-aggregate.minos.aggregate.actions.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.events.models uses a module listed above it, which is the healthy direction.
11→37 minos-microservice-aggregate.minos.aggregate.events.models uses minos-microservice-aggregate.minos.aggregate.entities.models part of a loop✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.events.models uses a type in minos-microservice-aggregate.minos.aggregate.entities.models.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.events.models.Event→packages.core.minos-microservice-aggregate.minos.aggregate.entities.models.RootEntity
- Direction
- minos-microservice-aggregate.minos.aggregate.events.models uses minos-microservice-aggregate.minos.aggregate.entities.models, so a change to minos-microservice-aggregate.minos.aggregate.entities.models can break minos-microservice-aggregate.minos.aggregate.events.models, while a change to minos-microservice-aggregate.minos.aggregate.events.models can't break minos-microservice-aggregate.minos.aggregate.entities.models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→3 minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc uses minos-microservice-aggregate.minos.aggregate.transactions.entries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc uses a type in minos-microservice-aggregate.minos.aggregate.transactions.entries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc.TransactionRepository→packages.core.minos-microservice-aggregate.minos.aggregate.transactions.entries.TransactionEntry
- Direction
- minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc uses minos-microservice-aggregate.minos.aggregate.transactions.entries, so a change to minos-microservice-aggregate.minos.aggregate.transactions.entries can break minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc, while a change to minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc can't break minos-microservice-aggregate.minos.aggregate.transactions.entries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc uses a module listed above it, which is the healthy direction.
13→4 minos-microservice-common.minos.common.database.clients.abc uses minos-microservice-common.minos.common.config.abc✕
- Connections
- 2 pairs of types, where a type in minos-microservice-common.minos.common.database.clients.abc uses a type in minos-microservice-common.minos.common.config.abc.
- The types involved
packages.core.minos-microservice-common.minos.common.database.clients.abc.DatabaseClient→packages.core.minos-microservice-common.minos.common.config.abc.Configpackages.core.minos-microservice-common.minos.common.database.clients.abc.DatabaseClientBuilder→packages.core.minos-microservice-common.minos.common.config.abc.Config
- Direction
- minos-microservice-common.minos.common.database.clients.abc uses minos-microservice-common.minos.common.config.abc, so a change to minos-microservice-common.minos.common.config.abc can break minos-microservice-common.minos.common.database.clients.abc, while a change to minos-microservice-common.minos.common.database.clients.abc can't break minos-microservice-common.minos.common.config.abc.
- Position
- Below the diagonal: minos-microservice-common.minos.common.database.clients.abc uses a module listed above it, which is the healthy direction.
13→5 minos-microservice-common.minos.common.database.clients.abc uses minos-microservice-common.minos.common.database.operations✕
- Connections
- 3 pairs of types, where a type in minos-microservice-common.minos.common.database.clients.abc uses a type in minos-microservice-common.minos.common.database.operations.
- The types involved
packages.core.minos-microservice-common.minos.common.database.clients.abc.DatabaseClient→packages.core.minos-microservice-common.minos.common.database.operations.ComposedDatabaseOperationpackages.core.minos-microservice-common.minos.common.database.clients.abc.DatabaseClient→packages.core.minos-microservice-common.minos.common.database.operations.DatabaseOperationpackages.core.minos-microservice-common.minos.common.database.clients.abc.DatabaseClient→packages.core.minos-microservice-common.minos.common.database.operations.DatabaseOperationFactory
- Direction
- minos-microservice-common.minos.common.database.clients.abc uses minos-microservice-common.minos.common.database.operations, so a change to minos-microservice-common.minos.common.database.operations can break minos-microservice-common.minos.common.database.clients.abc, while a change to minos-microservice-common.minos.common.database.clients.abc can't break minos-microservice-common.minos.common.database.operations.
- Position
- Below the diagonal: minos-microservice-common.minos.common.database.clients.abc uses a module listed above it, which is the healthy direction.
14→21 minos-microservice-common.minos.common.model.types.model_types uses minos-microservice-common.minos.common.model.abc part of a loop✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.model.types.model_types uses a type in minos-microservice-common.minos.common.model.abc.
- The types involved
packages.core.minos-microservice-common.minos.common.model.types.model_types.ModelType→packages.core.minos-microservice-common.minos.common.model.abc.Model
- Direction
- minos-microservice-common.minos.common.model.types.model_types uses minos-microservice-common.minos.common.model.abc, so a change to minos-microservice-common.minos.common.model.abc can break minos-microservice-common.minos.common.model.types.model_types, while a change to minos-microservice-common.minos.common.model.types.model_types can't break minos-microservice-common.minos.common.model.abc.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→4 minos-microservice-common.minos.common.setup uses minos-microservice-common.minos.common.config.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.setup uses a type in minos-microservice-common.minos.common.config.abc.
- The types involved
packages.core.minos-microservice-common.minos.common.setup.SetupMixin→packages.core.minos-microservice-common.minos.common.config.abc.Config
- Direction
- minos-microservice-common.minos.common.setup uses minos-microservice-common.minos.common.config.abc, so a change to minos-microservice-common.minos.common.config.abc can break minos-microservice-common.minos.common.setup, while a change to minos-microservice-common.minos.common.setup can't break minos-microservice-common.minos.common.config.abc.
- Position
- Below the diagonal: minos-microservice-common.minos.common.setup uses a module listed above it, which is the healthy direction.
16→7 minos-microservice-networks.minos.networks.brokers.collections.queues.abc uses minos-microservice-networks.minos.networks.brokers.messages.models.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-networks.minos.networks.brokers.collections.queues.abc uses a type in minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.collections.queues.abc.BrokerQueue→packages.core.minos-microservice-networks.minos.networks.brokers.messages.models.abc.BrokerMessage
- Direction
- minos-microservice-networks.minos.networks.brokers.collections.queues.abc uses minos-microservice-networks.minos.networks.brokers.messages.models.abc, so a change to minos-microservice-networks.minos.networks.brokers.messages.models.abc can break minos-microservice-networks.minos.networks.brokers.collections.queues.abc, while a change to minos-microservice-networks.minos.networks.brokers.collections.queues.abc can't break minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.collections.queues.abc uses a module listed above it, which is the healthy direction.
17→7 minos-microservice-networks.minos.networks.brokers.publishers.abc uses minos-microservice-networks.minos.networks.brokers.messages.models.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-networks.minos.networks.brokers.publishers.abc uses a type in minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.publishers.abc.BrokerPublisher→packages.core.minos-microservice-networks.minos.networks.brokers.messages.models.abc.BrokerMessage
- Direction
- minos-microservice-networks.minos.networks.brokers.publishers.abc uses minos-microservice-networks.minos.networks.brokers.messages.models.abc, so a change to minos-microservice-networks.minos.networks.brokers.messages.models.abc can break minos-microservice-networks.minos.networks.brokers.publishers.abc, while a change to minos-microservice-networks.minos.networks.brokers.publishers.abc can't break minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.publishers.abc uses a module listed above it, which is the healthy direction.
18→7 minos-microservice-networks.minos.networks.brokers.subscribers.abc uses minos-microservice-networks.minos.networks.brokers.messages.models.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-networks.minos.networks.brokers.subscribers.abc uses a type in minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.subscribers.abc.BrokerSubscriber→packages.core.minos-microservice-networks.minos.networks.brokers.messages.models.abc.BrokerMessage
- Direction
- minos-microservice-networks.minos.networks.brokers.subscribers.abc uses minos-microservice-networks.minos.networks.brokers.messages.models.abc, so a change to minos-microservice-networks.minos.networks.brokers.messages.models.abc can break minos-microservice-networks.minos.networks.brokers.subscribers.abc, while a change to minos-microservice-networks.minos.networks.brokers.subscribers.abc can't break minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.subscribers.abc uses a module listed above it, which is the healthy direction.
19→27 minos-microservice-saga.minos.saga.definitions.steps.conditional uses minos-microservice-saga.minos.saga.definitions.steps.abc part of a loop✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.definitions.steps.conditional uses a type in minos-microservice-saga.minos.saga.definitions.steps.abc.
- The types involved
packages.core.minos-microservice-saga.minos.saga.definitions.steps.conditional.ConditionalSagaStep→packages.core.minos-microservice-saga.minos.saga.definitions.steps.abc.SagaStep
- Direction
- minos-microservice-saga.minos.saga.definitions.steps.conditional uses minos-microservice-saga.minos.saga.definitions.steps.abc, so a change to minos-microservice-saga.minos.saga.definitions.steps.abc can break minos-microservice-saga.minos.saga.definitions.steps.conditional, while a change to minos-microservice-saga.minos.saga.definitions.steps.conditional can't break minos-microservice-saga.minos.saga.definitions.steps.abc.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→32 minos-microservice-saga.minos.saga.definitions.steps.conditional uses minos-microservice-saga.minos.saga.definitions.saga part of a loop✕
- Connections
- 3 pairs of types, where a type in minos-microservice-saga.minos.saga.definitions.steps.conditional uses a type in minos-microservice-saga.minos.saga.definitions.saga.
- The types involved
packages.core.minos-microservice-saga.minos.saga.definitions.steps.conditional.ConditionalSagaStep→packages.core.minos-microservice-saga.minos.saga.definitions.saga.Sagapackages.core.minos-microservice-saga.minos.saga.definitions.steps.conditional.ElseThenAlternative→packages.core.minos-microservice-saga.minos.saga.definitions.saga.Sagapackages.core.minos-microservice-saga.minos.saga.definitions.steps.conditional.IfThenAlternative→packages.core.minos-microservice-saga.minos.saga.definitions.saga.Saga
- Direction
- minos-microservice-saga.minos.saga.definitions.steps.conditional uses minos-microservice-saga.minos.saga.definitions.saga, so a change to minos-microservice-saga.minos.saga.definitions.saga can break minos-microservice-saga.minos.saga.definitions.steps.conditional, while a change to minos-microservice-saga.minos.saga.definitions.steps.conditional can't break minos-microservice-saga.minos.saga.definitions.saga.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→11 minos-microservice-aggregate.minos.aggregate.events.entries uses minos-microservice-aggregate.minos.aggregate.events.models✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.events.entries uses a type in minos-microservice-aggregate.minos.aggregate.events.models.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.events.entries.EventEntry→packages.core.minos-microservice-aggregate.minos.aggregate.events.models.Event
- Direction
- minos-microservice-aggregate.minos.aggregate.events.entries uses minos-microservice-aggregate.minos.aggregate.events.models, so a change to minos-microservice-aggregate.minos.aggregate.events.models can break minos-microservice-aggregate.minos.aggregate.events.entries, while a change to minos-microservice-aggregate.minos.aggregate.events.entries can't break minos-microservice-aggregate.minos.aggregate.events.models.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.events.entries uses a module listed above it, which is the healthy direction.
21→6 minos-microservice-common.minos.common.model.abc uses minos-microservice-common.minos.common.model.serializers.abc✕
- Connections
- 4 pairs of types, where a type in minos-microservice-common.minos.common.model.abc uses a type in minos-microservice-common.minos.common.model.serializers.abc.
- The types involved
packages.core.minos-microservice-common.minos.common.model.abc.Model→packages.core.minos-microservice-common.minos.common.model.serializers.abc.DataDecoderpackages.core.minos-microservice-common.minos.common.model.abc.Model→packages.core.minos-microservice-common.minos.common.model.serializers.abc.DataEncoderpackages.core.minos-microservice-common.minos.common.model.abc.Model→packages.core.minos-microservice-common.minos.common.model.serializers.abc.SchemaDecoderpackages.core.minos-microservice-common.minos.common.model.abc.Model→packages.core.minos-microservice-common.minos.common.model.serializers.abc.SchemaEncoder
- Direction
- minos-microservice-common.minos.common.model.abc uses minos-microservice-common.minos.common.model.serializers.abc, so a change to minos-microservice-common.minos.common.model.serializers.abc can break minos-microservice-common.minos.common.model.abc, while a change to minos-microservice-common.minos.common.model.abc can't break minos-microservice-common.minos.common.model.serializers.abc.
- Position
- Below the diagonal: minos-microservice-common.minos.common.model.abc uses a module listed above it, which is the healthy direction.
21→14 minos-microservice-common.minos.common.model.abc uses minos-microservice-common.minos.common.model.types.model_types✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.model.abc uses a type in minos-microservice-common.minos.common.model.types.model_types.
- The types involved
packages.core.minos-microservice-common.minos.common.model.abc.Model→packages.core.minos-microservice-common.minos.common.model.types.model_types.ModelType
- Direction
- minos-microservice-common.minos.common.model.abc uses minos-microservice-common.minos.common.model.types.model_types, so a change to minos-microservice-common.minos.common.model.types.model_types can break minos-microservice-common.minos.common.model.abc, while a change to minos-microservice-common.minos.common.model.abc can't break minos-microservice-common.minos.common.model.types.model_types.
- Position
- Below the diagonal: minos-microservice-common.minos.common.model.abc uses a module listed above it, which is the healthy direction.
22→4 minos-microservice-common.minos.common.pools uses minos-microservice-common.minos.common.config.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.pools uses a type in minos-microservice-common.minos.common.config.abc.
- The types involved
packages.core.minos-microservice-common.minos.common.pools.PoolFactory→packages.core.minos-microservice-common.minos.common.config.abc.Config
- Direction
- minos-microservice-common.minos.common.pools uses minos-microservice-common.minos.common.config.abc, so a change to minos-microservice-common.minos.common.config.abc can break minos-microservice-common.minos.common.pools, while a change to minos-microservice-common.minos.common.pools can't break minos-microservice-common.minos.common.config.abc.
- Position
- Below the diagonal: minos-microservice-common.minos.common.pools uses a module listed above it, which is the healthy direction.
22→15 minos-microservice-common.minos.common.pools uses minos-microservice-common.minos.common.setup✕
- Connections
- 2 pairs of types, where a type in minos-microservice-common.minos.common.pools uses a type in minos-microservice-common.minos.common.setup.
- The types involved
packages.core.minos-microservice-common.minos.common.pools.Pool→packages.core.minos-microservice-common.minos.common.setup.SetupMixinpackages.core.minos-microservice-common.minos.common.pools.PoolFactory→packages.core.minos-microservice-common.minos.common.setup.SetupMixin
- Direction
- minos-microservice-common.minos.common.pools uses minos-microservice-common.minos.common.setup, so a change to minos-microservice-common.minos.common.setup can break minos-microservice-common.minos.common.pools, while a change to minos-microservice-common.minos.common.pools can't break minos-microservice-common.minos.common.setup.
- Position
- Below the diagonal: minos-microservice-common.minos.common.pools uses a module listed above it, which is the healthy direction.
23→7 minos-microservice-networks.minos.networks.brokers.clients uses minos-microservice-networks.minos.networks.brokers.messages.models.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-networks.minos.networks.brokers.clients uses a type in minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.clients.BrokerClient→packages.core.minos-microservice-networks.minos.networks.brokers.messages.models.abc.BrokerMessage
- Direction
- minos-microservice-networks.minos.networks.brokers.clients uses minos-microservice-networks.minos.networks.brokers.messages.models.abc, so a change to minos-microservice-networks.minos.networks.brokers.messages.models.abc can break minos-microservice-networks.minos.networks.brokers.clients, while a change to minos-microservice-networks.minos.networks.brokers.clients can't break minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.clients uses a module listed above it, which is the healthy direction.
23→17 minos-microservice-networks.minos.networks.brokers.clients uses minos-microservice-networks.minos.networks.brokers.publishers.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-networks.minos.networks.brokers.clients uses a type in minos-microservice-networks.minos.networks.brokers.publishers.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.clients.BrokerClient→packages.core.minos-microservice-networks.minos.networks.brokers.publishers.abc.BrokerPublisher
- Direction
- minos-microservice-networks.minos.networks.brokers.clients uses minos-microservice-networks.minos.networks.brokers.publishers.abc, so a change to minos-microservice-networks.minos.networks.brokers.publishers.abc can break minos-microservice-networks.minos.networks.brokers.clients, while a change to minos-microservice-networks.minos.networks.brokers.clients can't break minos-microservice-networks.minos.networks.brokers.publishers.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.clients uses a module listed above it, which is the healthy direction.
23→18 minos-microservice-networks.minos.networks.brokers.clients uses minos-microservice-networks.minos.networks.brokers.subscribers.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-networks.minos.networks.brokers.clients uses a type in minos-microservice-networks.minos.networks.brokers.subscribers.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.clients.BrokerClient→packages.core.minos-microservice-networks.minos.networks.brokers.subscribers.abc.BrokerSubscriber
- Direction
- minos-microservice-networks.minos.networks.brokers.clients uses minos-microservice-networks.minos.networks.brokers.subscribers.abc, so a change to minos-microservice-networks.minos.networks.brokers.subscribers.abc can break minos-microservice-networks.minos.networks.brokers.clients, while a change to minos-microservice-networks.minos.networks.brokers.clients can't break minos-microservice-networks.minos.networks.brokers.subscribers.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.clients uses a module listed above it, which is the healthy direction.
24→7 minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl uses minos-microservice-networks.minos.networks.brokers.messages.models.abc✕
- Connections
- 2 pairs of types, where a type in minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl uses a type in minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl.DatabaseBrokerQueue→packages.core.minos-microservice-networks.minos.networks.brokers.messages.models.abc.BrokerMessagepackages.core.minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl._Entry→packages.core.minos-microservice-networks.minos.networks.brokers.messages.models.abc.BrokerMessage
- Direction
- minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl uses minos-microservice-networks.minos.networks.brokers.messages.models.abc, so a change to minos-microservice-networks.minos.networks.brokers.messages.models.abc can break minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl, while a change to minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl can't break minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl uses a module listed above it, which is the healthy direction.
24→16 minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl uses minos-microservice-networks.minos.networks.brokers.collections.queues.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl uses a type in minos-microservice-networks.minos.networks.brokers.collections.queues.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl.DatabaseBrokerQueue→packages.core.minos-microservice-networks.minos.networks.brokers.collections.queues.abc.BrokerQueue
- Direction
- minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl uses minos-microservice-networks.minos.networks.brokers.collections.queues.abc, so a change to minos-microservice-networks.minos.networks.brokers.collections.queues.abc can break minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl, while a change to minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl can't break minos-microservice-networks.minos.networks.brokers.collections.queues.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.collections.queues.database.impl uses a module listed above it, which is the healthy direction.
25→7 minos-microservice-networks.minos.networks.brokers.collections.queues.memory uses minos-microservice-networks.minos.networks.brokers.messages.models.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-networks.minos.networks.brokers.collections.queues.memory uses a type in minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.collections.queues.memory.InMemoryBrokerQueue→packages.core.minos-microservice-networks.minos.networks.brokers.messages.models.abc.BrokerMessage
- Direction
- minos-microservice-networks.minos.networks.brokers.collections.queues.memory uses minos-microservice-networks.minos.networks.brokers.messages.models.abc, so a change to minos-microservice-networks.minos.networks.brokers.messages.models.abc can break minos-microservice-networks.minos.networks.brokers.collections.queues.memory, while a change to minos-microservice-networks.minos.networks.brokers.collections.queues.memory can't break minos-microservice-networks.minos.networks.brokers.messages.models.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.collections.queues.memory uses a module listed above it, which is the healthy direction.
25→16 minos-microservice-networks.minos.networks.brokers.collections.queues.memory uses minos-microservice-networks.minos.networks.brokers.collections.queues.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-networks.minos.networks.brokers.collections.queues.memory uses a type in minos-microservice-networks.minos.networks.brokers.collections.queues.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.collections.queues.memory.InMemoryBrokerQueue→packages.core.minos-microservice-networks.minos.networks.brokers.collections.queues.abc.BrokerQueue
- Direction
- minos-microservice-networks.minos.networks.brokers.collections.queues.memory uses minos-microservice-networks.minos.networks.brokers.collections.queues.abc, so a change to minos-microservice-networks.minos.networks.brokers.collections.queues.abc can break minos-microservice-networks.minos.networks.brokers.collections.queues.memory, while a change to minos-microservice-networks.minos.networks.brokers.collections.queues.memory can't break minos-microservice-networks.minos.networks.brokers.collections.queues.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.collections.queues.memory uses a module listed above it, which is the healthy direction.
26→16 minos-microservice-networks.minos.networks.brokers.publishers.queued.queues.abc uses minos-microservice-networks.minos.networks.brokers.collections.queues.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-networks.minos.networks.brokers.publishers.queued.queues.abc uses a type in minos-microservice-networks.minos.networks.brokers.collections.queues.abc.
- The types involved
packages.core.minos-microservice-networks.minos.networks.brokers.publishers.queued.queues.abc.BrokerPublisherQueue→packages.core.minos-microservice-networks.minos.networks.brokers.collections.queues.abc.BrokerQueue
- Direction
- minos-microservice-networks.minos.networks.brokers.publishers.queued.queues.abc uses minos-microservice-networks.minos.networks.brokers.collections.queues.abc, so a change to minos-microservice-networks.minos.networks.brokers.collections.queues.abc can break minos-microservice-networks.minos.networks.brokers.publishers.queued.queues.abc, while a change to minos-microservice-networks.minos.networks.brokers.publishers.queued.queues.abc can't break minos-microservice-networks.minos.networks.brokers.collections.queues.abc.
- Position
- Below the diagonal: minos-microservice-networks.minos.networks.brokers.publishers.queued.queues.abc uses a module listed above it, which is the healthy direction.
27→19 minos-microservice-saga.minos.saga.definitions.steps.abc uses minos-microservice-saga.minos.saga.definitions.steps.conditional✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.definitions.steps.abc uses a type in minos-microservice-saga.minos.saga.definitions.steps.conditional.
- The types involved
packages.core.minos-microservice-saga.minos.saga.definitions.steps.abc.SagaStep→packages.core.minos-microservice-saga.minos.saga.definitions.steps.conditional.ConditionalSagaStep
- Direction
- minos-microservice-saga.minos.saga.definitions.steps.abc uses minos-microservice-saga.minos.saga.definitions.steps.conditional, so a change to minos-microservice-saga.minos.saga.definitions.steps.conditional can break minos-microservice-saga.minos.saga.definitions.steps.abc, while a change to minos-microservice-saga.minos.saga.definitions.steps.abc can't break minos-microservice-saga.minos.saga.definitions.steps.conditional.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.definitions.steps.abc uses a module listed above it, which is the healthy direction.
27→32 minos-microservice-saga.minos.saga.definitions.steps.abc uses minos-microservice-saga.minos.saga.definitions.saga part of a loop✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.definitions.steps.abc uses a type in minos-microservice-saga.minos.saga.definitions.saga.
- The types involved
packages.core.minos-microservice-saga.minos.saga.definitions.steps.abc.SagaStep→packages.core.minos-microservice-saga.minos.saga.definitions.saga.Saga
- Direction
- minos-microservice-saga.minos.saga.definitions.steps.abc uses minos-microservice-saga.minos.saga.definitions.saga, so a change to minos-microservice-saga.minos.saga.definitions.saga can break minos-microservice-saga.minos.saga.definitions.steps.abc, while a change to minos-microservice-saga.minos.saga.definitions.steps.abc can't break minos-microservice-saga.minos.saga.definitions.saga.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→3 minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses minos-microservice-aggregate.minos.aggregate.transactions.entries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses a type in minos-microservice-aggregate.minos.aggregate.transactions.entries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.events.repositories.abc.EventRepository→packages.core.minos-microservice-aggregate.minos.aggregate.transactions.entries.TransactionEntry
- Direction
- minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses minos-microservice-aggregate.minos.aggregate.transactions.entries, so a change to minos-microservice-aggregate.minos.aggregate.transactions.entries can break minos-microservice-aggregate.minos.aggregate.events.repositories.abc, while a change to minos-microservice-aggregate.minos.aggregate.events.repositories.abc can't break minos-microservice-aggregate.minos.aggregate.transactions.entries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses a module listed above it, which is the healthy direction.
28→11 minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses minos-microservice-aggregate.minos.aggregate.events.models✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses a type in minos-microservice-aggregate.minos.aggregate.events.models.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.events.repositories.abc.EventRepository→packages.core.minos-microservice-aggregate.minos.aggregate.events.models.Event
- Direction
- minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses minos-microservice-aggregate.minos.aggregate.events.models, so a change to minos-microservice-aggregate.minos.aggregate.events.models can break minos-microservice-aggregate.minos.aggregate.events.repositories.abc, while a change to minos-microservice-aggregate.minos.aggregate.events.repositories.abc can't break minos-microservice-aggregate.minos.aggregate.events.models.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses a module listed above it, which is the healthy direction.
28→12 minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses a type in minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.events.repositories.abc.EventRepository→packages.core.minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc.TransactionRepository
- Direction
- minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc, so a change to minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc can break minos-microservice-aggregate.minos.aggregate.events.repositories.abc, while a change to minos-microservice-aggregate.minos.aggregate.events.repositories.abc can't break minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses a module listed above it, which is the healthy direction.
28→20 minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses minos-microservice-aggregate.minos.aggregate.events.entries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses a type in minos-microservice-aggregate.minos.aggregate.events.entries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.events.repositories.abc.EventRepository→packages.core.minos-microservice-aggregate.minos.aggregate.events.entries.EventEntry
- Direction
- minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses minos-microservice-aggregate.minos.aggregate.events.entries, so a change to minos-microservice-aggregate.minos.aggregate.events.entries can break minos-microservice-aggregate.minos.aggregate.events.repositories.abc, while a change to minos-microservice-aggregate.minos.aggregate.events.repositories.abc can't break minos-microservice-aggregate.minos.aggregate.events.entries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.events.repositories.abc uses a module listed above it, which is the healthy direction.
29→20 minos-microservice-aggregate.minos.aggregate.snapshots.entries uses minos-microservice-aggregate.minos.aggregate.events.entries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.entries uses a type in minos-microservice-aggregate.minos.aggregate.events.entries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.entries.SnapshotEntry→packages.core.minos-microservice-aggregate.minos.aggregate.events.entries.EventEntry
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.entries uses minos-microservice-aggregate.minos.aggregate.events.entries, so a change to minos-microservice-aggregate.minos.aggregate.events.entries can break minos-microservice-aggregate.minos.aggregate.snapshots.entries, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.entries can't break minos-microservice-aggregate.minos.aggregate.events.entries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.entries uses a module listed above it, which is the healthy direction.
29→37 minos-microservice-aggregate.minos.aggregate.snapshots.entries uses minos-microservice-aggregate.minos.aggregate.entities.models part of a loop✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.entries uses a type in minos-microservice-aggregate.minos.aggregate.entities.models.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.entries.SnapshotEntry→packages.core.minos-microservice-aggregate.minos.aggregate.entities.models.RootEntity
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.entries uses minos-microservice-aggregate.minos.aggregate.entities.models, so a change to minos-microservice-aggregate.minos.aggregate.entities.models can break minos-microservice-aggregate.minos.aggregate.snapshots.entries, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.entries can't break minos-microservice-aggregate.minos.aggregate.entities.models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→4 minos-microservice-common.minos.common.database.pools uses minos-microservice-common.minos.common.config.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.database.pools uses a type in minos-microservice-common.minos.common.config.abc.
- The types involved
packages.core.minos-microservice-common.minos.common.database.pools.DatabaseClientPool→packages.core.minos-microservice-common.minos.common.config.abc.Config
- Direction
- minos-microservice-common.minos.common.database.pools uses minos-microservice-common.minos.common.config.abc, so a change to minos-microservice-common.minos.common.config.abc can break minos-microservice-common.minos.common.database.pools, while a change to minos-microservice-common.minos.common.database.pools can't break minos-microservice-common.minos.common.config.abc.
- Position
- Below the diagonal: minos-microservice-common.minos.common.database.pools uses a module listed above it, which is the healthy direction.
30→13 minos-microservice-common.minos.common.database.pools uses minos-microservice-common.minos.common.database.clients.abc✕
- Connections
- 2 pairs of types, where a type in minos-microservice-common.minos.common.database.pools uses a type in minos-microservice-common.minos.common.database.clients.abc.
- The types involved
packages.core.minos-microservice-common.minos.common.database.pools.DatabaseClientPool→packages.core.minos-microservice-common.minos.common.database.clients.abc.DatabaseClientpackages.core.minos-microservice-common.minos.common.database.pools.DatabaseClientPool→packages.core.minos-microservice-common.minos.common.database.clients.abc.DatabaseClientBuilder
- Direction
- minos-microservice-common.minos.common.database.pools uses minos-microservice-common.minos.common.database.clients.abc, so a change to minos-microservice-common.minos.common.database.clients.abc can break minos-microservice-common.minos.common.database.pools, while a change to minos-microservice-common.minos.common.database.pools can't break minos-microservice-common.minos.common.database.clients.abc.
- Position
- Below the diagonal: minos-microservice-common.minos.common.database.pools uses a module listed above it, which is the healthy direction.
30→22 minos-microservice-common.minos.common.database.pools uses minos-microservice-common.minos.common.pools✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.database.pools uses a type in minos-microservice-common.minos.common.pools.
- The types involved
packages.core.minos-microservice-common.minos.common.database.pools.DatabaseClientPool→packages.core.minos-microservice-common.minos.common.pools.Pool
- Direction
- minos-microservice-common.minos.common.database.pools uses minos-microservice-common.minos.common.pools, so a change to minos-microservice-common.minos.common.pools can break minos-microservice-common.minos.common.database.pools, while a change to minos-microservice-common.minos.common.database.pools can't break minos-microservice-common.minos.common.pools.
- Position
- Below the diagonal: minos-microservice-common.minos.common.database.pools uses a module listed above it, which is the healthy direction.
31→14 minos-microservice-common.minos.common.model.dynamic.abc uses minos-microservice-common.minos.common.model.types.model_types✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.model.dynamic.abc uses a type in minos-microservice-common.minos.common.model.types.model_types.
- The types involved
packages.core.minos-microservice-common.minos.common.model.dynamic.abc.DynamicModel→packages.core.minos-microservice-common.minos.common.model.types.model_types.ModelType
- Direction
- minos-microservice-common.minos.common.model.dynamic.abc uses minos-microservice-common.minos.common.model.types.model_types, so a change to minos-microservice-common.minos.common.model.types.model_types can break minos-microservice-common.minos.common.model.dynamic.abc, while a change to minos-microservice-common.minos.common.model.dynamic.abc can't break minos-microservice-common.minos.common.model.types.model_types.
- Position
- Below the diagonal: minos-microservice-common.minos.common.model.dynamic.abc uses a module listed above it, which is the healthy direction.
31→21 minos-microservice-common.minos.common.model.dynamic.abc uses minos-microservice-common.minos.common.model.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.model.dynamic.abc uses a type in minos-microservice-common.minos.common.model.abc.
- The types involved
packages.core.minos-microservice-common.minos.common.model.dynamic.abc.DynamicModel→packages.core.minos-microservice-common.minos.common.model.abc.Model
- Direction
- minos-microservice-common.minos.common.model.dynamic.abc uses minos-microservice-common.minos.common.model.abc, so a change to minos-microservice-common.minos.common.model.abc can break minos-microservice-common.minos.common.model.dynamic.abc, while a change to minos-microservice-common.minos.common.model.dynamic.abc can't break minos-microservice-common.minos.common.model.abc.
- Position
- Below the diagonal: minos-microservice-common.minos.common.model.dynamic.abc uses a module listed above it, which is the healthy direction.
32→19 minos-microservice-saga.minos.saga.definitions.saga uses minos-microservice-saga.minos.saga.definitions.steps.conditional✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.definitions.saga uses a type in minos-microservice-saga.minos.saga.definitions.steps.conditional.
- The types involved
packages.core.minos-microservice-saga.minos.saga.definitions.saga.Saga→packages.core.minos-microservice-saga.minos.saga.definitions.steps.conditional.ConditionalSagaStep
- Direction
- minos-microservice-saga.minos.saga.definitions.saga uses minos-microservice-saga.minos.saga.definitions.steps.conditional, so a change to minos-microservice-saga.minos.saga.definitions.steps.conditional can break minos-microservice-saga.minos.saga.definitions.saga, while a change to minos-microservice-saga.minos.saga.definitions.saga can't break minos-microservice-saga.minos.saga.definitions.steps.conditional.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.definitions.saga uses a module listed above it, which is the healthy direction.
32→27 minos-microservice-saga.minos.saga.definitions.saga uses minos-microservice-saga.minos.saga.definitions.steps.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.definitions.saga uses a type in minos-microservice-saga.minos.saga.definitions.steps.abc.
- The types involved
packages.core.minos-microservice-saga.minos.saga.definitions.saga.Saga→packages.core.minos-microservice-saga.minos.saga.definitions.steps.abc.SagaStep
- Direction
- minos-microservice-saga.minos.saga.definitions.saga uses minos-microservice-saga.minos.saga.definitions.steps.abc, so a change to minos-microservice-saga.minos.saga.definitions.steps.abc can break minos-microservice-saga.minos.saga.definitions.saga, while a change to minos-microservice-saga.minos.saga.definitions.saga can't break minos-microservice-saga.minos.saga.definitions.steps.abc.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.definitions.saga uses a module listed above it, which is the healthy direction.
33→10 minos-microservice-saga.minos.saga.executions.steps.abc uses minos-microservice-saga.minos.saga.context✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.executions.steps.abc uses a type in minos-microservice-saga.minos.saga.context.
- The types involved
packages.core.minos-microservice-saga.minos.saga.executions.steps.abc.SagaStepExecution→packages.core.minos-microservice-saga.minos.saga.context.SagaContext
- Direction
- minos-microservice-saga.minos.saga.executions.steps.abc uses minos-microservice-saga.minos.saga.context, so a change to minos-microservice-saga.minos.saga.context can break minos-microservice-saga.minos.saga.executions.steps.abc, while a change to minos-microservice-saga.minos.saga.executions.steps.abc can't break minos-microservice-saga.minos.saga.context.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.executions.steps.abc uses a module listed above it, which is the healthy direction.
33→27 minos-microservice-saga.minos.saga.executions.steps.abc uses minos-microservice-saga.minos.saga.definitions.steps.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.executions.steps.abc uses a type in minos-microservice-saga.minos.saga.definitions.steps.abc.
- The types involved
packages.core.minos-microservice-saga.minos.saga.executions.steps.abc.SagaStepExecution→packages.core.minos-microservice-saga.minos.saga.definitions.steps.abc.SagaStep
- Direction
- minos-microservice-saga.minos.saga.executions.steps.abc uses minos-microservice-saga.minos.saga.definitions.steps.abc, so a change to minos-microservice-saga.minos.saga.definitions.steps.abc can break minos-microservice-saga.minos.saga.executions.steps.abc, while a change to minos-microservice-saga.minos.saga.executions.steps.abc can't break minos-microservice-saga.minos.saga.definitions.steps.abc.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.executions.steps.abc uses a module listed above it, which is the healthy direction.
34→2 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses minos-microservice-aggregate.minos.aggregate.queries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses a type in minos-microservice-aggregate.minos.aggregate.queries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.SnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.queries._Condition
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses minos-microservice-aggregate.minos.aggregate.queries, so a change to minos-microservice-aggregate.minos.aggregate.queries can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc can't break minos-microservice-aggregate.minos.aggregate.queries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses a module listed above it, which is the healthy direction.
34→29 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses minos-microservice-aggregate.minos.aggregate.snapshots.entries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses a type in minos-microservice-aggregate.minos.aggregate.snapshots.entries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.SnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.entries.SnapshotEntry
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses minos-microservice-aggregate.minos.aggregate.snapshots.entries, so a change to minos-microservice-aggregate.minos.aggregate.snapshots.entries can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc can't break minos-microservice-aggregate.minos.aggregate.snapshots.entries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses a module listed above it, which is the healthy direction.
34→37 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses minos-microservice-aggregate.minos.aggregate.entities.models part of a loop✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses a type in minos-microservice-aggregate.minos.aggregate.entities.models.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.SnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.entities.models.RootEntity
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc uses minos-microservice-aggregate.minos.aggregate.entities.models, so a change to minos-microservice-aggregate.minos.aggregate.entities.models can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc can't break minos-microservice-aggregate.minos.aggregate.entities.models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→5 minos-microservice-common.minos.common.database.mixins uses minos-microservice-common.minos.common.database.operations✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.database.mixins uses a type in minos-microservice-common.minos.common.database.operations.
- The types involved
packages.core.minos-microservice-common.minos.common.database.mixins.DatabaseMixin→packages.core.minos-microservice-common.minos.common.database.operations.DatabaseOperation
- Direction
- minos-microservice-common.minos.common.database.mixins uses minos-microservice-common.minos.common.database.operations, so a change to minos-microservice-common.minos.common.database.operations can break minos-microservice-common.minos.common.database.mixins, while a change to minos-microservice-common.minos.common.database.mixins can't break minos-microservice-common.minos.common.database.operations.
- Position
- Below the diagonal: minos-microservice-common.minos.common.database.mixins uses a module listed above it, which is the healthy direction.
35→15 minos-microservice-common.minos.common.database.mixins uses minos-microservice-common.minos.common.setup✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.database.mixins uses a type in minos-microservice-common.minos.common.setup.
- The types involved
packages.core.minos-microservice-common.minos.common.database.mixins.DatabaseMixin→packages.core.minos-microservice-common.minos.common.setup.SetupMixin
- Direction
- minos-microservice-common.minos.common.database.mixins uses minos-microservice-common.minos.common.setup, so a change to minos-microservice-common.minos.common.setup can break minos-microservice-common.minos.common.database.mixins, while a change to minos-microservice-common.minos.common.database.mixins can't break minos-microservice-common.minos.common.setup.
- Position
- Below the diagonal: minos-microservice-common.minos.common.database.mixins uses a module listed above it, which is the healthy direction.
35→22 minos-microservice-common.minos.common.database.mixins uses minos-microservice-common.minos.common.pools✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.database.mixins uses a type in minos-microservice-common.minos.common.pools.
- The types involved
packages.core.minos-microservice-common.minos.common.database.mixins.DatabaseMixin→packages.core.minos-microservice-common.minos.common.pools.PoolFactory
- Direction
- minos-microservice-common.minos.common.database.mixins uses minos-microservice-common.minos.common.pools, so a change to minos-microservice-common.minos.common.pools can break minos-microservice-common.minos.common.database.mixins, while a change to minos-microservice-common.minos.common.database.mixins can't break minos-microservice-common.minos.common.pools.
- Position
- Below the diagonal: minos-microservice-common.minos.common.database.mixins uses a module listed above it, which is the healthy direction.
35→30 minos-microservice-common.minos.common.database.mixins uses minos-microservice-common.minos.common.database.pools✕
- Connections
- 1 pair of types, where a type in minos-microservice-common.minos.common.database.mixins uses a type in minos-microservice-common.minos.common.database.pools.
- The types involved
packages.core.minos-microservice-common.minos.common.database.mixins.DatabaseMixin→packages.core.minos-microservice-common.minos.common.database.pools.DatabaseClientPool
- Direction
- minos-microservice-common.minos.common.database.mixins uses minos-microservice-common.minos.common.database.pools, so a change to minos-microservice-common.minos.common.database.pools can break minos-microservice-common.minos.common.database.mixins, while a change to minos-microservice-common.minos.common.database.mixins can't break minos-microservice-common.minos.common.database.pools.
- Position
- Below the diagonal: minos-microservice-common.minos.common.database.mixins uses a module listed above it, which is the healthy direction.
36→10 minos-microservice-saga.minos.saga.executions.saga uses minos-microservice-saga.minos.saga.context✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.executions.saga uses a type in minos-microservice-saga.minos.saga.context.
- The types involved
packages.core.minos-microservice-saga.minos.saga.executions.saga.SagaExecution→packages.core.minos-microservice-saga.minos.saga.context.SagaContext
- Direction
- minos-microservice-saga.minos.saga.executions.saga uses minos-microservice-saga.minos.saga.context, so a change to minos-microservice-saga.minos.saga.context can break minos-microservice-saga.minos.saga.executions.saga, while a change to minos-microservice-saga.minos.saga.executions.saga can't break minos-microservice-saga.minos.saga.context.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.executions.saga uses a module listed above it, which is the healthy direction.
36→27 minos-microservice-saga.minos.saga.executions.saga uses minos-microservice-saga.minos.saga.definitions.steps.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.executions.saga uses a type in minos-microservice-saga.minos.saga.definitions.steps.abc.
- The types involved
packages.core.minos-microservice-saga.minos.saga.executions.saga.SagaExecution→packages.core.minos-microservice-saga.minos.saga.definitions.steps.abc.SagaStep
- Direction
- minos-microservice-saga.minos.saga.executions.saga uses minos-microservice-saga.minos.saga.definitions.steps.abc, so a change to minos-microservice-saga.minos.saga.definitions.steps.abc can break minos-microservice-saga.minos.saga.executions.saga, while a change to minos-microservice-saga.minos.saga.executions.saga can't break minos-microservice-saga.minos.saga.definitions.steps.abc.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.executions.saga uses a module listed above it, which is the healthy direction.
36→32 minos-microservice-saga.minos.saga.executions.saga uses minos-microservice-saga.minos.saga.definitions.saga✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.executions.saga uses a type in minos-microservice-saga.minos.saga.definitions.saga.
- The types involved
packages.core.minos-microservice-saga.minos.saga.executions.saga.SagaExecution→packages.core.minos-microservice-saga.minos.saga.definitions.saga.Saga
- Direction
- minos-microservice-saga.minos.saga.executions.saga uses minos-microservice-saga.minos.saga.definitions.saga, so a change to minos-microservice-saga.minos.saga.definitions.saga can break minos-microservice-saga.minos.saga.executions.saga, while a change to minos-microservice-saga.minos.saga.executions.saga can't break minos-microservice-saga.minos.saga.definitions.saga.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.executions.saga uses a module listed above it, which is the healthy direction.
36→33 minos-microservice-saga.minos.saga.executions.saga uses minos-microservice-saga.minos.saga.executions.steps.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.executions.saga uses a type in minos-microservice-saga.minos.saga.executions.steps.abc.
- The types involved
packages.core.minos-microservice-saga.minos.saga.executions.saga.SagaExecution→packages.core.minos-microservice-saga.minos.saga.executions.steps.abc.SagaStepExecution
- Direction
- minos-microservice-saga.minos.saga.executions.saga uses minos-microservice-saga.minos.saga.executions.steps.abc, so a change to minos-microservice-saga.minos.saga.executions.steps.abc can break minos-microservice-saga.minos.saga.executions.saga, while a change to minos-microservice-saga.minos.saga.executions.saga can't break minos-microservice-saga.minos.saga.executions.steps.abc.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.executions.saga uses a module listed above it, which is the healthy direction.
37→2 minos-microservice-aggregate.minos.aggregate.entities.models uses minos-microservice-aggregate.minos.aggregate.queries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.entities.models uses a type in minos-microservice-aggregate.minos.aggregate.queries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.entities.models.RootEntity→packages.core.minos-microservice-aggregate.minos.aggregate.queries._Condition
- Direction
- minos-microservice-aggregate.minos.aggregate.entities.models uses minos-microservice-aggregate.minos.aggregate.queries, so a change to minos-microservice-aggregate.minos.aggregate.queries can break minos-microservice-aggregate.minos.aggregate.entities.models, while a change to minos-microservice-aggregate.minos.aggregate.entities.models can't break minos-microservice-aggregate.minos.aggregate.queries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.entities.models uses a module listed above it, which is the healthy direction.
37→11 minos-microservice-aggregate.minos.aggregate.entities.models uses minos-microservice-aggregate.minos.aggregate.events.models✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.entities.models uses a type in minos-microservice-aggregate.minos.aggregate.events.models.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.entities.models.RootEntity→packages.core.minos-microservice-aggregate.minos.aggregate.events.models.Event
- Direction
- minos-microservice-aggregate.minos.aggregate.entities.models uses minos-microservice-aggregate.minos.aggregate.events.models, so a change to minos-microservice-aggregate.minos.aggregate.events.models can break minos-microservice-aggregate.minos.aggregate.entities.models, while a change to minos-microservice-aggregate.minos.aggregate.entities.models can't break minos-microservice-aggregate.minos.aggregate.events.models.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.entities.models uses a module listed above it, which is the healthy direction.
37→20 minos-microservice-aggregate.minos.aggregate.entities.models uses minos-microservice-aggregate.minos.aggregate.events.entries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.entities.models uses a type in minos-microservice-aggregate.minos.aggregate.events.entries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.entities.models.RootEntity→packages.core.minos-microservice-aggregate.minos.aggregate.events.entries.EventEntry
- Direction
- minos-microservice-aggregate.minos.aggregate.entities.models uses minos-microservice-aggregate.minos.aggregate.events.entries, so a change to minos-microservice-aggregate.minos.aggregate.events.entries can break minos-microservice-aggregate.minos.aggregate.entities.models, while a change to minos-microservice-aggregate.minos.aggregate.entities.models can't break minos-microservice-aggregate.minos.aggregate.events.entries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.entities.models uses a module listed above it, which is the healthy direction.
37→28 minos-microservice-aggregate.minos.aggregate.entities.models uses minos-microservice-aggregate.minos.aggregate.events.repositories.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.entities.models uses a type in minos-microservice-aggregate.minos.aggregate.events.repositories.abc.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.entities.models.RootEntity→packages.core.minos-microservice-aggregate.minos.aggregate.events.repositories.abc.EventRepository
- Direction
- minos-microservice-aggregate.minos.aggregate.entities.models uses minos-microservice-aggregate.minos.aggregate.events.repositories.abc, so a change to minos-microservice-aggregate.minos.aggregate.events.repositories.abc can break minos-microservice-aggregate.minos.aggregate.entities.models, while a change to minos-microservice-aggregate.minos.aggregate.entities.models can't break minos-microservice-aggregate.minos.aggregate.events.repositories.abc.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.entities.models uses a module listed above it, which is the healthy direction.
37→34 minos-microservice-aggregate.minos.aggregate.entities.models uses minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.entities.models uses a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.entities.models.RootEntity→packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.SnapshotRepository
- Direction
- minos-microservice-aggregate.minos.aggregate.entities.models uses minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc, so a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc can break minos-microservice-aggregate.minos.aggregate.entities.models, while a change to minos-microservice-aggregate.minos.aggregate.entities.models can't break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.entities.models uses a module listed above it, which is the healthy direction.
38→2 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses minos-microservice-aggregate.minos.aggregate.queries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses a type in minos-microservice-aggregate.minos.aggregate.queries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory.InMemorySnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.queries._Condition
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses minos-microservice-aggregate.minos.aggregate.queries, so a change to minos-microservice-aggregate.minos.aggregate.queries can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory can't break minos-microservice-aggregate.minos.aggregate.queries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses a module listed above it, which is the healthy direction.
38→12 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses a type in minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory.InMemorySnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc.TransactionRepository
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc, so a change to minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory can't break minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses a module listed above it, which is the healthy direction.
38→28 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses minos-microservice-aggregate.minos.aggregate.events.repositories.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses a type in minos-microservice-aggregate.minos.aggregate.events.repositories.abc.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory.InMemorySnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.events.repositories.abc.EventRepository
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses minos-microservice-aggregate.minos.aggregate.events.repositories.abc, so a change to minos-microservice-aggregate.minos.aggregate.events.repositories.abc can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory can't break minos-microservice-aggregate.minos.aggregate.events.repositories.abc.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses a module listed above it, which is the healthy direction.
38→29 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses minos-microservice-aggregate.minos.aggregate.snapshots.entries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses a type in minos-microservice-aggregate.minos.aggregate.snapshots.entries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory.InMemorySnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.entries.SnapshotEntry
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses minos-microservice-aggregate.minos.aggregate.snapshots.entries, so a change to minos-microservice-aggregate.minos.aggregate.snapshots.entries can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory can't break minos-microservice-aggregate.minos.aggregate.snapshots.entries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses a module listed above it, which is the healthy direction.
38→34 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory.InMemorySnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.SnapshotRepository
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc, so a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory can't break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.memory uses a module listed above it, which is the healthy direction.
39→32 minos-microservice-saga.minos.saga.manager uses minos-microservice-saga.minos.saga.definitions.saga✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.manager uses a type in minos-microservice-saga.minos.saga.definitions.saga.
- The types involved
packages.core.minos-microservice-saga.minos.saga.manager.SagaManager→packages.core.minos-microservice-saga.minos.saga.definitions.saga.Saga
- Direction
- minos-microservice-saga.minos.saga.manager uses minos-microservice-saga.minos.saga.definitions.saga, so a change to minos-microservice-saga.minos.saga.definitions.saga can break minos-microservice-saga.minos.saga.manager, while a change to minos-microservice-saga.minos.saga.manager can't break minos-microservice-saga.minos.saga.definitions.saga.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.manager uses a module listed above it, which is the healthy direction.
39→36 minos-microservice-saga.minos.saga.manager uses minos-microservice-saga.minos.saga.executions.saga✕
- Connections
- 1 pair of types, where a type in minos-microservice-saga.minos.saga.manager uses a type in minos-microservice-saga.minos.saga.executions.saga.
- The types involved
packages.core.minos-microservice-saga.minos.saga.manager.SagaManager→packages.core.minos-microservice-saga.minos.saga.executions.saga.SagaExecution
- Direction
- minos-microservice-saga.minos.saga.manager uses minos-microservice-saga.minos.saga.executions.saga, so a change to minos-microservice-saga.minos.saga.executions.saga can break minos-microservice-saga.minos.saga.manager, while a change to minos-microservice-saga.minos.saga.manager can't break minos-microservice-saga.minos.saga.executions.saga.
- Position
- Below the diagonal: minos-microservice-saga.minos.saga.manager uses a module listed above it, which is the healthy direction.
40→2 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.queries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a type in minos-microservice-aggregate.minos.aggregate.queries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl.DatabaseSnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.queries._Condition
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.queries, so a change to minos-microservice-aggregate.minos.aggregate.queries can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl can't break minos-microservice-aggregate.minos.aggregate.queries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a module listed above it, which is the healthy direction.
40→11 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.events.models✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a type in minos-microservice-aggregate.minos.aggregate.events.models.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl.DatabaseSnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.events.models.Event
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.events.models, so a change to minos-microservice-aggregate.minos.aggregate.events.models can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl can't break minos-microservice-aggregate.minos.aggregate.events.models.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a module listed above it, which is the healthy direction.
40→12 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a type in minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl.DatabaseSnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc.TransactionRepository
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc, so a change to minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl can't break minos-microservice-aggregate.minos.aggregate.transactions.repositories.abc.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a module listed above it, which is the healthy direction.
40→20 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.events.entries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a type in minos-microservice-aggregate.minos.aggregate.events.entries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl.DatabaseSnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.events.entries.EventEntry
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.events.entries, so a change to minos-microservice-aggregate.minos.aggregate.events.entries can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl can't break minos-microservice-aggregate.minos.aggregate.events.entries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a module listed above it, which is the healthy direction.
40→28 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.events.repositories.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a type in minos-microservice-aggregate.minos.aggregate.events.repositories.abc.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl.DatabaseSnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.events.repositories.abc.EventRepository
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.events.repositories.abc, so a change to minos-microservice-aggregate.minos.aggregate.events.repositories.abc can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl can't break minos-microservice-aggregate.minos.aggregate.events.repositories.abc.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a module listed above it, which is the healthy direction.
40→29 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.snapshots.entries✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a type in minos-microservice-aggregate.minos.aggregate.snapshots.entries.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl.DatabaseSnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.entries.SnapshotEntry
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.snapshots.entries, so a change to minos-microservice-aggregate.minos.aggregate.snapshots.entries can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl can't break minos-microservice-aggregate.minos.aggregate.snapshots.entries.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a module listed above it, which is the healthy direction.
40→34 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl.DatabaseSnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.SnapshotRepository
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc, so a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl can't break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.abc.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a module listed above it, which is the healthy direction.
40→37 minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.entities.models✕
- Connections
- 1 pair of types, where a type in minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a type in minos-microservice-aggregate.minos.aggregate.entities.models.
- The types involved
packages.core.minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl.DatabaseSnapshotRepository→packages.core.minos-microservice-aggregate.minos.aggregate.entities.models.RootEntity
- Direction
- minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses minos-microservice-aggregate.minos.aggregate.entities.models, so a change to minos-microservice-aggregate.minos.aggregate.entities.models can break minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl, while a change to minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl can't break minos-microservice-aggregate.minos.aggregate.entities.models.
- Position
- Below the diagonal: minos-microservice-aggregate.minos.aggregate.snapshots.repositories.database.impl uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 119 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 62 | High / Critical |
| A02:2025 — Security Misconfiguration | 56 | High / Critical |
| A07:2025 — Authentication Failures | 5 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3); Resolve the 28 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED; Resolve the 28 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3). | +6.5 pts | Low | Secret Scanning |
| Resolve the 28 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +3.8 pts | Medium | Supply-chain Provenance & Signing |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.5 pts | Low | ADR Quality |
| Resolve the 28 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +2.7 pts | Medium | Static Analysis (SAST) |
| Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. | +1.3 pts | Low | Secrets (history) |
| Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.3 pts | Low | Dependency Vulnerabilities |
| Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). | +1.3 pts | Low | Dependency Vulnerabilities |
| Resolve the 29 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (28), REDACTED. | +2.6 pts | Medium | IaC & Container Security |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
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 68 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 — 68 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, 529 of 552 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (codecov.yml) and a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.py), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — the Python suite (24 distributions) did not finish re-running within its budget: the Python suite did not finish re-running within its tier budget.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 117 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 101 of the 423 production source files in this repository: 306 are under the ~2,400-byte size floor this dimension measures over, and the remaining 16 have no attributable history left to measure.
- 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.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (pyproject.toml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is dependency-injector, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c pip install minos-discovery==0.0.8" did not complete successfully: exit code: 1; runtime evidence skipped.
- 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.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — 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. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
- 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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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 REDACTED, 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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AiopgTransactionDatabaseOperationFactory.build_query at 20.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with AiopgTransactionDatabaseOperationFactory.build_query (cyclomatic 20), AvroDataDecoder._build_single (cyclomatic 19), TypeHintComparator._compare (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
5 method(s) exceeded the cognitive complexity threshold of 15; the worst was AvroDataDecoder._build_single at 29.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with AvroDataDecoder._build_single (cognitive 29), AvroSchemaEncoder._build_single (cognitive 29), TypeHintComparator._compare (cognitive 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with testcases.py (2), abc.py. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
14 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with repository.py, common.py. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with testcases.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (21–22 lines × 2) finding(s) in Code Duplication — start with abc.py. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
10 production modules (Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
1 of 115 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with abc.py. — One of this dimension's main actionable groups (1 warning-level).
D9 · Test Distribution
2175 test methods: 2173 unit, 2 integration, 0 BDD, 0 e2e. The Python suite contributes 2175 test function(s) across 226 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.
D12 · Dependency Hygiene
12 outdated, 0 yanked pinned Python distributions. 12 of 54 shipped distributions were graded against pypi.org (0 not published there, 42 declared without an exact pin, which installs the newest release the declaration admits and so cannot be behind one). Only EXACT pins are graded for currency: a floor or a range already installs the newest release it admits, so reporting one would report this repository for being current. Whether a deliberate upper cap has itself gone stale is a different and weaker question, and is not asked. Whether any distribution is UNMAINTAINED is not graded — PyPI publishes no maintenance status, and release age does not stand in for one. Lockfiles are not read (REDACTED, uv.lock, Pipfile.lock, pdm.lock), so a lock-resolved install is outside this verdict. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D14 · License Compliance
0 of 88 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 54 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (34 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. 3 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/transactions.py (10×20=200); packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/events.py (10×18=180)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with transactions.py, events.py. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
20 deducted task-comment markers across 24691 LoC (0.1/KLoC) → score 9.9. 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 20 FixmeComment finding(s) in Explicit Debt — start with test_models.py (11), handlers.py (2), conf.py (2). — One of this dimension's main actionable groups (20 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 35 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (7 contexts). Contexts: cart, checkout, currency, notifier, payment, product, shipping.
D26 · Project Cohesion
1 of 25 build units (Python) flagged as possibly oversized/incoherent.
D27 · Navigability
54 % 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)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
119 finding(s): 0 critical, 113 high, 5 medium, 1 low. 70 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 1 file(s) — `docs/_templates/layout.html` (lines 1–2, line 3) — 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 28 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (28 issue-level).
- Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (14 issue-level).
- No action in Static Analysis (SAST) — all 70 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 (70 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
30 finding(s): 7 critical, 13 high, 10 medium, 0 low.
What to do
- Resolve the 13 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12), REDACTED. — One of this dimension's main actionable groups (13 issue-level).
- Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
56 finding(s): 0 critical, 21 high, 29 medium, 6 low.
What to do
- Resolve the 29 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (28), REDACTED. — One of this dimension's main actionable groups (29 warning-level).
- Resolve the 21 High IaC finding(s) in IaC & Container Security — start with REDACTED (16), REDACTED (5). — One of this dimension's main actionable groups (21 issue-level).
- Resolve the 6 Low IaC finding(s) in IaC & Container Security — start with REDACTED (6). — One of this dimension's main actionable groups (6 recommendation-level).
D34 · Knowledge Freshness
117 of 117 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/core/minos-microservice-aggregate/minos/aggregate/testing/snapshots/repositories/testcases.py. Counted over 117 of the 423 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 116 Orphaned file finding(s) in Knowledge Freshness — start with abc.py (12), impl.py (7), REDACTED (5). — One of this dimension's main actionable groups (116 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with testcases.py. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: events.py↔transactions.py 70%; publisher.py↔subscriber.py 64%; impl.py↔impl.py 60%
What to do
- Resolve the 5 Change coupling finding(s) in Change Coupling — start with publisher.py (2), events.py, impl.py. — One of this dimension's main actionable groups (5 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 28 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (28 warning-level).
- 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. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 54 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
DM1 · Aggregate boundaries
- `Bar` references the aggregate root `Foo` directly (via `first`) — hold its `FooId` instead.
- `Bar` references the aggregate root `Foo` directly (via `second`) — hold its `FooId` instead.
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `EventEntry` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-aggregate/minos/aggregate/events/entries.py:43
- `FieldDiff` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-aggregate/minos/aggregate/events/fields.py:44
- `IncrementalFieldDiff` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-aggregate/minos/aggregate/events/fields.py:66
- `DataTransferObject` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/minos/common/model/dynamic/dto.py:13
- `Foo` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:19
- `Bar` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:25
- `FooBar` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:32
- `Base` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:38
- `User` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:51
- `ShoppingList` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:76
- `Analytics` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:99
- `Customer` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:105
- `CustomerDict` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:127
- `CustomerFailList` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:137
- `CustomerFailDict` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:145
- `GenericUser` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:156
- `ReservedWordUser` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:162
- `Auth` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:168
- `Owner` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:174
- `Car` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:182
- `TextNumber` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-common/tests/model_classes.py:198
- `BrokerMessageV1` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/core/minos-microservice-networks/minos/networks/brokers/messages/models/v1.py:34
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `EventEntry` exposes publicly writable state (uuid, name, version, data, id, action, and 2 more). — packages/core/minos-microservice-aggregate/minos/aggregate/events/entries.py:43
- `FieldDiff` exposes publicly writable state (name, value). — packages/core/minos-microservice-aggregate/minos/aggregate/events/fields.py:44
- `IncrementalFieldDiff` exposes publicly writable state (action). — packages/core/minos-microservice-aggregate/minos/aggregate/events/fields.py:66
- `Foo` exposes publicly writable state (text). — packages/core/minos-microservice-common/tests/model_classes.py:19
- `Bar` exposes publicly writable state (first, second). — packages/core/minos-microservice-common/tests/model_classes.py:25
- `FooBar` exposes publicly writable state (identifier). — packages/core/minos-microservice-common/tests/model_classes.py:32
- `Base` exposes publicly writable state (id). — packages/core/minos-microservice-common/tests/model_classes.py:38
- `User` exposes publicly writable state (username). — packages/core/minos-microservice-common/tests/model_classes.py:51
- `ShoppingList` exposes publicly writable state (user, cost). — packages/core/minos-microservice-common/tests/model_classes.py:76
- `Analytics` exposes publicly writable state (orders). — packages/core/minos-microservice-common/tests/model_classes.py:99
- `Customer` exposes publicly writable state (name, surname, is_admin, lists). — packages/core/minos-microservice-common/tests/model_classes.py:105
- `CustomerDict` exposes publicly writable state (name, surname, friends). — packages/core/minos-microservice-common/tests/model_classes.py:127
- `CustomerFailList` exposes publicly writable state (friends). — packages/core/minos-microservice-common/tests/model_classes.py:137
- `CustomerFailDict` exposes publicly writable state (friends). — packages/core/minos-microservice-common/tests/model_classes.py:145
- `GenericUser` exposes publicly writable state (username). — packages/core/minos-microservice-common/tests/model_classes.py:156
- `ReservedWordUser` exposes publicly writable state (items). — packages/core/minos-microservice-common/tests/model_classes.py:162
- `Auth` exposes publicly writable state (user). — packages/core/minos-microservice-common/tests/model_classes.py:168
- `Owner` exposes publicly writable state (name, surname, age). — packages/core/minos-microservice-common/tests/model_classes.py:174
- `Car` exposes publicly writable state (doors, color, owner). — packages/core/minos-microservice-common/tests/model_classes.py:182
- `TextNumber` exposes publicly writable state (text, number). — packages/core/minos-microservice-common/tests/model_classes.py:198
- `BrokerMessageV1` exposes publicly writable state (topic, identifier, reply_topic, strategy, payload). — packages/core/minos-microservice-networks/minos/networks/brokers/messages/models/v1.py:34
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (opentelemetry-sdk) so requests are traceable across the system, not just health-probable.
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 28 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:8
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `httpx.AsyncClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×14) — REDACTED:59, REDACTED:72, REDACTED:104, …
What to do
- Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
P8 · Schema migrations
- SQLAlchemy create_all() builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Alembic (`alembic revision --autogenerate` + `alembic upgrade head`), so every schema change is a versioned file applied the same way in every environment. (×8) — tutorials/stock-wallet/microservices/wallet/src/queries/repository.py:28, tutorials/stock-wallet/microservices/stocks/src/queries/repository.py:24, tutorials/stock-wallet/microservices/crypto/src/queries/repository.py:24, …
What to do
- Replace SQLAlchemy create_all() with Alembic (`alembic revision --autogenerate` + `alembic upgrade head`) so the production schema can evolve safely and reproducibly.
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
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — packages/plugins/minos-discovery-kong/minos/plugins/kong/discovery.py:72, packages/core/minos-microservice-networks/minos/networks/brokers/messages/models/v1.py:186, packages/core/minos-microservice-networks/minos/networks/brokers/collections/queues/database/impl.py:242
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `error` at line 91 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/plugins/minos-router-graphql/minos/plugins/graphql/handlers.py:91
- `exception` at line 93 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — packages/plugins/minos-router-graphql/minos/plugins/graphql/handlers.py:93
- `debug` at line 68 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/plugins/minos-discovery-minos/minos/plugins/minos_discovery/client.py:68
- `debug` at line 89 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/plugins/minos-discovery-minos/minos/plugins/minos_discovery/client.py:89
- `debug` at line 112 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/plugins/minos-database-aiopg/minos/plugins/aiopg/clients.py:112
- `debug` at line 136 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/plugins/minos-database-aiopg/minos/plugins/aiopg/clients.py:136
- `info` at line 138 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/plugins/minos-broker-kafka/minos/plugins/kafka/subscriber.py:138
- `info` at line 154 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. (×2) — packages/plugins/minos-broker-kafka/minos/plugins/kafka/subscriber.py:154, packages/core/minos-microservice-networks/minos/networks/http/connectors.py:154
- `exception` at line 193 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-saga/minos/saga/manager.py:193
- `info` at line 185 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-saga/minos/saga/executions/saga.py:185
- `warning` at line 242 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-saga/minos/saga/executions/saga.py:242
- `warning` at line 272 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-saga/minos/saga/executions/saga.py:272
- `warning` at line 289 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-saga/minos/saga/executions/saga.py:289
- `error` at line 198 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/scheduling/schedulers.py:198
- `exception` at line 201 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/scheduling/schedulers.py:201
- `info` at line 99 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/http/connectors.py:99
- `info` at line 108 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/http/connectors.py:108
- `error` at line 169 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/http/connectors.py:169
- `exception` at line 173 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/http/connectors.py:173
- `info` at line 155 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/clients.py:155
- `debug` at line 79 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/subscribers/abc.py:79
- `debug` at line 50 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/publishers/abc.py:50
- `warning` at line 200 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/messages/models/v1.py:200
- `warning` at line 146 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/handlers/impl.py:146
- `info` at line 141 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/dispatchers/impl.py:141
- `error` at line 157 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/dispatchers/impl.py:157
- `exception` at line 161 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/dispatchers/impl.py:161
- `debug` at line 185 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/dispatchers/impl.py:185
- `debug` at line 30 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/collections/queues/abc.py:30
- `debug` at line 48 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/collections/queues/abc.py:48
- `warning` at line 42 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/collections/queues/memory.py:42
- `warning` at line 166 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-networks/minos/networks/brokers/collections/queues/database/impl.py:166
- `exception` at line 36 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-cqrs/minos/cqrs/handlers.py:36
- `debug` at line 87 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-common/minos/common/pools.py:87
- `debug` at line 144 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-common/minos/common/pools.py:144
- `debug` at line 151 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-common/minos/common/pools.py:151
- `exception` at line 25 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-common/minos/common/ports.py:25
- `exception` at line 41 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.exception("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.exception("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-common/minos/common/ports.py:41
- `warning` at line 74 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — packages/core/minos-microservice-common/minos/common/retries.py:74
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 65% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 41% | Weak — gated by D12, D13, P3, P7, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 38% | Weak — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 59% | Adequate — gated by DM4, DM5 | 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 — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 62 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c pip install minos-discovery==0.0.8" did not complete successfully: exit code: 1; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — 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 — ~22130 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
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- 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 35 current-state document(s) make no claim of a kind M4 checks. 9 claim(s) of kinds M4 does not check were not checked (path 9); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- 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.
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 160 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Aggregate holds a reference to another aggregate: Bar.first
- Aggregate holds a reference to another aggregate: Bar.second
- REDACTED
- REDACTED
- REDACTED
Serious — 197 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Anemic entity: EventEntry packages/core/minos-microservice-aggregate/minos/aggregate/events/entries.py:43
- Anemic entity: FieldDiff packages/core/minos-microservice-aggregate/minos/aggregate/events/fields.py:44
- Anemic entity: IncrementalFieldDiff packages/core/minos-microservice-aggregate/minos/aggregate/events/fields.py:66
- Anemic entity: DataTransferObject packages/core/minos-microservice-common/minos/common/model/dynamic/dto.py:13
- Anemic entity: Foo packages/core/minos-microservice-common/tests/model_classes.py:19
- Anemic entity: Bar packages/core/minos-microservice-common/tests/model_classes.py:25
- Anemic entity: FooBar packages/core/minos-microservice-common/tests/model_classes.py:32
- Anemic entity: Base packages/core/minos-microservice-common/tests/model_classes.py:38
- Anemic entity: User packages/core/minos-microservice-common/tests/model_classes.py:51
- Anemic entity: ShoppingList packages/core/minos-microservice-common/tests/model_classes.py:76
- Anemic entity: Analytics packages/core/minos-microservice-common/tests/model_classes.py:99
- Anemic entity: Customer packages/core/minos-microservice-common/tests/model_classes.py:105
- Anemic entity: CustomerDict packages/core/minos-microservice-common/tests/model_classes.py:127
- Anemic entity: CustomerFailList packages/core/minos-microservice-common/tests/model_classes.py:137
- Anemic entity: CustomerFailDict packages/core/minos-microservice-common/tests/model_classes.py:145
- Anemic entity: GenericUser packages/core/minos-microservice-common/tests/model_classes.py:156
- Anemic entity: ReservedWordUser packages/core/minos-microservice-common/tests/model_classes.py:162
- Anemic entity: Auth packages/core/minos-microservice-common/tests/model_classes.py:168
- Anemic entity: Owner packages/core/minos-microservice-common/tests/model_classes.py:174
- Anemic entity: Car packages/core/minos-microservice-common/tests/model_classes.py:182
- Anemic entity: TextNumber packages/core/minos-microservice-common/tests/model_classes.py:198
- Anemic entity: BrokerMessageV1 packages/core/minos-microservice-networks/minos/networks/brokers/messages/models/v1.py:34
- Mutable entity: EventEntry packages/core/minos-microservice-aggregate/minos/aggregate/events/entries.py:43
- Mutable entity: FieldDiff packages/core/minos-microservice-aggregate/minos/aggregate/events/fields.py:44
- Mutable entity: IncrementalFieldDiff packages/core/minos-microservice-aggregate/minos/aggregate/events/fields.py:66
- Mutable entity: Foo packages/core/minos-microservice-common/tests/model_classes.py:19
- Mutable entity: Bar packages/core/minos-microservice-common/tests/model_classes.py:25
- Mutable entity: FooBar packages/core/minos-microservice-common/tests/model_classes.py:32
- Mutable entity: Base packages/core/minos-microservice-common/tests/model_classes.py:38
- Mutable entity: User packages/core/minos-microservice-common/tests/model_classes.py:51
- Mutable entity: ShoppingList packages/core/minos-microservice-common/tests/model_classes.py:76
- Mutable entity: Analytics packages/core/minos-microservice-common/tests/model_classes.py:99
- Mutable entity: Customer packages/core/minos-microservice-common/tests/model_classes.py:105
- Mutable entity: CustomerDict packages/core/minos-microservice-common/tests/model_classes.py:127
- Mutable entity: CustomerFailList packages/core/minos-microservice-common/tests/model_classes.py:137
- Mutable entity: CustomerFailDict packages/core/minos-microservice-common/tests/model_classes.py:145
- Mutable entity: GenericUser packages/core/minos-microservice-common/tests/model_classes.py:156
- Mutable entity: ReservedWordUser packages/core/minos-microservice-common/tests/model_classes.py:162
- Mutable entity: Auth packages/core/minos-microservice-common/tests/model_classes.py:168
- Mutable entity: Owner packages/core/minos-microservice-common/tests/model_classes.py:174
- Mutable entity: Car packages/core/minos-microservice-common/tests/model_classes.py:182
- Mutable entity: TextNumber packages/core/minos-microservice-common/tests/model_classes.py:198
- Mutable entity: BrokerMessageV1 packages/core/minos-microservice-networks/minos/networks/brokers/messages/models/v1.py:34
- FixmeComment packages/core/minos-microservice-saga/tests/test_saga/test_executions/test_saga/test_execute.py:143
- FixmeComment packages/core/minos-microservice-saga/minos/saga/executions/saga.py:271
- FixmeComment packages/core/minos-microservice-networks/minos/networks/decorators/callables/handlers.py:117
- FixmeComment packages/core/minos-microservice-networks/minos/networks/decorators/callables/handlers.py:142
- FixmeComment packages/core/minos-microservice-networks/minos/networks/brokers/messages/models/v1.py:40
- FixmeComment packages/core/minos-microservice-common/minos/common/model/serializers/avro/schema/decoder.py:160
- FixmeComment packages/core/minos-microservice-common/minos/common/model/serializers/avro/schema/encoder.py:109
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:236
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:257
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:279
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:303
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:315
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:337
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:343
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:349
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:356
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:362
- FixmeComment packages/core/minos-microservice-aggregate/tests/test_aggregate/test_entities/test_refs/test_models.py:369
- FixmeComment docs/conf.py:10
- FixmeComment docs/conf.py:11
- Outbound HTTP without resilience REDACTED:59
- Outbound HTTP without resilience REDACTED:72
- Outbound HTTP without resilience REDACTED:104
- Outbound HTTP without resilience REDACTED:112
- Outbound HTTP without resilience REDACTED:122
- Outbound HTTP without resilience REDACTED:128
- Outbound HTTP without resilience REDACTED:141
- Outbound HTTP without resilience REDACTED:148
- Outbound HTTP without resilience REDACTED:155
- Outbound HTTP without resilience REDACTED:162
- Outbound HTTP without resilience REDACTED:169
- Outbound HTTP without resilience REDACTED:179
- Outbound HTTP without resilience REDACTED:203
- Outbound HTTP without resilience REDACTED:208
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Schema created by SQLAlchemy create_all() (no migration path) tutorials/stock-wallet/microservices/wallet/src/queries/repository.py:28
- Schema created by SQLAlchemy create_all() (no migration path) tutorials/stock-wallet/microservices/stocks/src/queries/repository.py:24
- Schema created by SQLAlchemy create_all() (no migration path) tutorials/stock-wallet/microservices/crypto/src/queries/repository.py:24
- Schema created by SQLAlchemy create_all() (no migration path) tutorials/eboutique/microservices/product/src/queries/repository.py:33
- Schema created by SQLAlchemy create_all() (no migration path) tutorials/eboutique/microservices/payment/src/queries/repository.py:24
- Schema created by SQLAlchemy create_all() (no migration path) tutorials/eboutique/microservices/notifier/src/queries/repository.py:24
- Schema created by SQLAlchemy create_all() (no migration path) tutorials/eboutique/microservices/checkout/src/queries/repository.py:24
- Schema created by SQLAlchemy create_all() (no migration path) tutorials/eboutique/microservices/cart/src/queries/repository.py:33
- Change coupling: events.py ↔ transactions.py packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/events.py:1
- Change coupling: publisher.py ↔ subscriber.py packages/plugins/minos-broker-rabbitmq/minos/plugins/rabbitmq/publisher.py:1
- Change coupling: impl.py ↔ impl.py packages/core/minos-microservice-aggregate/minos/aggregate/events/repositories/database/impl.py:1
- Change coupling: publisher.py ↔ subscriber.py packages/plugins/minos-broker-kafka/minos/plugins/kafka/publisher.py:1
- Change coupling: factories.py ↔ transactions.py packages/core/minos-microservice-aggregate/minos/aggregate/events/repositories/database/factories.py:1
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: EventRepositoryTestCase packages/core/minos-microservice-aggregate/minos/aggregate/testing/events/repositories/testcases.py:36
- TooManyMethods: TransactionRepositoryTestCase packages/core/minos-microservice-aggregate/minos/aggregate/testing/transactions/repositories/testcases.py:20
- TooManyMethods: Config packages/core/minos-microservice-common/minos/common/config/abc.py:51
- Swallowed exception (caught, then discarded) packages/plugins/minos-discovery-kong/minos/plugins/kong/discovery.py:72
- Swallowed exception (caught, then discarded) packages/core/minos-microservice-networks/minos/networks/brokers/messages/models/v1.py:186
- Swallowed exception (caught, then discarded) packages/core/minos-microservice-networks/minos/networks/brokers/collections/queues/database/impl.py:242
- Hotspot: packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/transactions.py packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/transactions.py:139
- Hotspot: packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/events.py packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/events.py:194
- Duplicated block (14 lines × 2) tutorials/eboutique/microservices/checkout/src/queries/repository.py:19
- Duplicated block (14 lines × 2) packages/plugins/minos-broker-kafka/minos/plugins/kafka/common.py:31
- AiopgTransactionDatabaseOperationFactory.build_query (cyclomatic 20) packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/transactions.py:139
- AvroDataDecoder._build_single (cyclomatic 19) packages/core/minos-microservice-common/minos/common/model/serializers/avro/data/decoder.py:101
- TypeHintComparator._compare (cyclomatic 19) packages/core/minos-microservice-common/minos/common/model/types/comparators.py:73
- AvroSchemaEncoder._build_single (cyclomatic 18) packages/core/minos-microservice-common/minos/common/model/serializers/avro/schema/encoder.py:107
- AiopgEventDatabaseOperationFactory.build_query (cyclomatic 18) packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/events.py:194
- AvroDataDecoder._build_single (cognitive 29) packages/core/minos-microservice-common/minos/common/model/serializers/avro/data/decoder.py:101
- AvroSchemaEncoder._build_single (cognitive 29) packages/core/minos-microservice-common/minos/common/model/serializers/avro/schema/encoder.py:107
- TypeHintComparator._compare (cognitive 20) packages/core/minos-microservice-common/minos/common/model/types/comparators.py:73
- AiopgTransactionDatabaseOperationFactory.build_query (cognitive 19) packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/transactions.py:139
- AiopgEventDatabaseOperationFactory.build_query (cognitive 17) packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/events.py:194
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) packages/core/minos-microservice-aggregate/minos/aggregate/testing/transactions/repositories/testcases.py:77
- Duplicated block (21–22 lines × 2) packages/core/minos-microservice-aggregate/minos/aggregate/events/repositories/abc.py:280
- Duplicated block (15 lines × 2) packages/plugins/minos-broker-rabbitmq/minos/plugins/rabbitmq/publisher.py:42
- Duplicated block (13 lines × 2) packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/events.py:241
- Duplicated block (26 lines × 2) packages/core/minos-microservice-aggregate/minos/aggregate/testing/snapshots/repositories/factories.py:36
- Duplicated block (13 lines × 10) tutorials/eboutique/microservices/cart/src/cli.py:29
- Duplicated block (36 lines × 5) tutorials/eboutique/microservices/checkout/src/queries/services.py:20
- Duplicated block (10 lines × 3) tutorials/eboutique/microservices/payment/src/queries/repository.py:19
- Duplicated block (5 lines × 2) packages/core/minos-microservice-aggregate/minos/aggregate/actions.py:19
- Duplicated block (9 lines × 2) packages/core/minos-microservice-aggregate/minos/aggregate/collections.py:126
- Duplicated block (8 lines × 6) packages/core/minos-microservice-common/minos/common/config/v1.py:231
- Duplicated block (5 lines × 3) packages/core/minos-microservice-networks/minos/networks/brokers/publishers/queued/impl.py:60
- Duplicated block (5 lines × 4) packages/core/minos-microservice-aggregate/minos/aggregate/testing/transactions/repositories/testcases.py:78
- Low cohesion: Model (LCOM4 4) packages/core/minos-microservice-common/minos/common/model/abc.py:62
Minor — 183 finding(s)
- Orphaned file packages/core/minos-microservice-aggregate/minos/aggregate/testing/events/repositories/testcases.py:1
- Orphaned file packages/core/minos-microservice-aggregate/minos/aggregate/testing/transactions/repositories/testcases.py:1
- Orphaned file packages/core/minos-microservice-aggregate/minos/aggregate/entities/models.py:1
- Orphaned file packages/core/minos-microservice-common/minos/common/model/abc.py:1
- Orphaned file packages/core/minos-microservice-saga/minos/saga/executions/saga.py:1
- Orphaned file packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/events.py:1
- Orphaned file packages/core/minos-microservice-aggregate/minos/aggregate/transactions/entries.py:1
- Orphaned file packages/core/minos-microservice-common/minos/common/config/v1.py:1
- Orphaned file packages/core/minos-microservice-aggregate/minos/aggregate/events/repositories/abc.py:1
- Orphaned file packages/core/minos-microservice-common/minos/common/model/serializers/avro/data/decoder.py:1
- Orphaned file packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/transactions.py:1
- Orphaned file packages/core/minos-microservice-common/minos/common/config/abc.py:1
- Orphaned file packages/core/minos-microservice-aggregate/minos/aggregate/snapshots/repositories/abc.py:1
- Orphaned file packages/plugins/minos-http-aiohttp/minos/plugins/aiohttp/requests.py:1
- Orphaned file packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/snapshots/queries.py:1
- Orphaned file packages/core/minos-microservice-saga/minos/saga/manager.py:1
- Orphaned file packages/plugins/minos-database-aiopg/minos/plugins/aiopg/factories/aggregate/snapshots/impl.py:1
- Orphaned file packages/core/minos-microservice-aggregate/minos/aggregate/snapshots/repositories/database/impl.py:1
- Orphaned file packages/core/minos-microservice-aggregate/minos/aggregate/events/fields.py:1
- Orphaned file REDACTED:1
- Orphaned file packages/core/minos-microservice-networks/minos/networks/brokers/collections/queues/database/impl.py:1
- Orphaned file packages/core/minos-microservice-common/minos/common/model/types/model_types.py:1
- Orphaned file packages/core/minos-microservice-networks/minos/networks/brokers/subscribers/abc.py:1
- Orphaned file packages/core/minos-microservice-common/minos/common/config/v2.py:1
- Orphaned file packages/plugins/minos-database-aiopg/minos/plugins/aiopg/clients.py:1
- Interpolated log message defeats structured logging packages/plugins/minos-router-graphql/minos/plugins/graphql/handlers.py:91
- Interpolated log message defeats structured logging packages/plugins/minos-router-graphql/minos/plugins/graphql/handlers.py:93
- Interpolated log message defeats structured logging packages/plugins/minos-discovery-minos/minos/plugins/minos_discovery/client.py:68
- Interpolated log message defeats structured logging packages/plugins/minos-discovery-minos/minos/plugins/minos_discovery/client.py:89
- Interpolated log message defeats structured logging packages/plugins/minos-database-aiopg/minos/plugins/aiopg/clients.py:112
- Interpolated log message defeats structured logging packages/plugins/minos-database-aiopg/minos/plugins/aiopg/clients.py:136
- Interpolated log message defeats structured logging packages/plugins/minos-broker-kafka/minos/plugins/kafka/subscriber.py:138
- Interpolated log message defeats structured logging packages/plugins/minos-broker-kafka/minos/plugins/kafka/subscriber.py:154
- Interpolated log message defeats structured logging packages/core/minos-microservice-saga/minos/saga/manager.py:193
- Interpolated log message defeats structured logging packages/core/minos-microservice-saga/minos/saga/executions/saga.py:185
- Interpolated log message defeats structured logging packages/core/minos-microservice-saga/minos/saga/executions/saga.py:242
- Interpolated log message defeats structured logging packages/core/minos-microservice-saga/minos/saga/executions/saga.py:272
- Interpolated log message defeats structured logging packages/core/minos-microservice-saga/minos/saga/executions/saga.py:289
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/scheduling/schedulers.py:198
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/scheduling/schedulers.py:201
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/http/connectors.py:99
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/http/connectors.py:108
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/http/connectors.py:154
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/http/connectors.py:169
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/http/connectors.py:173
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/brokers/clients.py:155
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/brokers/subscribers/abc.py:79
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/brokers/publishers/abc.py:50
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/brokers/messages/models/v1.py:200
- Interpolated log message defeats structured logging packages/core/minos-microservice-networks/minos/networks/brokers/handlers/impl.py:146
- Duplicated predicate packages/core/minos-microservice-aggregate/minos/aggregate/entities/refs/resolvers.py:57
- Duplicated predicate packages/core/minos-microservice-aggregate/minos/aggregate/transactions/entries.py:303
- Duplicated predicate packages/core/minos-microservice-aggregate/minos/aggregate/events/repositories/abc.py:92
- Duplicated predicate packages/core/minos-microservice-common/minos/common/model/declarative.py:62
- Duplicated predicate packages/core/minos-microservice-saga/minos/saga/definitions/steps/local.py:46
- Duplicated predicate packages/core/minos-microservice-saga/minos/saga/definitions/steps/local.py:48
- Duplicated predicate packages/core/minos-microservice-networks/minos/networks/brokers/dispatchers/requests.py:37
- Duplicated predicate packages/core/minos-microservice-aggregate/minos/aggregate/events/entries.py:167
- Duplicated predicate packages/core/minos-microservice-common/minos/common/model/declarative.py:65
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- Dormant codebase
- Most significant orphaned file packages/core/minos-microservice-aggregate/minos/aggregate/testing/snapshots/repositories/testcases.py:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:8
- Dependabot does not watch github-actions REDACTED:2
Minor — 12 finding(s)
- Outdated: aiosignal
- Outdated: async-timeout
- Outdated: attrs
- Outdated: charset-normalizer
- Outdated: click
- Outdated: colorama
- Outdated: colorlog
- Outdated: frozenlist
- Outdated: idna
- Outdated: multidict
- Outdated: six
- Outdated: yarl
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-3d85bb3f78d9421fb4bc41c162c86693/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-3d85bb3f78d9421fb4bc41c162c86693/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 . | 119 | 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 . | 30 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 56 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 |