Executive summary
systemsdk/docker-symfony-api falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 47 out of 100 and is rated Weak, and 24 of its 31 critical findings are security problems.
Accessibility, at 32, is the weakest lens and counts most in the score. The best first step is structuring the pages, worth about 11 points. Automating accessibility checks comes next, worth about 10 points. Raising Accessibility to 70 would lift the score to about 58.
Seven passwords or keys in the code's history and five in the code are open to anyone who can read the repository. Seven settings leave the servers or containers unsafe, and three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Replacing each exposed password or key, correcting the unsafe settings and pinning each tool to an exact version would close these risks. Updating the vulnerable packages would fix the two packages with a known security hole. Referring to the other business object by its identifier would take care of the five business objects holding another business object directly.
The product code is 26,341 lines, about €37,000 to rebuild.
If Accessibility rose from 32 to 70, the lowest score rated Strong, the score would rise from 47 to about 58.
New since the last survey: 2 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 22 findings
- Boundary Type-Coupling · Cross-context type UserGroup (User → ApiKey) src/ApiKey/Domain/Entity/ApiKey.php
- Boundary Type-Coupling · Cross-context type UserGroup (User → ApiKey) src/ApiKey/Domain/Entity/ApiKey.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Application/Resource/LogLoginFailureResource.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Application/Service/Interfaces/LoginLoggerServiceInterface.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Application/Service/LoginLoggerService.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Domain/Entity/LogLogin.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Domain/Entity/LogLogin.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Domain/Entity/LogLoginFailure.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Domain/Entity/LogLoginFailure.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Domain/Entity/LogRequest.php
- Boundary Type-Coupling · Cross-context type ApiKey (ApiKey → Log) src/Log/Domain/Entity/LogRequest.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Domain/Entity/LogRequest.php
- Boundary Type-Coupling · Cross-context type ApiKey (ApiKey → Log) src/Log/Domain/Entity/LogRequest.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Domain/Repository/Interfaces/LogLoginFailureRepositoryInterface.php
- Boundary Type-Coupling · Cross-context type User (User → Log) src/Log/Infrastructure/Repository/LogLoginFailureRepository.php
- Boundary Type-Coupling · Cross-context type Role (Role → User) src/User/Application/DTO/UserGroup/UserGroup.php
- Boundary Type-Coupling · Cross-context type Role (Role → User) src/User/Application/DTO/UserGroup/UserGroup.php
- Boundary Type-Coupling · Cross-context type ApiKey (ApiKey → User) src/User/Application/Security/UserTypeIdentification.php
- Boundary Type-Coupling · Cross-context type Role (Role → User) src/User/Domain/Entity/UserGroup.php
- Boundary Type-Coupling · Cross-context type Role (Role → User) src/User/Domain/Entity/UserGroup.php
- Boundary Type-Coupling · Cross-context type ApiKey (ApiKey → User) src/User/Domain/Entity/UserGroup.php
- Boundary Type-Coupling · Cross-context type ApiKey (ApiKey → User) src/User/Domain/Entity/UserGroup.php
Rebuild cost: about €37,000 · Estimate
| Cost to rebuild | €12,000 to €62,000, for 206 to 653 hours of work, about 0.3 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 47. 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 | Medium: 26,341 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 ApiKey.Domain.Repository.Interfaces | 2 General.Domain.Entity.Interfaces | 3 General.Domain.Enum.Interfaces | 4 General.Domain.Service.Interfaces | 5 General.Transport.Rest | 6 Role.Application.Security.Interfaces | 7 General.Application.DTO.Interfaces | 8 General.Domain.Enum | 9 General.Domain.Repository.Interfaces | 10 Log.Domain.Enum | 11 Role.Domain.Entity | 12 Tool.Domain.Entity | 13 User.Domain.Entity.Interfaces | 14 General.Application.DTO | 15 General.Application.Rest.Interfaces | 16 General.Infrastructure.Repository | 17 General.Transport.AutoMapper | 18 Tool.Domain.Repository.Interfaces | 19 User.Domain.Entity | 20 ApiKey.Domain.Entity | 21 General.Application.Rest | 22 Log.Domain.Repository.Interfaces | 23 Tool.Application.Service | 24 User.Application.DTO.User | 25 User.Domain.Repository.Interfaces | 26 ApiKey.Application.Resource | 27 ApiKey.Application.Security | 28 ApiKey.Application.Security.Provider.Interfaces | 29 Log.Application.Resource | 30 Log.Domain.Entity | 31 Role.Application.Resource | 32 User.Application.Resource | 33 ApiKey.Application.Security.Provider | 34 ApiKey.Transport.Command.ApiKey | 35 Log.Application.Service.Interfaces | 36 Role.Transport.Command.Role | 37 User.Transport.Form.Type.Console | 38 Log.Application.Service | 39 User.Application.Security | 40 User.Transport.EventSubscriber |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ApiKey.Domain.Repository.Interfaces | ||||||||||||||||||||||||||||||||||||||||
| 2 General.Domain.Entity.Interfaces | ||||||||||||||||||||||||||||||||||||||||
| 3 General.Domain.Enum.Interfaces | ||||||||||||||||||||||||||||||||||||||||
| 4 General.Domain.Service.Interfaces | ||||||||||||||||||||||||||||||||||||||||
| 5 General.Transport.Rest | ||||||||||||||||||||||||||||||||||||||||
| 6 Role.Application.Security.Interfaces | ||||||||||||||||||||||||||||||||||||||||
| 7 General.Application.DTO.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 General.Domain.Enum | 4 | |||||||||||||||||||||||||||||||||||||||
| 9 General.Domain.Repository.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Log.Domain.Enum | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Role.Domain.Entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Tool.Domain.Entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 User.Domain.Entity.Interfaces | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 General.Application.DTO | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 General.Application.Rest.Interfaces | 6 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 General.Infrastructure.Repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 General.Transport.AutoMapper | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Tool.Domain.Repository.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 User.Domain.Entity | 2 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 20 ApiKey.Domain.Entity | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 General.Application.Rest | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 Log.Domain.Repository.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Tool.Application.Service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 User.Application.DTO.User | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 User.Domain.Repository.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 ApiKey.Application.Resource | 9 | 9 | ||||||||||||||||||||||||||||||||||||||
| 27 ApiKey.Application.Security | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 ApiKey.Application.Security.Provider.Interfaces | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 Log.Application.Resource | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 30 Log.Domain.Entity | 3 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 Role.Application.Resource | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 User.Application.Resource | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 33 ApiKey.Application.Security.Provider | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 ApiKey.Transport.Command.ApiKey | 3 | 4 | 6 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 Log.Application.Service.Interfaces | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 36 Role.Transport.Command.Role | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 User.Transport.Form.Type.Console | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 Log.Application.Service | 1 | 1 | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 39 User.Application.Security | 2 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 User.Transport.EventSubscriber | 1 | 3 | 1 | 2 | 1 |
7→2 General.Application.DTO.Interfaces uses General.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in General.Application.DTO.Interfaces uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.General.Application.DTO.Interfaces.RestDtoInterface→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- General.Application.DTO.Interfaces uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break General.Application.DTO.Interfaces, while a change to General.Application.DTO.Interfaces can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: General.Application.DTO.Interfaces uses a module listed above it, which is the healthy direction.
8→3 General.Domain.Enum uses General.Domain.Enum.Interfaces✕
- Connections
- 4 pairs of types, where a type in General.Domain.Enum uses a type in General.Domain.Enum.Interfaces.
- The types involved
App.General.Domain.Enum.Language→App.General.Domain.Enum.Interfaces.DatabaseEnumInterfaceApp.General.Domain.Enum.Language→App.General.Domain.Enum.Interfaces.EnumWithDefaultInterfaceApp.General.Domain.Enum.Locale→App.General.Domain.Enum.Interfaces.DatabaseEnumInterfaceApp.General.Domain.Enum.Locale→App.General.Domain.Enum.Interfaces.EnumWithDefaultInterface
- Direction
- General.Domain.Enum uses General.Domain.Enum.Interfaces, so a change to General.Domain.Enum.Interfaces can break General.Domain.Enum, while a change to General.Domain.Enum can't break General.Domain.Enum.Interfaces.
- Position
- Below the diagonal: General.Domain.Enum uses a module listed above it, which is the healthy direction.
9→2 General.Domain.Repository.Interfaces uses General.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in General.Domain.Repository.Interfaces uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.General.Domain.Repository.Interfaces.BaseRepositoryInterface→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- General.Domain.Repository.Interfaces uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break General.Domain.Repository.Interfaces, while a change to General.Domain.Repository.Interfaces can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: General.Domain.Repository.Interfaces uses a module listed above it, which is the healthy direction.
10→3 Log.Domain.Enum uses General.Domain.Enum.Interfaces✕
- Connections
- 1 pair of types, where a type in Log.Domain.Enum uses a type in General.Domain.Enum.Interfaces.
- The types involved
App.Log.Domain.Enum.LogLogin→App.General.Domain.Enum.Interfaces.DatabaseEnumInterface
- Direction
- Log.Domain.Enum uses General.Domain.Enum.Interfaces, so a change to General.Domain.Enum.Interfaces can break Log.Domain.Enum, while a change to Log.Domain.Enum can't break General.Domain.Enum.Interfaces.
- Position
- Below the diagonal: Log.Domain.Enum uses a module listed above it, which is the healthy direction.
11→2 Role.Domain.Entity uses General.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in Role.Domain.Entity uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.Role.Domain.Entity.Role→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- Role.Domain.Entity uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break Role.Domain.Entity, while a change to Role.Domain.Entity can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: Role.Domain.Entity uses a module listed above it, which is the healthy direction.
12→2 Tool.Domain.Entity uses General.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in Tool.Domain.Entity uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.Tool.Domain.Entity.Health→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- Tool.Domain.Entity uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break Tool.Domain.Entity, while a change to Tool.Domain.Entity can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: Tool.Domain.Entity uses a module listed above it, which is the healthy direction.
13→2 User.Domain.Entity.Interfaces uses General.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in User.Domain.Entity.Interfaces uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.User.Domain.Entity.Interfaces.UserGroupAwareInterface→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- User.Domain.Entity.Interfaces uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break User.Domain.Entity.Interfaces, while a change to User.Domain.Entity.Interfaces can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: User.Domain.Entity.Interfaces uses a module listed above it, which is the healthy direction.
13→19 User.Domain.Entity.Interfaces uses User.Domain.Entity part of a loop✕
- Connections
- 1 pair of types, where a type in User.Domain.Entity.Interfaces uses a type in User.Domain.Entity.
- The types involved
App.User.Domain.Entity.Interfaces.UserGroupAwareInterface→App.User.Domain.Entity.UserGroup
- Direction
- User.Domain.Entity.Interfaces uses User.Domain.Entity, so a change to User.Domain.Entity can break User.Domain.Entity.Interfaces, while a change to User.Domain.Entity.Interfaces can't break User.Domain.Entity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 General.Application.DTO uses General.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in General.Application.DTO uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.General.Application.DTO.RestDto→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- General.Application.DTO uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break General.Application.DTO, while a change to General.Application.DTO can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: General.Application.DTO uses a module listed above it, which is the healthy direction.
14→7 General.Application.DTO uses General.Application.DTO.Interfaces✕
- Connections
- 1 pair of types, where a type in General.Application.DTO uses a type in General.Application.DTO.Interfaces.
- The types involved
App.General.Application.DTO.RestDto→App.General.Application.DTO.Interfaces.RestDtoInterface
- Direction
- General.Application.DTO uses General.Application.DTO.Interfaces, so a change to General.Application.DTO.Interfaces can break General.Application.DTO, while a change to General.Application.DTO can't break General.Application.DTO.Interfaces.
- Position
- Below the diagonal: General.Application.DTO uses a module listed above it, which is the healthy direction.
15→2 General.Application.Rest.Interfaces uses General.Domain.Entity.Interfaces✕
- Connections
- 6 pairs of types, where a type in General.Application.Rest.Interfaces uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.General.Application.Rest.Interfaces.RestCreateResourceInterface→App.General.Domain.Entity.Interfaces.EntityInterfaceApp.General.Application.Rest.Interfaces.RestDeleteResourceInterface→App.General.Domain.Entity.Interfaces.EntityInterfaceApp.General.Application.Rest.Interfaces.RestFindOneResourceInterface→App.General.Domain.Entity.Interfaces.EntityInterfaceApp.General.Application.Rest.Interfaces.RestPatchResourceInterface→App.General.Domain.Entity.Interfaces.EntityInterfaceApp.General.Application.Rest.Interfaces.RestSaveResourceInterface→App.General.Domain.Entity.Interfaces.EntityInterfaceApp.General.Application.Rest.Interfaces.RestUpdateResourceInterface→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- General.Application.Rest.Interfaces uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break General.Application.Rest.Interfaces, while a change to General.Application.Rest.Interfaces can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: General.Application.Rest.Interfaces uses a module listed above it, which is the healthy direction.
15→7 General.Application.Rest.Interfaces uses General.Application.DTO.Interfaces✕
- Connections
- 4 pairs of types, where a type in General.Application.Rest.Interfaces uses a type in General.Application.DTO.Interfaces.
- The types involved
App.General.Application.Rest.Interfaces.BaseRestResourceInterface→App.General.Application.DTO.Interfaces.RestDtoInterfaceApp.General.Application.Rest.Interfaces.RestCreateResourceInterface→App.General.Application.DTO.Interfaces.RestDtoInterfaceApp.General.Application.Rest.Interfaces.RestPatchResourceInterface→App.General.Application.DTO.Interfaces.RestDtoInterfaceApp.General.Application.Rest.Interfaces.RestUpdateResourceInterface→App.General.Application.DTO.Interfaces.RestDtoInterface
- Direction
- General.Application.Rest.Interfaces uses General.Application.DTO.Interfaces, so a change to General.Application.DTO.Interfaces can break General.Application.Rest.Interfaces, while a change to General.Application.Rest.Interfaces can't break General.Application.DTO.Interfaces.
- Position
- Below the diagonal: General.Application.Rest.Interfaces uses a module listed above it, which is the healthy direction.
15→9 General.Application.Rest.Interfaces uses General.Domain.Repository.Interfaces✕
- Connections
- 1 pair of types, where a type in General.Application.Rest.Interfaces uses a type in General.Domain.Repository.Interfaces.
- The types involved
App.General.Application.Rest.Interfaces.BaseRestResourceInterface→App.General.Domain.Repository.Interfaces.BaseRepositoryInterface
- Direction
- General.Application.Rest.Interfaces uses General.Domain.Repository.Interfaces, so a change to General.Domain.Repository.Interfaces can break General.Application.Rest.Interfaces, while a change to General.Application.Rest.Interfaces can't break General.Domain.Repository.Interfaces.
- Position
- Below the diagonal: General.Application.Rest.Interfaces uses a module listed above it, which is the healthy direction.
16→2 General.Infrastructure.Repository uses General.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in General.Infrastructure.Repository uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.General.Infrastructure.Repository.BaseRepository→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- General.Infrastructure.Repository uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break General.Infrastructure.Repository, while a change to General.Infrastructure.Repository can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: General.Infrastructure.Repository uses a module listed above it, which is the healthy direction.
16→9 General.Infrastructure.Repository uses General.Domain.Repository.Interfaces✕
- Connections
- 1 pair of types, where a type in General.Infrastructure.Repository uses a type in General.Domain.Repository.Interfaces.
- The types involved
App.General.Infrastructure.Repository.BaseRepository→App.General.Domain.Repository.Interfaces.BaseRepositoryInterface
- Direction
- General.Infrastructure.Repository uses General.Domain.Repository.Interfaces, so a change to General.Domain.Repository.Interfaces can break General.Infrastructure.Repository, while a change to General.Infrastructure.Repository can't break General.Domain.Repository.Interfaces.
- Position
- Below the diagonal: General.Infrastructure.Repository uses a module listed above it, which is the healthy direction.
17→7 General.Transport.AutoMapper uses General.Application.DTO.Interfaces✕
- Connections
- 1 pair of types, where a type in General.Transport.AutoMapper uses a type in General.Application.DTO.Interfaces.
- The types involved
App.General.Transport.AutoMapper.RestRequestMapper→App.General.Application.DTO.Interfaces.RestDtoInterface
- Direction
- General.Transport.AutoMapper uses General.Application.DTO.Interfaces, so a change to General.Application.DTO.Interfaces can break General.Transport.AutoMapper, while a change to General.Transport.AutoMapper can't break General.Application.DTO.Interfaces.
- Position
- Below the diagonal: General.Transport.AutoMapper uses a module listed above it, which is the healthy direction.
18→12 Tool.Domain.Repository.Interfaces uses Tool.Domain.Entity✕
- Connections
- 1 pair of types, where a type in Tool.Domain.Repository.Interfaces uses a type in Tool.Domain.Entity.
- The types involved
App.Tool.Domain.Repository.Interfaces.HealthRepositoryInterface→App.Tool.Domain.Entity.Health
- Direction
- Tool.Domain.Repository.Interfaces uses Tool.Domain.Entity, so a change to Tool.Domain.Entity can break Tool.Domain.Repository.Interfaces, while a change to Tool.Domain.Repository.Interfaces can't break Tool.Domain.Entity.
- Position
- Below the diagonal: Tool.Domain.Repository.Interfaces uses a module listed above it, which is the healthy direction.
19→2 User.Domain.Entity uses General.Domain.Entity.Interfaces✕
- Connections
- 2 pairs of types, where a type in User.Domain.Entity uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.User.Domain.Entity.User→App.General.Domain.Entity.Interfaces.EntityInterfaceApp.User.Domain.Entity.UserGroup→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- User.Domain.Entity uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break User.Domain.Entity, while a change to User.Domain.Entity can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: User.Domain.Entity uses a module listed above it, which is the healthy direction.
19→8 User.Domain.Entity uses General.Domain.Enum✕
- Connections
- 2 pairs of types, where a type in User.Domain.Entity uses a type in General.Domain.Enum.
- The types involved
App.User.Domain.Entity.User→App.General.Domain.Enum.LanguageApp.User.Domain.Entity.User→App.General.Domain.Enum.Locale
- Direction
- User.Domain.Entity uses General.Domain.Enum, so a change to General.Domain.Enum can break User.Domain.Entity, while a change to User.Domain.Entity can't break General.Domain.Enum.
- Position
- Below the diagonal: User.Domain.Entity uses a module listed above it, which is the healthy direction.
19→11 User.Domain.Entity uses Role.Domain.Entity✕
- Connections
- 1 pair of types, where a type in User.Domain.Entity uses a type in Role.Domain.Entity.
- The types involved
App.User.Domain.Entity.UserGroup→App.Role.Domain.Entity.Role
- Direction
- User.Domain.Entity uses Role.Domain.Entity, so a change to Role.Domain.Entity can break User.Domain.Entity, while a change to User.Domain.Entity can't break Role.Domain.Entity.
- Position
- Below the diagonal: User.Domain.Entity uses a module listed above it, which is the healthy direction.
19→13 User.Domain.Entity uses User.Domain.Entity.Interfaces✕
- Connections
- 2 pairs of types, where a type in User.Domain.Entity uses a type in User.Domain.Entity.Interfaces.
- The types involved
App.User.Domain.Entity.User→App.User.Domain.Entity.Interfaces.UserGroupAwareInterfaceApp.User.Domain.Entity.User→App.User.Domain.Entity.Interfaces.UserInterface
- Direction
- User.Domain.Entity uses User.Domain.Entity.Interfaces, so a change to User.Domain.Entity.Interfaces can break User.Domain.Entity, while a change to User.Domain.Entity can't break User.Domain.Entity.Interfaces.
- Position
- Below the diagonal: User.Domain.Entity uses a module listed above it, which is the healthy direction.
19→20 User.Domain.Entity uses ApiKey.Domain.Entity part of a loop✕
- Connections
- 1 pair of types, where a type in User.Domain.Entity uses a type in ApiKey.Domain.Entity.
- The types involved
App.User.Domain.Entity.UserGroup→App.ApiKey.Domain.Entity.ApiKey
- Direction
- User.Domain.Entity uses ApiKey.Domain.Entity, so a change to ApiKey.Domain.Entity can break User.Domain.Entity, while a change to User.Domain.Entity can't break ApiKey.Domain.Entity.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→2 ApiKey.Domain.Entity uses General.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in ApiKey.Domain.Entity uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.ApiKey.Domain.Entity.ApiKey→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- ApiKey.Domain.Entity uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break ApiKey.Domain.Entity, while a change to ApiKey.Domain.Entity can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: ApiKey.Domain.Entity uses a module listed above it, which is the healthy direction.
20→13 ApiKey.Domain.Entity uses User.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in ApiKey.Domain.Entity uses a type in User.Domain.Entity.Interfaces.
- The types involved
App.ApiKey.Domain.Entity.ApiKey→App.User.Domain.Entity.Interfaces.UserGroupAwareInterface
- Direction
- ApiKey.Domain.Entity uses User.Domain.Entity.Interfaces, so a change to User.Domain.Entity.Interfaces can break ApiKey.Domain.Entity, while a change to ApiKey.Domain.Entity can't break User.Domain.Entity.Interfaces.
- Position
- Below the diagonal: ApiKey.Domain.Entity uses a module listed above it, which is the healthy direction.
20→19 ApiKey.Domain.Entity uses User.Domain.Entity✕
- Connections
- 1 pair of types, where a type in ApiKey.Domain.Entity uses a type in User.Domain.Entity.
- The types involved
App.ApiKey.Domain.Entity.ApiKey→App.User.Domain.Entity.UserGroup
- Direction
- ApiKey.Domain.Entity uses User.Domain.Entity, so a change to User.Domain.Entity can break ApiKey.Domain.Entity, while a change to ApiKey.Domain.Entity can't break User.Domain.Entity.
- Position
- Below the diagonal: ApiKey.Domain.Entity uses a module listed above it, which is the healthy direction.
21→9 General.Application.Rest uses General.Domain.Repository.Interfaces✕
- Connections
- 2 pairs of types, where a type in General.Application.Rest uses a type in General.Domain.Repository.Interfaces.
- The types involved
App.General.Application.Rest.RestResource→App.General.Domain.Repository.Interfaces.BaseRepositoryInterfaceApp.General.Application.Rest.RestSmallResource→App.General.Domain.Repository.Interfaces.BaseRepositoryInterface
- Direction
- General.Application.Rest uses General.Domain.Repository.Interfaces, so a change to General.Domain.Repository.Interfaces can break General.Application.Rest, while a change to General.Application.Rest can't break General.Domain.Repository.Interfaces.
- Position
- Below the diagonal: General.Application.Rest uses a module listed above it, which is the healthy direction.
21→15 General.Application.Rest uses General.Application.Rest.Interfaces✕
- Connections
- 2 pairs of types, where a type in General.Application.Rest uses a type in General.Application.Rest.Interfaces.
- The types involved
App.General.Application.Rest.RestResource→App.General.Application.Rest.Interfaces.RestResourceInterfaceApp.General.Application.Rest.RestSmallResource→App.General.Application.Rest.Interfaces.RestSmallResourceInterface
- Direction
- General.Application.Rest uses General.Application.Rest.Interfaces, so a change to General.Application.Rest.Interfaces can break General.Application.Rest, while a change to General.Application.Rest can't break General.Application.Rest.Interfaces.
- Position
- Below the diagonal: General.Application.Rest uses a module listed above it, which is the healthy direction.
22→19 Log.Domain.Repository.Interfaces uses User.Domain.Entity✕
- Connections
- 1 pair of types, where a type in Log.Domain.Repository.Interfaces uses a type in User.Domain.Entity.
- The types involved
App.Log.Domain.Repository.Interfaces.LogLoginFailureRepositoryInterface→App.User.Domain.Entity.User
- Direction
- Log.Domain.Repository.Interfaces uses User.Domain.Entity, so a change to User.Domain.Entity can break Log.Domain.Repository.Interfaces, while a change to Log.Domain.Repository.Interfaces can't break User.Domain.Entity.
- Position
- Below the diagonal: Log.Domain.Repository.Interfaces uses a module listed above it, which is the healthy direction.
23→12 Tool.Application.Service uses Tool.Domain.Entity✕
- Connections
- 1 pair of types, where a type in Tool.Application.Service uses a type in Tool.Domain.Entity.
- The types involved
App.Tool.Application.Service.HealthService→App.Tool.Domain.Entity.Health
- Direction
- Tool.Application.Service uses Tool.Domain.Entity, so a change to Tool.Domain.Entity can break Tool.Application.Service, while a change to Tool.Application.Service can't break Tool.Domain.Entity.
- Position
- Below the diagonal: Tool.Application.Service uses a module listed above it, which is the healthy direction.
23→18 Tool.Application.Service uses Tool.Domain.Repository.Interfaces✕
- Connections
- 1 pair of types, where a type in Tool.Application.Service uses a type in Tool.Domain.Repository.Interfaces.
- The types involved
App.Tool.Application.Service.HealthService→App.Tool.Domain.Repository.Interfaces.HealthRepositoryInterface
- Direction
- Tool.Application.Service uses Tool.Domain.Repository.Interfaces, so a change to Tool.Domain.Repository.Interfaces can break Tool.Application.Service, while a change to Tool.Application.Service can't break Tool.Domain.Repository.Interfaces.
- Position
- Below the diagonal: Tool.Application.Service uses a module listed above it, which is the healthy direction.
24→2 User.Application.DTO.User uses General.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in User.Application.DTO.User uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.User.Application.DTO.User.User→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- User.Application.DTO.User uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break User.Application.DTO.User, while a change to User.Application.DTO.User can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: User.Application.DTO.User uses a module listed above it, which is the healthy direction.
24→8 User.Application.DTO.User uses General.Domain.Enum✕
- Connections
- 2 pairs of types, where a type in User.Application.DTO.User uses a type in General.Domain.Enum.
- The types involved
App.User.Application.DTO.User.User→App.General.Domain.Enum.LanguageApp.User.Application.DTO.User.User→App.General.Domain.Enum.Locale
- Direction
- User.Application.DTO.User uses General.Domain.Enum, so a change to General.Domain.Enum can break User.Application.DTO.User, while a change to User.Application.DTO.User can't break General.Domain.Enum.
- Position
- Below the diagonal: User.Application.DTO.User uses a module listed above it, which is the healthy direction.
24→13 User.Application.DTO.User uses User.Domain.Entity.Interfaces✕
- Connections
- 1 pair of types, where a type in User.Application.DTO.User uses a type in User.Domain.Entity.Interfaces.
- The types involved
App.User.Application.DTO.User.User→App.User.Domain.Entity.Interfaces.UserGroupAwareInterface
- Direction
- User.Application.DTO.User uses User.Domain.Entity.Interfaces, so a change to User.Domain.Entity.Interfaces can break User.Application.DTO.User, while a change to User.Application.DTO.User can't break User.Domain.Entity.Interfaces.
- Position
- Below the diagonal: User.Application.DTO.User uses a module listed above it, which is the healthy direction.
24→14 User.Application.DTO.User uses General.Application.DTO✕
- Connections
- 1 pair of types, where a type in User.Application.DTO.User uses a type in General.Application.DTO.
- The types involved
App.User.Application.DTO.User.User→App.General.Application.DTO.RestDto
- Direction
- User.Application.DTO.User uses General.Application.DTO, so a change to General.Application.DTO can break User.Application.DTO.User, while a change to User.Application.DTO.User can't break General.Application.DTO.
- Position
- Below the diagonal: User.Application.DTO.User uses a module listed above it, which is the healthy direction.
24→19 User.Application.DTO.User uses User.Domain.Entity✕
- Connections
- 1 pair of types, where a type in User.Application.DTO.User uses a type in User.Domain.Entity.
- The types involved
App.User.Application.DTO.User.User→App.User.Domain.Entity.User
- Direction
- User.Application.DTO.User uses User.Domain.Entity, so a change to User.Domain.Entity can break User.Application.DTO.User, while a change to User.Application.DTO.User can't break User.Domain.Entity.
- Position
- Below the diagonal: User.Application.DTO.User uses a module listed above it, which is the healthy direction.
25→19 User.Domain.Repository.Interfaces uses User.Domain.Entity✕
- Connections
- 1 pair of types, where a type in User.Domain.Repository.Interfaces uses a type in User.Domain.Entity.
- The types involved
App.User.Domain.Repository.Interfaces.UserRepositoryInterface→App.User.Domain.Entity.User
- Direction
- User.Domain.Repository.Interfaces uses User.Domain.Entity, so a change to User.Domain.Entity can break User.Domain.Repository.Interfaces, while a change to User.Domain.Repository.Interfaces can't break User.Domain.Entity.
- Position
- Below the diagonal: User.Domain.Repository.Interfaces uses a module listed above it, which is the healthy direction.
26→1 ApiKey.Application.Resource uses ApiKey.Domain.Repository.Interfaces✕
- Connections
- 9 pairs of types, where a type in ApiKey.Application.Resource uses a type in ApiKey.Domain.Repository.Interfaces.
- The types involved
App.ApiKey.Application.Resource.ApiKeyCountResource→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterfaceApp.ApiKey.Application.Resource.ApiKeyCreateResource→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterfaceApp.ApiKey.Application.Resource.ApiKeyDeleteResource→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterfaceApp.ApiKey.Application.Resource.ApiKeyFindOneResource→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterfaceApp.ApiKey.Application.Resource.ApiKeyIdsResource→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterfaceApp.ApiKey.Application.Resource.ApiKeyListResource→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterfaceApp.ApiKey.Application.Resource.ApiKeyPatchResource→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterfaceApp.ApiKey.Application.Resource.ApiKeyResource→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterfaceApp.ApiKey.Application.Resource.ApiKeyUpdateResource→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterface
- Direction
- ApiKey.Application.Resource uses ApiKey.Domain.Repository.Interfaces, so a change to ApiKey.Domain.Repository.Interfaces can break ApiKey.Application.Resource, while a change to ApiKey.Application.Resource can't break ApiKey.Domain.Repository.Interfaces.
- Position
- Below the diagonal: ApiKey.Application.Resource uses a module listed above it, which is the healthy direction.
26→21 ApiKey.Application.Resource uses General.Application.Rest✕
- Connections
- 9 pairs of types, where a type in ApiKey.Application.Resource uses a type in General.Application.Rest.
- The types involved
App.ApiKey.Application.Resource.ApiKeyCountResource→App.General.Application.Rest.RestSmallResourceApp.ApiKey.Application.Resource.ApiKeyCreateResource→App.General.Application.Rest.RestSmallResourceApp.ApiKey.Application.Resource.ApiKeyDeleteResource→App.General.Application.Rest.RestSmallResourceApp.ApiKey.Application.Resource.ApiKeyFindOneResource→App.General.Application.Rest.RestSmallResourceApp.ApiKey.Application.Resource.ApiKeyIdsResource→App.General.Application.Rest.RestSmallResourceApp.ApiKey.Application.Resource.ApiKeyListResource→App.General.Application.Rest.RestSmallResourceApp.ApiKey.Application.Resource.ApiKeyPatchResource→App.General.Application.Rest.RestSmallResourceApp.ApiKey.Application.Resource.ApiKeyResource→App.General.Application.Rest.RestResourceApp.ApiKey.Application.Resource.ApiKeyUpdateResource→App.General.Application.Rest.RestSmallResource
- Direction
- ApiKey.Application.Resource uses General.Application.Rest, so a change to General.Application.Rest can break ApiKey.Application.Resource, while a change to ApiKey.Application.Resource can't break General.Application.Rest.
- Position
- Below the diagonal: ApiKey.Application.Resource uses a module listed above it, which is the healthy direction.
27→20 ApiKey.Application.Security uses ApiKey.Domain.Entity✕
- Connections
- 1 pair of types, where a type in ApiKey.Application.Security uses a type in ApiKey.Domain.Entity.
- The types involved
App.ApiKey.Application.Security.ApiKeyUser→App.ApiKey.Domain.Entity.ApiKey
- Direction
- ApiKey.Application.Security uses ApiKey.Domain.Entity, so a change to ApiKey.Domain.Entity can break ApiKey.Application.Security, while a change to ApiKey.Application.Security can't break ApiKey.Domain.Entity.
- Position
- Below the diagonal: ApiKey.Application.Security uses a module listed above it, which is the healthy direction.
28→1 ApiKey.Application.Security.Provider.Interfaces uses ApiKey.Domain.Repository.Interfaces✕
- Connections
- 1 pair of types, where a type in ApiKey.Application.Security.Provider.Interfaces uses a type in ApiKey.Domain.Repository.Interfaces.
- The types involved
App.ApiKey.Application.Security.Provider.Interfaces.ApiKeyUserProviderInterface→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterface
- Direction
- ApiKey.Application.Security.Provider.Interfaces uses ApiKey.Domain.Repository.Interfaces, so a change to ApiKey.Domain.Repository.Interfaces can break ApiKey.Application.Security.Provider.Interfaces, while a change to ApiKey.Application.Security.Provider.Interfaces can't break ApiKey.Domain.Repository.Interfaces.
- Position
- Below the diagonal: ApiKey.Application.Security.Provider.Interfaces uses a module listed above it, which is the healthy direction.
28→6 ApiKey.Application.Security.Provider.Interfaces uses Role.Application.Security.Interfaces✕
- Connections
- 1 pair of types, where a type in ApiKey.Application.Security.Provider.Interfaces uses a type in Role.Application.Security.Interfaces.
- The types involved
App.ApiKey.Application.Security.Provider.Interfaces.ApiKeyUserProviderInterface→App.Role.Application.Security.Interfaces.RolesServiceInterface
- Direction
- ApiKey.Application.Security.Provider.Interfaces uses Role.Application.Security.Interfaces, so a change to Role.Application.Security.Interfaces can break ApiKey.Application.Security.Provider.Interfaces, while a change to ApiKey.Application.Security.Provider.Interfaces can't break Role.Application.Security.Interfaces.
- Position
- Below the diagonal: ApiKey.Application.Security.Provider.Interfaces uses a module listed above it, which is the healthy direction.
28→20 ApiKey.Application.Security.Provider.Interfaces uses ApiKey.Domain.Entity✕
- Connections
- 1 pair of types, where a type in ApiKey.Application.Security.Provider.Interfaces uses a type in ApiKey.Domain.Entity.
- The types involved
App.ApiKey.Application.Security.Provider.Interfaces.ApiKeyUserProviderInterface→App.ApiKey.Domain.Entity.ApiKey
- Direction
- ApiKey.Application.Security.Provider.Interfaces uses ApiKey.Domain.Entity, so a change to ApiKey.Domain.Entity can break ApiKey.Application.Security.Provider.Interfaces, while a change to ApiKey.Application.Security.Provider.Interfaces can't break ApiKey.Domain.Entity.
- Position
- Below the diagonal: ApiKey.Application.Security.Provider.Interfaces uses a module listed above it, which is the healthy direction.
29→19 Log.Application.Resource uses User.Domain.Entity✕
- Connections
- 1 pair of types, where a type in Log.Application.Resource uses a type in User.Domain.Entity.
- The types involved
App.Log.Application.Resource.LogLoginFailureResource→App.User.Domain.Entity.User
- Direction
- Log.Application.Resource uses User.Domain.Entity, so a change to User.Domain.Entity can break Log.Application.Resource, while a change to Log.Application.Resource can't break User.Domain.Entity.
- Position
- Below the diagonal: Log.Application.Resource uses a module listed above it, which is the healthy direction.
29→21 Log.Application.Resource uses General.Application.Rest✕
- Connections
- 3 pairs of types, where a type in Log.Application.Resource uses a type in General.Application.Rest.
- The types involved
App.Log.Application.Resource.LogLoginFailureResource→App.General.Application.Rest.RestResourceApp.Log.Application.Resource.LogLoginResource→App.General.Application.Rest.RestResourceApp.Log.Application.Resource.LogRequestResource→App.General.Application.Rest.RestResource
- Direction
- Log.Application.Resource uses General.Application.Rest, so a change to General.Application.Rest can break Log.Application.Resource, while a change to Log.Application.Resource can't break General.Application.Rest.
- Position
- Below the diagonal: Log.Application.Resource uses a module listed above it, which is the healthy direction.
29→22 Log.Application.Resource uses Log.Domain.Repository.Interfaces✕
- Connections
- 3 pairs of types, where a type in Log.Application.Resource uses a type in Log.Domain.Repository.Interfaces.
- The types involved
App.Log.Application.Resource.LogLoginFailureResource→App.Log.Domain.Repository.Interfaces.LogLoginFailureRepositoryInterfaceApp.Log.Application.Resource.LogLoginResource→App.Log.Domain.Repository.Interfaces.LogLoginRepositoryInterfaceApp.Log.Application.Resource.LogRequestResource→App.Log.Domain.Repository.Interfaces.LogRequestRepositoryInterface
- Direction
- Log.Application.Resource uses Log.Domain.Repository.Interfaces, so a change to Log.Domain.Repository.Interfaces can break Log.Application.Resource, while a change to Log.Application.Resource can't break Log.Domain.Repository.Interfaces.
- Position
- Below the diagonal: Log.Application.Resource uses a module listed above it, which is the healthy direction.
30→2 Log.Domain.Entity uses General.Domain.Entity.Interfaces✕
- Connections
- 3 pairs of types, where a type in Log.Domain.Entity uses a type in General.Domain.Entity.Interfaces.
- The types involved
App.Log.Domain.Entity.LogLogin→App.General.Domain.Entity.Interfaces.EntityInterfaceApp.Log.Domain.Entity.LogLoginFailure→App.General.Domain.Entity.Interfaces.EntityInterfaceApp.Log.Domain.Entity.LogRequest→App.General.Domain.Entity.Interfaces.EntityInterface
- Direction
- Log.Domain.Entity uses General.Domain.Entity.Interfaces, so a change to General.Domain.Entity.Interfaces can break Log.Domain.Entity, while a change to Log.Domain.Entity can't break General.Domain.Entity.Interfaces.
- Position
- Below the diagonal: Log.Domain.Entity uses a module listed above it, which is the healthy direction.
30→10 Log.Domain.Entity uses Log.Domain.Enum✕
- Connections
- 1 pair of types, where a type in Log.Domain.Entity uses a type in Log.Domain.Enum.
- The types involved
App.Log.Domain.Entity.LogLogin→App.Log.Domain.Enum.LogLogin
- Direction
- Log.Domain.Entity uses Log.Domain.Enum, so a change to Log.Domain.Enum can break Log.Domain.Entity, while a change to Log.Domain.Entity can't break Log.Domain.Enum.
- Position
- Below the diagonal: Log.Domain.Entity uses a module listed above it, which is the healthy direction.
30→19 Log.Domain.Entity uses User.Domain.Entity✕
- Connections
- 3 pairs of types, where a type in Log.Domain.Entity uses a type in User.Domain.Entity.
- The types involved
App.Log.Domain.Entity.LogLogin→App.User.Domain.Entity.UserApp.Log.Domain.Entity.LogLoginFailure→App.User.Domain.Entity.UserApp.Log.Domain.Entity.LogRequest→App.User.Domain.Entity.User
- Direction
- Log.Domain.Entity uses User.Domain.Entity, so a change to User.Domain.Entity can break Log.Domain.Entity, while a change to Log.Domain.Entity can't break User.Domain.Entity.
- Position
- Below the diagonal: Log.Domain.Entity uses a module listed above it, which is the healthy direction.
30→20 Log.Domain.Entity uses ApiKey.Domain.Entity✕
- Connections
- 1 pair of types, where a type in Log.Domain.Entity uses a type in ApiKey.Domain.Entity.
- The types involved
App.Log.Domain.Entity.LogRequest→App.ApiKey.Domain.Entity.ApiKey
- Direction
- Log.Domain.Entity uses ApiKey.Domain.Entity, so a change to ApiKey.Domain.Entity can break Log.Domain.Entity, while a change to Log.Domain.Entity can't break ApiKey.Domain.Entity.
- Position
- Below the diagonal: Log.Domain.Entity uses a module listed above it, which is the healthy direction.
31→21 Role.Application.Resource uses General.Application.Rest✕
- Connections
- 1 pair of types, where a type in Role.Application.Resource uses a type in General.Application.Rest.
- The types involved
App.Role.Application.Resource.RoleResource→App.General.Application.Rest.RestResource
- Direction
- Role.Application.Resource uses General.Application.Rest, so a change to General.Application.Rest can break Role.Application.Resource, while a change to Role.Application.Resource can't break General.Application.Rest.
- Position
- Below the diagonal: Role.Application.Resource uses a module listed above it, which is the healthy direction.
32→6 User.Application.Resource uses Role.Application.Security.Interfaces✕
- Connections
- 1 pair of types, where a type in User.Application.Resource uses a type in Role.Application.Security.Interfaces.
- The types involved
App.User.Application.Resource.UserResource→App.Role.Application.Security.Interfaces.RolesServiceInterface
- Direction
- User.Application.Resource uses Role.Application.Security.Interfaces, so a change to Role.Application.Security.Interfaces can break User.Application.Resource, while a change to User.Application.Resource can't break Role.Application.Security.Interfaces.
- Position
- Below the diagonal: User.Application.Resource uses a module listed above it, which is the healthy direction.
32→19 User.Application.Resource uses User.Domain.Entity✕
- Connections
- 1 pair of types, where a type in User.Application.Resource uses a type in User.Domain.Entity.
- The types involved
App.User.Application.Resource.UserResource→App.User.Domain.Entity.UserGroup
- Direction
- User.Application.Resource uses User.Domain.Entity, so a change to User.Domain.Entity can break User.Application.Resource, while a change to User.Application.Resource can't break User.Domain.Entity.
- Position
- Below the diagonal: User.Application.Resource uses a module listed above it, which is the healthy direction.
32→21 User.Application.Resource uses General.Application.Rest✕
- Connections
- 2 pairs of types, where a type in User.Application.Resource uses a type in General.Application.Rest.
- The types involved
App.User.Application.Resource.UserGroupResource→App.General.Application.Rest.RestResourceApp.User.Application.Resource.UserResource→App.General.Application.Rest.RestResource
- Direction
- User.Application.Resource uses General.Application.Rest, so a change to General.Application.Rest can break User.Application.Resource, while a change to User.Application.Resource can't break General.Application.Rest.
- Position
- Below the diagonal: User.Application.Resource uses a module listed above it, which is the healthy direction.
32→25 User.Application.Resource uses User.Domain.Repository.Interfaces✕
- Connections
- 2 pairs of types, where a type in User.Application.Resource uses a type in User.Domain.Repository.Interfaces.
- The types involved
App.User.Application.Resource.UserGroupResource→App.User.Domain.Repository.Interfaces.UserGroupRepositoryInterfaceApp.User.Application.Resource.UserResource→App.User.Domain.Repository.Interfaces.UserRepositoryInterface
- Direction
- User.Application.Resource uses User.Domain.Repository.Interfaces, so a change to User.Domain.Repository.Interfaces can break User.Application.Resource, while a change to User.Application.Resource can't break User.Domain.Repository.Interfaces.
- Position
- Below the diagonal: User.Application.Resource uses a module listed above it, which is the healthy direction.
33→1 ApiKey.Application.Security.Provider uses ApiKey.Domain.Repository.Interfaces✕
- Connections
- 1 pair of types, where a type in ApiKey.Application.Security.Provider uses a type in ApiKey.Domain.Repository.Interfaces.
- The types involved
App.ApiKey.Application.Security.Provider.ApiKeyUserProvider→App.ApiKey.Domain.Repository.Interfaces.ApiKeyRepositoryInterface
- Direction
- ApiKey.Application.Security.Provider uses ApiKey.Domain.Repository.Interfaces, so a change to ApiKey.Domain.Repository.Interfaces can break ApiKey.Application.Security.Provider, while a change to ApiKey.Application.Security.Provider can't break ApiKey.Domain.Repository.Interfaces.
- Position
- Below the diagonal: ApiKey.Application.Security.Provider uses a module listed above it, which is the healthy direction.
33→6 ApiKey.Application.Security.Provider uses Role.Application.Security.Interfaces✕
- Connections
- 1 pair of types, where a type in ApiKey.Application.Security.Provider uses a type in Role.Application.Security.Interfaces.
- The types involved
App.ApiKey.Application.Security.Provider.ApiKeyUserProvider→App.Role.Application.Security.Interfaces.RolesServiceInterface
- Direction
- ApiKey.Application.Security.Provider uses Role.Application.Security.Interfaces, so a change to Role.Application.Security.Interfaces can break ApiKey.Application.Security.Provider, while a change to ApiKey.Application.Security.Provider can't break Role.Application.Security.Interfaces.
- Position
- Below the diagonal: ApiKey.Application.Security.Provider uses a module listed above it, which is the healthy direction.
33→20 ApiKey.Application.Security.Provider uses ApiKey.Domain.Entity✕
- Connections
- 1 pair of types, where a type in ApiKey.Application.Security.Provider uses a type in ApiKey.Domain.Entity.
- The types involved
App.ApiKey.Application.Security.Provider.ApiKeyUserProvider→App.ApiKey.Domain.Entity.ApiKey
- Direction
- ApiKey.Application.Security.Provider uses ApiKey.Domain.Entity, so a change to ApiKey.Domain.Entity can break ApiKey.Application.Security.Provider, while a change to ApiKey.Application.Security.Provider can't break ApiKey.Domain.Entity.
- Position
- Below the diagonal: ApiKey.Application.Security.Provider uses a module listed above it, which is the healthy direction.
33→27 ApiKey.Application.Security.Provider uses ApiKey.Application.Security✕
- Connections
- 1 pair of types, where a type in ApiKey.Application.Security.Provider uses a type in ApiKey.Application.Security.
- The types involved
App.ApiKey.Application.Security.Provider.ApiKeyUserProvider→App.ApiKey.Application.Security.ApiKeyUser
- Direction
- ApiKey.Application.Security.Provider uses ApiKey.Application.Security, so a change to ApiKey.Application.Security can break ApiKey.Application.Security.Provider, while a change to ApiKey.Application.Security.Provider can't break ApiKey.Application.Security.
- Position
- Below the diagonal: ApiKey.Application.Security.Provider uses a module listed above it, which is the healthy direction.
33→28 ApiKey.Application.Security.Provider uses ApiKey.Application.Security.Provider.Interfaces✕
- Connections
- 1 pair of types, where a type in ApiKey.Application.Security.Provider uses a type in ApiKey.Application.Security.Provider.Interfaces.
- The types involved
App.ApiKey.Application.Security.Provider.ApiKeyUserProvider→App.ApiKey.Application.Security.Provider.Interfaces.ApiKeyUserProviderInterface
- Direction
- ApiKey.Application.Security.Provider uses ApiKey.Application.Security.Provider.Interfaces, so a change to ApiKey.Application.Security.Provider.Interfaces can break ApiKey.Application.Security.Provider, while a change to ApiKey.Application.Security.Provider can't break ApiKey.Application.Security.Provider.Interfaces.
- Position
- Below the diagonal: ApiKey.Application.Security.Provider uses a module listed above it, which is the healthy direction.
34→6 ApiKey.Transport.Command.ApiKey uses Role.Application.Security.Interfaces✕
- Connections
- 3 pairs of types, where a type in ApiKey.Transport.Command.ApiKey uses a type in Role.Application.Security.Interfaces.
- The types involved
App.ApiKey.Transport.Command.ApiKey.ApiKeyHelper→App.Role.Application.Security.Interfaces.RolesServiceInterfaceApp.ApiKey.Transport.Command.ApiKey.CreateApiKeyCommand→App.Role.Application.Security.Interfaces.RolesServiceInterfaceApp.ApiKey.Transport.Command.ApiKey.ListApiKeysCommand→App.Role.Application.Security.Interfaces.RolesServiceInterface
- Direction
- ApiKey.Transport.Command.ApiKey uses Role.Application.Security.Interfaces, so a change to Role.Application.Security.Interfaces can break ApiKey.Transport.Command.ApiKey, while a change to ApiKey.Transport.Command.ApiKey can't break Role.Application.Security.Interfaces.
- Position
- Below the diagonal: ApiKey.Transport.Command.ApiKey uses a module listed above it, which is the healthy direction.
34→20 ApiKey.Transport.Command.ApiKey uses ApiKey.Domain.Entity✕
- Connections
- 4 pairs of types, where a type in ApiKey.Transport.Command.ApiKey uses a type in ApiKey.Domain.Entity.
- The types involved
App.ApiKey.Transport.Command.ApiKey.ApiKeyHelper→App.ApiKey.Domain.Entity.ApiKeyApp.ApiKey.Transport.Command.ApiKey.ChangeTokenCommand→App.ApiKey.Domain.Entity.ApiKeyApp.ApiKey.Transport.Command.ApiKey.EditApiKeyCommand→App.ApiKey.Domain.Entity.ApiKeyApp.ApiKey.Transport.Command.ApiKey.RemoveApiKeyCommand→App.ApiKey.Domain.Entity.ApiKey
- Direction
- ApiKey.Transport.Command.ApiKey uses ApiKey.Domain.Entity, so a change to ApiKey.Domain.Entity can break ApiKey.Transport.Command.ApiKey, while a change to ApiKey.Transport.Command.ApiKey can't break ApiKey.Domain.Entity.
- Position
- Below the diagonal: ApiKey.Transport.Command.ApiKey uses a module listed above it, which is the healthy direction.
34→26 ApiKey.Transport.Command.ApiKey uses ApiKey.Application.Resource✕
- Connections
- 6 pairs of types, where a type in ApiKey.Transport.Command.ApiKey uses a type in ApiKey.Application.Resource.
- The types involved
App.ApiKey.Transport.Command.ApiKey.ApiKeyHelper→App.ApiKey.Application.Resource.ApiKeyResourceApp.ApiKey.Transport.Command.ApiKey.ChangeTokenCommand→App.ApiKey.Application.Resource.ApiKeyResourceApp.ApiKey.Transport.Command.ApiKey.CreateApiKeyCommand→App.ApiKey.Application.Resource.ApiKeyResourceApp.ApiKey.Transport.Command.ApiKey.EditApiKeyCommand→App.ApiKey.Application.Resource.ApiKeyResourceApp.ApiKey.Transport.Command.ApiKey.ListApiKeysCommand→App.ApiKey.Application.Resource.ApiKeyResourceApp.ApiKey.Transport.Command.ApiKey.RemoveApiKeyCommand→App.ApiKey.Application.Resource.ApiKeyResource
- Direction
- ApiKey.Transport.Command.ApiKey uses ApiKey.Application.Resource, so a change to ApiKey.Application.Resource can break ApiKey.Transport.Command.ApiKey, while a change to ApiKey.Transport.Command.ApiKey can't break ApiKey.Application.Resource.
- Position
- Below the diagonal: ApiKey.Transport.Command.ApiKey uses a module listed above it, which is the healthy direction.
34→31 ApiKey.Transport.Command.ApiKey uses Role.Application.Resource✕
- Connections
- 1 pair of types, where a type in ApiKey.Transport.Command.ApiKey uses a type in Role.Application.Resource.
- The types involved
App.ApiKey.Transport.Command.ApiKey.CreateApiKeyCommand→App.Role.Application.Resource.RoleResource
- Direction
- ApiKey.Transport.Command.ApiKey uses Role.Application.Resource, so a change to Role.Application.Resource can break ApiKey.Transport.Command.ApiKey, while a change to ApiKey.Transport.Command.ApiKey can't break Role.Application.Resource.
- Position
- Below the diagonal: ApiKey.Transport.Command.ApiKey uses a module listed above it, which is the healthy direction.
34→32 ApiKey.Transport.Command.ApiKey uses User.Application.Resource✕
- Connections
- 1 pair of types, where a type in ApiKey.Transport.Command.ApiKey uses a type in User.Application.Resource.
- The types involved
App.ApiKey.Transport.Command.ApiKey.CreateApiKeyCommand→App.User.Application.Resource.UserGroupResource
- Direction
- ApiKey.Transport.Command.ApiKey uses User.Application.Resource, so a change to User.Application.Resource can break ApiKey.Transport.Command.ApiKey, while a change to ApiKey.Transport.Command.ApiKey can't break User.Application.Resource.
- Position
- Below the diagonal: ApiKey.Transport.Command.ApiKey uses a module listed above it, which is the healthy direction.
35→10 Log.Application.Service.Interfaces uses Log.Domain.Enum✕
- Connections
- 1 pair of types, where a type in Log.Application.Service.Interfaces uses a type in Log.Domain.Enum.
- The types involved
App.Log.Application.Service.Interfaces.LoginLoggerServiceInterface→App.Log.Domain.Enum.LogLogin
- Direction
- Log.Application.Service.Interfaces uses Log.Domain.Enum, so a change to Log.Domain.Enum can break Log.Application.Service.Interfaces, while a change to Log.Application.Service.Interfaces can't break Log.Domain.Enum.
- Position
- Below the diagonal: Log.Application.Service.Interfaces uses a module listed above it, which is the healthy direction.
35→19 Log.Application.Service.Interfaces uses User.Domain.Entity✕
- Connections
- 1 pair of types, where a type in Log.Application.Service.Interfaces uses a type in User.Domain.Entity.
- The types involved
App.Log.Application.Service.Interfaces.LoginLoggerServiceInterface→App.User.Domain.Entity.User
- Direction
- Log.Application.Service.Interfaces uses User.Domain.Entity, so a change to User.Domain.Entity can break Log.Application.Service.Interfaces, while a change to Log.Application.Service.Interfaces can't break User.Domain.Entity.
- Position
- Below the diagonal: Log.Application.Service.Interfaces uses a module listed above it, which is the healthy direction.
35→26 Log.Application.Service.Interfaces uses ApiKey.Application.Resource✕
- Connections
- 1 pair of types, where a type in Log.Application.Service.Interfaces uses a type in ApiKey.Application.Resource.
- The types involved
App.Log.Application.Service.Interfaces.RequestLoggerServiceInterface→App.ApiKey.Application.Resource.ApiKeyResource
- Direction
- Log.Application.Service.Interfaces uses ApiKey.Application.Resource, so a change to ApiKey.Application.Resource can break Log.Application.Service.Interfaces, while a change to Log.Application.Service.Interfaces can't break ApiKey.Application.Resource.
- Position
- Below the diagonal: Log.Application.Service.Interfaces uses a module listed above it, which is the healthy direction.
35→29 Log.Application.Service.Interfaces uses Log.Application.Resource✕
- Connections
- 2 pairs of types, where a type in Log.Application.Service.Interfaces uses a type in Log.Application.Resource.
- The types involved
App.Log.Application.Service.Interfaces.LoginLoggerServiceInterface→App.Log.Application.Resource.LogLoginResourceApp.Log.Application.Service.Interfaces.RequestLoggerServiceInterface→App.Log.Application.Resource.LogRequestResource
- Direction
- Log.Application.Service.Interfaces uses Log.Application.Resource, so a change to Log.Application.Resource can break Log.Application.Service.Interfaces, while a change to Log.Application.Service.Interfaces can't break Log.Application.Resource.
- Position
- Below the diagonal: Log.Application.Service.Interfaces uses a module listed above it, which is the healthy direction.
35→32 Log.Application.Service.Interfaces uses User.Application.Resource✕
- Connections
- 1 pair of types, where a type in Log.Application.Service.Interfaces uses a type in User.Application.Resource.
- The types involved
App.Log.Application.Service.Interfaces.RequestLoggerServiceInterface→App.User.Application.Resource.UserResource
- Direction
- Log.Application.Service.Interfaces uses User.Application.Resource, so a change to User.Application.Resource can break Log.Application.Service.Interfaces, while a change to Log.Application.Service.Interfaces can't break User.Application.Resource.
- Position
- Below the diagonal: Log.Application.Service.Interfaces uses a module listed above it, which is the healthy direction.
36→6 Role.Transport.Command.Role uses Role.Application.Security.Interfaces✕
- Connections
- 1 pair of types, where a type in Role.Transport.Command.Role uses a type in Role.Application.Security.Interfaces.
- The types involved
App.Role.Transport.Command.Role.CreateRolesWithUserGroupsCommand→App.Role.Application.Security.Interfaces.RolesServiceInterface
- Direction
- Role.Transport.Command.Role uses Role.Application.Security.Interfaces, so a change to Role.Application.Security.Interfaces can break Role.Transport.Command.Role, while a change to Role.Transport.Command.Role can't break Role.Application.Security.Interfaces.
- Position
- Below the diagonal: Role.Transport.Command.Role uses a module listed above it, which is the healthy direction.
36→31 Role.Transport.Command.Role uses Role.Application.Resource✕
- Connections
- 1 pair of types, where a type in Role.Transport.Command.Role uses a type in Role.Application.Resource.
- The types involved
App.Role.Transport.Command.Role.CreateRolesWithUserGroupsCommand→App.Role.Application.Resource.RoleResource
- Direction
- Role.Transport.Command.Role uses Role.Application.Resource, so a change to Role.Application.Resource can break Role.Transport.Command.Role, while a change to Role.Transport.Command.Role can't break Role.Application.Resource.
- Position
- Below the diagonal: Role.Transport.Command.Role uses a module listed above it, which is the healthy direction.
36→32 Role.Transport.Command.Role uses User.Application.Resource✕
- Connections
- 1 pair of types, where a type in Role.Transport.Command.Role uses a type in User.Application.Resource.
- The types involved
App.Role.Transport.Command.Role.CreateRolesWithUserGroupsCommand→App.User.Application.Resource.UserGroupResource
- Direction
- Role.Transport.Command.Role uses User.Application.Resource, so a change to User.Application.Resource can break Role.Transport.Command.Role, while a change to Role.Transport.Command.Role can't break User.Application.Resource.
- Position
- Below the diagonal: Role.Transport.Command.Role uses a module listed above it, which is the healthy direction.
37→6 User.Transport.Form.Type.Console uses Role.Application.Security.Interfaces✕
- Connections
- 1 pair of types, where a type in User.Transport.Form.Type.Console uses a type in Role.Application.Security.Interfaces.
- The types involved
App.User.Transport.Form.Type.Console.UserGroupType→App.Role.Application.Security.Interfaces.RolesServiceInterface
- Direction
- User.Transport.Form.Type.Console uses Role.Application.Security.Interfaces, so a change to Role.Application.Security.Interfaces can break User.Transport.Form.Type.Console, while a change to User.Transport.Form.Type.Console can't break Role.Application.Security.Interfaces.
- Position
- Below the diagonal: User.Transport.Form.Type.Console uses a module listed above it, which is the healthy direction.
37→23 User.Transport.Form.Type.Console uses Tool.Application.Service✕
- Connections
- 1 pair of types, where a type in User.Transport.Form.Type.Console uses a type in Tool.Application.Service.
- The types involved
App.User.Transport.Form.Type.Console.UserType→App.Tool.Application.Service.LocalizationService
- Direction
- User.Transport.Form.Type.Console uses Tool.Application.Service, so a change to Tool.Application.Service can break User.Transport.Form.Type.Console, while a change to User.Transport.Form.Type.Console can't break Tool.Application.Service.
- Position
- Below the diagonal: User.Transport.Form.Type.Console uses a module listed above it, which is the healthy direction.
37→31 User.Transport.Form.Type.Console uses Role.Application.Resource✕
- Connections
- 1 pair of types, where a type in User.Transport.Form.Type.Console uses a type in Role.Application.Resource.
- The types involved
App.User.Transport.Form.Type.Console.UserGroupType→App.Role.Application.Resource.RoleResource
- Direction
- User.Transport.Form.Type.Console uses Role.Application.Resource, so a change to Role.Application.Resource can break User.Transport.Form.Type.Console, while a change to User.Transport.Form.Type.Console can't break Role.Application.Resource.
- Position
- Below the diagonal: User.Transport.Form.Type.Console uses a module listed above it, which is the healthy direction.
37→32 User.Transport.Form.Type.Console uses User.Application.Resource✕
- Connections
- 1 pair of types, where a type in User.Transport.Form.Type.Console uses a type in User.Application.Resource.
- The types involved
App.User.Transport.Form.Type.Console.UserType→App.User.Application.Resource.UserGroupResource
- Direction
- User.Transport.Form.Type.Console uses User.Application.Resource, so a change to User.Application.Resource can break User.Transport.Form.Type.Console, while a change to User.Transport.Form.Type.Console can't break User.Application.Resource.
- Position
- Below the diagonal: User.Transport.Form.Type.Console uses a module listed above it, which is the healthy direction.
38→10 Log.Application.Service uses Log.Domain.Enum✕
- Connections
- 1 pair of types, where a type in Log.Application.Service uses a type in Log.Domain.Enum.
- The types involved
App.Log.Application.Service.LoginLoggerService→App.Log.Domain.Enum.LogLogin
- Direction
- Log.Application.Service uses Log.Domain.Enum, so a change to Log.Domain.Enum can break Log.Application.Service, while a change to Log.Application.Service can't break Log.Domain.Enum.
- Position
- Below the diagonal: Log.Application.Service uses a module listed above it, which is the healthy direction.
38→19 Log.Application.Service uses User.Domain.Entity✕
- Connections
- 1 pair of types, where a type in Log.Application.Service uses a type in User.Domain.Entity.
- The types involved
App.Log.Application.Service.LoginLoggerService→App.User.Domain.Entity.User
- Direction
- Log.Application.Service uses User.Domain.Entity, so a change to User.Domain.Entity can break Log.Application.Service, while a change to Log.Application.Service can't break User.Domain.Entity.
- Position
- Below the diagonal: Log.Application.Service uses a module listed above it, which is the healthy direction.
38→26 Log.Application.Service uses ApiKey.Application.Resource✕
- Connections
- 1 pair of types, where a type in Log.Application.Service uses a type in ApiKey.Application.Resource.
- The types involved
App.Log.Application.Service.RequestLoggerService→App.ApiKey.Application.Resource.ApiKeyResource
- Direction
- Log.Application.Service uses ApiKey.Application.Resource, so a change to ApiKey.Application.Resource can break Log.Application.Service, while a change to Log.Application.Service can't break ApiKey.Application.Resource.
- Position
- Below the diagonal: Log.Application.Service uses a module listed above it, which is the healthy direction.
38→29 Log.Application.Service uses Log.Application.Resource✕
- Connections
- 2 pairs of types, where a type in Log.Application.Service uses a type in Log.Application.Resource.
- The types involved
App.Log.Application.Service.LoginLoggerService→App.Log.Application.Resource.LogLoginResourceApp.Log.Application.Service.RequestLoggerService→App.Log.Application.Resource.LogRequestResource
- Direction
- Log.Application.Service uses Log.Application.Resource, so a change to Log.Application.Resource can break Log.Application.Service, while a change to Log.Application.Service can't break Log.Application.Resource.
- Position
- Below the diagonal: Log.Application.Service uses a module listed above it, which is the healthy direction.
38→32 Log.Application.Service uses User.Application.Resource✕
- Connections
- 1 pair of types, where a type in Log.Application.Service uses a type in User.Application.Resource.
- The types involved
App.Log.Application.Service.RequestLoggerService→App.User.Application.Resource.UserResource
- Direction
- Log.Application.Service uses User.Application.Resource, so a change to User.Application.Resource can break Log.Application.Service, while a change to Log.Application.Service can't break User.Application.Resource.
- Position
- Below the diagonal: Log.Application.Service uses a module listed above it, which is the healthy direction.
38→35 Log.Application.Service uses Log.Application.Service.Interfaces✕
- Connections
- 2 pairs of types, where a type in Log.Application.Service uses a type in Log.Application.Service.Interfaces.
- The types involved
App.Log.Application.Service.LoginLoggerService→App.Log.Application.Service.Interfaces.LoginLoggerServiceInterfaceApp.Log.Application.Service.RequestLoggerService→App.Log.Application.Service.Interfaces.RequestLoggerServiceInterface
- Direction
- Log.Application.Service uses Log.Application.Service.Interfaces, so a change to Log.Application.Service.Interfaces can break Log.Application.Service, while a change to Log.Application.Service can't break Log.Application.Service.Interfaces.
- Position
- Below the diagonal: Log.Application.Service uses a module listed above it, which is the healthy direction.
39→8 User.Application.Security uses General.Domain.Enum✕
- Connections
- 2 pairs of types, where a type in User.Application.Security uses a type in General.Domain.Enum.
- The types involved
App.User.Application.Security.SecurityUser→App.General.Domain.Enum.LanguageApp.User.Application.Security.SecurityUser→App.General.Domain.Enum.Locale
- Direction
- User.Application.Security uses General.Domain.Enum, so a change to General.Domain.Enum can break User.Application.Security, while a change to User.Application.Security can't break General.Domain.Enum.
- Position
- Below the diagonal: User.Application.Security uses a module listed above it, which is the healthy direction.
39→19 User.Application.Security uses User.Domain.Entity✕
- Connections
- 2 pairs of types, where a type in User.Application.Security uses a type in User.Domain.Entity.
- The types involved
App.User.Application.Security.SecurityUser→App.User.Domain.Entity.UserApp.User.Application.Security.UserTypeIdentification→App.User.Domain.Entity.User
- Direction
- User.Application.Security uses User.Domain.Entity, so a change to User.Domain.Entity can break User.Application.Security, while a change to User.Application.Security can't break User.Domain.Entity.
- Position
- Below the diagonal: User.Application.Security uses a module listed above it, which is the healthy direction.
39→20 User.Application.Security uses ApiKey.Domain.Entity✕
- Connections
- 1 pair of types, where a type in User.Application.Security uses a type in ApiKey.Domain.Entity.
- The types involved
App.User.Application.Security.UserTypeIdentification→App.ApiKey.Domain.Entity.ApiKey
- Direction
- User.Application.Security uses ApiKey.Domain.Entity, so a change to ApiKey.Domain.Entity can break User.Application.Security, while a change to User.Application.Security can't break ApiKey.Domain.Entity.
- Position
- Below the diagonal: User.Application.Security uses a module listed above it, which is the healthy direction.
39→25 User.Application.Security uses User.Domain.Repository.Interfaces✕
- Connections
- 1 pair of types, where a type in User.Application.Security uses a type in User.Domain.Repository.Interfaces.
- The types involved
App.User.Application.Security.UserTypeIdentification→App.User.Domain.Repository.Interfaces.UserRepositoryInterface
- Direction
- User.Application.Security uses User.Domain.Repository.Interfaces, so a change to User.Domain.Repository.Interfaces can break User.Application.Security, while a change to User.Application.Security can't break User.Domain.Repository.Interfaces.
- Position
- Below the diagonal: User.Application.Security uses a module listed above it, which is the healthy direction.
39→27 User.Application.Security uses ApiKey.Application.Security✕
- Connections
- 1 pair of types, where a type in User.Application.Security uses a type in ApiKey.Application.Security.
- The types involved
App.User.Application.Security.UserTypeIdentification→App.ApiKey.Application.Security.ApiKeyUser
- Direction
- User.Application.Security uses ApiKey.Application.Security, so a change to ApiKey.Application.Security can break User.Application.Security, while a change to User.Application.Security can't break ApiKey.Application.Security.
- Position
- Below the diagonal: User.Application.Security uses a module listed above it, which is the healthy direction.
39→33 User.Application.Security uses ApiKey.Application.Security.Provider✕
- Connections
- 1 pair of types, where a type in User.Application.Security uses a type in ApiKey.Application.Security.Provider.
- The types involved
App.User.Application.Security.UserTypeIdentification→App.ApiKey.Application.Security.Provider.ApiKeyUserProvider
- Direction
- User.Application.Security uses ApiKey.Application.Security.Provider, so a change to ApiKey.Application.Security.Provider can break User.Application.Security, while a change to User.Application.Security can't break ApiKey.Application.Security.Provider.
- Position
- Below the diagonal: User.Application.Security uses a module listed above it, which is the healthy direction.
40→19 User.Transport.EventSubscriber uses User.Domain.Entity✕
- Connections
- 1 pair of types, where a type in User.Transport.EventSubscriber uses a type in User.Domain.Entity.
- The types involved
App.User.Transport.EventSubscriber.LockedUserSubscriber→App.User.Domain.Entity.User
- Direction
- User.Transport.EventSubscriber uses User.Domain.Entity, so a change to User.Domain.Entity can break User.Transport.EventSubscriber, while a change to User.Transport.EventSubscriber can't break User.Domain.Entity.
- Position
- Below the diagonal: User.Transport.EventSubscriber uses a module listed above it, which is the healthy direction.
40→25 User.Transport.EventSubscriber uses User.Domain.Repository.Interfaces✕
- Connections
- 3 pairs of types, where a type in User.Transport.EventSubscriber uses a type in User.Domain.Repository.Interfaces.
- The types involved
App.User.Transport.EventSubscriber.AuthenticationFailureSubscriber→App.User.Domain.Repository.Interfaces.UserRepositoryInterfaceApp.User.Transport.EventSubscriber.AuthenticationSuccessSubscriber→App.User.Domain.Repository.Interfaces.UserRepositoryInterfaceApp.User.Transport.EventSubscriber.LockedUserSubscriber→App.User.Domain.Repository.Interfaces.UserRepositoryInterface
- Direction
- User.Transport.EventSubscriber uses User.Domain.Repository.Interfaces, so a change to User.Domain.Repository.Interfaces can break User.Transport.EventSubscriber, while a change to User.Transport.EventSubscriber can't break User.Domain.Repository.Interfaces.
- Position
- Below the diagonal: User.Transport.EventSubscriber uses a module listed above it, which is the healthy direction.
40→29 User.Transport.EventSubscriber uses Log.Application.Resource✕
- Connections
- 1 pair of types, where a type in User.Transport.EventSubscriber uses a type in Log.Application.Resource.
- The types involved
App.User.Transport.EventSubscriber.LockedUserSubscriber→App.Log.Application.Resource.LogLoginFailureResource
- Direction
- User.Transport.EventSubscriber uses Log.Application.Resource, so a change to Log.Application.Resource can break User.Transport.EventSubscriber, while a change to User.Transport.EventSubscriber can't break Log.Application.Resource.
- Position
- Below the diagonal: User.Transport.EventSubscriber uses a module listed above it, which is the healthy direction.
40→35 User.Transport.EventSubscriber uses Log.Application.Service.Interfaces✕
- Connections
- 2 pairs of types, where a type in User.Transport.EventSubscriber uses a type in Log.Application.Service.Interfaces.
- The types involved
App.User.Transport.EventSubscriber.AuthenticationFailureSubscriber→App.Log.Application.Service.Interfaces.LoginLoggerServiceInterfaceApp.User.Transport.EventSubscriber.AuthenticationSuccessSubscriber→App.Log.Application.Service.Interfaces.LoginLoggerServiceInterface
- Direction
- User.Transport.EventSubscriber uses Log.Application.Service.Interfaces, so a change to Log.Application.Service.Interfaces can break User.Transport.EventSubscriber, while a change to User.Transport.EventSubscriber can't break Log.Application.Service.Interfaces.
- Position
- Below the diagonal: User.Transport.EventSubscriber uses a module listed above it, which is the healthy direction.
40→39 User.Transport.EventSubscriber uses User.Application.Security✕
- Connections
- 1 pair of types, where a type in User.Transport.EventSubscriber uses a type in User.Application.Security.
- The types involved
App.User.Transport.EventSubscriber.DoctrineExtensionSubscriber→App.User.Application.Security.UserTypeIdentification
- Direction
- User.Transport.EventSubscriber uses User.Application.Security, so a change to User.Application.Security can break User.Transport.EventSubscriber, while a change to User.Transport.EventSubscriber can't break User.Application.Security.
- Position
- Below the diagonal: User.Transport.EventSubscriber 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 — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 18 | High / Critical |
| A07:2025 — Authentication Failures | 13 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | High / Critical |
| A05:2025 — Injection | 4 | High / Critical |
Roadmap
Top priorities: Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge; Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +10.9 pts | Medium | Page structure |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +10.4 pts | Medium | A11y enforcement |
| Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. | +2.4 pts | Low | REDACTED Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.1 pts | Low | ADR Quality |
| Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. | +1.1 pts | Low | Secrets (history) |
| Resolve the 83 Orphaned file finding(s) in Knowledge Freshness — start with User.php (2), ApiKey.php (2), RepositoryHelper.php. | +2.1 pts | Medium | Knowledge Freshness |
| Resolve the 1 Banned license finding(s) in License Compliance. | +0.9 pts | Low | License Compliance |
| Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, HashiCorp Vault — not only APP_KEY in REDACTED) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps. | +1.6 pts | Medium | Data Protection |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 6.5 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| src/ApiKey/Domain/Entity/ApiKey.php | 7.0 | Mixed | Code Duplication: Duplicated block (6 lines × 3) |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| tests/Utils/PhpUnitUtil.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/General/Transport/Rest/RequestHandler.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/General/Infrastructure/Service/ElasticsearchService.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 66 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 66 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, 148 of 203 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`phpunit -c phpunit.xml.dist --coverage-html reports/coverage…`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.php), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 85 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 84 of the 405 production source files in this repository: 320 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D23 Boundary Type-Coupling — 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. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — 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. `(repository root)` (26165 LoC, 399 module-visible types across 163 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D31 IaC & Container Security — 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. Docker/elasticsearch/REDACTED, REDACTED carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 8 of 10 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/ApiKey/Application/Security/ApiKeyUser.php`, `src/ApiKey/Application/Security/Authenticator/ApiKeyAuthenticator.php`, `src/ApiKey/Application/Security/Provider/ApiKeyUserProvider.php`, `src/ApiKey/Application/Service/Crypt/OpenSslCryptApiKeyService.php`, `src/ApiKey/Domain/Entity/ApiKey.php`, … (+135 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Symfony DependencyInjection, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: docker.elastic.co/elasticsearch/elasticsearch:7.10.1: failed to resolve source metadata for docker.elastic.co/elasticsearch/elasticsearch:7.10.1: failed to do request: Head "https://docker.elastic.co/v2/elasticsearch/elasticsearch/manifests/7.10.1": Forbidden; runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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 REDACTED Scanning: REDACTED 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.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- 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.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
13 duplicated block group(s) detected. 1 of the 13 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with BinToUuidOT.php, UniqueEmailValidator.php, LoadApiKeyData.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ApiKey.php, UniqueEmail.php, LanguageValidator.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with CreateDateDimensionEntitiesCommand.php, ApiKeyType.php. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
2 of 72 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with ApiKey.php, RestSmallResource.php. — One of this dimension's main actionable groups (2 warning-level).
D9 · Test Distribution
9 test methods: 9 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 9 tests.
D12 · Dependency Hygiene
36 outdated, 0 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
5 secret(s) detected.
What to do
- Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
D14 · License Compliance
1 of 121 locked Composer package(s) use a banned license. Licences were read from this repository's REDACTED, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 9 package(s) under `packages-dev` are not installed for a consumer and are excluded.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
3 deducted task-comment markers across 26341 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with PhpUnitUtil.php, RequestHandler.php, ElasticsearchService.php. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 12 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
22 domain type(s) cross context boundaries across 6 contexts; they are measured and withheld (not published, not scored). Contexts: ApiKey, DateDimension, Log, Role, Tool, User.
D27 · Navigability
22 % of calls cross a namespace and 7 % go through an interface, but 72 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 3 high, 0 medium, 1 low. 3 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 142 file(s) — `src/ApiKey/Application/Security/ApiKeyUser.php` (line 23, line 24, line 29), `src/ApiKey/Application/Security/Authenticator/ApiKeyAuthenticator.php` (line 29), `src/ApiKey/Application/Security/Provider/ApiKeyUserProvider.php` (line 30, line 31, line 32, …), `src/ApiKey/Application/Service/Crypt/OpenSslCryptApiKeyService.php` (line 19, line 20), `src/ApiKey/Domain/Entity/ApiKey.php` (lines 50–52), … (+137 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
- No action in Static Analysis (SAST) — all 3 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 (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
18 finding(s): 0 critical, 7 high, 7 medium, 4 low.
What to do
- Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 4 Low IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
D34 · Knowledge Freshness
84 of 85 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is public/check.php. Counted over 85 of the 405 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 83 Orphaned file finding(s) in Knowledge Freshness — start with User.php (2), ApiKey.php (2), RepositoryHelper.php. — One of this dimension's main actionable groups (83 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with check.php. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 49 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
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — templates/base.html.twig:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — templates/base.html.twig:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 7 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, HashiCorp Vault — not only APP_KEY in REDACTED) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps.
- Enforce HTTPS (URL::forceScheme('https') / URL::forceHttps() in Laravel, or requires_channel: https / route schemes in Symfony) so data in transit is always encrypted.
C2 · Access Controls
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 scheduled purge / cleanup job (an Eloquent model's prunable() for model:prune, or a command that deletes rows past their retention — PruneOld… / PurgeExpired…).
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.
DM1 · Aggregate boundaries
- `LogLogin` references the aggregate root `User` directly (via `user`) — hold its `UserId` instead.
- `LogLoginFailure` references the aggregate root `User` directly (via `user`) — hold its `UserId` instead.
- `LogRequest` references the aggregate root `User` directly (via `user`) — hold its `UserId` instead.
- `LogRequest` references the aggregate root `ApiKey` directly (via `apiKey`) — hold its `ApiKeyId` instead.
- `UserGroup` references the aggregate root `Role` directly (via `role`) — hold its `RoleId` instead.
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `Role`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Role` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Role/Domain/Entity/Role.php:61
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `DateDimension` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/DateDimension/Domain/Entity/DateDimension.php:26
- `LogLoginFailure` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Log/Domain/Entity/LogLoginFailure.php:23
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
M1 · Documentation (README)
What to do
- Describe the projects a newcomer cannot place from the root README: 10 of 10 have no README of their own, in their folder or in their family's project (`tools/01_phpunit`, `tools/02_phpstan`, `tools/03_ecs`, `tools/04_php-coveralls`, `tools/05_phpinsights` and 5 more).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (opentelemetry-php) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
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
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
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
S1 · Web-Security Posture
- `https://cdn.jsdelivr.net/npm/idiomorph` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup. — templates/base.html.twig:17
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — docker/staging/nginx.conf:6
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/General/Application/Decorator/StopwatchDecorator.php:54
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 89% | Strong | Solid. |
| Architecture | 90% | Exemplary | Strongest area. |
| Maturity | 58% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 53% | Adequate — gated by D28, D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 76% | Adequate — gated by DM1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 32% | Weak — gated by AC3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- 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 — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, a change-history library on the models — spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable, venturecraft/revisionable, Gedmo Loggable — or an Eloquent model event, observer or Doctrine listener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 59 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AC6 Visual & motion safety — No styled element found in the parsed markup — AC6 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: docker.elastic.co/elasticsearch/elasticsearch:7.10.1: failed to resolve source metadata for docker.elastic.co/elasticsearch/elasticsearch:7.10.1: failed to do request: Head "https://docker.elastic.co/v2/elasticsearch/elasticsearch/manifests/7.10.1": Forbidden; 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.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; PHP not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 140 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the PHP source (service entry point: src/User/Transport/Controller/Api/V1/UserGroup/AttachUserController.php:45 (#[Route())
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.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.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- 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.
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 31 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Aggregate holds a reference to another aggregate: LogLogin.user
- Aggregate holds a reference to another aggregate: LogLoginFailure.user
- Aggregate holds a reference to another aggregate: LogRequest.user
- Aggregate holds a reference to another aggregate: LogRequest.apiKey
- Aggregate holds a reference to another aggregate: UserGroup.role
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang templates/base.html.twig:2
- Banned license: matomo/device-detector
Serious — 35 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment tests/Utils/PhpUnitUtil.php:273
- TodoComment src/General/Transport/Rest/RequestHandler.php:142
- TodoComment src/General/Infrastructure/Service/ElasticsearchService.php:120
- Duplicated block (9 lines × 2) src/General/Infrastructure/DQL/BinToUuidOT.php:25
- Duplicated block (9 lines × 2) src/User/Application/Validator/Constraints/UniqueEmailValidator.php:36
- Duplicated block (9 lines × 2) src/ApiKey/Infrastructure/DataFixtures/ORM/LoadApiKeyData.php:54
- Duplicated block (7 lines × 2) src/ApiKey/Application/DTO/ApiKey/ApiKey.php:119
- Duplicated block (7 lines × 2) src/User/Application/Validator/Constraints/UniqueEmail.php:40
- Duplicated block (7 lines × 2) src/Tool/Application/Validator/Constraints/LanguageValidator.php:30
- Duplicated block (14 lines × 2) src/DateDimension/Transport/Command/Utils/CreateDateDimensionEntitiesCommand.php:123
- Duplicated block (14 lines × 2) src/ApiKey/Transport/Form/Type/Console/ApiKeyType.php:60
- Low cohesion: ApiKey (LCOM4 9) src/ApiKey/Domain/Entity/ApiKey.php:36
- Low cohesion: RestSmallResource (LCOM4 4) src/General/Application/Rest/RestSmallResource.php:14
- Anemic entity: DateDimension src/DateDimension/Domain/Entity/DateDimension.php:26
- Anemic entity: LogLoginFailure src/Log/Domain/Entity/LogLoginFailure.php:23
- Page without a main landmark templates/base.html.twig:2
- Accessibility enforcement below the top rung
- REDACTED
- REDACTED
- Duplicated block (11–13 lines × 2) src/General/Transport/Rest/Traits/Methods/CountMethod.php:32
- Duplicated block (11 lines × 2) src/User/Transport/Command/User/ListUserGroupsCommand.php:56
- Duplicated block (6 lines × 3) src/ApiKey/Domain/Entity/ApiKey.php:294
- Duplicated block (8 lines × 2) src/Log/Infrastructure/Repository/LogLoginRepository.php:46
- Duplicated block (12 lines × 2) src/User/Transport/Command/User/EditUserCommand.php:73
- Constructible in an invalid state: Role src/Role/Domain/Entity/Role.php:61
- Coverage collected but not gated
- Third-party script without Subresource Integrity templates/base.html.twig:17
- Swallowed exception (caught, then discarded) src/General/Application/Decorator/StopwatchDecorator.php:54
Minor — 101 finding(s)
- Orphaned file src/General/Infrastructure/Rest/RepositoryHelper.php:1
- Orphaned file src/Log/Domain/Entity/Traits/LogRequestProcessRequestTrait.php:1
- Orphaned file src/General/Transport/Rest/RequestHandler.php:1
- Orphaned file src/Tool/Transport/Command/Utils/CheckDependencies.php:1
- Orphaned file src/User/Domain/Entity/User.php:1
- Orphaned file src/General/Domain/Repository/Interfaces/BaseRepositoryInterface.php:1
- Orphaned file src/Log/Domain/Entity/LogLogin.php:1
- Orphaned file src/ApiKey/Domain/Entity/ApiKey.php:1
- Orphaned file src/General/Infrastructure/Repository/Traits/RepositoryMethodsTrait.php:1
- Orphaned file src/General/Transport/EventSubscriber/ExceptionSubscriber.php:1
- Orphaned file src/User/Transport/Form/Type/Console/UserType.php:1
- Orphaned file src/User/Application/DTO/User/User.php:1
- Orphaned file src/General/Infrastructure/Repository/BaseRepository.php:1
- Orphaned file src/DateDimension/Domain/Entity/DateDimension.php:1
- Orphaned file src/General/Transport/Rest/ResponseHandler.php:1
- Orphaned file src/DateDimension/Transport/Command/Utils/CreateDateDimensionEntitiesCommand.php:1
- Orphaned file src/User/Domain/Entity/UserGroup.php:1
- Orphaned file src/General/Infrastructure/Rest/SearchTerm.php:1
- Orphaned file src/General/Transport/Rest/Traits/RestMethodHelper.php:1
- Orphaned file src/User/Transport/Command/User/UserHelper.php:1
- Orphaned file src/General/Application/Rest/Traits/RestResourceBaseMethods.php:1
- Orphaned file src/General/Application/Resource/ResourceCollection.php:1
- Orphaned file src/User/Transport/Command/User/CreateUserCommand.php:1
- Orphaned file src/General/Application/DTO/RestDto.php:1
- Orphaned file src/Log/Domain/Entity/LogRequest.php:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Partial data-retention evidence
- No ADRs found
- REDACTED
- REDACTED
- Concentrated knowledge decay
- Most significant orphaned file public/check.php:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No rollback/health safety
- No changelog
- No security response headers detected docker/staging/nginx.conf:6
- Duplicated predicate src/User/Application/Validator/Constraints/UniqueEmailValidator.php:37
Minor — 36 finding(s)
- Outdated: doctrine/doctrine-bundle
- Outdated: doctrine/doctrine-migrations-bundle
- Outdated: dukecity/command-scheduler-bundle
- Outdated: gedmo/doctrine-extensions
- Outdated: matomo/device-detector
- Outdated: symfony/amqp-messenger
- Outdated: symfony/config
- Outdated: symfony/console
- Outdated: symfony/doctrine-bridge
- Outdated: symfony/doctrine-messenger
- Outdated: symfony/dotenv
- Outdated: symfony/expression-language
- Outdated: symfony/flex
- Outdated: symfony/form
- Outdated: symfony/framework-bundle
- Outdated: symfony/http-client
- Outdated: symfony/intl
- Outdated: symfony/mailer
- Outdated: symfony/messenger
- Outdated: symfony/mime
- Outdated: symfony/monolog-bundle
- Outdated: symfony/notifier
- Outdated: symfony/process
- Outdated: symfony/property-access
- Outdated: symfony/property-info
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-01d9c07913844b18b64e611c9172b582/history.json --exit-code 0 --source . | 5 | 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-01d9c07913844b18b64e611c9172b582/tree.json --exit-code 0 --source . | 4 | 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 . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 18 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 140 file(s) — `src/ApiKey/Application/Security/ApiKeyUser.php`, `src/ApiKey/Application/Security/Authenticator/ApiKeyAuthenticator.php`, `src/ApiKey/Application/Security/Provider/ApiKeyUserProvider.php`, `src/ApiKey/Application/Service/Crypt/OpenSslCryptApiKeyService.php`, `src/ApiKey/Domain/Entity/ApiKey.php`, … (+135 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |