Executive summary
v-checha/nestjs-template is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because three passwords or keys sit in the current code and it has uses of packages that aren't listed. It scores 53 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Production Readiness, at 45, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 8 points. Replacing the 13 deprecated dependencies comes next, worth about 7 points. Raising Production Readiness to 52 would lift the score to about 56.
Sixty known security holes in the packages the code depends on can be used by attackers. Fourteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and three passwords or keys are open to anyone who can read the repository. Updating the vulnerable packages, pinning each tool to an exact version and replacing each exposed password or key would close these risks. Fixing the weaknesses the scanner points to would fix the two security weaknesses in the code, and the three unsafe settings in infrastructure or container files need changing to safe values. The two loops of files that import each other need breaking.
The product code is 12,166 lines, about €21,000 to rebuild.
If Production Readiness rose from 45 to 52, the lowest score rated Strong, the score would rise from 53 to about 56.
New since the last survey: 27 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 29 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [CVE redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Code Duplication · Duplicated block (9 lines × 2 locations) src/application/commands/role/create-role.command.ts
- Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (9 lines × 3 locations) src/presentation/modules/admin/admin-auth.controller.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/application/commands/storage/delete-file.command.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/core/services/role.service.ts
- Code Duplication · Duplicated block (8 lines × 9 locations) src/presentation/modules/admin/admin-role.controller.ts
- Code Duplication · Duplicated block (8 lines × 3 locations) src/presentation/modules/auth/auth.controller.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) admin/src/App.tsx
- Code Duplication · Duplicated block (7 lines × 2 locations) src/core/entities/email-verification.entity.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) src/core/services/user.service.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) src/presentation/modules/admin/admin-user.controller.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) src/presentation/modules/auth/auth.controller.ts
- Code Duplication · Duplicated block (6 lines × 3 locations) src/core/entities/email-verification.entity.ts
- Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) src/infrastructure/logger/logger.interface.ts
- Code Duplication · Duplicated block (6 lines × 4 locations) src/presentation/modules/admin/admin-role.controller.ts
Rebuild cost: about €21,000 · Estimate
| Cost to rebuild | €6,900 to €35,000, for 116 to 367 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 12,166 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 application.dtos.types.jwt-payload_interface | 2 core.entities.email-verification_entity | 3 core.entities.file_entity | 4 core.value-objects.entity-id_vo | 5 infrastructure.database.prisma.prisma_service | 6 infrastructure.logger.logger_service | 7 core.repositories.file_repository_interface | 8 core.services.health_service | 9 core.value-objects.permission-id_vo | 10 core.value-objects.role-id_vo | 11 core.value-objects.user-id_vo | 12 infrastructure.repositories.base_repository | 13 presentation.modules.admin.admin-user_controller | 14 presentation.modules.auth.auth_controller | 15 core.entities.password-reset_entity | 16 core.entities.permission_entity | 17 core.entities.refresh-token_entity | 18 core.services.storage_service | 19 infrastructure.repositories.email-verification_repository | 20 infrastructure.repositories.file_repository | 21 infrastructure.repositories.otp_repository | 22 application.mappers.file_mapper | 23 core.repositories.permission_repository_interface | 24 core.value-objects.collections.permissions_collection | 25 core.entities.role_entity | 26 application.mappers.role_mapper | 27 core.repositories.role_repository_interface | 28 core.specifications.role_specifications | 29 core.value-objects.collections.roles_collection | 30 core.entities.user_entity | 31 application.mappers.user_mapper | 32 core.repositories.user_repository_interface | 33 core.services.user-authorization_service | 34 core.services.auth_service | 35 core.services.role_service | 36 core.services.user_service | 37 presentation.modules.admin.admin-auth_controller | 38 application.commands.auth.login_command | 39 application.commands.auth.refresh-token_command | 40 application.commands.auth.verify-email_command |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 application.dtos.types.jwt-payload_interface | ||||||||||||||||||||||||||||||||||||||||
| 2 core.entities.email-verification_entity | ||||||||||||||||||||||||||||||||||||||||
| 3 core.entities.file_entity | ||||||||||||||||||||||||||||||||||||||||
| 4 core.value-objects.entity-id_vo | ||||||||||||||||||||||||||||||||||||||||
| 5 infrastructure.database.prisma.prisma_service | ||||||||||||||||||||||||||||||||||||||||
| 6 infrastructure.logger.logger_service | ||||||||||||||||||||||||||||||||||||||||
| 7 core.repositories.file_repository_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 core.services.health_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 core.value-objects.permission-id_vo | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 core.value-objects.role-id_vo | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 core.value-objects.user-id_vo | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 infrastructure.repositories.base_repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 presentation.modules.admin.admin-user_controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 presentation.modules.auth.auth_controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 core.entities.password-reset_entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 core.entities.permission_entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 core.entities.refresh-token_entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 core.services.storage_service | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 infrastructure.repositories.email-verification_repository | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 infrastructure.repositories.file_repository | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 infrastructure.repositories.otp_repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 application.mappers.file_mapper | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 core.repositories.permission_repository_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 core.value-objects.collections.permissions_collection | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 core.entities.role_entity | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 application.mappers.role_mapper | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 core.repositories.role_repository_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 core.specifications.role_specifications | 1 | 1 | 8 | |||||||||||||||||||||||||||||||||||||
| 29 core.value-objects.collections.roles_collection | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 core.entities.user_entity | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 application.mappers.user_mapper | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 core.repositories.user_repository_interface | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 core.services.user-authorization_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 core.services.auth_service | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 core.services.role_service | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 core.services.user_service | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 presentation.modules.admin.admin-auth_controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 application.commands.auth.login_command | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 application.commands.auth.refresh-token_command | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 application.commands.auth.verify-email_command | 1 | 1 | 1 |
7→3 core.repositories.file_repository_interface uses core.entities.file_entity✕
- Connections
- 1 pair of types, where a type in core.repositories.file_repository_interface uses a type in core.entities.file_entity.
- The types involved
src.core.repositories.file_repository_interface.IFileRepository→src.core.entities.file_entity.File
- Direction
- core.repositories.file_repository_interface uses core.entities.file_entity, so a change to core.entities.file_entity can break core.repositories.file_repository_interface, while a change to core.repositories.file_repository_interface can't break core.entities.file_entity.
- Position
- Below the diagonal: core.repositories.file_repository_interface uses a module listed above it, which is the healthy direction.
8→5 core.services.health_service uses infrastructure.database.prisma.prisma_service✕
- Connections
- 1 pair of types, where a type in core.services.health_service uses a type in infrastructure.database.prisma.prisma_service.
- The types involved
src.core.services.health_service.HealthService→src.infrastructure.database.prisma.prisma_service.PrismaService
- Direction
- core.services.health_service uses infrastructure.database.prisma.prisma_service, so a change to infrastructure.database.prisma.prisma_service can break core.services.health_service, while a change to core.services.health_service can't break infrastructure.database.prisma.prisma_service.
- Position
- Below the diagonal: core.services.health_service uses a module listed above it, which is the healthy direction.
8→6 core.services.health_service uses infrastructure.logger.logger_service✕
- Connections
- 1 pair of types, where a type in core.services.health_service uses a type in infrastructure.logger.logger_service.
- The types involved
src.core.services.health_service.HealthService→src.infrastructure.logger.logger_service.LoggerService
- Direction
- core.services.health_service uses infrastructure.logger.logger_service, so a change to infrastructure.logger.logger_service can break core.services.health_service, while a change to core.services.health_service can't break infrastructure.logger.logger_service.
- Position
- Below the diagonal: core.services.health_service uses a module listed above it, which is the healthy direction.
9→4 core.value-objects.permission-id_vo uses core.value-objects.entity-id_vo✕
- Connections
- 1 pair of types, where a type in core.value-objects.permission-id_vo uses a type in core.value-objects.entity-id_vo.
- The types involved
src.core.value-objects.permission-id_vo.PermissionId→src.core.value-objects.entity-id_vo.EntityId
- Direction
- core.value-objects.permission-id_vo uses core.value-objects.entity-id_vo, so a change to core.value-objects.entity-id_vo can break core.value-objects.permission-id_vo, while a change to core.value-objects.permission-id_vo can't break core.value-objects.entity-id_vo.
- Position
- Below the diagonal: core.value-objects.permission-id_vo uses a module listed above it, which is the healthy direction.
10→4 core.value-objects.role-id_vo uses core.value-objects.entity-id_vo✕
- Connections
- 1 pair of types, where a type in core.value-objects.role-id_vo uses a type in core.value-objects.entity-id_vo.
- The types involved
src.core.value-objects.role-id_vo.RoleId→src.core.value-objects.entity-id_vo.EntityId
- Direction
- core.value-objects.role-id_vo uses core.value-objects.entity-id_vo, so a change to core.value-objects.entity-id_vo can break core.value-objects.role-id_vo, while a change to core.value-objects.role-id_vo can't break core.value-objects.entity-id_vo.
- Position
- Below the diagonal: core.value-objects.role-id_vo uses a module listed above it, which is the healthy direction.
11→4 core.value-objects.user-id_vo uses core.value-objects.entity-id_vo✕
- Connections
- 1 pair of types, where a type in core.value-objects.user-id_vo uses a type in core.value-objects.entity-id_vo.
- The types involved
src.core.value-objects.user-id_vo.UserId→src.core.value-objects.entity-id_vo.EntityId
- Direction
- core.value-objects.user-id_vo uses core.value-objects.entity-id_vo, so a change to core.value-objects.entity-id_vo can break core.value-objects.user-id_vo, while a change to core.value-objects.user-id_vo can't break core.value-objects.entity-id_vo.
- Position
- Below the diagonal: core.value-objects.user-id_vo uses a module listed above it, which is the healthy direction.
12→6 infrastructure.repositories.base_repository uses infrastructure.logger.logger_service✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.base_repository uses a type in infrastructure.logger.logger_service.
- The types involved
src.infrastructure.repositories.base_repository.BaseRepository→src.infrastructure.logger.logger_service.LoggerService
- Direction
- infrastructure.repositories.base_repository uses infrastructure.logger.logger_service, so a change to infrastructure.logger.logger_service can break infrastructure.repositories.base_repository, while a change to infrastructure.repositories.base_repository can't break infrastructure.logger.logger_service.
- Position
- Below the diagonal: infrastructure.repositories.base_repository uses a module listed above it, which is the healthy direction.
13→1 presentation.modules.admin.admin-user_controller uses application.dtos.types.jwt-payload_interface✕
- Connections
- 1 pair of types, where a type in presentation.modules.admin.admin-user_controller uses a type in application.dtos.types.jwt-payload_interface.
- The types involved
src.presentation.modules.admin.admin-user_controller.AdminUserController→src.application.dtos.types.jwt-payload_interface.IJwtPayload
- Direction
- presentation.modules.admin.admin-user_controller uses application.dtos.types.jwt-payload_interface, so a change to application.dtos.types.jwt-payload_interface can break presentation.modules.admin.admin-user_controller, while a change to presentation.modules.admin.admin-user_controller can't break application.dtos.types.jwt-payload_interface.
- Position
- Below the diagonal: presentation.modules.admin.admin-user_controller uses a module listed above it, which is the healthy direction.
14→1 presentation.modules.auth.auth_controller uses application.dtos.types.jwt-payload_interface✕
- Connections
- 1 pair of types, where a type in presentation.modules.auth.auth_controller uses a type in application.dtos.types.jwt-payload_interface.
- The types involved
src.presentation.modules.auth.auth_controller.AuthController→src.application.dtos.types.jwt-payload_interface.IJwtPayload
- Direction
- presentation.modules.auth.auth_controller uses application.dtos.types.jwt-payload_interface, so a change to application.dtos.types.jwt-payload_interface can break presentation.modules.auth.auth_controller, while a change to presentation.modules.auth.auth_controller can't break application.dtos.types.jwt-payload_interface.
- Position
- Below the diagonal: presentation.modules.auth.auth_controller uses a module listed above it, which is the healthy direction.
15→11 core.entities.password-reset_entity uses core.value-objects.user-id_vo✕
- Connections
- 1 pair of types, where a type in core.entities.password-reset_entity uses a type in core.value-objects.user-id_vo.
- The types involved
src.core.entities.password-reset_entity.PasswordReset→src.core.value-objects.user-id_vo.UserId
- Direction
- core.entities.password-reset_entity uses core.value-objects.user-id_vo, so a change to core.value-objects.user-id_vo can break core.entities.password-reset_entity, while a change to core.entities.password-reset_entity can't break core.value-objects.user-id_vo.
- Position
- Below the diagonal: core.entities.password-reset_entity uses a module listed above it, which is the healthy direction.
16→9 core.entities.permission_entity uses core.value-objects.permission-id_vo✕
- Connections
- 1 pair of types, where a type in core.entities.permission_entity uses a type in core.value-objects.permission-id_vo.
- The types involved
src.core.entities.permission_entity.Permission→src.core.value-objects.permission-id_vo.PermissionId
- Direction
- core.entities.permission_entity uses core.value-objects.permission-id_vo, so a change to core.value-objects.permission-id_vo can break core.entities.permission_entity, while a change to core.entities.permission_entity can't break core.value-objects.permission-id_vo.
- Position
- Below the diagonal: core.entities.permission_entity uses a module listed above it, which is the healthy direction.
17→11 core.entities.refresh-token_entity uses core.value-objects.user-id_vo✕
- Connections
- 1 pair of types, where a type in core.entities.refresh-token_entity uses a type in core.value-objects.user-id_vo.
- The types involved
src.core.entities.refresh-token_entity.RefreshToken→src.core.value-objects.user-id_vo.UserId
- Direction
- core.entities.refresh-token_entity uses core.value-objects.user-id_vo, so a change to core.value-objects.user-id_vo can break core.entities.refresh-token_entity, while a change to core.entities.refresh-token_entity can't break core.value-objects.user-id_vo.
- Position
- Below the diagonal: core.entities.refresh-token_entity uses a module listed above it, which is the healthy direction.
18→3 core.services.storage_service uses core.entities.file_entity✕
- Connections
- 2 pairs of types, where a type in core.services.storage_service uses a type in core.entities.file_entity.
- The types involved
src.core.services.storage_service.IStorageProvider→src.core.entities.file_entity.Filesrc.core.services.storage_service.StorageService→src.core.entities.file_entity.File
- Direction
- core.services.storage_service uses core.entities.file_entity, so a change to core.entities.file_entity can break core.services.storage_service, while a change to core.services.storage_service can't break core.entities.file_entity.
- Position
- Below the diagonal: core.services.storage_service uses a module listed above it, which is the healthy direction.
18→7 core.services.storage_service uses core.repositories.file_repository_interface✕
- Connections
- 1 pair of types, where a type in core.services.storage_service uses a type in core.repositories.file_repository_interface.
- The types involved
src.core.services.storage_service.StorageService→src.core.repositories.file_repository_interface.IFileRepository
- Direction
- core.services.storage_service uses core.repositories.file_repository_interface, so a change to core.repositories.file_repository_interface can break core.services.storage_service, while a change to core.services.storage_service can't break core.repositories.file_repository_interface.
- Position
- Below the diagonal: core.services.storage_service uses a module listed above it, which is the healthy direction.
19→2 infrastructure.repositories.email-verification_repository uses core.entities.email-verification_entity✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.email-verification_repository uses a type in core.entities.email-verification_entity.
- The types involved
src.infrastructure.repositories.email-verification_repository.EmailVerificationRepository→src.core.entities.email-verification_entity.EmailVerification
- Direction
- infrastructure.repositories.email-verification_repository uses core.entities.email-verification_entity, so a change to core.entities.email-verification_entity can break infrastructure.repositories.email-verification_repository, while a change to infrastructure.repositories.email-verification_repository can't break core.entities.email-verification_entity.
- Position
- Below the diagonal: infrastructure.repositories.email-verification_repository uses a module listed above it, which is the healthy direction.
19→5 infrastructure.repositories.email-verification_repository uses infrastructure.database.prisma.prisma_service✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.email-verification_repository uses a type in infrastructure.database.prisma.prisma_service.
- The types involved
src.infrastructure.repositories.email-verification_repository.EmailVerificationRepository→src.infrastructure.database.prisma.prisma_service.PrismaService
- Direction
- infrastructure.repositories.email-verification_repository uses infrastructure.database.prisma.prisma_service, so a change to infrastructure.database.prisma.prisma_service can break infrastructure.repositories.email-verification_repository, while a change to infrastructure.repositories.email-verification_repository can't break infrastructure.database.prisma.prisma_service.
- Position
- Below the diagonal: infrastructure.repositories.email-verification_repository uses a module listed above it, which is the healthy direction.
19→12 infrastructure.repositories.email-verification_repository uses infrastructure.repositories.base_repository✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.email-verification_repository uses a type in infrastructure.repositories.base_repository.
- The types involved
src.infrastructure.repositories.email-verification_repository.EmailVerificationRepository→src.infrastructure.repositories.base_repository.BaseRepository
- Direction
- infrastructure.repositories.email-verification_repository uses infrastructure.repositories.base_repository, so a change to infrastructure.repositories.base_repository can break infrastructure.repositories.email-verification_repository, while a change to infrastructure.repositories.email-verification_repository can't break infrastructure.repositories.base_repository.
- Position
- Below the diagonal: infrastructure.repositories.email-verification_repository uses a module listed above it, which is the healthy direction.
20→3 infrastructure.repositories.file_repository uses core.entities.file_entity✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.file_repository uses a type in core.entities.file_entity.
- The types involved
src.infrastructure.repositories.file_repository.FileRepository→src.core.entities.file_entity.File
- Direction
- infrastructure.repositories.file_repository uses core.entities.file_entity, so a change to core.entities.file_entity can break infrastructure.repositories.file_repository, while a change to infrastructure.repositories.file_repository can't break core.entities.file_entity.
- Position
- Below the diagonal: infrastructure.repositories.file_repository uses a module listed above it, which is the healthy direction.
20→5 infrastructure.repositories.file_repository uses infrastructure.database.prisma.prisma_service✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.file_repository uses a type in infrastructure.database.prisma.prisma_service.
- The types involved
src.infrastructure.repositories.file_repository.FileRepository→src.infrastructure.database.prisma.prisma_service.PrismaService
- Direction
- infrastructure.repositories.file_repository uses infrastructure.database.prisma.prisma_service, so a change to infrastructure.database.prisma.prisma_service can break infrastructure.repositories.file_repository, while a change to infrastructure.repositories.file_repository can't break infrastructure.database.prisma.prisma_service.
- Position
- Below the diagonal: infrastructure.repositories.file_repository uses a module listed above it, which is the healthy direction.
20→7 infrastructure.repositories.file_repository uses core.repositories.file_repository_interface✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.file_repository uses a type in core.repositories.file_repository_interface.
- The types involved
src.infrastructure.repositories.file_repository.FileRepository→src.core.repositories.file_repository_interface.IFileRepository
- Direction
- infrastructure.repositories.file_repository uses core.repositories.file_repository_interface, so a change to core.repositories.file_repository_interface can break infrastructure.repositories.file_repository, while a change to infrastructure.repositories.file_repository can't break core.repositories.file_repository_interface.
- Position
- Below the diagonal: infrastructure.repositories.file_repository uses a module listed above it, which is the healthy direction.
20→12 infrastructure.repositories.file_repository uses infrastructure.repositories.base_repository✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.file_repository uses a type in infrastructure.repositories.base_repository.
- The types involved
src.infrastructure.repositories.file_repository.FileRepository→src.infrastructure.repositories.base_repository.BaseRepository
- Direction
- infrastructure.repositories.file_repository uses infrastructure.repositories.base_repository, so a change to infrastructure.repositories.base_repository can break infrastructure.repositories.file_repository, while a change to infrastructure.repositories.file_repository can't break infrastructure.repositories.base_repository.
- Position
- Below the diagonal: infrastructure.repositories.file_repository uses a module listed above it, which is the healthy direction.
21→5 infrastructure.repositories.otp_repository uses infrastructure.database.prisma.prisma_service✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.otp_repository uses a type in infrastructure.database.prisma.prisma_service.
- The types involved
src.infrastructure.repositories.otp_repository.OtpRepository→src.infrastructure.database.prisma.prisma_service.PrismaService
- Direction
- infrastructure.repositories.otp_repository uses infrastructure.database.prisma.prisma_service, so a change to infrastructure.database.prisma.prisma_service can break infrastructure.repositories.otp_repository, while a change to infrastructure.repositories.otp_repository can't break infrastructure.database.prisma.prisma_service.
- Position
- Below the diagonal: infrastructure.repositories.otp_repository uses a module listed above it, which is the healthy direction.
21→12 infrastructure.repositories.otp_repository uses infrastructure.repositories.base_repository✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.otp_repository uses a type in infrastructure.repositories.base_repository.
- The types involved
src.infrastructure.repositories.otp_repository.OtpRepository→src.infrastructure.repositories.base_repository.BaseRepository
- Direction
- infrastructure.repositories.otp_repository uses infrastructure.repositories.base_repository, so a change to infrastructure.repositories.base_repository can break infrastructure.repositories.otp_repository, while a change to infrastructure.repositories.otp_repository can't break infrastructure.repositories.base_repository.
- Position
- Below the diagonal: infrastructure.repositories.otp_repository uses a module listed above it, which is the healthy direction.
22→3 application.mappers.file_mapper uses core.entities.file_entity✕
- Connections
- 1 pair of types, where a type in application.mappers.file_mapper uses a type in core.entities.file_entity.
- The types involved
src.application.mappers.file_mapper.FileMapper→src.core.entities.file_entity.File
- Direction
- application.mappers.file_mapper uses core.entities.file_entity, so a change to core.entities.file_entity can break application.mappers.file_mapper, while a change to application.mappers.file_mapper can't break core.entities.file_entity.
- Position
- Below the diagonal: application.mappers.file_mapper uses a module listed above it, which is the healthy direction.
22→18 application.mappers.file_mapper uses core.services.storage_service✕
- Connections
- 1 pair of types, where a type in application.mappers.file_mapper uses a type in core.services.storage_service.
- The types involved
src.application.mappers.file_mapper.FileMapper→src.core.services.storage_service.StorageService
- Direction
- application.mappers.file_mapper uses core.services.storage_service, so a change to core.services.storage_service can break application.mappers.file_mapper, while a change to application.mappers.file_mapper can't break core.services.storage_service.
- Position
- Below the diagonal: application.mappers.file_mapper uses a module listed above it, which is the healthy direction.
23→16 core.repositories.permission_repository_interface uses core.entities.permission_entity✕
- Connections
- 1 pair of types, where a type in core.repositories.permission_repository_interface uses a type in core.entities.permission_entity.
- The types involved
src.core.repositories.permission_repository_interface.IPermissionRepository→src.core.entities.permission_entity.Permission
- Direction
- core.repositories.permission_repository_interface uses core.entities.permission_entity, so a change to core.entities.permission_entity can break core.repositories.permission_repository_interface, while a change to core.repositories.permission_repository_interface can't break core.entities.permission_entity.
- Position
- Below the diagonal: core.repositories.permission_repository_interface uses a module listed above it, which is the healthy direction.
24→9 core.value-objects.collections.permissions_collection uses core.value-objects.permission-id_vo✕
- Connections
- 1 pair of types, where a type in core.value-objects.collections.permissions_collection uses a type in core.value-objects.permission-id_vo.
- The types involved
src.core.value-objects.collections.permissions_collection.PermissionsCollection→src.core.value-objects.permission-id_vo.PermissionId
- Direction
- core.value-objects.collections.permissions_collection uses core.value-objects.permission-id_vo, so a change to core.value-objects.permission-id_vo can break core.value-objects.collections.permissions_collection, while a change to core.value-objects.collections.permissions_collection can't break core.value-objects.permission-id_vo.
- Position
- Below the diagonal: core.value-objects.collections.permissions_collection uses a module listed above it, which is the healthy direction.
24→16 core.value-objects.collections.permissions_collection uses core.entities.permission_entity✕
- Connections
- 1 pair of types, where a type in core.value-objects.collections.permissions_collection uses a type in core.entities.permission_entity.
- The types involved
src.core.value-objects.collections.permissions_collection.PermissionsCollection→src.core.entities.permission_entity.Permission
- Direction
- core.value-objects.collections.permissions_collection uses core.entities.permission_entity, so a change to core.entities.permission_entity can break core.value-objects.collections.permissions_collection, while a change to core.value-objects.collections.permissions_collection can't break core.entities.permission_entity.
- Position
- Below the diagonal: core.value-objects.collections.permissions_collection uses a module listed above it, which is the healthy direction.
25→9 core.entities.role_entity uses core.value-objects.permission-id_vo✕
- Connections
- 1 pair of types, where a type in core.entities.role_entity uses a type in core.value-objects.permission-id_vo.
- The types involved
src.core.entities.role_entity.Role→src.core.value-objects.permission-id_vo.PermissionId
- Direction
- core.entities.role_entity uses core.value-objects.permission-id_vo, so a change to core.value-objects.permission-id_vo can break core.entities.role_entity, while a change to core.entities.role_entity can't break core.value-objects.permission-id_vo.
- Position
- Below the diagonal: core.entities.role_entity uses a module listed above it, which is the healthy direction.
25→10 core.entities.role_entity uses core.value-objects.role-id_vo✕
- Connections
- 1 pair of types, where a type in core.entities.role_entity uses a type in core.value-objects.role-id_vo.
- The types involved
src.core.entities.role_entity.Role→src.core.value-objects.role-id_vo.RoleId
- Direction
- core.entities.role_entity uses core.value-objects.role-id_vo, so a change to core.value-objects.role-id_vo can break core.entities.role_entity, while a change to core.entities.role_entity can't break core.value-objects.role-id_vo.
- Position
- Below the diagonal: core.entities.role_entity uses a module listed above it, which is the healthy direction.
25→16 core.entities.role_entity uses core.entities.permission_entity✕
- Connections
- 1 pair of types, where a type in core.entities.role_entity uses a type in core.entities.permission_entity.
- The types involved
src.core.entities.role_entity.Role→src.core.entities.permission_entity.Permission
- Direction
- core.entities.role_entity uses core.entities.permission_entity, so a change to core.entities.permission_entity can break core.entities.role_entity, while a change to core.entities.role_entity can't break core.entities.permission_entity.
- Position
- Below the diagonal: core.entities.role_entity uses a module listed above it, which is the healthy direction.
25→24 core.entities.role_entity uses core.value-objects.collections.permissions_collection✕
- Connections
- 1 pair of types, where a type in core.entities.role_entity uses a type in core.value-objects.collections.permissions_collection.
- The types involved
src.core.entities.role_entity.Role→src.core.value-objects.collections.permissions_collection.PermissionsCollection
- Direction
- core.entities.role_entity uses core.value-objects.collections.permissions_collection, so a change to core.value-objects.collections.permissions_collection can break core.entities.role_entity, while a change to core.entities.role_entity can't break core.value-objects.collections.permissions_collection.
- Position
- Below the diagonal: core.entities.role_entity uses a module listed above it, which is the healthy direction.
26→16 application.mappers.role_mapper uses core.entities.permission_entity✕
- Connections
- 1 pair of types, where a type in application.mappers.role_mapper uses a type in core.entities.permission_entity.
- The types involved
src.application.mappers.role_mapper.RoleMapper→src.core.entities.permission_entity.Permission
- Direction
- application.mappers.role_mapper uses core.entities.permission_entity, so a change to core.entities.permission_entity can break application.mappers.role_mapper, while a change to application.mappers.role_mapper can't break core.entities.permission_entity.
- Position
- Below the diagonal: application.mappers.role_mapper uses a module listed above it, which is the healthy direction.
26→25 application.mappers.role_mapper uses core.entities.role_entity✕
- Connections
- 1 pair of types, where a type in application.mappers.role_mapper uses a type in core.entities.role_entity.
- The types involved
src.application.mappers.role_mapper.RoleMapper→src.core.entities.role_entity.Role
- Direction
- application.mappers.role_mapper uses core.entities.role_entity, so a change to core.entities.role_entity can break application.mappers.role_mapper, while a change to application.mappers.role_mapper can't break core.entities.role_entity.
- Position
- Below the diagonal: application.mappers.role_mapper uses a module listed above it, which is the healthy direction.
27→25 core.repositories.role_repository_interface uses core.entities.role_entity✕
- Connections
- 1 pair of types, where a type in core.repositories.role_repository_interface uses a type in core.entities.role_entity.
- The types involved
src.core.repositories.role_repository_interface.IRoleRepository→src.core.entities.role_entity.Role
- Direction
- core.repositories.role_repository_interface uses core.entities.role_entity, so a change to core.entities.role_entity can break core.repositories.role_repository_interface, while a change to core.repositories.role_repository_interface can't break core.entities.role_entity.
- Position
- Below the diagonal: core.repositories.role_repository_interface uses a module listed above it, which is the healthy direction.
28→9 core.specifications.role_specifications uses core.value-objects.permission-id_vo✕
- Connections
- 1 pair of types, where a type in core.specifications.role_specifications uses a type in core.value-objects.permission-id_vo.
- The types involved
src.core.specifications.role_specifications.RoleHasPermissionSpecification→src.core.value-objects.permission-id_vo.PermissionId
- Direction
- core.specifications.role_specifications uses core.value-objects.permission-id_vo, so a change to core.value-objects.permission-id_vo can break core.specifications.role_specifications, while a change to core.specifications.role_specifications can't break core.value-objects.permission-id_vo.
- Position
- Below the diagonal: core.specifications.role_specifications uses a module listed above it, which is the healthy direction.
28→16 core.specifications.role_specifications uses core.entities.permission_entity✕
- Connections
- 1 pair of types, where a type in core.specifications.role_specifications uses a type in core.entities.permission_entity.
- The types involved
src.core.specifications.role_specifications.CanAssignPermissionToRoleSpecification→src.core.entities.permission_entity.Permission
- Direction
- core.specifications.role_specifications uses core.entities.permission_entity, so a change to core.entities.permission_entity can break core.specifications.role_specifications, while a change to core.specifications.role_specifications can't break core.entities.permission_entity.
- Position
- Below the diagonal: core.specifications.role_specifications uses a module listed above it, which is the healthy direction.
28→25 core.specifications.role_specifications uses core.entities.role_entity✕
- Connections
- 8 pairs of types, where a type in core.specifications.role_specifications uses a type in core.entities.role_entity.
- The types involved
src.core.specifications.role_specifications.AdminRoleSpecification→src.core.entities.role_entity.Rolesrc.core.specifications.role_specifications.BasicUserRoleSpecification→src.core.entities.role_entity.Rolesrc.core.specifications.role_specifications.CanAssignPermissionToRoleSpecification→src.core.entities.role_entity.Rolesrc.core.specifications.role_specifications.CanDeleteRoleSpecification→src.core.entities.role_entity.Rolesrc.core.specifications.role_specifications.DefaultRoleSpecification→src.core.entities.role_entity.Rolesrc.core.specifications.role_specifications.HasMinimumPermissionsSpecification→src.core.entities.role_entity.Rolesrc.core.specifications.role_specifications.RoleHasPermissionByNameSpecification→src.core.entities.role_entity.Rolesrc.core.specifications.role_specifications.RoleHasPermissionSpecification→src.core.entities.role_entity.Role
- Direction
- core.specifications.role_specifications uses core.entities.role_entity, so a change to core.entities.role_entity can break core.specifications.role_specifications, while a change to core.specifications.role_specifications can't break core.entities.role_entity.
- Position
- Below the diagonal: core.specifications.role_specifications uses a module listed above it, which is the healthy direction.
29→10 core.value-objects.collections.roles_collection uses core.value-objects.role-id_vo✕
- Connections
- 1 pair of types, where a type in core.value-objects.collections.roles_collection uses a type in core.value-objects.role-id_vo.
- The types involved
src.core.value-objects.collections.roles_collection.RolesCollection→src.core.value-objects.role-id_vo.RoleId
- Direction
- core.value-objects.collections.roles_collection uses core.value-objects.role-id_vo, so a change to core.value-objects.role-id_vo can break core.value-objects.collections.roles_collection, while a change to core.value-objects.collections.roles_collection can't break core.value-objects.role-id_vo.
- Position
- Below the diagonal: core.value-objects.collections.roles_collection uses a module listed above it, which is the healthy direction.
29→24 core.value-objects.collections.roles_collection uses core.value-objects.collections.permissions_collection✕
- Connections
- 1 pair of types, where a type in core.value-objects.collections.roles_collection uses a type in core.value-objects.collections.permissions_collection.
- The types involved
src.core.value-objects.collections.roles_collection.RolesCollection→src.core.value-objects.collections.permissions_collection.PermissionsCollection
- Direction
- core.value-objects.collections.roles_collection uses core.value-objects.collections.permissions_collection, so a change to core.value-objects.collections.permissions_collection can break core.value-objects.collections.roles_collection, while a change to core.value-objects.collections.roles_collection can't break core.value-objects.collections.permissions_collection.
- Position
- Below the diagonal: core.value-objects.collections.roles_collection uses a module listed above it, which is the healthy direction.
29→25 core.value-objects.collections.roles_collection uses core.entities.role_entity✕
- Connections
- 1 pair of types, where a type in core.value-objects.collections.roles_collection uses a type in core.entities.role_entity.
- The types involved
src.core.value-objects.collections.roles_collection.RolesCollection→src.core.entities.role_entity.Role
- Direction
- core.value-objects.collections.roles_collection uses core.entities.role_entity, so a change to core.entities.role_entity can break core.value-objects.collections.roles_collection, while a change to core.value-objects.collections.roles_collection can't break core.entities.role_entity.
- Position
- Below the diagonal: core.value-objects.collections.roles_collection uses a module listed above it, which is the healthy direction.
30→10 core.entities.user_entity uses core.value-objects.role-id_vo✕
- Connections
- 1 pair of types, where a type in core.entities.user_entity uses a type in core.value-objects.role-id_vo.
- The types involved
src.core.entities.user_entity.User→src.core.value-objects.role-id_vo.RoleId
- Direction
- core.entities.user_entity uses core.value-objects.role-id_vo, so a change to core.value-objects.role-id_vo can break core.entities.user_entity, while a change to core.entities.user_entity can't break core.value-objects.role-id_vo.
- Position
- Below the diagonal: core.entities.user_entity uses a module listed above it, which is the healthy direction.
30→11 core.entities.user_entity uses core.value-objects.user-id_vo✕
- Connections
- 1 pair of types, where a type in core.entities.user_entity uses a type in core.value-objects.user-id_vo.
- The types involved
src.core.entities.user_entity.User→src.core.value-objects.user-id_vo.UserId
- Direction
- core.entities.user_entity uses core.value-objects.user-id_vo, so a change to core.value-objects.user-id_vo can break core.entities.user_entity, while a change to core.entities.user_entity can't break core.value-objects.user-id_vo.
- Position
- Below the diagonal: core.entities.user_entity uses a module listed above it, which is the healthy direction.
30→25 core.entities.user_entity uses core.entities.role_entity✕
- Connections
- 1 pair of types, where a type in core.entities.user_entity uses a type in core.entities.role_entity.
- The types involved
src.core.entities.user_entity.User→src.core.entities.role_entity.Role
- Direction
- core.entities.user_entity uses core.entities.role_entity, so a change to core.entities.role_entity can break core.entities.user_entity, while a change to core.entities.user_entity can't break core.entities.role_entity.
- Position
- Below the diagonal: core.entities.user_entity uses a module listed above it, which is the healthy direction.
30→29 core.entities.user_entity uses core.value-objects.collections.roles_collection✕
- Connections
- 1 pair of types, where a type in core.entities.user_entity uses a type in core.value-objects.collections.roles_collection.
- The types involved
src.core.entities.user_entity.User→src.core.value-objects.collections.roles_collection.RolesCollection
- Direction
- core.entities.user_entity uses core.value-objects.collections.roles_collection, so a change to core.value-objects.collections.roles_collection can break core.entities.user_entity, while a change to core.entities.user_entity can't break core.value-objects.collections.roles_collection.
- Position
- Below the diagonal: core.entities.user_entity uses a module listed above it, which is the healthy direction.
31→25 application.mappers.user_mapper uses core.entities.role_entity✕
- Connections
- 1 pair of types, where a type in application.mappers.user_mapper uses a type in core.entities.role_entity.
- The types involved
src.application.mappers.user_mapper.UserMapper→src.core.entities.role_entity.Role
- Direction
- application.mappers.user_mapper uses core.entities.role_entity, so a change to core.entities.role_entity can break application.mappers.user_mapper, while a change to application.mappers.user_mapper can't break core.entities.role_entity.
- Position
- Below the diagonal: application.mappers.user_mapper uses a module listed above it, which is the healthy direction.
31→30 application.mappers.user_mapper uses core.entities.user_entity✕
- Connections
- 1 pair of types, where a type in application.mappers.user_mapper uses a type in core.entities.user_entity.
- The types involved
src.application.mappers.user_mapper.UserMapper→src.core.entities.user_entity.User
- Direction
- application.mappers.user_mapper uses core.entities.user_entity, so a change to core.entities.user_entity can break application.mappers.user_mapper, while a change to application.mappers.user_mapper can't break core.entities.user_entity.
- Position
- Below the diagonal: application.mappers.user_mapper uses a module listed above it, which is the healthy direction.
32→30 core.repositories.user_repository_interface uses core.entities.user_entity✕
- Connections
- 1 pair of types, where a type in core.repositories.user_repository_interface uses a type in core.entities.user_entity.
- The types involved
src.core.repositories.user_repository_interface.IUserRepository→src.core.entities.user_entity.User
- Direction
- core.repositories.user_repository_interface uses core.entities.user_entity, so a change to core.entities.user_entity can break core.repositories.user_repository_interface, while a change to core.repositories.user_repository_interface can't break core.entities.user_entity.
- Position
- Below the diagonal: core.repositories.user_repository_interface uses a module listed above it, which is the healthy direction.
33→25 core.services.user-authorization_service uses core.entities.role_entity✕
- Connections
- 1 pair of types, where a type in core.services.user-authorization_service uses a type in core.entities.role_entity.
- The types involved
src.core.services.user-authorization_service.UserAuthorizationService→src.core.entities.role_entity.Role
- Direction
- core.services.user-authorization_service uses core.entities.role_entity, so a change to core.entities.role_entity can break core.services.user-authorization_service, while a change to core.services.user-authorization_service can't break core.entities.role_entity.
- Position
- Below the diagonal: core.services.user-authorization_service uses a module listed above it, which is the healthy direction.
33→30 core.services.user-authorization_service uses core.entities.user_entity✕
- Connections
- 1 pair of types, where a type in core.services.user-authorization_service uses a type in core.entities.user_entity.
- The types involved
src.core.services.user-authorization_service.UserAuthorizationService→src.core.entities.user_entity.User
- Direction
- core.services.user-authorization_service uses core.entities.user_entity, so a change to core.entities.user_entity can break core.services.user-authorization_service, while a change to core.services.user-authorization_service can't break core.entities.user_entity.
- Position
- Below the diagonal: core.services.user-authorization_service uses a module listed above it, which is the healthy direction.
34→6 core.services.auth_service uses infrastructure.logger.logger_service✕
- Connections
- 1 pair of types, where a type in core.services.auth_service uses a type in infrastructure.logger.logger_service.
- The types involved
src.core.services.auth_service.AuthService→src.infrastructure.logger.logger_service.LoggerService
- Direction
- core.services.auth_service uses infrastructure.logger.logger_service, so a change to infrastructure.logger.logger_service can break core.services.auth_service, while a change to core.services.auth_service can't break infrastructure.logger.logger_service.
- Position
- Below the diagonal: core.services.auth_service uses a module listed above it, which is the healthy direction.
34→17 core.services.auth_service uses core.entities.refresh-token_entity✕
- Connections
- 1 pair of types, where a type in core.services.auth_service uses a type in core.entities.refresh-token_entity.
- The types involved
src.core.services.auth_service.AuthService→src.core.entities.refresh-token_entity.RefreshToken
- Direction
- core.services.auth_service uses core.entities.refresh-token_entity, so a change to core.entities.refresh-token_entity can break core.services.auth_service, while a change to core.services.auth_service can't break core.entities.refresh-token_entity.
- Position
- Below the diagonal: core.services.auth_service uses a module listed above it, which is the healthy direction.
34→30 core.services.auth_service uses core.entities.user_entity✕
- Connections
- 1 pair of types, where a type in core.services.auth_service uses a type in core.entities.user_entity.
- The types involved
src.core.services.auth_service.AuthService→src.core.entities.user_entity.User
- Direction
- core.services.auth_service uses core.entities.user_entity, so a change to core.entities.user_entity can break core.services.auth_service, while a change to core.services.auth_service can't break core.entities.user_entity.
- Position
- Below the diagonal: core.services.auth_service uses a module listed above it, which is the healthy direction.
34→32 core.services.auth_service uses core.repositories.user_repository_interface✕
- Connections
- 1 pair of types, where a type in core.services.auth_service uses a type in core.repositories.user_repository_interface.
- The types involved
src.core.services.auth_service.AuthService→src.core.repositories.user_repository_interface.IUserRepository
- Direction
- core.services.auth_service uses core.repositories.user_repository_interface, so a change to core.repositories.user_repository_interface can break core.services.auth_service, while a change to core.services.auth_service can't break core.repositories.user_repository_interface.
- Position
- Below the diagonal: core.services.auth_service uses a module listed above it, which is the healthy direction.
35→23 core.services.role_service uses core.repositories.permission_repository_interface✕
- Connections
- 1 pair of types, where a type in core.services.role_service uses a type in core.repositories.permission_repository_interface.
- The types involved
src.core.services.role_service.RoleService→src.core.repositories.permission_repository_interface.IPermissionRepository
- Direction
- core.services.role_service uses core.repositories.permission_repository_interface, so a change to core.repositories.permission_repository_interface can break core.services.role_service, while a change to core.services.role_service can't break core.repositories.permission_repository_interface.
- Position
- Below the diagonal: core.services.role_service uses a module listed above it, which is the healthy direction.
35→25 core.services.role_service uses core.entities.role_entity✕
- Connections
- 1 pair of types, where a type in core.services.role_service uses a type in core.entities.role_entity.
- The types involved
src.core.services.role_service.RoleService→src.core.entities.role_entity.Role
- Direction
- core.services.role_service uses core.entities.role_entity, so a change to core.entities.role_entity can break core.services.role_service, while a change to core.services.role_service can't break core.entities.role_entity.
- Position
- Below the diagonal: core.services.role_service uses a module listed above it, which is the healthy direction.
35→27 core.services.role_service uses core.repositories.role_repository_interface✕
- Connections
- 1 pair of types, where a type in core.services.role_service uses a type in core.repositories.role_repository_interface.
- The types involved
src.core.services.role_service.RoleService→src.core.repositories.role_repository_interface.IRoleRepository
- Direction
- core.services.role_service uses core.repositories.role_repository_interface, so a change to core.repositories.role_repository_interface can break core.services.role_service, while a change to core.services.role_service can't break core.repositories.role_repository_interface.
- Position
- Below the diagonal: core.services.role_service uses a module listed above it, which is the healthy direction.
35→32 core.services.role_service uses core.repositories.user_repository_interface✕
- Connections
- 1 pair of types, where a type in core.services.role_service uses a type in core.repositories.user_repository_interface.
- The types involved
src.core.services.role_service.RoleService→src.core.repositories.user_repository_interface.IUserRepository
- Direction
- core.services.role_service uses core.repositories.user_repository_interface, so a change to core.repositories.user_repository_interface can break core.services.role_service, while a change to core.services.role_service can't break core.repositories.user_repository_interface.
- Position
- Below the diagonal: core.services.role_service uses a module listed above it, which is the healthy direction.
35→33 core.services.role_service uses core.services.user-authorization_service✕
- Connections
- 1 pair of types, where a type in core.services.role_service uses a type in core.services.user-authorization_service.
- The types involved
src.core.services.role_service.RoleService→src.core.services.user-authorization_service.UserAuthorizationService
- Direction
- core.services.role_service uses core.services.user-authorization_service, so a change to core.services.user-authorization_service can break core.services.role_service, while a change to core.services.role_service can't break core.services.user-authorization_service.
- Position
- Below the diagonal: core.services.role_service uses a module listed above it, which is the healthy direction.
36→27 core.services.user_service uses core.repositories.role_repository_interface✕
- Connections
- 1 pair of types, where a type in core.services.user_service uses a type in core.repositories.role_repository_interface.
- The types involved
src.core.services.user_service.UserService→src.core.repositories.role_repository_interface.IRoleRepository
- Direction
- core.services.user_service uses core.repositories.role_repository_interface, so a change to core.repositories.role_repository_interface can break core.services.user_service, while a change to core.services.user_service can't break core.repositories.role_repository_interface.
- Position
- Below the diagonal: core.services.user_service uses a module listed above it, which is the healthy direction.
36→30 core.services.user_service uses core.entities.user_entity✕
- Connections
- 1 pair of types, where a type in core.services.user_service uses a type in core.entities.user_entity.
- The types involved
src.core.services.user_service.UserService→src.core.entities.user_entity.User
- Direction
- core.services.user_service uses core.entities.user_entity, so a change to core.entities.user_entity can break core.services.user_service, while a change to core.services.user_service can't break core.entities.user_entity.
- Position
- Below the diagonal: core.services.user_service uses a module listed above it, which is the healthy direction.
36→32 core.services.user_service uses core.repositories.user_repository_interface✕
- Connections
- 1 pair of types, where a type in core.services.user_service uses a type in core.repositories.user_repository_interface.
- The types involved
src.core.services.user_service.UserService→src.core.repositories.user_repository_interface.IUserRepository
- Direction
- core.services.user_service uses core.repositories.user_repository_interface, so a change to core.repositories.user_repository_interface can break core.services.user_service, while a change to core.services.user_service can't break core.repositories.user_repository_interface.
- Position
- Below the diagonal: core.services.user_service uses a module listed above it, which is the healthy direction.
36→33 core.services.user_service uses core.services.user-authorization_service✕
- Connections
- 1 pair of types, where a type in core.services.user_service uses a type in core.services.user-authorization_service.
- The types involved
src.core.services.user_service.UserService→src.core.services.user-authorization_service.UserAuthorizationService
- Direction
- core.services.user_service uses core.services.user-authorization_service, so a change to core.services.user-authorization_service can break core.services.user_service, while a change to core.services.user_service can't break core.services.user-authorization_service.
- Position
- Below the diagonal: core.services.user_service uses a module listed above it, which is the healthy direction.
37→1 presentation.modules.admin.admin-auth_controller uses application.dtos.types.jwt-payload_interface✕
- Connections
- 1 pair of types, where a type in presentation.modules.admin.admin-auth_controller uses a type in application.dtos.types.jwt-payload_interface.
- The types involved
src.presentation.modules.admin.admin-auth_controller.AdminAuthController→src.application.dtos.types.jwt-payload_interface.IJwtPayload
- Direction
- presentation.modules.admin.admin-auth_controller uses application.dtos.types.jwt-payload_interface, so a change to application.dtos.types.jwt-payload_interface can break presentation.modules.admin.admin-auth_controller, while a change to presentation.modules.admin.admin-auth_controller can't break application.dtos.types.jwt-payload_interface.
- Position
- Below the diagonal: presentation.modules.admin.admin-auth_controller uses a module listed above it, which is the healthy direction.
37→32 presentation.modules.admin.admin-auth_controller uses core.repositories.user_repository_interface✕
- Connections
- 1 pair of types, where a type in presentation.modules.admin.admin-auth_controller uses a type in core.repositories.user_repository_interface.
- The types involved
src.presentation.modules.admin.admin-auth_controller.AdminAuthController→src.core.repositories.user_repository_interface.IUserRepository
- Direction
- presentation.modules.admin.admin-auth_controller uses core.repositories.user_repository_interface, so a change to core.repositories.user_repository_interface can break presentation.modules.admin.admin-auth_controller, while a change to presentation.modules.admin.admin-auth_controller can't break core.repositories.user_repository_interface.
- Position
- Below the diagonal: presentation.modules.admin.admin-auth_controller uses a module listed above it, which is the healthy direction.
37→33 presentation.modules.admin.admin-auth_controller uses core.services.user-authorization_service✕
- Connections
- 1 pair of types, where a type in presentation.modules.admin.admin-auth_controller uses a type in core.services.user-authorization_service.
- The types involved
src.presentation.modules.admin.admin-auth_controller.AdminAuthController→src.core.services.user-authorization_service.UserAuthorizationService
- Direction
- presentation.modules.admin.admin-auth_controller uses core.services.user-authorization_service, so a change to core.services.user-authorization_service can break presentation.modules.admin.admin-auth_controller, while a change to presentation.modules.admin.admin-auth_controller can't break core.services.user-authorization_service.
- Position
- Below the diagonal: presentation.modules.admin.admin-auth_controller uses a module listed above it, which is the healthy direction.
38→6 application.commands.auth.login_command uses infrastructure.logger.logger_service✕
- Connections
- 1 pair of types, where a type in application.commands.auth.login_command uses a type in infrastructure.logger.logger_service.
- The types involved
src.application.commands.auth.login_command.LoginCommandHandler→src.infrastructure.logger.logger_service.LoggerService
- Direction
- application.commands.auth.login_command uses infrastructure.logger.logger_service, so a change to infrastructure.logger.logger_service can break application.commands.auth.login_command, while a change to application.commands.auth.login_command can't break infrastructure.logger.logger_service.
- Position
- Below the diagonal: application.commands.auth.login_command uses a module listed above it, which is the healthy direction.
38→27 application.commands.auth.login_command uses core.repositories.role_repository_interface✕
- Connections
- 1 pair of types, where a type in application.commands.auth.login_command uses a type in core.repositories.role_repository_interface.
- The types involved
src.application.commands.auth.login_command.LoginCommandHandler→src.core.repositories.role_repository_interface.IRoleRepository
- Direction
- application.commands.auth.login_command uses core.repositories.role_repository_interface, so a change to core.repositories.role_repository_interface can break application.commands.auth.login_command, while a change to application.commands.auth.login_command can't break core.repositories.role_repository_interface.
- Position
- Below the diagonal: application.commands.auth.login_command uses a module listed above it, which is the healthy direction.
38→34 application.commands.auth.login_command uses core.services.auth_service✕
- Connections
- 1 pair of types, where a type in application.commands.auth.login_command uses a type in core.services.auth_service.
- The types involved
src.application.commands.auth.login_command.LoginCommandHandler→src.core.services.auth_service.AuthService
- Direction
- application.commands.auth.login_command uses core.services.auth_service, so a change to core.services.auth_service can break application.commands.auth.login_command, while a change to application.commands.auth.login_command can't break core.services.auth_service.
- Position
- Below the diagonal: application.commands.auth.login_command uses a module listed above it, which is the healthy direction.
38→36 application.commands.auth.login_command uses core.services.user_service✕
- Connections
- 1 pair of types, where a type in application.commands.auth.login_command uses a type in core.services.user_service.
- The types involved
src.application.commands.auth.login_command.LoginCommandHandler→src.core.services.user_service.UserService
- Direction
- application.commands.auth.login_command uses core.services.user_service, so a change to core.services.user_service can break application.commands.auth.login_command, while a change to application.commands.auth.login_command can't break core.services.user_service.
- Position
- Below the diagonal: application.commands.auth.login_command uses a module listed above it, which is the healthy direction.
39→27 application.commands.auth.refresh-token_command uses core.repositories.role_repository_interface✕
- Connections
- 1 pair of types, where a type in application.commands.auth.refresh-token_command uses a type in core.repositories.role_repository_interface.
- The types involved
src.application.commands.auth.refresh-token_command.RefreshTokenCommandHandler→src.core.repositories.role_repository_interface.IRoleRepository
- Direction
- application.commands.auth.refresh-token_command uses core.repositories.role_repository_interface, so a change to core.repositories.role_repository_interface can break application.commands.auth.refresh-token_command, while a change to application.commands.auth.refresh-token_command can't break core.repositories.role_repository_interface.
- Position
- Below the diagonal: application.commands.auth.refresh-token_command uses a module listed above it, which is the healthy direction.
39→32 application.commands.auth.refresh-token_command uses core.repositories.user_repository_interface✕
- Connections
- 1 pair of types, where a type in application.commands.auth.refresh-token_command uses a type in core.repositories.user_repository_interface.
- The types involved
src.application.commands.auth.refresh-token_command.RefreshTokenCommandHandler→src.core.repositories.user_repository_interface.IUserRepository
- Direction
- application.commands.auth.refresh-token_command uses core.repositories.user_repository_interface, so a change to core.repositories.user_repository_interface can break application.commands.auth.refresh-token_command, while a change to application.commands.auth.refresh-token_command can't break core.repositories.user_repository_interface.
- Position
- Below the diagonal: application.commands.auth.refresh-token_command uses a module listed above it, which is the healthy direction.
39→34 application.commands.auth.refresh-token_command uses core.services.auth_service✕
- Connections
- 1 pair of types, where a type in application.commands.auth.refresh-token_command uses a type in core.services.auth_service.
- The types involved
src.application.commands.auth.refresh-token_command.RefreshTokenCommandHandler→src.core.services.auth_service.AuthService
- Direction
- application.commands.auth.refresh-token_command uses core.services.auth_service, so a change to core.services.auth_service can break application.commands.auth.refresh-token_command, while a change to application.commands.auth.refresh-token_command can't break core.services.auth_service.
- Position
- Below the diagonal: application.commands.auth.refresh-token_command uses a module listed above it, which is the healthy direction.
40→27 application.commands.auth.verify-email_command uses core.repositories.role_repository_interface✕
- Connections
- 1 pair of types, where a type in application.commands.auth.verify-email_command uses a type in core.repositories.role_repository_interface.
- The types involved
src.application.commands.auth.verify-email_command.VerifyEmailCommandHandler→src.core.repositories.role_repository_interface.IRoleRepository
- Direction
- application.commands.auth.verify-email_command uses core.repositories.role_repository_interface, so a change to core.repositories.role_repository_interface can break application.commands.auth.verify-email_command, while a change to application.commands.auth.verify-email_command can't break core.repositories.role_repository_interface.
- Position
- Below the diagonal: application.commands.auth.verify-email_command uses a module listed above it, which is the healthy direction.
40→32 application.commands.auth.verify-email_command uses core.repositories.user_repository_interface✕
- Connections
- 1 pair of types, where a type in application.commands.auth.verify-email_command uses a type in core.repositories.user_repository_interface.
- The types involved
src.application.commands.auth.verify-email_command.VerifyEmailCommandHandler→src.core.repositories.user_repository_interface.IUserRepository
- Direction
- application.commands.auth.verify-email_command uses core.repositories.user_repository_interface, so a change to core.repositories.user_repository_interface can break application.commands.auth.verify-email_command, while a change to application.commands.auth.verify-email_command can't break core.repositories.user_repository_interface.
- Position
- Below the diagonal: application.commands.auth.verify-email_command uses a module listed above it, which is the healthy direction.
40→34 application.commands.auth.verify-email_command uses core.services.auth_service✕
- Connections
- 1 pair of types, where a type in application.commands.auth.verify-email_command uses a type in core.services.auth_service.
- The types involved
src.application.commands.auth.verify-email_command.VerifyEmailCommandHandler→src.core.services.auth_service.AuthService
- Direction
- application.commands.auth.verify-email_command uses core.services.auth_service, so a change to core.services.auth_service can break application.commands.auth.verify-email_command, while a change to application.commands.auth.verify-email_command can't break core.services.auth_service.
- Position
- Below the diagonal: application.commands.auth.verify-email_command 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 | 87 | High / Critical |
| A05:2025 — Injection | 27 | High / Critical |
| A02:2025 — Security Misconfiguration | 7 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
| A01:2025 — Broken Access Control | 1 | Medium |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED; Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13); Resolve the 119 Low coverage finding(s) in Code Coverage — start with index.ts (14), change-password.command.ts (2), update-user.command.ts (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED. | +7.6 pts | Low | Secret Scanning |
| Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13). | +6.8 pts | Medium | Dependency Hygiene |
| Resolve the 3 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (3). | +2.4 pts | Low | Dependency Hygiene |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +4.4 pts | Medium | Dependency Hygiene |
| Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / Secret Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps. | +4.1 pts | Medium | Data Protection |
| Improve Test Distribution — currently 6.4/10. | +3.6 pts | Medium | Test Distribution |
| Resolve the 119 Low coverage finding(s) in Code Coverage — start with index.ts (14), change-password.command.ts (2), update-user.command.ts (2). | +4.8 pts | High | Code Coverage |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (2). | +1.3 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 0.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.3 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.2 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.5 | Near-clean | Secret Scanning: Leaked secret: REDACTED |
| src/core/services/role.service.ts | 6.5 | Near-clean | Cognitive Complexity: RoleService.updateRole (cognitive 16) |
| package.json | 6.5 | Near-clean | Dependency Hygiene: Deprecated: multer |
| admin/src/pages/roles/edit.tsx | 7.4 | Near-clean | Cyclomatic Complexity: edit.RoleEdit (cyclomatic 24) |
| test/auth.e2e-spec.ts | 7.4 | Near-clean | Test Quality: Skipped test: should get current user info with valid token |
| src/core/services/user.service.ts | 7.6 | Near-clean | Cognitive Complexity: UserService.updateUserDetails (cognitive 26) |
| admin/src/pages/health/index.tsx | 7.8 | Near-clean | Cyclomatic Complexity: index.HealthMonitor (cyclomatic 37) |
| admin/src/pages/users/list.tsx | 7.8 | Near-clean | Cyclomatic Complexity: list.UserList (cyclomatic 18) |
| admin/src/pages/users/show.tsx | 7.8 | Near-clean | Cyclomatic Complexity: show.UserShow (cyclomatic 16) |
| src/application/commands/auth/send-verification-email.command.ts | 7.8 | Near-clean | Code Coverage: Low coverage: src/application/commands/auth/send-verification-email.command.ts |
| test/role.e2e-spec.ts | 7.8 | Near-clean | Test Quality: Skipped test: should get role list when authenticated with role:read permission |
| REDACTED | 7.9 | Near-clean | Data Compliance (PII/GDPR): Medium: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 86 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 86 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, 534 of 585 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
- 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.
- D32 Data Compliance (PII/GDPR) — 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. `REDACTED`, `src/application/queries/admin/get-health.query.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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 REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:39 -------------------- 37 | 38 | # Install production dependencies only 39 | >>> RUN npm ci --only=production 40 | 41 | # Copy Prisma schema -------------------- ERROR: failed to solve: process "/bin/sh -c npm ci --only=production" did not complete successfully: exit code: 127; runtime evidence skipped.
- 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.
- R10 Code Duplication — 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. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
- 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. 198 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- 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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- 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.
- C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was index.HealthMonitor at 37.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with index.HealthMonitor (cyclomatic 37), edit.RoleEdit (cyclomatic 24), list.UserList (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was UserService.updateUserDetails at 26.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with UserService.updateUserDetails (cognitive 26), index.HealthMonitor (cognitive 24), edit.RoleEdit (cognitive 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
6 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 6 FunctionTooLong finding(s) in God Classes — start with edit.tsx (2), App.tsx, show.tsx. — One of this dimension's main actionable groups (6 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D5 · Coupling
2 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 36 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D8 · Code Coverage
Line coverage 19.1% — 119 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest via `npm ci --ignore-scripts` in the repository root).
What to do
- Resolve the 119 Low coverage finding(s) in Code Coverage — start with index.ts (14), change-password.command.ts (2), update-user.command.ts (2). — One of this dimension's main actionable groups (119 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
134 test methods: 97 unit, 0 integration, 0 BDD, 37 e2e. The JavaScript/TypeScript suite contributes 134 `it`/`test` case(s) across 15 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 6.4/10. — 134 test methods: 97 unit, 0 integration, 0 BDD, 37 e2e. The JavaScript/TypeScript suite contributes 134 `it`/`test` case(s) across 15 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
6 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 134 tests.
What to do
- Resolve the 6 Skipped test finding(s) in Test Quality — start with auth.e2e-spec.ts (3), role.e2e-spec.ts (2), user.e2e-spec.ts. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 Mock-dominated test finding(s) in Test Quality — start with logger.service.spec.ts. — One of this dimension's main actionable groups (1 recommendation-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in the repository root (81 tests)): measured (0 flaky).
D12 · Dependency Hygiene
36 outdated direct production npm dependency(ies) of 45 graded, 0 pinning defect(s), across 2 package.json (2 of them the product) and 2 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 3 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13). — One of this dimension's main actionable groups (13 recommendation-level).
- Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with package.json (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (3). — One of this dimension's main actionable groups (3 recommendation-level).
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 1032 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1032 package(s) this repository's committed lockfile installs for a consumer — its 45 production, optional and peer dependency(ies), across 2 product package.json manifest(s), and everything those install in turn. Its 37 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/core/services/user.service.ts (3×15=45); src/infrastructure/config/configuration.ts (2×15=30)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with user.service.ts, configuration.ts. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 12166 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 38 document(s) read across 2 unit(s).
D20 · ADR Quality
0 of 2 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D24 · Comment Value
46 of 419 judged comments only repeat the code they sit on (11.0 %). 4 comment(s) in another language or script were not judged.
What to do
- Resolve the 34 redundant comment finding(s) in Comment Value — start with register-user.command.spec.ts (3), REDACTED (3), user.service.ts (3). — One of this dimension's main actionable groups (34 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
51 % of calls cross a namespace and 34 % go through an interface, but 56 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Pass-through layer finding(s) in Navigability — start with admin-health.controller.ts. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
27 finding(s): 0 critical, 16 high, 11 medium, 0 low. 14 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `REDACTED` (line 77, line 92, line 130), `src/application/queries/admin/get-health.query.ts` (line 27) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 14 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (14 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
87 finding(s): 5 critical, 55 high, 19 medium, 8 low.
What to do
- Resolve the 53 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (53). — One of this dimension's main actionable groups (53 issue-level).
- Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
7 finding(s): 0 critical, 3 high, 3 medium, 1 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D32 · Data Compliance (PII/GDPR)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 2 file(s) — `REDACTED`, `src/application/queries/admin/get-health.query.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
What to do
- Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
50 of 50 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 50 of the 202 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 50 Orphaned file finding(s) in Knowledge Freshness — start with edit.tsx (2), show.tsx (2), REDACTED. — One of this dimension's main actionable groups (50 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 32 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / Secret Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
- Enforce HTTPS (serve through https.createServer / NestJS httpsOptions, or redirect plain HTTP with express-sslify behind your TLS terminator) so data in transit is always encrypted.
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — src/core/entities/user.entity.ts:311
What to do
- Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
C3 · Audit Trail
- An audit mechanism is present, but the trail is not yet complete — missing: an ORM write hook every change flows through (a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware or a query extension, or an event-store append), per-model coverage (@Audited, or a change-history plugin such as mongoose-history or sequelize-paper-trail applied to each model).
What to do
- Back the audit convention with a structural mechanism: an ORM write hook (a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware) writing every sensitive change to an audit-log table, and apply it to each model that needs a who-changed-what trail.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM6 · Domain ↔ infrastructure boundary
- `DomainException` (domain layer) imports `@nestjs/common` — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — src/core/exceptions/domain-exceptions.ts:1
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
- `onError` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — REDACTED:274
- The guard above `return false;` also returns `false`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — REDACTED:363
- `checkConfiguration` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/core/services/health.service.ts:213
- `checkMemoryUsage` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/core/services/health.service.ts:228
- The guard above `return null;` also returns `null`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — src/core/services/user.service.ts:75
- The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — src/infrastructure/logger/logger.service.ts:68
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×6) — test/auth.e2e-spec.ts:59, test/auth.e2e-spec.ts:93, test/auth.e2e-spec.ts:121, …
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- 2 ADR-shaped document(s) detected by content — `docs/01-overview/ARCHITECTURE_OVERVIEW.md`, `docs/02-architecture/architecture-decisions.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
- Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- `prettier --write "src/**/*.ts" "test/**/*.ts"` (the `format` script this step runs) invokes prettier in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:33
What to do
- Add `--check` to the prettier step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
P2 · Observability
- `src/presentation/modules/auth/providers/email.provider.ts` reports through `console.*` at line 50 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/presentation/modules/auth/providers/email.provider.ts:50
- `src/presentation/modules/auth/providers/email.provider.ts` reports through `console.*` at line 102 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/presentation/modules/auth/providers/email.provider.ts:102
- `src/presentation/modules/auth/providers/email.provider.ts` reports through `console.*` at line 149 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/presentation/modules/auth/providers/email.provider.ts:149
- `src/presentation/modules/auth/providers/email.provider.ts` reports through `console.*` at line 200 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/presentation/modules/auth/providers/email.provider.ts:200
- `src/infrastructure/storage/providers/minio.provider.ts` reports through `console.*` at line 35 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/infrastructure/storage/providers/minio.provider.ts:35
- `src/infrastructure/logger/logger.service.ts` reports through `console.*` at line 67 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/infrastructure/logger/logger.service.ts:67
- `src/infrastructure/logger/logger.service.ts` reports through `console.*` at line 69 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/infrastructure/logger/logger.service.ts:69
- `src/infrastructure/logger/logger.service.ts` reports through `console.*` at line 73 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/infrastructure/logger/logger.service.ts:73
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
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:46
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 7 duplicated blocks under src/presentation/modules/ have copies in at least two of the sibling directories admin, auth, storage, user — 3 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/presentation/modules/admin/admin.module.ts:111
- src/core/value-objects/collections/permissions.collection.ts:9 · src/core/value-objects/collections/roles.collection.ts:10 — the two spans are one implementation copied and then locally edited — 722 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/core/value-objects/collections/permissions.collection.ts:9
- admin/src/pages/auth/verify-email.tsx:7 · admin/src/pages/auth/verify-otp.tsx:7 — the two spans are one implementation copied and then locally edited — 408 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — admin/src/pages/auth/verify-email.tsx:7
- admin/src/pages/roles/create.tsx:33 · admin/src/pages/roles/edit.tsx:59 — the two spans are one implementation copied and then locally edited — 292 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — admin/src/pages/roles/create.tsx:33
- src/infrastructure/storage/providers/minio.provider.ts:13 · src/infrastructure/storage/providers/s3.provider.ts:14 — the two spans are one implementation copied and then locally edited — 235 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/infrastructure/storage/providers/minio.provider.ts:13
- src/core/entities/role.entity.ts:66 · src/core/entities/user.entity.ts:122 — the two spans are one implementation copied and then locally edited — 200 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/core/entities/role.entity.ts:66
- src/application/dtos/responses/auth/auth.response.ts:12 · src/application/dtos/responses/user/user.response.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/application/dtos/responses/auth/auth.response.ts:12
- src/application/commands/auth/refresh-token.command.ts:47 · src/application/commands/auth/verify-email.command.ts:50 — the two spans are one implementation copied and then locally edited — 208 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/application/commands/auth/refresh-token.command.ts:47
- src/application/dtos/requests/role/create-role.request.ts:5 · src/application/dtos/requests/role/update-role.request.ts:5 — the two spans are one implementation copied and then locally edited — 135 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/application/dtos/requests/role/create-role.request.ts:5
- src/application/commands/role/assign-permission.command.ts:9 · src/application/commands/role/remove-permission.command.ts:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/application/commands/role/assign-permission.command.ts:9
- src/core/entities/email-verification.entity.ts:8 · src/core/entities/password-reset.entity.ts:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/core/entities/email-verification.entity.ts:8
- src/infrastructure/services/throttler.service.ts:13 · src/infrastructure/services/throttler.service.ts:66 — the two spans are one implementation copied and then locally edited — 126 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/infrastructure/services/throttler.service.ts:13
- src/presentation/modules/storage/storage.controller.ts:82 · src/presentation/modules/storage/storage.controller.ts:104 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/presentation/modules/storage/storage.controller.ts:82
- src/application/dtos/requests/user/admin-change-password.request.ts:5 · src/application/dtos/requests/user/change-password.request.ts:14 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/application/dtos/requests/user/admin-change-password.request.ts:5
- src/presentation/modules/admin/admin-health.controller.ts:41 · src/presentation/modules/admin/admin-health.controller.ts:65 · src/presentation/modules/admin/admin-health.controller.ts:95 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/presentation/modules/admin/admin-health.controller.ts:41
- src/presentation/modules/admin/admin-role.controller.ts:107 · src/presentation/modules/admin/admin-role.controller.ts:127 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/presentation/modules/admin/admin-role.controller.ts:107
- admin/src/pages/health/index.tsx:160 · admin/src/pages/health/index.tsx:180 · admin/src/pages/health/index.tsx:200 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — admin/src/pages/health/index.tsx:160
- admin/src/pages/users/create.tsx:12 · admin/src/pages/users/edit.tsx:52 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — admin/src/pages/users/create.tsx:12
- admin/src/providers/data-provider.ts:198 · admin/src/providers/data-provider.ts:230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — admin/src/providers/data-provider.ts:198
- src/application/commands/auth/verify-email.command.ts:69 · src/application/commands/auth/verify-otp.command.ts:51 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/application/commands/auth/verify-email.command.ts:69
- src/application/dtos/responses/health/health.response.ts:23 · src/application/dtos/responses/health/health.response.ts:177 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/application/dtos/responses/health/health.response.ts:23
- src/application/commands/auth/request-password-reset.command.ts:8 · src/application/commands/auth/reset-password.command.ts:8 · src/application/commands/auth/send-verification-email.command.ts:7 — the 3 copies are spread across 3 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — src/application/commands/auth/request-password-reset.command.ts:8
- src/application/dtos/requests/auth/password-reset.request.ts:26 · src/application/dtos/requests/user/admin-change-password.request.ts:7 · src/application/dtos/requests/user/change-password.request.ts:16 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/application/dtos/requests/auth/password-reset.request.ts:26
- REDACTED:4 · admin/src/providers/data-provider.ts:8 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:4
- src/core/services/role.service.ts:27 · src/core/services/role.service.ts:53 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/core/services/role.service.ts:27
- src/presentation/modules/admin/admin.module.ts:111 · src/presentation/modules/auth/auth.module.ts:66 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/presentation/modules/admin/admin.module.ts:111
- src/presentation/modules/auth/providers/email.provider.ts:94 · src/presentation/modules/auth/providers/email.provider.ts:141 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/presentation/modules/auth/providers/email.provider.ts:94
- admin/src/pages/health/index.tsx:222 · admin/src/pages/health/index.tsx:238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — admin/src/pages/health/index.tsx:222
- admin/src/pages/roles/show.tsx:28 · admin/src/pages/users/show.tsx:81 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — admin/src/pages/roles/show.tsx:28
- admin/src/pages/users/create.tsx:51 · admin/src/pages/users/edit.tsx:72 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — admin/src/pages/users/create.tsx:51
- admin/src/providers/data-provider.ts:102 · admin/src/providers/data-provider.ts:117 · admin/src/providers/data-provider.ts:147 · admin/src/providers/data-provider.ts:190 · +2 more site(s) not listed — all 6 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — admin/src/providers/data-provider.ts:102
- admin/src/providers/data-provider.ts:132 · admin/src/providers/data-provider.ts:238 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — admin/src/providers/data-provider.ts:132
- src/core/specifications/specification.base.ts:43 · src/core/specifications/specification.base.ts:59 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/core/specifications/specification.base.ts:43
- src/application/commands/auth/check-email-verification-status.command.ts:6 · src/application/commands/auth/disable-2fa.command.ts:8 · src/application/commands/auth/generate-otp.command.ts:6 · src/application/commands/auth/logout.command.ts:6 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/application/commands/auth/check-email-verification-status.command.ts:6
- REDACTED:189 · REDACTED:274 · src/core/services/user.service.ts:229 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — REDACTED:189
- REDACTED:274 · src/core/services/user.service.ts:229 · src/core/services/user.service.ts:240 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — REDACTED:274
- src/core/services/role.service.ts:153 · src/core/services/user.service.ts:194 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/core/services/role.service.ts:153
- src/core/services/user.service.ts:229 · src/core/services/user.service.ts:240 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/core/services/user.service.ts:229
- admin/src/pages/roles/show.tsx:48 · admin/src/pages/users/show.tsx:119 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — admin/src/pages/roles/show.tsx:48
- REDACTED:96 · src/application/commands/auth/refresh-token.command.ts:50 · src/application/commands/auth/verify-email.command.ts:53 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — REDACTED:96
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- src/application/commands/admin/change-password.command.ts:2 imports src/infrastructure/logger/logger.service.ts against the layered-src rules. — src/application/commands/admin/change-password.command.ts:2
- src/application/commands/admin/update-user.command.ts:2 imports src/infrastructure/logger/logger.service.ts against the layered-src rules. — src/application/commands/admin/update-user.command.ts:2
- src/application/commands/auth/login.command.spec.ts:11 imports src/infrastructure/logger/logger.service.ts against the layered-src rules. — src/application/commands/auth/login.command.spec.ts:11
- src/application/commands/auth/login.command.spec.ts:14 imports src/presentation/modules/auth/providers/token.provider.ts against the layered-src rules. — src/application/commands/auth/login.command.spec.ts:14
- REDACTED:12 imports src/infrastructure/logger/logger.service.ts against the layered-src rules. — REDACTED:12
- REDACTED:15 imports src/presentation/modules/auth/providers/token.provider.ts against the layered-src rules. — REDACTED:15
- src/application/commands/auth/refresh-token.command.spec.ts:13 imports src/infrastructure/logger/logger.service.ts against the layered-src rules. — src/application/commands/auth/refresh-token.command.spec.ts:13
- src/application/commands/auth/request-password-reset.command.ts:6 imports src/presentation/modules/auth/providers/email.provider.ts against the layered-src rules. — src/application/commands/auth/request-password-reset.command.ts:6
- src/application/commands/auth/send-verification-email.command.ts:5 imports src/presentation/modules/auth/providers/email.provider.ts against the layered-src rules. — src/application/commands/auth/send-verification-email.command.ts:5
- src/application/queries/admin/get-health.query.ts:2 imports src/infrastructure/logger/logger.service.ts against the layered-src rules. — src/application/queries/admin/get-health.query.ts:2
- src/application/queries/admin/get-user.query.ts:4 imports src/infrastructure/logger/logger.service.ts against the layered-src rules. — src/application/queries/admin/get-user.query.ts:4
What to do
- Fix the listed violations: respect the layer/slice order — import only through a slice's public index and never upward into a higher layer (11 rows).
R2 · Cyclomatic Complexity
- HealthMonitor has cyclomatic complexity 21 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — admin/src/pages/health/index.tsx:27
- UserShow has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — admin/src/pages/users/show.tsx:16
- getList has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — admin/src/providers/data-provider.ts:33
- updateUserDetails has cyclomatic complexity 15 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/core/services/user.service.ts:85
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/infrastructure/config/configuration.ts:1
- (anonymous) has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:3
- updateRole has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/core/services/role.service.ts:89
- login has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:66
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- REDACTED has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×22) — admin/src/pages/health/index.tsx:1, REDACTED:1, admin/src/providers/data-provider.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 48 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 5 application, 4 tooling and 22 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (5 application, 4 tooling, 22 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 (×7) — src/application/commands/auth/disable-2fa.command.ts, src/application/commands/auth/verify-2fa.command.ts, src/application/commands/auth/generate-otp.command.ts, …
- Nothing ultimately consumes this binding: its only referrer is the re-export in src/application/dtos/responses/storage/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/application/dtos/responses/storage/index.ts in the same commit, or the barrel will import a name that no longer exists. — src/application/dtos/responses/storage/file.response.ts:66
- Nothing imports this binding — it is safe to review for removal. (×16) — src/core/exceptions/domain-exceptions.ts:30, src/core/exceptions/domain-exceptions.ts:121, src/core/exceptions/domain-exceptions.ts:134, …
- Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used. — src/core/entities/user.entity.ts:308
- Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. (×2) — src/presentation/modules/admin/admin.controller.ts:17, src/presentation/modules/auth/strategies/jwt.strategy.ts:13
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. (×2) — src/presentation/filters/all-exceptions.filter.ts:2, src/presentation/interceptors/logging.interceptor.ts:2
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- src/core/entities/role.entity.ts → src/core/specifications/role.specifications.ts → src/core/entities/role.entity.ts — src/core/entities/role.entity.ts:9
- src/core/entities/user.entity.ts → src/core/specifications/user.specifications.ts → src/core/entities/user.entity.ts — src/core/entities/user.entity.ts:13
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
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
X2 · Cancellation propagation
- Only 0/16 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `login` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — REDACTED:66
- `logout` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — REDACTED:141
- `check` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`. — REDACTED:161
- `register` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — REDACTED:208
- `forgotPassword` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — REDACTED:232
- `updatePassword` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — REDACTED:252
- `getList` awaits `axiosInstance.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axiosInstance.get(url, { signal })`. — admin/src/providers/data-provider.ts:33
- `getOne` awaits `axiosInstance.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axiosInstance.get(url, { signal })`. — admin/src/providers/data-provider.ts:110
- `create` awaits `axiosInstance.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axiosInstance.post(url, { signal })`. — admin/src/providers/data-provider.ts:125
- `update` awaits `axiosInstance.put(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axiosInstance.put(url, { signal })`. — admin/src/providers/data-provider.ts:140
- `deleteOne` awaits `axiosInstance.delete(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axiosInstance.delete(url, { signal })`. — admin/src/providers/data-provider.ts:155
- `getMany` awaits `axiosInstance.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axiosInstance.get(url, { signal })`. — admin/src/providers/data-provider.ts:198
- `createMany` awaits `axiosInstance.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axiosInstance.post(url, { signal })`. — admin/src/providers/data-provider.ts:214
- `deleteMany` awaits `axiosInstance.delete(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axiosInstance.delete(url, { signal })`. — admin/src/providers/data-provider.ts:230
- `updateMany` awaits `axiosInstance.put(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axiosInstance.put(url, { signal })`. — admin/src/providers/data-provider.ts:246
- `updateRolePermissions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — admin/src/pages/roles/edit.tsx:74
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `debug` at line 106 is called with an argument built by `roles.map((r) => r.name)` (line 109), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — REDACTED:106
What to do
- Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 2/3 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.
- ~6.0 `!` null assertions per 1k TypeScript source lines — 85 assertion(s) across the 14207 source line(s) of the 198 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/application/dtos/responses/auth/auth.response.ts (20), src/application/dtos/responses/user/user.response.ts (11), src/application/dtos/responses/health/health.response.ts (10). 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 | 65% | Strong | Solid. |
| Architecture | 68% | Adequate — gated by D26, R11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 72% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 45% | Adequate — gated by D13, R8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 51% | Adequate — gated by D29, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 67% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- 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.
Not included — 49 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:39 -------------------- 37 | 38 | # Install production dependencies only 39 | >>> RUN npm ci --only=production 40 | 41 | # Copy Prisma schema -------------------- ERROR: failed to solve: process "/bin/sh -c npm ci --only=production" did not complete successfully: exit code: 127; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D16 Bus Factor — bus factor 1 — one contributor carries this repository
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (2223 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. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — None of 1 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- 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, .tsx) 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.
- DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (44 CQRS handler(s))
- ED5 Idempotency — 30 mutating command handler(s)/consumer(s) detected and 30 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
- 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:12 (NestFactory.create))
- P9 Domain vs controller coverage — coverage data present for 144 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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.
- S1 Web-Security Posture — Not assessed: 198 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.
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 87 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) src/core/entities/role.entity.ts:9
- Import cycle (2 files) src/core/entities/user.entity.ts:13
- Domain depends on infrastructure: DomainException src/core/exceptions/domain-exceptions.ts:1
- Unlisted import 'express' src/presentation/filters/all-exceptions.filter.ts:2
- Unlisted import 'rxjs' src/presentation/interceptors/logging.interceptor.ts:2
Serious — 297 finding(s)
- Low coverage: src/application/commands/admin/change-password.command.ts src/application/commands/admin/change-password.command.ts:1
- Low coverage: src/application/commands/admin/update-user.command.ts src/application/commands/admin/update-user.command.ts:1
- Low coverage: src/application/commands/auth/check-email-verification-status.command.ts src/application/commands/auth/check-email-verification-status.command.ts:1
- Low coverage: src/application/commands/auth/disable-2fa.command.ts src/application/commands/auth/disable-2fa.command.ts:1
- Low coverage: src/application/commands/auth/generate-otp.command.ts src/application/commands/auth/generate-otp.command.ts:1
- Low coverage: REDACTED REDACTED:1
- Low coverage: src/application/commands/auth/logout.command.ts src/application/commands/auth/logout.command.ts:1
- Low coverage: src/application/commands/auth/register-user.command.ts src/application/commands/auth/register-user.command.ts:1
- Low coverage: src/application/commands/auth/request-password-reset.command.ts src/application/commands/auth/request-password-reset.command.ts:1
- Low coverage: src/application/commands/auth/reset-password.command.ts src/application/commands/auth/reset-password.command.ts:1
- Low coverage: src/application/commands/auth/send-verification-email.command.ts src/application/commands/auth/send-verification-email.command.ts:1
- Low coverage: src/application/commands/auth/setup-2fa.command.ts src/application/commands/auth/setup-2fa.command.ts:1
- Low coverage: src/application/commands/auth/verify-2fa.command.ts src/application/commands/auth/verify-2fa.command.ts:1
- Low coverage: src/application/commands/auth/verify-email.command.ts src/application/commands/auth/verify-email.command.ts:1
- Low coverage: src/application/commands/auth/verify-otp.command.ts src/application/commands/auth/verify-otp.command.ts:1
- Low coverage: src/application/commands/role/assign-permission.command.ts src/application/commands/role/assign-permission.command.ts:1
- Low coverage: src/application/commands/role/create-role.command.ts src/application/commands/role/create-role.command.ts:1
- Low coverage: src/application/commands/role/delete-role.command.ts src/application/commands/role/delete-role.command.ts:1
- Low coverage: src/application/commands/role/remove-permission.command.ts src/application/commands/role/remove-permission.command.ts:1
- Low coverage: src/application/commands/role/update-role.command.ts src/application/commands/role/update-role.command.ts:1
- Low coverage: src/application/commands/storage/delete-file.command.ts src/application/commands/storage/delete-file.command.ts:1
- Low coverage: src/application/commands/storage/update-file-access.command.ts src/application/commands/storage/update-file-access.command.ts:1
- Low coverage: src/application/commands/storage/upload-file.command.ts src/application/commands/storage/upload-file.command.ts:1
- Low coverage: src/application/commands/user/activate-user.command.ts src/application/commands/user/activate-user.command.ts:1
- Low coverage: src/application/commands/user/assign-role.command.ts src/application/commands/user/assign-role.command.ts:1
- No test reaches this file admin/src/pages/health/index.tsx:1
- No test reaches this file REDACTED:1
- No test reaches this file admin/src/providers/data-provider.ts:1
- No test reaches this file admin/src/App.tsx:1
- No test reaches this file admin/src/pages/roles/edit.tsx:1
- No test reaches this file admin/src/pages/users/show.tsx:1
- No test reaches this file admin/src/pages/users/list.tsx:1
- No test reaches this file admin/src/pages/auth/verify-email.tsx:1
- No test reaches this file admin/src/pages/users/edit.tsx:1
- No test reaches this file src/main.ts:1
- No test reaches this file admin/src/pages/roles/create.tsx:1
- No test reaches this file admin/src/pages/roles/show.tsx:1
- No test reaches this file admin/src/pages/auth/verify-otp.tsx:1
- No test reaches this file admin/src/pages/users/create.tsx:1
- No test reaches this file admin/src/pages/roles/list.tsx:1
- No test reaches this file src/application/commands/auth/disable-2fa.command.ts:1
- No test reaches this file src/application/commands/auth/verify-2fa.command.ts:1
- No test reaches this file src/application/commands/auth/generate-otp.command.ts:1
- No test reaches this file src/application/commands/auth/setup-2fa.command.ts:1
- No test reaches this file src/core/value-objects/file-id.vo.ts:1
- No test reaches this file admin/src/main.tsx:1
- No test reaches this file src/presentation/modules/auth/providers/otp.provider.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Async function without AbortSignal: login REDACTED:66
- Async function without AbortSignal: logout REDACTED:141
- Async function without AbortSignal: check REDACTED:161
- Async function without AbortSignal: register REDACTED:208
- Async function without AbortSignal: forgotPassword REDACTED:232
- Async function without AbortSignal: updatePassword REDACTED:252
- Async function without AbortSignal: getList admin/src/providers/data-provider.ts:33
- Async function without AbortSignal: getOne admin/src/providers/data-provider.ts:110
- Async function without AbortSignal: create admin/src/providers/data-provider.ts:125
- Async function without AbortSignal: update admin/src/providers/data-provider.ts:140
- Async function without AbortSignal: deleteOne admin/src/providers/data-provider.ts:155
- Async function without AbortSignal: getMany admin/src/providers/data-provider.ts:198
- Async function without AbortSignal: createMany admin/src/providers/data-provider.ts:214
- Async function without AbortSignal: deleteMany admin/src/providers/data-provider.ts:230
- Async function without AbortSignal: updateMany admin/src/providers/data-provider.ts:246
- Async function without AbortSignal: updateRolePermissions admin/src/pages/roles/edit.tsx:74
- Boundary violation [layered:upward-import] src/application/commands/admin/change-password.command.ts:2
- Boundary violation [layered:upward-import] src/application/commands/admin/update-user.command.ts:2
- Boundary violation [layered:upward-import] src/application/commands/auth/login.command.spec.ts:11
- Boundary violation [layered:upward-import] src/application/commands/auth/login.command.spec.ts:14
- Boundary violation [layered:upward-import] REDACTED:12
- Boundary violation [layered:upward-import] REDACTED:15
- Boundary violation [layered:upward-import] src/application/commands/auth/refresh-token.command.spec.ts:13
- Boundary violation [layered:upward-import] src/application/commands/auth/request-password-reset.command.ts:6
- Boundary violation [layered:upward-import] src/application/commands/auth/send-verification-email.command.ts:5
- Boundary violation [layered:upward-import] src/application/queries/admin/get-health.query.ts:2
- Boundary violation [layered:upward-import] src/application/queries/admin/get-user.query.ts:4
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Skipped test: should get current user info with valid token test/auth.e2e-spec.ts:59
- Skipped test: should register a new user with valid input test/auth.e2e-spec.ts:93
- Skipped test: should return tokens for valid credentials test/auth.e2e-spec.ts:121
- Skipped test: should get role list when authenticated with role:read permission test/role.e2e-spec.ts:60
- Skipped test: should get role by ID when authenticated with permissions test/role.e2e-spec.ts:80
- Skipped test: should get user list when authenticated as admin test/user.e2e-spec.ts:61
- FunctionTooLong: App.App admin/src/App.tsx:30
- FunctionTooLong: edit.RoleEdit admin/src/pages/roles/edit.tsx:11
- FunctionTooLong: show.UserShow admin/src/pages/users/show.tsx:16
- FunctionTooLong: list.UserList admin/src/pages/users/list.tsx:7
- FunctionTooLong: verify-email.VerifyEmail admin/src/pages/auth/verify-email.tsx:9
- FunctionTooLong: edit.UserEdit admin/src/pages/users/edit.tsx:6
- Duplicated block (11 lines × 2 locations) admin/src/pages/health/index.tsx:222
- Duplicated block (11 lines × 2 locations) admin/src/pages/roles/show.tsx:28
- Duplicated block (11 lines × 2 locations) admin/src/pages/users/create.tsx:51
- Duplicated block (11 lines × 2 locations) admin/src/providers/data-provider.ts:132
- Duplicated block (11 lines × 2 locations) src/core/specifications/specification.base.ts:43
- Duplicated block (15 lines × 2 locations) admin/src/pages/users/create.tsx:12
- Duplicated block (15 lines × 2 locations) admin/src/providers/data-provider.ts:198
- Duplicated block (15 lines × 2 locations) src/application/commands/auth/verify-email.command.ts:69
- Duplicated block (15 lines × 2 locations) src/application/dtos/responses/health/health.response.ts:23
- Duplicated block (13 lines × 2 locations) REDACTED:4
- Duplicated block (13 lines × 2 locations) src/core/services/role.service.ts:27
- Duplicated block (13 lines × 2 locations) src/presentation/modules/admin/admin.module.ts:111
- Duplicated block (13 lines × 2 locations) src/presentation/modules/auth/providers/email.provider.ts:94
- Deprecated: multer package.json:69
- Deprecated: eslint package.json:97
- Deprecated: supertest package.json:106
- REDACTED
- REDACTED
- REDACTED
- Hotspot: src/core/services/user.service.ts src/core/services/user.service.ts:85
- Hotspot: src/infrastructure/config/configuration.ts src/infrastructure/config/configuration.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Guard cannot change the result — returns what the code already falls through to REDACTED:363
- Guard cannot change the result — returns what the code already falls through to src/core/services/user.service.ts:75
- Fake-async — async method never awaits src/core/services/health.service.ts:213
- Fake-async — async method never awaits src/core/services/health.service.ts:228
- Duplicated block with local edits (26 matched lines × 2 locations) src/application/commands/auth/refresh-token.command.ts:47
- Duplicated block with local edits (26 matched lines × 2 locations) src/application/dtos/requests/role/create-role.request.ts:5
- Duplicated block (16 lines × 2 locations) src/application/dtos/requests/user/admin-change-password.request.ts:5
- Duplicated block (16 lines × 2 locations) src/presentation/modules/admin/admin-role.controller.ts:107
- Duplicated block (14 lines × 3 locations) src/application/commands/auth/request-password-reset.command.ts:8
- Duplicated block (14 lines × 3 locations) src/application/dtos/requests/auth/password-reset.request.ts:26
- Duplicated block (10 lines × 3 locations) REDACTED:189
- Duplicated block (10 lines × 3 locations) REDACTED:274
- Duplicated block (10 lines × 2 locations) src/core/services/role.service.ts:153
- Duplicated block (10 lines × 2 locations) src/core/services/user.service.ts:229
- Dead file (~27 LoC) src/application/commands/auth/disable-2fa.command.ts
- Dead file (~27 LoC) src/application/commands/auth/verify-2fa.command.ts
- index.HealthMonitor (cyclomatic 37) admin/src/pages/health/index.tsx:27
- edit.RoleEdit (cyclomatic 24) admin/src/pages/roles/edit.tsx:11
- list.UserList (cyclomatic 18) admin/src/pages/users/list.tsx:7
- show.UserShow (cyclomatic 16) admin/src/pages/users/show.tsx:16
- bus factor 1 — one contributor carries this repository
- UserService.updateUserDetails (cognitive 26) src/core/services/user.service.ts:85
- index.HealthMonitor (cognitive 24) admin/src/pages/health/index.tsx:27
- edit.RoleEdit (cognitive 20) admin/src/pages/roles/edit.tsx:11
- RoleService.updateRole (cognitive 16) src/core/services/role.service.ts:89
- REDACTED
- REDACTED
- REDACTED
- Hollow method — returns a constant without doing the work REDACTED:274
- Both branches are identical — the condition decides nothing src/infrastructure/logger/logger.service.ts:68
- CI formatting step cannot fail REDACTED:33
- Coverage collected but not gated
- Duplication concentrated across 4 sibling directories (7 clone groups) src/presentation/modules/admin/admin.module.ts:111
- Duplicated block with local edits (97 matched lines × 2 locations) src/core/value-objects/collections/permissions.collection.ts:9
- Duplicated block with local edits (63 matched lines × 2 locations) admin/src/pages/auth/verify-email.tsx:7
- Duplicated block with local edits (58 matched lines × 2 locations) admin/src/pages/roles/create.tsx:33
- Duplicated block with local edits (37 matched lines × 2 locations) src/infrastructure/storage/providers/minio.provider.ts:13
- Duplicated block with local edits (35 matched lines × 2 locations) src/core/entities/role.entity.ts:66
- Duplicated block (31 lines × 2 locations) src/application/dtos/responses/auth/auth.response.ts:12
- Duplicated block (25 lines × 2 locations) src/application/commands/role/assign-permission.command.ts:9
- Duplicated block (23 lines × 2 locations) src/core/entities/email-verification.entity.ts:8
- Duplicated block with local edits (21 matched lines × 2 locations) src/infrastructure/services/throttler.service.ts:13
- Duplicated block (19 lines × 2 locations) src/presentation/modules/storage/storage.controller.ts:82
- Duplicated block (16 lines × 3 locations) src/presentation/modules/admin/admin-health.controller.ts:41
- Duplicated block (15 lines × 3 locations) admin/src/pages/health/index.tsx:160
- Duplicated block (11 lines × 6 locations) admin/src/providers/data-provider.ts:102
- Duplicated block (10 lines × 5 locations) src/application/commands/auth/check-email-verification-status.command.ts:6
- Duplicated block (9 lines × 2 locations) admin/src/pages/roles/show.tsx:48
- Duplicated block (9 lines × 3 locations) REDACTED:96
- Complex function HealthMonitor (cyclomatic 21, cognitive 19) admin/src/pages/health/index.tsx:27
- Complex function UserShow (cyclomatic 16, cognitive 14) admin/src/pages/users/show.tsx:16
- Complex function getList (cyclomatic 16, cognitive 14) admin/src/providers/data-provider.ts:33
- Complex function updateUserDetails (cyclomatic 15, cognitive 26) src/core/services/user.service.ts:85
- Complex function (anonymous) (cyclomatic 15, cognitive 14) src/infrastructure/config/configuration.ts:1
- Complex function (anonymous) (cyclomatic 13, cognitive 12) REDACTED:3
- Complex function updateRole (cyclomatic 11, cognitive 16) src/core/services/role.service.ts:89
- Complex function login (cyclomatic 11, cognitive 10) REDACTED:66
- REDACTED: 402 lines of code REDACTED:1
- Dependency Freshness
- Dead file (~24 LoC) src/application/commands/auth/generate-otp.command.ts
- Dead file (~22 LoC) src/application/commands/auth/setup-2fa.command.ts
- Dead file (~15 LoC) src/core/value-objects/file-id.vo.ts
- Dead file (~8 LoC) src/infrastructure/logger/logger.interface.ts
- Dead file (~0 LoC) src/presentation/modules/auth/providers/otp.provider.ts
- Unused dependency '@aws-sdk/lib-storage'
- Unused dependency 'dotenv'
- Unused dependency 'express-session'
Minor — 167 finding(s)
- Orphaned file REDACTED:1
- Orphaned file admin/src/pages/health/index.tsx:1
- Orphaned file src/core/services/health.service.ts:1
- Orphaned file src/core/services/user.service.ts:1
- Orphaned file src/presentation/modules/auth/providers/email.provider.ts:1
- Orphaned file src/core/entities/user.entity.ts:1
- Orphaned file src/presentation/modules/auth/auth.controller.ts:1
- Orphaned file src/presentation/modules/admin/admin-user.controller.ts:1
- Orphaned file src/core/value-objects/collections/roles.collection.ts:1
- Orphaned file admin/src/pages/roles/edit.tsx:1
- Orphaned file admin/src/App.tsx:1
- Orphaned file REDACTED:1
- Orphaned file src/presentation/modules/admin/admin-role.controller.ts:1
- Orphaned file admin/src/providers/data-provider.ts:1
- Orphaned file src/presentation/modules/admin/admin.module.ts:1
- Orphaned file src/application/dtos/responses/health/health.response.ts:1
- Orphaned file src/core/value-objects/collections/permissions.collection.ts:1
- Orphaned file src/core/services/role.service.ts:1
- Orphaned file src/core/exceptions/domain-exceptions.ts:1
- Orphaned file admin/src/pages/users/show.tsx:1
- Orphaned file src/core/entities/role.entity.ts:1
- Orphaned file src/presentation/modules/storage/storage.controller.ts:1
- Orphaned file admin/src/pages/users/edit.tsx:1
- Orphaned file admin/src/pages/auth/verify-email.tsx:1
- Orphaned file admin/src/pages/users/list.tsx:1
- redundant comment REDACTED:163
- redundant comment REDACTED:216
- redundant comment src/application/commands/auth/generate-otp.command.ts:19
- redundant comment src/application/commands/auth/login.command.spec.ts:340
- redundant comment REDACTED:58
- redundant comment REDACTED:80
- redundant comment src/application/commands/auth/logout.command.ts:19
- redundant comment src/application/commands/auth/refresh-token.command.spec.ts:312
- redundant comment src/application/commands/auth/refresh-token.command.ts:34
- redundant comment src/application/commands/auth/register-user.command.spec.ts:10
- redundant comment src/application/commands/auth/register-user.command.spec.ts:15
- redundant comment src/application/commands/auth/register-user.command.spec.ts:45
- redundant comment src/application/commands/auth/request-password-reset.command.ts:29
- redundant comment src/application/commands/auth/reset-password.command.ts:26
- redundant comment src/application/commands/auth/send-verification-email.command.ts:24
- redundant comment src/application/commands/auth/send-verification-email.command.ts:27
- redundant comment src/application/commands/auth/verify-email.command.ts:35
- redundant comment src/application/commands/role/assign-permission.command.ts:29
- redundant comment src/application/commands/role/remove-permission.command.ts:29
- redundant comment src/core/exceptions/domain-exceptions.ts:19
- redundant comment src/core/services/auth.service.spec.ts:47
- redundant comment REDACTED:201
- redundant comment REDACTED:204
- redundant comment REDACTED:391
- redundant comment src/core/services/role.service.ts:165
- Deprecated: inflight REDACTED:6547
- Deprecated: rimraf REDACTED:9578
- Deprecated: glob REDACTED:9603
- Deprecated: glob REDACTED:2760
- Deprecated: are-we-there-yet REDACTED:5392
- Deprecated: gauge REDACTED:8115
- Deprecated: inflight REDACTED:8609
- Deprecated: glob REDACTED:9184
- Deprecated: glob REDACTED:9547
- Deprecated: npmlog REDACTED:11022
- Deprecated: rimraf REDACTED:12315
- Deprecated: glob REDACTED:12341
- Deprecated: glob REDACTED:13505
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Console output used as the logging channel src/presentation/modules/auth/providers/email.provider.ts:50
- Console output used as the logging channel src/presentation/modules/auth/providers/email.provider.ts:102
- Console output used as the logging channel src/presentation/modules/auth/providers/email.provider.ts:149
- Console output used as the logging channel src/presentation/modules/auth/providers/email.provider.ts:200
- Console output used as the logging channel src/infrastructure/storage/providers/minio.provider.ts:35
- Console output used as the logging channel src/infrastructure/logger/logger.service.ts:67
- Console output used as the logging channel src/infrastructure/logger/logger.service.ts:69
- Console output used as the logging channel src/infrastructure/logger/logger.service.ts:73
- Duplicated predicate src/core/entities/permission.entity.ts:114
- Duplicated predicate src/presentation/filters/all-exceptions.filter.ts:50
- Duplicated predicate src/infrastructure/storage/providers/minio.provider.ts:100
- Duplicated predicate admin/src/pages/roles/create.tsx:105
- Duplicated predicate REDACTED:99
- Duplicated predicate REDACTED:10
- Duplicated predicate src/application/commands/storage/delete-file.command.ts:27
- Disabled test test/auth.e2e-spec.ts:59
- Disabled test test/auth.e2e-spec.ts:93
- Disabled test test/auth.e2e-spec.ts:121
- Disabled test test/role.e2e-spec.ts:60
- Disabled test test/role.e2e-spec.ts:80
- Disabled test test/user.e2e-spec.ts:61
- Outdated (npm): @nestjs/config package.json:51
- Outdated (npm): nodemailer package.json:71
- Outdated (npm): uuid package.json:78
- No named authorization policies src/core/entities/user.entity.ts:311
- Partial audit-trail evidence
- Partial data-retention evidence
- Mock-dominated test: should respect environment-based log levels src/infrastructure/logger/logger.service.spec.ts:107
- Projects may be oversized for their cohesion
- High interface indirection
- Scattered collaborators
- Pass-through layer src/presentation/modules/admin/admin-health.controller.ts:23
- REDACTED
- Dormant codebase
- REDACTED
- ADRs not easily discoverable
- No dependency-update automation package.json:46
- No changelog
- Unused export 'FileResponseDto' src/application/dtos/responses/storage/file.response.ts:66
- Unused export 'InvalidInputException' src/core/exceptions/domain-exceptions.ts:30
- Unused export 'RoleHasAssignedUsersException' src/core/exceptions/domain-exceptions.ts:121
- Unused export 'InvalidCredentialsException' src/core/exceptions/domain-exceptions.ts:134
- Unused export 'AccountLockedException' src/core/exceptions/domain-exceptions.ts:140
- Unused export 'TwoFactorRequiredException' src/core/exceptions/domain-exceptions.ts:146
- Unused export 'FileNotOwnedByUserException' src/core/exceptions/domain-exceptions.ts:153
- Unused export 'FileAccessDeniedException' src/core/exceptions/domain-exceptions.ts:159
- Unused export 'InvalidFileOperationException' src/core/exceptions/domain-exceptions.ts:165
- Unused export 'BusinessRuleValidationException' src/core/exceptions/domain-exceptions.ts:172
- Unused export 'DefaultRoleSpecification' src/core/specifications/role.specifications.ts:9
- Unused export 'RoleHasPermissionSpecification' src/core/specifications/role.specifications.ts:27
- Unused export 'RoleHasPermissionByNameSpecification' src/core/specifications/role.specifications.ts:40
- Unused export 'HasMinimumPermissionsSpecification' src/core/specifications/role.specifications.ts:97
- Unused export 'BasicUserRoleSpecification' src/core/specifications/role.specifications.ts:110
- Unused export 'EligibleForAdminRoleSpecification' src/core/specifications/user.specifications.ts:35
- Unused export 'FullName' src/core/value-objects/name.vo.ts:42
- Unused private method 'isEligibleForRole' src/core/entities/user.entity.ts:308
- Unused private field 'commandBus' src/presentation/modules/admin/admin.controller.ts:17
- Unused private field 'configService' src/presentation/modules/auth/strategies/jwt.strategy.ts:13
- Not all async functions that make a request accept an AbortSignal
- Diagnostic log message is built whether or not it is wanted REDACTED:106
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) reduce the strict null checking score
Minor — 34 finding(s)
- Outdated (npm): @ant-design/charts
- Outdated (npm): @ant-design/icons
- Outdated (npm): @aws-sdk/client-s3
- Outdated (npm): @aws-sdk/lib-storage
- Outdated (npm): @aws-sdk/s3-request-presigner
- Outdated (npm): @nestjs/common
- Outdated (npm): @nestjs/core
- Outdated (npm): @nestjs/cqrs
- Outdated (npm): @nestjs/jwt
- Outdated (npm): @nestjs/passport
- Outdated (npm): @nestjs/platform-express
- Outdated (npm): @nestjs/swagger
- Outdated (npm): @prisma/adapter-pg
- Outdated (npm): @prisma/client
- Outdated (npm): @refinedev/antd
- Outdated (npm): @refinedev/core
- Outdated (npm): @refinedev/devtools
- Outdated (npm): @refinedev/kbar
- Outdated (npm): @refinedev/simple-rest
- Outdated (npm): @types/multer
- Outdated (npm): antd
- Outdated (npm): axios
- Outdated (npm): bcrypt
- Outdated (npm): class-validator
- Outdated (npm): dotenv
- doc comments repeat the names REDACTED:286
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-08dfd69ab7134e8da9eef4a8457020d3/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-08dfd69ab7134e8da9eef4a8457020d3/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 src/generated . | 27 | 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 | 87 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 7 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.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 src/generated . | 1 | artifacts/raw/semgrep-gdpr.json |
| 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 |