Executive summary
knucklesuganda/py_assimilator falls short of our standard for production, in part because 12 files are no longer known to anyone active in the project. It scores 63 out of 100 and is rated Adequate, and all four of its critical findings are security problems in the build pipeline.
Maturity, at 50, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 12 files no active contributor knows, worth about 12 points. Recording design decisions comes next, worth about 7 points. Raising Maturity to 70 would lift the score to about 69.
Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 3,335 lines, about €3,800 to rebuild.
If Maturity rose from 50 to 70, the lowest score rated Strong, the score would rise from 63 to about 69.
Rebuild cost: about €3,800 · Estimate
| Cost to rebuild | €1,300 to €6,300, for 21 to 66 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,335 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 core.database.models | 2 core.database.repository | 3 core.database.specifications.filtering_options | 4 core.database.specifications.types | 5 core.exceptions | 6 core.patterns.context_managers | 7 core.patterns.error_wrapper | 8 core.services.base | 9 core.usability.registry | 10 alchemy.database.error_wrapper | 11 alchemy.database.repository | 12 alchemy.database.specifications.filtering_options | 13 core.database.specifications.specifications | 14 core.database.unit_of_work | 15 core.events.events | 16 core.events.exceptions | 17 internal.database.error_wrapper | 18 internal.database.repository | 19 internal.database.specifications | 20 internal.database.specifications.filtering_options | 21 mongo.database.error_wrapper | 22 mongo.database.models | 23 mongo.database.repository | 24 redis_.database.repository | 25 alchemy.database.specifications.specifications | 26 alchemy.database.unit_of_work | 27 alchemy.events.database.repository | 28 core.events.events_bus | 29 core.services.crud | 30 internal.database.specifications.filter_specifications | 31 internal.database.specifications.specifications | 32 internal.database.unit_of_work | 33 mongo.database.unit_of_work | 34 redis_.database.unit_of_work | 35 core.events.outbox_relay | 36 core.usability | 37 internal.events.events_bus | 38 kafka_.events.events_bus | 39 redis_.events.events_bus | 40 alchemy.events.outbox_relay |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core.database.models | ||||||||||||||||||||||||||||||||||||||||
| 2 core.database.repository | ||||||||||||||||||||||||||||||||||||||||
| 3 core.database.specifications.filtering_options | ||||||||||||||||||||||||||||||||||||||||
| 4 core.database.specifications.types | ||||||||||||||||||||||||||||||||||||||||
| 5 core.exceptions | ||||||||||||||||||||||||||||||||||||||||
| 6 core.patterns.context_managers | ||||||||||||||||||||||||||||||||||||||||
| 7 core.patterns.error_wrapper | ||||||||||||||||||||||||||||||||||||||||
| 8 core.services.base | ||||||||||||||||||||||||||||||||||||||||
| 9 core.usability.registry | ||||||||||||||||||||||||||||||||||||||||
| 10 alchemy.database.error_wrapper | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 alchemy.database.repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 alchemy.database.specifications.filtering_options | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 core.database.specifications.specifications | 4 | |||||||||||||||||||||||||||||||||||||||
| 14 core.database.unit_of_work | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 core.events.events | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 core.events.exceptions | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 internal.database.error_wrapper | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 internal.database.repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 internal.database.specifications | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 internal.database.specifications.filtering_options | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 mongo.database.error_wrapper | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 mongo.database.models | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 mongo.database.repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 redis_.database.repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 alchemy.database.specifications.specifications | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 alchemy.database.unit_of_work | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 alchemy.events.database.repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 core.events.events_bus | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 core.services.crud | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 internal.database.specifications.filter_specifications | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 internal.database.specifications.specifications | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 internal.database.unit_of_work | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 mongo.database.unit_of_work | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 redis_.database.unit_of_work | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 core.events.outbox_relay | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 core.usability | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 internal.events.events_bus | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 kafka_.events.events_bus | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 redis_.events.events_bus | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 alchemy.events.outbox_relay | 1 | 1 | 1 |
10→7 alchemy.database.error_wrapper uses core.patterns.error_wrapper✕
- Connections
- 1 pair of types, where a type in alchemy.database.error_wrapper uses a type in core.patterns.error_wrapper.
- The types involved
assimilator.alchemy.database.error_wrapper.AlchemyErrorWrapper→assimilator.core.patterns.error_wrapper.ErrorWrapper
- Direction
- alchemy.database.error_wrapper uses core.patterns.error_wrapper, so a change to core.patterns.error_wrapper can break alchemy.database.error_wrapper, while a change to alchemy.database.error_wrapper can't break core.patterns.error_wrapper.
- Position
- Below the diagonal: alchemy.database.error_wrapper uses a module listed above it, which is the healthy direction.
11→2 alchemy.database.repository uses core.database.repository✕
- Connections
- 1 pair of types, where a type in alchemy.database.repository uses a type in core.database.repository.
- The types involved
assimilator.alchemy.database.repository.AlchemyRepository→assimilator.core.database.repository.Repository
- Direction
- alchemy.database.repository uses core.database.repository, so a change to core.database.repository can break alchemy.database.repository, while a change to alchemy.database.repository can't break core.database.repository.
- Position
- Below the diagonal: alchemy.database.repository uses a module listed above it, which is the healthy direction.
12→3 alchemy.database.specifications.filtering_options uses core.database.specifications.filtering_options✕
- Connections
- 1 pair of types, where a type in alchemy.database.specifications.filtering_options uses a type in core.database.specifications.filtering_options.
- The types involved
assimilator.alchemy.database.specifications.filtering_options.AlchemyFilteringOptions→assimilator.core.database.specifications.filtering_options.FilteringOptions
- Direction
- alchemy.database.specifications.filtering_options uses core.database.specifications.filtering_options, so a change to core.database.specifications.filtering_options can break alchemy.database.specifications.filtering_options, while a change to alchemy.database.specifications.filtering_options can't break core.database.specifications.filtering_options.
- Position
- Below the diagonal: alchemy.database.specifications.filtering_options uses a module listed above it, which is the healthy direction.
13→4 core.database.specifications.specifications uses core.database.specifications.types✕
- Connections
- 4 pairs of types, where a type in core.database.specifications.specifications uses a type in core.database.specifications.types.
- The types involved
assimilator.core.database.specifications.specifications.SpecificationList→assimilator.core.database.specifications.types.JoinSpecificationProtocolassimilator.core.database.specifications.specifications.SpecificationList→assimilator.core.database.specifications.types.OnlySpecificationProtocolassimilator.core.database.specifications.specifications.SpecificationList→assimilator.core.database.specifications.types.OrderSpecificationProtocolassimilator.core.database.specifications.specifications.SpecificationList→assimilator.core.database.specifications.types.PaginateSpecificationProtocol
- Direction
- core.database.specifications.specifications uses core.database.specifications.types, so a change to core.database.specifications.types can break core.database.specifications.specifications, while a change to core.database.specifications.specifications can't break core.database.specifications.types.
- Position
- Below the diagonal: core.database.specifications.specifications uses a module listed above it, which is the healthy direction.
14→2 core.database.unit_of_work uses core.database.repository✕
- Connections
- 1 pair of types, where a type in core.database.unit_of_work uses a type in core.database.repository.
- The types involved
assimilator.core.database.unit_of_work.UnitOfWork→assimilator.core.database.repository.Repository
- Direction
- core.database.unit_of_work uses core.database.repository, so a change to core.database.repository can break core.database.unit_of_work, while a change to core.database.unit_of_work can't break core.database.repository.
- Position
- Below the diagonal: core.database.unit_of_work uses a module listed above it, which is the healthy direction.
14→7 core.database.unit_of_work uses core.patterns.error_wrapper✕
- Connections
- 1 pair of types, where a type in core.database.unit_of_work uses a type in core.patterns.error_wrapper.
- The types involved
assimilator.core.database.unit_of_work.UnitOfWork→assimilator.core.patterns.error_wrapper.ErrorWrapper
- Direction
- core.database.unit_of_work uses core.patterns.error_wrapper, so a change to core.patterns.error_wrapper can break core.database.unit_of_work, while a change to core.database.unit_of_work can't break core.patterns.error_wrapper.
- Position
- Below the diagonal: core.database.unit_of_work uses a module listed above it, which is the healthy direction.
15→1 core.events.events uses core.database.models✕
- Connections
- 1 pair of types, where a type in core.events.events uses a type in core.database.models.
- The types involved
assimilator.core.events.events.Event→assimilator.core.database.models.BaseModel
- Direction
- core.events.events uses core.database.models, so a change to core.database.models can break core.events.events, while a change to core.events.events can't break core.database.models.
- Position
- Below the diagonal: core.events.events uses a module listed above it, which is the healthy direction.
16→5 core.events.exceptions uses core.exceptions✕
- Connections
- 1 pair of types, where a type in core.events.exceptions uses a type in core.exceptions.
- The types involved
assimilator.core.events.exceptions.EventParsingError→assimilator.core.exceptions.ParsingError
- Direction
- core.events.exceptions uses core.exceptions, so a change to core.exceptions can break core.events.exceptions, while a change to core.events.exceptions can't break core.exceptions.
- Position
- Below the diagonal: core.events.exceptions uses a module listed above it, which is the healthy direction.
17→7 internal.database.error_wrapper uses core.patterns.error_wrapper✕
- Connections
- 1 pair of types, where a type in internal.database.error_wrapper uses a type in core.patterns.error_wrapper.
- The types involved
assimilator.internal.database.error_wrapper.InternalErrorWrapper→assimilator.core.patterns.error_wrapper.ErrorWrapper
- Direction
- internal.database.error_wrapper uses core.patterns.error_wrapper, so a change to core.patterns.error_wrapper can break internal.database.error_wrapper, while a change to internal.database.error_wrapper can't break core.patterns.error_wrapper.
- Position
- Below the diagonal: internal.database.error_wrapper uses a module listed above it, which is the healthy direction.
18→2 internal.database.repository uses core.database.repository✕
- Connections
- 1 pair of types, where a type in internal.database.repository uses a type in core.database.repository.
- The types involved
assimilator.internal.database.repository.InternalRepository→assimilator.core.database.repository.Repository
- Direction
- internal.database.repository uses core.database.repository, so a change to core.database.repository can break internal.database.repository, while a change to internal.database.repository can't break core.database.repository.
- Position
- Below the diagonal: internal.database.repository uses a module listed above it, which is the healthy direction.
19→1 internal.database.specifications uses core.database.models✕
- Connections
- 1 pair of types, where a type in internal.database.specifications uses a type in core.database.models.
- The types involved
assimilator.internal.database.specifications.utils→assimilator.core.database.models.BaseModel
- Direction
- internal.database.specifications uses core.database.models, so a change to core.database.models can break internal.database.specifications, while a change to internal.database.specifications can't break core.database.models.
- Position
- Below the diagonal: internal.database.specifications uses a module listed above it, which is the healthy direction.
20→3 internal.database.specifications.filtering_options uses core.database.specifications.filtering_options✕
- Connections
- 1 pair of types, where a type in internal.database.specifications.filtering_options uses a type in core.database.specifications.filtering_options.
- The types involved
assimilator.internal.database.specifications.filtering_options.InternalFilteringOptions→assimilator.core.database.specifications.filtering_options.FilteringOptions
- Direction
- internal.database.specifications.filtering_options uses core.database.specifications.filtering_options, so a change to core.database.specifications.filtering_options can break internal.database.specifications.filtering_options, while a change to internal.database.specifications.filtering_options can't break core.database.specifications.filtering_options.
- Position
- Below the diagonal: internal.database.specifications.filtering_options uses a module listed above it, which is the healthy direction.
21→7 mongo.database.error_wrapper uses core.patterns.error_wrapper✕
- Connections
- 1 pair of types, where a type in mongo.database.error_wrapper uses a type in core.patterns.error_wrapper.
- The types involved
assimilator.mongo.database.error_wrapper.MongoErrorWrapper→assimilator.core.patterns.error_wrapper.ErrorWrapper
- Direction
- mongo.database.error_wrapper uses core.patterns.error_wrapper, so a change to core.patterns.error_wrapper can break mongo.database.error_wrapper, while a change to mongo.database.error_wrapper can't break core.patterns.error_wrapper.
- Position
- Below the diagonal: mongo.database.error_wrapper uses a module listed above it, which is the healthy direction.
22→1 mongo.database.models uses core.database.models✕
- Connections
- 1 pair of types, where a type in mongo.database.models uses a type in core.database.models.
- The types involved
assimilator.mongo.database.models.MongoModel→assimilator.core.database.models.BaseModel
- Direction
- mongo.database.models uses core.database.models, so a change to core.database.models can break mongo.database.models, while a change to mongo.database.models can't break core.database.models.
- Position
- Below the diagonal: mongo.database.models uses a module listed above it, which is the healthy direction.
23→2 mongo.database.repository uses core.database.repository✕
- Connections
- 1 pair of types, where a type in mongo.database.repository uses a type in core.database.repository.
- The types involved
assimilator.mongo.database.repository.MongoRepository→assimilator.core.database.repository.Repository
- Direction
- mongo.database.repository uses core.database.repository, so a change to core.database.repository can break mongo.database.repository, while a change to mongo.database.repository can't break core.database.repository.
- Position
- Below the diagonal: mongo.database.repository uses a module listed above it, which is the healthy direction.
24→2 redis_.database.repository uses core.database.repository✕
- Connections
- 1 pair of types, where a type in redis_.database.repository uses a type in core.database.repository.
- The types involved
assimilator.redis_.database.repository.RedisRepository→assimilator.core.database.repository.Repository
- Direction
- redis_.database.repository uses core.database.repository, so a change to core.database.repository can break redis_.database.repository, while a change to redis_.database.repository can't break core.database.repository.
- Position
- Below the diagonal: redis_.database.repository uses a module listed above it, which is the healthy direction.
25→13 alchemy.database.specifications.specifications uses core.database.specifications.specifications✕
- Connections
- 2 pairs of types, where a type in alchemy.database.specifications.specifications uses a type in core.database.specifications.specifications.
- The types involved
assimilator.alchemy.database.specifications.specifications.AlchemyFilter→assimilator.core.database.specifications.specifications.FilterSpecificationassimilator.alchemy.database.specifications.specifications.AlchemySpecificationList→assimilator.core.database.specifications.specifications.SpecificationList
- Direction
- alchemy.database.specifications.specifications uses core.database.specifications.specifications, so a change to core.database.specifications.specifications can break alchemy.database.specifications.specifications, while a change to alchemy.database.specifications.specifications can't break core.database.specifications.specifications.
- Position
- Below the diagonal: alchemy.database.specifications.specifications uses a module listed above it, which is the healthy direction.
26→11 alchemy.database.unit_of_work uses alchemy.database.repository✕
- Connections
- 1 pair of types, where a type in alchemy.database.unit_of_work uses a type in alchemy.database.repository.
- The types involved
assimilator.alchemy.database.unit_of_work.AlchemyUnitOfWork→assimilator.alchemy.database.repository.AlchemyRepository
- Direction
- alchemy.database.unit_of_work uses alchemy.database.repository, so a change to alchemy.database.repository can break alchemy.database.unit_of_work, while a change to alchemy.database.unit_of_work can't break alchemy.database.repository.
- Position
- Below the diagonal: alchemy.database.unit_of_work uses a module listed above it, which is the healthy direction.
26→14 alchemy.database.unit_of_work uses core.database.unit_of_work✕
- Connections
- 1 pair of types, where a type in alchemy.database.unit_of_work uses a type in core.database.unit_of_work.
- The types involved
assimilator.alchemy.database.unit_of_work.AlchemyUnitOfWork→assimilator.core.database.unit_of_work.UnitOfWork
- Direction
- alchemy.database.unit_of_work uses core.database.unit_of_work, so a change to core.database.unit_of_work can break alchemy.database.unit_of_work, while a change to alchemy.database.unit_of_work can't break core.database.unit_of_work.
- Position
- Below the diagonal: alchemy.database.unit_of_work uses a module listed above it, which is the healthy direction.
27→7 alchemy.events.database.repository uses core.patterns.error_wrapper✕
- Connections
- 1 pair of types, where a type in alchemy.events.database.repository uses a type in core.patterns.error_wrapper.
- The types involved
assimilator.alchemy.events.database.repository.AlchemyOutboxRepository→assimilator.core.patterns.error_wrapper.ErrorWrapper
- Direction
- alchemy.events.database.repository uses core.patterns.error_wrapper, so a change to core.patterns.error_wrapper can break alchemy.events.database.repository, while a change to alchemy.events.database.repository can't break core.patterns.error_wrapper.
- Position
- Below the diagonal: alchemy.events.database.repository uses a module listed above it, which is the healthy direction.
27→11 alchemy.events.database.repository uses alchemy.database.repository✕
- Connections
- 1 pair of types, where a type in alchemy.events.database.repository uses a type in alchemy.database.repository.
- The types involved
assimilator.alchemy.events.database.repository.AlchemyOutboxRepository→assimilator.alchemy.database.repository.AlchemyRepository
- Direction
- alchemy.events.database.repository uses alchemy.database.repository, so a change to alchemy.database.repository can break alchemy.events.database.repository, while a change to alchemy.events.database.repository can't break alchemy.database.repository.
- Position
- Below the diagonal: alchemy.events.database.repository uses a module listed above it, which is the healthy direction.
28→6 core.events.events_bus uses core.patterns.context_managers✕
- Connections
- 2 pairs of types, where a type in core.events.events_bus uses a type in core.patterns.context_managers.
- The types involved
assimilator.core.events.events_bus.EventConsumer→assimilator.core.patterns.context_managers.StartCloseContextMixinassimilator.core.events.events_bus.EventProducer→assimilator.core.patterns.context_managers.StartCloseContextMixin
- Direction
- core.events.events_bus uses core.patterns.context_managers, so a change to core.patterns.context_managers can break core.events.events_bus, while a change to core.events.events_bus can't break core.patterns.context_managers.
- Position
- Below the diagonal: core.events.events_bus uses a module listed above it, which is the healthy direction.
28→15 core.events.events_bus uses core.events.events✕
- Connections
- 2 pairs of types, where a type in core.events.events_bus uses a type in core.events.events.
- The types involved
assimilator.core.events.events_bus.EventBus→assimilator.core.events.events.Eventassimilator.core.events.events_bus.EventProducer→assimilator.core.events.events.Event
- Direction
- core.events.events_bus uses core.events.events, so a change to core.events.events can break core.events.events_bus, while a change to core.events.events_bus can't break core.events.events.
- Position
- Below the diagonal: core.events.events_bus uses a module listed above it, which is the healthy direction.
29→8 core.services.crud uses core.services.base✕
- Connections
- 1 pair of types, where a type in core.services.crud uses a type in core.services.base.
- The types involved
assimilator.core.services.crud.CRUDService→assimilator.core.services.base.Service
- Direction
- core.services.crud uses core.services.base, so a change to core.services.base can break core.services.crud, while a change to core.services.crud can't break core.services.base.
- Position
- Below the diagonal: core.services.crud uses a module listed above it, which is the healthy direction.
29→14 core.services.crud uses core.database.unit_of_work✕
- Connections
- 1 pair of types, where a type in core.services.crud uses a type in core.database.unit_of_work.
- The types involved
assimilator.core.services.crud.CRUDService→assimilator.core.database.unit_of_work.UnitOfWork
- Direction
- core.services.crud uses core.database.unit_of_work, so a change to core.database.unit_of_work can break core.services.crud, while a change to core.services.crud can't break core.database.unit_of_work.
- Position
- Below the diagonal: core.services.crud uses a module listed above it, which is the healthy direction.
30→13 internal.database.specifications.filter_specifications uses core.database.specifications.specifications✕
- Connections
- 1 pair of types, where a type in internal.database.specifications.filter_specifications uses a type in core.database.specifications.specifications.
- The types involved
assimilator.internal.database.specifications.filter_specifications.InternalFilter→assimilator.core.database.specifications.specifications.FilterSpecification
- Direction
- internal.database.specifications.filter_specifications uses core.database.specifications.specifications, so a change to core.database.specifications.specifications can break internal.database.specifications.filter_specifications, while a change to internal.database.specifications.filter_specifications can't break core.database.specifications.specifications.
- Position
- Below the diagonal: internal.database.specifications.filter_specifications uses a module listed above it, which is the healthy direction.
31→13 internal.database.specifications.specifications uses core.database.specifications.specifications✕
- Connections
- 1 pair of types, where a type in internal.database.specifications.specifications uses a type in core.database.specifications.specifications.
- The types involved
assimilator.internal.database.specifications.specifications.InternalSpecificationList→assimilator.core.database.specifications.specifications.SpecificationList
- Direction
- internal.database.specifications.specifications uses core.database.specifications.specifications, so a change to core.database.specifications.specifications can break internal.database.specifications.specifications, while a change to internal.database.specifications.specifications can't break core.database.specifications.specifications.
- Position
- Below the diagonal: internal.database.specifications.specifications uses a module listed above it, which is the healthy direction.
32→2 internal.database.unit_of_work uses core.database.repository✕
- Connections
- 1 pair of types, where a type in internal.database.unit_of_work uses a type in core.database.repository.
- The types involved
assimilator.internal.database.unit_of_work.InternalUnitOfWork→assimilator.core.database.repository.Repository
- Direction
- internal.database.unit_of_work uses core.database.repository, so a change to core.database.repository can break internal.database.unit_of_work, while a change to internal.database.unit_of_work can't break core.database.repository.
- Position
- Below the diagonal: internal.database.unit_of_work uses a module listed above it, which is the healthy direction.
32→14 internal.database.unit_of_work uses core.database.unit_of_work✕
- Connections
- 1 pair of types, where a type in internal.database.unit_of_work uses a type in core.database.unit_of_work.
- The types involved
assimilator.internal.database.unit_of_work.InternalUnitOfWork→assimilator.core.database.unit_of_work.UnitOfWork
- Direction
- internal.database.unit_of_work uses core.database.unit_of_work, so a change to core.database.unit_of_work can break internal.database.unit_of_work, while a change to internal.database.unit_of_work can't break core.database.unit_of_work.
- Position
- Below the diagonal: internal.database.unit_of_work uses a module listed above it, which is the healthy direction.
33→14 mongo.database.unit_of_work uses core.database.unit_of_work✕
- Connections
- 1 pair of types, where a type in mongo.database.unit_of_work uses a type in core.database.unit_of_work.
- The types involved
assimilator.mongo.database.unit_of_work.MongoUnitOfWork→assimilator.core.database.unit_of_work.UnitOfWork
- Direction
- mongo.database.unit_of_work uses core.database.unit_of_work, so a change to core.database.unit_of_work can break mongo.database.unit_of_work, while a change to mongo.database.unit_of_work can't break core.database.unit_of_work.
- Position
- Below the diagonal: mongo.database.unit_of_work uses a module listed above it, which is the healthy direction.
33→23 mongo.database.unit_of_work uses mongo.database.repository✕
- Connections
- 1 pair of types, where a type in mongo.database.unit_of_work uses a type in mongo.database.repository.
- The types involved
assimilator.mongo.database.unit_of_work.MongoUnitOfWork→assimilator.mongo.database.repository.MongoRepository
- Direction
- mongo.database.unit_of_work uses mongo.database.repository, so a change to mongo.database.repository can break mongo.database.unit_of_work, while a change to mongo.database.unit_of_work can't break mongo.database.repository.
- Position
- Below the diagonal: mongo.database.unit_of_work uses a module listed above it, which is the healthy direction.
34→14 redis_.database.unit_of_work uses core.database.unit_of_work✕
- Connections
- 1 pair of types, where a type in redis_.database.unit_of_work uses a type in core.database.unit_of_work.
- The types involved
assimilator.redis_.database.unit_of_work.RedisUnitOfWork→assimilator.core.database.unit_of_work.UnitOfWork
- Direction
- redis_.database.unit_of_work uses core.database.unit_of_work, so a change to core.database.unit_of_work can break redis_.database.unit_of_work, while a change to redis_.database.unit_of_work can't break core.database.unit_of_work.
- Position
- Below the diagonal: redis_.database.unit_of_work uses a module listed above it, which is the healthy direction.
34→24 redis_.database.unit_of_work uses redis_.database.repository✕
- Connections
- 1 pair of types, where a type in redis_.database.unit_of_work uses a type in redis_.database.repository.
- The types involved
assimilator.redis_.database.unit_of_work.RedisUnitOfWork→assimilator.redis_.database.repository.RedisRepository
- Direction
- redis_.database.unit_of_work uses redis_.database.repository, so a change to redis_.database.repository can break redis_.database.unit_of_work, while a change to redis_.database.unit_of_work can't break redis_.database.repository.
- Position
- Below the diagonal: redis_.database.unit_of_work uses a module listed above it, which is the healthy direction.
35→14 core.events.outbox_relay uses core.database.unit_of_work✕
- Connections
- 1 pair of types, where a type in core.events.outbox_relay uses a type in core.database.unit_of_work.
- The types involved
assimilator.core.events.outbox_relay.OutboxRelay→assimilator.core.database.unit_of_work.UnitOfWork
- Direction
- core.events.outbox_relay uses core.database.unit_of_work, so a change to core.database.unit_of_work can break core.events.outbox_relay, while a change to core.events.outbox_relay can't break core.database.unit_of_work.
- Position
- Below the diagonal: core.events.outbox_relay uses a module listed above it, which is the healthy direction.
35→28 core.events.outbox_relay uses core.events.events_bus✕
- Connections
- 1 pair of types, where a type in core.events.outbox_relay uses a type in core.events.events_bus.
- The types involved
assimilator.core.events.outbox_relay.OutboxRelay→assimilator.core.events.events_bus.EventProducer
- Direction
- core.events.outbox_relay uses core.events.events_bus, so a change to core.events.events_bus can break core.events.outbox_relay, while a change to core.events.outbox_relay can't break core.events.events_bus.
- Position
- Below the diagonal: core.events.outbox_relay uses a module listed above it, which is the healthy direction.
36→2 core.usability uses core.database.repository✕
- Connections
- 1 pair of types, where a type in core.usability uses a type in core.database.repository.
- The types involved
assimilator.core.usability.pattern_creator→assimilator.core.database.repository.Repository
- Direction
- core.usability uses core.database.repository, so a change to core.database.repository can break core.usability, while a change to core.usability can't break core.database.repository.
- Position
- Below the diagonal: core.usability uses a module listed above it, which is the healthy direction.
36→9 core.usability uses core.usability.registry✕
- Connections
- 1 pair of types, where a type in core.usability uses a type in core.usability.registry.
- The types involved
assimilator.core.usability.registry→assimilator.core.usability.registry.PatternList
- Direction
- core.usability uses core.usability.registry, so a change to core.usability.registry can break core.usability, while a change to core.usability can't break core.usability.registry.
- Position
- Below the diagonal: core.usability uses a module listed above it, which is the healthy direction.
36→14 core.usability uses core.database.unit_of_work✕
- Connections
- 1 pair of types, where a type in core.usability uses a type in core.database.unit_of_work.
- The types involved
assimilator.core.usability.pattern_creator→assimilator.core.database.unit_of_work.UnitOfWork
- Direction
- core.usability uses core.database.unit_of_work, so a change to core.database.unit_of_work can break core.usability, while a change to core.usability can't break core.database.unit_of_work.
- Position
- Below the diagonal: core.usability uses a module listed above it, which is the healthy direction.
36→29 core.usability uses core.services.crud✕
- Connections
- 1 pair of types, where a type in core.usability uses a type in core.services.crud.
- The types involved
assimilator.core.usability.pattern_creator→assimilator.core.services.crud.CRUDService
- Direction
- core.usability uses core.services.crud, so a change to core.services.crud can break core.usability, while a change to core.usability can't break core.services.crud.
- Position
- Below the diagonal: core.usability uses a module listed above it, which is the healthy direction.
37→15 internal.events.events_bus uses core.events.events✕
- Connections
- 1 pair of types, where a type in internal.events.events_bus uses a type in core.events.events.
- The types involved
assimilator.internal.events.events_bus.InternalEventProducer→assimilator.core.events.events.Event
- Direction
- internal.events.events_bus uses core.events.events, so a change to core.events.events can break internal.events.events_bus, while a change to internal.events.events_bus can't break core.events.events.
- Position
- Below the diagonal: internal.events.events_bus uses a module listed above it, which is the healthy direction.
37→28 internal.events.events_bus uses core.events.events_bus✕
- Connections
- 2 pairs of types, where a type in internal.events.events_bus uses a type in core.events.events_bus.
- The types involved
assimilator.internal.events.events_bus.InternalEventConsumer→assimilator.core.events.events_bus.EventConsumerassimilator.internal.events.events_bus.InternalEventProducer→assimilator.core.events.events_bus.EventProducer
- Direction
- internal.events.events_bus uses core.events.events_bus, so a change to core.events.events_bus can break internal.events.events_bus, while a change to internal.events.events_bus can't break core.events.events_bus.
- Position
- Below the diagonal: internal.events.events_bus uses a module listed above it, which is the healthy direction.
38→15 kafka_.events.events_bus uses core.events.events✕
- Connections
- 1 pair of types, where a type in kafka_.events.events_bus uses a type in core.events.events.
- The types involved
assimilator.kafka_.events.events_bus.KafkaEventProducer→assimilator.core.events.events.Event
- Direction
- kafka_.events.events_bus uses core.events.events, so a change to core.events.events can break kafka_.events.events_bus, while a change to kafka_.events.events_bus can't break core.events.events.
- Position
- Below the diagonal: kafka_.events.events_bus uses a module listed above it, which is the healthy direction.
38→28 kafka_.events.events_bus uses core.events.events_bus✕
- Connections
- 2 pairs of types, where a type in kafka_.events.events_bus uses a type in core.events.events_bus.
- The types involved
assimilator.kafka_.events.events_bus.KafkaEventConsumer→assimilator.core.events.events_bus.EventConsumerassimilator.kafka_.events.events_bus.KafkaEventProducer→assimilator.core.events.events_bus.EventProducer
- Direction
- kafka_.events.events_bus uses core.events.events_bus, so a change to core.events.events_bus can break kafka_.events.events_bus, while a change to kafka_.events.events_bus can't break core.events.events_bus.
- Position
- Below the diagonal: kafka_.events.events_bus uses a module listed above it, which is the healthy direction.
39→15 redis_.events.events_bus uses core.events.events✕
- Connections
- 1 pair of types, where a type in redis_.events.events_bus uses a type in core.events.events.
- The types involved
assimilator.redis_.events.events_bus.RedisEventProducer→assimilator.core.events.events.Event
- Direction
- redis_.events.events_bus uses core.events.events, so a change to core.events.events can break redis_.events.events_bus, while a change to redis_.events.events_bus can't break core.events.events.
- Position
- Below the diagonal: redis_.events.events_bus uses a module listed above it, which is the healthy direction.
39→28 redis_.events.events_bus uses core.events.events_bus✕
- Connections
- 2 pairs of types, where a type in redis_.events.events_bus uses a type in core.events.events_bus.
- The types involved
assimilator.redis_.events.events_bus.RedisEventConsumer→assimilator.core.events.events_bus.EventConsumerassimilator.redis_.events.events_bus.RedisEventProducer→assimilator.core.events.events_bus.EventProducer
- Direction
- redis_.events.events_bus uses core.events.events_bus, so a change to core.events.events_bus can break redis_.events.events_bus, while a change to redis_.events.events_bus can't break core.events.events_bus.
- Position
- Below the diagonal: redis_.events.events_bus uses a module listed above it, which is the healthy direction.
40→14 alchemy.events.outbox_relay uses core.database.unit_of_work✕
- Connections
- 1 pair of types, where a type in alchemy.events.outbox_relay uses a type in core.database.unit_of_work.
- The types involved
assimilator.alchemy.events.outbox_relay.AlchemyOutboxRelay→assimilator.core.database.unit_of_work.UnitOfWork
- Direction
- alchemy.events.outbox_relay uses core.database.unit_of_work, so a change to core.database.unit_of_work can break alchemy.events.outbox_relay, while a change to alchemy.events.outbox_relay can't break core.database.unit_of_work.
- Position
- Below the diagonal: alchemy.events.outbox_relay uses a module listed above it, which is the healthy direction.
40→28 alchemy.events.outbox_relay uses core.events.events_bus✕
- Connections
- 1 pair of types, where a type in alchemy.events.outbox_relay uses a type in core.events.events_bus.
- The types involved
assimilator.alchemy.events.outbox_relay.AlchemyOutboxRelay→assimilator.core.events.events_bus.EventProducer
- Direction
- alchemy.events.outbox_relay uses core.events.events_bus, so a change to core.events.events_bus can break alchemy.events.outbox_relay, while a change to alchemy.events.outbox_relay can't break core.events.events_bus.
- Position
- Below the diagonal: alchemy.events.outbox_relay uses a module listed above it, which is the healthy direction.
40→35 alchemy.events.outbox_relay uses core.events.outbox_relay✕
- Connections
- 1 pair of types, where a type in alchemy.events.outbox_relay uses a type in core.events.outbox_relay.
- The types involved
assimilator.alchemy.events.outbox_relay.AlchemyOutboxRelay→assimilator.core.events.outbox_relay.OutboxRelay
- Direction
- alchemy.events.outbox_relay uses core.events.outbox_relay, so a change to core.events.outbox_relay can break alchemy.events.outbox_relay, while a change to alchemy.events.outbox_relay can't break core.events.outbox_relay.
- Position
- Below the diagonal: alchemy.events.outbox_relay 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 6 | High / Critical |
Roadmap
Top priorities: Resolve the 12 Orphaned file finding(s) in Knowledge Freshness — start with repository.py (5), specifications.py (2), models.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; Replace SQLAlchemy create_all() with Alembic (`alembic revision --autogenerate` + `alembic upgrade head`) so the production schema can evolve safely and reproducibly.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 12 Orphaned file finding(s) in Knowledge Freshness — start with repository.py (5), specifications.py (2), models.py. | +12.2 pts | Medium | 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. | +6.8 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.8 pts | Low | Knowledge Freshness |
| Replace SQLAlchemy create_all() with Alembic (`alembic revision --autogenerate` + `alembic upgrade head`) so the production schema can evolve safely and reproducibly. | +3.4 pts | Medium | Schema migrations |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.7 pts | Medium | Documentation (README) |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.1 pts | Medium | Release Hygiene |
| Resolve the 1 Scattered collaborators finding(s) in Navigability. | +1.0 pts | Low | Navigability |
| The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it. | +1.0 pts | Medium | Code composition |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| assimilator/alchemy/database/specifications/specifications.py | 8.5 | Near-clean | Cognitive Complexity: specifications.alchemy_only (cognitive 16) |
| assimilator/alchemy/database/repository.py | 8.5 | Near-clean | Change Coupling: Change coupling: repository.py ↔ repository.py |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 49 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 — 49 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, 27 of 33 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ 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.
- D12 Dependency Hygiene — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's 1 shipped Python distribution(s) across 1 manifest(s) WERE read; what went unanswered is the currency half, because it grades an EXACT pin against the newest release and every declaration here is a floor or a range — which installs the newest release it admits and so cannot be behind one. So pypi.org was never asked. This is a true statement about the repository, and the healthy one, NOT a gap on our side: no reader we could write would find a currency question here.
- 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 131 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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.
- X4 Structured logging — 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, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was specifications.alchemy_only at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with specifications.alchemy_only (cognitive 16). — Refactoring it lifts Cognitive Complexity from 9.9 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D6 · Cohesion (LCOM4)
0 of 25 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 5 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 1 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (4 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 3335 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 25 document(s) read across 1 unit(s).
D27 · Navigability
80 % of calls cross a namespace and 0 % go through an interface, but 43 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 4 high, 2 medium, 0 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `docs/docs_theme/base.html` (lines 1–4) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
12 of 12 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is assimilator/redis_/database/repository.py. Counted over 12 of the 76 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 12 Orphaned file finding(s) in Knowledge Freshness — start with repository.py (5), specifications.py (2), models.py. — One of this dimension's main actionable groups (12 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
Strongest change-coupling: repository.py↔repository.py 69%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with repository.py. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P10 · Library API & versioning
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.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
- SQLAlchemy create_all() builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Alembic (`alembic revision --autogenerate` + `alembic upgrade head`), so every schema change is a versioned file applied the same way in every environment. (×4) — examples/simplest_example.py:33, examples/simple_database/models.py:24, examples/fastapi_crud_example/models.py:77, …
What to do
- Replace SQLAlchemy create_all() with Alembic (`alembic revision --autogenerate` + `alembic upgrade head`) so the production schema can evolve safely and reproducibly.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `dict_to_internal_models` is public and takes `data: dict` from its caller, and it calls itself at line 25 (`dict_to_internal_models`) with a piece of `data` — and nowhere in `dict_to_internal_models` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `dict_to_internal_models` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — assimilator/internal/database/models_utils.py:25
- `dict_to_alchemy_models` is public and takes `data: dict` from its caller, and it calls itself at line 26 (`dict_to_alchemy_models`) with a piece of `data` (and at line 35) — and nowhere in `dict_to_alchemy_models` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `dict_to_alchemy_models` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — assimilator/alchemy/database/model_utils.py:26
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
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
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 100% | Exemplary | Strongest area. |
| Architecture | 90% | Exemplary | Solid. |
| Maturity | 50% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 98% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 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 — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 67 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — 1 markup document under demonstration, documentation or developer-tool trees (or modules the build marks non-production) but none in the product; no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — those pages are demos or docs for the code, not something this tier can boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~0 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
- D12 Dependency Hygiene — Dependency currency not established — no declaration carries an exact pin to grade
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, Python not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Python surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .py source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (3344 LoC, 140 module-visible types across 25 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- 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.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet).
- D5 Coupling — Not applicable — this Python build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- 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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 11 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 25 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (path 2); M4 checks only links and versions and artefact counts.
- 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'.
- P2 Observability — This repository's Python source (1 module(s), 76 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — 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
- 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 — 4 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 11 finding(s)
- Schema created by SQLAlchemy create_all() (no migration path) examples/simplest_example.py:33
- Schema created by SQLAlchemy create_all() (no migration path) examples/simple_database/models.py:24
- Schema created by SQLAlchemy create_all() (no migration path) examples/fastapi_crud_example/models.py:77
- Schema created by SQLAlchemy create_all() (no migration path) examples/complex_database/models.py:65
- REDACTED
- REDACTED
- Recursive walk over a caller-supplied document has no depth cap assimilator/internal/database/models_utils.py:25
- Recursive walk over a caller-supplied document has no depth cap assimilator/alchemy/database/model_utils.py:26
- specifications.alchemy_only (cognitive 16) assimilator/alchemy/database/specifications/specifications.py:129
- Change coupling: repository.py ↔ repository.py assimilator/alchemy/database/repository.py:1
- REDACTED
Minor — 17 finding(s)
- Orphaned file assimilator/redis_/database/repository.py:1
- Orphaned file assimilator/core/database/repository.py:1
- Orphaned file assimilator/mongo/database/repository.py:1
- Orphaned file assimilator/alchemy/database/specifications/specifications.py:1
- Orphaned file assimilator/alchemy/database/repository.py:1
- Orphaned file assimilator/internal/database/repository.py:1
- Orphaned file assimilator/core/database/models.py:1
- Orphaned file assimilator/core/database/specifications/adaptive.py:1
- Orphaned file assimilator/internal/database/specifications/internal_operator.py:1
- Orphaned file assimilator/core/database/specifications/filtering_options.py:1
- Orphaned file assimilator/mongo/database/specifications/specifications.py:1
- Orphaned file assimilator/internal/database/specifications/filter_specifications.py:1
- Scattered collaborators
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No changelog
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — Python dependencies read, no exact pin to grade for currency
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9718807a07da4057bdb0009c918dbd9b/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-9718807a07da4057bdb0009c918dbd9b/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 . | 6 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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 | — |
| 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry) — not scanned yet). | 0 | — |