Executive summary
andrea-acampora/nestjs-ddd-devops is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 54 out of 100, which the At risk rating leaves unchanged.
Domain Modelling, at 51, is the weakest lens, level with Production Readiness, and counts most in the score. The best first steps are replacing the two exposed passwords or keys and switching the old ones off and recording design decisions, each worth about 3 points.
Fifty-four known security holes in the packages the code depends on can be used by attackers. Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and three settings leave the servers or containers unsafe. Updating the vulnerable packages, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the two passwords or keys in the code and the password or key in the code's history need replacing, with the old ones switched off. The loop of files that import each other needs breaking.
The product code is 1,782 lines, about €3,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 12 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Web-Security Posture · Password hashing without a KDF src/modules/user/infrastructure/database/repository/user.repository.ts
Fixed since the last survey: 13 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- DR & Backup · No DR/backup evidence
Rebuild cost: about €3,000 · Estimate
| Cost to rebuild | €1,000 to €5,000, for 17 to 53 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 54. 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 | Very small: 1,782 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 libs.api.rest.collection_interface | 2 libs.api.rest.paginated_response_dto | 3 libs.ddd.use-case_interface | 4 modules.auth.api.rest.presentation.body.login_body | 5 modules.auth.api.rest.presentation.dto.auth-user_dto | 6 modules.communication.application.service.email_service_interface | 7 modules.user.api.graphql.presentation.model.user_model | 8 modules.user.api.rest.presentation.dto.user_dto | 9 modules.user.api.rest.presentation.params.user-sort_params | 10 modules.user.domain.value-object.user-role_enum | 11 libs.api.rest | 12 libs.ddd.repository_interface | 13 modules.auth.api.rest.presentation.body.signup_body | 14 modules.auth.api.rest.presentation.dto.jwt-user_dto | 15 modules.auth.application.use-case.login_use-case | 16 modules.user.api.graphql.resolver.user_resolver | 17 modules.user.api.rest.presentation.params.user_params | 18 modules.user.application.command.create-user_command | 19 modules.user.domain.entity.user_entity | 20 modules.user.infrastructure.database.entity.user_entity | 21 libs.ddd.mikro-orm-repository_abstract | 22 modules.auth.application.service.jwt-auth-service_interface | 23 modules.auth.application.use-case.signup_use-case | 24 modules.user.api.graphql.presentation.model | 25 modules.user.api.rest.controller.user_controller | 26 modules.user.api.rest.presentation.dto | 27 modules.user.domain.event.created-user_event | 28 modules.user.domain.repository.user_repository_interface | 29 modules.user.infrastructure.database.mapper.user_mapper | 30 modules.auth.api.rest.controller.auth_controller | 31 modules.auth.infrastructure.jwt.jwt_service | 32 modules.communication.application.handler.event.created-user_handler | 33 modules.user.application.handler.query.check-auth-user-by-id_handler | 34 modules.user.application.handler.query.get-all-users_handler | 35 modules.user.application.handler.query.get-auth-user-by-email_handler | 36 modules.user.application.handler.query.get-user-by-id_handler | 37 modules.user.application.use-case.create-user_use-case | 38 modules.user.infrastructure.database.repository.user_repository | 39 modules.user.application.handler.command.create-user_handler | 40 modules.user.application.handler.command.register-user_handler |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 libs.api.rest.collection_interface | ||||||||||||||||||||||||||||||||||||||||
| 2 libs.api.rest.paginated_response_dto | ||||||||||||||||||||||||||||||||||||||||
| 3 libs.ddd.use-case_interface | ||||||||||||||||||||||||||||||||||||||||
| 4 modules.auth.api.rest.presentation.body.login_body | ||||||||||||||||||||||||||||||||||||||||
| 5 modules.auth.api.rest.presentation.dto.auth-user_dto | ||||||||||||||||||||||||||||||||||||||||
| 6 modules.communication.application.service.email_service_interface | ||||||||||||||||||||||||||||||||||||||||
| 7 modules.user.api.graphql.presentation.model.user_model | ||||||||||||||||||||||||||||||||||||||||
| 8 modules.user.api.rest.presentation.dto.user_dto | ||||||||||||||||||||||||||||||||||||||||
| 9 modules.user.api.rest.presentation.params.user-sort_params | ||||||||||||||||||||||||||||||||||||||||
| 10 modules.user.domain.value-object.user-role_enum | ||||||||||||||||||||||||||||||||||||||||
| 11 libs.api.rest | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 libs.ddd.repository_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 modules.auth.api.rest.presentation.body.signup_body | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 modules.auth.api.rest.presentation.dto.jwt-user_dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 modules.auth.application.use-case.login_use-case | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 modules.user.api.graphql.resolver.user_resolver | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 modules.user.api.rest.presentation.params.user_params | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 modules.user.application.command.create-user_command | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 modules.user.domain.entity.user_entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 modules.user.infrastructure.database.entity.user_entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 libs.ddd.mikro-orm-repository_abstract | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 modules.auth.application.service.jwt-auth-service_interface | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 modules.auth.application.use-case.signup_use-case | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 modules.user.api.graphql.presentation.model | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 modules.user.api.rest.controller.user_controller | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 26 modules.user.api.rest.presentation.dto | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 modules.user.domain.event.created-user_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 modules.user.domain.repository.user_repository_interface | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 modules.user.infrastructure.database.mapper.user_mapper | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 modules.auth.api.rest.controller.auth_controller | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 31 modules.auth.infrastructure.jwt.jwt_service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 modules.communication.application.handler.event.created-user_handler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 modules.user.application.handler.query.check-auth-user-by-id_handler | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 modules.user.application.handler.query.get-all-users_handler | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 modules.user.application.handler.query.get-auth-user-by-email_handler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 modules.user.application.handler.query.get-user-by-id_handler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 modules.user.application.use-case.create-user_use-case | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 modules.user.infrastructure.database.repository.user_repository | 1 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 modules.user.application.handler.command.create-user_handler | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 modules.user.application.handler.command.register-user_handler | 1 | 1 |
11→1 libs.api.rest uses libs.api.rest.collection_interface✕
- Connections
- 2 pairs of types, where a type in libs.api.rest uses a type in libs.api.rest.collection_interface.
- The types involved
src.libs.api.rest.collection.interface→src.libs.api.rest.collection_interface.Collectionsrc.libs.api.rest.paginated.response.dto→src.libs.api.rest.collection_interface.Collection
- Direction
- libs.api.rest uses libs.api.rest.collection_interface, so a change to libs.api.rest.collection_interface can break libs.api.rest, while a change to libs.api.rest can't break libs.api.rest.collection_interface.
- Position
- Below the diagonal: libs.api.rest uses a module listed above it, which is the healthy direction.
11→2 libs.api.rest uses libs.api.rest.paginated_response_dto✕
- Connections
- 1 pair of types, where a type in libs.api.rest uses a type in libs.api.rest.paginated_response_dto.
- The types involved
src.libs.api.rest.paginated.response.dto→src.libs.api.rest.paginated_response_dto.PaginatedResponse
- Direction
- libs.api.rest uses libs.api.rest.paginated_response_dto, so a change to libs.api.rest.paginated_response_dto can break libs.api.rest, while a change to libs.api.rest can't break libs.api.rest.paginated_response_dto.
- Position
- Below the diagonal: libs.api.rest uses a module listed above it, which is the healthy direction.
12→1 libs.ddd.repository_interface uses libs.api.rest.collection_interface✕
- Connections
- 1 pair of types, where a type in libs.ddd.repository_interface uses a type in libs.api.rest.collection_interface.
- The types involved
src.libs.ddd.repository_interface.Repository→src.libs.api.rest.collection_interface.Collection
- Direction
- libs.ddd.repository_interface uses libs.api.rest.collection_interface, so a change to libs.api.rest.collection_interface can break libs.ddd.repository_interface, while a change to libs.ddd.repository_interface can't break libs.api.rest.collection_interface.
- Position
- Below the diagonal: libs.ddd.repository_interface uses a module listed above it, which is the healthy direction.
13→4 modules.auth.api.rest.presentation.body.signup_body uses modules.auth.api.rest.presentation.body.login_body✕
- Connections
- 1 pair of types, where a type in modules.auth.api.rest.presentation.body.signup_body uses a type in modules.auth.api.rest.presentation.body.login_body.
- The types involved
src.modules.auth.api.rest.presentation.body.signup_body.SignupBody→src.modules.auth.api.rest.presentation.body.login_body.LoginBody
- Direction
- modules.auth.api.rest.presentation.body.signup_body uses modules.auth.api.rest.presentation.body.login_body, so a change to modules.auth.api.rest.presentation.body.login_body can break modules.auth.api.rest.presentation.body.signup_body, while a change to modules.auth.api.rest.presentation.body.signup_body can't break modules.auth.api.rest.presentation.body.login_body.
- Position
- Below the diagonal: modules.auth.api.rest.presentation.body.signup_body uses a module listed above it, which is the healthy direction.
14→5 modules.auth.api.rest.presentation.dto.jwt-user_dto uses modules.auth.api.rest.presentation.dto.auth-user_dto✕
- Connections
- 1 pair of types, where a type in modules.auth.api.rest.presentation.dto.jwt-user_dto uses a type in modules.auth.api.rest.presentation.dto.auth-user_dto.
- The types involved
src.modules.auth.api.rest.presentation.dto.jwt-user_dto.JwtUser→src.modules.auth.api.rest.presentation.dto.auth-user_dto.AuthUser
- Direction
- modules.auth.api.rest.presentation.dto.jwt-user_dto uses modules.auth.api.rest.presentation.dto.auth-user_dto, so a change to modules.auth.api.rest.presentation.dto.auth-user_dto can break modules.auth.api.rest.presentation.dto.jwt-user_dto, while a change to modules.auth.api.rest.presentation.dto.jwt-user_dto can't break modules.auth.api.rest.presentation.dto.auth-user_dto.
- Position
- Below the diagonal: modules.auth.api.rest.presentation.dto.jwt-user_dto uses a module listed above it, which is the healthy direction.
15→3 modules.auth.application.use-case.login_use-case uses libs.ddd.use-case_interface✕
- Connections
- 1 pair of types, where a type in modules.auth.application.use-case.login_use-case uses a type in libs.ddd.use-case_interface.
- The types involved
src.modules.auth.application.use-case.login_use-case.LoginUseCase→src.libs.ddd.use-case_interface.UseCase
- Direction
- modules.auth.application.use-case.login_use-case uses libs.ddd.use-case_interface, so a change to libs.ddd.use-case_interface can break modules.auth.application.use-case.login_use-case, while a change to modules.auth.application.use-case.login_use-case can't break libs.ddd.use-case_interface.
- Position
- Below the diagonal: modules.auth.application.use-case.login_use-case uses a module listed above it, which is the healthy direction.
15→4 modules.auth.application.use-case.login_use-case uses modules.auth.api.rest.presentation.body.login_body✕
- Connections
- 1 pair of types, where a type in modules.auth.application.use-case.login_use-case uses a type in modules.auth.api.rest.presentation.body.login_body.
- The types involved
src.modules.auth.application.use-case.login_use-case.LoginUseCase→src.modules.auth.api.rest.presentation.body.login_body.LoginBody
- Direction
- modules.auth.application.use-case.login_use-case uses modules.auth.api.rest.presentation.body.login_body, so a change to modules.auth.api.rest.presentation.body.login_body can break modules.auth.application.use-case.login_use-case, while a change to modules.auth.application.use-case.login_use-case can't break modules.auth.api.rest.presentation.body.login_body.
- Position
- Below the diagonal: modules.auth.application.use-case.login_use-case uses a module listed above it, which is the healthy direction.
15→5 modules.auth.application.use-case.login_use-case uses modules.auth.api.rest.presentation.dto.auth-user_dto✕
- Connections
- 1 pair of types, where a type in modules.auth.application.use-case.login_use-case uses a type in modules.auth.api.rest.presentation.dto.auth-user_dto.
- The types involved
src.modules.auth.application.use-case.login_use-case.LoginUseCase→src.modules.auth.api.rest.presentation.dto.auth-user_dto.AuthUser
- Direction
- modules.auth.application.use-case.login_use-case uses modules.auth.api.rest.presentation.dto.auth-user_dto, so a change to modules.auth.api.rest.presentation.dto.auth-user_dto can break modules.auth.application.use-case.login_use-case, while a change to modules.auth.application.use-case.login_use-case can't break modules.auth.api.rest.presentation.dto.auth-user_dto.
- Position
- Below the diagonal: modules.auth.application.use-case.login_use-case uses a module listed above it, which is the healthy direction.
16→7 modules.user.api.graphql.resolver.user_resolver uses modules.user.api.graphql.presentation.model.user_model✕
- Connections
- 1 pair of types, where a type in modules.user.api.graphql.resolver.user_resolver uses a type in modules.user.api.graphql.presentation.model.user_model.
- The types involved
src.modules.user.api.graphql.resolver.user_resolver.UserResolver→src.modules.user.api.graphql.presentation.model.user_model.UserModel
- Direction
- modules.user.api.graphql.resolver.user_resolver uses modules.user.api.graphql.presentation.model.user_model, so a change to modules.user.api.graphql.presentation.model.user_model can break modules.user.api.graphql.resolver.user_resolver, while a change to modules.user.api.graphql.resolver.user_resolver can't break modules.user.api.graphql.presentation.model.user_model.
- Position
- Below the diagonal: modules.user.api.graphql.resolver.user_resolver uses a module listed above it, which is the healthy direction.
17→9 modules.user.api.rest.presentation.params.user_params uses modules.user.api.rest.presentation.params.user-sort_params✕
- Connections
- 1 pair of types, where a type in modules.user.api.rest.presentation.params.user_params uses a type in modules.user.api.rest.presentation.params.user-sort_params.
- The types involved
src.modules.user.api.rest.presentation.params.user_params.UserParams→src.modules.user.api.rest.presentation.params.user-sort_params.UserSortParams
- Direction
- modules.user.api.rest.presentation.params.user_params uses modules.user.api.rest.presentation.params.user-sort_params, so a change to modules.user.api.rest.presentation.params.user-sort_params can break modules.user.api.rest.presentation.params.user_params, while a change to modules.user.api.rest.presentation.params.user_params can't break modules.user.api.rest.presentation.params.user-sort_params.
- Position
- Below the diagonal: modules.user.api.rest.presentation.params.user_params uses a module listed above it, which is the healthy direction.
18→10 modules.user.application.command.create-user_command uses modules.user.domain.value-object.user-role_enum✕
- Connections
- 1 pair of types, where a type in modules.user.application.command.create-user_command uses a type in modules.user.domain.value-object.user-role_enum.
- The types involved
src.modules.user.application.command.create-user_command.CreateUserCommand→src.modules.user.domain.value-object.user-role_enum.UserRole
- Direction
- modules.user.application.command.create-user_command uses modules.user.domain.value-object.user-role_enum, so a change to modules.user.domain.value-object.user-role_enum can break modules.user.application.command.create-user_command, while a change to modules.user.application.command.create-user_command can't break modules.user.domain.value-object.user-role_enum.
- Position
- Below the diagonal: modules.user.application.command.create-user_command uses a module listed above it, which is the healthy direction.
19→10 modules.user.domain.entity.user_entity uses modules.user.domain.value-object.user-role_enum✕
- Connections
- 1 pair of types, where a type in modules.user.domain.entity.user_entity uses a type in modules.user.domain.value-object.user-role_enum.
- The types involved
src.modules.user.domain.entity.user_entity.UserProps→src.modules.user.domain.value-object.user-role_enum.UserRole
- Direction
- modules.user.domain.entity.user_entity uses modules.user.domain.value-object.user-role_enum, so a change to modules.user.domain.value-object.user-role_enum can break modules.user.domain.entity.user_entity, while a change to modules.user.domain.entity.user_entity can't break modules.user.domain.value-object.user-role_enum.
- Position
- Below the diagonal: modules.user.domain.entity.user_entity uses a module listed above it, which is the healthy direction.
20→10 modules.user.infrastructure.database.entity.user_entity uses modules.user.domain.value-object.user-role_enum✕
- Connections
- 1 pair of types, where a type in modules.user.infrastructure.database.entity.user_entity uses a type in modules.user.domain.value-object.user-role_enum.
- The types involved
src.modules.user.infrastructure.database.entity.user_entity.UserEntity→src.modules.user.domain.value-object.user-role_enum.UserRole
- Direction
- modules.user.infrastructure.database.entity.user_entity uses modules.user.domain.value-object.user-role_enum, so a change to modules.user.domain.value-object.user-role_enum can break modules.user.infrastructure.database.entity.user_entity, while a change to modules.user.infrastructure.database.entity.user_entity can't break modules.user.domain.value-object.user-role_enum.
- Position
- Below the diagonal: modules.user.infrastructure.database.entity.user_entity uses a module listed above it, which is the healthy direction.
21→1 libs.ddd.mikro-orm-repository_abstract uses libs.api.rest.collection_interface✕
- Connections
- 1 pair of types, where a type in libs.ddd.mikro-orm-repository_abstract uses a type in libs.api.rest.collection_interface.
- The types involved
src.libs.ddd.mikro-orm-repository_abstract.MikroOrmRepository→src.libs.api.rest.collection_interface.Collection
- Direction
- libs.ddd.mikro-orm-repository_abstract uses libs.api.rest.collection_interface, so a change to libs.api.rest.collection_interface can break libs.ddd.mikro-orm-repository_abstract, while a change to libs.ddd.mikro-orm-repository_abstract can't break libs.api.rest.collection_interface.
- Position
- Below the diagonal: libs.ddd.mikro-orm-repository_abstract uses a module listed above it, which is the healthy direction.
21→12 libs.ddd.mikro-orm-repository_abstract uses libs.ddd.repository_interface✕
- Connections
- 1 pair of types, where a type in libs.ddd.mikro-orm-repository_abstract uses a type in libs.ddd.repository_interface.
- The types involved
src.libs.ddd.mikro-orm-repository_abstract.MikroOrmRepository→src.libs.ddd.repository_interface.Repository
- Direction
- libs.ddd.mikro-orm-repository_abstract uses libs.ddd.repository_interface, so a change to libs.ddd.repository_interface can break libs.ddd.mikro-orm-repository_abstract, while a change to libs.ddd.mikro-orm-repository_abstract can't break libs.ddd.repository_interface.
- Position
- Below the diagonal: libs.ddd.mikro-orm-repository_abstract uses a module listed above it, which is the healthy direction.
22→5 modules.auth.application.service.jwt-auth-service_interface uses modules.auth.api.rest.presentation.dto.auth-user_dto✕
- Connections
- 1 pair of types, where a type in modules.auth.application.service.jwt-auth-service_interface uses a type in modules.auth.api.rest.presentation.dto.auth-user_dto.
- The types involved
src.modules.auth.application.service.jwt-auth-service_interface.JwtAuthService→src.modules.auth.api.rest.presentation.dto.auth-user_dto.AuthUser
- Direction
- modules.auth.application.service.jwt-auth-service_interface uses modules.auth.api.rest.presentation.dto.auth-user_dto, so a change to modules.auth.api.rest.presentation.dto.auth-user_dto can break modules.auth.application.service.jwt-auth-service_interface, while a change to modules.auth.application.service.jwt-auth-service_interface can't break modules.auth.api.rest.presentation.dto.auth-user_dto.
- Position
- Below the diagonal: modules.auth.application.service.jwt-auth-service_interface uses a module listed above it, which is the healthy direction.
22→14 modules.auth.application.service.jwt-auth-service_interface uses modules.auth.api.rest.presentation.dto.jwt-user_dto✕
- Connections
- 1 pair of types, where a type in modules.auth.application.service.jwt-auth-service_interface uses a type in modules.auth.api.rest.presentation.dto.jwt-user_dto.
- The types involved
src.modules.auth.application.service.jwt-auth-service_interface.JwtAuthService→src.modules.auth.api.rest.presentation.dto.jwt-user_dto.JwtUser
- Direction
- modules.auth.application.service.jwt-auth-service_interface uses modules.auth.api.rest.presentation.dto.jwt-user_dto, so a change to modules.auth.api.rest.presentation.dto.jwt-user_dto can break modules.auth.application.service.jwt-auth-service_interface, while a change to modules.auth.application.service.jwt-auth-service_interface can't break modules.auth.api.rest.presentation.dto.jwt-user_dto.
- Position
- Below the diagonal: modules.auth.application.service.jwt-auth-service_interface uses a module listed above it, which is the healthy direction.
23→3 modules.auth.application.use-case.signup_use-case uses libs.ddd.use-case_interface✕
- Connections
- 1 pair of types, where a type in modules.auth.application.use-case.signup_use-case uses a type in libs.ddd.use-case_interface.
- The types involved
src.modules.auth.application.use-case.signup_use-case.SignupUseCase→src.libs.ddd.use-case_interface.UseCase
- Direction
- modules.auth.application.use-case.signup_use-case uses libs.ddd.use-case_interface, so a change to libs.ddd.use-case_interface can break modules.auth.application.use-case.signup_use-case, while a change to modules.auth.application.use-case.signup_use-case can't break libs.ddd.use-case_interface.
- Position
- Below the diagonal: modules.auth.application.use-case.signup_use-case uses a module listed above it, which is the healthy direction.
23→5 modules.auth.application.use-case.signup_use-case uses modules.auth.api.rest.presentation.dto.auth-user_dto✕
- Connections
- 1 pair of types, where a type in modules.auth.application.use-case.signup_use-case uses a type in modules.auth.api.rest.presentation.dto.auth-user_dto.
- The types involved
src.modules.auth.application.use-case.signup_use-case.SignupUseCase→src.modules.auth.api.rest.presentation.dto.auth-user_dto.AuthUser
- Direction
- modules.auth.application.use-case.signup_use-case uses modules.auth.api.rest.presentation.dto.auth-user_dto, so a change to modules.auth.api.rest.presentation.dto.auth-user_dto can break modules.auth.application.use-case.signup_use-case, while a change to modules.auth.application.use-case.signup_use-case can't break modules.auth.api.rest.presentation.dto.auth-user_dto.
- Position
- Below the diagonal: modules.auth.application.use-case.signup_use-case uses a module listed above it, which is the healthy direction.
23→13 modules.auth.application.use-case.signup_use-case uses modules.auth.api.rest.presentation.body.signup_body✕
- Connections
- 1 pair of types, where a type in modules.auth.application.use-case.signup_use-case uses a type in modules.auth.api.rest.presentation.body.signup_body.
- The types involved
src.modules.auth.application.use-case.signup_use-case.SignupUseCase→src.modules.auth.api.rest.presentation.body.signup_body.SignupBody
- Direction
- modules.auth.application.use-case.signup_use-case uses modules.auth.api.rest.presentation.body.signup_body, so a change to modules.auth.api.rest.presentation.body.signup_body can break modules.auth.application.use-case.signup_use-case, while a change to modules.auth.application.use-case.signup_use-case can't break modules.auth.api.rest.presentation.body.signup_body.
- Position
- Below the diagonal: modules.auth.application.use-case.signup_use-case uses a module listed above it, which is the healthy direction.
24→7 modules.user.api.graphql.presentation.model uses modules.user.api.graphql.presentation.model.user_model✕
- Connections
- 1 pair of types, where a type in modules.user.api.graphql.presentation.model uses a type in modules.user.api.graphql.presentation.model.user_model.
- The types involved
src.modules.user.api.graphql.presentation.model.user.model→src.modules.user.api.graphql.presentation.model.user_model.UserModel
- Direction
- modules.user.api.graphql.presentation.model uses modules.user.api.graphql.presentation.model.user_model, so a change to modules.user.api.graphql.presentation.model.user_model can break modules.user.api.graphql.presentation.model, while a change to modules.user.api.graphql.presentation.model can't break modules.user.api.graphql.presentation.model.user_model.
- Position
- Below the diagonal: modules.user.api.graphql.presentation.model uses a module listed above it, which is the healthy direction.
24→19 modules.user.api.graphql.presentation.model uses modules.user.domain.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.api.graphql.presentation.model uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.api.graphql.presentation.model.user.model→src.modules.user.domain.entity.user_entity.User
- Direction
- modules.user.api.graphql.presentation.model uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.api.graphql.presentation.model, while a change to modules.user.api.graphql.presentation.model can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.api.graphql.presentation.model uses a module listed above it, which is the healthy direction.
25→2 modules.user.api.rest.controller.user_controller uses libs.api.rest.paginated_response_dto✕
- Connections
- 1 pair of types, where a type in modules.user.api.rest.controller.user_controller uses a type in libs.api.rest.paginated_response_dto.
- The types involved
src.modules.user.api.rest.controller.user_controller.UserController→src.libs.api.rest.paginated_response_dto.PaginatedResponse
- Direction
- modules.user.api.rest.controller.user_controller uses libs.api.rest.paginated_response_dto, so a change to libs.api.rest.paginated_response_dto can break modules.user.api.rest.controller.user_controller, while a change to modules.user.api.rest.controller.user_controller can't break libs.api.rest.paginated_response_dto.
- Position
- Below the diagonal: modules.user.api.rest.controller.user_controller uses a module listed above it, which is the healthy direction.
25→8 modules.user.api.rest.controller.user_controller uses modules.user.api.rest.presentation.dto.user_dto✕
- Connections
- 1 pair of types, where a type in modules.user.api.rest.controller.user_controller uses a type in modules.user.api.rest.presentation.dto.user_dto.
- The types involved
src.modules.user.api.rest.controller.user_controller.UserController→src.modules.user.api.rest.presentation.dto.user_dto.UserDto
- Direction
- modules.user.api.rest.controller.user_controller uses modules.user.api.rest.presentation.dto.user_dto, so a change to modules.user.api.rest.presentation.dto.user_dto can break modules.user.api.rest.controller.user_controller, while a change to modules.user.api.rest.controller.user_controller can't break modules.user.api.rest.presentation.dto.user_dto.
- Position
- Below the diagonal: modules.user.api.rest.controller.user_controller uses a module listed above it, which is the healthy direction.
25→10 modules.user.api.rest.controller.user_controller uses modules.user.domain.value-object.user-role_enum✕
- Connections
- 1 pair of types, where a type in modules.user.api.rest.controller.user_controller uses a type in modules.user.domain.value-object.user-role_enum.
- The types involved
src.modules.user.api.rest.controller.user_controller.UserController→src.modules.user.domain.value-object.user-role_enum.UserRole
- Direction
- modules.user.api.rest.controller.user_controller uses modules.user.domain.value-object.user-role_enum, so a change to modules.user.domain.value-object.user-role_enum can break modules.user.api.rest.controller.user_controller, while a change to modules.user.api.rest.controller.user_controller can't break modules.user.domain.value-object.user-role_enum.
- Position
- Below the diagonal: modules.user.api.rest.controller.user_controller uses a module listed above it, which is the healthy direction.
25→17 modules.user.api.rest.controller.user_controller uses modules.user.api.rest.presentation.params.user_params✕
- Connections
- 1 pair of types, where a type in modules.user.api.rest.controller.user_controller uses a type in modules.user.api.rest.presentation.params.user_params.
- The types involved
src.modules.user.api.rest.controller.user_controller.UserController→src.modules.user.api.rest.presentation.params.user_params.UserParams
- Direction
- modules.user.api.rest.controller.user_controller uses modules.user.api.rest.presentation.params.user_params, so a change to modules.user.api.rest.presentation.params.user_params can break modules.user.api.rest.controller.user_controller, while a change to modules.user.api.rest.controller.user_controller can't break modules.user.api.rest.presentation.params.user_params.
- Position
- Below the diagonal: modules.user.api.rest.controller.user_controller uses a module listed above it, which is the healthy direction.
25→18 modules.user.api.rest.controller.user_controller uses modules.user.application.command.create-user_command✕
- Connections
- 1 pair of types, where a type in modules.user.api.rest.controller.user_controller uses a type in modules.user.application.command.create-user_command.
- The types involved
src.modules.user.api.rest.controller.user_controller.UserController→src.modules.user.application.command.create-user_command.CreateUserCommand
- Direction
- modules.user.api.rest.controller.user_controller uses modules.user.application.command.create-user_command, so a change to modules.user.application.command.create-user_command can break modules.user.api.rest.controller.user_controller, while a change to modules.user.api.rest.controller.user_controller can't break modules.user.application.command.create-user_command.
- Position
- Below the diagonal: modules.user.api.rest.controller.user_controller uses a module listed above it, which is the healthy direction.
26→8 modules.user.api.rest.presentation.dto uses modules.user.api.rest.presentation.dto.user_dto✕
- Connections
- 1 pair of types, where a type in modules.user.api.rest.presentation.dto uses a type in modules.user.api.rest.presentation.dto.user_dto.
- The types involved
src.modules.user.api.rest.presentation.dto.user.dto→src.modules.user.api.rest.presentation.dto.user_dto.UserDto
- Direction
- modules.user.api.rest.presentation.dto uses modules.user.api.rest.presentation.dto.user_dto, so a change to modules.user.api.rest.presentation.dto.user_dto can break modules.user.api.rest.presentation.dto, while a change to modules.user.api.rest.presentation.dto can't break modules.user.api.rest.presentation.dto.user_dto.
- Position
- Below the diagonal: modules.user.api.rest.presentation.dto uses a module listed above it, which is the healthy direction.
26→19 modules.user.api.rest.presentation.dto uses modules.user.domain.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.api.rest.presentation.dto uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.api.rest.presentation.dto.user.dto→src.modules.user.domain.entity.user_entity.User
- Direction
- modules.user.api.rest.presentation.dto uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.api.rest.presentation.dto, while a change to modules.user.api.rest.presentation.dto can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.api.rest.presentation.dto uses a module listed above it, which is the healthy direction.
27→19 modules.user.domain.event.created-user_event uses modules.user.domain.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.domain.event.created-user_event uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.domain.event.created-user_event.CreatedUserEvent→src.modules.user.domain.entity.user_entity.User
- Direction
- modules.user.domain.event.created-user_event uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.domain.event.created-user_event, while a change to modules.user.domain.event.created-user_event can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.domain.event.created-user_event uses a module listed above it, which is the healthy direction.
28→1 modules.user.domain.repository.user_repository_interface uses libs.api.rest.collection_interface✕
- Connections
- 1 pair of types, where a type in modules.user.domain.repository.user_repository_interface uses a type in libs.api.rest.collection_interface.
- The types involved
src.modules.user.domain.repository.user_repository_interface.UserRepository→src.libs.api.rest.collection_interface.Collection
- Direction
- modules.user.domain.repository.user_repository_interface uses libs.api.rest.collection_interface, so a change to libs.api.rest.collection_interface can break modules.user.domain.repository.user_repository_interface, while a change to modules.user.domain.repository.user_repository_interface can't break libs.api.rest.collection_interface.
- Position
- Below the diagonal: modules.user.domain.repository.user_repository_interface uses a module listed above it, which is the healthy direction.
28→19 modules.user.domain.repository.user_repository_interface uses modules.user.domain.entity.user_entity✕
- Connections
- 2 pairs of types, where a type in modules.user.domain.repository.user_repository_interface uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.domain.repository.user_repository_interface.UserRepository→src.modules.user.domain.entity.user_entity.Usersrc.modules.user.domain.repository.user_repository_interface.UserRepository→src.modules.user.domain.entity.user_entity.UserProps
- Direction
- modules.user.domain.repository.user_repository_interface uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.domain.repository.user_repository_interface, while a change to modules.user.domain.repository.user_repository_interface can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.domain.repository.user_repository_interface uses a module listed above it, which is the healthy direction.
29→19 modules.user.infrastructure.database.mapper.user_mapper uses modules.user.domain.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.infrastructure.database.mapper.user_mapper uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.infrastructure.database.mapper.user_mapper.UserMapper→src.modules.user.domain.entity.user_entity.User
- Direction
- modules.user.infrastructure.database.mapper.user_mapper uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.infrastructure.database.mapper.user_mapper, while a change to modules.user.infrastructure.database.mapper.user_mapper can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.infrastructure.database.mapper.user_mapper uses a module listed above it, which is the healthy direction.
29→20 modules.user.infrastructure.database.mapper.user_mapper uses modules.user.infrastructure.database.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.infrastructure.database.mapper.user_mapper uses a type in modules.user.infrastructure.database.entity.user_entity.
- The types involved
src.modules.user.infrastructure.database.mapper.user_mapper.UserMapper→src.modules.user.infrastructure.database.entity.user_entity.UserEntity
- Direction
- modules.user.infrastructure.database.mapper.user_mapper uses modules.user.infrastructure.database.entity.user_entity, so a change to modules.user.infrastructure.database.entity.user_entity can break modules.user.infrastructure.database.mapper.user_mapper, while a change to modules.user.infrastructure.database.mapper.user_mapper can't break modules.user.infrastructure.database.entity.user_entity.
- Position
- Below the diagonal: modules.user.infrastructure.database.mapper.user_mapper uses a module listed above it, which is the healthy direction.
30→3 modules.auth.api.rest.controller.auth_controller uses libs.ddd.use-case_interface✕
- Connections
- 1 pair of types, where a type in modules.auth.api.rest.controller.auth_controller uses a type in libs.ddd.use-case_interface.
- The types involved
src.modules.auth.api.rest.controller.auth_controller.AuthController→src.libs.ddd.use-case_interface.UseCase
- Direction
- modules.auth.api.rest.controller.auth_controller uses libs.ddd.use-case_interface, so a change to libs.ddd.use-case_interface can break modules.auth.api.rest.controller.auth_controller, while a change to modules.auth.api.rest.controller.auth_controller can't break libs.ddd.use-case_interface.
- Position
- Below the diagonal: modules.auth.api.rest.controller.auth_controller uses a module listed above it, which is the healthy direction.
30→4 modules.auth.api.rest.controller.auth_controller uses modules.auth.api.rest.presentation.body.login_body✕
- Connections
- 1 pair of types, where a type in modules.auth.api.rest.controller.auth_controller uses a type in modules.auth.api.rest.presentation.body.login_body.
- The types involved
src.modules.auth.api.rest.controller.auth_controller.AuthController→src.modules.auth.api.rest.presentation.body.login_body.LoginBody
- Direction
- modules.auth.api.rest.controller.auth_controller uses modules.auth.api.rest.presentation.body.login_body, so a change to modules.auth.api.rest.presentation.body.login_body can break modules.auth.api.rest.controller.auth_controller, while a change to modules.auth.api.rest.controller.auth_controller can't break modules.auth.api.rest.presentation.body.login_body.
- Position
- Below the diagonal: modules.auth.api.rest.controller.auth_controller uses a module listed above it, which is the healthy direction.
30→5 modules.auth.api.rest.controller.auth_controller uses modules.auth.api.rest.presentation.dto.auth-user_dto✕
- Connections
- 1 pair of types, where a type in modules.auth.api.rest.controller.auth_controller uses a type in modules.auth.api.rest.presentation.dto.auth-user_dto.
- The types involved
src.modules.auth.api.rest.controller.auth_controller.AuthController→src.modules.auth.api.rest.presentation.dto.auth-user_dto.AuthUser
- Direction
- modules.auth.api.rest.controller.auth_controller uses modules.auth.api.rest.presentation.dto.auth-user_dto, so a change to modules.auth.api.rest.presentation.dto.auth-user_dto can break modules.auth.api.rest.controller.auth_controller, while a change to modules.auth.api.rest.controller.auth_controller can't break modules.auth.api.rest.presentation.dto.auth-user_dto.
- Position
- Below the diagonal: modules.auth.api.rest.controller.auth_controller uses a module listed above it, which is the healthy direction.
30→13 modules.auth.api.rest.controller.auth_controller uses modules.auth.api.rest.presentation.body.signup_body✕
- Connections
- 1 pair of types, where a type in modules.auth.api.rest.controller.auth_controller uses a type in modules.auth.api.rest.presentation.body.signup_body.
- The types involved
src.modules.auth.api.rest.controller.auth_controller.AuthController→src.modules.auth.api.rest.presentation.body.signup_body.SignupBody
- Direction
- modules.auth.api.rest.controller.auth_controller uses modules.auth.api.rest.presentation.body.signup_body, so a change to modules.auth.api.rest.presentation.body.signup_body can break modules.auth.api.rest.controller.auth_controller, while a change to modules.auth.api.rest.controller.auth_controller can't break modules.auth.api.rest.presentation.body.signup_body.
- Position
- Below the diagonal: modules.auth.api.rest.controller.auth_controller uses a module listed above it, which is the healthy direction.
30→14 modules.auth.api.rest.controller.auth_controller uses modules.auth.api.rest.presentation.dto.jwt-user_dto✕
- Connections
- 1 pair of types, where a type in modules.auth.api.rest.controller.auth_controller uses a type in modules.auth.api.rest.presentation.dto.jwt-user_dto.
- The types involved
src.modules.auth.api.rest.controller.auth_controller.AuthController→src.modules.auth.api.rest.presentation.dto.jwt-user_dto.JwtUser
- Direction
- modules.auth.api.rest.controller.auth_controller uses modules.auth.api.rest.presentation.dto.jwt-user_dto, so a change to modules.auth.api.rest.presentation.dto.jwt-user_dto can break modules.auth.api.rest.controller.auth_controller, while a change to modules.auth.api.rest.controller.auth_controller can't break modules.auth.api.rest.presentation.dto.jwt-user_dto.
- Position
- Below the diagonal: modules.auth.api.rest.controller.auth_controller uses a module listed above it, which is the healthy direction.
30→22 modules.auth.api.rest.controller.auth_controller uses modules.auth.application.service.jwt-auth-service_interface✕
- Connections
- 1 pair of types, where a type in modules.auth.api.rest.controller.auth_controller uses a type in modules.auth.application.service.jwt-auth-service_interface.
- The types involved
src.modules.auth.api.rest.controller.auth_controller.AuthController→src.modules.auth.application.service.jwt-auth-service_interface.JwtAuthService
- Direction
- modules.auth.api.rest.controller.auth_controller uses modules.auth.application.service.jwt-auth-service_interface, so a change to modules.auth.application.service.jwt-auth-service_interface can break modules.auth.api.rest.controller.auth_controller, while a change to modules.auth.api.rest.controller.auth_controller can't break modules.auth.application.service.jwt-auth-service_interface.
- Position
- Below the diagonal: modules.auth.api.rest.controller.auth_controller uses a module listed above it, which is the healthy direction.
31→5 modules.auth.infrastructure.jwt.jwt_service uses modules.auth.api.rest.presentation.dto.auth-user_dto✕
- Connections
- 1 pair of types, where a type in modules.auth.infrastructure.jwt.jwt_service uses a type in modules.auth.api.rest.presentation.dto.auth-user_dto.
- The types involved
src.modules.auth.infrastructure.jwt.jwt_service.JwtService→src.modules.auth.api.rest.presentation.dto.auth-user_dto.AuthUser
- Direction
- modules.auth.infrastructure.jwt.jwt_service uses modules.auth.api.rest.presentation.dto.auth-user_dto, so a change to modules.auth.api.rest.presentation.dto.auth-user_dto can break modules.auth.infrastructure.jwt.jwt_service, while a change to modules.auth.infrastructure.jwt.jwt_service can't break modules.auth.api.rest.presentation.dto.auth-user_dto.
- Position
- Below the diagonal: modules.auth.infrastructure.jwt.jwt_service uses a module listed above it, which is the healthy direction.
31→14 modules.auth.infrastructure.jwt.jwt_service uses modules.auth.api.rest.presentation.dto.jwt-user_dto✕
- Connections
- 1 pair of types, where a type in modules.auth.infrastructure.jwt.jwt_service uses a type in modules.auth.api.rest.presentation.dto.jwt-user_dto.
- The types involved
src.modules.auth.infrastructure.jwt.jwt_service.JwtService→src.modules.auth.api.rest.presentation.dto.jwt-user_dto.JwtUser
- Direction
- modules.auth.infrastructure.jwt.jwt_service uses modules.auth.api.rest.presentation.dto.jwt-user_dto, so a change to modules.auth.api.rest.presentation.dto.jwt-user_dto can break modules.auth.infrastructure.jwt.jwt_service, while a change to modules.auth.infrastructure.jwt.jwt_service can't break modules.auth.api.rest.presentation.dto.jwt-user_dto.
- Position
- Below the diagonal: modules.auth.infrastructure.jwt.jwt_service uses a module listed above it, which is the healthy direction.
31→22 modules.auth.infrastructure.jwt.jwt_service uses modules.auth.application.service.jwt-auth-service_interface✕
- Connections
- 1 pair of types, where a type in modules.auth.infrastructure.jwt.jwt_service uses a type in modules.auth.application.service.jwt-auth-service_interface.
- The types involved
src.modules.auth.infrastructure.jwt.jwt_service.JwtService→src.modules.auth.application.service.jwt-auth-service_interface.JwtAuthService
- Direction
- modules.auth.infrastructure.jwt.jwt_service uses modules.auth.application.service.jwt-auth-service_interface, so a change to modules.auth.application.service.jwt-auth-service_interface can break modules.auth.infrastructure.jwt.jwt_service, while a change to modules.auth.infrastructure.jwt.jwt_service can't break modules.auth.application.service.jwt-auth-service_interface.
- Position
- Below the diagonal: modules.auth.infrastructure.jwt.jwt_service uses a module listed above it, which is the healthy direction.
32→6 modules.communication.application.handler.event.created-user_handler uses modules.communication.application.service.email_service_interface✕
- Connections
- 1 pair of types, where a type in modules.communication.application.handler.event.created-user_handler uses a type in modules.communication.application.service.email_service_interface.
- The types involved
src.modules.communication.application.handler.event.created-user_handler.CreatedUserHandler→src.modules.communication.application.service.email_service_interface.EmailService
- Direction
- modules.communication.application.handler.event.created-user_handler uses modules.communication.application.service.email_service_interface, so a change to modules.communication.application.service.email_service_interface can break modules.communication.application.handler.event.created-user_handler, while a change to modules.communication.application.handler.event.created-user_handler can't break modules.communication.application.service.email_service_interface.
- Position
- Below the diagonal: modules.communication.application.handler.event.created-user_handler uses a module listed above it, which is the healthy direction.
32→27 modules.communication.application.handler.event.created-user_handler uses modules.user.domain.event.created-user_event✕
- Connections
- 1 pair of types, where a type in modules.communication.application.handler.event.created-user_handler uses a type in modules.user.domain.event.created-user_event.
- The types involved
src.modules.communication.application.handler.event.created-user_handler.CreatedUserHandler→src.modules.user.domain.event.created-user_event.CreatedUserEvent
- Direction
- modules.communication.application.handler.event.created-user_handler uses modules.user.domain.event.created-user_event, so a change to modules.user.domain.event.created-user_event can break modules.communication.application.handler.event.created-user_handler, while a change to modules.communication.application.handler.event.created-user_handler can't break modules.user.domain.event.created-user_event.
- Position
- Below the diagonal: modules.communication.application.handler.event.created-user_handler uses a module listed above it, which is the healthy direction.
33→28 modules.user.application.handler.query.check-auth-user-by-id_handler uses modules.user.domain.repository.user_repository_interface✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.query.check-auth-user-by-id_handler uses a type in modules.user.domain.repository.user_repository_interface.
- The types involved
src.modules.user.application.handler.query.check-auth-user-by-id_handler.CheckAuthUserByIdHandler→src.modules.user.domain.repository.user_repository_interface.UserRepository
- Direction
- modules.user.application.handler.query.check-auth-user-by-id_handler uses modules.user.domain.repository.user_repository_interface, so a change to modules.user.domain.repository.user_repository_interface can break modules.user.application.handler.query.check-auth-user-by-id_handler, while a change to modules.user.application.handler.query.check-auth-user-by-id_handler can't break modules.user.domain.repository.user_repository_interface.
- Position
- Below the diagonal: modules.user.application.handler.query.check-auth-user-by-id_handler uses a module listed above it, which is the healthy direction.
34→1 modules.user.application.handler.query.get-all-users_handler uses libs.api.rest.collection_interface✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.query.get-all-users_handler uses a type in libs.api.rest.collection_interface.
- The types involved
src.modules.user.application.handler.query.get-all-users_handler.GetAllUsersHandler→src.libs.api.rest.collection_interface.Collection
- Direction
- modules.user.application.handler.query.get-all-users_handler uses libs.api.rest.collection_interface, so a change to libs.api.rest.collection_interface can break modules.user.application.handler.query.get-all-users_handler, while a change to modules.user.application.handler.query.get-all-users_handler can't break libs.api.rest.collection_interface.
- Position
- Below the diagonal: modules.user.application.handler.query.get-all-users_handler uses a module listed above it, which is the healthy direction.
34→19 modules.user.application.handler.query.get-all-users_handler uses modules.user.domain.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.query.get-all-users_handler uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.application.handler.query.get-all-users_handler.GetAllUsersHandler→src.modules.user.domain.entity.user_entity.User
- Direction
- modules.user.application.handler.query.get-all-users_handler uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.application.handler.query.get-all-users_handler, while a change to modules.user.application.handler.query.get-all-users_handler can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.application.handler.query.get-all-users_handler uses a module listed above it, which is the healthy direction.
34→28 modules.user.application.handler.query.get-all-users_handler uses modules.user.domain.repository.user_repository_interface✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.query.get-all-users_handler uses a type in modules.user.domain.repository.user_repository_interface.
- The types involved
src.modules.user.application.handler.query.get-all-users_handler.GetAllUsersHandler→src.modules.user.domain.repository.user_repository_interface.UserRepository
- Direction
- modules.user.application.handler.query.get-all-users_handler uses modules.user.domain.repository.user_repository_interface, so a change to modules.user.domain.repository.user_repository_interface can break modules.user.application.handler.query.get-all-users_handler, while a change to modules.user.application.handler.query.get-all-users_handler can't break modules.user.domain.repository.user_repository_interface.
- Position
- Below the diagonal: modules.user.application.handler.query.get-all-users_handler uses a module listed above it, which is the healthy direction.
35→19 modules.user.application.handler.query.get-auth-user-by-email_handler uses modules.user.domain.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.query.get-auth-user-by-email_handler uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.application.handler.query.get-auth-user-by-email_handler.GetAuthUserByEmailHandler→src.modules.user.domain.entity.user_entity.User
- Direction
- modules.user.application.handler.query.get-auth-user-by-email_handler uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.application.handler.query.get-auth-user-by-email_handler, while a change to modules.user.application.handler.query.get-auth-user-by-email_handler can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.application.handler.query.get-auth-user-by-email_handler uses a module listed above it, which is the healthy direction.
35→28 modules.user.application.handler.query.get-auth-user-by-email_handler uses modules.user.domain.repository.user_repository_interface✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.query.get-auth-user-by-email_handler uses a type in modules.user.domain.repository.user_repository_interface.
- The types involved
src.modules.user.application.handler.query.get-auth-user-by-email_handler.GetAuthUserByEmailHandler→src.modules.user.domain.repository.user_repository_interface.UserRepository
- Direction
- modules.user.application.handler.query.get-auth-user-by-email_handler uses modules.user.domain.repository.user_repository_interface, so a change to modules.user.domain.repository.user_repository_interface can break modules.user.application.handler.query.get-auth-user-by-email_handler, while a change to modules.user.application.handler.query.get-auth-user-by-email_handler can't break modules.user.domain.repository.user_repository_interface.
- Position
- Below the diagonal: modules.user.application.handler.query.get-auth-user-by-email_handler uses a module listed above it, which is the healthy direction.
36→19 modules.user.application.handler.query.get-user-by-id_handler uses modules.user.domain.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.query.get-user-by-id_handler uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.application.handler.query.get-user-by-id_handler.GetUserByIdHandler→src.modules.user.domain.entity.user_entity.User
- Direction
- modules.user.application.handler.query.get-user-by-id_handler uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.application.handler.query.get-user-by-id_handler, while a change to modules.user.application.handler.query.get-user-by-id_handler can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.application.handler.query.get-user-by-id_handler uses a module listed above it, which is the healthy direction.
36→28 modules.user.application.handler.query.get-user-by-id_handler uses modules.user.domain.repository.user_repository_interface✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.query.get-user-by-id_handler uses a type in modules.user.domain.repository.user_repository_interface.
- The types involved
src.modules.user.application.handler.query.get-user-by-id_handler.GetUserByIdHandler→src.modules.user.domain.repository.user_repository_interface.UserRepository
- Direction
- modules.user.application.handler.query.get-user-by-id_handler uses modules.user.domain.repository.user_repository_interface, so a change to modules.user.domain.repository.user_repository_interface can break modules.user.application.handler.query.get-user-by-id_handler, while a change to modules.user.application.handler.query.get-user-by-id_handler can't break modules.user.domain.repository.user_repository_interface.
- Position
- Below the diagonal: modules.user.application.handler.query.get-user-by-id_handler uses a module listed above it, which is the healthy direction.
37→3 modules.user.application.use-case.create-user_use-case uses libs.ddd.use-case_interface✕
- Connections
- 1 pair of types, where a type in modules.user.application.use-case.create-user_use-case uses a type in libs.ddd.use-case_interface.
- The types involved
src.modules.user.application.use-case.create-user_use-case.CreateUserUseCase→src.libs.ddd.use-case_interface.UseCase
- Direction
- modules.user.application.use-case.create-user_use-case uses libs.ddd.use-case_interface, so a change to libs.ddd.use-case_interface can break modules.user.application.use-case.create-user_use-case, while a change to modules.user.application.use-case.create-user_use-case can't break libs.ddd.use-case_interface.
- Position
- Below the diagonal: modules.user.application.use-case.create-user_use-case uses a module listed above it, which is the healthy direction.
37→19 modules.user.application.use-case.create-user_use-case uses modules.user.domain.entity.user_entity✕
- Connections
- 2 pairs of types, where a type in modules.user.application.use-case.create-user_use-case uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.application.use-case.create-user_use-case.CreateUserUseCase→src.modules.user.domain.entity.user_entity.Usersrc.modules.user.application.use-case.create-user_use-case.CreateUserUseCase→src.modules.user.domain.entity.user_entity.UserProps
- Direction
- modules.user.application.use-case.create-user_use-case uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.application.use-case.create-user_use-case, while a change to modules.user.application.use-case.create-user_use-case can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.application.use-case.create-user_use-case uses a module listed above it, which is the healthy direction.
37→28 modules.user.application.use-case.create-user_use-case uses modules.user.domain.repository.user_repository_interface✕
- Connections
- 1 pair of types, where a type in modules.user.application.use-case.create-user_use-case uses a type in modules.user.domain.repository.user_repository_interface.
- The types involved
src.modules.user.application.use-case.create-user_use-case.CreateUserUseCase→src.modules.user.domain.repository.user_repository_interface.UserRepository
- Direction
- modules.user.application.use-case.create-user_use-case uses modules.user.domain.repository.user_repository_interface, so a change to modules.user.domain.repository.user_repository_interface can break modules.user.application.use-case.create-user_use-case, while a change to modules.user.application.use-case.create-user_use-case can't break modules.user.domain.repository.user_repository_interface.
- Position
- Below the diagonal: modules.user.application.use-case.create-user_use-case uses a module listed above it, which is the healthy direction.
38→1 modules.user.infrastructure.database.repository.user_repository uses libs.api.rest.collection_interface✕
- Connections
- 1 pair of types, where a type in modules.user.infrastructure.database.repository.user_repository uses a type in libs.api.rest.collection_interface.
- The types involved
src.modules.user.infrastructure.database.repository.user_repository.UserRepositoryImpl→src.libs.api.rest.collection_interface.Collection
- Direction
- modules.user.infrastructure.database.repository.user_repository uses libs.api.rest.collection_interface, so a change to libs.api.rest.collection_interface can break modules.user.infrastructure.database.repository.user_repository, while a change to modules.user.infrastructure.database.repository.user_repository can't break libs.api.rest.collection_interface.
- Position
- Below the diagonal: modules.user.infrastructure.database.repository.user_repository uses a module listed above it, which is the healthy direction.
38→17 modules.user.infrastructure.database.repository.user_repository uses modules.user.api.rest.presentation.params.user_params✕
- Connections
- 1 pair of types, where a type in modules.user.infrastructure.database.repository.user_repository uses a type in modules.user.api.rest.presentation.params.user_params.
- The types involved
src.modules.user.infrastructure.database.repository.user_repository.UserRepositoryImpl→src.modules.user.api.rest.presentation.params.user_params.UserParams
- Direction
- modules.user.infrastructure.database.repository.user_repository uses modules.user.api.rest.presentation.params.user_params, so a change to modules.user.api.rest.presentation.params.user_params can break modules.user.infrastructure.database.repository.user_repository, while a change to modules.user.infrastructure.database.repository.user_repository can't break modules.user.api.rest.presentation.params.user_params.
- Position
- Below the diagonal: modules.user.infrastructure.database.repository.user_repository uses a module listed above it, which is the healthy direction.
38→19 modules.user.infrastructure.database.repository.user_repository uses modules.user.domain.entity.user_entity✕
- Connections
- 2 pairs of types, where a type in modules.user.infrastructure.database.repository.user_repository uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.infrastructure.database.repository.user_repository.UserRepositoryImpl→src.modules.user.domain.entity.user_entity.Usersrc.modules.user.infrastructure.database.repository.user_repository.UserRepositoryImpl→src.modules.user.domain.entity.user_entity.UserProps
- Direction
- modules.user.infrastructure.database.repository.user_repository uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.infrastructure.database.repository.user_repository, while a change to modules.user.infrastructure.database.repository.user_repository can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.infrastructure.database.repository.user_repository uses a module listed above it, which is the healthy direction.
38→20 modules.user.infrastructure.database.repository.user_repository uses modules.user.infrastructure.database.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.infrastructure.database.repository.user_repository uses a type in modules.user.infrastructure.database.entity.user_entity.
- The types involved
src.modules.user.infrastructure.database.repository.user_repository.UserRepositoryImpl→src.modules.user.infrastructure.database.entity.user_entity.UserEntity
- Direction
- modules.user.infrastructure.database.repository.user_repository uses modules.user.infrastructure.database.entity.user_entity, so a change to modules.user.infrastructure.database.entity.user_entity can break modules.user.infrastructure.database.repository.user_repository, while a change to modules.user.infrastructure.database.repository.user_repository can't break modules.user.infrastructure.database.entity.user_entity.
- Position
- Below the diagonal: modules.user.infrastructure.database.repository.user_repository uses a module listed above it, which is the healthy direction.
38→28 modules.user.infrastructure.database.repository.user_repository uses modules.user.domain.repository.user_repository_interface✕
- Connections
- 1 pair of types, where a type in modules.user.infrastructure.database.repository.user_repository uses a type in modules.user.domain.repository.user_repository_interface.
- The types involved
src.modules.user.infrastructure.database.repository.user_repository.UserRepositoryImpl→src.modules.user.domain.repository.user_repository_interface.UserRepository
- Direction
- modules.user.infrastructure.database.repository.user_repository uses modules.user.domain.repository.user_repository_interface, so a change to modules.user.domain.repository.user_repository_interface can break modules.user.infrastructure.database.repository.user_repository, while a change to modules.user.infrastructure.database.repository.user_repository can't break modules.user.domain.repository.user_repository_interface.
- Position
- Below the diagonal: modules.user.infrastructure.database.repository.user_repository uses a module listed above it, which is the healthy direction.
38→29 modules.user.infrastructure.database.repository.user_repository uses modules.user.infrastructure.database.mapper.user_mapper✕
- Connections
- 1 pair of types, where a type in modules.user.infrastructure.database.repository.user_repository uses a type in modules.user.infrastructure.database.mapper.user_mapper.
- The types involved
src.modules.user.infrastructure.database.repository.user_repository.UserRepositoryImpl→src.modules.user.infrastructure.database.mapper.user_mapper.UserMapper
- Direction
- modules.user.infrastructure.database.repository.user_repository uses modules.user.infrastructure.database.mapper.user_mapper, so a change to modules.user.infrastructure.database.mapper.user_mapper can break modules.user.infrastructure.database.repository.user_repository, while a change to modules.user.infrastructure.database.repository.user_repository can't break modules.user.infrastructure.database.mapper.user_mapper.
- Position
- Below the diagonal: modules.user.infrastructure.database.repository.user_repository uses a module listed above it, which is the healthy direction.
39→18 modules.user.application.handler.command.create-user_handler uses modules.user.application.command.create-user_command✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.command.create-user_handler uses a type in modules.user.application.command.create-user_command.
- The types involved
src.modules.user.application.handler.command.create-user_handler.CreateUserHandler→src.modules.user.application.command.create-user_command.CreateUserCommand
- Direction
- modules.user.application.handler.command.create-user_handler uses modules.user.application.command.create-user_command, so a change to modules.user.application.command.create-user_command can break modules.user.application.handler.command.create-user_handler, while a change to modules.user.application.handler.command.create-user_handler can't break modules.user.application.command.create-user_command.
- Position
- Below the diagonal: modules.user.application.handler.command.create-user_handler uses a module listed above it, which is the healthy direction.
39→19 modules.user.application.handler.command.create-user_handler uses modules.user.domain.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.command.create-user_handler uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.application.handler.command.create-user_handler.CreateUserHandler→src.modules.user.domain.entity.user_entity.User
- Direction
- modules.user.application.handler.command.create-user_handler uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.application.handler.command.create-user_handler, while a change to modules.user.application.handler.command.create-user_handler can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.application.handler.command.create-user_handler uses a module listed above it, which is the healthy direction.
39→37 modules.user.application.handler.command.create-user_handler uses modules.user.application.use-case.create-user_use-case✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.command.create-user_handler uses a type in modules.user.application.use-case.create-user_use-case.
- The types involved
src.modules.user.application.handler.command.create-user_handler.CreateUserHandler→src.modules.user.application.use-case.create-user_use-case.CreateUserUseCase
- Direction
- modules.user.application.handler.command.create-user_handler uses modules.user.application.use-case.create-user_use-case, so a change to modules.user.application.use-case.create-user_use-case can break modules.user.application.handler.command.create-user_handler, while a change to modules.user.application.handler.command.create-user_handler can't break modules.user.application.use-case.create-user_use-case.
- Position
- Below the diagonal: modules.user.application.handler.command.create-user_handler uses a module listed above it, which is the healthy direction.
40→19 modules.user.application.handler.command.register-user_handler uses modules.user.domain.entity.user_entity✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.command.register-user_handler uses a type in modules.user.domain.entity.user_entity.
- The types involved
src.modules.user.application.handler.command.register-user_handler.RegisterUserHandler→src.modules.user.domain.entity.user_entity.User
- Direction
- modules.user.application.handler.command.register-user_handler uses modules.user.domain.entity.user_entity, so a change to modules.user.domain.entity.user_entity can break modules.user.application.handler.command.register-user_handler, while a change to modules.user.application.handler.command.register-user_handler can't break modules.user.domain.entity.user_entity.
- Position
- Below the diagonal: modules.user.application.handler.command.register-user_handler uses a module listed above it, which is the healthy direction.
40→37 modules.user.application.handler.command.register-user_handler uses modules.user.application.use-case.create-user_use-case✕
- Connections
- 1 pair of types, where a type in modules.user.application.handler.command.register-user_handler uses a type in modules.user.application.use-case.create-user_use-case.
- The types involved
src.modules.user.application.handler.command.register-user_handler.RegisterUserHandler→src.modules.user.application.use-case.create-user_use-case.CreateUserUseCase
- Direction
- modules.user.application.handler.command.register-user_handler uses modules.user.application.use-case.create-user_use-case, so a change to modules.user.application.use-case.create-user_use-case can break modules.user.application.handler.command.register-user_handler, while a change to modules.user.application.handler.command.register-user_handler can't break modules.user.application.use-case.create-user_use-case.
- Position
- Below the diagonal: modules.user.application.handler.command.register-user_handler 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 | 86 | High / Critical |
| A05:2025 — Injection | 12 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2); Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with user.repository.ts, jwt.service.ts, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). | +2.7 pts | Low | Secret Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.7 pts | Low | ADR Quality |
| Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with user.repository.ts, jwt.service.ts, REDACTED. | +2.5 pts | Low | Knowledge Freshness |
| Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. | +2.5 pts | Low | Test Distribution |
| Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / Secret Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps. | +2.1 pts | Medium | Data Protection |
| Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters). | +1.8 pts | Medium | Encapsulated state |
| 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. | +1.8 pts | Medium | Architecture documentation |
| Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services. | +1.4 pts | Medium | Rich vs anemic model |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| package.json | 7.2 | Mixed | Dependency Hygiene: Deprecated: @apollo/server |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 80 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 80 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, 144 of 163 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
- 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 scored — the JavaScript/TypeScript suite (jest via `npm ci --ignore-scripts` in the repository root (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
- 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 253 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 — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- 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.
- P8 Schema migrations — 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
- 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- 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.
D6 · Cohesion (LCOM4)
0 of 4 classes have LCOM4 above 3.
D9 · Test Distribution
11 test methods: 0 unit, 0 integration, 0 BDD, 11 e2e. The JavaScript/TypeScript suite contributes 11 `it`/`test` case(s) across 3 test file(s) declaring at least one; its tier split is read from package names and paths only.
What to do
- Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 11 tests.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 1782 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (4 contexts). Contexts: auth, communication, health, user.
D26 · Project Cohesion
0 of 1 build units (npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
12 finding(s): 0 critical, 7 high, 5 medium, 0 low. 5 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 5 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 (5 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
80 finding(s): 8 critical, 46 high, 19 medium, 7 low.
What to do
- Resolve the 45 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (45). — One of this dimension's main actionable groups (45 issue-level).
- Resolve the 8 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 3 high, 1 medium, 1 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
5 of 5 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/modules/user/infrastructure/database/repository/user.repository.ts. Counted over 5 of the 85 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with user.repository.ts, jwt.service.ts, REDACTED. — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 34 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
AX5 · Architecture & structure
AX6 · Interface segregation
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / Secret Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
- Enforce HTTPS (serve through https.createServer / NestJS httpsOptions, or redirect plain HTTP with express-sslify behind your TLS terminator) so data in transit is always encrypted.
C2 · Access Controls
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
- `User`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was checked for any branch (`if`, ternary, `switch`) or any call — it has neither, only assignments; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `User` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/modules/user/domain/entity/user.entity.ts:21
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM4 · Rich vs anemic model
- `User` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/user/domain/entity/user.entity.ts:17
- `UserEntity` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/user/infrastructure/database/entity/user.entity.ts:7
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `User` exposes publicly writable state (id, props). — src/modules/user/domain/entity/user.entity.ts:17
- `UserEntity` exposes publicly writable state (id, email, password, firstName, lastName, role, and 1 more). — src/modules/user/infrastructure/database/entity/user.entity.ts:7
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
DM9 · Scattered domain decisions
ED5 · Idempotency
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- `src/modules/communication/infrastructure/email/email.service.ts` reports through `console.*` at line 10 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/modules/communication/infrastructure/email/email.service.ts:10
What to do
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 3682 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:11
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- src/modules/auth/api/rest/presentation/body/login.body.ts:9 · src/modules/user/api/rest/presentation/body/create-user.body.ts:9 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/modules/auth/api/rest/presentation/body/login.body.ts:9
- src/modules/user/application/handler/command/create-user.handler.ts:10 · src/modules/user/application/handler/command/register-user.handler.ts:11 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/modules/user/application/handler/command/create-user.handler.ts:10
- src/modules/user/application/handler/command/create-user.handler.ts:5 · src/modules/user/application/handler/command/register-user.handler.ts:6 · src/modules/user/application/handler/query/check-auth-user-by-id.handler.ts:2 · src/modules/user/application/handler/query/get-all-users.handler.ts:4 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/modules/user/application/handler/command/create-user.handler.ts:5
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- src/modules/user/api/graphql/resolver/user.resolver.ts:13 imports @nestjs/graphql/dist/exceptions, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/modules/user/api/graphql/resolver/user.resolver.ts:13
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
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. (×10) — src/libs/ddd/mikro-orm-repository.abstract.ts:1, src/main.ts:1, src/libs/api/graphql/paginated.type.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 55 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 5 application, 6 tooling and 8 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (5 application, 6 tooling, 8 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 (×8) — src/libs/ddd/mikro-orm-repository.abstract.ts, src/libs/exceptions/custom-bad-request.exception.ts, src/libs/exceptions/custom-not-found.exception.ts, …
- no import path from any entry point (5 application, 6 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/modules/user/api/graphql/presentation/model/paginated-user.model.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/libs/api/graphql/paginated.type.ts
- no import path from any entry point (5 application, 6 tooling, 8 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/libs/ddd/mikro-orm-repository.abstract.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 (×2) — src/libs/ddd/repository.interface.ts, src/libs/ddd/base-entity.interface.ts
- Nothing imports this binding — it is safe to review for removal. (×3) — src/config/env/configuration.constant.ts:7, src/libs/api/rest/collection.interface.ts:6, src/libs/decorator/auth.decorator.ts:16
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
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — src/modules/auth/api/guard/auth.guard.ts:7
- 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. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- src/modules/user/domain/entity/user.entity.ts → src/modules/user/domain/event/created-user.event.ts → src/modules/user/domain/entity/user.entity.ts — src/modules/user/domain/entity/user.entity.ts:4
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- `mikroOrmRepository.create({ … password: data.password … })`: this saves the password exactly as it was typed, with no hash in between. Anyone who gets a copy of the database (a backup, a leak) can read every user's password — and people reuse passwords on other sites. Hash it first with a slow, salted password hash (`bcrypt.hash`, `argon2.hash`, or `scrypt`) and store only the hash. — src/modules/user/infrastructure/database/repository/user.repository.ts:47
What to do
- Store passwords with a salted, deliberately slow KDF — scrypt or PBKDF2 from node:crypto, or bcrypt/Argon2 — and compare with a constant-time check. A fast digest of a password, however it is encoded, is reversed by precomputed tables or GPU guessing. Start in `src/modules/user/infrastructure/database/repository/user.repository.ts:47`.
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
X5 · Nullable reference types
- ~13.7 `!` null assertions per 1k TypeScript source lines — 28 assertion(s) across the 2042 source line(s) of the 82 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/libs/api/graphql/paginated.type.ts (6), src/modules/user/api/graphql/presentation/input/create-user.input.ts (4), src/modules/user/api/rest/presentation/body/create-user.body.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81% | Strong | Solid. |
| Architecture | 80% | Strong | Solid. |
| Maturity | 51% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 51% | Adequate — gated by D9, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 52% | Adequate — gated by D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 51% | Adequate — gated by DM4, DM5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 12 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 — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
- 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).
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D11 Test Reliability — No tests discovered
- D14 License Compliance — Not scored — this repository's 435 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 9 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.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (455 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D24 Comment Value — Too few judgeable comments (1 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (No tests found, exiting with code 1), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 event handler(s); 6 CQRS handler(s)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (command argument 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: src/main.ts:16 (NestFactory.create))
- P8 Schema migrations — MikroORM is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) 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.
- 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.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — 71 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite declares a test script but contains no test files: the repository root
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'fastify' src/modules/auth/api/guard/auth.guard.ts:7
- Import cycle (2 files) src/modules/user/domain/entity/user.entity.ts:4
- Password hashing without a KDF src/modules/user/infrastructure/database/repository/user.repository.ts:47
Serious — 63 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No test reaches this file src/libs/ddd/mikro-orm-repository.abstract.ts:1
- No test reaches this file src/main.ts:1
- No test reaches this file src/libs/api/graphql/paginated.type.ts:1
- No test reaches this file src/libs/exceptions/exception.filter.ts:1
- No test reaches this file src/config/database/migrations/create-admin-credentials.migration.ts:1
- No test reaches this file src/libs/exceptions/custom-bad-request.exception.ts:1
- No test reaches this file src/libs/exceptions/custom-not-found.exception.ts:1
- No test reaches this file src/libs/ddd/value-object.abstract.ts:1
- No test reaches this file src/modules/user/api/graphql/presentation/model/paginated-user.model.ts:1
- No test reaches this file src/modules/user/application/query/get-user-by-email.query.ts:1
- Dead file (~3 LoC) src/libs/ddd/application-service.interface.ts
- Dead file (~3 LoC) src/libs/ddd/base-entity.interface.ts
- Dead file (~3 LoC) src/libs/ddd/domain-service.interface.ts
- Dead file (~3 LoC) src/modules/user/application/query/get-user-by-email.query.ts
- REDACTED
- REDACTED
- REDACTED
- Anemic entity: User src/modules/user/domain/entity/user.entity.ts:17
- Anemic entity: UserEntity src/modules/user/infrastructure/database/entity/user.entity.ts:7
- Mutable entity: User src/modules/user/domain/entity/user.entity.ts:17
- Mutable entity: UserEntity src/modules/user/infrastructure/database/entity/user.entity.ts:7
- Dead file (~13 LoC) src/libs/exceptions/custom-bad-request.exception.ts
- Dead file (~13 LoC) src/libs/exceptions/custom-not-found.exception.ts
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Coverage not measured — JavaScript/TypeScript suite
- Constructible in an invalid state: User src/modules/user/domain/entity/user.entity.ts:21
- Duplicated block (19 lines × 2 locations) src/modules/auth/api/rest/presentation/body/login.body.ts:9
- Duplicated block (17 lines × 2 locations) src/modules/user/application/handler/command/create-user.handler.ts:10
- Duplicated block (11 lines × 6 locations) src/modules/user/application/handler/command/create-user.handler.ts:5
- Boundary violation [package:third-party-deep-import] src/modules/user/api/graphql/resolver/user.resolver.ts:13
- Dependency Freshness
- No typecheck script
- Dead file (~54 LoC) src/libs/ddd/mikro-orm-repository.abstract.ts
- Dead file (~41 LoC) src/libs/api/graphql/paginated.type.ts
- Dead file (~14 LoC) src/libs/ddd/repository.interface.ts
- Dead file (~12 LoC) src/libs/ddd/value-object.abstract.ts
- Dead file (~6 LoC) src/modules/user/api/graphql/presentation/model/paginated-user.model.ts
- Unused dependency '@fastify/compress'
- Unused dependency '@semantic-release/changelog'
- Unused dependency 'source-map-support'
Minor — 29 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file src/modules/user/infrastructure/database/repository/user.repository.ts:1
- Orphaned file src/modules/auth/infrastructure/jwt/jwt.service.ts:1
- Orphaned file REDACTED:1
- Orphaned file src/modules/auth/api/guard/auth.guard.ts:1
- Orphaned file src/modules/user/api/graphql/resolver/user.resolver.ts:1
- No ADRs found
- REDACTED
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- No ADRs
- Console output used as the logging channel src/modules/communication/infrastructure/email/email.service.ts:10
- No SAST REDACTED:11
- No rollback/health safety
- Unused export 'PORT' src/config/env/configuration.constant.ts:7
- Unused export 'emptyCollection' src/libs/api/rest/collection.interface.ts:6
- Unused export 'InjectAuthUser' src/libs/decorator/auth.decorator.ts:16
- Null assertions (`!`) reduce the strict null checking score
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-d2ca6c29ca344d4c896335650207f559/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-d2ca6c29ca344d4c896335650207f559/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 . | 12 | 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 | 80 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 |