Executive summary
javierparadadev/python-ddd-skeleton is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because two files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 55 out of 100, which the At risk rating leaves unchanged.
Maturity, at 37, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 17 points. Having someone learn and document the two files no active contributor knows comes next, worth about 14 points. Raising Maturity to 70 would lift the score to about 69.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three known security holes in the packages the code depends on can be used by attackers, and one secret can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting the secret to its own step would close these risks.
The product code is 663 lines, too few for a meaningful rebuild estimate.
If Maturity rose from 37 to 70, the lowest score rated Strong, the score would rise from 55 to about 69.
New since the last survey: 1 finding
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 2 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing · Unpinned build actions
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Infrastructure.environment.EnvVar | 2 Infrastructure.persistence.mongo.PyMongoConfiguration | 3 domain.BaseObject | 4 domain.DomainError | 5 domain.Interface | 6 domain.Metadata | 7 domain.Response | 8 domain.criteria.FilterField | 9 domain.criteria.FilterOperator | 10 domain.criteria.FilterValue | 11 domain.criteria.LimitOffset | 12 domain.criteria.OrderAttribute | 13 domain.criteria.OrderDirection | 14 domain.event_sourcing.DomainEvent | 15 Infrastructure.environment.EnvManager | 16 Infrastructure.persistence.minio.MinioClientFactory | 17 Infrastructure.persistence.mongo.PyMongoClientFactory | 18 domain.UncontrolledError | 19 domain.cqrs.command.Command | 20 domain.cqrs.command.CommandNoRegisteredError | 21 domain.cqrs.query.Query | 22 domain.cqrs.query.QueryNoRegisteredError | 23 domain.criteria.CriteriaQueryMetadata | 24 domain.criteria.Filter | 25 domain.criteria.Limit | 26 domain.criteria.OrderBy | 27 domain.event_sourcing.EventBus | 28 domain.event_sourcing.EventSubscriber | 29 domain.logger.Logger | 30 Infrastructure.eventbus.InMemoryEventBus | 31 Infrastructure.logger.NativeConsoleLogger | 32 domain.cqrs.command.CommandBus | 33 domain.cqrs.command.CommandHandler | 34 domain.cqrs.query.QueryBus | 35 domain.cqrs.query.QueryHandler | 36 domain.criteria.Criteria | 37 Infrastructure.cqrs.InMemoryCommandBus | 38 Infrastructure.cqrs.InMemoryQueryBus | 39 Infrastructure.persistence.mongo | 40 Infrastructure.persistence.mongo.PyMongoRepository |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Infrastructure.environment.EnvVar | ||||||||||||||||||||||||||||||||||||||||
| 2 Infrastructure.persistence.mongo.PyMongoConfiguration | ||||||||||||||||||||||||||||||||||||||||
| 3 domain.BaseObject | ||||||||||||||||||||||||||||||||||||||||
| 4 domain.DomainError | ||||||||||||||||||||||||||||||||||||||||
| 5 domain.Interface | ||||||||||||||||||||||||||||||||||||||||
| 6 domain.Metadata | ||||||||||||||||||||||||||||||||||||||||
| 7 domain.Response | ||||||||||||||||||||||||||||||||||||||||
| 8 domain.criteria.FilterField | ||||||||||||||||||||||||||||||||||||||||
| 9 domain.criteria.FilterOperator | ||||||||||||||||||||||||||||||||||||||||
| 10 domain.criteria.FilterValue | ||||||||||||||||||||||||||||||||||||||||
| 11 domain.criteria.LimitOffset | ||||||||||||||||||||||||||||||||||||||||
| 12 domain.criteria.OrderAttribute | ||||||||||||||||||||||||||||||||||||||||
| 13 domain.criteria.OrderDirection | ||||||||||||||||||||||||||||||||||||||||
| 14 domain.event_sourcing.DomainEvent | ||||||||||||||||||||||||||||||||||||||||
| 15 Infrastructure.environment.EnvManager | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Infrastructure.persistence.minio.MinioClientFactory | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Infrastructure.persistence.mongo.PyMongoClientFactory | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 domain.UncontrolledError | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 domain.cqrs.command.Command | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 domain.cqrs.command.CommandNoRegisteredError | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 domain.cqrs.query.Query | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 domain.cqrs.query.QueryNoRegisteredError | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 domain.criteria.CriteriaQueryMetadata | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 domain.criteria.Filter | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 domain.criteria.Limit | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 domain.criteria.OrderBy | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 domain.event_sourcing.EventBus | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 domain.event_sourcing.EventSubscriber | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 domain.logger.Logger | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 Infrastructure.eventbus.InMemoryEventBus | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 Infrastructure.logger.NativeConsoleLogger | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 domain.cqrs.command.CommandBus | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 domain.cqrs.command.CommandHandler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 domain.cqrs.query.QueryBus | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 domain.cqrs.query.QueryHandler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 domain.criteria.Criteria | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Infrastructure.cqrs.InMemoryCommandBus | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 Infrastructure.cqrs.InMemoryQueryBus | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 Infrastructure.persistence.mongo | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 Infrastructure.persistence.mongo.PyMongoRepository | 1 |
15→1 Infrastructure.environment.EnvManager uses Infrastructure.environment.EnvVar✕
- Connections
- 1 pair of types, where a type in Infrastructure.environment.EnvManager uses a type in Infrastructure.environment.EnvVar.
- The types involved
src.contexts.shared.Infrastructure.environment.EnvManager.EnvManager→src.contexts.shared.Infrastructure.environment.EnvVar.EnvVar
- Direction
- Infrastructure.environment.EnvManager uses Infrastructure.environment.EnvVar, so a change to Infrastructure.environment.EnvVar can break Infrastructure.environment.EnvManager, while a change to Infrastructure.environment.EnvManager can't break Infrastructure.environment.EnvVar.
- Position
- Below the diagonal: Infrastructure.environment.EnvManager uses a module listed above it, which is the healthy direction.
16→2 Infrastructure.persistence.minio.MinioClientFactory uses Infrastructure.persistence.mongo.PyMongoConfiguration✕
- Connections
- 1 pair of types, where a type in Infrastructure.persistence.minio.MinioClientFactory uses a type in Infrastructure.persistence.mongo.PyMongoConfiguration.
- The types involved
src.contexts.shared.Infrastructure.persistence.minio.MinioClientFactory.MinioClientFactory→src.contexts.shared.Infrastructure.persistence.mongo.PyMongoConfiguration.PyMongoConfiguration
- Direction
- Infrastructure.persistence.minio.MinioClientFactory uses Infrastructure.persistence.mongo.PyMongoConfiguration, so a change to Infrastructure.persistence.mongo.PyMongoConfiguration can break Infrastructure.persistence.minio.MinioClientFactory, while a change to Infrastructure.persistence.minio.MinioClientFactory can't break Infrastructure.persistence.mongo.PyMongoConfiguration.
- Position
- Below the diagonal: Infrastructure.persistence.minio.MinioClientFactory uses a module listed above it, which is the healthy direction.
17→2 Infrastructure.persistence.mongo.PyMongoClientFactory uses Infrastructure.persistence.mongo.PyMongoConfiguration✕
- Connections
- 1 pair of types, where a type in Infrastructure.persistence.mongo.PyMongoClientFactory uses a type in Infrastructure.persistence.mongo.PyMongoConfiguration.
- The types involved
src.contexts.shared.Infrastructure.persistence.mongo.PyMongoClientFactory.PyMongoClientFactory→src.contexts.shared.Infrastructure.persistence.mongo.PyMongoConfiguration.PyMongoConfiguration
- Direction
- Infrastructure.persistence.mongo.PyMongoClientFactory uses Infrastructure.persistence.mongo.PyMongoConfiguration, so a change to Infrastructure.persistence.mongo.PyMongoConfiguration can break Infrastructure.persistence.mongo.PyMongoClientFactory, while a change to Infrastructure.persistence.mongo.PyMongoClientFactory can't break Infrastructure.persistence.mongo.PyMongoConfiguration.
- Position
- Below the diagonal: Infrastructure.persistence.mongo.PyMongoClientFactory uses a module listed above it, which is the healthy direction.
18→4 domain.UncontrolledError uses domain.DomainError✕
- Connections
- 1 pair of types, where a type in domain.UncontrolledError uses a type in domain.DomainError.
- The types involved
src.contexts.shared.domain.UncontrolledError.UncontrolledError→src.contexts.shared.domain.DomainError.DomainError
- Direction
- domain.UncontrolledError uses domain.DomainError, so a change to domain.DomainError can break domain.UncontrolledError, while a change to domain.UncontrolledError can't break domain.DomainError.
- Position
- Below the diagonal: domain.UncontrolledError uses a module listed above it, which is the healthy direction.
19→5 domain.cqrs.command.Command uses domain.Interface✕
- Connections
- 1 pair of types, where a type in domain.cqrs.command.Command uses a type in domain.Interface.
- The types involved
src.contexts.shared.domain.cqrs.command.Command.Command→src.contexts.shared.domain.Interface.Interface
- Direction
- domain.cqrs.command.Command uses domain.Interface, so a change to domain.Interface can break domain.cqrs.command.Command, while a change to domain.cqrs.command.Command can't break domain.Interface.
- Position
- Below the diagonal: domain.cqrs.command.Command uses a module listed above it, which is the healthy direction.
20→4 domain.cqrs.command.CommandNoRegisteredError uses domain.DomainError✕
- Connections
- 1 pair of types, where a type in domain.cqrs.command.CommandNoRegisteredError uses a type in domain.DomainError.
- The types involved
src.contexts.shared.domain.cqrs.command.CommandNoRegisteredError.CommandNotRegisteredError→src.contexts.shared.domain.DomainError.DomainError
- Direction
- domain.cqrs.command.CommandNoRegisteredError uses domain.DomainError, so a change to domain.DomainError can break domain.cqrs.command.CommandNoRegisteredError, while a change to domain.cqrs.command.CommandNoRegisteredError can't break domain.DomainError.
- Position
- Below the diagonal: domain.cqrs.command.CommandNoRegisteredError uses a module listed above it, which is the healthy direction.
21→5 domain.cqrs.query.Query uses domain.Interface✕
- Connections
- 1 pair of types, where a type in domain.cqrs.query.Query uses a type in domain.Interface.
- The types involved
src.contexts.shared.domain.cqrs.query.Query.Query→src.contexts.shared.domain.Interface.Interface
- Direction
- domain.cqrs.query.Query uses domain.Interface, so a change to domain.Interface can break domain.cqrs.query.Query, while a change to domain.cqrs.query.Query can't break domain.Interface.
- Position
- Below the diagonal: domain.cqrs.query.Query uses a module listed above it, which is the healthy direction.
22→4 domain.cqrs.query.QueryNoRegisteredError uses domain.DomainError✕
- Connections
- 1 pair of types, where a type in domain.cqrs.query.QueryNoRegisteredError uses a type in domain.DomainError.
- The types involved
src.contexts.shared.domain.cqrs.query.QueryNoRegisteredError.QueryNotRegisteredError→src.contexts.shared.domain.DomainError.DomainError
- Direction
- domain.cqrs.query.QueryNoRegisteredError uses domain.DomainError, so a change to domain.DomainError can break domain.cqrs.query.QueryNoRegisteredError, while a change to domain.cqrs.query.QueryNoRegisteredError can't break domain.DomainError.
- Position
- Below the diagonal: domain.cqrs.query.QueryNoRegisteredError uses a module listed above it, which is the healthy direction.
23→6 domain.criteria.CriteriaQueryMetadata uses domain.Metadata✕
- Connections
- 1 pair of types, where a type in domain.criteria.CriteriaQueryMetadata uses a type in domain.Metadata.
- The types involved
src.contexts.shared.domain.criteria.CriteriaQueryMetadata.CriteriaQueryMetadata→src.contexts.shared.domain.Metadata.Metadata
- Direction
- domain.criteria.CriteriaQueryMetadata uses domain.Metadata, so a change to domain.Metadata can break domain.criteria.CriteriaQueryMetadata, while a change to domain.criteria.CriteriaQueryMetadata can't break domain.Metadata.
- Position
- Below the diagonal: domain.criteria.CriteriaQueryMetadata uses a module listed above it, which is the healthy direction.
24→8 domain.criteria.Filter uses domain.criteria.FilterField✕
- Connections
- 1 pair of types, where a type in domain.criteria.Filter uses a type in domain.criteria.FilterField.
- The types involved
src.contexts.shared.domain.criteria.Filter.Filter→src.contexts.shared.domain.criteria.FilterField.FilterField
- Direction
- domain.criteria.Filter uses domain.criteria.FilterField, so a change to domain.criteria.FilterField can break domain.criteria.Filter, while a change to domain.criteria.Filter can't break domain.criteria.FilterField.
- Position
- Below the diagonal: domain.criteria.Filter uses a module listed above it, which is the healthy direction.
24→9 domain.criteria.Filter uses domain.criteria.FilterOperator✕
- Connections
- 1 pair of types, where a type in domain.criteria.Filter uses a type in domain.criteria.FilterOperator.
- The types involved
src.contexts.shared.domain.criteria.Filter.Filter→src.contexts.shared.domain.criteria.FilterOperator.FilterOperator
- Direction
- domain.criteria.Filter uses domain.criteria.FilterOperator, so a change to domain.criteria.FilterOperator can break domain.criteria.Filter, while a change to domain.criteria.Filter can't break domain.criteria.FilterOperator.
- Position
- Below the diagonal: domain.criteria.Filter uses a module listed above it, which is the healthy direction.
24→10 domain.criteria.Filter uses domain.criteria.FilterValue✕
- Connections
- 1 pair of types, where a type in domain.criteria.Filter uses a type in domain.criteria.FilterValue.
- The types involved
src.contexts.shared.domain.criteria.Filter.Filter→src.contexts.shared.domain.criteria.FilterValue.FilterValue
- Direction
- domain.criteria.Filter uses domain.criteria.FilterValue, so a change to domain.criteria.FilterValue can break domain.criteria.Filter, while a change to domain.criteria.Filter can't break domain.criteria.FilterValue.
- Position
- Below the diagonal: domain.criteria.Filter uses a module listed above it, which is the healthy direction.
25→11 domain.criteria.Limit uses domain.criteria.LimitOffset✕
- Connections
- 1 pair of types, where a type in domain.criteria.Limit uses a type in domain.criteria.LimitOffset.
- The types involved
src.contexts.shared.domain.criteria.Limit.Limit→src.contexts.shared.domain.criteria.LimitOffset.LimitOffset
- Direction
- domain.criteria.Limit uses domain.criteria.LimitOffset, so a change to domain.criteria.LimitOffset can break domain.criteria.Limit, while a change to domain.criteria.Limit can't break domain.criteria.LimitOffset.
- Position
- Below the diagonal: domain.criteria.Limit uses a module listed above it, which is the healthy direction.
26→12 domain.criteria.OrderBy uses domain.criteria.OrderAttribute✕
- Connections
- 1 pair of types, where a type in domain.criteria.OrderBy uses a type in domain.criteria.OrderAttribute.
- The types involved
src.contexts.shared.domain.criteria.OrderBy.OrderBy→src.contexts.shared.domain.criteria.OrderAttribute.OrderAttribute
- Direction
- domain.criteria.OrderBy uses domain.criteria.OrderAttribute, so a change to domain.criteria.OrderAttribute can break domain.criteria.OrderBy, while a change to domain.criteria.OrderBy can't break domain.criteria.OrderAttribute.
- Position
- Below the diagonal: domain.criteria.OrderBy uses a module listed above it, which is the healthy direction.
26→13 domain.criteria.OrderBy uses domain.criteria.OrderDirection✕
- Connections
- 1 pair of types, where a type in domain.criteria.OrderBy uses a type in domain.criteria.OrderDirection.
- The types involved
src.contexts.shared.domain.criteria.OrderBy.OrderBy→src.contexts.shared.domain.criteria.OrderDirection.OrderDirection
- Direction
- domain.criteria.OrderBy uses domain.criteria.OrderDirection, so a change to domain.criteria.OrderDirection can break domain.criteria.OrderBy, while a change to domain.criteria.OrderBy can't break domain.criteria.OrderDirection.
- Position
- Below the diagonal: domain.criteria.OrderBy uses a module listed above it, which is the healthy direction.
27→5 domain.event_sourcing.EventBus uses domain.Interface✕
- Connections
- 1 pair of types, where a type in domain.event_sourcing.EventBus uses a type in domain.Interface.
- The types involved
src.contexts.shared.domain.event_sourcing.EventBus.EventBus→src.contexts.shared.domain.Interface.Interface
- Direction
- domain.event_sourcing.EventBus uses domain.Interface, so a change to domain.Interface can break domain.event_sourcing.EventBus, while a change to domain.event_sourcing.EventBus can't break domain.Interface.
- Position
- Below the diagonal: domain.event_sourcing.EventBus uses a module listed above it, which is the healthy direction.
28→5 domain.event_sourcing.EventSubscriber uses domain.Interface✕
- Connections
- 1 pair of types, where a type in domain.event_sourcing.EventSubscriber uses a type in domain.Interface.
- The types involved
src.contexts.shared.domain.event_sourcing.EventSubscriber.EventSubscriber→src.contexts.shared.domain.Interface.Interface
- Direction
- domain.event_sourcing.EventSubscriber uses domain.Interface, so a change to domain.Interface can break domain.event_sourcing.EventSubscriber, while a change to domain.event_sourcing.EventSubscriber can't break domain.Interface.
- Position
- Below the diagonal: domain.event_sourcing.EventSubscriber uses a module listed above it, which is the healthy direction.
28→14 domain.event_sourcing.EventSubscriber uses domain.event_sourcing.DomainEvent✕
- Connections
- 1 pair of types, where a type in domain.event_sourcing.EventSubscriber uses a type in domain.event_sourcing.DomainEvent.
- The types involved
src.contexts.shared.domain.event_sourcing.EventSubscriber.EventSubscriber→src.contexts.shared.domain.event_sourcing.DomainEvent.DomainEvent
- Direction
- domain.event_sourcing.EventSubscriber uses domain.event_sourcing.DomainEvent, so a change to domain.event_sourcing.DomainEvent can break domain.event_sourcing.EventSubscriber, while a change to domain.event_sourcing.EventSubscriber can't break domain.event_sourcing.DomainEvent.
- Position
- Below the diagonal: domain.event_sourcing.EventSubscriber uses a module listed above it, which is the healthy direction.
29→5 domain.logger.Logger uses domain.Interface✕
- Connections
- 1 pair of types, where a type in domain.logger.Logger uses a type in domain.Interface.
- The types involved
src.contexts.shared.domain.logger.Logger.Logger→src.contexts.shared.domain.Interface.Interface
- Direction
- domain.logger.Logger uses domain.Interface, so a change to domain.Interface can break domain.logger.Logger, while a change to domain.logger.Logger can't break domain.Interface.
- Position
- Below the diagonal: domain.logger.Logger uses a module listed above it, which is the healthy direction.
30→3 Infrastructure.eventbus.InMemoryEventBus uses domain.BaseObject✕
- Connections
- 1 pair of types, where a type in Infrastructure.eventbus.InMemoryEventBus uses a type in domain.BaseObject.
- The types involved
src.contexts.shared.Infrastructure.eventbus.InMemoryEventBus.InMemoryEventBus→src.contexts.shared.domain.BaseObject.BaseObject
- Direction
- Infrastructure.eventbus.InMemoryEventBus uses domain.BaseObject, so a change to domain.BaseObject can break Infrastructure.eventbus.InMemoryEventBus, while a change to Infrastructure.eventbus.InMemoryEventBus can't break domain.BaseObject.
- Position
- Below the diagonal: Infrastructure.eventbus.InMemoryEventBus uses a module listed above it, which is the healthy direction.
30→27 Infrastructure.eventbus.InMemoryEventBus uses domain.event_sourcing.EventBus✕
- Connections
- 1 pair of types, where a type in Infrastructure.eventbus.InMemoryEventBus uses a type in domain.event_sourcing.EventBus.
- The types involved
src.contexts.shared.Infrastructure.eventbus.InMemoryEventBus.InMemoryEventBus→src.contexts.shared.domain.event_sourcing.EventBus.EventBus
- Direction
- Infrastructure.eventbus.InMemoryEventBus uses domain.event_sourcing.EventBus, so a change to domain.event_sourcing.EventBus can break Infrastructure.eventbus.InMemoryEventBus, while a change to Infrastructure.eventbus.InMemoryEventBus can't break domain.event_sourcing.EventBus.
- Position
- Below the diagonal: Infrastructure.eventbus.InMemoryEventBus uses a module listed above it, which is the healthy direction.
30→28 Infrastructure.eventbus.InMemoryEventBus uses domain.event_sourcing.EventSubscriber✕
- Connections
- 1 pair of types, where a type in Infrastructure.eventbus.InMemoryEventBus uses a type in domain.event_sourcing.EventSubscriber.
- The types involved
src.contexts.shared.Infrastructure.eventbus.InMemoryEventBus.InMemoryEventBus→src.contexts.shared.domain.event_sourcing.EventSubscriber.EventSubscriber
- Direction
- Infrastructure.eventbus.InMemoryEventBus uses domain.event_sourcing.EventSubscriber, so a change to domain.event_sourcing.EventSubscriber can break Infrastructure.eventbus.InMemoryEventBus, while a change to Infrastructure.eventbus.InMemoryEventBus can't break domain.event_sourcing.EventSubscriber.
- Position
- Below the diagonal: Infrastructure.eventbus.InMemoryEventBus uses a module listed above it, which is the healthy direction.
31→3 Infrastructure.logger.NativeConsoleLogger uses domain.BaseObject✕
- Connections
- 1 pair of types, where a type in Infrastructure.logger.NativeConsoleLogger uses a type in domain.BaseObject.
- The types involved
src.contexts.shared.Infrastructure.logger.NativeConsoleLogger.NativeConsoleLogger→src.contexts.shared.domain.BaseObject.BaseObject
- Direction
- Infrastructure.logger.NativeConsoleLogger uses domain.BaseObject, so a change to domain.BaseObject can break Infrastructure.logger.NativeConsoleLogger, while a change to Infrastructure.logger.NativeConsoleLogger can't break domain.BaseObject.
- Position
- Below the diagonal: Infrastructure.logger.NativeConsoleLogger uses a module listed above it, which is the healthy direction.
31→29 Infrastructure.logger.NativeConsoleLogger uses domain.logger.Logger✕
- Connections
- 1 pair of types, where a type in Infrastructure.logger.NativeConsoleLogger uses a type in domain.logger.Logger.
- The types involved
src.contexts.shared.Infrastructure.logger.NativeConsoleLogger.NativeConsoleLogger→src.contexts.shared.domain.logger.Logger.Logger
- Direction
- Infrastructure.logger.NativeConsoleLogger uses domain.logger.Logger, so a change to domain.logger.Logger can break Infrastructure.logger.NativeConsoleLogger, while a change to Infrastructure.logger.NativeConsoleLogger can't break domain.logger.Logger.
- Position
- Below the diagonal: Infrastructure.logger.NativeConsoleLogger uses a module listed above it, which is the healthy direction.
32→5 domain.cqrs.command.CommandBus uses domain.Interface✕
- Connections
- 1 pair of types, where a type in domain.cqrs.command.CommandBus uses a type in domain.Interface.
- The types involved
src.contexts.shared.domain.cqrs.command.CommandBus.CommandBus→src.contexts.shared.domain.Interface.Interface
- Direction
- domain.cqrs.command.CommandBus uses domain.Interface, so a change to domain.Interface can break domain.cqrs.command.CommandBus, while a change to domain.cqrs.command.CommandBus can't break domain.Interface.
- Position
- Below the diagonal: domain.cqrs.command.CommandBus uses a module listed above it, which is the healthy direction.
32→19 domain.cqrs.command.CommandBus uses domain.cqrs.command.Command✕
- Connections
- 1 pair of types, where a type in domain.cqrs.command.CommandBus uses a type in domain.cqrs.command.Command.
- The types involved
src.contexts.shared.domain.cqrs.command.CommandBus.CommandBus→src.contexts.shared.domain.cqrs.command.Command.Command
- Direction
- domain.cqrs.command.CommandBus uses domain.cqrs.command.Command, so a change to domain.cqrs.command.Command can break domain.cqrs.command.CommandBus, while a change to domain.cqrs.command.CommandBus can't break domain.cqrs.command.Command.
- Position
- Below the diagonal: domain.cqrs.command.CommandBus uses a module listed above it, which is the healthy direction.
33→5 domain.cqrs.command.CommandHandler uses domain.Interface✕
- Connections
- 1 pair of types, where a type in domain.cqrs.command.CommandHandler uses a type in domain.Interface.
- The types involved
src.contexts.shared.domain.cqrs.command.CommandHandler.CommandHandler→src.contexts.shared.domain.Interface.Interface
- Direction
- domain.cqrs.command.CommandHandler uses domain.Interface, so a change to domain.Interface can break domain.cqrs.command.CommandHandler, while a change to domain.cqrs.command.CommandHandler can't break domain.Interface.
- Position
- Below the diagonal: domain.cqrs.command.CommandHandler uses a module listed above it, which is the healthy direction.
33→19 domain.cqrs.command.CommandHandler uses domain.cqrs.command.Command✕
- Connections
- 1 pair of types, where a type in domain.cqrs.command.CommandHandler uses a type in domain.cqrs.command.Command.
- The types involved
src.contexts.shared.domain.cqrs.command.CommandHandler.CommandHandler→src.contexts.shared.domain.cqrs.command.Command.Command
- Direction
- domain.cqrs.command.CommandHandler uses domain.cqrs.command.Command, so a change to domain.cqrs.command.Command can break domain.cqrs.command.CommandHandler, while a change to domain.cqrs.command.CommandHandler can't break domain.cqrs.command.Command.
- Position
- Below the diagonal: domain.cqrs.command.CommandHandler uses a module listed above it, which is the healthy direction.
34→5 domain.cqrs.query.QueryBus uses domain.Interface✕
- Connections
- 1 pair of types, where a type in domain.cqrs.query.QueryBus uses a type in domain.Interface.
- The types involved
src.contexts.shared.domain.cqrs.query.QueryBus.QueryBus→src.contexts.shared.domain.Interface.Interface
- Direction
- domain.cqrs.query.QueryBus uses domain.Interface, so a change to domain.Interface can break domain.cqrs.query.QueryBus, while a change to domain.cqrs.query.QueryBus can't break domain.Interface.
- Position
- Below the diagonal: domain.cqrs.query.QueryBus uses a module listed above it, which is the healthy direction.
34→7 domain.cqrs.query.QueryBus uses domain.Response✕
- Connections
- 1 pair of types, where a type in domain.cqrs.query.QueryBus uses a type in domain.Response.
- The types involved
src.contexts.shared.domain.cqrs.query.QueryBus.QueryBus→src.contexts.shared.domain.Response.Response
- Direction
- domain.cqrs.query.QueryBus uses domain.Response, so a change to domain.Response can break domain.cqrs.query.QueryBus, while a change to domain.cqrs.query.QueryBus can't break domain.Response.
- Position
- Below the diagonal: domain.cqrs.query.QueryBus uses a module listed above it, which is the healthy direction.
34→21 domain.cqrs.query.QueryBus uses domain.cqrs.query.Query✕
- Connections
- 1 pair of types, where a type in domain.cqrs.query.QueryBus uses a type in domain.cqrs.query.Query.
- The types involved
src.contexts.shared.domain.cqrs.query.QueryBus.QueryBus→src.contexts.shared.domain.cqrs.query.Query.Query
- Direction
- domain.cqrs.query.QueryBus uses domain.cqrs.query.Query, so a change to domain.cqrs.query.Query can break domain.cqrs.query.QueryBus, while a change to domain.cqrs.query.QueryBus can't break domain.cqrs.query.Query.
- Position
- Below the diagonal: domain.cqrs.query.QueryBus uses a module listed above it, which is the healthy direction.
35→5 domain.cqrs.query.QueryHandler uses domain.Interface✕
- Connections
- 1 pair of types, where a type in domain.cqrs.query.QueryHandler uses a type in domain.Interface.
- The types involved
src.contexts.shared.domain.cqrs.query.QueryHandler.QueryHandler→src.contexts.shared.domain.Interface.Interface
- Direction
- domain.cqrs.query.QueryHandler uses domain.Interface, so a change to domain.Interface can break domain.cqrs.query.QueryHandler, while a change to domain.cqrs.query.QueryHandler can't break domain.Interface.
- Position
- Below the diagonal: domain.cqrs.query.QueryHandler uses a module listed above it, which is the healthy direction.
35→21 domain.cqrs.query.QueryHandler uses domain.cqrs.query.Query✕
- Connections
- 1 pair of types, where a type in domain.cqrs.query.QueryHandler uses a type in domain.cqrs.query.Query.
- The types involved
src.contexts.shared.domain.cqrs.query.QueryHandler.QueryHandler→src.contexts.shared.domain.cqrs.query.Query.Query
- Direction
- domain.cqrs.query.QueryHandler uses domain.cqrs.query.Query, so a change to domain.cqrs.query.Query can break domain.cqrs.query.QueryHandler, while a change to domain.cqrs.query.QueryHandler can't break domain.cqrs.query.Query.
- Position
- Below the diagonal: domain.cqrs.query.QueryHandler uses a module listed above it, which is the healthy direction.
36→25 domain.criteria.Criteria uses domain.criteria.Limit✕
- Connections
- 1 pair of types, where a type in domain.criteria.Criteria uses a type in domain.criteria.Limit.
- The types involved
src.contexts.shared.domain.criteria.Criteria.Criteria→src.contexts.shared.domain.criteria.Limit.Limit
- Direction
- domain.criteria.Criteria uses domain.criteria.Limit, so a change to domain.criteria.Limit can break domain.criteria.Criteria, while a change to domain.criteria.Criteria can't break domain.criteria.Limit.
- Position
- Below the diagonal: domain.criteria.Criteria uses a module listed above it, which is the healthy direction.
36→26 domain.criteria.Criteria uses domain.criteria.OrderBy✕
- Connections
- 1 pair of types, where a type in domain.criteria.Criteria uses a type in domain.criteria.OrderBy.
- The types involved
src.contexts.shared.domain.criteria.Criteria.Criteria→src.contexts.shared.domain.criteria.OrderBy.OrderBy
- Direction
- domain.criteria.Criteria uses domain.criteria.OrderBy, so a change to domain.criteria.OrderBy can break domain.criteria.Criteria, while a change to domain.criteria.Criteria can't break domain.criteria.OrderBy.
- Position
- Below the diagonal: domain.criteria.Criteria uses a module listed above it, which is the healthy direction.
37→3 Infrastructure.cqrs.InMemoryCommandBus uses domain.BaseObject✕
- Connections
- 1 pair of types, where a type in Infrastructure.cqrs.InMemoryCommandBus uses a type in domain.BaseObject.
- The types involved
src.contexts.shared.Infrastructure.cqrs.InMemoryCommandBus.InMemoryCommandBus→src.contexts.shared.domain.BaseObject.BaseObject
- Direction
- Infrastructure.cqrs.InMemoryCommandBus uses domain.BaseObject, so a change to domain.BaseObject can break Infrastructure.cqrs.InMemoryCommandBus, while a change to Infrastructure.cqrs.InMemoryCommandBus can't break domain.BaseObject.
- Position
- Below the diagonal: Infrastructure.cqrs.InMemoryCommandBus uses a module listed above it, which is the healthy direction.
37→19 Infrastructure.cqrs.InMemoryCommandBus uses domain.cqrs.command.Command✕
- Connections
- 1 pair of types, where a type in Infrastructure.cqrs.InMemoryCommandBus uses a type in domain.cqrs.command.Command.
- The types involved
src.contexts.shared.Infrastructure.cqrs.InMemoryCommandBus.InMemoryCommandBus→src.contexts.shared.domain.cqrs.command.Command.Command
- Direction
- Infrastructure.cqrs.InMemoryCommandBus uses domain.cqrs.command.Command, so a change to domain.cqrs.command.Command can break Infrastructure.cqrs.InMemoryCommandBus, while a change to Infrastructure.cqrs.InMemoryCommandBus can't break domain.cqrs.command.Command.
- Position
- Below the diagonal: Infrastructure.cqrs.InMemoryCommandBus uses a module listed above it, which is the healthy direction.
37→32 Infrastructure.cqrs.InMemoryCommandBus uses domain.cqrs.command.CommandBus✕
- Connections
- 1 pair of types, where a type in Infrastructure.cqrs.InMemoryCommandBus uses a type in domain.cqrs.command.CommandBus.
- The types involved
src.contexts.shared.Infrastructure.cqrs.InMemoryCommandBus.InMemoryCommandBus→src.contexts.shared.domain.cqrs.command.CommandBus.CommandBus
- Direction
- Infrastructure.cqrs.InMemoryCommandBus uses domain.cqrs.command.CommandBus, so a change to domain.cqrs.command.CommandBus can break Infrastructure.cqrs.InMemoryCommandBus, while a change to Infrastructure.cqrs.InMemoryCommandBus can't break domain.cqrs.command.CommandBus.
- Position
- Below the diagonal: Infrastructure.cqrs.InMemoryCommandBus uses a module listed above it, which is the healthy direction.
38→3 Infrastructure.cqrs.InMemoryQueryBus uses domain.BaseObject✕
- Connections
- 1 pair of types, where a type in Infrastructure.cqrs.InMemoryQueryBus uses a type in domain.BaseObject.
- The types involved
src.contexts.shared.Infrastructure.cqrs.InMemoryQueryBus.InMemoryQueryBus→src.contexts.shared.domain.BaseObject.BaseObject
- Direction
- Infrastructure.cqrs.InMemoryQueryBus uses domain.BaseObject, so a change to domain.BaseObject can break Infrastructure.cqrs.InMemoryQueryBus, while a change to Infrastructure.cqrs.InMemoryQueryBus can't break domain.BaseObject.
- Position
- Below the diagonal: Infrastructure.cqrs.InMemoryQueryBus uses a module listed above it, which is the healthy direction.
38→21 Infrastructure.cqrs.InMemoryQueryBus uses domain.cqrs.query.Query✕
- Connections
- 1 pair of types, where a type in Infrastructure.cqrs.InMemoryQueryBus uses a type in domain.cqrs.query.Query.
- The types involved
src.contexts.shared.Infrastructure.cqrs.InMemoryQueryBus.InMemoryQueryBus→src.contexts.shared.domain.cqrs.query.Query.Query
- Direction
- Infrastructure.cqrs.InMemoryQueryBus uses domain.cqrs.query.Query, so a change to domain.cqrs.query.Query can break Infrastructure.cqrs.InMemoryQueryBus, while a change to Infrastructure.cqrs.InMemoryQueryBus can't break domain.cqrs.query.Query.
- Position
- Below the diagonal: Infrastructure.cqrs.InMemoryQueryBus uses a module listed above it, which is the healthy direction.
38→34 Infrastructure.cqrs.InMemoryQueryBus uses domain.cqrs.query.QueryBus✕
- Connections
- 1 pair of types, where a type in Infrastructure.cqrs.InMemoryQueryBus uses a type in domain.cqrs.query.QueryBus.
- The types involved
src.contexts.shared.Infrastructure.cqrs.InMemoryQueryBus.InMemoryQueryBus→src.contexts.shared.domain.cqrs.query.QueryBus.QueryBus
- Direction
- Infrastructure.cqrs.InMemoryQueryBus uses domain.cqrs.query.QueryBus, so a change to domain.cqrs.query.QueryBus can break Infrastructure.cqrs.InMemoryQueryBus, while a change to Infrastructure.cqrs.InMemoryQueryBus can't break domain.cqrs.query.QueryBus.
- Position
- Below the diagonal: Infrastructure.cqrs.InMemoryQueryBus uses a module listed above it, which is the healthy direction.
39→36 Infrastructure.persistence.mongo uses domain.criteria.Criteria✕
- Connections
- 1 pair of types, where a type in Infrastructure.persistence.mongo uses a type in domain.criteria.Criteria.
- The types involved
src.contexts.shared.Infrastructure.persistence.mongo.parse_criteria_to_mongo_query→src.contexts.shared.domain.criteria.Criteria.Criteria
- Direction
- Infrastructure.persistence.mongo uses domain.criteria.Criteria, so a change to domain.criteria.Criteria can break Infrastructure.persistence.mongo, while a change to Infrastructure.persistence.mongo can't break domain.criteria.Criteria.
- Position
- Below the diagonal: Infrastructure.persistence.mongo uses a module listed above it, which is the healthy direction.
40→36 Infrastructure.persistence.mongo.PyMongoRepository uses domain.criteria.Criteria✕
- Connections
- 1 pair of types, where a type in Infrastructure.persistence.mongo.PyMongoRepository uses a type in domain.criteria.Criteria.
- The types involved
src.contexts.shared.Infrastructure.persistence.mongo.PyMongoRepository.PyMongoRepository→src.contexts.shared.domain.criteria.Criteria.Criteria
- Direction
- Infrastructure.persistence.mongo.PyMongoRepository uses domain.criteria.Criteria, so a change to domain.criteria.Criteria can break Infrastructure.persistence.mongo.PyMongoRepository, while a change to Infrastructure.persistence.mongo.PyMongoRepository can't break domain.criteria.Criteria.
- Position
- Below the diagonal: Infrastructure.persistence.mongo.PyMongoRepository uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 22 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with parse_dict_format_to_criteria.py, MinioRepository.py; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +16.7 pts | Low | ADR Quality |
| Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with parse_dict_format_to_criteria.py, MinioRepository.py. | +14.2 pts | Low | Knowledge Freshness |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +7.7 pts | Low | Knowledge Freshness |
| 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. | +12.8 pts | Medium | Architecture documentation |
| Expand the README with getting-started, architecture overview and a project map. | +6.0 pts | Medium | Documentation (README) |
| Enable Dependabot/Renovate or a dependency-review gate. | +2.3 pts | Medium | Security & performance tooling |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +1.8 pts | Medium | Deployment & Rollback |
| Swallowed exception (empty catch) | +1.3 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/contexts/shared/Infrastructure/eventbus/InMemoryEventBus.py | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/contexts/shared/Infrastructure/persistence/minio/MinioRepository.py | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/contexts/shared/Infrastructure/parsers/parse_dict_format_to_criteria.py | 8.5 | Near-clean | Cognitive Complexity: parse_dict_format_to_criteria.parse_dict_to_criteria (cognitive 31) |
| src/contexts/shared/Infrastructure/persistence/minio/MinioClientFactory.py | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 51 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 — 51 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, 40 of 54 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.py) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 79 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- 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 — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- 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.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- 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.
- C3 Audit Trail — 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. 'pymongo' is imported (src/contexts/shared/Infrastructure/persistence/mongo/PyMongoClientFactory.py:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'pymongo' is imported (src/contexts/shared/Infrastructure/persistence/mongo/PyMongoClientFactory.py:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'pymongo' is imported (src/contexts/shared/Infrastructure/persistence/mongo/PyMongoClientFactory.py:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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.
- 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.
- 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.
- 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.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was parse_dict_format_to_criteria.parse_dict_to_criteria at 31.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with parse_dict_format_to_criteria.parse_dict_to_criteria (cognitive 31). — Refactoring it lifts Cognitive Complexity from 9.2 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with MinioClientFactory.py. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 11 classes have LCOM4 above 3.
D12 · Dependency Hygiene
9 outdated, 0 yanked pinned Python distributions. 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 (poetry.lock, 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
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 23 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 9 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (14 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
3 deducted task-comment markers across 663 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with InMemoryEventBus.py (2), MinioRepository.py. — One of this dimension's main actionable groups (3 warning-level).
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).
D27 · Navigability
46 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
22 finding(s): 0 critical, 17 high, 5 medium, 0 low. 16 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 16 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 (16 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
4 finding(s): 1 critical, 2 high, 1 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
2 of 2 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/contexts/shared/Infrastructure/parsers/parse_dict_format_to_criteria.py. Counted over 2 of the 49 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 2 Orphaned file finding(s) in Knowledge Freshness — start with parse_dict_format_to_criteria.py, MinioRepository.py. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 9 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
AX8 · Test isolation
M1 · Documentation (README)
- The root README is 33 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
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
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/contexts/shared/Infrastructure/eventbus/InMemoryEventBus.py:30
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 78% | Adequate — gated by X3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 69% | Adequate | Acceptable, with room to improve. |
| Maturity | 37% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 65% | Adequate | Acceptable, with room to improve. |
| Security | 91% | Exemplary | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 3 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'pymongo' (src/contexts/shared/Infrastructure/persistence/mongo/PyMongoClientFactory.py:1) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and MongoEngine model fields, Alembic and Django migration columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL files). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'pymongo' (src/contexts/shared/Infrastructure/persistence/mongo/PyMongoClientFactory.py:1) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and mongoengine model fields, Alembic and Django migration columns, SQL schemas). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'pymongo' (src/contexts/shared/Infrastructure/persistence/mongo/PyMongoClientFactory.py:1) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and mongoengine model fields, Alembic and Django migration columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 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 applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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
- 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 — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) 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.
- D10 Test Quality — ~17 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 — no .py test runner
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (663 LoC, 50 module-visible types across 15 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- 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
- D9 Test Distribution — Test source is 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows 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 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 20 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment src/contexts/shared/Infrastructure/persistence/minio/MinioRepository.py:60
- TodoComment src/contexts/shared/Infrastructure/eventbus/InMemoryEventBus.py:29
- TodoComment src/contexts/shared/Infrastructure/eventbus/InMemoryEventBus.py:31
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- parse_dict_format_to_criteria.parse_dict_to_criteria (cognitive 31) src/contexts/shared/Infrastructure/parsers/parse_dict_format_to_criteria.py:15
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) src/contexts/shared/Infrastructure/persistence/minio/MinioClientFactory.py:21
- Swallowed exception (empty catch) src/contexts/shared/Infrastructure/eventbus/InMemoryEventBus.py:30
Minor — 8 finding(s)
- Orphaned file src/contexts/shared/Infrastructure/parsers/parse_dict_format_to_criteria.py:1
- Orphaned file src/contexts/shared/Infrastructure/persistence/minio/MinioRepository.py:1
- No ADRs found
- Orphaned files with no living knowledge
- REDACTED
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
Minor — 9 finding(s)
- Outdated: anyio
- Outdated: fastapi
- Outdated: idna
- Outdated: minio
- Outdated: pydantic
- Outdated: pymongo
- Outdated: sniffio
- Outdated: starlette
- Outdated: typing-extensions
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-70abbca498c64da9b59c173761cd0fb1/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-70abbca498c64da9b59c173761cd0fb1/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 . | 22 | 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 . | 4 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | 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 |