Executive summary
jorge07/symfony-7-es-cqrs-boilerplate is rated At risk because critical security findings are open. It scores 58 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Accessibility, at 46, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 8 points. Having someone learn and document the nine files no active contributor knows comes next, worth about 4 points. Raising Accessibility to 58 would lift the score to about 64.
Five passwords or keys are open to anyone who can read the repository. Two known security holes in the packages the code depends on can be used by attackers. Replacing each exposed password or key and updating the vulnerable packages would close both risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and the two unsafe settings in infrastructure or container files need changing to safe values. The page that doesn't say its language needs its language set.
The product code is 4,826 lines, about €11,000 to rebuild.
If Accessibility rose from 46 to 58, the lowest score rated Strong, the score would rise from 58 to about 64.
New since the last survey: 2 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 1 finding
- PII in the event store · PII in event: UserEmailChanged src/App/User/Domain/Event/UserEmailChanged.php
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,700 to €19,000, for 62 to 196 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 58. 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: 4,826 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 App.Shared.Application.Command | 2 App.Shared.Application.Query | 3 App.Shared.Domain.Exception | 4 App.Shared.Domain.Repository | 5 App.Shared.Domain.ValueObject | 6 App.Shared.Infrastructure.Bus.AsyncEvent | 7 App.Shared.Infrastructure.Persistence.ReadModel.Repository | 8 App.User.Domain.ValueObject | 9 App.Shared.Application.Query.Event.GetEvents | 10 App.Shared.Infrastructure.Bus.Command | 11 App.Shared.Infrastructure.Bus.Query | 12 App.Shared.Infrastructure.Event.ReadModel | 13 App.User.Domain.Specification | 14 App.User.Domain.ValueObject.Auth | 15 UI.Http.Rest.Response | 16 UI.Http.Web.Controller | 17 App.User.Application.Query.Auth | 18 App.User.Domain.Event | 19 App.User.Infrastructure.Auth.Guard | 20 App.User.Infrastructure.Persistence.Doctrine.Types | 21 App.User.Infrastructure.ReadModel | 22 UI.Http.Rest.Controller | 23 App.User.Domain | 24 UI.Http.Rest.Controller.Auth | 25 UI.Http.Rest.Controller.Event | 26 App.User.Domain.Repository | 27 App.User.Application.Command.ChangeEmail | 28 App.User.Application.Command.SignIn | 29 App.User.Application.Command.SignUp | 30 App.User.Application.Query.Auth.GetToken | 31 App.User.Application.Query.User.FindByEmail | 32 App.User.Infrastructure.ReadModel.Mysql | 33 App.User.Infrastructure.Repository | 34 App.User.Infrastructure.Specification | 35 App.User.Infrastructure.Auth | 36 App.User.Infrastructure.ReadModel.Projections | 37 UI.Http.Rest.Controller.Healthz | 38 App.User.Application.Query.Auth.GetAuthUserByEmail | 39 UI.Http | 40 UI.Http.Rest.Controller.User |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 App.Shared.Application.Command | ||||||||||||||||||||||||||||||||||||||||
| 2 App.Shared.Application.Query | ||||||||||||||||||||||||||||||||||||||||
| 3 App.Shared.Domain.Exception | ||||||||||||||||||||||||||||||||||||||||
| 4 App.Shared.Domain.Repository | ||||||||||||||||||||||||||||||||||||||||
| 5 App.Shared.Domain.ValueObject | ||||||||||||||||||||||||||||||||||||||||
| 6 App.Shared.Infrastructure.Bus.AsyncEvent | ||||||||||||||||||||||||||||||||||||||||
| 7 App.Shared.Infrastructure.Persistence.ReadModel.Repository | ||||||||||||||||||||||||||||||||||||||||
| 8 App.User.Domain.ValueObject | ||||||||||||||||||||||||||||||||||||||||
| 9 App.Shared.Application.Query.Event.GetEvents | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 App.Shared.Infrastructure.Bus.Command | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 App.Shared.Infrastructure.Bus.Query | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 App.Shared.Infrastructure.Event.ReadModel | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 App.User.Domain.Specification | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 App.User.Domain.ValueObject.Auth | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 UI.Http.Rest.Response | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 UI.Http.Web.Controller | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 App.User.Application.Query.Auth | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 App.User.Domain.Event | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 App.User.Infrastructure.Auth.Guard | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 App.User.Infrastructure.Persistence.Doctrine.Types | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 App.User.Infrastructure.ReadModel | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 UI.Http.Rest.Controller | 4 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 App.User.Domain | 1 | 1 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||
| 24 UI.Http.Rest.Controller.Auth | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 UI.Http.Rest.Controller.Event | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 App.User.Domain.Repository | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 App.User.Application.Command.ChangeEmail | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 App.User.Application.Command.SignIn | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 App.User.Application.Command.SignUp | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 App.User.Application.Query.Auth.GetToken | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 App.User.Application.Query.User.FindByEmail | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 App.User.Infrastructure.ReadModel.Mysql | 1 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 33 App.User.Infrastructure.Repository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 App.User.Infrastructure.Specification | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 App.User.Infrastructure.Auth | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 App.User.Infrastructure.ReadModel.Projections | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 UI.Http.Rest.Controller.Healthz | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 App.User.Application.Query.Auth.GetAuthUserByEmail | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 UI.Http | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 UI.Http.Rest.Controller.User | 1 | 2 | 3 | 1 |
9→2 App.Shared.Application.Query.Event.GetEvents uses App.Shared.Application.Query✕
- Connections
- 3 pairs of types, where a type in App.Shared.Application.Query.Event.GetEvents uses a type in App.Shared.Application.Query.
- The types involved
App.Shared.Application.Query.Event.GetEvents.GetEventsHandler→App.Shared.Application.Query.CollectionApp.Shared.Application.Query.Event.GetEvents.GetEventsHandler→App.Shared.Application.Query.QueryHandlerInterfaceApp.Shared.Application.Query.Event.GetEvents.GetEventsQuery→App.Shared.Application.Query.QueryInterface
- Direction
- App.Shared.Application.Query.Event.GetEvents uses App.Shared.Application.Query, so a change to App.Shared.Application.Query can break App.Shared.Application.Query.Event.GetEvents, while a change to App.Shared.Application.Query.Event.GetEvents can't break App.Shared.Application.Query.
- Position
- Below the diagonal: App.Shared.Application.Query.Event.GetEvents uses a module listed above it, which is the healthy direction.
9→4 App.Shared.Application.Query.Event.GetEvents uses App.Shared.Domain.Repository✕
- Connections
- 1 pair of types, where a type in App.Shared.Application.Query.Event.GetEvents uses a type in App.Shared.Domain.Repository.
- The types involved
App.Shared.Application.Query.Event.GetEvents.GetEventsHandler→App.Shared.Domain.Repository.EventRepositoryInterface
- Direction
- App.Shared.Application.Query.Event.GetEvents uses App.Shared.Domain.Repository, so a change to App.Shared.Domain.Repository can break App.Shared.Application.Query.Event.GetEvents, while a change to App.Shared.Application.Query.Event.GetEvents can't break App.Shared.Domain.Repository.
- Position
- Below the diagonal: App.Shared.Application.Query.Event.GetEvents uses a module listed above it, which is the healthy direction.
10→1 App.Shared.Infrastructure.Bus.Command uses App.Shared.Application.Command✕
- Connections
- 2 pairs of types, where a type in App.Shared.Infrastructure.Bus.Command uses a type in App.Shared.Application.Command.
- The types involved
App.Shared.Infrastructure.Bus.Command.MessengerCommandBus→App.Shared.Application.Command.CommandBusInterfaceApp.Shared.Infrastructure.Bus.Command.MessengerCommandBus→App.Shared.Application.Command.CommandInterface
- Direction
- App.Shared.Infrastructure.Bus.Command uses App.Shared.Application.Command, so a change to App.Shared.Application.Command can break App.Shared.Infrastructure.Bus.Command, while a change to App.Shared.Infrastructure.Bus.Command can't break App.Shared.Application.Command.
- Position
- Below the diagonal: App.Shared.Infrastructure.Bus.Command uses a module listed above it, which is the healthy direction.
11→2 App.Shared.Infrastructure.Bus.Query uses App.Shared.Application.Query✕
- Connections
- 2 pairs of types, where a type in App.Shared.Infrastructure.Bus.Query uses a type in App.Shared.Application.Query.
- The types involved
App.Shared.Infrastructure.Bus.Query.MessengerQueryBus→App.Shared.Application.Query.QueryBusInterfaceApp.Shared.Infrastructure.Bus.Query.MessengerQueryBus→App.Shared.Application.Query.QueryInterface
- Direction
- App.Shared.Infrastructure.Bus.Query uses App.Shared.Application.Query, so a change to App.Shared.Application.Query can break App.Shared.Infrastructure.Bus.Query, while a change to App.Shared.Infrastructure.Bus.Query can't break App.Shared.Application.Query.
- Position
- Below the diagonal: App.Shared.Infrastructure.Bus.Query uses a module listed above it, which is the healthy direction.
12→4 App.Shared.Infrastructure.Event.ReadModel uses App.Shared.Domain.Repository✕
- Connections
- 1 pair of types, where a type in App.Shared.Infrastructure.Event.ReadModel uses a type in App.Shared.Domain.Repository.
- The types involved
App.Shared.Infrastructure.Event.ReadModel.ElasticSearchEventRepository→App.Shared.Domain.Repository.EventRepositoryInterface
- Direction
- App.Shared.Infrastructure.Event.ReadModel uses App.Shared.Domain.Repository, so a change to App.Shared.Domain.Repository can break App.Shared.Infrastructure.Event.ReadModel, while a change to App.Shared.Infrastructure.Event.ReadModel can't break App.Shared.Domain.Repository.
- Position
- Below the diagonal: App.Shared.Infrastructure.Event.ReadModel uses a module listed above it, which is the healthy direction.
12→7 App.Shared.Infrastructure.Event.ReadModel uses App.Shared.Infrastructure.Persistence.ReadModel.Repository✕
- Connections
- 1 pair of types, where a type in App.Shared.Infrastructure.Event.ReadModel uses a type in App.Shared.Infrastructure.Persistence.ReadModel.Repository.
- The types involved
App.Shared.Infrastructure.Event.ReadModel.ElasticSearchEventRepository→App.Shared.Infrastructure.Persistence.ReadModel.Repository.ElasticSearchRepository
- Direction
- App.Shared.Infrastructure.Event.ReadModel uses App.Shared.Infrastructure.Persistence.ReadModel.Repository, so a change to App.Shared.Infrastructure.Persistence.ReadModel.Repository can break App.Shared.Infrastructure.Event.ReadModel, while a change to App.Shared.Infrastructure.Event.ReadModel can't break App.Shared.Infrastructure.Persistence.ReadModel.Repository.
- Position
- Below the diagonal: App.Shared.Infrastructure.Event.ReadModel uses a module listed above it, which is the healthy direction.
13→8 App.User.Domain.Specification uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Domain.Specification uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Domain.Specification.UniqueEmailSpecificationInterface→App.User.Domain.ValueObject.Email
- Direction
- App.User.Domain.Specification uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Domain.Specification, while a change to App.User.Domain.Specification can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Domain.Specification uses a module listed above it, which is the healthy direction.
14→8 App.User.Domain.ValueObject.Auth uses App.User.Domain.ValueObject✕
- Connections
- 2 pairs of types, where a type in App.User.Domain.ValueObject.Auth uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Domain.ValueObject.Auth.Credentials→App.User.Domain.ValueObject.EmailApp.User.Domain.ValueObject.Auth.UserCredentials→App.User.Domain.ValueObject.Email
- Direction
- App.User.Domain.ValueObject.Auth uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Domain.ValueObject.Auth, while a change to App.User.Domain.ValueObject.Auth can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Domain.ValueObject.Auth uses a module listed above it, which is the healthy direction.
15→2 UI.Http.Rest.Response uses App.Shared.Application.Query✕
- Connections
- 2 pairs of types, where a type in UI.Http.Rest.Response uses a type in App.Shared.Application.Query.
- The types involved
UI.Http.Rest.Response.OpenApi→App.Shared.Application.Query.CollectionUI.Http.Rest.Response.OpenApi→App.Shared.Application.Query.Item
- Direction
- UI.Http.Rest.Response uses App.Shared.Application.Query, so a change to App.Shared.Application.Query can break UI.Http.Rest.Response, while a change to UI.Http.Rest.Response can't break App.Shared.Application.Query.
- Position
- Below the diagonal: UI.Http.Rest.Response uses a module listed above it, which is the healthy direction.
16→1 UI.Http.Web.Controller uses App.Shared.Application.Command✕
- Connections
- 2 pairs of types, where a type in UI.Http.Web.Controller uses a type in App.Shared.Application.Command.
- The types involved
UI.Http.Web.Controller.AbstractRenderController→App.Shared.Application.Command.CommandBusInterfaceUI.Http.Web.Controller.AbstractRenderController→App.Shared.Application.Command.CommandInterface
- Direction
- UI.Http.Web.Controller uses App.Shared.Application.Command, so a change to App.Shared.Application.Command can break UI.Http.Web.Controller, while a change to UI.Http.Web.Controller can't break App.Shared.Application.Command.
- Position
- Below the diagonal: UI.Http.Web.Controller uses a module listed above it, which is the healthy direction.
16→2 UI.Http.Web.Controller uses App.Shared.Application.Query✕
- Connections
- 2 pairs of types, where a type in UI.Http.Web.Controller uses a type in App.Shared.Application.Query.
- The types involved
UI.Http.Web.Controller.AbstractRenderController→App.Shared.Application.Query.QueryBusInterfaceUI.Http.Web.Controller.AbstractRenderController→App.Shared.Application.Query.QueryInterface
- Direction
- UI.Http.Web.Controller uses App.Shared.Application.Query, so a change to App.Shared.Application.Query can break UI.Http.Web.Controller, while a change to UI.Http.Web.Controller can't break App.Shared.Application.Query.
- Position
- Below the diagonal: UI.Http.Web.Controller uses a module listed above it, which is the healthy direction.
17→8 App.User.Application.Query.Auth uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Application.Query.Auth uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Application.Query.Auth.AuthenticationProviderInterface→App.User.Domain.ValueObject.Email
- Direction
- App.User.Application.Query.Auth uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Application.Query.Auth, while a change to App.User.Application.Query.Auth can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Application.Query.Auth uses a module listed above it, which is the healthy direction.
17→14 App.User.Application.Query.Auth uses App.User.Domain.ValueObject.Auth✕
- Connections
- 1 pair of types, where a type in App.User.Application.Query.Auth uses a type in App.User.Domain.ValueObject.Auth.
- The types involved
App.User.Application.Query.Auth.AuthenticationProviderInterface→App.User.Domain.ValueObject.Auth.HashedPassword
- Direction
- App.User.Application.Query.Auth uses App.User.Domain.ValueObject.Auth, so a change to App.User.Domain.ValueObject.Auth can break App.User.Application.Query.Auth, while a change to App.User.Application.Query.Auth can't break App.User.Domain.ValueObject.Auth.
- Position
- Below the diagonal: App.User.Application.Query.Auth uses a module listed above it, which is the healthy direction.
18→5 App.User.Domain.Event uses App.Shared.Domain.ValueObject✕
- Connections
- 2 pairs of types, where a type in App.User.Domain.Event uses a type in App.Shared.Domain.ValueObject.
- The types involved
App.User.Domain.Event.UserEmailChanged→App.Shared.Domain.ValueObject.DateTimeApp.User.Domain.Event.UserWasCreated→App.Shared.Domain.ValueObject.DateTime
- Direction
- App.User.Domain.Event uses App.Shared.Domain.ValueObject, so a change to App.Shared.Domain.ValueObject can break App.User.Domain.Event, while a change to App.User.Domain.Event can't break App.Shared.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Domain.Event uses a module listed above it, which is the healthy direction.
18→8 App.User.Domain.Event uses App.User.Domain.ValueObject✕
- Connections
- 2 pairs of types, where a type in App.User.Domain.Event uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Domain.Event.UserEmailChanged→App.User.Domain.ValueObject.EmailApp.User.Domain.Event.UserSignedIn→App.User.Domain.ValueObject.Email
- Direction
- App.User.Domain.Event uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Domain.Event, while a change to App.User.Domain.Event can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Domain.Event uses a module listed above it, which is the healthy direction.
18→14 App.User.Domain.Event uses App.User.Domain.ValueObject.Auth✕
- Connections
- 1 pair of types, where a type in App.User.Domain.Event uses a type in App.User.Domain.ValueObject.Auth.
- The types involved
App.User.Domain.Event.UserWasCreated→App.User.Domain.ValueObject.Auth.Credentials
- Direction
- App.User.Domain.Event uses App.User.Domain.ValueObject.Auth, so a change to App.User.Domain.ValueObject.Auth can break App.User.Domain.Event, while a change to App.User.Domain.Event can't break App.User.Domain.ValueObject.Auth.
- Position
- Below the diagonal: App.User.Domain.Event uses a module listed above it, which is the healthy direction.
19→10 App.User.Infrastructure.Auth.Guard uses App.Shared.Infrastructure.Bus.Command✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Auth.Guard uses a type in App.Shared.Infrastructure.Bus.Command.
- The types involved
App.User.Infrastructure.Auth.Guard.LoginAuthenticator→App.Shared.Infrastructure.Bus.Command.MessengerCommandBus
- Direction
- App.User.Infrastructure.Auth.Guard uses App.Shared.Infrastructure.Bus.Command, so a change to App.Shared.Infrastructure.Bus.Command can break App.User.Infrastructure.Auth.Guard, while a change to App.User.Infrastructure.Auth.Guard can't break App.Shared.Infrastructure.Bus.Command.
- Position
- Below the diagonal: App.User.Infrastructure.Auth.Guard uses a module listed above it, which is the healthy direction.
19→11 App.User.Infrastructure.Auth.Guard uses App.Shared.Infrastructure.Bus.Query✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Auth.Guard uses a type in App.Shared.Infrastructure.Bus.Query.
- The types involved
App.User.Infrastructure.Auth.Guard.LoginAuthenticator→App.Shared.Infrastructure.Bus.Query.MessengerQueryBus
- Direction
- App.User.Infrastructure.Auth.Guard uses App.Shared.Infrastructure.Bus.Query, so a change to App.Shared.Infrastructure.Bus.Query can break App.User.Infrastructure.Auth.Guard, while a change to App.User.Infrastructure.Auth.Guard can't break App.Shared.Infrastructure.Bus.Query.
- Position
- Below the diagonal: App.User.Infrastructure.Auth.Guard uses a module listed above it, which is the healthy direction.
20→8 App.User.Infrastructure.Persistence.Doctrine.Types uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Persistence.Doctrine.Types uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Infrastructure.Persistence.Doctrine.Types.EmailType→App.User.Domain.ValueObject.Email
- Direction
- App.User.Infrastructure.Persistence.Doctrine.Types uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Infrastructure.Persistence.Doctrine.Types, while a change to App.User.Infrastructure.Persistence.Doctrine.Types can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Infrastructure.Persistence.Doctrine.Types uses a module listed above it, which is the healthy direction.
20→14 App.User.Infrastructure.Persistence.Doctrine.Types uses App.User.Domain.ValueObject.Auth✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Persistence.Doctrine.Types uses a type in App.User.Domain.ValueObject.Auth.
- The types involved
App.User.Infrastructure.Persistence.Doctrine.Types.HashedPasswordType→App.User.Domain.ValueObject.Auth.HashedPassword
- Direction
- App.User.Infrastructure.Persistence.Doctrine.Types uses App.User.Domain.ValueObject.Auth, so a change to App.User.Domain.ValueObject.Auth can break App.User.Infrastructure.Persistence.Doctrine.Types, while a change to App.User.Infrastructure.Persistence.Doctrine.Types can't break App.User.Domain.ValueObject.Auth.
- Position
- Below the diagonal: App.User.Infrastructure.Persistence.Doctrine.Types uses a module listed above it, which is the healthy direction.
21→5 App.User.Infrastructure.ReadModel uses App.Shared.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.ReadModel uses a type in App.Shared.Domain.ValueObject.
- The types involved
App.User.Infrastructure.ReadModel.UserView→App.Shared.Domain.ValueObject.DateTime
- Direction
- App.User.Infrastructure.ReadModel uses App.Shared.Domain.ValueObject, so a change to App.Shared.Domain.ValueObject can break App.User.Infrastructure.ReadModel, while a change to App.User.Infrastructure.ReadModel can't break App.Shared.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Infrastructure.ReadModel uses a module listed above it, which is the healthy direction.
21→8 App.User.Infrastructure.ReadModel uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.ReadModel uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Infrastructure.ReadModel.UserView→App.User.Domain.ValueObject.Email
- Direction
- App.User.Infrastructure.ReadModel uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Infrastructure.ReadModel, while a change to App.User.Infrastructure.ReadModel can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Infrastructure.ReadModel uses a module listed above it, which is the healthy direction.
21→14 App.User.Infrastructure.ReadModel uses App.User.Domain.ValueObject.Auth✕
- Connections
- 2 pairs of types, where a type in App.User.Infrastructure.ReadModel uses a type in App.User.Domain.ValueObject.Auth.
- The types involved
App.User.Infrastructure.ReadModel.UserView→App.User.Domain.ValueObject.Auth.CredentialsApp.User.Infrastructure.ReadModel.UserView→App.User.Domain.ValueObject.Auth.HashedPassword
- Direction
- App.User.Infrastructure.ReadModel uses App.User.Domain.ValueObject.Auth, so a change to App.User.Domain.ValueObject.Auth can break App.User.Infrastructure.ReadModel, while a change to App.User.Infrastructure.ReadModel can't break App.User.Domain.ValueObject.Auth.
- Position
- Below the diagonal: App.User.Infrastructure.ReadModel uses a module listed above it, which is the healthy direction.
22→1 UI.Http.Rest.Controller uses App.Shared.Application.Command✕
- Connections
- 4 pairs of types, where a type in UI.Http.Rest.Controller uses a type in App.Shared.Application.Command.
- The types involved
UI.Http.Rest.Controller.CommandController→App.Shared.Application.Command.CommandBusInterfaceUI.Http.Rest.Controller.CommandController→App.Shared.Application.Command.CommandInterfaceUI.Http.Rest.Controller.CommandQueryController→App.Shared.Application.Command.CommandBusInterfaceUI.Http.Rest.Controller.CommandQueryController→App.Shared.Application.Command.CommandInterface
- Direction
- UI.Http.Rest.Controller uses App.Shared.Application.Command, so a change to App.Shared.Application.Command can break UI.Http.Rest.Controller, while a change to UI.Http.Rest.Controller can't break App.Shared.Application.Command.
- Position
- Below the diagonal: UI.Http.Rest.Controller uses a module listed above it, which is the healthy direction.
22→2 UI.Http.Rest.Controller uses App.Shared.Application.Query✕
- Connections
- 5 pairs of types, where a type in UI.Http.Rest.Controller uses a type in App.Shared.Application.Query.
- The types involved
UI.Http.Rest.Controller.CommandQueryController→App.Shared.Application.Query.QueryBusInterfaceUI.Http.Rest.Controller.QueryController→App.Shared.Application.Query.CollectionUI.Http.Rest.Controller.QueryController→App.Shared.Application.Query.ItemUI.Http.Rest.Controller.QueryController→App.Shared.Application.Query.QueryBusInterfaceUI.Http.Rest.Controller.QueryController→App.Shared.Application.Query.QueryInterface
- Direction
- UI.Http.Rest.Controller uses App.Shared.Application.Query, so a change to App.Shared.Application.Query can break UI.Http.Rest.Controller, while a change to UI.Http.Rest.Controller can't break App.Shared.Application.Query.
- Position
- Below the diagonal: UI.Http.Rest.Controller uses a module listed above it, which is the healthy direction.
22→15 UI.Http.Rest.Controller uses UI.Http.Rest.Response✕
- Connections
- 1 pair of types, where a type in UI.Http.Rest.Controller uses a type in UI.Http.Rest.Response.
- The types involved
UI.Http.Rest.Controller.QueryController→UI.Http.Rest.Response.OpenApi
- Direction
- UI.Http.Rest.Controller uses UI.Http.Rest.Response, so a change to UI.Http.Rest.Response can break UI.Http.Rest.Controller, while a change to UI.Http.Rest.Controller can't break UI.Http.Rest.Response.
- Position
- Below the diagonal: UI.Http.Rest.Controller uses a module listed above it, which is the healthy direction.
23→5 App.User.Domain uses App.Shared.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Domain uses a type in App.Shared.Domain.ValueObject.
- The types involved
App.User.Domain.User→App.Shared.Domain.ValueObject.DateTime
- Direction
- App.User.Domain uses App.Shared.Domain.ValueObject, so a change to App.Shared.Domain.ValueObject can break App.User.Domain, while a change to App.User.Domain can't break App.Shared.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Domain uses a module listed above it, which is the healthy direction.
23→8 App.User.Domain uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Domain uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Domain.User→App.User.Domain.ValueObject.Email
- Direction
- App.User.Domain uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Domain, while a change to App.User.Domain can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Domain uses a module listed above it, which is the healthy direction.
23→13 App.User.Domain uses App.User.Domain.Specification✕
- Connections
- 1 pair of types, where a type in App.User.Domain uses a type in App.User.Domain.Specification.
- The types involved
App.User.Domain.User→App.User.Domain.Specification.UniqueEmailSpecificationInterface
- Direction
- App.User.Domain uses App.User.Domain.Specification, so a change to App.User.Domain.Specification can break App.User.Domain, while a change to App.User.Domain can't break App.User.Domain.Specification.
- Position
- Below the diagonal: App.User.Domain uses a module listed above it, which is the healthy direction.
23→14 App.User.Domain uses App.User.Domain.ValueObject.Auth✕
- Connections
- 2 pairs of types, where a type in App.User.Domain uses a type in App.User.Domain.ValueObject.Auth.
- The types involved
App.User.Domain.User→App.User.Domain.ValueObject.Auth.CredentialsApp.User.Domain.User→App.User.Domain.ValueObject.Auth.HashedPassword
- Direction
- App.User.Domain uses App.User.Domain.ValueObject.Auth, so a change to App.User.Domain.ValueObject.Auth can break App.User.Domain, while a change to App.User.Domain can't break App.User.Domain.ValueObject.Auth.
- Position
- Below the diagonal: App.User.Domain uses a module listed above it, which is the healthy direction.
23→18 App.User.Domain uses App.User.Domain.Event✕
- Connections
- 3 pairs of types, where a type in App.User.Domain uses a type in App.User.Domain.Event.
- The types involved
App.User.Domain.User→App.User.Domain.Event.UserEmailChangedApp.User.Domain.User→App.User.Domain.Event.UserSignedInApp.User.Domain.User→App.User.Domain.Event.UserWasCreated
- Direction
- App.User.Domain uses App.User.Domain.Event, so a change to App.User.Domain.Event can break App.User.Domain, while a change to App.User.Domain can't break App.User.Domain.Event.
- Position
- Below the diagonal: App.User.Domain uses a module listed above it, which is the healthy direction.
24→15 UI.Http.Rest.Controller.Auth uses UI.Http.Rest.Response✕
- Connections
- 1 pair of types, where a type in UI.Http.Rest.Controller.Auth uses a type in UI.Http.Rest.Response.
- The types involved
UI.Http.Rest.Controller.Auth.CheckController→UI.Http.Rest.Response.OpenApi
- Direction
- UI.Http.Rest.Controller.Auth uses UI.Http.Rest.Response, so a change to UI.Http.Rest.Response can break UI.Http.Rest.Controller.Auth, while a change to UI.Http.Rest.Controller.Auth can't break UI.Http.Rest.Response.
- Position
- Below the diagonal: UI.Http.Rest.Controller.Auth uses a module listed above it, which is the healthy direction.
24→22 UI.Http.Rest.Controller.Auth uses UI.Http.Rest.Controller✕
- Connections
- 1 pair of types, where a type in UI.Http.Rest.Controller.Auth uses a type in UI.Http.Rest.Controller.
- The types involved
UI.Http.Rest.Controller.Auth.CheckController→UI.Http.Rest.Controller.CommandQueryController
- Direction
- UI.Http.Rest.Controller.Auth uses UI.Http.Rest.Controller, so a change to UI.Http.Rest.Controller can break UI.Http.Rest.Controller.Auth, while a change to UI.Http.Rest.Controller.Auth can't break UI.Http.Rest.Controller.
- Position
- Below the diagonal: UI.Http.Rest.Controller.Auth uses a module listed above it, which is the healthy direction.
25→15 UI.Http.Rest.Controller.Event uses UI.Http.Rest.Response✕
- Connections
- 1 pair of types, where a type in UI.Http.Rest.Controller.Event uses a type in UI.Http.Rest.Response.
- The types involved
UI.Http.Rest.Controller.Event.GetEventsController→UI.Http.Rest.Response.OpenApi
- Direction
- UI.Http.Rest.Controller.Event uses UI.Http.Rest.Response, so a change to UI.Http.Rest.Response can break UI.Http.Rest.Controller.Event, while a change to UI.Http.Rest.Controller.Event can't break UI.Http.Rest.Response.
- Position
- Below the diagonal: UI.Http.Rest.Controller.Event uses a module listed above it, which is the healthy direction.
25→22 UI.Http.Rest.Controller.Event uses UI.Http.Rest.Controller✕
- Connections
- 1 pair of types, where a type in UI.Http.Rest.Controller.Event uses a type in UI.Http.Rest.Controller.
- The types involved
UI.Http.Rest.Controller.Event.GetEventsController→UI.Http.Rest.Controller.QueryController
- Direction
- UI.Http.Rest.Controller.Event uses UI.Http.Rest.Controller, so a change to UI.Http.Rest.Controller can break UI.Http.Rest.Controller.Event, while a change to UI.Http.Rest.Controller.Event can't break UI.Http.Rest.Controller.
- Position
- Below the diagonal: UI.Http.Rest.Controller.Event uses a module listed above it, which is the healthy direction.
26→8 App.User.Domain.Repository uses App.User.Domain.ValueObject✕
- Connections
- 3 pairs of types, where a type in App.User.Domain.Repository uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Domain.Repository.CheckUserByEmailInterface→App.User.Domain.ValueObject.EmailApp.User.Domain.Repository.GetUserCredentialsByEmailInterface→App.User.Domain.ValueObject.EmailApp.User.Domain.Repository.UserReadModelRepositoryInterface→App.User.Domain.ValueObject.Email
- Direction
- App.User.Domain.Repository uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Domain.Repository, while a change to App.User.Domain.Repository can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Domain.Repository uses a module listed above it, which is the healthy direction.
26→14 App.User.Domain.Repository uses App.User.Domain.ValueObject.Auth✕
- Connections
- 1 pair of types, where a type in App.User.Domain.Repository uses a type in App.User.Domain.ValueObject.Auth.
- The types involved
App.User.Domain.Repository.GetUserCredentialsByEmailInterface→App.User.Domain.ValueObject.Auth.UserCredentials
- Direction
- App.User.Domain.Repository uses App.User.Domain.ValueObject.Auth, so a change to App.User.Domain.ValueObject.Auth can break App.User.Domain.Repository, while a change to App.User.Domain.Repository can't break App.User.Domain.ValueObject.Auth.
- Position
- Below the diagonal: App.User.Domain.Repository uses a module listed above it, which is the healthy direction.
26→23 App.User.Domain.Repository uses App.User.Domain✕
- Connections
- 1 pair of types, where a type in App.User.Domain.Repository uses a type in App.User.Domain.
- The types involved
App.User.Domain.Repository.UserRepositoryInterface→App.User.Domain.User
- Direction
- App.User.Domain.Repository uses App.User.Domain, so a change to App.User.Domain can break App.User.Domain.Repository, while a change to App.User.Domain.Repository can't break App.User.Domain.
- Position
- Below the diagonal: App.User.Domain.Repository uses a module listed above it, which is the healthy direction.
27→1 App.User.Application.Command.ChangeEmail uses App.Shared.Application.Command✕
- Connections
- 2 pairs of types, where a type in App.User.Application.Command.ChangeEmail uses a type in App.Shared.Application.Command.
- The types involved
App.User.Application.Command.ChangeEmail.ChangeEmailCommand→App.Shared.Application.Command.CommandInterfaceApp.User.Application.Command.ChangeEmail.ChangeEmailHandler→App.Shared.Application.Command.CommandHandlerInterface
- Direction
- App.User.Application.Command.ChangeEmail uses App.Shared.Application.Command, so a change to App.Shared.Application.Command can break App.User.Application.Command.ChangeEmail, while a change to App.User.Application.Command.ChangeEmail can't break App.Shared.Application.Command.
- Position
- Below the diagonal: App.User.Application.Command.ChangeEmail uses a module listed above it, which is the healthy direction.
27→8 App.User.Application.Command.ChangeEmail uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Application.Command.ChangeEmail uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Application.Command.ChangeEmail.ChangeEmailCommand→App.User.Domain.ValueObject.Email
- Direction
- App.User.Application.Command.ChangeEmail uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Application.Command.ChangeEmail, while a change to App.User.Application.Command.ChangeEmail can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Application.Command.ChangeEmail uses a module listed above it, which is the healthy direction.
27→13 App.User.Application.Command.ChangeEmail uses App.User.Domain.Specification✕
- Connections
- 1 pair of types, where a type in App.User.Application.Command.ChangeEmail uses a type in App.User.Domain.Specification.
- The types involved
App.User.Application.Command.ChangeEmail.ChangeEmailHandler→App.User.Domain.Specification.UniqueEmailSpecificationInterface
- Direction
- App.User.Application.Command.ChangeEmail uses App.User.Domain.Specification, so a change to App.User.Domain.Specification can break App.User.Application.Command.ChangeEmail, while a change to App.User.Application.Command.ChangeEmail can't break App.User.Domain.Specification.
- Position
- Below the diagonal: App.User.Application.Command.ChangeEmail uses a module listed above it, which is the healthy direction.
27→26 App.User.Application.Command.ChangeEmail uses App.User.Domain.Repository✕
- Connections
- 1 pair of types, where a type in App.User.Application.Command.ChangeEmail uses a type in App.User.Domain.Repository.
- The types involved
App.User.Application.Command.ChangeEmail.ChangeEmailHandler→App.User.Domain.Repository.UserRepositoryInterface
- Direction
- App.User.Application.Command.ChangeEmail uses App.User.Domain.Repository, so a change to App.User.Domain.Repository can break App.User.Application.Command.ChangeEmail, while a change to App.User.Application.Command.ChangeEmail can't break App.User.Domain.Repository.
- Position
- Below the diagonal: App.User.Application.Command.ChangeEmail uses a module listed above it, which is the healthy direction.
28→1 App.User.Application.Command.SignIn uses App.Shared.Application.Command✕
- Connections
- 2 pairs of types, where a type in App.User.Application.Command.SignIn uses a type in App.Shared.Application.Command.
- The types involved
App.User.Application.Command.SignIn.SignInCommand→App.Shared.Application.Command.CommandInterfaceApp.User.Application.Command.SignIn.SignInHandler→App.Shared.Application.Command.CommandHandlerInterface
- Direction
- App.User.Application.Command.SignIn uses App.Shared.Application.Command, so a change to App.Shared.Application.Command can break App.User.Application.Command.SignIn, while a change to App.User.Application.Command.SignIn can't break App.Shared.Application.Command.
- Position
- Below the diagonal: App.User.Application.Command.SignIn uses a module listed above it, which is the healthy direction.
28→8 App.User.Application.Command.SignIn uses App.User.Domain.ValueObject✕
- Connections
- 2 pairs of types, where a type in App.User.Application.Command.SignIn uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Application.Command.SignIn.SignInCommand→App.User.Domain.ValueObject.EmailApp.User.Application.Command.SignIn.SignInHandler→App.User.Domain.ValueObject.Email
- Direction
- App.User.Application.Command.SignIn uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Application.Command.SignIn, while a change to App.User.Application.Command.SignIn can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Application.Command.SignIn uses a module listed above it, which is the healthy direction.
28→26 App.User.Application.Command.SignIn uses App.User.Domain.Repository✕
- Connections
- 2 pairs of types, where a type in App.User.Application.Command.SignIn uses a type in App.User.Domain.Repository.
- The types involved
App.User.Application.Command.SignIn.SignInHandler→App.User.Domain.Repository.CheckUserByEmailInterfaceApp.User.Application.Command.SignIn.SignInHandler→App.User.Domain.Repository.UserRepositoryInterface
- Direction
- App.User.Application.Command.SignIn uses App.User.Domain.Repository, so a change to App.User.Domain.Repository can break App.User.Application.Command.SignIn, while a change to App.User.Application.Command.SignIn can't break App.User.Domain.Repository.
- Position
- Below the diagonal: App.User.Application.Command.SignIn uses a module listed above it, which is the healthy direction.
29→1 App.User.Application.Command.SignUp uses App.Shared.Application.Command✕
- Connections
- 2 pairs of types, where a type in App.User.Application.Command.SignUp uses a type in App.Shared.Application.Command.
- The types involved
App.User.Application.Command.SignUp.SignUpCommand→App.Shared.Application.Command.CommandInterfaceApp.User.Application.Command.SignUp.SignUpHandler→App.Shared.Application.Command.CommandHandlerInterface
- Direction
- App.User.Application.Command.SignUp uses App.Shared.Application.Command, so a change to App.Shared.Application.Command can break App.User.Application.Command.SignUp, while a change to App.User.Application.Command.SignUp can't break App.Shared.Application.Command.
- Position
- Below the diagonal: App.User.Application.Command.SignUp uses a module listed above it, which is the healthy direction.
29→13 App.User.Application.Command.SignUp uses App.User.Domain.Specification✕
- Connections
- 1 pair of types, where a type in App.User.Application.Command.SignUp uses a type in App.User.Domain.Specification.
- The types involved
App.User.Application.Command.SignUp.SignUpHandler→App.User.Domain.Specification.UniqueEmailSpecificationInterface
- Direction
- App.User.Application.Command.SignUp uses App.User.Domain.Specification, so a change to App.User.Domain.Specification can break App.User.Application.Command.SignUp, while a change to App.User.Application.Command.SignUp can't break App.User.Domain.Specification.
- Position
- Below the diagonal: App.User.Application.Command.SignUp uses a module listed above it, which is the healthy direction.
29→26 App.User.Application.Command.SignUp uses App.User.Domain.Repository✕
- Connections
- 1 pair of types, where a type in App.User.Application.Command.SignUp uses a type in App.User.Domain.Repository.
- The types involved
App.User.Application.Command.SignUp.SignUpHandler→App.User.Domain.Repository.UserRepositoryInterface
- Direction
- App.User.Application.Command.SignUp uses App.User.Domain.Repository, so a change to App.User.Domain.Repository can break App.User.Application.Command.SignUp, while a change to App.User.Application.Command.SignUp can't break App.User.Domain.Repository.
- Position
- Below the diagonal: App.User.Application.Command.SignUp uses a module listed above it, which is the healthy direction.
30→2 App.User.Application.Query.Auth.GetToken uses App.Shared.Application.Query✕
- Connections
- 2 pairs of types, where a type in App.User.Application.Query.Auth.GetToken uses a type in App.Shared.Application.Query.
- The types involved
App.User.Application.Query.Auth.GetToken.GetTokenHandler→App.Shared.Application.Query.QueryHandlerInterfaceApp.User.Application.Query.Auth.GetToken.GetTokenQuery→App.Shared.Application.Query.QueryInterface
- Direction
- App.User.Application.Query.Auth.GetToken uses App.Shared.Application.Query, so a change to App.Shared.Application.Query can break App.User.Application.Query.Auth.GetToken, while a change to App.User.Application.Query.Auth.GetToken can't break App.Shared.Application.Query.
- Position
- Below the diagonal: App.User.Application.Query.Auth.GetToken uses a module listed above it, which is the healthy direction.
30→8 App.User.Application.Query.Auth.GetToken uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Application.Query.Auth.GetToken uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Application.Query.Auth.GetToken.GetTokenQuery→App.User.Domain.ValueObject.Email
- Direction
- App.User.Application.Query.Auth.GetToken uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Application.Query.Auth.GetToken, while a change to App.User.Application.Query.Auth.GetToken can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Application.Query.Auth.GetToken uses a module listed above it, which is the healthy direction.
30→17 App.User.Application.Query.Auth.GetToken uses App.User.Application.Query.Auth✕
- Connections
- 1 pair of types, where a type in App.User.Application.Query.Auth.GetToken uses a type in App.User.Application.Query.Auth.
- The types involved
App.User.Application.Query.Auth.GetToken.GetTokenHandler→App.User.Application.Query.Auth.AuthenticationProviderInterface
- Direction
- App.User.Application.Query.Auth.GetToken uses App.User.Application.Query.Auth, so a change to App.User.Application.Query.Auth can break App.User.Application.Query.Auth.GetToken, while a change to App.User.Application.Query.Auth.GetToken can't break App.User.Application.Query.Auth.
- Position
- Below the diagonal: App.User.Application.Query.Auth.GetToken uses a module listed above it, which is the healthy direction.
30→26 App.User.Application.Query.Auth.GetToken uses App.User.Domain.Repository✕
- Connections
- 1 pair of types, where a type in App.User.Application.Query.Auth.GetToken uses a type in App.User.Domain.Repository.
- The types involved
App.User.Application.Query.Auth.GetToken.GetTokenHandler→App.User.Domain.Repository.GetUserCredentialsByEmailInterface
- Direction
- App.User.Application.Query.Auth.GetToken uses App.User.Domain.Repository, so a change to App.User.Domain.Repository can break App.User.Application.Query.Auth.GetToken, while a change to App.User.Application.Query.Auth.GetToken can't break App.User.Domain.Repository.
- Position
- Below the diagonal: App.User.Application.Query.Auth.GetToken uses a module listed above it, which is the healthy direction.
31→2 App.User.Application.Query.User.FindByEmail uses App.Shared.Application.Query✕
- Connections
- 3 pairs of types, where a type in App.User.Application.Query.User.FindByEmail uses a type in App.Shared.Application.Query.
- The types involved
App.User.Application.Query.User.FindByEmail.FindByEmailHandler→App.Shared.Application.Query.ItemApp.User.Application.Query.User.FindByEmail.FindByEmailHandler→App.Shared.Application.Query.QueryHandlerInterfaceApp.User.Application.Query.User.FindByEmail.FindByEmailQuery→App.Shared.Application.Query.QueryInterface
- Direction
- App.User.Application.Query.User.FindByEmail uses App.Shared.Application.Query, so a change to App.Shared.Application.Query can break App.User.Application.Query.User.FindByEmail, while a change to App.User.Application.Query.User.FindByEmail can't break App.Shared.Application.Query.
- Position
- Below the diagonal: App.User.Application.Query.User.FindByEmail uses a module listed above it, which is the healthy direction.
31→8 App.User.Application.Query.User.FindByEmail uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Application.Query.User.FindByEmail uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Application.Query.User.FindByEmail.FindByEmailQuery→App.User.Domain.ValueObject.Email
- Direction
- App.User.Application.Query.User.FindByEmail uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Application.Query.User.FindByEmail, while a change to App.User.Application.Query.User.FindByEmail can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Application.Query.User.FindByEmail uses a module listed above it, which is the healthy direction.
31→26 App.User.Application.Query.User.FindByEmail uses App.User.Domain.Repository✕
- Connections
- 1 pair of types, where a type in App.User.Application.Query.User.FindByEmail uses a type in App.User.Domain.Repository.
- The types involved
App.User.Application.Query.User.FindByEmail.FindByEmailHandler→App.User.Domain.Repository.UserReadModelRepositoryInterface
- Direction
- App.User.Application.Query.User.FindByEmail uses App.User.Domain.Repository, so a change to App.User.Domain.Repository can break App.User.Application.Query.User.FindByEmail, while a change to App.User.Application.Query.User.FindByEmail can't break App.User.Domain.Repository.
- Position
- Below the diagonal: App.User.Application.Query.User.FindByEmail uses a module listed above it, which is the healthy direction.
32→7 App.User.Infrastructure.ReadModel.Mysql uses App.Shared.Infrastructure.Persistence.ReadModel.Repository✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.ReadModel.Mysql uses a type in App.Shared.Infrastructure.Persistence.ReadModel.Repository.
- The types involved
App.User.Infrastructure.ReadModel.Mysql.MysqlReadModelUserRepository→App.Shared.Infrastructure.Persistence.ReadModel.Repository.MysqlRepository
- Direction
- App.User.Infrastructure.ReadModel.Mysql uses App.Shared.Infrastructure.Persistence.ReadModel.Repository, so a change to App.Shared.Infrastructure.Persistence.ReadModel.Repository can break App.User.Infrastructure.ReadModel.Mysql, while a change to App.User.Infrastructure.ReadModel.Mysql can't break App.Shared.Infrastructure.Persistence.ReadModel.Repository.
- Position
- Below the diagonal: App.User.Infrastructure.ReadModel.Mysql uses a module listed above it, which is the healthy direction.
32→8 App.User.Infrastructure.ReadModel.Mysql uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.ReadModel.Mysql uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Infrastructure.ReadModel.Mysql.MysqlReadModelUserRepository→App.User.Domain.ValueObject.Email
- Direction
- App.User.Infrastructure.ReadModel.Mysql uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Infrastructure.ReadModel.Mysql, while a change to App.User.Infrastructure.ReadModel.Mysql can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Infrastructure.ReadModel.Mysql uses a module listed above it, which is the healthy direction.
32→14 App.User.Infrastructure.ReadModel.Mysql uses App.User.Domain.ValueObject.Auth✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.ReadModel.Mysql uses a type in App.User.Domain.ValueObject.Auth.
- The types involved
App.User.Infrastructure.ReadModel.Mysql.MysqlReadModelUserRepository→App.User.Domain.ValueObject.Auth.UserCredentials
- Direction
- App.User.Infrastructure.ReadModel.Mysql uses App.User.Domain.ValueObject.Auth, so a change to App.User.Domain.ValueObject.Auth can break App.User.Infrastructure.ReadModel.Mysql, while a change to App.User.Infrastructure.ReadModel.Mysql can't break App.User.Domain.ValueObject.Auth.
- Position
- Below the diagonal: App.User.Infrastructure.ReadModel.Mysql uses a module listed above it, which is the healthy direction.
32→21 App.User.Infrastructure.ReadModel.Mysql uses App.User.Infrastructure.ReadModel✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.ReadModel.Mysql uses a type in App.User.Infrastructure.ReadModel.
- The types involved
App.User.Infrastructure.ReadModel.Mysql.MysqlReadModelUserRepository→App.User.Infrastructure.ReadModel.UserView
- Direction
- App.User.Infrastructure.ReadModel.Mysql uses App.User.Infrastructure.ReadModel, so a change to App.User.Infrastructure.ReadModel can break App.User.Infrastructure.ReadModel.Mysql, while a change to App.User.Infrastructure.ReadModel.Mysql can't break App.User.Infrastructure.ReadModel.
- Position
- Below the diagonal: App.User.Infrastructure.ReadModel.Mysql uses a module listed above it, which is the healthy direction.
32→26 App.User.Infrastructure.ReadModel.Mysql uses App.User.Domain.Repository✕
- Connections
- 3 pairs of types, where a type in App.User.Infrastructure.ReadModel.Mysql uses a type in App.User.Domain.Repository.
- The types involved
App.User.Infrastructure.ReadModel.Mysql.MysqlReadModelUserRepository→App.User.Domain.Repository.CheckUserByEmailInterfaceApp.User.Infrastructure.ReadModel.Mysql.MysqlReadModelUserRepository→App.User.Domain.Repository.GetUserCredentialsByEmailInterfaceApp.User.Infrastructure.ReadModel.Mysql.MysqlReadModelUserRepository→App.User.Domain.Repository.UserReadModelRepositoryInterface
- Direction
- App.User.Infrastructure.ReadModel.Mysql uses App.User.Domain.Repository, so a change to App.User.Domain.Repository can break App.User.Infrastructure.ReadModel.Mysql, while a change to App.User.Infrastructure.ReadModel.Mysql can't break App.User.Domain.Repository.
- Position
- Below the diagonal: App.User.Infrastructure.ReadModel.Mysql uses a module listed above it, which is the healthy direction.
33→23 App.User.Infrastructure.Repository uses App.User.Domain✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Repository uses a type in App.User.Domain.
- The types involved
App.User.Infrastructure.Repository.UserStore→App.User.Domain.User
- Direction
- App.User.Infrastructure.Repository uses App.User.Domain, so a change to App.User.Domain can break App.User.Infrastructure.Repository, while a change to App.User.Infrastructure.Repository can't break App.User.Domain.
- Position
- Below the diagonal: App.User.Infrastructure.Repository uses a module listed above it, which is the healthy direction.
33→26 App.User.Infrastructure.Repository uses App.User.Domain.Repository✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Repository uses a type in App.User.Domain.Repository.
- The types involved
App.User.Infrastructure.Repository.UserStore→App.User.Domain.Repository.UserRepositoryInterface
- Direction
- App.User.Infrastructure.Repository uses App.User.Domain.Repository, so a change to App.User.Domain.Repository can break App.User.Infrastructure.Repository, while a change to App.User.Infrastructure.Repository can't break App.User.Domain.Repository.
- Position
- Below the diagonal: App.User.Infrastructure.Repository uses a module listed above it, which is the healthy direction.
34→8 App.User.Infrastructure.Specification uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Specification uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Infrastructure.Specification.UniqueEmailSpecification→App.User.Domain.ValueObject.Email
- Direction
- App.User.Infrastructure.Specification uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Infrastructure.Specification, while a change to App.User.Infrastructure.Specification can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Infrastructure.Specification uses a module listed above it, which is the healthy direction.
34→13 App.User.Infrastructure.Specification uses App.User.Domain.Specification✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Specification uses a type in App.User.Domain.Specification.
- The types involved
App.User.Infrastructure.Specification.UniqueEmailSpecification→App.User.Domain.Specification.UniqueEmailSpecificationInterface
- Direction
- App.User.Infrastructure.Specification uses App.User.Domain.Specification, so a change to App.User.Domain.Specification can break App.User.Infrastructure.Specification, while a change to App.User.Infrastructure.Specification can't break App.User.Domain.Specification.
- Position
- Below the diagonal: App.User.Infrastructure.Specification uses a module listed above it, which is the healthy direction.
34→26 App.User.Infrastructure.Specification uses App.User.Domain.Repository✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Specification uses a type in App.User.Domain.Repository.
- The types involved
App.User.Infrastructure.Specification.UniqueEmailSpecification→App.User.Domain.Repository.CheckUserByEmailInterface
- Direction
- App.User.Infrastructure.Specification uses App.User.Domain.Repository, so a change to App.User.Domain.Repository can break App.User.Infrastructure.Specification, while a change to App.User.Infrastructure.Specification can't break App.User.Domain.Repository.
- Position
- Below the diagonal: App.User.Infrastructure.Specification uses a module listed above it, which is the healthy direction.
35→8 App.User.Infrastructure.Auth uses App.User.Domain.ValueObject✕
- Connections
- 2 pairs of types, where a type in App.User.Infrastructure.Auth uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Infrastructure.Auth.Auth→App.User.Domain.ValueObject.EmailApp.User.Infrastructure.Auth.AuthenticationProvider→App.User.Domain.ValueObject.Email
- Direction
- App.User.Infrastructure.Auth uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Infrastructure.Auth, while a change to App.User.Infrastructure.Auth can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Infrastructure.Auth uses a module listed above it, which is the healthy direction.
35→14 App.User.Infrastructure.Auth uses App.User.Domain.ValueObject.Auth✕
- Connections
- 2 pairs of types, where a type in App.User.Infrastructure.Auth uses a type in App.User.Domain.ValueObject.Auth.
- The types involved
App.User.Infrastructure.Auth.Auth→App.User.Domain.ValueObject.Auth.HashedPasswordApp.User.Infrastructure.Auth.AuthenticationProvider→App.User.Domain.ValueObject.Auth.HashedPassword
- Direction
- App.User.Infrastructure.Auth uses App.User.Domain.ValueObject.Auth, so a change to App.User.Domain.ValueObject.Auth can break App.User.Infrastructure.Auth, while a change to App.User.Infrastructure.Auth can't break App.User.Domain.ValueObject.Auth.
- Position
- Below the diagonal: App.User.Infrastructure.Auth uses a module listed above it, which is the healthy direction.
35→17 App.User.Infrastructure.Auth uses App.User.Application.Query.Auth✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Auth uses a type in App.User.Application.Query.Auth.
- The types involved
App.User.Infrastructure.Auth.AuthenticationProvider→App.User.Application.Query.Auth.AuthenticationProviderInterface
- Direction
- App.User.Infrastructure.Auth uses App.User.Application.Query.Auth, so a change to App.User.Application.Query.Auth can break App.User.Infrastructure.Auth, while a change to App.User.Infrastructure.Auth can't break App.User.Application.Query.Auth.
- Position
- Below the diagonal: App.User.Infrastructure.Auth uses a module listed above it, which is the healthy direction.
35→32 App.User.Infrastructure.Auth uses App.User.Infrastructure.ReadModel.Mysql✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.Auth uses a type in App.User.Infrastructure.ReadModel.Mysql.
- The types involved
App.User.Infrastructure.Auth.AuthProvider→App.User.Infrastructure.ReadModel.Mysql.MysqlReadModelUserRepository
- Direction
- App.User.Infrastructure.Auth uses App.User.Infrastructure.ReadModel.Mysql, so a change to App.User.Infrastructure.ReadModel.Mysql can break App.User.Infrastructure.Auth, while a change to App.User.Infrastructure.Auth can't break App.User.Infrastructure.ReadModel.Mysql.
- Position
- Below the diagonal: App.User.Infrastructure.Auth uses a module listed above it, which is the healthy direction.
36→18 App.User.Infrastructure.ReadModel.Projections uses App.User.Domain.Event✕
- Connections
- 3 pairs of types, where a type in App.User.Infrastructure.ReadModel.Projections uses a type in App.User.Domain.Event.
- The types involved
App.User.Infrastructure.ReadModel.Projections.ConsoleProjectionFactory→App.User.Domain.Event.UserSignedInApp.User.Infrastructure.ReadModel.Projections.UserProjectionFactory→App.User.Domain.Event.UserEmailChangedApp.User.Infrastructure.ReadModel.Projections.UserProjectionFactory→App.User.Domain.Event.UserWasCreated
- Direction
- App.User.Infrastructure.ReadModel.Projections uses App.User.Domain.Event, so a change to App.User.Domain.Event can break App.User.Infrastructure.ReadModel.Projections, while a change to App.User.Infrastructure.ReadModel.Projections can't break App.User.Domain.Event.
- Position
- Below the diagonal: App.User.Infrastructure.ReadModel.Projections uses a module listed above it, which is the healthy direction.
36→32 App.User.Infrastructure.ReadModel.Projections uses App.User.Infrastructure.ReadModel.Mysql✕
- Connections
- 1 pair of types, where a type in App.User.Infrastructure.ReadModel.Projections uses a type in App.User.Infrastructure.ReadModel.Mysql.
- The types involved
App.User.Infrastructure.ReadModel.Projections.UserProjectionFactory→App.User.Infrastructure.ReadModel.Mysql.MysqlReadModelUserRepository
- Direction
- App.User.Infrastructure.ReadModel.Projections uses App.User.Infrastructure.ReadModel.Mysql, so a change to App.User.Infrastructure.ReadModel.Mysql can break App.User.Infrastructure.ReadModel.Projections, while a change to App.User.Infrastructure.ReadModel.Projections can't break App.User.Infrastructure.ReadModel.Mysql.
- Position
- Below the diagonal: App.User.Infrastructure.ReadModel.Projections uses a module listed above it, which is the healthy direction.
37→12 UI.Http.Rest.Controller.Healthz uses App.Shared.Infrastructure.Event.ReadModel✕
- Connections
- 1 pair of types, where a type in UI.Http.Rest.Controller.Healthz uses a type in App.Shared.Infrastructure.Event.ReadModel.
- The types involved
UI.Http.Rest.Controller.Healthz.HealthzController→App.Shared.Infrastructure.Event.ReadModel.ElasticSearchEventRepository
- Direction
- UI.Http.Rest.Controller.Healthz uses App.Shared.Infrastructure.Event.ReadModel, so a change to App.Shared.Infrastructure.Event.ReadModel can break UI.Http.Rest.Controller.Healthz, while a change to UI.Http.Rest.Controller.Healthz can't break App.Shared.Infrastructure.Event.ReadModel.
- Position
- Below the diagonal: UI.Http.Rest.Controller.Healthz uses a module listed above it, which is the healthy direction.
37→15 UI.Http.Rest.Controller.Healthz uses UI.Http.Rest.Response✕
- Connections
- 1 pair of types, where a type in UI.Http.Rest.Controller.Healthz uses a type in UI.Http.Rest.Response.
- The types involved
UI.Http.Rest.Controller.Healthz.HealthzController→UI.Http.Rest.Response.OpenApi
- Direction
- UI.Http.Rest.Controller.Healthz uses UI.Http.Rest.Response, so a change to UI.Http.Rest.Response can break UI.Http.Rest.Controller.Healthz, while a change to UI.Http.Rest.Controller.Healthz can't break UI.Http.Rest.Response.
- Position
- Below the diagonal: UI.Http.Rest.Controller.Healthz uses a module listed above it, which is the healthy direction.
37→32 UI.Http.Rest.Controller.Healthz uses App.User.Infrastructure.ReadModel.Mysql✕
- Connections
- 1 pair of types, where a type in UI.Http.Rest.Controller.Healthz uses a type in App.User.Infrastructure.ReadModel.Mysql.
- The types involved
UI.Http.Rest.Controller.Healthz.HealthzController→App.User.Infrastructure.ReadModel.Mysql.MysqlReadModelUserRepository
- Direction
- UI.Http.Rest.Controller.Healthz uses App.User.Infrastructure.ReadModel.Mysql, so a change to App.User.Infrastructure.ReadModel.Mysql can break UI.Http.Rest.Controller.Healthz, while a change to UI.Http.Rest.Controller.Healthz can't break App.User.Infrastructure.ReadModel.Mysql.
- Position
- Below the diagonal: UI.Http.Rest.Controller.Healthz uses a module listed above it, which is the healthy direction.
38→2 App.User.Application.Query.Auth.GetAuthUserByEmail uses App.Shared.Application.Query✕
- Connections
- 2 pairs of types, where a type in App.User.Application.Query.Auth.GetAuthUserByEmail uses a type in App.Shared.Application.Query.
- The types involved
App.User.Application.Query.Auth.GetAuthUserByEmail.GetAuthUserByEmailHandler→App.Shared.Application.Query.QueryHandlerInterfaceApp.User.Application.Query.Auth.GetAuthUserByEmail.GetAuthUserByEmailQuery→App.Shared.Application.Query.QueryInterface
- Direction
- App.User.Application.Query.Auth.GetAuthUserByEmail uses App.Shared.Application.Query, so a change to App.Shared.Application.Query can break App.User.Application.Query.Auth.GetAuthUserByEmail, while a change to App.User.Application.Query.Auth.GetAuthUserByEmail can't break App.Shared.Application.Query.
- Position
- Below the diagonal: App.User.Application.Query.Auth.GetAuthUserByEmail uses a module listed above it, which is the healthy direction.
38→8 App.User.Application.Query.Auth.GetAuthUserByEmail uses App.User.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in App.User.Application.Query.Auth.GetAuthUserByEmail uses a type in App.User.Domain.ValueObject.
- The types involved
App.User.Application.Query.Auth.GetAuthUserByEmail.GetAuthUserByEmailQuery→App.User.Domain.ValueObject.Email
- Direction
- App.User.Application.Query.Auth.GetAuthUserByEmail uses App.User.Domain.ValueObject, so a change to App.User.Domain.ValueObject can break App.User.Application.Query.Auth.GetAuthUserByEmail, while a change to App.User.Application.Query.Auth.GetAuthUserByEmail can't break App.User.Domain.ValueObject.
- Position
- Below the diagonal: App.User.Application.Query.Auth.GetAuthUserByEmail uses a module listed above it, which is the healthy direction.
38→26 App.User.Application.Query.Auth.GetAuthUserByEmail uses App.User.Domain.Repository✕
- Connections
- 1 pair of types, where a type in App.User.Application.Query.Auth.GetAuthUserByEmail uses a type in App.User.Domain.Repository.
- The types involved
App.User.Application.Query.Auth.GetAuthUserByEmail.GetAuthUserByEmailHandler→App.User.Domain.Repository.GetUserCredentialsByEmailInterface
- Direction
- App.User.Application.Query.Auth.GetAuthUserByEmail uses App.User.Domain.Repository, so a change to App.User.Domain.Repository can break App.User.Application.Query.Auth.GetAuthUserByEmail, while a change to App.User.Application.Query.Auth.GetAuthUserByEmail can't break App.User.Domain.Repository.
- Position
- Below the diagonal: App.User.Application.Query.Auth.GetAuthUserByEmail uses a module listed above it, which is the healthy direction.
38→35 App.User.Application.Query.Auth.GetAuthUserByEmail uses App.User.Infrastructure.Auth✕
- Connections
- 1 pair of types, where a type in App.User.Application.Query.Auth.GetAuthUserByEmail uses a type in App.User.Infrastructure.Auth.
- The types involved
App.User.Application.Query.Auth.GetAuthUserByEmail.GetAuthUserByEmailHandler→App.User.Infrastructure.Auth.Auth
- Direction
- App.User.Application.Query.Auth.GetAuthUserByEmail uses App.User.Infrastructure.Auth, so a change to App.User.Infrastructure.Auth can break App.User.Application.Query.Auth.GetAuthUserByEmail, while a change to App.User.Application.Query.Auth.GetAuthUserByEmail can't break App.User.Infrastructure.Auth.
- Position
- Below the diagonal: App.User.Application.Query.Auth.GetAuthUserByEmail uses a module listed above it, which is the healthy direction.
39→35 UI.Http uses App.User.Infrastructure.Auth✕
- Connections
- 1 pair of types, where a type in UI.Http uses a type in App.User.Infrastructure.Auth.
- The types involved
UI.Http.Session→App.User.Infrastructure.Auth.Auth
- Direction
- UI.Http uses App.User.Infrastructure.Auth, so a change to App.User.Infrastructure.Auth can break UI.Http, while a change to UI.Http can't break App.User.Infrastructure.Auth.
- Position
- Below the diagonal: UI.Http uses a module listed above it, which is the healthy direction.
40→1 UI.Http.Rest.Controller.User uses App.Shared.Application.Command✕
- Connections
- 1 pair of types, where a type in UI.Http.Rest.Controller.User uses a type in App.Shared.Application.Command.
- The types involved
UI.Http.Rest.Controller.User.UserChangeEmailController→App.Shared.Application.Command.CommandBusInterface
- Direction
- UI.Http.Rest.Controller.User uses App.Shared.Application.Command, so a change to App.Shared.Application.Command can break UI.Http.Rest.Controller.User, while a change to UI.Http.Rest.Controller.User can't break App.Shared.Application.Command.
- Position
- Below the diagonal: UI.Http.Rest.Controller.User uses a module listed above it, which is the healthy direction.
40→15 UI.Http.Rest.Controller.User uses UI.Http.Rest.Response✕
- Connections
- 2 pairs of types, where a type in UI.Http.Rest.Controller.User uses a type in UI.Http.Rest.Response.
- The types involved
UI.Http.Rest.Controller.User.GetUserByEmailController→UI.Http.Rest.Response.OpenApiUI.Http.Rest.Controller.User.SignUpController→UI.Http.Rest.Response.OpenApi
- Direction
- UI.Http.Rest.Controller.User uses UI.Http.Rest.Response, so a change to UI.Http.Rest.Response can break UI.Http.Rest.Controller.User, while a change to UI.Http.Rest.Controller.User can't break UI.Http.Rest.Response.
- Position
- Below the diagonal: UI.Http.Rest.Controller.User uses a module listed above it, which is the healthy direction.
40→22 UI.Http.Rest.Controller.User uses UI.Http.Rest.Controller✕
- Connections
- 3 pairs of types, where a type in UI.Http.Rest.Controller.User uses a type in UI.Http.Rest.Controller.
- The types involved
UI.Http.Rest.Controller.User.GetUserByEmailController→UI.Http.Rest.Controller.QueryControllerUI.Http.Rest.Controller.User.SignUpController→UI.Http.Rest.Controller.CommandControllerUI.Http.Rest.Controller.User.UserChangeEmailController→UI.Http.Rest.Controller.CommandController
- Direction
- UI.Http.Rest.Controller.User uses UI.Http.Rest.Controller, so a change to UI.Http.Rest.Controller can break UI.Http.Rest.Controller.User, while a change to UI.Http.Rest.Controller.User can't break UI.Http.Rest.Controller.
- Position
- Below the diagonal: UI.Http.Rest.Controller.User uses a module listed above it, which is the healthy direction.
40→39 UI.Http.Rest.Controller.User uses UI.Http✕
- Connections
- 1 pair of types, where a type in UI.Http.Rest.Controller.User uses a type in UI.Http.
- The types involved
UI.Http.Rest.Controller.User.UserChangeEmailController→UI.Http.Session
- Direction
- UI.Http.Rest.Controller.User uses UI.Http, so a change to UI.Http can break UI.Http.Rest.Controller.User, while a change to UI.Http.Rest.Controller.User can't break UI.Http.
- Position
- Below the diagonal: UI.Http.Rest.Controller.User uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event Sourcing
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 15 | High / Critical |
| A05:2025 — Injection | 7 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 2 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +8.3 pts | Medium | Keyboard semantics |
| Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with User.php, MysqlReadModelUserRepository.php, LoginAuthenticator.php. | +4.0 pts | Low | Knowledge Freshness |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +5.2 pts | Medium | A11y enforcement |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +4.5 pts | Medium | Page structure |
| 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. | +3.8 pts | Medium | Architecture documentation |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.6 pts | Low | Bus Factor |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.8 pts | Low | Knowledge Freshness |
| Resolve the 2 Abandoned package finding(s) in Dependency Hygiene. | +0.3 pts | Low | Dependency Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 6.1 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 68 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 68 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, 46 of 62 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- 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.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/App/Shared/Application/Query/Collection.php`, `src/App/Shared/Application/Query/Event/GetEvents/GetEventsHandler.php`, `src/App/Shared/Application/Query/Event/GetEvents/GetEventsQuery.php`, `src/App/Shared/Application/Query/Item.php`, `src/App/Shared/Infrastructure/Bus/AsyncEvent/MessengerAsyncEventBus.php`, … (+42 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D41 Kernel & Syscall Confinement — 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. Etc/artifact/chart/templates/deployment-worker.yaml:2, REDACTED:2, REDACTED:2 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Symfony DependencyInjection, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (docker-compose.ci.yml). compose up failed (exit 15 — the compose project is invalid) — empty compose file; runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- ES3 PII in the event store — 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 persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D6 · Cohesion (LCOM4)
0 of 20 classes have LCOM4 above 3.
D9 · Test Distribution
27 test methods: 27 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 27 tests.
D12 · Dependency Hygiene
4 outdated, 2 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question. An ABANDONED package is a migration rather than an upgrade: it receives no further releases at all, including security releases.
What to do
- Resolve the 2 Abandoned package finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 91 locked Composer package(s) use a banned license. Licences were read from this repository's REDACTED, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 53 package(s) under `packages-dev` are not installed for a consumer and are excluded.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/App/User/Infrastructure/Auth/Guard/LoginAuthenticator.php. Counted over 9 of the 96 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 4826 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. 8 document(s) read across 1 unit(s).
D27 · Navigability
45 % of calls cross a namespace and 12 % go through an interface, but 71 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 3 high, 4 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 57 file(s) — `etc/artifact/chart/config/parameters.yaml`, `REDACTED`, `REDACTED`, `etc/artifact/chart/templates/hpa.yaml`, `etc/artifact/chart/templates/ingress.yaml`, … (+52 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
15 finding(s): 1 critical, 1 high, 12 medium, 1 low.
What to do
- Resolve the 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 12 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (12 warning-level).
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/App/User/Domain/User.php. Counted over 9 of the 96 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, MysqlReadModelUserRepository.php, LoginAuthenticator.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.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
No workload manifest could be read as a pod spec, so no confinement was judged.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 23 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
AC2 · Forms & labels
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — src/UI/Http/Web/templates/base.html.twig:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/UI/Http/Web/templates/base.html.twig:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — REDACTED:15
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 8 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — Gate abilities and policy classes (Gate::define, a UserPolicy), spatie/laravel-permission roles and permissions, or a Symfony Voter — and consult them where access is checked ($this->authorize, a can: middleware, #[IsGranted]), so the rule set is reviewable and testable on its own.
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
ES1 · Fold determinism
ES2 · Immutable events
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (opentelemetry-php) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P8 · Schema migrations
S1 · Web-Security Posture
- Set: Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Content-Security-Policy, Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−1.0 on this card.) — etc/prod/nginx/nginx.conf:1
What to do
- Add Content-Security-Policy, Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/UI/Http/Rest/EventSubscriber/JsonBodyParserSubscriber.php:56
- `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/App/Shared/Infrastructure/Persistence/ReadModel/Repository/ElasticSearchRepository.php:106
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- 1/2 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
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.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Strong | Solid. |
| Architecture | 77% | Strong | Solid. |
| Maturity | 60% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 75% | Exemplary | Solid. |
| Security | 75% | Strong | Solid. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Event Sourcing | 100% | Exemplary | Solid. |
| Accessibility | 46% | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 2 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 60 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — empty compose file; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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.
- 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.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; PHP not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (User), 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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (4812 LoC, 95 module-visible types across 52 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D32 Data Compliance (PII/GDPR) — 47 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
- D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES3 PII in the event store — This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the PHP source (service entry point: src/UI/Http/Web/Controller/HomeController.php:21 (#[Route())
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang src/UI/Http/Web/templates/base.html.twig:2
- REDACTED
- REDACTED
- REDACTED
Serious — 26 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Abandoned package: broadway/broadway-bundle
- Abandoned package: broadway/event-store-dbal
- REDACTED
- REDACTED
- Swallowed exception (caught, then discarded) src/UI/Http/Rest/EventSubscriber/JsonBodyParserSubscriber.php:56
- Swallowed exception (caught, then discarded) src/App/Shared/Infrastructure/Persistence/ReadModel/Repository/ElasticSearchRepository.php:106
- Page without a main landmark src/UI/Http/Web/templates/base.html.twig:2
- Anchor without href REDACTED:15
- Accessibility enforcement below the top rung
- REDACTED
- Coverage collected but not gated
Minor — 19 finding(s)
- Orphaned file src/App/User/Domain/User.php:1
- Orphaned file src/App/User/Infrastructure/ReadModel/Mysql/MysqlReadModelUserRepository.php:1
- Orphaned file src/App/User/Infrastructure/Auth/Guard/LoginAuthenticator.php:1
- Orphaned file src/UI/Http/Rest/EventSubscriber/ExceptionSubscriber.php:1
- Orphaned file src/App/Shared/Infrastructure/Persistence/ReadModel/Repository/ElasticSearchRepository.php:1
- Orphaned file src/App/Shared/Infrastructure/Persistence/ReadModel/Repository/MysqlRepository.php:1
- Orphaned file src/App/User/Infrastructure/ReadModel/UserView.php:1
- Orphaned file src/UI/Http/Rest/Response/OpenApi.php:1
- Orphaned file src/UI/Http/Web/Controller/SignUpController.php:1
- No named authorization policies
- Off-boarding risk: anonymized user #1
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No network policy
- No ADRs
- Security headers incomplete etc/prod/nginx/nginx.conf:1
- PHP static analysis does not check null everywhere
Minor — 4 finding(s)
- Outdated: beberlei/assert
- Outdated: doctrine/orm
- Outdated: ramsey/uuid
- Outdated: symfony/flex
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-0d0ce1194c2c4ac7a0a3460975c464a3/history.json --exit-code 0 --source . | 5 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0d0ce1194c2c4ac7a0a3460975c464a3/tree.json --exit-code 0 --source . | 3 | 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 . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 15 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 47 file(s) — `src/App/Shared/Application/Query/Collection.php`, `src/App/Shared/Application/Query/Event/GetEvents/GetEventsHandler.php`, `src/App/Shared/Application/Query/Event/GetEvents/GetEventsQuery.php`, `src/App/Shared/Application/Query/Item.php`, `src/App/Shared/Infrastructure/Bus/AsyncEvent/MessengerAsyncEventBus.php`, … (+42 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |