Executive summary
BenGorUser/User falls short of our standard for a preview release because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 55 out of 100 and is rated Adequate, and it has no critical findings.
Production Readiness, at 43, is the weakest lens and counts most in the score. The best first step is having someone learn and document the nine files no active contributor knows, worth about 8 points. Moving the pipeline to a build service that still runs would lift Production Readiness itself, also worth about 8. Raising Production Readiness to 62 would lift the score to about 62.
Most of the ten serious findings are in Code Health.
The product code is 6,195 lines, about €13,000 to rebuild.
If Production Readiness rose from 43 to 62, the lowest score rated Strong, the score would rise from 55 to about 62.
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,300 to €21,000, for 71 to 225 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,195 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Application.DataTransformer | 2 Domain.Model.Exception | 3 Infrastructure.CommandBus | 4 Domain.Model.Event | 5 Domain.Model | 6 Application.Command.ChangePassword | 7 Application.Command.Enable | 8 Application.Command.GrantRole | 9 Application.Command.Invite | 10 Application.Command.LogIn | 11 Application.Command.LogOut | 12 Application.Command.PurgeOutdatedTokens | 13 Application.Command.Remove | 14 Application.Command.RequestRememberPassword | 15 Application.Command.RevokeRole | 16 Application.Command.SignUp | 17 Application.Query | 18 Domain.Event | 19 Infrastructure.Domain.Model | 20 Infrastructure.Routing | 21 Infrastructure.Security | 22 Infrastructure.Persistence |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Application.DataTransformer | ||||||||||||||||||||||
| 2 Domain.Model.Exception | ||||||||||||||||||||||
| 3 Infrastructure.CommandBus | ||||||||||||||||||||||
| 4 Domain.Model.Event | 24 | |||||||||||||||||||||
| 5 Domain.Model | 1 | |||||||||||||||||||||
| 6 Application.Command.ChangePassword | 6 | |||||||||||||||||||||
| 7 Application.Command.Enable | 1 | |||||||||||||||||||||
| 8 Application.Command.GrantRole | 1 | |||||||||||||||||||||
| 9 Application.Command.Invite | 3 | |||||||||||||||||||||
| 10 Application.Command.LogIn | 2 | |||||||||||||||||||||
| 11 Application.Command.LogOut | 1 | |||||||||||||||||||||
| 12 Application.Command.PurgeOutdatedTokens | 2 | |||||||||||||||||||||
| 13 Application.Command.Remove | 1 | |||||||||||||||||||||
| 14 Application.Command.RequestRememberPassword | 1 | |||||||||||||||||||||
| 15 Application.Command.RevokeRole | 1 | |||||||||||||||||||||
| 16 Application.Command.SignUp | 8 | |||||||||||||||||||||
| 17 Application.Query | 4 | 4 | ||||||||||||||||||||
| 18 Domain.Event | 4 | 9 | ||||||||||||||||||||
| 19 Infrastructure.Domain.Model | 1 | 7 | ||||||||||||||||||||
| 20 Infrastructure.Routing | 1 | |||||||||||||||||||||
| 21 Infrastructure.Security | 2 | |||||||||||||||||||||
| 22 Infrastructure.Persistence | 10 | 2 |
4→5 Domain.Model.Event uses Domain.Model part of a loop✕
- Connections
- 24 pairs of types, where a type in Domain.Model.Event uses a type in Domain.Model.
- The types involved
BenGorUser.User.Domain.Model.Event.UserEnabled→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Domain.Model.Event.UserEnabled→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Domain.Model.Event.UserInvitationTokenRegenerated→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Domain.Model.Event.UserInvitationTokenRegenerated→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Domain.Model.Event.UserInvitationTokenRegenerated→BenGorUser.User.Domain.Model.UserTokenBenGorUser.User.Domain.Model.Event.UserInvited→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Domain.Model.Event.UserInvited→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Domain.Model.Event.UserInvited→BenGorUser.User.Domain.Model.UserTokenBenGorUser.User.Domain.Model.Event.UserLoggedIn→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Domain.Model.Event.UserLoggedIn→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Domain.Model.Event.UserLoggedOut→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Domain.Model.Event.UserLoggedOut→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Domain.Model.Event.UserRegistered→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Domain.Model.Event.UserRegistered→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Domain.Model.Event.UserRegistered→BenGorUser.User.Domain.Model.UserTokenBenGorUser.User.Domain.Model.Event.UserRememberPasswordRequested→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Domain.Model.Event.UserRememberPasswordRequested→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Domain.Model.Event.UserRememberPasswordRequested→BenGorUser.User.Domain.Model.UserTokenBenGorUser.User.Domain.Model.Event.UserRoleGranted→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Domain.Model.Event.UserRoleGranted→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Domain.Model.Event.UserRoleGranted→BenGorUser.User.Domain.Model.UserRoleBenGorUser.User.Domain.Model.Event.UserRoleRevoked→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Domain.Model.Event.UserRoleRevoked→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Domain.Model.Event.UserRoleRevoked→BenGorUser.User.Domain.Model.UserRole
- Direction
- Domain.Model.Event uses Domain.Model, so a change to Domain.Model can break Domain.Model.Event, while a change to Domain.Model.Event can't break Domain.Model.
- 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.
5→4 Domain.Model uses Domain.Model.Event✕
- Connections
- 1 pair of types, where a type in Domain.Model uses a type in Domain.Model.Event.
- The types involved
BenGorUser.User.Domain.Model.UserAggregateRoot→BenGorUser.User.Domain.Model.Event.UserEvent
- Direction
- Domain.Model uses Domain.Model.Event, so a change to Domain.Model.Event can break Domain.Model, while a change to Domain.Model can't break Domain.Model.Event.
- Position
- Below the diagonal: Domain.Model uses a module listed above it, which is the healthy direction.
6→5 Application.Command.ChangePassword uses Domain.Model✕
- Connections
- 6 pairs of types, where a type in Application.Command.ChangePassword uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.ChangePassword.ByRequestRememberPasswordChangeUserPasswordHandler→BenGorUser.User.Domain.Model.UserPasswordEncoderBenGorUser.User.Application.Command.ChangePassword.ByRequestRememberPasswordChangeUserPasswordHandler→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Application.Command.ChangePassword.ChangeUserPasswordHandler→BenGorUser.User.Domain.Model.UserPasswordEncoderBenGorUser.User.Application.Command.ChangePassword.ChangeUserPasswordHandler→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Application.Command.ChangePassword.WithoutOldPasswordChangeUserPasswordHandler→BenGorUser.User.Domain.Model.UserPasswordEncoderBenGorUser.User.Application.Command.ChangePassword.WithoutOldPasswordChangeUserPasswordHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.ChangePassword uses Domain.Model, so a change to Domain.Model can break Application.Command.ChangePassword, while a change to Application.Command.ChangePassword can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.ChangePassword uses a module listed above it, which is the healthy direction.
7→5 Application.Command.Enable uses Domain.Model✕
- Connections
- 1 pair of types, where a type in Application.Command.Enable uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.Enable.EnableUserHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.Enable uses Domain.Model, so a change to Domain.Model can break Application.Command.Enable, while a change to Application.Command.Enable can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.Enable uses a module listed above it, which is the healthy direction.
8→5 Application.Command.GrantRole uses Domain.Model✕
- Connections
- 1 pair of types, where a type in Application.Command.GrantRole uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.GrantRole.GrantUserRoleHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.GrantRole uses Domain.Model, so a change to Domain.Model can break Application.Command.GrantRole, while a change to Application.Command.GrantRole can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.GrantRole uses a module listed above it, which is the healthy direction.
9→5 Application.Command.Invite uses Domain.Model✕
- Connections
- 3 pairs of types, where a type in Application.Command.Invite uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.Invite.InviteUserHandler→BenGorUser.User.Domain.Model.UserFactoryInviteBenGorUser.User.Application.Command.Invite.InviteUserHandler→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Application.Command.Invite.ResendInvitationUserHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.Invite uses Domain.Model, so a change to Domain.Model can break Application.Command.Invite, while a change to Application.Command.Invite can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.Invite uses a module listed above it, which is the healthy direction.
10→5 Application.Command.LogIn uses Domain.Model✕
- Connections
- 2 pairs of types, where a type in Application.Command.LogIn uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.LogIn.LogInUserHandler→BenGorUser.User.Domain.Model.UserPasswordEncoderBenGorUser.User.Application.Command.LogIn.LogInUserHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.LogIn uses Domain.Model, so a change to Domain.Model can break Application.Command.LogIn, while a change to Application.Command.LogIn can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.LogIn uses a module listed above it, which is the healthy direction.
11→5 Application.Command.LogOut uses Domain.Model✕
- Connections
- 1 pair of types, where a type in Application.Command.LogOut uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.LogOut.LogOutUserHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.LogOut uses Domain.Model, so a change to Domain.Model can break Application.Command.LogOut, while a change to Application.Command.LogOut can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.LogOut uses a module listed above it, which is the healthy direction.
12→5 Application.Command.PurgeOutdatedTokens uses Domain.Model✕
- Connections
- 2 pairs of types, where a type in Application.Command.PurgeOutdatedTokens uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.PurgeOutdatedTokens.PurgeOutdatedInvitationTokensUserHandler→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Application.Command.PurgeOutdatedTokens.PurgeOutdatedRememberPasswordTokensUserHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.PurgeOutdatedTokens uses Domain.Model, so a change to Domain.Model can break Application.Command.PurgeOutdatedTokens, while a change to Application.Command.PurgeOutdatedTokens can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.PurgeOutdatedTokens uses a module listed above it, which is the healthy direction.
13→5 Application.Command.Remove uses Domain.Model✕
- Connections
- 1 pair of types, where a type in Application.Command.Remove uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.Remove.RemoveUserHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.Remove uses Domain.Model, so a change to Domain.Model can break Application.Command.Remove, while a change to Application.Command.Remove can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.Remove uses a module listed above it, which is the healthy direction.
14→5 Application.Command.RequestRememberPassword uses Domain.Model✕
- Connections
- 1 pair of types, where a type in Application.Command.RequestRememberPassword uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.RequestRememberPassword.RequestRememberPasswordHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.RequestRememberPassword uses Domain.Model, so a change to Domain.Model can break Application.Command.RequestRememberPassword, while a change to Application.Command.RequestRememberPassword can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.RequestRememberPassword uses a module listed above it, which is the healthy direction.
15→5 Application.Command.RevokeRole uses Domain.Model✕
- Connections
- 1 pair of types, where a type in Application.Command.RevokeRole uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.RevokeRole.RevokeUserRoleHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.RevokeRole uses Domain.Model, so a change to Domain.Model can break Application.Command.RevokeRole, while a change to Application.Command.RevokeRole can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.RevokeRole uses a module listed above it, which is the healthy direction.
16→5 Application.Command.SignUp uses Domain.Model✕
- Connections
- 8 pairs of types, where a type in Application.Command.SignUp uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Command.SignUp.ByInvitationSignUpUserHandler→BenGorUser.User.Domain.Model.UserPasswordEncoderBenGorUser.User.Application.Command.SignUp.ByInvitationSignUpUserHandler→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Application.Command.SignUp.SignUpUserHandler→BenGorUser.User.Domain.Model.UserFactorySignUpBenGorUser.User.Application.Command.SignUp.SignUpUserHandler→BenGorUser.User.Domain.Model.UserPasswordEncoderBenGorUser.User.Application.Command.SignUp.SignUpUserHandler→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Application.Command.SignUp.WithConfirmationSignUpUserHandler→BenGorUser.User.Domain.Model.UserFactorySignUpBenGorUser.User.Application.Command.SignUp.WithConfirmationSignUpUserHandler→BenGorUser.User.Domain.Model.UserPasswordEncoderBenGorUser.User.Application.Command.SignUp.WithConfirmationSignUpUserHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Command.SignUp uses Domain.Model, so a change to Domain.Model can break Application.Command.SignUp, while a change to Application.Command.SignUp can't break Domain.Model.
- Position
- Below the diagonal: Application.Command.SignUp uses a module listed above it, which is the healthy direction.
17→1 Application.Query uses Application.DataTransformer✕
- Connections
- 4 pairs of types, where a type in Application.Query uses a type in Application.DataTransformer.
- The types involved
BenGorUser.User.Application.Query.UserOfEmailHandler→BenGorUser.User.Application.DataTransformer.UserDataTransformerBenGorUser.User.Application.Query.UserOfIdHandler→BenGorUser.User.Application.DataTransformer.UserDataTransformerBenGorUser.User.Application.Query.UserOfInvitationTokenHandler→BenGorUser.User.Application.DataTransformer.UserDataTransformerBenGorUser.User.Application.Query.UserOfRememberPasswordTokenHandler→BenGorUser.User.Application.DataTransformer.UserDataTransformer
- Direction
- Application.Query uses Application.DataTransformer, so a change to Application.DataTransformer can break Application.Query, while a change to Application.Query can't break Application.DataTransformer.
- Position
- Below the diagonal: Application.Query uses a module listed above it, which is the healthy direction.
17→5 Application.Query uses Domain.Model✕
- Connections
- 4 pairs of types, where a type in Application.Query uses a type in Domain.Model.
- The types involved
BenGorUser.User.Application.Query.UserOfEmailHandler→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Application.Query.UserOfIdHandler→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Application.Query.UserOfInvitationTokenHandler→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Application.Query.UserOfRememberPasswordTokenHandler→BenGorUser.User.Domain.Model.UserRepository
- Direction
- Application.Query uses Domain.Model, so a change to Domain.Model can break Application.Query, while a change to Application.Query can't break Domain.Model.
- Position
- Below the diagonal: Application.Query uses a module listed above it, which is the healthy direction.
18→4 Domain.Event uses Domain.Model.Event✕
- Connections
- 4 pairs of types, where a type in Domain.Event uses a type in Domain.Model.Event.
- The types involved
BenGorUser.User.Domain.Event.UserEventSubscriber→BenGorUser.User.Domain.Model.Event.UserEventBenGorUser.User.Domain.Event.UserInvitedMailerSubscriber→BenGorUser.User.Domain.Model.Event.UserEventBenGorUser.User.Domain.Event.UserRegisteredMailerSubscriber→BenGorUser.User.Domain.Model.Event.UserEventBenGorUser.User.Domain.Event.UserRememberPasswordRequestedMailerSubscriber→BenGorUser.User.Domain.Model.Event.UserEvent
- Direction
- Domain.Event uses Domain.Model.Event, so a change to Domain.Model.Event can break Domain.Event, while a change to Domain.Event can't break Domain.Model.Event.
- Position
- Below the diagonal: Domain.Event uses a module listed above it, which is the healthy direction.
18→5 Domain.Event uses Domain.Model✕
- Connections
- 9 pairs of types, where a type in Domain.Event uses a type in Domain.Model.
- The types involved
BenGorUser.User.Domain.Event.UserInvitedMailerSubscriber→BenGorUser.User.Domain.Model.UserMailableFactoryBenGorUser.User.Domain.Event.UserInvitedMailerSubscriber→BenGorUser.User.Domain.Model.UserMailerBenGorUser.User.Domain.Event.UserInvitedMailerSubscriber→BenGorUser.User.Domain.Model.UserUrlGeneratorBenGorUser.User.Domain.Event.UserRegisteredMailerSubscriber→BenGorUser.User.Domain.Model.UserMailableFactoryBenGorUser.User.Domain.Event.UserRegisteredMailerSubscriber→BenGorUser.User.Domain.Model.UserMailerBenGorUser.User.Domain.Event.UserRegisteredMailerSubscriber→BenGorUser.User.Domain.Model.UserUrlGeneratorBenGorUser.User.Domain.Event.UserRememberPasswordRequestedMailerSubscriber→BenGorUser.User.Domain.Model.UserMailableFactoryBenGorUser.User.Domain.Event.UserRememberPasswordRequestedMailerSubscriber→BenGorUser.User.Domain.Model.UserMailerBenGorUser.User.Domain.Event.UserRememberPasswordRequestedMailerSubscriber→BenGorUser.User.Domain.Model.UserUrlGenerator
- Direction
- Domain.Event uses Domain.Model, so a change to Domain.Model can break Domain.Event, while a change to Domain.Event can't break Domain.Model.
- Position
- Below the diagonal: Domain.Event uses a module listed above it, which is the healthy direction.
19→4 Infrastructure.Domain.Model uses Domain.Model.Event✕
- Connections
- 1 pair of types, where a type in Infrastructure.Domain.Model uses a type in Domain.Model.Event.
- The types involved
BenGorUser.User.Infrastructure.Domain.Model.UserEventBus→BenGorUser.User.Domain.Model.Event.UserEvent
- Direction
- Infrastructure.Domain.Model uses Domain.Model.Event, so a change to Domain.Model.Event can break Infrastructure.Domain.Model, while a change to Infrastructure.Domain.Model can't break Domain.Model.Event.
- Position
- Below the diagonal: Infrastructure.Domain.Model uses a module listed above it, which is the healthy direction.
19→5 Infrastructure.Domain.Model uses Domain.Model✕
- Connections
- 7 pairs of types, where a type in Infrastructure.Domain.Model uses a type in Domain.Model.
- The types involved
BenGorUser.User.Infrastructure.Domain.Model.UserFactoryInvite→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Infrastructure.Domain.Model.UserFactoryInvite→BenGorUser.User.Domain.Model.UserFactoryInviteBenGorUser.User.Infrastructure.Domain.Model.UserFactoryInvite→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Infrastructure.Domain.Model.UserFactorySignUp→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Infrastructure.Domain.Model.UserFactorySignUp→BenGorUser.User.Domain.Model.UserFactorySignUpBenGorUser.User.Infrastructure.Domain.Model.UserFactorySignUp→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Infrastructure.Domain.Model.UserFactorySignUp→BenGorUser.User.Domain.Model.UserPassword
- Direction
- Infrastructure.Domain.Model uses Domain.Model, so a change to Domain.Model can break Infrastructure.Domain.Model, while a change to Infrastructure.Domain.Model can't break Domain.Model.
- Position
- Below the diagonal: Infrastructure.Domain.Model uses a module listed above it, which is the healthy direction.
20→5 Infrastructure.Routing uses Domain.Model✕
- Connections
- 1 pair of types, where a type in Infrastructure.Routing uses a type in Domain.Model.
- The types involved
BenGorUser.User.Infrastructure.Routing.PlainUserUrlGenerator→BenGorUser.User.Domain.Model.UserUrlGenerator
- Direction
- Infrastructure.Routing uses Domain.Model, so a change to Domain.Model can break Infrastructure.Routing, while a change to Infrastructure.Routing can't break Domain.Model.
- Position
- Below the diagonal: Infrastructure.Routing uses a module listed above it, which is the healthy direction.
21→5 Infrastructure.Security uses Domain.Model✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Security uses a type in Domain.Model.
- The types involved
BenGorUser.User.Infrastructure.Security.DummyUserPasswordEncoder→BenGorUser.User.Domain.Model.UserPasswordBenGorUser.User.Infrastructure.Security.DummyUserPasswordEncoder→BenGorUser.User.Domain.Model.UserPasswordEncoder
- Direction
- Infrastructure.Security uses Domain.Model, so a change to Domain.Model can break Infrastructure.Security, while a change to Infrastructure.Security can't break Domain.Model.
- Position
- Below the diagonal: Infrastructure.Security uses a module listed above it, which is the healthy direction.
22→5 Infrastructure.Persistence uses Domain.Model✕
- Connections
- 10 pairs of types, where a type in Infrastructure.Persistence uses a type in Domain.Model.
- The types involved
BenGorUser.User.Infrastructure.Persistence.InMemoryUserRepository→BenGorUser.User.Domain.Model.UserBenGorUser.User.Infrastructure.Persistence.InMemoryUserRepository→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Infrastructure.Persistence.InMemoryUserRepository→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Infrastructure.Persistence.InMemoryUserRepository→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Infrastructure.Persistence.InMemoryUserRepository→BenGorUser.User.Domain.Model.UserTokenBenGorUser.User.Infrastructure.Persistence.SqlUserRepository→BenGorUser.User.Domain.Model.UserBenGorUser.User.Infrastructure.Persistence.SqlUserRepository→BenGorUser.User.Domain.Model.UserEmailBenGorUser.User.Infrastructure.Persistence.SqlUserRepository→BenGorUser.User.Domain.Model.UserIdBenGorUser.User.Infrastructure.Persistence.SqlUserRepository→BenGorUser.User.Domain.Model.UserRepositoryBenGorUser.User.Infrastructure.Persistence.SqlUserRepository→BenGorUser.User.Domain.Model.UserToken
- Direction
- Infrastructure.Persistence uses Domain.Model, so a change to Domain.Model can break Infrastructure.Persistence, while a change to Infrastructure.Persistence can't break Domain.Model.
- Position
- Below the diagonal: Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
22→19 Infrastructure.Persistence uses Infrastructure.Domain.Model✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Persistence uses a type in Infrastructure.Domain.Model.
- The types involved
BenGorUser.User.Infrastructure.Persistence.InMemoryUserRepository→BenGorUser.User.Infrastructure.Domain.Model.UserEventBusBenGorUser.User.Infrastructure.Persistence.SqlUserRepository→BenGorUser.User.Infrastructure.Domain.Model.UserEventBus
- Direction
- Infrastructure.Persistence uses Infrastructure.Domain.Model, so a change to Infrastructure.Domain.Model can break Infrastructure.Persistence, while a change to Infrastructure.Persistence can't break Infrastructure.Domain.Model.
- Position
- Below the diagonal: Infrastructure.Persistence 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
Roadmap
Top priorities: Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with User.php, SqlUserRepository.php, InMemoryUserRepository.php; Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with User.php, SqlUserRepository.php, InMemoryUserRepository.php. | +8.0 pts | Low | Knowledge Freshness |
| Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists. | +7.8 pts | Medium | CI/CD gates |
| 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. | +6.1 pts | Medium | Architecture documentation |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +3.2 pts | Medium | Nullable reference types |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.3 pts | Low | Knowledge Freshness |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +1.1 pts | Low | Project Cohesion |
| Add an 'Architecture' / 'How it works' section to the root README — the high-level shape. | +1.3 pts | Medium | Documentation (README) |
| Resolve the 1 TooManyMethods finding(s) in God Classes — start with User.php. | +0.2 pts | Medium | God Classes |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/BenGorUser/User/Domain/Model/User.php | 8.5 | Near-clean | God Classes: TooManyMethods: User |
| src/BenGorUser/User/Application/Command/SignUp/SignUpUserHandler.php | 8.5 | Near-clean | Code Duplication: Duplicated block (19 lines × 2) |
| src/BenGorUser/User/Application/Command/SignUp/SignUpUserCommand.php | 8.5 | Near-clean | Code Duplication: Duplicated block (44 lines × 2) |
| src/BenGorUser/User/Domain/Model/Event/UserEnabled.php | 8.5 | Near-clean | Code Duplication: Duplicated block (27 lines × 3) |
| src/BenGorUser/User/Domain/Model/Event/UserInvitationTokenRegenerated.php | 8.5 | Near-clean | Code Duplication: Duplicated block (38 lines × 2) |
| src/BenGorUser/User/Application/Command/PurgeOutdatedTokens/PurgeOutdatedInvitationTokensUserHandler.php | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| src/BenGorUser/User/Application/Query/UserOfEmailHandler.php | 8.5 | Near-clean | Code Duplication: Duplicated block (8 lines × 2) |
| src/BenGorUser/User/Domain/Event/UserInvitedMailerSubscriber.php | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 3) |
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 49 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 49 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, 17 of 26 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage 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.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 1 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- 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.
- 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.
- 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.
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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").
- 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.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- 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
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with User.php. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
7 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with SignUpUserHandler.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (44 lines × 2) finding(s) in Code Duplication — start with SignUpUserCommand.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (27 lines × 3) finding(s) in Code Duplication — start with UserEnabled.php. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 7 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 6195 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 13 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 1 build units (Composer) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
38 % of calls cross a namespace and 6 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D34 · Knowledge Freshness
9 of 9 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/BenGorUser/User/Domain/Model/User.php. Counted over 9 of the 94 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 9 Orphaned file finding(s) in Knowledge Freshness — start with User.php, SqlUserRepository.php, InMemoryUserRepository.php. — One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `README.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.
What to do
- Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add phpstan or psalm (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 562 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
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
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 85% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 50% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 43% | Adequate — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Exemplary | Strongest area. |
| Domain Modelling | 100% | Exemplary | Solid. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 79 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's PHP imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~3261 lines of test source are present (.php) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 1 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
- D16 Bus Factor — bus factor 1 — one contributor carries this repository
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; PHP not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed PHP surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (BenGorUser), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — 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
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- 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
- D9 Test Distribution — Test source is present (.php) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- 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
- 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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a PHP event-sourcing aggregate base (broadway/prooph/EventSauce AggregateRoot); 2 PHP aggregate(s) recording domain events (recordThat/apply)
- 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's PHP source (1 module(s), 94 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the PHP source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- 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.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Serious — 10 finding(s)
- bus factor 1 — one contributor carries this repository
- TooManyMethods: User src/BenGorUser/User/Domain/Model/User.php:39
- Duplicated block (19 lines × 2) src/BenGorUser/User/Application/Command/SignUp/SignUpUserHandler.php:79
- Duplicated block (44 lines × 2) src/BenGorUser/User/Application/Command/SignUp/SignUpUserCommand.php:63
- Duplicated block (27 lines × 3) src/BenGorUser/User/Domain/Model/Event/UserEnabled.php:55
- Duplicated block (38 lines × 2) src/BenGorUser/User/Domain/Model/Event/UserInvitationTokenRegenerated.php:63
- Duplicated block (9 lines × 2) src/BenGorUser/User/Application/Command/PurgeOutdatedTokens/PurgeOutdatedInvitationTokensUserHandler.php:49
- Duplicated block (8 lines × 2) src/BenGorUser/User/Application/Query/UserOfEmailHandler.php:64
- Duplicated block (13 lines × 3) src/BenGorUser/User/Domain/Event/UserInvitedMailerSubscriber.php:72
- CI pipeline targets a decommissioned service
Minor — 16 finding(s)
- Orphaned file src/BenGorUser/User/Domain/Model/User.php:1
- Orphaned file src/BenGorUser/User/Infrastructure/Persistence/SqlUserRepository.php:1
- Orphaned file src/BenGorUser/User/Infrastructure/Persistence/InMemoryUserRepository.php:1
- Orphaned file src/BenGorUser/User/Domain/Model/UserPassword.php:1
- Orphaned file src/BenGorUser/User/Domain/Model/UserMailable.php:1
- Orphaned file src/BenGorUser/User/Application/Command/SignUp/WithConfirmationSignUpUserHandler.php:1
- Orphaned file src/BenGorUser/User/Application/Command/SignUp/SignUpUserHandler.php:1
- Orphaned file src/BenGorUser/User/Application/DataTransformer/UserDTODataTransformer.php:1
- Orphaned file src/BenGorUser/User/Domain/Model/UserEmail.php:1
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- PHP static analysis does not check null everywhere
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-a1a3f967e7ec4a3fa87ddde34f2e7498/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a1a3f967e7ec4a3fa87ddde34f2e7498/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |