Executive summary
marcoturi/fastify-boilerplate is rated At risk because critical security findings are open. Its score is held back in part because we found no access checks on the code's endpoints or handlers. It scores 56 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Security and Compliance, at 32, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 20 points. Raising Security and Compliance to 66 would lift the score to about 72.
Twelve known security holes in the packages the code depends on can be used by attackers. Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one automatic update takes new releases before a bad one can be spotted. Updating the vulnerable packages, pinning each tool to an exact version and setting a waiting period for automatic updates would close these risks.
The product code is 2,444 lines, about €4,200 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Security and Compliance rose from 32 to 66, the lowest score rated Strong, the score would rise from 56 to about 72.
New since the last survey: 37 findings
- Test Quality · No assertions: drain() resolves at once when no handler is running src/shared/cqrs/event-bus.spec.ts
- Test Quality · No assertions: types the handler by its creator (checked by tsc) src/shared/cqrs/request-bus.spec.ts
- Churn × Complexity Hotspots · Repeated repair: src/shared/db/postgres.ts src/shared/db/postgres.ts
- Churn × Complexity Hotspots · Repeated repair: src/config/env.ts src/config/env.ts
- Churn × Complexity Hotspots · Repeated repair: src/index.ts src/index.ts
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Cyclomatic Complexity · Complex function formatError (cyclomatic 11, cognitive 11) src/server/graphql-error-formatter.ts
- Test Coverage · No test reaches this file src/server/plugins/readiness.ts
- Test Coverage · No test reaches this file src/modules/user/commands/delete-user/delete-user.resolver.ts
- Dead Code · Dead file (~52 LoC) src/server/plugins/swagger.ts
- Dead Code · Dead file (~41 LoC) src/shared/cqrs/index.ts
- Dead Code · Dead file (~32 LoC) src/declarations.ts
- Dead Code · Dead file (~30 LoC) src/server/plugins/readiness.ts
- Dead Code · Dead file (~27 LoC) src/modules/user/commands/delete-user/delete-user.route.ts
- Dead Code · Dead file (~25 LoC) src/modules/user/commands/create-user/create-user.route.ts
- Dead Code · Dead file (~23 LoC) src/modules/user/queries/find-users/find-users.route.ts
- Dead Code · Dead file (~20 LoC) src/shared/api/paginated.response.base.ts
- Dead Code · Dead file (~18 LoC) src/modules/user/commands/delete-user/delete-user.handler.ts
- Dead Code · Dead file (~17 LoC) src/modules/user/queries/find-users/find-users.resolver.ts
- Dead Code · Dead file (~15 LoC) src/modules/user/commands/delete-user/delete-user.resolver.ts
- Dead Code · Dead file (~14 LoC) src/modules/user/commands/create-user/create-user.resolver.ts
- Dead Code · Dead file (~13 LoC) src/modules/settings/commands/create-settings/create-settings.event-handler.ts
- Dead Code · Dead file (~11 LoC) src/modules/user/index.ts
- Dead Code · Dead file (~9 LoC) src/server/plugins/request-context.ts
- Dead Code · Dead file (~3 LoC) src/server/plugins/cqrs.ts
- Dependency Hygiene · Unused dependency '@opentelemetry/instrumentation'
- Incompleteness & stubs · Fake-async — async method never awaits src/modules/user/commands/create-user/create-user.resolver.ts
- Incompleteness & stubs · Fake-async — async method never awaits src/modules/user/commands/delete-user/delete-user.resolver.ts
Fixed since the last survey: 62 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) src/shared/cqrs/otel-middleware.ts
- Test Coverage · No test reaches this file src/server/plugins/error-handler.ts
- Test Coverage · No test reaches this file src/shared/cqrs/otel-middleware.ts
- Test Coverage · No test reaches this file src/modules/user/database/user.repository.ts
- Test Coverage · No test reaches this file src/modules/user/user.mapper.ts
- Test Coverage · No test reaches this file src/shared/cqrs/middlewares.ts
- Test Coverage · No test reaches this file src/shared/api/api-error.response.ts
- Test Coverage · No test reaches this file src/modules/user/commands/create-user/create-user.handler.ts
- Test Coverage · No test reaches this file src/shared/ddd/query.base.ts
- Test Coverage · No test reaches this file src/modules/user/queries/find-users/find-users.handler.ts
- Test Coverage · No test reaches this file src/modules/user/dtos/user.graphql-schema.ts
- Test Coverage · No test reaches this file src/shared/utils/validator.util.ts
- Test Coverage · No test reaches this file src/modules/user/queries/find-users/find-users.graphql-schema.ts
- Test Coverage · No test reaches this file src/modules/user/commands/create-user/create-user.graphql-schema.ts
- Test Coverage · No test reaches this file src/server/plugins/cqrs.ts
- Test Coverage · No test reaches this file src/modules/user/dtos/user.paginated.response.dto.ts
- Test Coverage · No test reaches this file src/modules/user/domain/user.errors.ts
- Test Coverage · No test reaches this file src/shared/cqrs/command-bus.ts
- Test Coverage · No test reaches this file src/shared/cqrs/query-bus.ts
- Dead Code · Dead file (~82 LoC) src/server/plugins/error-handler.ts
- Dead Code · Dead file (~80 LoC) src/shared/cqrs/otel-middleware.ts
- Dead Code · Dead file (~58 LoC) src/server/plugins/swagger.ts
- Dead Code · Dead file (~55 LoC) src/shared/cqrs/index.ts
- Dead Code · Dead file (~52 LoC) src/modules/user/user.mapper.ts
- Dead Code · Dead file (~49 LoC) src/shared/cqrs/middlewares.ts
- Dead Code · Dead file (~38 LoC) src/shared/api/api-error.response.ts
- Dead Code · Dead file (~37 LoC) src/modules/user/commands/create-user/create-user.handler.ts
- Dead Code · Dead file (~33 LoC) src/shared/ddd/query.base.ts
- Dead Code · Dead file (~31 LoC) src/modules/user/commands/create-user/create-user.schema.ts
- Dead Code · Dead file (~31 LoC) src/modules/user/dtos/user.response.dto.ts
- Dead Code · Dead file (~31 LoC) src/modules/user/queries/find-users/find-users.handler.ts
- Dead Code · Dead file (~31 LoC) src/modules/user/queries/find-users/find-users.schema.ts
- Dead Code · Dead file (~29 LoC) src/modules/user/commands/delete-user/delete-user.route.ts
- Dead Code · Dead file (~27 LoC) src/modules/user/commands/create-user/create-user.route.ts
- Dead Code · Dead file (~27 LoC) src/modules/user/queries/find-users/find-users.route.ts
- Dead Code · Dead file (~24 LoC) src/modules/user/dtos/user.graphql-schema.ts
- Dead Code · Dead file (~23 LoC) src/modules/user/commands/create-user/create-user.resolver.ts
- Dead Code · Dead file (~23 LoC) src/shared/utils/validator.util.ts
- Dead Code · Dead file (~21 LoC) src/modules/user/commands/delete-user/delete-user.handler.ts
- Dead Code · Dead file (~20 LoC) src/shared/api/paginated-query.request.dto.ts
- Dead Code · Dead file (~16 LoC) src/modules/user/index.ts
- Dead Code · Dead file (~16 LoC) src/shared/api/response.base.ts
- Dead Code · Dead file (~14 LoC) src/modules/settings/commands/create-settings/create-settings.event-handler.ts
- Dead Code · Dead file (~14 LoC) src/modules/user/queries/find-users/find-users.graphql-schema.ts
- Dead Code · Dead file (~14 LoC) src/server/plugins/request-context.ts
- Dead Code · Dead file (~13 LoC) src/modules/user/commands/create-user/create-user.graphql-schema.ts
- Dead Code · Dead file (~11 LoC) src/modules/user/queries/find-users/find-users.resolver.ts
- Dead Code · Dead file (~11 LoC) src/server/plugins/cqrs.ts
- Dead Code · Dead file (~11 LoC) src/shared/api/paginated.response.base.ts
- Dead Code · Dead file (~10 LoC) src/modules/user/dtos/user.paginated.response.dto.ts
- Dead Code · Dead file (~9 LoC) src/modules/user/domain/user.errors.ts
- Dead Code · Dead file (~9 LoC) src/shared/api/id.response.dto.ts
- Dead Code · Dead file (~6 LoC) src/shared/cqrs/command-bus.ts
- Dead Code · Dead file (~6 LoC) src/shared/cqrs/query-bus.ts
- Dead Code · Dead file (~2 LoC) src/shared/utils/index.ts
- Dependency Hygiene · Unused dependency '@cucumber/html-formatter'
- Dependency Hygiene · Unused dependency '@semantic-release/exec'
Rebuild cost: about €4,200 · Estimate
| Cost to rebuild | €1,400 to €7,100, for 23 to 75 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. 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: 2,444 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 (global) | 2 src.config | 3 src.declarations | 4 src.modules.user.domain | 5 src.modules.user.domain.user_types | 6 src.server.di | 7 src.shared | 8 src.shared.app | 9 src.shared.cqrs.bus_types | 10 src.shared.db.repository_port | 11 src.shared.db.sql-fragments | 12 src.shared.db.transaction-context | 13 src.shared.ddd.mapper_interface | 14 src.shared.exceptions.exception-base | 15 src.shared.utils | 16 src.modules | 17 src.modules.user | 18 src.modules.user.database.user_repository_port | 19 src.shared.api | 20 src.shared.cqrs.event-bus | 21 src.shared.db.sql-repository_base | 22 src.shared.ddd | 23 src.shared.exceptions.exceptions | 24 src.modules.settings.commands.create-settings | 25 src.modules.user.commands.create-user | 26 src.modules.user.commands.delete-user | 27 src.modules.user.database | 28 src.modules.user.domain.user_errors | 29 src.modules.user.queries.find-users | 30 src.shared.cqrs | 31 src.shared.db | 32 src | 33 src.server | 34 src.server.plugins |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||
| 2 src.config | ||||||||||||||||||||||||||||||||||
| 3 src.declarations | ||||||||||||||||||||||||||||||||||
| 4 src.modules.user.domain | ||||||||||||||||||||||||||||||||||
| 5 src.modules.user.domain.user_types | ||||||||||||||||||||||||||||||||||
| 6 src.server.di | ||||||||||||||||||||||||||||||||||
| 7 src.shared | ||||||||||||||||||||||||||||||||||
| 8 src.shared.app | ||||||||||||||||||||||||||||||||||
| 9 src.shared.cqrs.bus_types | ||||||||||||||||||||||||||||||||||
| 10 src.shared.db.repository_port | ||||||||||||||||||||||||||||||||||
| 11 src.shared.db.sql-fragments | ||||||||||||||||||||||||||||||||||
| 12 src.shared.db.transaction-context | ||||||||||||||||||||||||||||||||||
| 13 src.shared.ddd.mapper_interface | ||||||||||||||||||||||||||||||||||
| 14 src.shared.exceptions.exception-base | ||||||||||||||||||||||||||||||||||
| 15 src.shared.utils | ||||||||||||||||||||||||||||||||||
| 16 src.modules | 3 | |||||||||||||||||||||||||||||||||
| 17 src.modules.user | 1 | 1 | ||||||||||||||||||||||||||||||||
| 18 src.modules.user.database.user_repository_port | 1 | 2 | ||||||||||||||||||||||||||||||||
| 19 src.shared.api | 1 | |||||||||||||||||||||||||||||||||
| 20 src.shared.cqrs.event-bus | 1 | |||||||||||||||||||||||||||||||||
| 21 src.shared.db.sql-repository_base | 2 | 1 | ||||||||||||||||||||||||||||||||
| 22 src.shared.ddd | 1 | |||||||||||||||||||||||||||||||||
| 23 src.shared.exceptions.exceptions | 4 | |||||||||||||||||||||||||||||||||
| 24 src.modules.settings.commands.create-settings | 1 | |||||||||||||||||||||||||||||||||
| 25 src.modules.user.commands.create-user | 2 | 1 | ||||||||||||||||||||||||||||||||
| 26 src.modules.user.commands.delete-user | 2 | 1 | ||||||||||||||||||||||||||||||||
| 27 src.modules.user.database | 1 | 1 | ||||||||||||||||||||||||||||||||
| 28 src.modules.user.domain.user_errors | 1 | |||||||||||||||||||||||||||||||||
| 29 src.modules.user.queries.find-users | 2 | 1 | ||||||||||||||||||||||||||||||||
| 30 src.shared.cqrs | 13 | 1 | ||||||||||||||||||||||||||||||||
| 31 src.shared.db | 1 | 1 | ||||||||||||||||||||||||||||||||
| 32 src | 1 | |||||||||||||||||||||||||||||||||
| 33 src.server | 1 | |||||||||||||||||||||||||||||||||
| 34 src.server.plugins | 3 |
16→9 src.modules uses src.shared.cqrs.bus_types✕
- Connections
- 3 pairs of types, where a type in src.modules uses a type in src.shared.cqrs.bus_types.
- The types involved
src.modules.Dependencies→src.shared.cqrs.bus_types.CommandBussrc.modules.Dependencies→src.shared.cqrs.bus_types.EventBussrc.modules.Dependencies→src.shared.cqrs.bus_types.QueryBus
- Direction
- src.modules uses src.shared.cqrs.bus_types, so a change to src.shared.cqrs.bus_types can break src.modules, while a change to src.modules can't break src.shared.cqrs.bus_types.
- Position
- Below the diagonal: src.modules uses a module listed above it, which is the healthy direction.
17→5 src.modules.user uses src.modules.user.domain.user_types✕
- Connections
- 1 pair of types, where a type in src.modules.user uses a type in src.modules.user.domain.user_types.
- The types involved
src.modules.user.user.mapper→src.modules.user.domain.user_types.UserEntity
- Direction
- src.modules.user uses src.modules.user.domain.user_types, so a change to src.modules.user.domain.user_types can break src.modules.user, while a change to src.modules.user can't break src.modules.user.domain.user_types.
- Position
- Below the diagonal: src.modules.user uses a module listed above it, which is the healthy direction.
17→13 src.modules.user uses src.shared.ddd.mapper_interface✕
- Connections
- 1 pair of types, where a type in src.modules.user uses a type in src.shared.ddd.mapper_interface.
- The types involved
src.modules.user.user.mapper→src.shared.ddd.mapper_interface.Mapper
- Direction
- src.modules.user uses src.shared.ddd.mapper_interface, so a change to src.shared.ddd.mapper_interface can break src.modules.user, while a change to src.modules.user can't break src.shared.ddd.mapper_interface.
- Position
- Below the diagonal: src.modules.user uses a module listed above it, which is the healthy direction.
18→5 src.modules.user.database.user_repository_port uses src.modules.user.domain.user_types✕
- Connections
- 1 pair of types, where a type in src.modules.user.database.user_repository_port uses a type in src.modules.user.domain.user_types.
- The types involved
src.modules.user.database.user_repository_port.UserRepository→src.modules.user.domain.user_types.UserEntity
- Direction
- src.modules.user.database.user_repository_port uses src.modules.user.domain.user_types, so a change to src.modules.user.domain.user_types can break src.modules.user.database.user_repository_port, while a change to src.modules.user.database.user_repository_port can't break src.modules.user.domain.user_types.
- Position
- Below the diagonal: src.modules.user.database.user_repository_port uses a module listed above it, which is the healthy direction.
18→10 src.modules.user.database.user_repository_port uses src.shared.db.repository_port✕
- Connections
- 2 pairs of types, where a type in src.modules.user.database.user_repository_port uses a type in src.shared.db.repository_port.
- The types involved
src.modules.user.database.user_repository_port.UserRepository→src.shared.db.repository_port.Paginatedsrc.modules.user.database.user_repository_port.UserRepository→src.shared.db.repository_port.PaginatedQueryParams
- Direction
- src.modules.user.database.user_repository_port uses src.shared.db.repository_port, so a change to src.shared.db.repository_port can break src.modules.user.database.user_repository_port, while a change to src.modules.user.database.user_repository_port can't break src.shared.db.repository_port.
- Position
- Below the diagonal: src.modules.user.database.user_repository_port uses a module listed above it, which is the healthy direction.
19→10 src.shared.api uses src.shared.db.repository_port✕
- Connections
- 1 pair of types, where a type in src.shared.api uses a type in src.shared.db.repository_port.
- The types involved
src.shared.api.paginated.response.base→src.shared.db.repository_port.Paginated
- Direction
- src.shared.api uses src.shared.db.repository_port, so a change to src.shared.db.repository_port can break src.shared.api, while a change to src.shared.api can't break src.shared.db.repository_port.
- Position
- Below the diagonal: src.shared.api uses a module listed above it, which is the healthy direction.
20→9 src.shared.cqrs.event-bus uses src.shared.cqrs.bus_types✕
- Connections
- 1 pair of types, where a type in src.shared.cqrs.event-bus uses a type in src.shared.cqrs.bus_types.
- The types involved
src.shared.cqrs.event-bus.QueuedEvent→src.shared.cqrs.bus_types.Action
- Direction
- src.shared.cqrs.event-bus uses src.shared.cqrs.bus_types, so a change to src.shared.cqrs.bus_types can break src.shared.cqrs.event-bus, while a change to src.shared.cqrs.event-bus can't break src.shared.cqrs.bus_types.
- Position
- Below the diagonal: src.shared.cqrs.event-bus uses a module listed above it, which is the healthy direction.
21→10 src.shared.db.sql-repository_base uses src.shared.db.repository_port✕
- Connections
- 2 pairs of types, where a type in src.shared.db.sql-repository_base uses a type in src.shared.db.repository_port.
- The types involved
src.shared.db.sql-repository_base.QueryHelpers→src.shared.db.repository_port.Paginatedsrc.shared.db.sql-repository_base.QueryHelpers→src.shared.db.repository_port.PaginatedQueryParams
- Direction
- src.shared.db.sql-repository_base uses src.shared.db.repository_port, so a change to src.shared.db.repository_port can break src.shared.db.sql-repository_base, while a change to src.shared.db.sql-repository_base can't break src.shared.db.repository_port.
- Position
- Below the diagonal: src.shared.db.sql-repository_base uses a module listed above it, which is the healthy direction.
21→13 src.shared.db.sql-repository_base uses src.shared.ddd.mapper_interface✕
- Connections
- 1 pair of types, where a type in src.shared.db.sql-repository_base uses a type in src.shared.ddd.mapper_interface.
- The types involved
src.shared.db.sql-repository_base.RepositoryProps→src.shared.ddd.mapper_interface.Mapper
- Direction
- src.shared.db.sql-repository_base uses src.shared.ddd.mapper_interface, so a change to src.shared.ddd.mapper_interface can break src.shared.db.sql-repository_base, while a change to src.shared.db.sql-repository_base can't break src.shared.ddd.mapper_interface.
- Position
- Below the diagonal: src.shared.db.sql-repository_base uses a module listed above it, which is the healthy direction.
22→10 src.shared.ddd uses src.shared.db.repository_port✕
- Connections
- 1 pair of types, where a type in src.shared.ddd uses a type in src.shared.db.repository_port.
- The types involved
src.shared.ddd.query.base→src.shared.db.repository_port.PaginatedQueryParams
- Direction
- src.shared.ddd uses src.shared.db.repository_port, so a change to src.shared.db.repository_port can break src.shared.ddd, while a change to src.shared.ddd can't break src.shared.db.repository_port.
- Position
- Below the diagonal: src.shared.ddd uses a module listed above it, which is the healthy direction.
23→14 src.shared.exceptions.exceptions uses src.shared.exceptions.exception-base✕
- Connections
- 4 pairs of types, where a type in src.shared.exceptions.exceptions uses a type in src.shared.exceptions.exception-base.
- The types involved
src.shared.exceptions.exceptions.AlreadyExistsException→src.shared.exceptions.exception-base.ExceptionBasesrc.shared.exceptions.exceptions.ArgumentInvalidException→src.shared.exceptions.exception-base.ExceptionBasesrc.shared.exceptions.exceptions.InternalException→src.shared.exceptions.exception-base.ExceptionBasesrc.shared.exceptions.exceptions.NotFoundException→src.shared.exceptions.exception-base.ExceptionBase
- Direction
- src.shared.exceptions.exceptions uses src.shared.exceptions.exception-base, so a change to src.shared.exceptions.exception-base can break src.shared.exceptions.exceptions, while a change to src.shared.exceptions.exceptions can't break src.shared.exceptions.exception-base.
- Position
- Below the diagonal: src.shared.exceptions.exceptions uses a module listed above it, which is the healthy direction.
24→16 src.modules.settings.commands.create-settings uses src.modules✕
- Connections
- 1 pair of types, where a type in src.modules.settings.commands.create-settings uses a type in src.modules.
- The types involved
src.modules.settings.commands.create-settings.create-settings.event-handler→src.modules.Dependencies
- Direction
- src.modules.settings.commands.create-settings uses src.modules, so a change to src.modules can break src.modules.settings.commands.create-settings, while a change to src.modules.settings.commands.create-settings can't break src.modules.
- Position
- Below the diagonal: src.modules.settings.commands.create-settings uses a module listed above it, which is the healthy direction.
25→3 src.modules.user.commands.create-user uses src.declarations✕
- Connections
- 2 pairs of types, where a type in src.modules.user.commands.create-user uses a type in src.declarations.
- The types involved
src.modules.user.commands.create-user.create-user.resolver→src.declarations.FastifyRouteInstancesrc.modules.user.commands.create-user.create-user.route→src.declarations.FastifyRouteInstance
- Direction
- src.modules.user.commands.create-user uses src.declarations, so a change to src.declarations can break src.modules.user.commands.create-user, while a change to src.modules.user.commands.create-user can't break src.declarations.
- Position
- Below the diagonal: src.modules.user.commands.create-user uses a module listed above it, which is the healthy direction.
25→16 src.modules.user.commands.create-user uses src.modules✕
- Connections
- 1 pair of types, where a type in src.modules.user.commands.create-user uses a type in src.modules.
- The types involved
src.modules.user.commands.create-user.create-user.handler→src.modules.Dependencies
- Direction
- src.modules.user.commands.create-user uses src.modules, so a change to src.modules can break src.modules.user.commands.create-user, while a change to src.modules.user.commands.create-user can't break src.modules.
- Position
- Below the diagonal: src.modules.user.commands.create-user uses a module listed above it, which is the healthy direction.
26→3 src.modules.user.commands.delete-user uses src.declarations✕
- Connections
- 2 pairs of types, where a type in src.modules.user.commands.delete-user uses a type in src.declarations.
- The types involved
src.modules.user.commands.delete-user.delete-user.resolver→src.declarations.FastifyRouteInstancesrc.modules.user.commands.delete-user.delete-user.route→src.declarations.FastifyRouteInstance
- Direction
- src.modules.user.commands.delete-user uses src.declarations, so a change to src.declarations can break src.modules.user.commands.delete-user, while a change to src.modules.user.commands.delete-user can't break src.declarations.
- Position
- Below the diagonal: src.modules.user.commands.delete-user uses a module listed above it, which is the healthy direction.
26→16 src.modules.user.commands.delete-user uses src.modules✕
- Connections
- 1 pair of types, where a type in src.modules.user.commands.delete-user uses a type in src.modules.
- The types involved
src.modules.user.commands.delete-user.delete-user.handler→src.modules.Dependencies
- Direction
- src.modules.user.commands.delete-user uses src.modules, so a change to src.modules can break src.modules.user.commands.delete-user, while a change to src.modules.user.commands.delete-user can't break src.modules.
- Position
- Below the diagonal: src.modules.user.commands.delete-user uses a module listed above it, which is the healthy direction.
27→16 src.modules.user.database uses src.modules✕
- Connections
- 1 pair of types, where a type in src.modules.user.database uses a type in src.modules.
- The types involved
src.modules.user.database.user.repository→src.modules.Dependencies
- Direction
- src.modules.user.database uses src.modules, so a change to src.modules can break src.modules.user.database, while a change to src.modules.user.database can't break src.modules.
- Position
- Below the diagonal: src.modules.user.database uses a module listed above it, which is the healthy direction.
27→18 src.modules.user.database uses src.modules.user.database.user_repository_port✕
- Connections
- 1 pair of types, where a type in src.modules.user.database uses a type in src.modules.user.database.user_repository_port.
- The types involved
src.modules.user.database.user.repository→src.modules.user.database.user_repository_port.UserRepository
- Direction
- src.modules.user.database uses src.modules.user.database.user_repository_port, so a change to src.modules.user.database.user_repository_port can break src.modules.user.database, while a change to src.modules.user.database can't break src.modules.user.database.user_repository_port.
- Position
- Below the diagonal: src.modules.user.database uses a module listed above it, which is the healthy direction.
28→23 src.modules.user.domain.user_errors uses src.shared.exceptions.exceptions✕
- Connections
- 1 pair of types, where a type in src.modules.user.domain.user_errors uses a type in src.shared.exceptions.exceptions.
- The types involved
src.modules.user.domain.user_errors.UserAlreadyExistsError→src.shared.exceptions.exceptions.AlreadyExistsException
- Direction
- src.modules.user.domain.user_errors uses src.shared.exceptions.exceptions, so a change to src.shared.exceptions.exceptions can break src.modules.user.domain.user_errors, while a change to src.modules.user.domain.user_errors can't break src.shared.exceptions.exceptions.
- Position
- Below the diagonal: src.modules.user.domain.user_errors uses a module listed above it, which is the healthy direction.
29→3 src.modules.user.queries.find-users uses src.declarations✕
- Connections
- 2 pairs of types, where a type in src.modules.user.queries.find-users uses a type in src.declarations.
- The types involved
src.modules.user.queries.find-users.find-users.resolver→src.declarations.FastifyRouteInstancesrc.modules.user.queries.find-users.find-users.route→src.declarations.FastifyRouteInstance
- Direction
- src.modules.user.queries.find-users uses src.declarations, so a change to src.declarations can break src.modules.user.queries.find-users, while a change to src.modules.user.queries.find-users can't break src.declarations.
- Position
- Below the diagonal: src.modules.user.queries.find-users uses a module listed above it, which is the healthy direction.
29→16 src.modules.user.queries.find-users uses src.modules✕
- Connections
- 1 pair of types, where a type in src.modules.user.queries.find-users uses a type in src.modules.
- The types involved
src.modules.user.queries.find-users.find-users.handler→src.modules.Dependencies
- Direction
- src.modules.user.queries.find-users uses src.modules, so a change to src.modules can break src.modules.user.queries.find-users, while a change to src.modules.user.queries.find-users can't break src.modules.
- Position
- Below the diagonal: src.modules.user.queries.find-users uses a module listed above it, which is the healthy direction.
30→9 src.shared.cqrs uses src.shared.cqrs.bus_types✕
- Connections
- 13 pairs of types, where a type in src.shared.cqrs uses a type in src.shared.cqrs.bus_types.
- The types involved
src.shared.cqrs.FastifyInstance→src.shared.cqrs.bus_types.CommandBussrc.shared.cqrs.FastifyInstance→src.shared.cqrs.bus_types.EventBussrc.shared.cqrs.FastifyInstance→src.shared.cqrs.bus_types.QueryBussrc.shared.cqrs.action-creator→src.shared.cqrs.bus_types.ActionCreatorsrc.shared.cqrs.event-bus→src.shared.cqrs.bus_types.Actionsrc.shared.cqrs.event-bus→src.shared.cqrs.bus_types.ActionCreatorsrc.shared.cqrs.event-bus→src.shared.cqrs.bus_types.EventBussrc.shared.cqrs.event-bus→src.shared.cqrs.bus_types.EventBusOptionssrc.shared.cqrs.event-bus→src.shared.cqrs.bus_types.SequentialProcessingOptionssrc.shared.cqrs.middlewares→src.shared.cqrs.bus_types.Actionsrc.shared.cqrs.request-bus→src.shared.cqrs.bus_types.Actionsrc.shared.cqrs.request-bus→src.shared.cqrs.bus_types.ActionCreatorsrc.shared.cqrs.request-bus→src.shared.cqrs.bus_types.RequestBus
- Direction
- src.shared.cqrs uses src.shared.cqrs.bus_types, so a change to src.shared.cqrs.bus_types can break src.shared.cqrs, while a change to src.shared.cqrs can't break src.shared.cqrs.bus_types.
- Position
- Below the diagonal: src.shared.cqrs uses a module listed above it, which is the healthy direction.
30→20 src.shared.cqrs uses src.shared.cqrs.event-bus✕
- Connections
- 1 pair of types, where a type in src.shared.cqrs uses a type in src.shared.cqrs.event-bus.
- The types involved
src.shared.cqrs.event-bus→src.shared.cqrs.event-bus.HandlerRegistration
- Direction
- src.shared.cqrs uses src.shared.cqrs.event-bus, so a change to src.shared.cqrs.event-bus can break src.shared.cqrs, while a change to src.shared.cqrs can't break src.shared.cqrs.event-bus.
- Position
- Below the diagonal: src.shared.cqrs uses a module listed above it, which is the healthy direction.
31→14 src.shared.db uses src.shared.exceptions.exception-base✕
- Connections
- 1 pair of types, where a type in src.shared.db uses a type in src.shared.exceptions.exception-base.
- The types involved
src.shared.db.database-errors→src.shared.exceptions.exception-base.ExceptionBase
- Direction
- src.shared.db uses src.shared.exceptions.exception-base, so a change to src.shared.exceptions.exception-base can break src.shared.db, while a change to src.shared.db can't break src.shared.exceptions.exception-base.
- Position
- Below the diagonal: src.shared.db uses a module listed above it, which is the healthy direction.
31→21 src.shared.db uses src.shared.db.sql-repository_base✕
- Connections
- 1 pair of types, where a type in src.shared.db uses a type in src.shared.db.sql-repository_base.
- The types involved
src.shared.db.sql-repository.base→src.shared.db.sql-repository_base.RepositoryProps
- Direction
- src.shared.db uses src.shared.db.sql-repository_base, so a change to src.shared.db.sql-repository_base can break src.shared.db, while a change to src.shared.db can't break src.shared.db.sql-repository_base.
- Position
- Below the diagonal: src.shared.db uses a module listed above it, which is the healthy direction.
32→30 src uses src.shared.cqrs✕
- Connections
- 1 pair of types, where a type in src uses a type in src.shared.cqrs.
- The types involved
src.index→src.shared.cqrs.FastifyInstance
- Direction
- src uses src.shared.cqrs, so a change to src.shared.cqrs can break src, while a change to src can't break src.shared.cqrs.
- Position
- Below the diagonal: src uses a module listed above it, which is the healthy direction.
33→30 src.server uses src.shared.cqrs✕
- Connections
- 1 pair of types, where a type in src.server uses a type in src.shared.cqrs.
- The types involved
src.server.index→src.shared.cqrs.FastifyInstance
- Direction
- src.server uses src.shared.cqrs, so a change to src.shared.cqrs can break src.server, while a change to src.server can't break src.shared.cqrs.
- Position
- Below the diagonal: src.server uses a module listed above it, which is the healthy direction.
34→30 src.server.plugins uses src.shared.cqrs✕
- Connections
- 3 pairs of types, where a type in src.server.plugins uses a type in src.shared.cqrs.
- The types involved
src.server.plugins.error-handler→src.shared.cqrs.FastifyInstancesrc.server.plugins.readiness→src.shared.cqrs.FastifyInstancesrc.server.plugins.swagger→src.shared.cqrs.FastifyInstance
- Direction
- src.server.plugins uses src.shared.cqrs, so a change to src.shared.cqrs can break src.server.plugins, while a change to src.server.plugins can't break src.shared.cqrs.
- Position
- Below the diagonal: src.server.plugins uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 20 | High / Critical |
| A05:2025 — Injection | 14 | High / Critical |
| A02:2025 — Security Misconfiguration | 3 | Medium |
Roadmap
Top priorities: Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10); Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +19.6 pts | Medium | Access Controls |
| Resolve the 2 redundant comment finding(s) in Comment Value — start with index.ts (2). | +2.5 pts | Low | Comment Value |
| Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). | +4.1 pts | Medium | Dependency Vulnerabilities |
| 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. | +3.4 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). | +1.3 pts | Low | Dependency Vulnerabilities |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.3 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| src/modules/settings/commands/create-settings/create-settings.event-handler.ts | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/shared/cqrs/event-bus.spec.ts | 8.5 | Near-clean | Test Quality: No assertions: drain() resolves at once when no handler is running |
| src/shared/cqrs/request-bus.spec.ts | 8.5 | Near-clean | Test Quality: No assertions: types the handler by its creator (checked by tsc) |
| src/server/index.ts | 9.3 | Near-clean | Comment Value: redundant comment |
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 72 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 — 72 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, 89 of 98 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and 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 MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
- 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 for the node:test suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D12 Dependency Hygiene — 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 repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because registry.npmjs.org — the registry that answers it — was asked and did not reply (registry returned 429). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add registry.npmjs.org to the allowlist and re-run — not to build anything.
- 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 1837 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.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (client/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/config/env.ts`, `src/server/options.ts`, `src/server/plugins/error-handler.ts`, `src/shared/cqrs/bus.types.ts`, `src/shared/utils/with-timeout.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Awilix, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 14 — a file the compose project references is missing) — time="2026-11-09T05:14:17Z" level=warning msg="The \"POSTGRES_DB\" variable is not set. Defaulting to a blank string." env file .env not found: stat .env: no such file or directory; 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. 'postgres' is imported (src/shared/db/postgres.ts:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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. 'postgres' is imported (src/shared/db/postgres.ts:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'postgres' is imported (src/shared/db/postgres.ts:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'postgres' is imported (src/shared/db/postgres.ts:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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. 72 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- 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.
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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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").
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D5 · Coupling
2 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D9 · Test Distribution
104 test methods: 104 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 104 `it`/`test` case(s) across 21 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 104 tests.
What to do
- Resolve the 2 No assertions finding(s) in Test Quality — start with event-bus.spec.ts, request-bus.spec.ts. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: src/shared/db/postgres.ts (10 of 15 changes were fixes); src/config/env.ts (6 of 10 changes were fixes); src/index.ts (6 of 7 changes were fixes)
What to do
- Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with postgres.ts, env.ts, index.ts. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
1 deducted task-comment markers across 2101 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with create-settings.event-handler.ts. — One of this dimension's main actionable groups (1 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. 2 document(s) read across 2 unit(s).
D24 · Comment Value
2 of 74 judged comments only repeat the code they sit on (2.7 %). 4 comment(s) in another language or script were not judged.
What to do
- Resolve the 2 redundant comment finding(s) in Comment Value — start with index.ts (2). — One of this dimension's main actionable groups (2 recommendation-level).
D26 · Project Cohesion
0 of 1 build units (npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
14 finding(s): 0 critical, 12 high, 2 medium, 0 low. 11 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 5 file(s) — `src/config/env.ts` (line 4), `src/server/options.ts` (line 34), `src/server/plugins/error-handler.ts` (line 56), `src/shared/cqrs/bus.types.ts` (line 6, line 9), `src/shared/utils/with-timeout.ts` (line 5) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 11 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 (11 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
15 finding(s): 2 critical, 10 high, 3 medium, 0 low.
What to do
- Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 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).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 11 of the 74 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 24 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
C2 · Access Controls
- This repository serves requests — Fastify() (src/index.ts:12) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — src/index.ts:12
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `createUserResolver` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/modules/user/commands/create-user/create-user.resolver.ts:7
- `deleteUserResolver` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/modules/user/commands/delete-user/delete-user.resolver.ts:8
What to do
- Remove the dead code that still moves this score: delete dead if(false) branches and either do the real async work or drop the async keyword from fake-async functions.
M1 · Documentation (README)
What to do
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
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
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
P11 · BDD / executable specs
P2 · Observability
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
R2 · Cyclomatic Complexity
- formatError has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/server/graphql-error-formatter.ts:35
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×22) — src/index.ts:1, src/server/plugins/swagger.ts:1, src/instrumentation.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- Unreachable from the 6 application, 3 tooling and 31 test entry point(s) detected in this repo. Gate removals on `pnpm run type:check` — an undetected custom entry would make these reachable.
- no import path from any entry point (6 application, 3 tooling, 31 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×13) — src/server/plugins/swagger.ts, src/declarations.ts, src/server/plugins/readiness.ts, …
- no import path from any entry point (6 application, 3 tooling, 31 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/server/plugins/cqrs.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/shared/cqrs/index.ts
- no import path from any entry point (6 application, 3 tooling, 31 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/modules/user/queries/find-users/find-users.resolver.ts, src/modules/user/queries/find-users/find-users.route.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/shared/api/paginated.response.base.ts
- no import path from any entry point (6 application, 3 tooling, 31 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/modules/user/commands/delete-user/delete-user.resolver.ts, src/modules/user/commands/delete-user/delete-user.route.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/modules/user/commands/delete-user/delete-user.handler.ts
- No runtime consumer imports this binding — the only demand on it comes from a type-position import of its module, which asks for the module's type surface rather than for this name. If the value is genuinely unneeded, remove it; if a consumer needs only its TYPE, export that type (e.g. `export type X = typeof x`) and drop the value. A value export — a const, a function, a class — cannot itself be rewritten as `export type`. — src/modules/user/database/user.repository.ts:21
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
- Every import is type-only — move it to devDependencies. — src/declarations.ts:3
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn` at line 19 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/index.ts:19
- `info` at line 23 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/index.ts:23
- `debug` at line 47 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/shared/db/postgres.ts:47
- `debug` at line 134 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/shared/cqrs/event-bus.ts:134
- `debug` at line 35 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/shared/cqrs/middlewares.ts:35
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 76% | Strong | Solid. |
| Architecture | 97% | Exemplary | Solid. |
| Maturity | 69% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 80% | Exemplary | Solid. |
| Security | 32% | Weak — gated by D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 1 observation(s) recorded · Dependency currency not established — registry.npmjs.org did not answer
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'postgres' (src/shared/db/postgres.ts:2) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'postgres' (src/shared/db/postgres.ts:2) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'postgres' (src/shared/db/postgres.ts:2) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 14 — a file the compose project references is missing) — time="2026-11-09T05:14:17Z" level=warning msg="The \"POSTGRES_DB\" variable is not set. Defaulting to a blank string." env file .env not found: stat .env: no such file or directory; 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: this repository stores data through 'postgres' (src/shared/db/postgres.ts:2) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- D14 License Compliance — Not scored — this repository's 206 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 12 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (299 declarations, no unit with a dominant convention).
- 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"]`.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — 5 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.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 8 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (8 with fewer than two methods), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- 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 measured — JavaScript/TypeScript suite
- DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: src/index.ts:12 (Fastify())
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: 72 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 24 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
Serious — 59 finding(s)
- No test reaches this file src/index.ts:1
- No test reaches this file src/server/plugins/swagger.ts:1
- No test reaches this file src/instrumentation.ts:1
- No test reaches this file src/shared/cqrs/index.ts:1
- No test reaches this file src/modules/user/commands/create-user/create-user.schema.ts:1
- No test reaches this file src/modules/user/dtos/user.response.dto.ts:1
- No test reaches this file src/server/plugins/readiness.ts:1
- No test reaches this file src/modules/user/commands/delete-user/delete-user.route.ts:1
- No test reaches this file src/modules/user/commands/create-user/create-user.route.ts:1
- No test reaches this file src/modules/user/queries/find-users/find-users.route.ts:1
- No test reaches this file src/shared/api/paginated-query.request.dto.ts:1
- No test reaches this file src/shared/api/paginated.response.base.ts:1
- No test reaches this file src/modules/user/commands/delete-user/delete-user.handler.ts:1
- No test reaches this file src/modules/user/queries/find-users/find-users.resolver.ts:1
- No test reaches this file scripts/codegen.ts:1
- No test reaches this file src/shared/api/response.base.ts:1
- No test reaches this file src/modules/user/commands/delete-user/delete-user.resolver.ts:1
- No test reaches this file src/modules/user/commands/create-user/create-user.resolver.ts:1
- No test reaches this file src/modules/settings/commands/create-settings/create-settings.event-handler.ts:1
- No test reaches this file src/modules/user/queries/find-users/find-users.schema.ts:1
- No test reaches this file src/server/plugins/request-context.ts:1
- No test reaches this file src/shared/api/id.response.dto.ts:1
- Repeated repair: src/shared/db/postgres.ts src/shared/db/postgres.ts:21
- Repeated repair: src/config/env.ts src/config/env.ts:44
- Repeated repair: src/index.ts src/index.ts:11
- REDACTED
- REDACTED
- REDACTED
- No assertions: drain() resolves at once when no handler is running src/shared/cqrs/event-bus.spec.ts:179
- No assertions: types the handler by its creator (checked by tsc) src/shared/cqrs/request-bus.spec.ts:25
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Fake-async — async method never awaits src/modules/user/commands/create-user/create-user.resolver.ts:7
- Fake-async — async method never awaits src/modules/user/commands/delete-user/delete-user.resolver.ts:8
- No authorization src/index.ts:12
- TodoComment src/modules/settings/commands/create-settings/create-settings.event-handler.ts:9
- REDACTED
- REDACTED
- Complex function formatError (cyclomatic 11, cognitive 11) src/server/graphql-error-formatter.ts:35
- Dead file (~52 LoC) src/server/plugins/swagger.ts
- Dead file (~41 LoC) src/shared/cqrs/index.ts
- Dead file (~32 LoC) src/declarations.ts
- Dead file (~30 LoC) src/server/plugins/readiness.ts
- Dead file (~27 LoC) src/modules/user/commands/delete-user/delete-user.route.ts
- Dead file (~25 LoC) src/modules/user/commands/create-user/create-user.route.ts
- Dead file (~23 LoC) src/modules/user/queries/find-users/find-users.route.ts
- Dead file (~20 LoC) src/shared/api/paginated.response.base.ts
- Dead file (~18 LoC) src/modules/user/commands/delete-user/delete-user.handler.ts
- Dead file (~17 LoC) src/modules/user/queries/find-users/find-users.resolver.ts
- Dead file (~15 LoC) src/modules/user/commands/delete-user/delete-user.resolver.ts
- Dead file (~14 LoC) src/modules/user/commands/create-user/create-user.resolver.ts
- Dead file (~13 LoC) src/modules/settings/commands/create-settings/create-settings.event-handler.ts
- Dead file (~11 LoC) src/modules/user/index.ts
- Dead file (~9 LoC) src/server/plugins/request-context.ts
- Dead file (~3 LoC) src/server/plugins/cqrs.ts
- Unused dependency '@opentelemetry/instrumentation'
- Unused dependency 'openapi-typescript'
Minor — 15 finding(s)
- Interpolated log message defeats structured logging src/index.ts:19
- Interpolated log message defeats structured logging src/index.ts:23
- Interpolated log message defeats structured logging src/shared/db/postgres.ts:47
- Interpolated log message defeats structured logging src/shared/cqrs/event-bus.ts:134
- Interpolated log message defeats structured logging src/shared/cqrs/middlewares.ts:35
- redundant comment src/server/index.ts:56
- redundant comment src/server/index.ts:67
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- CI build step not evidenced
- Unused export 'default' src/modules/user/database/user.repository.ts:21
- Type-only dependency '@fastify/type-provider-typebox' in production deps src/declarations.ts:3
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-b17863d7c8a94d74b7fb3ec5709fd45e/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-b17863d7c8a94d74b7fb3ec5709fd45e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 14 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 15 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | 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 5 file(s) — `src/config/env.ts`, `src/server/options.ts`, `src/server/plugins/error-handler.ts`, `src/shared/cqrs/bus.types.ts`, `src/shared/utils/with-timeout.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |