Executive summary
NicklasWallgren/go-template is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 51 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Domain Modelling, at 43, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 4 points. Protecting the business objects' state would lift Domain Modelling itself, worth about 5 points. Raising Domain Modelling to 65 would lift the score to about 56.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six known security holes in the packages the code depends on can be used by attackers, and five settings leave the servers or containers unsafe. Pinning each tool to an exact version, updating the vulnerable packages and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. Saving the change and the message together would take care of the place where data is saved and a message sent separately.
The product code is 3,453 lines, about €7,200 to rebuild.
If Domain Modelling rose from 43 to 65, the lowest score rated Strong, the score would rise from 51 to about 56.
Rebuild cost: about €7,200 · Estimate
| Cost to rebuild | €2,400 to €12,000, for 40 to 127 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 51. 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,453 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 com/NicklasWallgren/go-template | 2 com/NicklasWallgren/go-template/adapters/driven/env | 3 com/NicklasWallgren/go-template/adapters/driven/logger | 4 com/NicklasWallgren/go-template/adapters/driven/persistence/drivers | 5 com/NicklasWallgren/go-template/adapters/driven/persistence/errors | 6 com/NicklasWallgren/go-template/adapters/driven/persistence/models | 7 com/NicklasWallgren/go-template/adapters/driven/persistence/transaction | 8 com/NicklasWallgren/go-template/adapters/driven/pubsub | 9 com/NicklasWallgren/go-template/adapters/driver/api | 10 com/NicklasWallgren/go-template/adapters/driver/api/errors | 11 com/NicklasWallgren/go-template/adapters/driver/api/request | 12 com/NicklasWallgren/go-template/adapters/driver/api/request/types | 13 com/NicklasWallgren/go-template/adapters/driver/api/response | 14 com/NicklasWallgren/go-template/adapters/driver/api/users/response | 15 com/NicklasWallgren/go-template/domain/common | 16 com/NicklasWallgren/go-template/domain/users/models | 17 com/NicklasWallgren/go-template/domain/validation | 18 com/NicklasWallgren/go-template/adapters/driver/api/common | 19 com/NicklasWallgren/go-template/adapters/driver/api/converters | 20 com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers | 21 com/NicklasWallgren/go-template/config | 22 com/NicklasWallgren/go-template/domain/event | 23 com/NicklasWallgren/go-template/domain/users/entities | 24 com/NicklasWallgren/go-template/adapters/driven/persistence | 25 com/NicklasWallgren/go-template/adapters/driven/rabbitmq | 26 com/NicklasWallgren/go-template/adapters/driver/api/middlewares | 27 com/NicklasWallgren/go-template/adapters/driver/api/routes | 28 com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers | 29 com/NicklasWallgren/go-template/domain | 30 com/NicklasWallgren/go-template/domain/users/event | 31 com/NicklasWallgren/go-template/adapters/driven | 32 com/NicklasWallgren/go-template/adapters/driven/health/checker | 33 com/NicklasWallgren/go-template/adapters/driven/persistence/migration | 34 com/NicklasWallgren/go-template/adapters/driven/persistence/users | 35 com/NicklasWallgren/go-template/adapters/driven/health | 36 com/NicklasWallgren/go-template/adapters/driver/cmd | 37 com/NicklasWallgren/go-template/domain/users | 38 com/NicklasWallgren/go-template/adapters/driver/api/health | 39 com/NicklasWallgren/go-template/adapters/driver/api/users | 40 com/NicklasWallgren/go-template/bootstrap |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com/NicklasWallgren/go-template | ||||||||||||||||||||||||||||||||||||||||
| 2 com/NicklasWallgren/go-template/adapters/driven/env | ||||||||||||||||||||||||||||||||||||||||
| 3 com/NicklasWallgren/go-template/adapters/driven/logger | ||||||||||||||||||||||||||||||||||||||||
| 4 com/NicklasWallgren/go-template/adapters/driven/persistence/drivers | ||||||||||||||||||||||||||||||||||||||||
| 5 com/NicklasWallgren/go-template/adapters/driven/persistence/errors | ||||||||||||||||||||||||||||||||||||||||
| 6 com/NicklasWallgren/go-template/adapters/driven/persistence/models | ||||||||||||||||||||||||||||||||||||||||
| 7 com/NicklasWallgren/go-template/adapters/driven/persistence/transaction | ||||||||||||||||||||||||||||||||||||||||
| 8 com/NicklasWallgren/go-template/adapters/driven/pubsub | ||||||||||||||||||||||||||||||||||||||||
| 9 com/NicklasWallgren/go-template/adapters/driver/api | ||||||||||||||||||||||||||||||||||||||||
| 10 com/NicklasWallgren/go-template/adapters/driver/api/errors | ||||||||||||||||||||||||||||||||||||||||
| 11 com/NicklasWallgren/go-template/adapters/driver/api/request | ||||||||||||||||||||||||||||||||||||||||
| 12 com/NicklasWallgren/go-template/adapters/driver/api/request/types | ||||||||||||||||||||||||||||||||||||||||
| 13 com/NicklasWallgren/go-template/adapters/driver/api/response | ||||||||||||||||||||||||||||||||||||||||
| 14 com/NicklasWallgren/go-template/adapters/driver/api/users/response | ||||||||||||||||||||||||||||||||||||||||
| 15 com/NicklasWallgren/go-template/domain/common | ||||||||||||||||||||||||||||||||||||||||
| 16 com/NicklasWallgren/go-template/domain/users/models | ||||||||||||||||||||||||||||||||||||||||
| 17 com/NicklasWallgren/go-template/domain/validation | ||||||||||||||||||||||||||||||||||||||||
| 18 com/NicklasWallgren/go-template/adapters/driver/api/common | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 com/NicklasWallgren/go-template/adapters/driver/api/converters | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers | 8 | |||||||||||||||||||||||||||||||||||||||
| 21 com/NicklasWallgren/go-template/config | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 com/NicklasWallgren/go-template/domain/event | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 com/NicklasWallgren/go-template/domain/users/entities | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 com/NicklasWallgren/go-template/adapters/driven/persistence | 3 | 6 | 4 | |||||||||||||||||||||||||||||||||||||
| 25 com/NicklasWallgren/go-template/adapters/driven/rabbitmq | 3 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 26 com/NicklasWallgren/go-template/adapters/driver/api/middlewares | 3 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 27 com/NicklasWallgren/go-template/adapters/driver/api/routes | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 com/NicklasWallgren/go-template/domain | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 com/NicklasWallgren/go-template/domain/users/event | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 com/NicklasWallgren/go-template/adapters/driven | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 32 com/NicklasWallgren/go-template/adapters/driven/health/checker | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 com/NicklasWallgren/go-template/adapters/driven/persistence/migration | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 com/NicklasWallgren/go-template/adapters/driven/persistence/users | 6 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 com/NicklasWallgren/go-template/adapters/driven/health | 4 | |||||||||||||||||||||||||||||||||||||||
| 36 com/NicklasWallgren/go-template/adapters/driver/cmd | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 com/NicklasWallgren/go-template/domain/users | 2 | 6 | 2 | 5 | 2 | 3 | 7 | |||||||||||||||||||||||||||||||||
| 38 com/NicklasWallgren/go-template/adapters/driver/api/health | 2 | 1 | 2 | 1 | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||
| 39 com/NicklasWallgren/go-template/adapters/driver/api/users | 3 | 2 | 1 | 3 | 2 | 2 | 4 | 1 | 1 | 2 | 3 | |||||||||||||||||||||||||||||
| 40 com/NicklasWallgren/go-template/bootstrap | 2 | 1 |
18→3 com/NicklasWallgren/go-template/adapters/driver/api/common uses com/NicklasWallgren/go-template/adapters/driven/logger✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/common uses a type in com/NicklasWallgren/go-template/adapters/driven/logger.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/common.common→github.com/NicklasWallgren/go-template/adapters/driven/logger.Logger
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/common uses com/NicklasWallgren/go-template/adapters/driven/logger, so a change to com/NicklasWallgren/go-template/adapters/driven/logger can break com/NicklasWallgren/go-template/adapters/driver/api/common, while a change to com/NicklasWallgren/go-template/adapters/driver/api/common can't break com/NicklasWallgren/go-template/adapters/driven/logger.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/common uses a module listed above it, which is the healthy direction.
19→6 com/NicklasWallgren/go-template/adapters/driver/api/converters uses com/NicklasWallgren/go-template/adapters/driven/persistence/models✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/converters uses a type in com/NicklasWallgren/go-template/adapters/driven/persistence/models.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/converters.PageableResponseConverter→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Page
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/converters uses com/NicklasWallgren/go-template/adapters/driven/persistence/models, so a change to com/NicklasWallgren/go-template/adapters/driven/persistence/models can break com/NicklasWallgren/go-template/adapters/driver/api/converters, while a change to com/NicklasWallgren/go-template/adapters/driver/api/converters can't break com/NicklasWallgren/go-template/adapters/driven/persistence/models.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/converters uses a module listed above it, which is the healthy direction.
19→13 com/NicklasWallgren/go-template/adapters/driver/api/converters uses com/NicklasWallgren/go-template/adapters/driver/api/response✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/converters uses a type in com/NicklasWallgren/go-template/adapters/driver/api/response.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/converters.PageableResponseConverter→github.com/NicklasWallgren/go-template/adapters/driver/api/response.PageableResponse
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/converters uses com/NicklasWallgren/go-template/adapters/driver/api/response, so a change to com/NicklasWallgren/go-template/adapters/driver/api/response can break com/NicklasWallgren/go-template/adapters/driver/api/converters, while a change to com/NicklasWallgren/go-template/adapters/driver/api/converters can't break com/NicklasWallgren/go-template/adapters/driver/api/response.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/converters uses a module listed above it, which is the healthy direction.
20→13 com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers uses com/NicklasWallgren/go-template/adapters/driver/api/response✕
- Connections
- 8 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers uses a type in com/NicklasWallgren/go-template/adapters/driver/api/response.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.APIErrorTypeHandler→github.com/NicklasWallgren/go-template/adapters/driver/api/response.APIResponseEnvelopegithub.com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.DomainErrorTypeHandler→github.com/NicklasWallgren/go-template/adapters/driver/api/response.APIResponseEnvelopegithub.com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.ErrorResponseManager→github.com/NicklasWallgren/go-template/adapters/driver/api/response.APIResponseEnvelopegithub.com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.ErrorTypeResponseHandler→github.com/NicklasWallgren/go-template/adapters/driver/api/response.APIResponseEnvelopegithub.com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.ValidationErrorTypeHandler→github.com/NicklasWallgren/go-template/adapters/driver/api/response.APIResponseEnvelopegithub.com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.ValidationFieldErrorTypeHandler→github.com/NicklasWallgren/go-template/adapters/driver/api/response.APIResponseEnvelopegithub.com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.ValidationGoPlaygroundErrorHandler→github.com/NicklasWallgren/go-template/adapters/driver/api/response.APIResponseEnvelopegithub.com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.errorResponseManager→github.com/NicklasWallgren/go-template/adapters/driver/api/response.APIResponseEnvelope
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers uses com/NicklasWallgren/go-template/adapters/driver/api/response, so a change to com/NicklasWallgren/go-template/adapters/driver/api/response can break com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers, while a change to com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers can't break com/NicklasWallgren/go-template/adapters/driver/api/response.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers uses a module listed above it, which is the healthy direction.
21→2 com/NicklasWallgren/go-template/config uses com/NicklasWallgren/go-template/adapters/driven/env✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/config uses a type in com/NicklasWallgren/go-template/adapters/driven/env.
- The types involved
github.com/NicklasWallgren/go-template/config.config→github.com/NicklasWallgren/go-template/adapters/driven/env.Env
- Direction
- com/NicklasWallgren/go-template/config uses com/NicklasWallgren/go-template/adapters/driven/env, so a change to com/NicklasWallgren/go-template/adapters/driven/env can break com/NicklasWallgren/go-template/config, while a change to com/NicklasWallgren/go-template/config can't break com/NicklasWallgren/go-template/adapters/driven/env.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/config uses a module listed above it, which is the healthy direction.
22→8 com/NicklasWallgren/go-template/domain/event uses com/NicklasWallgren/go-template/adapters/driven/pubsub✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/domain/event uses a type in com/NicklasWallgren/go-template/adapters/driven/pubsub.
- The types involved
github.com/NicklasWallgren/go-template/domain/event.EntityEventListener→github.com/NicklasWallgren/go-template/adapters/driven/pubsub.AMQPPublishergithub.com/NicklasWallgren/go-template/domain/event.event→github.com/NicklasWallgren/go-template/adapters/driven/pubsub.AMQPPublisher
- Direction
- com/NicklasWallgren/go-template/domain/event uses com/NicklasWallgren/go-template/adapters/driven/pubsub, so a change to com/NicklasWallgren/go-template/adapters/driven/pubsub can break com/NicklasWallgren/go-template/domain/event, while a change to com/NicklasWallgren/go-template/domain/event can't break com/NicklasWallgren/go-template/adapters/driven/pubsub.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain/event uses a module listed above it, which is the healthy direction.
23→15 com/NicklasWallgren/go-template/domain/users/entities uses com/NicklasWallgren/go-template/domain/common✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/domain/users/entities uses a type in com/NicklasWallgren/go-template/domain/common.
- The types involved
github.com/NicklasWallgren/go-template/domain/users/entities.entities→github.com/NicklasWallgren/go-template/domain/common.PrimaryID
- Direction
- com/NicklasWallgren/go-template/domain/users/entities uses com/NicklasWallgren/go-template/domain/common, so a change to com/NicklasWallgren/go-template/domain/common can break com/NicklasWallgren/go-template/domain/users/entities, while a change to com/NicklasWallgren/go-template/domain/users/entities can't break com/NicklasWallgren/go-template/domain/common.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain/users/entities uses a module listed above it, which is the healthy direction.
24→3 com/NicklasWallgren/go-template/adapters/driven/persistence uses com/NicklasWallgren/go-template/adapters/driven/logger✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/persistence uses a type in com/NicklasWallgren/go-template/adapters/driven/logger.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/persistence.entityRepository→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/adapters/driven/persistence.persistence→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/adapters/driven/persistence.repository→github.com/NicklasWallgren/go-template/adapters/driven/logger.Logger
- Direction
- com/NicklasWallgren/go-template/adapters/driven/persistence uses com/NicklasWallgren/go-template/adapters/driven/logger, so a change to com/NicklasWallgren/go-template/adapters/driven/logger can break com/NicklasWallgren/go-template/adapters/driven/persistence, while a change to com/NicklasWallgren/go-template/adapters/driven/persistence can't break com/NicklasWallgren/go-template/adapters/driven/logger.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/persistence uses a module listed above it, which is the healthy direction.
24→6 com/NicklasWallgren/go-template/adapters/driven/persistence uses com/NicklasWallgren/go-template/adapters/driven/persistence/models✕
- Connections
- 6 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/persistence uses a type in com/NicklasWallgren/go-template/adapters/driven/persistence/models.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/persistence.EntityRepository→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Pagegithub.com/NicklasWallgren/go-template/adapters/driven/persistence.EntityRepository→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Paginationgithub.com/NicklasWallgren/go-template/adapters/driven/persistence.entityRepository→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Pagegithub.com/NicklasWallgren/go-template/adapters/driven/persistence.entityRepository→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Paginationgithub.com/NicklasWallgren/go-template/adapters/driven/persistence.persistence→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.CriteriaAndPaginationgithub.com/NicklasWallgren/go-template/adapters/driven/persistence.persistence→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Page
- Direction
- com/NicklasWallgren/go-template/adapters/driven/persistence uses com/NicklasWallgren/go-template/adapters/driven/persistence/models, so a change to com/NicklasWallgren/go-template/adapters/driven/persistence/models can break com/NicklasWallgren/go-template/adapters/driven/persistence, while a change to com/NicklasWallgren/go-template/adapters/driven/persistence can't break com/NicklasWallgren/go-template/adapters/driven/persistence/models.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/persistence uses a module listed above it, which is the healthy direction.
24→21 com/NicklasWallgren/go-template/adapters/driven/persistence uses com/NicklasWallgren/go-template/config✕
- Connections
- 4 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/persistence uses a type in com/NicklasWallgren/go-template/config.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/persistence.entityRepository→github.com/NicklasWallgren/go-template/config.AppConfiggithub.com/NicklasWallgren/go-template/adapters/driven/persistence.persistence→github.com/NicklasWallgren/go-template/config.AppConfiggithub.com/NicklasWallgren/go-template/adapters/driven/persistence.persistence→github.com/NicklasWallgren/go-template/config.DatabaseConfiggithub.com/NicklasWallgren/go-template/adapters/driven/persistence.repository→github.com/NicklasWallgren/go-template/config.AppConfig
- Direction
- com/NicklasWallgren/go-template/adapters/driven/persistence uses com/NicklasWallgren/go-template/config, so a change to com/NicklasWallgren/go-template/config can break com/NicklasWallgren/go-template/adapters/driven/persistence, while a change to com/NicklasWallgren/go-template/adapters/driven/persistence can't break com/NicklasWallgren/go-template/config.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/persistence uses a module listed above it, which is the healthy direction.
25→3 com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses com/NicklasWallgren/go-template/adapters/driven/logger✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses a type in com/NicklasWallgren/go-template/adapters/driven/logger.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/rabbitmq.RabbitMQConsumer→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/adapters/driven/rabbitmq.RabbitMQPublisher→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/adapters/driven/rabbitmq.rabbitmq→github.com/NicklasWallgren/go-template/adapters/driven/logger.Logger
- Direction
- com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses com/NicklasWallgren/go-template/adapters/driven/logger, so a change to com/NicklasWallgren/go-template/adapters/driven/logger can break com/NicklasWallgren/go-template/adapters/driven/rabbitmq, while a change to com/NicklasWallgren/go-template/adapters/driven/rabbitmq can't break com/NicklasWallgren/go-template/adapters/driven/logger.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses a module listed above it, which is the healthy direction.
25→8 com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses com/NicklasWallgren/go-template/adapters/driven/pubsub✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses a type in com/NicklasWallgren/go-template/adapters/driven/pubsub.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/rabbitmq.RabbitMQPublisher→github.com/NicklasWallgren/go-template/adapters/driven/pubsub.AMQPPublishergithub.com/NicklasWallgren/go-template/adapters/driven/rabbitmq.rabbitmq→github.com/NicklasWallgren/go-template/adapters/driven/pubsub.AMQPPublisher
- Direction
- com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses com/NicklasWallgren/go-template/adapters/driven/pubsub, so a change to com/NicklasWallgren/go-template/adapters/driven/pubsub can break com/NicklasWallgren/go-template/adapters/driven/rabbitmq, while a change to com/NicklasWallgren/go-template/adapters/driven/rabbitmq can't break com/NicklasWallgren/go-template/adapters/driven/pubsub.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses a module listed above it, which is the healthy direction.
25→21 com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses com/NicklasWallgren/go-template/config✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses a type in com/NicklasWallgren/go-template/config.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/rabbitmq.RabbitMQConsumer→github.com/NicklasWallgren/go-template/config.AppConfiggithub.com/NicklasWallgren/go-template/adapters/driven/rabbitmq.RabbitMQPublisher→github.com/NicklasWallgren/go-template/config.RabbitMQConfiggithub.com/NicklasWallgren/go-template/adapters/driven/rabbitmq.rabbitmq→github.com/NicklasWallgren/go-template/config.AppConfig
- Direction
- com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses com/NicklasWallgren/go-template/config, so a change to com/NicklasWallgren/go-template/config can break com/NicklasWallgren/go-template/adapters/driven/rabbitmq, while a change to com/NicklasWallgren/go-template/adapters/driven/rabbitmq can't break com/NicklasWallgren/go-template/config.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/rabbitmq uses a module listed above it, which is the healthy direction.
26→2 com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses com/NicklasWallgren/go-template/adapters/driven/env✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses a type in com/NicklasWallgren/go-template/adapters/driven/env.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/middlewares.CorsMiddleware→github.com/NicklasWallgren/go-template/adapters/driven/env.Envgithub.com/NicklasWallgren/go-template/adapters/driver/api/middlewares.ObservabilityMiddleware→github.com/NicklasWallgren/go-template/adapters/driven/env.Envgithub.com/NicklasWallgren/go-template/adapters/driver/api/middlewares.middlewares→github.com/NicklasWallgren/go-template/adapters/driven/env.Env
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses com/NicklasWallgren/go-template/adapters/driven/env, so a change to com/NicklasWallgren/go-template/adapters/driven/env can break com/NicklasWallgren/go-template/adapters/driver/api/middlewares, while a change to com/NicklasWallgren/go-template/adapters/driver/api/middlewares can't break com/NicklasWallgren/go-template/adapters/driven/env.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses a module listed above it, which is the healthy direction.
26→3 com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses com/NicklasWallgren/go-template/adapters/driven/logger✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses a type in com/NicklasWallgren/go-template/adapters/driven/logger.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/middlewares.CorsMiddleware→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/adapters/driver/api/middlewares.ObservabilityMiddleware→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/adapters/driver/api/middlewares.middlewares→github.com/NicklasWallgren/go-template/adapters/driven/logger.Logger
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses com/NicklasWallgren/go-template/adapters/driven/logger, so a change to com/NicklasWallgren/go-template/adapters/driven/logger can break com/NicklasWallgren/go-template/adapters/driver/api/middlewares, while a change to com/NicklasWallgren/go-template/adapters/driver/api/middlewares can't break com/NicklasWallgren/go-template/adapters/driven/logger.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses a module listed above it, which is the healthy direction.
26→18 com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses com/NicklasWallgren/go-template/adapters/driver/api/common✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses a type in com/NicklasWallgren/go-template/adapters/driver/api/common.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/middlewares.CorsMiddleware→github.com/NicklasWallgren/go-template/adapters/driver/api/common.RequestHandlergithub.com/NicklasWallgren/go-template/adapters/driver/api/middlewares.ObservabilityMiddleware→github.com/NicklasWallgren/go-template/adapters/driver/api/common.RequestHandlergithub.com/NicklasWallgren/go-template/adapters/driver/api/middlewares.middlewares→github.com/NicklasWallgren/go-template/adapters/driver/api/common.RequestHandler
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses com/NicklasWallgren/go-template/adapters/driver/api/common, so a change to com/NicklasWallgren/go-template/adapters/driver/api/common can break com/NicklasWallgren/go-template/adapters/driver/api/middlewares, while a change to com/NicklasWallgren/go-template/adapters/driver/api/middlewares can't break com/NicklasWallgren/go-template/adapters/driver/api/common.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/middlewares uses a module listed above it, which is the healthy direction.
27→18 com/NicklasWallgren/go-template/adapters/driver/api/routes uses com/NicklasWallgren/go-template/adapters/driver/api/common✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/routes uses a type in com/NicklasWallgren/go-template/adapters/driver/api/common.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/routes.SwaggerRoutes→github.com/NicklasWallgren/go-template/adapters/driver/api/common.RequestHandlergithub.com/NicklasWallgren/go-template/adapters/driver/api/routes.routes→github.com/NicklasWallgren/go-template/adapters/driver/api/common.RequestHandler
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/routes uses com/NicklasWallgren/go-template/adapters/driver/api/common, so a change to com/NicklasWallgren/go-template/adapters/driver/api/common can break com/NicklasWallgren/go-template/adapters/driver/api/routes, while a change to com/NicklasWallgren/go-template/adapters/driver/api/routes can't break com/NicklasWallgren/go-template/adapters/driver/api/common.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/routes uses a module listed above it, which is the healthy direction.
28→20 com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers uses com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers uses a type in com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers.RootRouteHandler→github.com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.ErrorResponseManagergithub.com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers.handlers→github.com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.ErrorResponseManager
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers uses com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers, so a change to com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers can break com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers, while a change to com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers can't break com/NicklasWallgren/go-template/adapters/driver/api/errors/handlers.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers uses a module listed above it, which is the healthy direction.
29→22 com/NicklasWallgren/go-template/domain uses com/NicklasWallgren/go-template/domain/event✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/domain uses a type in com/NicklasWallgren/go-template/domain/event.
- The types involved
github.com/NicklasWallgren/go-template/domain.domain→github.com/NicklasWallgren/go-template/domain/event.Dispatchergithub.com/NicklasWallgren/go-template/domain.domain→github.com/NicklasWallgren/go-template/domain/event.EntityEventListener
- Direction
- com/NicklasWallgren/go-template/domain uses com/NicklasWallgren/go-template/domain/event, so a change to com/NicklasWallgren/go-template/domain/event can break com/NicklasWallgren/go-template/domain, while a change to com/NicklasWallgren/go-template/domain can't break com/NicklasWallgren/go-template/domain/event.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain uses a module listed above it, which is the healthy direction.
30→23 com/NicklasWallgren/go-template/domain/users/event uses com/NicklasWallgren/go-template/domain/users/entities✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/domain/users/event uses a type in com/NicklasWallgren/go-template/domain/users/entities.
- The types involved
github.com/NicklasWallgren/go-template/domain/users/event.event→github.com/NicklasWallgren/go-template/domain/users/entities.User
- Direction
- com/NicklasWallgren/go-template/domain/users/event uses com/NicklasWallgren/go-template/domain/users/entities, so a change to com/NicklasWallgren/go-template/domain/users/entities can break com/NicklasWallgren/go-template/domain/users/event, while a change to com/NicklasWallgren/go-template/domain/users/event can't break com/NicklasWallgren/go-template/domain/users/entities.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain/users/event uses a module listed above it, which is the healthy direction.
31→3 com/NicklasWallgren/go-template/adapters/driven uses com/NicklasWallgren/go-template/adapters/driven/logger✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driven uses a type in com/NicklasWallgren/go-template/adapters/driven/logger.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven.driven→github.com/NicklasWallgren/go-template/adapters/driven/logger.Logger
- Direction
- com/NicklasWallgren/go-template/adapters/driven uses com/NicklasWallgren/go-template/adapters/driven/logger, so a change to com/NicklasWallgren/go-template/adapters/driven/logger can break com/NicklasWallgren/go-template/adapters/driven, while a change to com/NicklasWallgren/go-template/adapters/driven can't break com/NicklasWallgren/go-template/adapters/driven/logger.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven uses a module listed above it, which is the healthy direction.
31→21 com/NicklasWallgren/go-template/adapters/driven uses com/NicklasWallgren/go-template/config✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driven uses a type in com/NicklasWallgren/go-template/config.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven.driven→github.com/NicklasWallgren/go-template/config.AppConfig
- Direction
- com/NicklasWallgren/go-template/adapters/driven uses com/NicklasWallgren/go-template/config, so a change to com/NicklasWallgren/go-template/config can break com/NicklasWallgren/go-template/adapters/driven, while a change to com/NicklasWallgren/go-template/adapters/driven can't break com/NicklasWallgren/go-template/config.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven uses a module listed above it, which is the healthy direction.
31→23 com/NicklasWallgren/go-template/adapters/driven uses com/NicklasWallgren/go-template/domain/users/entities✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driven uses a type in com/NicklasWallgren/go-template/domain/users/entities.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven.driven→github.com/NicklasWallgren/go-template/domain/users/entities.User
- Direction
- com/NicklasWallgren/go-template/adapters/driven uses com/NicklasWallgren/go-template/domain/users/entities, so a change to com/NicklasWallgren/go-template/domain/users/entities can break com/NicklasWallgren/go-template/adapters/driven, while a change to com/NicklasWallgren/go-template/adapters/driven can't break com/NicklasWallgren/go-template/domain/users/entities.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven uses a module listed above it, which is the healthy direction.
31→24 com/NicklasWallgren/go-template/adapters/driven uses com/NicklasWallgren/go-template/adapters/driven/persistence✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven uses a type in com/NicklasWallgren/go-template/adapters/driven/persistence.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven.driven→github.com/NicklasWallgren/go-template/adapters/driven/persistence.Databasegithub.com/NicklasWallgren/go-template/adapters/driven.driven→github.com/NicklasWallgren/go-template/adapters/driven/persistence.EntityRepository
- Direction
- com/NicklasWallgren/go-template/adapters/driven uses com/NicklasWallgren/go-template/adapters/driven/persistence, so a change to com/NicklasWallgren/go-template/adapters/driven/persistence can break com/NicklasWallgren/go-template/adapters/driven, while a change to com/NicklasWallgren/go-template/adapters/driven can't break com/NicklasWallgren/go-template/adapters/driven/persistence.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven uses a module listed above it, which is the healthy direction.
32→3 com/NicklasWallgren/go-template/adapters/driven/health/checker uses com/NicklasWallgren/go-template/adapters/driven/logger✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/health/checker uses a type in com/NicklasWallgren/go-template/adapters/driven/logger.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/health/checker.DBHealthChecker→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/adapters/driven/health/checker.checker→github.com/NicklasWallgren/go-template/adapters/driven/logger.Logger
- Direction
- com/NicklasWallgren/go-template/adapters/driven/health/checker uses com/NicklasWallgren/go-template/adapters/driven/logger, so a change to com/NicklasWallgren/go-template/adapters/driven/logger can break com/NicklasWallgren/go-template/adapters/driven/health/checker, while a change to com/NicklasWallgren/go-template/adapters/driven/health/checker can't break com/NicklasWallgren/go-template/adapters/driven/logger.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/health/checker uses a module listed above it, which is the healthy direction.
32→24 com/NicklasWallgren/go-template/adapters/driven/health/checker uses com/NicklasWallgren/go-template/adapters/driven/persistence✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/health/checker uses a type in com/NicklasWallgren/go-template/adapters/driven/persistence.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/health/checker.DBHealthChecker→github.com/NicklasWallgren/go-template/adapters/driven/persistence.Repositorygithub.com/NicklasWallgren/go-template/adapters/driven/health/checker.checker→github.com/NicklasWallgren/go-template/adapters/driven/persistence.Repository
- Direction
- com/NicklasWallgren/go-template/adapters/driven/health/checker uses com/NicklasWallgren/go-template/adapters/driven/persistence, so a change to com/NicklasWallgren/go-template/adapters/driven/persistence can break com/NicklasWallgren/go-template/adapters/driven/health/checker, while a change to com/NicklasWallgren/go-template/adapters/driven/health/checker can't break com/NicklasWallgren/go-template/adapters/driven/persistence.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/health/checker uses a module listed above it, which is the healthy direction.
33→21 com/NicklasWallgren/go-template/adapters/driven/persistence/migration uses com/NicklasWallgren/go-template/config✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driven/persistence/migration uses a type in com/NicklasWallgren/go-template/config.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/persistence/migration.migration→github.com/NicklasWallgren/go-template/config.AppConfig
- Direction
- com/NicklasWallgren/go-template/adapters/driven/persistence/migration uses com/NicklasWallgren/go-template/config, so a change to com/NicklasWallgren/go-template/config can break com/NicklasWallgren/go-template/adapters/driven/persistence/migration, while a change to com/NicklasWallgren/go-template/adapters/driven/persistence/migration can't break com/NicklasWallgren/go-template/config.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/persistence/migration uses a module listed above it, which is the healthy direction.
33→24 com/NicklasWallgren/go-template/adapters/driven/persistence/migration uses com/NicklasWallgren/go-template/adapters/driven/persistence✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/persistence/migration uses a type in com/NicklasWallgren/go-template/adapters/driven/persistence.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/persistence/migration.GooseMigrator→github.com/NicklasWallgren/go-template/adapters/driven/persistence.Databasegithub.com/NicklasWallgren/go-template/adapters/driven/persistence/migration.migration→github.com/NicklasWallgren/go-template/adapters/driven/persistence.Database
- Direction
- com/NicklasWallgren/go-template/adapters/driven/persistence/migration uses com/NicklasWallgren/go-template/adapters/driven/persistence, so a change to com/NicklasWallgren/go-template/adapters/driven/persistence can break com/NicklasWallgren/go-template/adapters/driven/persistence/migration, while a change to com/NicklasWallgren/go-template/adapters/driven/persistence/migration can't break com/NicklasWallgren/go-template/adapters/driven/persistence.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/persistence/migration uses a module listed above it, which is the healthy direction.
34→6 com/NicklasWallgren/go-template/adapters/driven/persistence/users uses com/NicklasWallgren/go-template/adapters/driven/persistence/models✕
- Connections
- 6 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/persistence/users uses a type in com/NicklasWallgren/go-template/adapters/driven/persistence/models.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.UserRepository→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.CriteriaAndPaginationgithub.com/NicklasWallgren/go-template/adapters/driven/persistence/users.UserRepository→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Pagegithub.com/NicklasWallgren/go-template/adapters/driven/persistence/users.UserRepository→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Paginationgithub.com/NicklasWallgren/go-template/adapters/driven/persistence/users.userRepository→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.CriteriaAndPaginationgithub.com/NicklasWallgren/go-template/adapters/driven/persistence/users.userRepository→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Pagegithub.com/NicklasWallgren/go-template/adapters/driven/persistence/users.userRepository→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Pagination
- Direction
- com/NicklasWallgren/go-template/adapters/driven/persistence/users uses com/NicklasWallgren/go-template/adapters/driven/persistence/models, so a change to com/NicklasWallgren/go-template/adapters/driven/persistence/models can break com/NicklasWallgren/go-template/adapters/driven/persistence/users, while a change to com/NicklasWallgren/go-template/adapters/driven/persistence/users can't break com/NicklasWallgren/go-template/adapters/driven/persistence/models.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/persistence/users uses a module listed above it, which is the healthy direction.
34→16 com/NicklasWallgren/go-template/adapters/driven/persistence/users uses com/NicklasWallgren/go-template/domain/users/models✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/persistence/users uses a type in com/NicklasWallgren/go-template/domain/users/models.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.UserRepository→github.com/NicklasWallgren/go-template/domain/users/models.SenderOverviewgithub.com/NicklasWallgren/go-template/adapters/driven/persistence/users.userRepository→github.com/NicklasWallgren/go-template/domain/users/models.SenderOverview
- Direction
- com/NicklasWallgren/go-template/adapters/driven/persistence/users uses com/NicklasWallgren/go-template/domain/users/models, so a change to com/NicklasWallgren/go-template/domain/users/models can break com/NicklasWallgren/go-template/adapters/driven/persistence/users, while a change to com/NicklasWallgren/go-template/adapters/driven/persistence/users can't break com/NicklasWallgren/go-template/domain/users/models.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/persistence/users uses a module listed above it, which is the healthy direction.
34→23 com/NicklasWallgren/go-template/adapters/driven/persistence/users uses com/NicklasWallgren/go-template/domain/users/entities✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/persistence/users uses a type in com/NicklasWallgren/go-template/domain/users/entities.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.UserRepository→github.com/NicklasWallgren/go-template/domain/users/entities.Usergithub.com/NicklasWallgren/go-template/adapters/driven/persistence/users.userRepository→github.com/NicklasWallgren/go-template/domain/users/entities.Usergithub.com/NicklasWallgren/go-template/adapters/driven/persistence/users.users→github.com/NicklasWallgren/go-template/domain/users/entities.User
- Direction
- com/NicklasWallgren/go-template/adapters/driven/persistence/users uses com/NicklasWallgren/go-template/domain/users/entities, so a change to com/NicklasWallgren/go-template/domain/users/entities can break com/NicklasWallgren/go-template/adapters/driven/persistence/users, while a change to com/NicklasWallgren/go-template/adapters/driven/persistence/users can't break com/NicklasWallgren/go-template/domain/users/entities.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/persistence/users uses a module listed above it, which is the healthy direction.
34→24 com/NicklasWallgren/go-template/adapters/driven/persistence/users uses com/NicklasWallgren/go-template/adapters/driven/persistence✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driven/persistence/users uses a type in com/NicklasWallgren/go-template/adapters/driven/persistence.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.users→github.com/NicklasWallgren/go-template/adapters/driven/persistence.EntityRepository
- Direction
- com/NicklasWallgren/go-template/adapters/driven/persistence/users uses com/NicklasWallgren/go-template/adapters/driven/persistence, so a change to com/NicklasWallgren/go-template/adapters/driven/persistence can break com/NicklasWallgren/go-template/adapters/driven/persistence/users, while a change to com/NicklasWallgren/go-template/adapters/driven/persistence/users can't break com/NicklasWallgren/go-template/adapters/driven/persistence.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/persistence/users uses a module listed above it, which is the healthy direction.
35→32 com/NicklasWallgren/go-template/adapters/driven/health uses com/NicklasWallgren/go-template/adapters/driven/health/checker✕
- Connections
- 4 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driven/health uses a type in com/NicklasWallgren/go-template/adapters/driven/health/checker.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driven/health.HealthCheckerManager→github.com/NicklasWallgren/go-template/adapters/driven/health/checker.HealthCheckergithub.com/NicklasWallgren/go-template/adapters/driven/health.HealthResult→github.com/NicklasWallgren/go-template/adapters/driven/health/checker.Healthgithub.com/NicklasWallgren/go-template/adapters/driven/health.HealthResult→github.com/NicklasWallgren/go-template/adapters/driven/health/checker.HealthStatusgithub.com/NicklasWallgren/go-template/adapters/driven/health.health→github.com/NicklasWallgren/go-template/adapters/driven/health/checker.HealthChecker
- Direction
- com/NicklasWallgren/go-template/adapters/driven/health uses com/NicklasWallgren/go-template/adapters/driven/health/checker, so a change to com/NicklasWallgren/go-template/adapters/driven/health/checker can break com/NicklasWallgren/go-template/adapters/driven/health, while a change to com/NicklasWallgren/go-template/adapters/driven/health can't break com/NicklasWallgren/go-template/adapters/driven/health/checker.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driven/health uses a module listed above it, which is the healthy direction.
36→21 com/NicklasWallgren/go-template/adapters/driver/cmd uses com/NicklasWallgren/go-template/config✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driver/cmd uses a type in com/NicklasWallgren/go-template/config.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/cmd.cmd→github.com/NicklasWallgren/go-template/config.AssetsConfig
- Direction
- com/NicklasWallgren/go-template/adapters/driver/cmd uses com/NicklasWallgren/go-template/config, so a change to com/NicklasWallgren/go-template/config can break com/NicklasWallgren/go-template/adapters/driver/cmd, while a change to com/NicklasWallgren/go-template/adapters/driver/cmd can't break com/NicklasWallgren/go-template/config.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/cmd uses a module listed above it, which is the healthy direction.
36→33 com/NicklasWallgren/go-template/adapters/driver/cmd uses com/NicklasWallgren/go-template/adapters/driven/persistence/migration✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driver/cmd uses a type in com/NicklasWallgren/go-template/adapters/driven/persistence/migration.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/cmd.cmd→github.com/NicklasWallgren/go-template/adapters/driven/persistence/migration.Migrator
- Direction
- com/NicklasWallgren/go-template/adapters/driver/cmd uses com/NicklasWallgren/go-template/adapters/driven/persistence/migration, so a change to com/NicklasWallgren/go-template/adapters/driven/persistence/migration can break com/NicklasWallgren/go-template/adapters/driver/cmd, while a change to com/NicklasWallgren/go-template/adapters/driver/cmd can't break com/NicklasWallgren/go-template/adapters/driven/persistence/migration.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/cmd uses a module listed above it, which is the healthy direction.
37→3 com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/adapters/driven/logger✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/domain/users uses a type in com/NicklasWallgren/go-template/adapters/driven/logger.
- The types involved
github.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/domain/users.users→github.com/NicklasWallgren/go-template/adapters/driven/logger.Logger
- Direction
- com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/adapters/driven/logger, so a change to com/NicklasWallgren/go-template/adapters/driven/logger can break com/NicklasWallgren/go-template/domain/users, while a change to com/NicklasWallgren/go-template/domain/users can't break com/NicklasWallgren/go-template/adapters/driven/logger.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain/users uses a module listed above it, which is the healthy direction.
37→6 com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/adapters/driven/persistence/models✕
- Connections
- 6 pairs of types, where a type in com/NicklasWallgren/go-template/domain/users uses a type in com/NicklasWallgren/go-template/adapters/driven/persistence/models.
- The types involved
github.com/NicklasWallgren/go-template/domain/users.UserService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.CriteriaAndPaginationgithub.com/NicklasWallgren/go-template/domain/users.UserService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Pagegithub.com/NicklasWallgren/go-template/domain/users.UserService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Paginationgithub.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.CriteriaAndPaginationgithub.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Pagegithub.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/models.Pagination
- Direction
- com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/adapters/driven/persistence/models, so a change to com/NicklasWallgren/go-template/adapters/driven/persistence/models can break com/NicklasWallgren/go-template/domain/users, while a change to com/NicklasWallgren/go-template/domain/users can't break com/NicklasWallgren/go-template/adapters/driven/persistence/models.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain/users uses a module listed above it, which is the healthy direction.
37→16 com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/domain/users/models✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/domain/users uses a type in com/NicklasWallgren/go-template/domain/users/models.
- The types involved
github.com/NicklasWallgren/go-template/domain/users.UserService→github.com/NicklasWallgren/go-template/domain/users/models.SenderOverviewgithub.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/domain/users/models.SenderOverview
- Direction
- com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/domain/users/models, so a change to com/NicklasWallgren/go-template/domain/users/models can break com/NicklasWallgren/go-template/domain/users, while a change to com/NicklasWallgren/go-template/domain/users can't break com/NicklasWallgren/go-template/domain/users/models.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain/users uses a module listed above it, which is the healthy direction.
37→17 com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/domain/validation✕
- Connections
- 5 pairs of types, where a type in com/NicklasWallgren/go-template/domain/users uses a type in com/NicklasWallgren/go-template/domain/validation.
- The types involved
github.com/NicklasWallgren/go-template/domain/users.UserValidator→github.com/NicklasWallgren/go-template/domain/validation.EntityCreationValidatorgithub.com/NicklasWallgren/go-template/domain/users.UserValidator→github.com/NicklasWallgren/go-template/domain/validation.EntityDeleteValidatorgithub.com/NicklasWallgren/go-template/domain/users.UserValidator→github.com/NicklasWallgren/go-template/domain/validation.EntityUpdateValidatorgithub.com/NicklasWallgren/go-template/domain/users.UserValidator→github.com/NicklasWallgren/go-template/domain/validation.EntityValidatorgithub.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/domain/validation.EntityValidator
- Direction
- com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/domain/validation, so a change to com/NicklasWallgren/go-template/domain/validation can break com/NicklasWallgren/go-template/domain/users, while a change to com/NicklasWallgren/go-template/domain/users can't break com/NicklasWallgren/go-template/domain/validation.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain/users uses a module listed above it, which is the healthy direction.
37→22 com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/domain/event✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/domain/users uses a type in com/NicklasWallgren/go-template/domain/event.
- The types involved
github.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/domain/event.Dispatchergithub.com/NicklasWallgren/go-template/domain/users.users→github.com/NicklasWallgren/go-template/domain/event.Dispatcher
- Direction
- com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/domain/event, so a change to com/NicklasWallgren/go-template/domain/event can break com/NicklasWallgren/go-template/domain/users, while a change to com/NicklasWallgren/go-template/domain/users can't break com/NicklasWallgren/go-template/domain/event.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain/users uses a module listed above it, which is the healthy direction.
37→23 com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/domain/users/entities✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/domain/users uses a type in com/NicklasWallgren/go-template/domain/users/entities.
- The types involved
github.com/NicklasWallgren/go-template/domain/users.UserService→github.com/NicklasWallgren/go-template/domain/users/entities.Usergithub.com/NicklasWallgren/go-template/domain/users.UserValidator→github.com/NicklasWallgren/go-template/domain/users/entities.Usergithub.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/domain/users/entities.User
- Direction
- com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/domain/users/entities, so a change to com/NicklasWallgren/go-template/domain/users/entities can break com/NicklasWallgren/go-template/domain/users, while a change to com/NicklasWallgren/go-template/domain/users can't break com/NicklasWallgren/go-template/domain/users/entities.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain/users uses a module listed above it, which is the healthy direction.
37→34 com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/adapters/driven/persistence/users✕
- Connections
- 7 pairs of types, where a type in com/NicklasWallgren/go-template/domain/users uses a type in com/NicklasWallgren/go-template/adapters/driven/persistence/users.
- The types involved
github.com/NicklasWallgren/go-template/domain/users.UserService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.FindAllCriteriagithub.com/NicklasWallgren/go-template/domain/users.UserService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.OverviewCriteriagithub.com/NicklasWallgren/go-template/domain/users.UserValidator→github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.UserRepositorygithub.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.FindAllCriteriagithub.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.OverviewCriteriagithub.com/NicklasWallgren/go-template/domain/users.userService→github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.UserRepositorygithub.com/NicklasWallgren/go-template/domain/users.users→github.com/NicklasWallgren/go-template/adapters/driven/persistence/users.UserRepository
- Direction
- com/NicklasWallgren/go-template/domain/users uses com/NicklasWallgren/go-template/adapters/driven/persistence/users, so a change to com/NicklasWallgren/go-template/adapters/driven/persistence/users can break com/NicklasWallgren/go-template/domain/users, while a change to com/NicklasWallgren/go-template/domain/users can't break com/NicklasWallgren/go-template/adapters/driven/persistence/users.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/domain/users uses a module listed above it, which is the healthy direction.
38→3 com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driven/logger✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/health uses a type in com/NicklasWallgren/go-template/adapters/driven/logger.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/health.HealthRoutes→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/adapters/driver/api/health.health→github.com/NicklasWallgren/go-template/adapters/driven/logger.Logger
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driven/logger, so a change to com/NicklasWallgren/go-template/adapters/driven/logger can break com/NicklasWallgren/go-template/adapters/driver/api/health, while a change to com/NicklasWallgren/go-template/adapters/driver/api/health can't break com/NicklasWallgren/go-template/adapters/driven/logger.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/health uses a module listed above it, which is the healthy direction.
38→13 com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driver/api/response✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/health uses a type in com/NicklasWallgren/go-template/adapters/driver/api/response.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/health.HealthController→github.com/NicklasWallgren/go-template/adapters/driver/api/response.APIResponseEnvelope
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driver/api/response, so a change to com/NicklasWallgren/go-template/adapters/driver/api/response can break com/NicklasWallgren/go-template/adapters/driver/api/health, while a change to com/NicklasWallgren/go-template/adapters/driver/api/health can't break com/NicklasWallgren/go-template/adapters/driver/api/response.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/health uses a module listed above it, which is the healthy direction.
38→18 com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driver/api/common✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/health uses a type in com/NicklasWallgren/go-template/adapters/driver/api/common.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/health.HealthRoutes→github.com/NicklasWallgren/go-template/adapters/driver/api/common.RequestHandlergithub.com/NicklasWallgren/go-template/adapters/driver/api/health.health→github.com/NicklasWallgren/go-template/adapters/driver/api/common.RequestHandler
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driver/api/common, so a change to com/NicklasWallgren/go-template/adapters/driver/api/common can break com/NicklasWallgren/go-template/adapters/driver/api/health, while a change to com/NicklasWallgren/go-template/adapters/driver/api/health can't break com/NicklasWallgren/go-template/adapters/driver/api/common.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/health uses a module listed above it, which is the healthy direction.
38→27 com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driver/api/routes✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/health uses a type in com/NicklasWallgren/go-template/adapters/driver/api/routes.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/health.health→github.com/NicklasWallgren/go-template/adapters/driver/api/routes.Route
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driver/api/routes, so a change to com/NicklasWallgren/go-template/adapters/driver/api/routes can break com/NicklasWallgren/go-template/adapters/driver/api/health, while a change to com/NicklasWallgren/go-template/adapters/driver/api/health can't break com/NicklasWallgren/go-template/adapters/driver/api/routes.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/health uses a module listed above it, which is the healthy direction.
38→28 com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/health uses a type in com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/health.HealthRoutes→github.com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers.RootRouteHandlergithub.com/NicklasWallgren/go-template/adapters/driver/api/health.health→github.com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers.RootRouteHandler
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers, so a change to com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers can break com/NicklasWallgren/go-template/adapters/driver/api/health, while a change to com/NicklasWallgren/go-template/adapters/driver/api/health can't break com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/health uses a module listed above it, which is the healthy direction.
38→32 com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driven/health/checker✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/health uses a type in com/NicklasWallgren/go-template/adapters/driven/health/checker.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/health.health→github.com/NicklasWallgren/go-template/adapters/driven/health/checker.Healthgithub.com/NicklasWallgren/go-template/adapters/driver/api/health.health→github.com/NicklasWallgren/go-template/adapters/driven/health/checker.HealthStatus
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driven/health/checker, so a change to com/NicklasWallgren/go-template/adapters/driven/health/checker can break com/NicklasWallgren/go-template/adapters/driver/api/health, while a change to com/NicklasWallgren/go-template/adapters/driver/api/health can't break com/NicklasWallgren/go-template/adapters/driven/health/checker.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/health uses a module listed above it, which is the healthy direction.
38→35 com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driven/health✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/health uses a type in com/NicklasWallgren/go-template/adapters/driven/health.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/health.HealthAPIConverter→github.com/NicklasWallgren/go-template/adapters/driven/health.HealthResultgithub.com/NicklasWallgren/go-template/adapters/driver/api/health.HealthController→github.com/NicklasWallgren/go-template/adapters/driven/health.HealthCheckerManagergithub.com/NicklasWallgren/go-template/adapters/driver/api/health.health→github.com/NicklasWallgren/go-template/adapters/driven/health.HealthCheckerManager
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/health uses com/NicklasWallgren/go-template/adapters/driven/health, so a change to com/NicklasWallgren/go-template/adapters/driven/health can break com/NicklasWallgren/go-template/adapters/driver/api/health, while a change to com/NicklasWallgren/go-template/adapters/driver/api/health can't break com/NicklasWallgren/go-template/adapters/driven/health.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/health uses a module listed above it, which is the healthy direction.
39→3 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driven/logger✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/adapters/driven/logger.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.UserController→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/adapters/driver/api/users.UserRoutes→github.com/NicklasWallgren/go-template/adapters/driven/logger.Loggergithub.com/NicklasWallgren/go-template/adapters/driver/api/users.users→github.com/NicklasWallgren/go-template/adapters/driven/logger.Logger
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driven/logger, so a change to com/NicklasWallgren/go-template/adapters/driven/logger can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/adapters/driven/logger.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
39→12 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/request/types✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/adapters/driver/api/request/types.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.CreateUserRequest→github.com/NicklasWallgren/go-template/adapters/driver/api/request/types.Dategithub.com/NicklasWallgren/go-template/adapters/driver/api/users.UpdateUserRequest→github.com/NicklasWallgren/go-template/adapters/driver/api/request/types.Date
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/request/types, so a change to com/NicklasWallgren/go-template/adapters/driver/api/request/types can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/adapters/driver/api/request/types.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
39→13 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/response✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/adapters/driver/api/response.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.UserController→github.com/NicklasWallgren/go-template/adapters/driver/api/response.APIResponseEnvelope
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/response, so a change to com/NicklasWallgren/go-template/adapters/driver/api/response can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/adapters/driver/api/response.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
39→14 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/users/response✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/adapters/driver/api/users/response.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.userAPIConverter→github.com/NicklasWallgren/go-template/adapters/driver/api/users/response.UserOverviewResponsegithub.com/NicklasWallgren/go-template/adapters/driver/api/users.userAPIConverter→github.com/NicklasWallgren/go-template/adapters/driver/api/users/response.UserResponsegithub.com/NicklasWallgren/go-template/adapters/driver/api/users.userOverviewAPIConverter→github.com/NicklasWallgren/go-template/adapters/driver/api/users/response.UserOverviewResponse
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/users/response, so a change to com/NicklasWallgren/go-template/adapters/driver/api/users/response can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/adapters/driver/api/users/response.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
39→16 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/domain/users/models✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/domain/users/models.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.userAPIConverter→github.com/NicklasWallgren/go-template/domain/users/models.SenderOverviewgithub.com/NicklasWallgren/go-template/adapters/driver/api/users.userOverviewAPIConverter→github.com/NicklasWallgren/go-template/domain/users/models.SenderOverview
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/domain/users/models, so a change to com/NicklasWallgren/go-template/domain/users/models can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/domain/users/models.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
39→18 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/common✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/adapters/driver/api/common.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.UserRoutes→github.com/NicklasWallgren/go-template/adapters/driver/api/common.RequestHandlergithub.com/NicklasWallgren/go-template/adapters/driver/api/users.users→github.com/NicklasWallgren/go-template/adapters/driver/api/common.RequestHandler
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/common, so a change to com/NicklasWallgren/go-template/adapters/driver/api/common can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/adapters/driver/api/common.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
39→19 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/converters✕
- Connections
- 4 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/adapters/driver/api/converters.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.UserAPIConverter→github.com/NicklasWallgren/go-template/adapters/driver/api/converters.APIRequestCreateConvertergithub.com/NicklasWallgren/go-template/adapters/driver/api/users.UserAPIConverter→github.com/NicklasWallgren/go-template/adapters/driver/api/converters.APIRequestUpdateConvertergithub.com/NicklasWallgren/go-template/adapters/driver/api/users.UserAPIConverter→github.com/NicklasWallgren/go-template/adapters/driver/api/converters.APIResponseConvertergithub.com/NicklasWallgren/go-template/adapters/driver/api/users.UserOverviewAPIConverter→github.com/NicklasWallgren/go-template/adapters/driver/api/converters.APIResponseConverter
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/converters, so a change to com/NicklasWallgren/go-template/adapters/driver/api/converters can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/adapters/driver/api/converters.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
39→23 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/domain/users/entities✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/domain/users/entities.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.userAPIConverter→github.com/NicklasWallgren/go-template/domain/users/entities.User
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/domain/users/entities, so a change to com/NicklasWallgren/go-template/domain/users/entities can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/domain/users/entities.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
39→27 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/routes✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/adapters/driver/api/routes.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.users→github.com/NicklasWallgren/go-template/adapters/driver/api/routes.Route
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/routes, so a change to com/NicklasWallgren/go-template/adapters/driver/api/routes can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/adapters/driver/api/routes.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
39→28 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.UserRoutes→github.com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers.RootRouteHandlergithub.com/NicklasWallgren/go-template/adapters/driver/api/users.users→github.com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers.RootRouteHandler
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers, so a change to com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/adapters/driver/api/routes/handlers.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
39→37 com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/domain/users✕
- Connections
- 3 pairs of types, where a type in com/NicklasWallgren/go-template/adapters/driver/api/users uses a type in com/NicklasWallgren/go-template/domain/users.
- The types involved
github.com/NicklasWallgren/go-template/adapters/driver/api/users.UserController→github.com/NicklasWallgren/go-template/domain/users.UserServicegithub.com/NicklasWallgren/go-template/adapters/driver/api/users.userAPIConverter→github.com/NicklasWallgren/go-template/domain/users.UserServicegithub.com/NicklasWallgren/go-template/adapters/driver/api/users.users→github.com/NicklasWallgren/go-template/domain/users.UserService
- Direction
- com/NicklasWallgren/go-template/adapters/driver/api/users uses com/NicklasWallgren/go-template/domain/users, so a change to com/NicklasWallgren/go-template/domain/users can break com/NicklasWallgren/go-template/adapters/driver/api/users, while a change to com/NicklasWallgren/go-template/adapters/driver/api/users can't break com/NicklasWallgren/go-template/domain/users.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/adapters/driver/api/users uses a module listed above it, which is the healthy direction.
40→21 com/NicklasWallgren/go-template/bootstrap uses com/NicklasWallgren/go-template/config✕
- Connections
- 2 pairs of types, where a type in com/NicklasWallgren/go-template/bootstrap uses a type in com/NicklasWallgren/go-template/config.
- The types involved
github.com/NicklasWallgren/go-template/bootstrap.App→github.com/NicklasWallgren/go-template/config.AssetsConfiggithub.com/NicklasWallgren/go-template/bootstrap.bootstrap→github.com/NicklasWallgren/go-template/config.AssetsConfig
- Direction
- com/NicklasWallgren/go-template/bootstrap uses com/NicklasWallgren/go-template/config, so a change to com/NicklasWallgren/go-template/config can break com/NicklasWallgren/go-template/bootstrap, while a change to com/NicklasWallgren/go-template/bootstrap can't break com/NicklasWallgren/go-template/config.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/bootstrap uses a module listed above it, which is the healthy direction.
40→36 com/NicklasWallgren/go-template/bootstrap uses com/NicklasWallgren/go-template/adapters/driver/cmd✕
- Connections
- 1 pair of types, where a type in com/NicklasWallgren/go-template/bootstrap uses a type in com/NicklasWallgren/go-template/adapters/driver/cmd.
- The types involved
github.com/NicklasWallgren/go-template/bootstrap.App→github.com/NicklasWallgren/go-template/adapters/driver/cmd.CommandRunner
- Direction
- com/NicklasWallgren/go-template/bootstrap uses com/NicklasWallgren/go-template/adapters/driver/cmd, so a change to com/NicklasWallgren/go-template/adapters/driver/cmd can break com/NicklasWallgren/go-template/bootstrap, while a change to com/NicklasWallgren/go-template/bootstrap can't break com/NicklasWallgren/go-template/adapters/driver/cmd.
- Position
- Below the diagonal: com/NicklasWallgren/go-template/bootstrap uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 97 | High / Critical |
| A05:2025 — Injection | 22 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 11 | High / Critical |
Roadmap
Top priorities: Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters); Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.8 pts | Low | ADR Quality |
| Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with transaction.go, user_controller.go, user_service.go. | +3.8 pts | Low | Knowledge Freshness |
| Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters). | +5.1 pts | Medium | Encapsulated state |
| Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services. | +4.0 pts | Medium | Rich vs anemic model |
| Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed. | +3.7 pts | Medium | Repository granularity |
| Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. | +1.5 pts | Low | Dependency Hygiene |
| 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. | +2.8 pts | Medium | Architecture documentation |
| Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion). | +2.6 pts | Medium | Domain ↔ infrastructure boundary |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| adapters/driven/persistence/entity_repository.go | 6.3 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| adapters/driven/rabbitmq/publisher.go | 6.5 | Mixed | Explicit Debt: TodoComment |
| adapters/driver/cmd/migrate.go | 6.6 | Mixed | Explicit Debt: TodoComment |
| adapters/driven/persistence/migration/goose_migrator.go | 6.6 | Mixed | Explicit Debt: TodoComment |
| tests/integration/utils/db_utils.go | 6.9 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| adapters/driver/cmd/command.go | 7.3 | Near-clean | Explicit Debt: TodoComment |
| adapters/driver/cmd/server.go | 7.3 | Near-clean | Explicit Debt: TodoComment |
| adapters/driver/api/users/user_controller.go | 7.3 | Near-clean | Explicit Debt: TodoComment |
| adapters/driver/api/users/user_request.go | 7.3 | Near-clean | Explicit Debt: TodoComment |
| adapters/driven/rabbitmq/consumer.go | 7.3 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 57 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 212 of 247 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`coverage report`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.go), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) 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 (`go test -coverprofile=coverage.out ./...`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — the Go suite (github.com/NicklasWallgren/go-template) did not finish re-running within its budget: the Go suite did not finish re-running within its tier budget.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 86 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `adapters/driven/persistence/users/user_repository.go`, `adapters/driver/api/users/user_converter.go`, `adapters/driver/api/users/user_overview_converter.go`, `domain/validation/validator.go` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c go build -o ./build/go-template ." did not complete successfully: exit code: 1; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — 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 authorization 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 authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit 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 audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention 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 retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights 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 data-subject rights controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — 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, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- X22 Contradicted release guard — 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 Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Go 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.
- X23 Unguarded diagnostic materialisation — 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, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — 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, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — 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, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — 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 Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go 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.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — 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 no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 function(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 function(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 over-large unit(s) detected — types, modules or files that carry too much.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with entity_repository.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with entity_repository.go. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
2 of 12 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with user_validator.go, entity_repository.go. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
8 test methods: 5 unit, 3 integration, 0 BDD, 0 e2e. The Go suite contributes 8 test case(s) across 8 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 3 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
D12 · Dependency Hygiene
24 outdated, 0 author-deprecated direct Go module(s), 2 pinning or checksum defect(s). 27 of 27 direct requirement(s) were graded against proxy.golang.org (0 not served there, 1 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
What to do
- Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 104 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's REDACTED requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included. A further 1 module(s) are not known to the public Go module index (private modules, or pins the public proxy never served) and are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
52 deducted task-comment markers across 3453 LoC (1.0/KLoC) → score 8.1. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 52 TodoComment finding(s) in Explicit Debt — start with publisher.go (6), migrate.go (4), goose_migrator.go (4). — One of this dimension's main actionable groups (52 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 1 build units (Go) flagged as possibly oversized/incoherent.
D27 · Navigability
68 % of calls cross a namespace and 35 % go through an interface, but 46 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
- 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)
22 finding(s): 0 critical, 15 high, 7 medium, 0 low. 10 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 4 file(s) — `adapters/driven/persistence/users/user_repository.go` (lines 39–40, line 42), `adapters/driver/api/users/user_converter.go` (lines 15–16, lines 18–19), `adapters/driver/api/users/user_overview_converter.go` (lines 10–11, lines 12–14), `domain/validation/validator.go` (lines 12–14, line 17) — 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 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
11 finding(s): 2 critical, 4 high, 5 medium, 0 low.
What to do
- Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
97 finding(s): 0 critical, 5 high, 75 medium, 17 low.
What to do
- Resolve the 75 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (25), REDACTED (21), REDACTED (21). — One of this dimension's main actionable groups (75 warning-level).
- Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 17 Low IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (5), REDACTED (5). — One of this dimension's main actionable groups (17 recommendation-level).
D34 · Knowledge Freshness
9 of 9 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is adapters/driven/persistence/transaction/transaction.go. Counted over 9 of the 105 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 9 Orphaned file finding(s) in Knowledge Freshness — start with transaction.go, user_controller.go, user_service.go. — One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
0/3 workload(s) run every container under a seccomp profile; 0/3 declare an AppArmor/SELinux profile.
What to do
- Resolve the 3 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 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
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `User` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — domain/users/entities/user.go:10
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `User` exposes publicly writable state (Name, Email, Age, Birthday, CreatedAt, UpdatedAt). — domain/users/entities/user.go:10
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
- The domain package `github.com/NicklasWallgren/go-template/domain/event` imports `pkg:adapters` — an infrastructure concern (persistence/HTTP/broker/auth). The dependency direction points from the domain layer to infrastructure; invert it behind a domain-owned port. — domain/event/entity_listener.go:7
- The domain package `github.com/NicklasWallgren/go-template/domain/users` imports `pkg:adapters` — an infrastructure concern (persistence/HTTP/broker/auth). The dependency direction points from the domain layer to infrastructure; invert it behind a domain-owned port. — domain/users/user_validator.go:6
- The domain package `github.com/NicklasWallgren/go-template/domain/users` imports `gorm.io/gorm` — an infrastructure concern (persistence/HTTP/broker/auth). The dependency direction points from the domain layer to infrastructure; invert it behind a domain-owned port. — domain/users/user_validator.go:10
- The domain package `github.com/NicklasWallgren/go-template/domain/validation` imports `gorm.io/gorm` — an infrastructure concern (persistence/HTTP/broker/auth). The dependency direction points from the domain layer to infrastructure; invert it behind a domain-owned port. — domain/validation/validator.go:7
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM7 · Repository granularity
- `Repository` leaks the infrastructure/framework type `DB` through its contract. A repository should be a persistence PORT over an aggregate ROOT — expose intention-revealing whole-aggregate operations (Save/FindByID) and keep framework types, query specifications and business logic out of its contract so callers can't bypass the aggregate's invariants. — adapters/driven/persistence/repository.go:18
- `UserRepository` leaks the infrastructure/framework type `DB` through its contract. A repository should be a persistence PORT over an aggregate ROOT — expose intention-revealing whole-aggregate operations (Save/FindByID) and keep framework types, query specifications and business logic out of its contract so callers can't bypass the aggregate's invariants. — adapters/driven/persistence/users/user_repository.go:18
What to do
- Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED3 · Event naming
- `EntityEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — domain/event/entity_event.go:21
What to do
- Name events in the past tense — they record facts that already happened.
ED4 · Outbox / dual-write
- `userService.CreateUser` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — domain/users/user_service.go:134
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
P2 · Observability
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X26 · Unsynchronised callback handoff
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 92% | Exemplary | Strongest area. |
| Architecture | 78% | Strong | 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 P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Adequate — gated by D29, D31 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 43% | Weak — gated by DM4, DM5, DM7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 89% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 3 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). 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.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit 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 audit 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.
- C4 Data Retention — Not assessed: these retention 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 retention 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.
- C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Go's fx constructs every dependency once for the life of the application, so there is no shorter lifetime to capture.
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c go build -o ./build/go-template ." did not complete successfully: exit code: 1; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization 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 authorization 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.
- D10 Test Quality — ~807 lines of test source are present (.go) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included
- D16 Bus Factor — 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .go, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
- D5 Coupling — Not applicable — this Go build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED5 Idempotency — Not assessed, and this one is on us: 5 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Go source (service entry point: adapters/driver/cmd/server.go:62 (http.Server{))
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) 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 `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, 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: Go has no async/await function colour, 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — 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
- 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.
- X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Go's `++`, `--` and assignments are STATEMENTS, not expressions, so none of them can appear in a `case` expression or anywhere else in a condition, and a type switch's cases are types. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — 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
- X27 Collection changed while being enumerated — 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
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Go's type system has no nullable and non-nullable types — every pointer, map, slice and interface is nil-able at every position, there is no switch that turns null checking on, and the compiler produces no nullability warning for an operator to silence. Not a gap in the analyzer and not a finding about your code.
- 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 — 27 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dual write (no outbox): userService.CreateUser domain/users/user_service.go:134
Serious — 152 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment tests/integration/utils.go:40
- TodoComment tests/integration/utils/db_utils.go:20
- TodoComment tests/integration/utils/db_utils.go:25
- TodoComment tests/integration/utils/db_utils.go:36
- TodoComment tests/integration/api/users/user_controller_test.go:129
- TodoComment tests/factories/factory.go:11
- TodoComment domain/validation/validator_test.go:9
- TodoComment adapters/driven/rabbitmq/publisher.go:46
- TodoComment domain/errors/errors.go:9
- TodoComment domain/common/entity.go:9
- TodoComment config/app_config.go:15
- TodoComment config/database_config.go:10
- TodoComment bootstrap/app.go:47
- TodoComment adapters/driver/cmd/command.go:24
- TodoComment adapters/driver/cmd/command.go:69
- TodoComment adapters/driver/cmd/migrate.go:42
- TodoComment adapters/driver/cmd/migrate.go:49
- TodoComment adapters/driver/cmd/migrate.go:56
- TodoComment adapters/driver/cmd/migrate.go:63
- TodoComment adapters/driver/cmd/rabbitmq.go:28
- TodoComment adapters/driver/cmd/server.go:47
- TodoComment adapters/driver/cmd/server.go:76
- TodoComment adapters/driver/api/users/user_controller.go:88
- TodoComment adapters/driver/api/users/user_controller.go:111
- TodoComment adapters/driver/api/users/user_request.go:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dependency pinned to a stale untagged commit: github.com/rs/cors/wrapper/gin
- Dependency pinned to a stale untagged commit: github.com/swaggo/files
- Low cohesion: UserValidator (LCOM4 6) domain/users/user_validator.go:15
- Low cohesion: entityRepository (LCOM4 4) adapters/driven/persistence/entity_repository.go:34
- Leaky repository contract: Repository adapters/driven/persistence/repository.go:18
- Leaky repository contract: UserRepository adapters/driven/persistence/users/user_repository.go:18
- REDACTED
- Duplicated block (11 lines × 2) adapters/driven/persistence/entity_repository.go:100
- Duplicated block (8 lines × 2) adapters/driven/persistence/entity_repository.go:171
- Coverage collected but not gated
- No DR/backup evidence
Minor — 44 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file adapters/driven/persistence/transaction/transaction.go:1
- Orphaned file adapters/driver/api/users/user_controller.go:1
- Orphaned file domain/users/user_service.go:1
- Orphaned file adapters/driven/persistence/entity_repository.go:1
- Orphaned file adapters/driven/persistence/users/user_repository.go:1
- Orphaned file adapters/driven/persistence/repository.go:1
- Orphaned file domain/users/user_validator.go:1
- Orphaned file adapters/driven/rabbitmq/publisher.go:1
- Orphaned file adapters/driver/api/module.go:1
- Domain depends on infrastructure: event domain/event/entity_listener.go:7
- Domain depends on infrastructure: users domain/users/user_validator.go:6
- Domain depends on infrastructure: users domain/users/user_validator.go:10
- Domain depends on infrastructure: validation domain/validation/validator.go:7
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- No seccomp profile REDACTED:2
- No ADRs found
- High interface indirection
- Scattered collaborators
- Orphaned files with no living knowledge
- No network policy
- Anemic entity: User domain/users/entities/user.go:10
- Mutable entity: User domain/users/entities/user.go:10
- Event not named in past tense: EntityEvent domain/event/entity_event.go:21
- No ADRs
- Dependabot does not watch github-actions REDACTED:2
- No changelog
Minor — 24 finding(s)
- Outdated: github.com/brianvoe/gofakeit/v6
- Outdated: github.com/gin-gonic/gin
- Outdated: github.com/gkampitakis/go-snaps
- Outdated: github.com/go-playground/validator/v10
- Outdated: github.com/go-sql-driver/mysql
- Outdated: github.com/iamolegga/enviper
- Outdated: github.com/jackc/pgconn
- Outdated: github.com/lib/pq
- Outdated: github.com/mariomac/gostream
- Outdated: github.com/mitchellh/mapstructure
- Outdated: github.com/pressly/goose/v3
- Outdated: github.com/spf13/cobra
- Outdated: github.com/spf13/viper
- Outdated: github.com/stretchr/testify
- Outdated: github.com/swaggo/files
- Outdated: github.com/swaggo/gin-swagger
- Outdated: github.com/swaggo/swag
- Outdated: go.uber.org/fx
- Outdated: go.uber.org/zap
- Outdated: gopkg.in/DataDog/dd-trace-go.v1
- Outdated: gorm.io/driver/mysql
- Outdated: gorm.io/driver/postgres
- Outdated: gorm.io/gorm
- Outdated: moul.io/zapgorm2
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-97a4d4a1fda343bf98c47bf7a93eada9/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-97a4d4a1fda343bf98c47bf7a93eada9/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 --exclude tests/mocks . | 22 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d76341dc69a94cd48f3cfd17251125dc | 11 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 97 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 4 file(s) — `adapters/driven/persistence/users/user_repository.go`, `adapters/driver/api/users/user_converter.go`, `adapters/driver/api/users/user_overview_converter.go`, `domain/validation/validator.go` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d76341dc69a94cd48f3cfd17251125dc | 0 | artifacts/raw/osv-scanner.json |