Executive summary
0xb4lamx/nestjs-boilerplate-microservice is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no encryption of stored data, no key vault and no enforced HTTPS and no access checks on the code's endpoints or handlers. It scores 40 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Security and Compliance, at 23, is the weakest lens and counts most in the score. The best first steps are encrypting the sensitive stored data and keeping its keys in a vault and adding access checks, each worth about 12 points. Raising Security and Compliance to 66 would lift the score to about 53.
Thirty-two known security holes in the packages the code depends on can be used by attackers. One automatic update takes new releases before a bad one can be spotted, and one setting leaves the servers or containers unsafe. Updating the vulnerable packages, setting a waiting period for automatic updates and correcting the unsafe settings would close these risks. The piece of business logic tied to the database or web code needs separating from the database and web code.
The product code is 1,364 lines, about €1,400 to rebuild.
If Security and Compliance rose from 23 to 66, the lowest score rated Strong, the score would rise from 40 to about 53.
New since the last survey: 8 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
Fixed since the last survey: 5 findings
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dead Code · Dead file (~28 LoC) ormconfig.js
Rebuild cost: about €1,400 · Estimate
| Cost to rebuild | €460 to €2,300, for 8 to 24 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 40. 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,364 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 app_service | 2 common.abstract_entity | 3 common.dto.abstract_dto | 4 filters.rpc-exception_filter | 5 interfaces.IFile | 6 interfaces.aws-config_interface | 7 interfaces.swagger-config_interface | 8 modules.users.commands.impl.welcome-user_command | 9 modules.users.dtos.user-id-request-params_dto | 10 modules.users.dtos.user-register_dto | 11 modules.users.commands.impl.create-user_command | 12 modules.users.commands.impl.delete-user_command | 13 modules.users.dtos.user_dto | 14 modules.users.entities.user_entity | 15 modules.users.repository.user_repository | 16 shared.services.config_service | 17 modules.users.commands.handlers.create-user_handler | 18 modules.users.commands.handlers.delete-user_handler | 19 modules.users.commands.handlers.welcome-user_handler | 20 modules.users.commands.impl.update-user_command | 21 modules.users.events.impl.abstract_event | 22 modules.users.queries.impl.get-user_query | 23 modules.users.services.users_service | 24 shared.services.aws-s3_service | 25 shared.services.logger_service | 26 app_controller | 27 filters.http-exception_filter | 28 modules.users.commands.handlers.update-user_handler | 29 modules.users.controllers.users_controller | 30 modules.users.events.impl.user-created_event | 31 modules.users.events.impl.user-deleted_event | 32 modules.users.events.impl.user-updated_event | 33 modules.users.events.impl.user-welcomed_event | 34 modules.users.graphql.users_resolver | 35 modules.users.queries.handlers.get-user_handler | 36 modules.users.queries.handlers.get-users_handler | 37 modules.users.events.handlers.user-created_handler | 38 modules.users.events.handlers.user-deleted_handler | 39 modules.users.events.handlers.user-updated_handler | 40 modules.users.events.handlers.user-welcomed_handler |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 app_service | ||||||||||||||||||||||||||||||||||||||||
| 2 common.abstract_entity | ||||||||||||||||||||||||||||||||||||||||
| 3 common.dto.abstract_dto | ||||||||||||||||||||||||||||||||||||||||
| 4 filters.rpc-exception_filter | ||||||||||||||||||||||||||||||||||||||||
| 5 interfaces.IFile | ||||||||||||||||||||||||||||||||||||||||
| 6 interfaces.aws-config_interface | ||||||||||||||||||||||||||||||||||||||||
| 7 interfaces.swagger-config_interface | ||||||||||||||||||||||||||||||||||||||||
| 8 modules.users.commands.impl.welcome-user_command | ||||||||||||||||||||||||||||||||||||||||
| 9 modules.users.dtos.user-id-request-params_dto | ||||||||||||||||||||||||||||||||||||||||
| 10 modules.users.dtos.user-register_dto | ||||||||||||||||||||||||||||||||||||||||
| 11 modules.users.commands.impl.create-user_command | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 modules.users.commands.impl.delete-user_command | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 modules.users.dtos.user_dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 modules.users.entities.user_entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 modules.users.repository.user_repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 shared.services.config_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 modules.users.commands.handlers.create-user_handler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 modules.users.commands.handlers.delete-user_handler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 modules.users.commands.handlers.welcome-user_handler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 modules.users.commands.impl.update-user_command | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 modules.users.events.impl.abstract_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 modules.users.queries.impl.get-user_query | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 modules.users.services.users_service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 shared.services.aws-s3_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 shared.services.logger_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 app_controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 filters.http-exception_filter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 modules.users.commands.handlers.update-user_handler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 modules.users.controllers.users_controller | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 modules.users.events.impl.user-created_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 modules.users.events.impl.user-deleted_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 modules.users.events.impl.user-updated_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 modules.users.events.impl.user-welcomed_event | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 modules.users.graphql.users_resolver | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 modules.users.queries.handlers.get-user_handler | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 modules.users.queries.handlers.get-users_handler | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 modules.users.events.handlers.user-created_handler | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 modules.users.events.handlers.user-deleted_handler | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 modules.users.events.handlers.user-updated_handler | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 modules.users.events.handlers.user-welcomed_handler | 1 |
11→10 modules.users.commands.impl.create-user_command uses modules.users.dtos.user-register_dto✕
- Connections
- 1 pair of types, where a type in modules.users.commands.impl.create-user_command uses a type in modules.users.dtos.user-register_dto.
- The types involved
src.modules.users.commands.impl.create-user_command.CreateUserCommand→src.modules.users.dtos.user-register_dto.UserRegisterDto
- Direction
- modules.users.commands.impl.create-user_command uses modules.users.dtos.user-register_dto, so a change to modules.users.dtos.user-register_dto can break modules.users.commands.impl.create-user_command, while a change to modules.users.commands.impl.create-user_command can't break modules.users.dtos.user-register_dto.
- Position
- Below the diagonal: modules.users.commands.impl.create-user_command uses a module listed above it, which is the healthy direction.
12→9 modules.users.commands.impl.delete-user_command uses modules.users.dtos.user-id-request-params_dto✕
- Connections
- 1 pair of types, where a type in modules.users.commands.impl.delete-user_command uses a type in modules.users.dtos.user-id-request-params_dto.
- The types involved
src.modules.users.commands.impl.delete-user_command.DeleteUserCommand→src.modules.users.dtos.user-id-request-params_dto.UserIdRequestParamsDto
- Direction
- modules.users.commands.impl.delete-user_command uses modules.users.dtos.user-id-request-params_dto, so a change to modules.users.dtos.user-id-request-params_dto can break modules.users.commands.impl.delete-user_command, while a change to modules.users.commands.impl.delete-user_command can't break modules.users.dtos.user-id-request-params_dto.
- Position
- Below the diagonal: modules.users.commands.impl.delete-user_command uses a module listed above it, which is the healthy direction.
13→3 modules.users.dtos.user_dto uses common.dto.abstract_dto✕
- Connections
- 1 pair of types, where a type in modules.users.dtos.user_dto uses a type in common.dto.abstract_dto.
- The types involved
src.modules.users.dtos.user_dto.UserDto→src.common.dto.abstract_dto.AbstractDto
- Direction
- modules.users.dtos.user_dto uses common.dto.abstract_dto, so a change to common.dto.abstract_dto can break modules.users.dtos.user_dto, while a change to modules.users.dtos.user_dto can't break common.dto.abstract_dto.
- Position
- Below the diagonal: modules.users.dtos.user_dto uses a module listed above it, which is the healthy direction.
14→2 modules.users.entities.user_entity uses common.abstract_entity✕
- Connections
- 1 pair of types, where a type in modules.users.entities.user_entity uses a type in common.abstract_entity.
- The types involved
src.modules.users.entities.user_entity.User→src.common.abstract_entity.AbstractEntity
- Direction
- modules.users.entities.user_entity uses common.abstract_entity, so a change to common.abstract_entity can break modules.users.entities.user_entity, while a change to modules.users.entities.user_entity can't break common.abstract_entity.
- Position
- Below the diagonal: modules.users.entities.user_entity uses a module listed above it, which is the healthy direction.
15→10 modules.users.repository.user_repository uses modules.users.dtos.user-register_dto✕
- Connections
- 1 pair of types, where a type in modules.users.repository.user_repository uses a type in modules.users.dtos.user-register_dto.
- The types involved
src.modules.users.repository.user_repository.UserRepository→src.modules.users.dtos.user-register_dto.UserRegisterDto
- Direction
- modules.users.repository.user_repository uses modules.users.dtos.user-register_dto, so a change to modules.users.dtos.user-register_dto can break modules.users.repository.user_repository, while a change to modules.users.repository.user_repository can't break modules.users.dtos.user-register_dto.
- Position
- Below the diagonal: modules.users.repository.user_repository uses a module listed above it, which is the healthy direction.
16→6 shared.services.config_service uses interfaces.aws-config_interface✕
- Connections
- 1 pair of types, where a type in shared.services.config_service uses a type in interfaces.aws-config_interface.
- The types involved
src.shared.services.config_service.ConfigService→src.interfaces.aws-config_interface.IAwsConfigInterface
- Direction
- shared.services.config_service uses interfaces.aws-config_interface, so a change to interfaces.aws-config_interface can break shared.services.config_service, while a change to shared.services.config_service can't break interfaces.aws-config_interface.
- Position
- Below the diagonal: shared.services.config_service uses a module listed above it, which is the healthy direction.
16→7 shared.services.config_service uses interfaces.swagger-config_interface✕
- Connections
- 1 pair of types, where a type in shared.services.config_service uses a type in interfaces.swagger-config_interface.
- The types involved
src.shared.services.config_service.ConfigService→src.interfaces.swagger-config_interface.ISwaggerConfigInterface
- Direction
- shared.services.config_service uses interfaces.swagger-config_interface, so a change to interfaces.swagger-config_interface can break shared.services.config_service, while a change to shared.services.config_service can't break interfaces.swagger-config_interface.
- Position
- Below the diagonal: shared.services.config_service uses a module listed above it, which is the healthy direction.
17→11 modules.users.commands.handlers.create-user_handler uses modules.users.commands.impl.create-user_command✕
- Connections
- 1 pair of types, where a type in modules.users.commands.handlers.create-user_handler uses a type in modules.users.commands.impl.create-user_command.
- The types involved
src.modules.users.commands.handlers.create-user_handler.CreateUserHandler→src.modules.users.commands.impl.create-user_command.CreateUserCommand
- Direction
- modules.users.commands.handlers.create-user_handler uses modules.users.commands.impl.create-user_command, so a change to modules.users.commands.impl.create-user_command can break modules.users.commands.handlers.create-user_handler, while a change to modules.users.commands.handlers.create-user_handler can't break modules.users.commands.impl.create-user_command.
- Position
- Below the diagonal: modules.users.commands.handlers.create-user_handler uses a module listed above it, which is the healthy direction.
17→15 modules.users.commands.handlers.create-user_handler uses modules.users.repository.user_repository✕
- Connections
- 1 pair of types, where a type in modules.users.commands.handlers.create-user_handler uses a type in modules.users.repository.user_repository.
- The types involved
src.modules.users.commands.handlers.create-user_handler.CreateUserHandler→src.modules.users.repository.user_repository.UserRepository
- Direction
- modules.users.commands.handlers.create-user_handler uses modules.users.repository.user_repository, so a change to modules.users.repository.user_repository can break modules.users.commands.handlers.create-user_handler, while a change to modules.users.commands.handlers.create-user_handler can't break modules.users.repository.user_repository.
- Position
- Below the diagonal: modules.users.commands.handlers.create-user_handler uses a module listed above it, which is the healthy direction.
18→12 modules.users.commands.handlers.delete-user_handler uses modules.users.commands.impl.delete-user_command✕
- Connections
- 1 pair of types, where a type in modules.users.commands.handlers.delete-user_handler uses a type in modules.users.commands.impl.delete-user_command.
- The types involved
src.modules.users.commands.handlers.delete-user_handler.DeleteUserHandler→src.modules.users.commands.impl.delete-user_command.DeleteUserCommand
- Direction
- modules.users.commands.handlers.delete-user_handler uses modules.users.commands.impl.delete-user_command, so a change to modules.users.commands.impl.delete-user_command can break modules.users.commands.handlers.delete-user_handler, while a change to modules.users.commands.handlers.delete-user_handler can't break modules.users.commands.impl.delete-user_command.
- Position
- Below the diagonal: modules.users.commands.handlers.delete-user_handler uses a module listed above it, which is the healthy direction.
18→15 modules.users.commands.handlers.delete-user_handler uses modules.users.repository.user_repository✕
- Connections
- 1 pair of types, where a type in modules.users.commands.handlers.delete-user_handler uses a type in modules.users.repository.user_repository.
- The types involved
src.modules.users.commands.handlers.delete-user_handler.DeleteUserHandler→src.modules.users.repository.user_repository.UserRepository
- Direction
- modules.users.commands.handlers.delete-user_handler uses modules.users.repository.user_repository, so a change to modules.users.repository.user_repository can break modules.users.commands.handlers.delete-user_handler, while a change to modules.users.commands.handlers.delete-user_handler can't break modules.users.repository.user_repository.
- Position
- Below the diagonal: modules.users.commands.handlers.delete-user_handler uses a module listed above it, which is the healthy direction.
19→8 modules.users.commands.handlers.welcome-user_handler uses modules.users.commands.impl.welcome-user_command✕
- Connections
- 1 pair of types, where a type in modules.users.commands.handlers.welcome-user_handler uses a type in modules.users.commands.impl.welcome-user_command.
- The types involved
src.modules.users.commands.handlers.welcome-user_handler.WelcomeUserHandler→src.modules.users.commands.impl.welcome-user_command.WelcomeUserCommand
- Direction
- modules.users.commands.handlers.welcome-user_handler uses modules.users.commands.impl.welcome-user_command, so a change to modules.users.commands.impl.welcome-user_command can break modules.users.commands.handlers.welcome-user_handler, while a change to modules.users.commands.handlers.welcome-user_handler can't break modules.users.commands.impl.welcome-user_command.
- Position
- Below the diagonal: modules.users.commands.handlers.welcome-user_handler uses a module listed above it, which is the healthy direction.
19→15 modules.users.commands.handlers.welcome-user_handler uses modules.users.repository.user_repository✕
- Connections
- 1 pair of types, where a type in modules.users.commands.handlers.welcome-user_handler uses a type in modules.users.repository.user_repository.
- The types involved
src.modules.users.commands.handlers.welcome-user_handler.WelcomeUserHandler→src.modules.users.repository.user_repository.UserRepository
- Direction
- modules.users.commands.handlers.welcome-user_handler uses modules.users.repository.user_repository, so a change to modules.users.repository.user_repository can break modules.users.commands.handlers.welcome-user_handler, while a change to modules.users.commands.handlers.welcome-user_handler can't break modules.users.repository.user_repository.
- Position
- Below the diagonal: modules.users.commands.handlers.welcome-user_handler uses a module listed above it, which is the healthy direction.
20→13 modules.users.commands.impl.update-user_command uses modules.users.dtos.user_dto✕
- Connections
- 1 pair of types, where a type in modules.users.commands.impl.update-user_command uses a type in modules.users.dtos.user_dto.
- The types involved
src.modules.users.commands.impl.update-user_command.UpdateUserCommand→src.modules.users.dtos.user_dto.UserDto
- Direction
- modules.users.commands.impl.update-user_command uses modules.users.dtos.user_dto, so a change to modules.users.dtos.user_dto can break modules.users.commands.impl.update-user_command, while a change to modules.users.commands.impl.update-user_command can't break modules.users.dtos.user_dto.
- Position
- Below the diagonal: modules.users.commands.impl.update-user_command uses a module listed above it, which is the healthy direction.
21→13 modules.users.events.impl.abstract_event uses modules.users.dtos.user_dto✕
- Connections
- 1 pair of types, where a type in modules.users.events.impl.abstract_event uses a type in modules.users.dtos.user_dto.
- The types involved
src.modules.users.events.impl.abstract_event.UserAbstractEvent→src.modules.users.dtos.user_dto.UserDto
- Direction
- modules.users.events.impl.abstract_event uses modules.users.dtos.user_dto, so a change to modules.users.dtos.user_dto can break modules.users.events.impl.abstract_event, while a change to modules.users.events.impl.abstract_event can't break modules.users.dtos.user_dto.
- Position
- Below the diagonal: modules.users.events.impl.abstract_event uses a module listed above it, which is the healthy direction.
22→14 modules.users.queries.impl.get-user_query uses modules.users.entities.user_entity✕
- Connections
- 1 pair of types, where a type in modules.users.queries.impl.get-user_query uses a type in modules.users.entities.user_entity.
- The types involved
src.modules.users.queries.impl.get-user_query.GetUserQuery→src.modules.users.entities.user_entity.User
- Direction
- modules.users.queries.impl.get-user_query uses modules.users.entities.user_entity, so a change to modules.users.entities.user_entity can break modules.users.queries.impl.get-user_query, while a change to modules.users.queries.impl.get-user_query can't break modules.users.entities.user_entity.
- Position
- Below the diagonal: modules.users.queries.impl.get-user_query uses a module listed above it, which is the healthy direction.
23→9 modules.users.services.users_service uses modules.users.dtos.user-id-request-params_dto✕
- Connections
- 1 pair of types, where a type in modules.users.services.users_service uses a type in modules.users.dtos.user-id-request-params_dto.
- The types involved
src.modules.users.services.users_service.UsersService→src.modules.users.dtos.user-id-request-params_dto.UserIdRequestParamsDto
- Direction
- modules.users.services.users_service uses modules.users.dtos.user-id-request-params_dto, so a change to modules.users.dtos.user-id-request-params_dto can break modules.users.services.users_service, while a change to modules.users.services.users_service can't break modules.users.dtos.user-id-request-params_dto.
- Position
- Below the diagonal: modules.users.services.users_service uses a module listed above it, which is the healthy direction.
23→10 modules.users.services.users_service uses modules.users.dtos.user-register_dto✕
- Connections
- 1 pair of types, where a type in modules.users.services.users_service uses a type in modules.users.dtos.user-register_dto.
- The types involved
src.modules.users.services.users_service.UsersService→src.modules.users.dtos.user-register_dto.UserRegisterDto
- Direction
- modules.users.services.users_service uses modules.users.dtos.user-register_dto, so a change to modules.users.dtos.user-register_dto can break modules.users.services.users_service, while a change to modules.users.services.users_service can't break modules.users.dtos.user-register_dto.
- Position
- Below the diagonal: modules.users.services.users_service uses a module listed above it, which is the healthy direction.
23→13 modules.users.services.users_service uses modules.users.dtos.user_dto✕
- Connections
- 1 pair of types, where a type in modules.users.services.users_service uses a type in modules.users.dtos.user_dto.
- The types involved
src.modules.users.services.users_service.UsersService→src.modules.users.dtos.user_dto.UserDto
- Direction
- modules.users.services.users_service uses modules.users.dtos.user_dto, so a change to modules.users.dtos.user_dto can break modules.users.services.users_service, while a change to modules.users.services.users_service can't break modules.users.dtos.user_dto.
- Position
- Below the diagonal: modules.users.services.users_service uses a module listed above it, which is the healthy direction.
24→5 shared.services.aws-s3_service uses interfaces.IFile✕
- Connections
- 1 pair of types, where a type in shared.services.aws-s3_service uses a type in interfaces.IFile.
- The types involved
src.shared.services.aws-s3_service.AwsS3Service→src.interfaces.IFile.IFile
- Direction
- shared.services.aws-s3_service uses interfaces.IFile, so a change to interfaces.IFile can break shared.services.aws-s3_service, while a change to shared.services.aws-s3_service can't break interfaces.IFile.
- Position
- Below the diagonal: shared.services.aws-s3_service uses a module listed above it, which is the healthy direction.
24→16 shared.services.aws-s3_service uses shared.services.config_service✕
- Connections
- 1 pair of types, where a type in shared.services.aws-s3_service uses a type in shared.services.config_service.
- The types involved
src.shared.services.aws-s3_service.AwsS3Service→src.shared.services.config_service.ConfigService
- Direction
- shared.services.aws-s3_service uses shared.services.config_service, so a change to shared.services.config_service can break shared.services.aws-s3_service, while a change to shared.services.aws-s3_service can't break shared.services.config_service.
- Position
- Below the diagonal: shared.services.aws-s3_service uses a module listed above it, which is the healthy direction.
25→16 shared.services.logger_service uses shared.services.config_service✕
- Connections
- 1 pair of types, where a type in shared.services.logger_service uses a type in shared.services.config_service.
- The types involved
src.shared.services.logger_service.LoggerService→src.shared.services.config_service.ConfigService
- Direction
- shared.services.logger_service uses shared.services.config_service, so a change to shared.services.config_service can break shared.services.logger_service, while a change to shared.services.logger_service can't break shared.services.config_service.
- Position
- Below the diagonal: shared.services.logger_service uses a module listed above it, which is the healthy direction.
26→1 app_controller uses app_service✕
- Connections
- 1 pair of types, where a type in app_controller uses a type in app_service.
- The types involved
src.app_controller.AppController→src.app_service.AppService
- Direction
- app_controller uses app_service, so a change to app_service can break app_controller, while a change to app_controller can't break app_service.
- Position
- Below the diagonal: app_controller uses a module listed above it, which is the healthy direction.
26→16 app_controller uses shared.services.config_service✕
- Connections
- 1 pair of types, where a type in app_controller uses a type in shared.services.config_service.
- The types involved
src.app_controller.AppController→src.shared.services.config_service.ConfigService
- Direction
- app_controller uses shared.services.config_service, so a change to shared.services.config_service can break app_controller, while a change to app_controller can't break shared.services.config_service.
- Position
- Below the diagonal: app_controller uses a module listed above it, which is the healthy direction.
26→25 app_controller uses shared.services.logger_service✕
- Connections
- 1 pair of types, where a type in app_controller uses a type in shared.services.logger_service.
- The types involved
src.app_controller.AppController→src.shared.services.logger_service.LoggerService
- Direction
- app_controller uses shared.services.logger_service, so a change to shared.services.logger_service can break app_controller, while a change to app_controller can't break shared.services.logger_service.
- Position
- Below the diagonal: app_controller uses a module listed above it, which is the healthy direction.
27→4 filters.http-exception_filter uses filters.rpc-exception_filter✕
- Connections
- 1 pair of types, where a type in filters.http-exception_filter uses a type in filters.rpc-exception_filter.
- The types involved
src.filters.http-exception_filter.HttpExceptionFilter→src.filters.rpc-exception_filter.ExceptionFilter
- Direction
- filters.http-exception_filter uses filters.rpc-exception_filter, so a change to filters.rpc-exception_filter can break filters.http-exception_filter, while a change to filters.http-exception_filter can't break filters.rpc-exception_filter.
- Position
- Below the diagonal: filters.http-exception_filter uses a module listed above it, which is the healthy direction.
27→25 filters.http-exception_filter uses shared.services.logger_service✕
- Connections
- 1 pair of types, where a type in filters.http-exception_filter uses a type in shared.services.logger_service.
- The types involved
src.filters.http-exception_filter.HttpExceptionFilter→src.shared.services.logger_service.LoggerService
- Direction
- filters.http-exception_filter uses shared.services.logger_service, so a change to shared.services.logger_service can break filters.http-exception_filter, while a change to filters.http-exception_filter can't break shared.services.logger_service.
- Position
- Below the diagonal: filters.http-exception_filter uses a module listed above it, which is the healthy direction.
28→15 modules.users.commands.handlers.update-user_handler uses modules.users.repository.user_repository✕
- Connections
- 1 pair of types, where a type in modules.users.commands.handlers.update-user_handler uses a type in modules.users.repository.user_repository.
- The types involved
src.modules.users.commands.handlers.update-user_handler.UpdateUserHandler→src.modules.users.repository.user_repository.UserRepository
- Direction
- modules.users.commands.handlers.update-user_handler uses modules.users.repository.user_repository, so a change to modules.users.repository.user_repository can break modules.users.commands.handlers.update-user_handler, while a change to modules.users.commands.handlers.update-user_handler can't break modules.users.repository.user_repository.
- Position
- Below the diagonal: modules.users.commands.handlers.update-user_handler uses a module listed above it, which is the healthy direction.
28→20 modules.users.commands.handlers.update-user_handler uses modules.users.commands.impl.update-user_command✕
- Connections
- 1 pair of types, where a type in modules.users.commands.handlers.update-user_handler uses a type in modules.users.commands.impl.update-user_command.
- The types involved
src.modules.users.commands.handlers.update-user_handler.UpdateUserHandler→src.modules.users.commands.impl.update-user_command.UpdateUserCommand
- Direction
- modules.users.commands.handlers.update-user_handler uses modules.users.commands.impl.update-user_command, so a change to modules.users.commands.impl.update-user_command can break modules.users.commands.handlers.update-user_handler, while a change to modules.users.commands.handlers.update-user_handler can't break modules.users.commands.impl.update-user_command.
- Position
- Below the diagonal: modules.users.commands.handlers.update-user_handler uses a module listed above it, which is the healthy direction.
29→9 modules.users.controllers.users_controller uses modules.users.dtos.user-id-request-params_dto✕
- Connections
- 1 pair of types, where a type in modules.users.controllers.users_controller uses a type in modules.users.dtos.user-id-request-params_dto.
- The types involved
src.modules.users.controllers.users_controller.UsersController→src.modules.users.dtos.user-id-request-params_dto.UserIdRequestParamsDto
- Direction
- modules.users.controllers.users_controller uses modules.users.dtos.user-id-request-params_dto, so a change to modules.users.dtos.user-id-request-params_dto can break modules.users.controllers.users_controller, while a change to modules.users.controllers.users_controller can't break modules.users.dtos.user-id-request-params_dto.
- Position
- Below the diagonal: modules.users.controllers.users_controller uses a module listed above it, which is the healthy direction.
29→10 modules.users.controllers.users_controller uses modules.users.dtos.user-register_dto✕
- Connections
- 1 pair of types, where a type in modules.users.controllers.users_controller uses a type in modules.users.dtos.user-register_dto.
- The types involved
src.modules.users.controllers.users_controller.UsersController→src.modules.users.dtos.user-register_dto.UserRegisterDto
- Direction
- modules.users.controllers.users_controller uses modules.users.dtos.user-register_dto, so a change to modules.users.dtos.user-register_dto can break modules.users.controllers.users_controller, while a change to modules.users.controllers.users_controller can't break modules.users.dtos.user-register_dto.
- Position
- Below the diagonal: modules.users.controllers.users_controller uses a module listed above it, which is the healthy direction.
29→13 modules.users.controllers.users_controller uses modules.users.dtos.user_dto✕
- Connections
- 1 pair of types, where a type in modules.users.controllers.users_controller uses a type in modules.users.dtos.user_dto.
- The types involved
src.modules.users.controllers.users_controller.UsersController→src.modules.users.dtos.user_dto.UserDto
- Direction
- modules.users.controllers.users_controller uses modules.users.dtos.user_dto, so a change to modules.users.dtos.user_dto can break modules.users.controllers.users_controller, while a change to modules.users.controllers.users_controller can't break modules.users.dtos.user_dto.
- Position
- Below the diagonal: modules.users.controllers.users_controller uses a module listed above it, which is the healthy direction.
29→23 modules.users.controllers.users_controller uses modules.users.services.users_service✕
- Connections
- 1 pair of types, where a type in modules.users.controllers.users_controller uses a type in modules.users.services.users_service.
- The types involved
src.modules.users.controllers.users_controller.UsersController→src.modules.users.services.users_service.UsersService
- Direction
- modules.users.controllers.users_controller uses modules.users.services.users_service, so a change to modules.users.services.users_service can break modules.users.controllers.users_controller, while a change to modules.users.controllers.users_controller can't break modules.users.services.users_service.
- Position
- Below the diagonal: modules.users.controllers.users_controller uses a module listed above it, which is the healthy direction.
30→21 modules.users.events.impl.user-created_event uses modules.users.events.impl.abstract_event✕
- Connections
- 1 pair of types, where a type in modules.users.events.impl.user-created_event uses a type in modules.users.events.impl.abstract_event.
- The types involved
src.modules.users.events.impl.user-created_event.UserCreatedEvent→src.modules.users.events.impl.abstract_event.UserAbstractEvent
- Direction
- modules.users.events.impl.user-created_event uses modules.users.events.impl.abstract_event, so a change to modules.users.events.impl.abstract_event can break modules.users.events.impl.user-created_event, while a change to modules.users.events.impl.user-created_event can't break modules.users.events.impl.abstract_event.
- Position
- Below the diagonal: modules.users.events.impl.user-created_event uses a module listed above it, which is the healthy direction.
31→21 modules.users.events.impl.user-deleted_event uses modules.users.events.impl.abstract_event✕
- Connections
- 1 pair of types, where a type in modules.users.events.impl.user-deleted_event uses a type in modules.users.events.impl.abstract_event.
- The types involved
src.modules.users.events.impl.user-deleted_event.UserDeletedEvent→src.modules.users.events.impl.abstract_event.UserAbstractEvent
- Direction
- modules.users.events.impl.user-deleted_event uses modules.users.events.impl.abstract_event, so a change to modules.users.events.impl.abstract_event can break modules.users.events.impl.user-deleted_event, while a change to modules.users.events.impl.user-deleted_event can't break modules.users.events.impl.abstract_event.
- Position
- Below the diagonal: modules.users.events.impl.user-deleted_event uses a module listed above it, which is the healthy direction.
32→21 modules.users.events.impl.user-updated_event uses modules.users.events.impl.abstract_event✕
- Connections
- 1 pair of types, where a type in modules.users.events.impl.user-updated_event uses a type in modules.users.events.impl.abstract_event.
- The types involved
src.modules.users.events.impl.user-updated_event.UserUpdatedEvent→src.modules.users.events.impl.abstract_event.UserAbstractEvent
- Direction
- modules.users.events.impl.user-updated_event uses modules.users.events.impl.abstract_event, so a change to modules.users.events.impl.abstract_event can break modules.users.events.impl.user-updated_event, while a change to modules.users.events.impl.user-updated_event can't break modules.users.events.impl.abstract_event.
- Position
- Below the diagonal: modules.users.events.impl.user-updated_event uses a module listed above it, which is the healthy direction.
33→21 modules.users.events.impl.user-welcomed_event uses modules.users.events.impl.abstract_event✕
- Connections
- 1 pair of types, where a type in modules.users.events.impl.user-welcomed_event uses a type in modules.users.events.impl.abstract_event.
- The types involved
src.modules.users.events.impl.user-welcomed_event.UserWelcomedEvent→src.modules.users.events.impl.abstract_event.UserAbstractEvent
- Direction
- modules.users.events.impl.user-welcomed_event uses modules.users.events.impl.abstract_event, so a change to modules.users.events.impl.abstract_event can break modules.users.events.impl.user-welcomed_event, while a change to modules.users.events.impl.user-welcomed_event can't break modules.users.events.impl.abstract_event.
- Position
- Below the diagonal: modules.users.events.impl.user-welcomed_event uses a module listed above it, which is the healthy direction.
34→23 modules.users.graphql.users_resolver uses modules.users.services.users_service✕
- Connections
- 1 pair of types, where a type in modules.users.graphql.users_resolver uses a type in modules.users.services.users_service.
- The types involved
src.modules.users.graphql.users_resolver.UsersResolver→src.modules.users.services.users_service.UsersService
- Direction
- modules.users.graphql.users_resolver uses modules.users.services.users_service, so a change to modules.users.services.users_service can break modules.users.graphql.users_resolver, while a change to modules.users.graphql.users_resolver can't break modules.users.services.users_service.
- Position
- Below the diagonal: modules.users.graphql.users_resolver uses a module listed above it, which is the healthy direction.
35→13 modules.users.queries.handlers.get-user_handler uses modules.users.dtos.user_dto✕
- Connections
- 1 pair of types, where a type in modules.users.queries.handlers.get-user_handler uses a type in modules.users.dtos.user_dto.
- The types involved
src.modules.users.queries.handlers.get-user_handler.GetUserHandler→src.modules.users.dtos.user_dto.UserDto
- Direction
- modules.users.queries.handlers.get-user_handler uses modules.users.dtos.user_dto, so a change to modules.users.dtos.user_dto can break modules.users.queries.handlers.get-user_handler, while a change to modules.users.queries.handlers.get-user_handler can't break modules.users.dtos.user_dto.
- Position
- Below the diagonal: modules.users.queries.handlers.get-user_handler uses a module listed above it, which is the healthy direction.
35→15 modules.users.queries.handlers.get-user_handler uses modules.users.repository.user_repository✕
- Connections
- 1 pair of types, where a type in modules.users.queries.handlers.get-user_handler uses a type in modules.users.repository.user_repository.
- The types involved
src.modules.users.queries.handlers.get-user_handler.GetUserHandler→src.modules.users.repository.user_repository.UserRepository
- Direction
- modules.users.queries.handlers.get-user_handler uses modules.users.repository.user_repository, so a change to modules.users.repository.user_repository can break modules.users.queries.handlers.get-user_handler, while a change to modules.users.queries.handlers.get-user_handler can't break modules.users.repository.user_repository.
- Position
- Below the diagonal: modules.users.queries.handlers.get-user_handler uses a module listed above it, which is the healthy direction.
35→22 modules.users.queries.handlers.get-user_handler uses modules.users.queries.impl.get-user_query✕
- Connections
- 1 pair of types, where a type in modules.users.queries.handlers.get-user_handler uses a type in modules.users.queries.impl.get-user_query.
- The types involved
src.modules.users.queries.handlers.get-user_handler.GetUserHandler→src.modules.users.queries.impl.get-user_query.GetUserQuery
- Direction
- modules.users.queries.handlers.get-user_handler uses modules.users.queries.impl.get-user_query, so a change to modules.users.queries.impl.get-user_query can break modules.users.queries.handlers.get-user_handler, while a change to modules.users.queries.handlers.get-user_handler can't break modules.users.queries.impl.get-user_query.
- Position
- Below the diagonal: modules.users.queries.handlers.get-user_handler uses a module listed above it, which is the healthy direction.
35→25 modules.users.queries.handlers.get-user_handler uses shared.services.logger_service✕
- Connections
- 1 pair of types, where a type in modules.users.queries.handlers.get-user_handler uses a type in shared.services.logger_service.
- The types involved
src.modules.users.queries.handlers.get-user_handler.GetUserHandler→src.shared.services.logger_service.LoggerService
- Direction
- modules.users.queries.handlers.get-user_handler uses shared.services.logger_service, so a change to shared.services.logger_service can break modules.users.queries.handlers.get-user_handler, while a change to modules.users.queries.handlers.get-user_handler can't break shared.services.logger_service.
- Position
- Below the diagonal: modules.users.queries.handlers.get-user_handler uses a module listed above it, which is the healthy direction.
36→15 modules.users.queries.handlers.get-users_handler uses modules.users.repository.user_repository✕
- Connections
- 1 pair of types, where a type in modules.users.queries.handlers.get-users_handler uses a type in modules.users.repository.user_repository.
- The types involved
src.modules.users.queries.handlers.get-users_handler.GetUsersHandler→src.modules.users.repository.user_repository.UserRepository
- Direction
- modules.users.queries.handlers.get-users_handler uses modules.users.repository.user_repository, so a change to modules.users.repository.user_repository can break modules.users.queries.handlers.get-users_handler, while a change to modules.users.queries.handlers.get-users_handler can't break modules.users.repository.user_repository.
- Position
- Below the diagonal: modules.users.queries.handlers.get-users_handler uses a module listed above it, which is the healthy direction.
36→25 modules.users.queries.handlers.get-users_handler uses shared.services.logger_service✕
- Connections
- 1 pair of types, where a type in modules.users.queries.handlers.get-users_handler uses a type in shared.services.logger_service.
- The types involved
src.modules.users.queries.handlers.get-users_handler.GetUsersHandler→src.shared.services.logger_service.LoggerService
- Direction
- modules.users.queries.handlers.get-users_handler uses shared.services.logger_service, so a change to shared.services.logger_service can break modules.users.queries.handlers.get-users_handler, while a change to modules.users.queries.handlers.get-users_handler can't break shared.services.logger_service.
- Position
- Below the diagonal: modules.users.queries.handlers.get-users_handler uses a module listed above it, which is the healthy direction.
37→30 modules.users.events.handlers.user-created_handler uses modules.users.events.impl.user-created_event✕
- Connections
- 1 pair of types, where a type in modules.users.events.handlers.user-created_handler uses a type in modules.users.events.impl.user-created_event.
- The types involved
src.modules.users.events.handlers.user-created_handler.UserCreatedHandler→src.modules.users.events.impl.user-created_event.UserCreatedEvent
- Direction
- modules.users.events.handlers.user-created_handler uses modules.users.events.impl.user-created_event, so a change to modules.users.events.impl.user-created_event can break modules.users.events.handlers.user-created_handler, while a change to modules.users.events.handlers.user-created_handler can't break modules.users.events.impl.user-created_event.
- Position
- Below the diagonal: modules.users.events.handlers.user-created_handler uses a module listed above it, which is the healthy direction.
38→31 modules.users.events.handlers.user-deleted_handler uses modules.users.events.impl.user-deleted_event✕
- Connections
- 1 pair of types, where a type in modules.users.events.handlers.user-deleted_handler uses a type in modules.users.events.impl.user-deleted_event.
- The types involved
src.modules.users.events.handlers.user-deleted_handler.UserDeletedHandler→src.modules.users.events.impl.user-deleted_event.UserDeletedEvent
- Direction
- modules.users.events.handlers.user-deleted_handler uses modules.users.events.impl.user-deleted_event, so a change to modules.users.events.impl.user-deleted_event can break modules.users.events.handlers.user-deleted_handler, while a change to modules.users.events.handlers.user-deleted_handler can't break modules.users.events.impl.user-deleted_event.
- Position
- Below the diagonal: modules.users.events.handlers.user-deleted_handler uses a module listed above it, which is the healthy direction.
39→32 modules.users.events.handlers.user-updated_handler uses modules.users.events.impl.user-updated_event✕
- Connections
- 1 pair of types, where a type in modules.users.events.handlers.user-updated_handler uses a type in modules.users.events.impl.user-updated_event.
- The types involved
src.modules.users.events.handlers.user-updated_handler.UserUpdatedHandler→src.modules.users.events.impl.user-updated_event.UserUpdatedEvent
- Direction
- modules.users.events.handlers.user-updated_handler uses modules.users.events.impl.user-updated_event, so a change to modules.users.events.impl.user-updated_event can break modules.users.events.handlers.user-updated_handler, while a change to modules.users.events.handlers.user-updated_handler can't break modules.users.events.impl.user-updated_event.
- Position
- Below the diagonal: modules.users.events.handlers.user-updated_handler uses a module listed above it, which is the healthy direction.
40→33 modules.users.events.handlers.user-welcomed_handler uses modules.users.events.impl.user-welcomed_event✕
- Connections
- 1 pair of types, where a type in modules.users.events.handlers.user-welcomed_handler uses a type in modules.users.events.impl.user-welcomed_event.
- The types involved
src.modules.users.events.handlers.user-welcomed_handler.UserWelcomedHandler→src.modules.users.events.impl.user-welcomed_event.UserWelcomedEvent
- Direction
- modules.users.events.handlers.user-welcomed_handler uses modules.users.events.impl.user-welcomed_event, so a change to modules.users.events.impl.user-welcomed_event can break modules.users.events.handlers.user-welcomed_handler, while a change to modules.users.events.handlers.user-welcomed_handler can't break modules.users.events.impl.user-welcomed_event.
- Position
- Below the diagonal: modules.users.events.handlers.user-welcomed_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 | 59 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
| A05:2025 — Injection | 1 | High / Critical |
Roadmap
Top priorities: Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.); Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.). | +12.2 pts | Medium | Data Protection |
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +12.2 pts | Medium | Access Controls |
| Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository). | +5.4 pts | Medium | Domain ↔ infrastructure boundary |
| Resolve the 25 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (25). | +3.2 pts | Medium | Dependency Vulnerabilities |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.5 pts | Low | Dependency Vulnerabilities |
| Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). | +1.5 pts | Low | Dependency Vulnerabilities |
| Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. | +1.5 pts | Low | IaC & Container Security |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/providers/event-bus.provider.ts | 6.9 | Near-clean | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| package.json | 7.1 | Near-clean | Dependency Hygiene: Deprecated: @apollo/federation |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/modules/users/repository/user.repository.ts | 7.3 | Near-clean | Explicit Debt: TodoComment |
| src/app.controller.ts | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/main.ts | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/shared/services/aws-s3.service.ts | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/shared/services/config.service.ts | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/modules/users/entities/user.entity.ts | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 71 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 71 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, 121 of 134 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
- 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. Not scored — 34 production npm declaration(s) across 1 package.json (1 of them the product) were read for PINNING discipline (1 defect(s) reported), but the outdated/deprecated signal needs registry.npmjs.org, which could not be reached on this run, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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-maintainer repository — bus factor is not applicable (4 contributor(s) across 448 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 3 hold 3.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and 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.
- AXB2 Runtime readiness — 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 app expects a service on the same machine (for example a database) that our sandbox does not run. This is a limit of our sandbox, not of your repository. (rule: local-service). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): the app expects a service on the same machine (for example a database) that our sandbox does not run. This is a limit of our sandbox, not of your repository. Last output: "[Nest] 1477 - 11/09/2026, 4:50:41 AM WARN [EventStoreBus] connecting to subscription g1 $ce-orders. Retrying... / [Nest] 1477 - 11/09/2026, 4:50:43 AM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (9)... / Error: connect ECONNREFUSED 127.0.0.1:3306 / at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1634:16) / [Nest] 1477 - 11/09/2026, 4:50:43 AM ERROR [ExceptionHandler] connect ECONNREFUSED 127.0.0.1:3306 / Error: connect ECONNREFUSED 127.0.0.1:3306 / at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1634:16)" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): the app expects a service on the same machine (for example a database) that our sandbox does not run. This is a limit of our sandbox, not of your repository. Last output: "[Nest] 1477 - 11/09/2026, 4:50:41 AM WARN [EventStoreBus] connecting to subscription g1 $ce-orders. Retrying... / [Nest] 1477 - 11/09/2026, 4:50:43 AM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (9)... / Error: connect ECONNREFUSED 127.0.0.1:3306 / at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1634:16) / [Nest] 1477 - 11/09/2026, 4:50:43 AM ERROR [ExceptionHandler] connect ECONNREFUSED 127.0.0.1:3306 / Error: connect ECONNREFUSED 127.0.0.1:3306 / at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1634:16)" No runtime evidence was gathered.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 62 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D9 · Test Distribution
2 test methods: 1 unit, 0 integration, 0 BDD, 1 e2e. The JavaScript/TypeScript suite contributes 2 `it`/`test` case(s) across 2 test file(s) declaring at least one; its tier split is read from package names and paths only.
What to do
- Improve Test Distribution — currently 3.5/10. — 2 test methods: 1 unit, 0 integration, 0 BDD, 1 e2e. The JavaScript/TypeScript suite contributes 2 `it`/`test` case(s) across 2 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in the repository root (1 tests)): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
10 deducted task-comment markers across 1292 LoC (0.3/KLoC) → score 9.4. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 10 TodoComment finding(s) in Explicit Debt — start with event-bus.provider.ts (3), user.repository.ts (2), app.controller.ts. — One of this dimension's main actionable groups (10 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 1 build units (npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
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).
D30 · Dependency Vulnerabilities
59 finding(s): 6 critical, 26 high, 23 medium, 4 low.
What to do
- Resolve the 25 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (25). — One of this dimension's main actionable groups (25 issue-level).
- Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 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
4 finding(s): 0 critical, 1 high, 3 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 2 of the 63 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
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
AX5 · Architecture & structure
AX6 · Interface segregation
AX9 · CQS / query purity
C1 · Data Protection
- No encryption usage (node:crypto createCipheriv, Web Crypto subtle.encrypt, crypto-js AES, tweetnacl/libsodium secretbox, a column-encryption layer such as typeorm-encrypted, prisma-field-encryption or mongoose-field-encryption, or MongoDB client-side field-level encryption) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — src/modules/users/entities/user.entity.ts:14
What to do
- Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
- 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
- This repository serves requests — NestFactory.create (src/main.ts:19) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — src/main.ts:19
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
DM6 · Domain ↔ infrastructure boundary
- User is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — src/modules/users/entities/user.entity.ts:11
What to do
- Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
What to do
- Run the test suite in CI via an explicit runner step (`npm test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
- `src/shared/services/config.service.ts` reports through `console.*` at line 21 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/shared/services/config.service.ts:21
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 7191 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.
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
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
- 60 typed · 1 plain JS — the untyped files are ormconfig.js. tsconfig.json switches off noImplicitAny, so the typed files are only partly type-checked.
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
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/main.ts:1, src/filters/http-exception.filter.ts:1, src/interceptors/logging.interceptor.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 51 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Unreachable from the 3 application, 2 tooling and 2 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 (3 application, 2 tooling, 2 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 (×5) — src/interceptors/logging.interceptor.ts, src/shared/grpc/setup.ts, src/providers/utils.service.ts, …
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/filters/http-exception.filter.ts:8
- 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
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `error` at line 28 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/shared/services/logger.service.ts:28
- `log` at line 24 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/interceptors/logging.interceptor.ts:24
- `log` at line 40 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/interceptors/logging.interceptor.ts:40
- `error` at line 41 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/filters/http-exception.filter.ts:41
- `error` at line 47 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/filters/http-exception.filter.ts:47
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~3.3 `!` null assertions per 1k TypeScript source lines — 5 assertion(s) across the 1535 source line(s) of the 60 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/modules/users/dtos/user.dto.ts (3), src/common/dto/abstract.dto.ts (1), src/modules/users/dtos/user-id-request-params.dto.ts (1). 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 | 61% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 69% | Strong | Solid. |
| Maturity | 90% | Exemplary | Solid. |
| Readiness | 55% | Adequate — gated by D9, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 23% | Weak — gated by C1, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 43% | Adequate | Acceptable, with room to improve. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 22 observation(s) recorded · Not scored — 34 production npm declaration(s) across 1 package.json (1 of them the product) were read for PINNING discipline (1 defect(s) reported), but the outdated/deprecated signal needs registry.npmjs.org, which could not be reached on this run, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
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 — 63 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).
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- 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 — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): the app expects a service on the same machine (for example a database) that our sandbox does not run. This is a limit of our sandbox, not of your repository. Last output: "[Nest] 1477 - 11/09/2026, 4:50:41 AM WARN [EventStoreBus] connecting to subscription g1 $ce-orders. Retrying... / [Nest] 1477 - 11/09/2026, 4:50:43 AM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (9)... / Error: connect ECONNREFUSED 127.0.0.1:3306 / at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1634:16) / [Nest] 1477 - 11/09/2026, 4:50:43 AM ERROR [ExceptionHandler] connect ECONNREFUSED 127.0.0.1:3306 / Error: connect ECONNREFUSED 127.0.0.1:3306 / at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1634:16)" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D14 License Compliance — Not scored — this repository's 473 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 10 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-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (300 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (users), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (5 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.
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- 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 — This repo declares itself a template / kata / sample; tests are deferred to the application built from it, so coverage is not scored here.
- DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 4 event handler(s); 6 CQRS handler(s)
- ED5 Idempotency — 8 mutating command handler(s)/consumer(s) detected and 8 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M2 Architecture documentation — This repo declares itself a template / kata / sample / demo — formal architecture documentation (ADRs, C4 diagrams) is deferred to a real application built from it, so its absence is not a defect here.
- 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:19 (NestFactory.create))
- 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: 62 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 36 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
- Domain fused to persistence infrastructure: User src/modules/users/entities/user.entity.ts:11
- Unlisted import 'express' src/filters/http-exception.filter.ts:8
Serious — 65 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
- TodoComment src/app.controller.ts:41
- TodoComment src/main.ts:54
- TodoComment src/shared/services/aws-s3.service.ts:19
- TodoComment src/shared/services/config.service.ts:102
- TodoComment src/providers/event-bus.provider.ts:20
- TodoComment src/providers/event-bus.provider.ts:21
- TodoComment src/providers/event-bus.provider.ts:22
- TodoComment src/modules/users/repository/user.repository.ts:26
- TodoComment src/modules/users/repository/user.repository.ts:34
- TodoComment src/modules/users/entities/user.entity.ts:27
- No test reaches this file src/main.ts:1
- No test reaches this file src/filters/http-exception.filter.ts:1
- No test reaches this file src/interceptors/logging.interceptor.ts:1
- No test reaches this file ormconfig.js:1
- No test reaches this file src/migrations/1569232747766-CreateUsersTable.ts:1
- No test reaches this file src/shared/grpc/setup.ts:1
- No test reaches this file src/providers/utils.service.ts:1
- No test reaches this file src/shared/swagger/setup.ts:1
- No test reaches this file src/exceptions/file-not-image.exception.ts:1
- No test reaches this file src/filters/rpc-exception.filter.ts:1
- Deprecated: @apollo/federation package.json:43
- Deprecated: aws-sdk package.json:57
- Deprecated: @types/express-rate-limit package.json:84
- Deprecated: @types/uuid package.json:91
- Deprecated: eslint package.json:95
- REDACTED
- REDACTED
- REDACTED
- No data-protection/encryption src/modules/users/entities/user.entity.ts:14
- No authorization src/main.ts:19
- Floating npm dependency: nestjs-eventstore
- REDACTED
- Type Safety
- Dependency Freshness
- Dead file (~50 LoC) src/interceptors/logging.interceptor.ts
- Dead file (~23 LoC) src/shared/grpc/setup.ts
- Dead file (~21 LoC) src/providers/utils.service.ts
- Dead file (~13 LoC) src/exceptions/file-not-image.exception.ts
- Dead file (~10 LoC) src/filters/rpc-exception.filter.ts
- Unused dependency '@apollo/federation'
- Unused dependency '@commitlint/lint'
- Unused dependency 'cz-conventional-changelog'
Minor — 32 finding(s)
- Deprecated: uuid REDACTED:159
- Deprecated: @apollo/subgraph REDACTED:173
- Deprecated: uuid REDACTED:272
- Deprecated: @apollo/server REDACTED:306
- Deprecated: @apollo/server-plugin-landing-page-graphql-playground REDACTED:361
- Deprecated: uuid REDACTED:426
- Deprecated: uuid REDACTED:481
- Deprecated: @humanwhocodes/config-array REDACTED:1669
- Deprecated: @humanwhocodes/object-schema REDACTED:1698
- Deprecated: uuid REDACTED:2744
- Deprecated: apollo-reporting-protobuf REDACTED:3824
- Deprecated: apollo-server-env REDACTED:3873
- Deprecated: apollo-server-types REDACTED:3885
- Deprecated: uuid REDACTED:10607
- Deprecated: querystring REDACTED:11415
- Deprecated: subscriptions-transport-ws REDACTED:12784
- Deprecated: glob REDACTED:13623
- Interpolated log message defeats structured logging src/shared/services/logger.service.ts:28
- Interpolated log message defeats structured logging src/interceptors/logging.interceptor.ts:24
- Interpolated log message defeats structured logging src/interceptors/logging.interceptor.ts:40
- Interpolated log message defeats structured logging src/filters/http-exception.filter.ts:41
- Interpolated log message defeats structured logging src/filters/http-exception.filter.ts:47
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No tests — template/sample
- CI test execution not evidenced
- Console output used as the logging channel src/shared/services/config.service.ts:21
- No SAST
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) reduce the strict null checking score
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (registry.npmjs.org unreachable)
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-e44969c3626a44c2860ca53fd71a1210/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-e44969c3626a44c2860ca53fd71a1210/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude docs . | 1 | 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 | 59 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | 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 |