Executive summary
Andyhacool/HRM is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because two passwords or keys sit in the current code and we found no working pipeline that builds or tests changes to the code. It scores 40 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 30, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 8 points. Making the tests check their results comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 48.
Nine known security holes in the packages the code depends on can be used by attackers. Two passwords or keys in the code and one in the code's history are open to anyone who can read the repository. Updating the vulnerable packages and replacing each exposed password or key would close both risks. Hashing passwords with a password-hashing function such as Argon2, bcrypt or PBKDF2 would fix the place where passwords are scrambled with a fast general-purpose hash. The four data fields that are written but never read need removing.
The product code is 3,018 lines, about €4,000 to rebuild.
If Production Readiness rose from 30 to 70, the lowest score rated Strong, the score would rise from 40 to about 48.
New since the last survey: 12 findings
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 src/HRM.Domain/HRM.Domain.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 src/HRM.Infra.CrossCutting.Bus/HRM.Infra.CrossCutting.Bus.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 src/HRM.Infra.CrossCutting.IoC/HRM.Infra.CrossCutting.IoC.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 src/HRM.Infra.IdentityTest/HRM.Infra.IdentityUnitTests.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 src/HRM.Infrastructure.UnitTests/HRM.Infrastructure.UnitTests.csproj
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 REDACTED
- Ambient inputs in the domain · Domain type reads the wall clock: RefreshToken src/HRM.Domain/Entities/Identity/RefreshToken.cs
Fixed since the last survey: 8 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Dependency Hygiene · Vulnerable: AutoMapper
- Dependency Hygiene · Vulnerable: Microsoft.NETCore.App
- Dependency Hygiene · Vulnerable: Microsoft.AspNetCore.App
- Dependency Hygiene · Vulnerable: System.IdentityModel.Tokens.Jwt
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 REDACTED
- Rich vs anemic model · Anemic entity: User src/HRM.Domain/Entities/Identity/User.cs
- Repository granularity · Repository for a non-root entity: IUserRepository → User src/HRM.Domain/Interfaces/IUserRepository.cs
Rebuild cost: about €4,000 · Estimate
| Cost to rebuild | €1,400 to €6,700, for 23 to 71 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 40. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,018 lines of product code, of which 54% is declarations and boilerplate, 40% straight logic and 6% logic with branches |
| 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Domain.Core.Bus | 2 Domain.Core.Events | 3 Domain.Core.Model | 4 Infra.CrossCutting.Identity.Context | 5 Infra.CrossCutting.Identity.Dto | 6 Domain.Core.Commands | 7 Domain.Core.Notifications | 8 Domain.Events | 9 Domain.Models | 10 Domain.SharedKernel | 11 Infra.CrossCutting.Bus | 12 Infra.CrossCutting.Identity.Events | 13 Infra.CrossCutting.Identity.Interfaces.Services | 14 Infra.CrossCutting.Identity.Models | 15 Infra.CrossCutting.Identity.Responses | 16 Application.ViewModels | 17 Domain | 18 Domain.Commands | 19 Domain.EventHandlers | 20 Domain.Models.Identity | 21 Infra.CrossCutting.Identity.EventHandlers | 22 Infra.CrossCutting.Identity.Requests | 23 Application.Interfaces | 24 Domain.Interfaces | 25 Infra.Data.Context | 26 Infra.Data.Mappings | 27 Domain.CommandHandlers | 28 Infra.CrossCutting.Identity.Interfaces | 29 Infra.CrossCutting.Identity.Presenters | 30 Infra.Data.Repository | 31 Infra.Data.Repository.EventSourcing | 32 Infra.Data.Specifications | 33 Infra.Data.UoW | 34 WebApi.Controllers | 35 Application.Services | 36 Infra.CrossCutting.Identity.Auth | 37 Infra.CrossCutting.Identity.AuthHandlers | 38 Infra.CrossCutting.Identity.Repositories | 39 Infra.CrossCutting.Identity.UseCaseHandlers | 40 Infra.Data.EventSourcing |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Domain.Core.Bus | ||||||||||||||||||||||||||||||||||||||||
| 2 Domain.Core.Events | ||||||||||||||||||||||||||||||||||||||||
| 3 Domain.Core.Model | ||||||||||||||||||||||||||||||||||||||||
| 4 Infra.CrossCutting.Identity.Context | ||||||||||||||||||||||||||||||||||||||||
| 5 Infra.CrossCutting.Identity.Dto | ||||||||||||||||||||||||||||||||||||||||
| 6 Domain.Core.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 Domain.Core.Notifications | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 Domain.Events | 3 | |||||||||||||||||||||||||||||||||||||||
| 9 Domain.Models | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 Domain.SharedKernel | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Infra.CrossCutting.Bus | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Infra.CrossCutting.Identity.Events | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Infra.CrossCutting.Identity.Interfaces.Services | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Infra.CrossCutting.Identity.Models | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Infra.CrossCutting.Identity.Responses | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 Application.ViewModels | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Domain | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 Domain.Commands | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 Domain.EventHandlers | 3 | |||||||||||||||||||||||||||||||||||||||
| 20 Domain.Models.Identity | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Infra.CrossCutting.Identity.EventHandlers | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Infra.CrossCutting.Identity.Requests | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Application.Interfaces | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 24 Domain.Interfaces | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Infra.Data.Context | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Infra.Data.Mappings | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Domain.CommandHandlers | 2 | 1 | 3 | 3 | 3 | |||||||||||||||||||||||||||||||||||
| 28 Infra.CrossCutting.Identity.Interfaces | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 Infra.CrossCutting.Identity.Presenters | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 Infra.Data.Repository | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 Infra.Data.Repository.EventSourcing | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Infra.Data.Specifications | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 Infra.Data.UoW | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 WebApi.Controllers | 2 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 Application.Services | 2 | 3 | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||
| 36 Infra.CrossCutting.Identity.Auth | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 37 Infra.CrossCutting.Identity.AuthHandlers | 1 | 1 | 2 | 1 | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 38 Infra.CrossCutting.Identity.Repositories | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 Infra.CrossCutting.Identity.UseCaseHandlers | 2 | 2 | 3 | 1 | 1 | 2 | 5 | 2 | 2 | |||||||||||||||||||||||||||||||
| 40 Infra.Data.EventSourcing | 1 | 1 | 1 |
6→2 Domain.Core.Commands uses Domain.Core.Events✕
- Connections
- 1 pair of types, where a type in Domain.Core.Commands uses a type in Domain.Core.Events.
- The types involved
HRM.Domain.Core.Commands.Command→HRM.Domain.Core.Events.Message
- Direction
- Domain.Core.Commands uses Domain.Core.Events, so a change to Domain.Core.Events can break Domain.Core.Commands, while a change to Domain.Core.Commands can't break Domain.Core.Events.
- Position
- Below the diagonal: Domain.Core.Commands uses a module listed above it, which is the healthy direction.
7→2 Domain.Core.Notifications uses Domain.Core.Events✕
- Connections
- 1 pair of types, where a type in Domain.Core.Notifications uses a type in Domain.Core.Events.
- The types involved
HRM.Domain.Core.Notifications.DomainNotification→HRM.Domain.Core.Events.Event
- Direction
- Domain.Core.Notifications uses Domain.Core.Events, so a change to Domain.Core.Events can break Domain.Core.Notifications, while a change to Domain.Core.Notifications can't break Domain.Core.Events.
- Position
- Below the diagonal: Domain.Core.Notifications uses a module listed above it, which is the healthy direction.
8→2 Domain.Events uses Domain.Core.Events✕
- Connections
- 3 pairs of types, where a type in Domain.Events uses a type in Domain.Core.Events.
- The types involved
HRM.Domain.Events.EmployeeRegisteredEvent→HRM.Domain.Core.Events.EventHRM.Domain.Events.EmployeeRemovedEvent→HRM.Domain.Core.Events.EventHRM.Domain.Events.EmployeeUpdatedEvent→HRM.Domain.Core.Events.Event
- Direction
- Domain.Events uses Domain.Core.Events, so a change to Domain.Core.Events can break Domain.Events, while a change to Domain.Events can't break Domain.Core.Events.
- Position
- Below the diagonal: Domain.Events uses a module listed above it, which is the healthy direction.
9→3 Domain.Models uses Domain.Core.Model✕
- Connections
- 2 pairs of types, where a type in Domain.Models uses a type in Domain.Core.Model.
- The types involved
HRM.Domain.Models.Person→HRM.Domain.Core.Model.ValueObjectHRM.Domain.Models.RefreshToken→HRM.Domain.Core.Model.Entity
- Direction
- Domain.Models uses Domain.Core.Model, so a change to Domain.Core.Model can break Domain.Models, while a change to Domain.Models can't break Domain.Core.Model.
- Position
- Below the diagonal: Domain.Models uses a module listed above it, which is the healthy direction.
10→3 Domain.SharedKernel uses Domain.Core.Model✕
- Connections
- 1 pair of types, where a type in Domain.SharedKernel uses a type in Domain.Core.Model.
- The types involved
HRM.Domain.SharedKernel.Address→HRM.Domain.Core.Model.ValueObject
- Direction
- Domain.SharedKernel uses Domain.Core.Model, so a change to Domain.Core.Model can break Domain.SharedKernel, while a change to Domain.SharedKernel can't break Domain.Core.Model.
- Position
- Below the diagonal: Domain.SharedKernel uses a module listed above it, which is the healthy direction.
11→1 Infra.CrossCutting.Bus uses Domain.Core.Bus✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Bus uses a type in Domain.Core.Bus.
- The types involved
HRM.Infra.CrossCutting.Bus.InMemoryBus→HRM.Domain.Core.Bus.IMediatorHandler
- Direction
- Infra.CrossCutting.Bus uses Domain.Core.Bus, so a change to Domain.Core.Bus can break Infra.CrossCutting.Bus, while a change to Infra.CrossCutting.Bus can't break Domain.Core.Bus.
- Position
- Below the diagonal: Infra.CrossCutting.Bus uses a module listed above it, which is the healthy direction.
11→2 Infra.CrossCutting.Bus uses Domain.Core.Events✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Bus uses a type in Domain.Core.Events.
- The types involved
HRM.Infra.CrossCutting.Bus.InMemoryBus→HRM.Domain.Core.Events.IEventStore
- Direction
- Infra.CrossCutting.Bus uses Domain.Core.Events, so a change to Domain.Core.Events can break Infra.CrossCutting.Bus, while a change to Infra.CrossCutting.Bus can't break Domain.Core.Events.
- Position
- Below the diagonal: Infra.CrossCutting.Bus uses a module listed above it, which is the healthy direction.
12→2 Infra.CrossCutting.Identity.Events uses Domain.Core.Events✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.Events uses a type in Domain.Core.Events.
- The types involved
HRM.Infra.CrossCutting.Identity.Events.UserRegisteredEvent→HRM.Domain.Core.Events.Event
- Direction
- Infra.CrossCutting.Identity.Events uses Domain.Core.Events, so a change to Domain.Core.Events can break Infra.CrossCutting.Identity.Events, while a change to Infra.CrossCutting.Identity.Events can't break Domain.Core.Events.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Events uses a module listed above it, which is the healthy direction.
13→5 Infra.CrossCutting.Identity.Interfaces.Services uses Infra.CrossCutting.Identity.Dto✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.Interfaces.Services uses a type in Infra.CrossCutting.Identity.Dto.
- The types involved
HRM.Infra.CrossCutting.Identity.Interfaces.Services.IJwtFactory→HRM.Infra.CrossCutting.Identity.Dto.AccessToken
- Direction
- Infra.CrossCutting.Identity.Interfaces.Services uses Infra.CrossCutting.Identity.Dto, so a change to Infra.CrossCutting.Identity.Dto can break Infra.CrossCutting.Identity.Interfaces.Services, while a change to Infra.CrossCutting.Identity.Interfaces.Services can't break Infra.CrossCutting.Identity.Dto.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Interfaces.Services uses a module listed above it, which is the healthy direction.
14→4 Infra.CrossCutting.Identity.Models uses Infra.CrossCutting.Identity.Context✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.Models uses a type in Infra.CrossCutting.Identity.Context.
- The types involved
HRM.Infra.CrossCutting.Identity.Models.AppIdentityDbContextFactory→HRM.Infra.CrossCutting.Identity.Context.AppIdentityDbContext
- Direction
- Infra.CrossCutting.Identity.Models uses Infra.CrossCutting.Identity.Context, so a change to Infra.CrossCutting.Identity.Context can break Infra.CrossCutting.Identity.Models, while a change to Infra.CrossCutting.Identity.Models can't break Infra.CrossCutting.Identity.Context.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Models uses a module listed above it, which is the healthy direction.
15→5 Infra.CrossCutting.Identity.Responses uses Infra.CrossCutting.Identity.Dto✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.Responses uses a type in Infra.CrossCutting.Identity.Dto.
- The types involved
HRM.Infra.CrossCutting.Identity.Responses.ExchangeRefreshTokenResponse→HRM.Infra.CrossCutting.Identity.Dto.AccessTokenHRM.Infra.CrossCutting.Identity.Responses.LoginResponse→HRM.Infra.CrossCutting.Identity.Dto.AccessToken
- Direction
- Infra.CrossCutting.Identity.Responses uses Infra.CrossCutting.Identity.Dto, so a change to Infra.CrossCutting.Identity.Dto can break Infra.CrossCutting.Identity.Responses, while a change to Infra.CrossCutting.Identity.Responses can't break Infra.CrossCutting.Identity.Dto.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Responses uses a module listed above it, which is the healthy direction.
16→9 Application.ViewModels uses Domain.Models✕
- Connections
- 1 pair of types, where a type in Application.ViewModels uses a type in Domain.Models.
- The types involved
HRM.Application.ViewModels.EmployeeViewModel→HRM.Domain.Models.Gender
- Direction
- Application.ViewModels uses Domain.Models, so a change to Domain.Models can break Application.ViewModels, while a change to Application.ViewModels can't break Domain.Models.
- Position
- Below the diagonal: Application.ViewModels uses a module listed above it, which is the healthy direction.
17→3 Domain uses Domain.Core.Model✕
- Connections
- 1 pair of types, where a type in Domain uses a type in Domain.Core.Model.
- The types involved
HRM.Domain.Employee→HRM.Domain.Core.Model.AggregateRoot
- Direction
- Domain uses Domain.Core.Model, so a change to Domain.Core.Model can break Domain, while a change to Domain can't break Domain.Core.Model.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
17→9 Domain uses Domain.Models✕
- Connections
- 2 pairs of types, where a type in Domain uses a type in Domain.Models.
- The types involved
HRM.Domain.Employee→HRM.Domain.Models.GenderHRM.Domain.Employee→HRM.Domain.Models.Person
- Direction
- Domain uses Domain.Models, so a change to Domain.Models can break Domain, while a change to Domain can't break Domain.Models.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
17→10 Domain uses Domain.SharedKernel✕
- Connections
- 1 pair of types, where a type in Domain uses a type in Domain.SharedKernel.
- The types involved
HRM.Domain.Employee→HRM.Domain.SharedKernel.Address
- Direction
- Domain uses Domain.SharedKernel, so a change to Domain.SharedKernel can break Domain, while a change to Domain can't break Domain.SharedKernel.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
18→6 Domain.Commands uses Domain.Core.Commands✕
- Connections
- 1 pair of types, where a type in Domain.Commands uses a type in Domain.Core.Commands.
- The types involved
HRM.Domain.Commands.EmployeeCommand→HRM.Domain.Core.Commands.Command
- Direction
- Domain.Commands uses Domain.Core.Commands, so a change to Domain.Core.Commands can break Domain.Commands, while a change to Domain.Commands can't break Domain.Core.Commands.
- Position
- Below the diagonal: Domain.Commands uses a module listed above it, which is the healthy direction.
18→9 Domain.Commands uses Domain.Models✕
- Connections
- 2 pairs of types, where a type in Domain.Commands uses a type in Domain.Models.
- The types involved
HRM.Domain.Commands.EmployeeCommand→HRM.Domain.Models.GenderHRM.Domain.Commands.RegisterNewEmployeeCommand→HRM.Domain.Models.Gender
- Direction
- Domain.Commands uses Domain.Models, so a change to Domain.Models can break Domain.Commands, while a change to Domain.Commands can't break Domain.Models.
- Position
- Below the diagonal: Domain.Commands uses a module listed above it, which is the healthy direction.
19→8 Domain.EventHandlers uses Domain.Events✕
- Connections
- 3 pairs of types, where a type in Domain.EventHandlers uses a type in Domain.Events.
- The types involved
HRM.Domain.EventHandlers.EmployeeEventHandler→HRM.Domain.Events.EmployeeRegisteredEventHRM.Domain.EventHandlers.EmployeeEventHandler→HRM.Domain.Events.EmployeeRemovedEventHRM.Domain.EventHandlers.EmployeeEventHandler→HRM.Domain.Events.EmployeeUpdatedEvent
- Direction
- Domain.EventHandlers uses Domain.Events, so a change to Domain.Events can break Domain.EventHandlers, while a change to Domain.EventHandlers can't break Domain.Events.
- Position
- Below the diagonal: Domain.EventHandlers uses a module listed above it, which is the healthy direction.
20→3 Domain.Models.Identity uses Domain.Core.Model✕
- Connections
- 1 pair of types, where a type in Domain.Models.Identity uses a type in Domain.Core.Model.
- The types involved
HRM.Domain.Models.Identity.User→HRM.Domain.Core.Model.Entity
- Direction
- Domain.Models.Identity uses Domain.Core.Model, so a change to Domain.Core.Model can break Domain.Models.Identity, while a change to Domain.Models.Identity can't break Domain.Core.Model.
- Position
- Below the diagonal: Domain.Models.Identity uses a module listed above it, which is the healthy direction.
20→9 Domain.Models.Identity uses Domain.Models✕
- Connections
- 1 pair of types, where a type in Domain.Models.Identity uses a type in Domain.Models.
- The types involved
HRM.Domain.Models.Identity.User→HRM.Domain.Models.RefreshToken
- Direction
- Domain.Models.Identity uses Domain.Models, so a change to Domain.Models can break Domain.Models.Identity, while a change to Domain.Models.Identity can't break Domain.Models.
- Position
- Below the diagonal: Domain.Models.Identity uses a module listed above it, which is the healthy direction.
21→12 Infra.CrossCutting.Identity.EventHandlers uses Infra.CrossCutting.Identity.Events✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.EventHandlers uses a type in Infra.CrossCutting.Identity.Events.
- The types involved
HRM.Infra.CrossCutting.Identity.EventHandlers.UserEventHandler→HRM.Infra.CrossCutting.Identity.Events.UserRegisteredEvent
- Direction
- Infra.CrossCutting.Identity.EventHandlers uses Infra.CrossCutting.Identity.Events, so a change to Infra.CrossCutting.Identity.Events can break Infra.CrossCutting.Identity.EventHandlers, while a change to Infra.CrossCutting.Identity.EventHandlers can't break Infra.CrossCutting.Identity.Events.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.EventHandlers uses a module listed above it, which is the healthy direction.
22→6 Infra.CrossCutting.Identity.Requests uses Domain.Core.Commands✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.Requests uses a type in Domain.Core.Commands.
- The types involved
HRM.Infra.CrossCutting.Identity.Requests.AuthRequest→HRM.Domain.Core.Commands.Command
- Direction
- Infra.CrossCutting.Identity.Requests uses Domain.Core.Commands, so a change to Domain.Core.Commands can break Infra.CrossCutting.Identity.Requests, while a change to Infra.CrossCutting.Identity.Requests can't break Domain.Core.Commands.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Requests uses a module listed above it, which is the healthy direction.
23→15 Application.Interfaces uses Infra.CrossCutting.Identity.Responses✕
- Connections
- 2 pairs of types, where a type in Application.Interfaces uses a type in Infra.CrossCutting.Identity.Responses.
- The types involved
HRM.Application.Interfaces.IAccountAppService→HRM.Infra.CrossCutting.Identity.Responses.ExchangeRefreshTokenResponseHRM.Application.Interfaces.IAccountAppService→HRM.Infra.CrossCutting.Identity.Responses.LoginResponse
- Direction
- Application.Interfaces uses Infra.CrossCutting.Identity.Responses, so a change to Infra.CrossCutting.Identity.Responses can break Application.Interfaces, while a change to Application.Interfaces can't break Infra.CrossCutting.Identity.Responses.
- Position
- Below the diagonal: Application.Interfaces uses a module listed above it, which is the healthy direction.
23→16 Application.Interfaces uses Application.ViewModels✕
- Connections
- 3 pairs of types, where a type in Application.Interfaces uses a type in Application.ViewModels.
- The types involved
HRM.Application.Interfaces.IAccountAppService→HRM.Application.ViewModels.LoginViewModelHRM.Application.Interfaces.IAccountAppService→HRM.Application.ViewModels.RefreshTokenViewModelHRM.Application.Interfaces.IAccountAppService→HRM.Application.ViewModels.RegisterUserViewModel
- Direction
- Application.Interfaces uses Application.ViewModels, so a change to Application.ViewModels can break Application.Interfaces, while a change to Application.Interfaces can't break Application.ViewModels.
- Position
- Below the diagonal: Application.Interfaces uses a module listed above it, which is the healthy direction.
24→17 Domain.Interfaces uses Domain✕
- Connections
- 1 pair of types, where a type in Domain.Interfaces uses a type in Domain.
- The types involved
HRM.Domain.Interfaces.IEmployeeRepository→HRM.Domain.Employee
- Direction
- Domain.Interfaces uses Domain, so a change to Domain can break Domain.Interfaces, while a change to Domain.Interfaces can't break Domain.
- Position
- Below the diagonal: Domain.Interfaces uses a module listed above it, which is the healthy direction.
24→20 Domain.Interfaces uses Domain.Models.Identity✕
- Connections
- 1 pair of types, where a type in Domain.Interfaces uses a type in Domain.Models.Identity.
- The types involved
HRM.Domain.Interfaces.IUserRepository→HRM.Domain.Models.Identity.User
- Direction
- Domain.Interfaces uses Domain.Models.Identity, so a change to Domain.Models.Identity can break Domain.Interfaces, while a change to Domain.Interfaces can't break Domain.Models.Identity.
- Position
- Below the diagonal: Domain.Interfaces uses a module listed above it, which is the healthy direction.
25→2 Infra.Data.Context uses Domain.Core.Events✕
- Connections
- 1 pair of types, where a type in Infra.Data.Context uses a type in Domain.Core.Events.
- The types involved
HRM.Infra.Data.Context.EventSourcingContext→HRM.Domain.Core.Events.StoredEvent
- Direction
- Infra.Data.Context uses Domain.Core.Events, so a change to Domain.Core.Events can break Infra.Data.Context, while a change to Infra.Data.Context can't break Domain.Core.Events.
- Position
- Below the diagonal: Infra.Data.Context uses a module listed above it, which is the healthy direction.
25→17 Infra.Data.Context uses Domain✕
- Connections
- 1 pair of types, where a type in Infra.Data.Context uses a type in Domain.
- The types involved
HRM.Infra.Data.Context.HRMContext→HRM.Domain.Employee
- Direction
- Infra.Data.Context uses Domain, so a change to Domain can break Infra.Data.Context, while a change to Infra.Data.Context can't break Domain.
- Position
- Below the diagonal: Infra.Data.Context uses a module listed above it, which is the healthy direction.
26→2 Infra.Data.Mappings uses Domain.Core.Events✕
- Connections
- 1 pair of types, where a type in Infra.Data.Mappings uses a type in Domain.Core.Events.
- The types involved
HRM.Infra.Data.Mappings.StoredEventMap→HRM.Domain.Core.Events.StoredEvent
- Direction
- Infra.Data.Mappings uses Domain.Core.Events, so a change to Domain.Core.Events can break Infra.Data.Mappings, while a change to Infra.Data.Mappings can't break Domain.Core.Events.
- Position
- Below the diagonal: Infra.Data.Mappings uses a module listed above it, which is the healthy direction.
26→17 Infra.Data.Mappings uses Domain✕
- Connections
- 1 pair of types, where a type in Infra.Data.Mappings uses a type in Domain.
- The types involved
HRM.Infra.Data.Mappings.EmployeeMap→HRM.Domain.Employee
- Direction
- Infra.Data.Mappings uses Domain, so a change to Domain can break Infra.Data.Mappings, while a change to Infra.Data.Mappings can't break Domain.
- Position
- Below the diagonal: Infra.Data.Mappings uses a module listed above it, which is the healthy direction.
27→1 Domain.CommandHandlers uses Domain.Core.Bus✕
- Connections
- 2 pairs of types, where a type in Domain.CommandHandlers uses a type in Domain.Core.Bus.
- The types involved
HRM.Domain.CommandHandlers.CommandHandler→HRM.Domain.Core.Bus.IMediatorHandlerHRM.Domain.CommandHandlers.EmployeeCommandHandler→HRM.Domain.Core.Bus.IMediatorHandler
- Direction
- Domain.CommandHandlers uses Domain.Core.Bus, so a change to Domain.Core.Bus can break Domain.CommandHandlers, while a change to Domain.CommandHandlers can't break Domain.Core.Bus.
- Position
- Below the diagonal: Domain.CommandHandlers uses a module listed above it, which is the healthy direction.
27→6 Domain.CommandHandlers uses Domain.Core.Commands✕
- Connections
- 1 pair of types, where a type in Domain.CommandHandlers uses a type in Domain.Core.Commands.
- The types involved
HRM.Domain.CommandHandlers.CommandHandler→HRM.Domain.Core.Commands.Command
- Direction
- Domain.CommandHandlers uses Domain.Core.Commands, so a change to Domain.Core.Commands can break Domain.CommandHandlers, while a change to Domain.CommandHandlers can't break Domain.Core.Commands.
- Position
- Below the diagonal: Domain.CommandHandlers uses a module listed above it, which is the healthy direction.
27→7 Domain.CommandHandlers uses Domain.Core.Notifications✕
- Connections
- 3 pairs of types, where a type in Domain.CommandHandlers uses a type in Domain.Core.Notifications.
- The types involved
HRM.Domain.CommandHandlers.CommandHandler→HRM.Domain.Core.Notifications.DomainNotificationHRM.Domain.CommandHandlers.CommandHandler→HRM.Domain.Core.Notifications.DomainNotificationHandlerHRM.Domain.CommandHandlers.EmployeeCommandHandler→HRM.Domain.Core.Notifications.DomainNotification
- Direction
- Domain.CommandHandlers uses Domain.Core.Notifications, so a change to Domain.Core.Notifications can break Domain.CommandHandlers, while a change to Domain.CommandHandlers can't break Domain.Core.Notifications.
- Position
- Below the diagonal: Domain.CommandHandlers uses a module listed above it, which is the healthy direction.
27→18 Domain.CommandHandlers uses Domain.Commands✕
- Connections
- 3 pairs of types, where a type in Domain.CommandHandlers uses a type in Domain.Commands.
- The types involved
HRM.Domain.CommandHandlers.EmployeeCommandHandler→HRM.Domain.Commands.RegisterNewEmployeeCommandHRM.Domain.CommandHandlers.EmployeeCommandHandler→HRM.Domain.Commands.RemoveEmployeeCommandHRM.Domain.CommandHandlers.EmployeeCommandHandler→HRM.Domain.Commands.UpdateEmployeeCommand
- Direction
- Domain.CommandHandlers uses Domain.Commands, so a change to Domain.Commands can break Domain.CommandHandlers, while a change to Domain.CommandHandlers can't break Domain.Commands.
- Position
- Below the diagonal: Domain.CommandHandlers uses a module listed above it, which is the healthy direction.
27→24 Domain.CommandHandlers uses Domain.Interfaces✕
- Connections
- 3 pairs of types, where a type in Domain.CommandHandlers uses a type in Domain.Interfaces.
- The types involved
HRM.Domain.CommandHandlers.CommandHandler→HRM.Domain.Interfaces.IUnitOfWorkHRM.Domain.CommandHandlers.EmployeeCommandHandler→HRM.Domain.Interfaces.IEmployeeRepositoryHRM.Domain.CommandHandlers.EmployeeCommandHandler→HRM.Domain.Interfaces.IUnitOfWork
- Direction
- Domain.CommandHandlers uses Domain.Interfaces, so a change to Domain.Interfaces can break Domain.CommandHandlers, while a change to Domain.CommandHandlers can't break Domain.Interfaces.
- Position
- Below the diagonal: Domain.CommandHandlers uses a module listed above it, which is the healthy direction.
28→15 Infra.CrossCutting.Identity.Interfaces uses Infra.CrossCutting.Identity.Responses✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.Interfaces uses a type in Infra.CrossCutting.Identity.Responses.
- The types involved
HRM.Infra.CrossCutting.Identity.Interfaces.IExchangeRefreshTokenHandler→HRM.Infra.CrossCutting.Identity.Responses.ExchangeRefreshTokenResponseHRM.Infra.CrossCutting.Identity.Interfaces.ILoginHandler→HRM.Infra.CrossCutting.Identity.Responses.LoginResponse
- Direction
- Infra.CrossCutting.Identity.Interfaces uses Infra.CrossCutting.Identity.Responses, so a change to Infra.CrossCutting.Identity.Responses can break Infra.CrossCutting.Identity.Interfaces, while a change to Infra.CrossCutting.Identity.Interfaces can't break Infra.CrossCutting.Identity.Responses.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Interfaces uses a module listed above it, which is the healthy direction.
28→22 Infra.CrossCutting.Identity.Interfaces uses Infra.CrossCutting.Identity.Requests✕
- Connections
- 3 pairs of types, where a type in Infra.CrossCutting.Identity.Interfaces uses a type in Infra.CrossCutting.Identity.Requests.
- The types involved
HRM.Infra.CrossCutting.Identity.Interfaces.IExchangeRefreshTokenHandler→HRM.Infra.CrossCutting.Identity.Requests.ExchangeRefreshTokenRequestHRM.Infra.CrossCutting.Identity.Interfaces.ILoginHandler→HRM.Infra.CrossCutting.Identity.Requests.LoginRequestHRM.Infra.CrossCutting.Identity.Interfaces.IRegisterUserHandler→HRM.Infra.CrossCutting.Identity.Requests.RegisterUserRequest
- Direction
- Infra.CrossCutting.Identity.Interfaces uses Infra.CrossCutting.Identity.Requests, so a change to Infra.CrossCutting.Identity.Requests can break Infra.CrossCutting.Identity.Interfaces, while a change to Infra.CrossCutting.Identity.Interfaces can't break Infra.CrossCutting.Identity.Requests.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Interfaces uses a module listed above it, which is the healthy direction.
28→24 Infra.CrossCutting.Identity.Interfaces uses Domain.Interfaces✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.Interfaces uses a type in Domain.Interfaces.
- The types involved
HRM.Infra.CrossCutting.Identity.Interfaces.IExchangeRefreshTokenHandler→HRM.Domain.Interfaces.IOutputPortHRM.Infra.CrossCutting.Identity.Interfaces.ILoginHandler→HRM.Domain.Interfaces.IOutputPort
- Direction
- Infra.CrossCutting.Identity.Interfaces uses Domain.Interfaces, so a change to Domain.Interfaces can break Infra.CrossCutting.Identity.Interfaces, while a change to Infra.CrossCutting.Identity.Interfaces can't break Domain.Interfaces.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Interfaces uses a module listed above it, which is the healthy direction.
29→15 Infra.CrossCutting.Identity.Presenters uses Infra.CrossCutting.Identity.Responses✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.Presenters uses a type in Infra.CrossCutting.Identity.Responses.
- The types involved
HRM.Infra.CrossCutting.Identity.Presenters.ExchangeRefreshTokenPresenter→HRM.Infra.CrossCutting.Identity.Responses.ExchangeRefreshTokenResponseHRM.Infra.CrossCutting.Identity.Presenters.LoginPresenter→HRM.Infra.CrossCutting.Identity.Responses.LoginResponse
- Direction
- Infra.CrossCutting.Identity.Presenters uses Infra.CrossCutting.Identity.Responses, so a change to Infra.CrossCutting.Identity.Responses can break Infra.CrossCutting.Identity.Presenters, while a change to Infra.CrossCutting.Identity.Presenters can't break Infra.CrossCutting.Identity.Responses.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Presenters uses a module listed above it, which is the healthy direction.
29→24 Infra.CrossCutting.Identity.Presenters uses Domain.Interfaces✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.Presenters uses a type in Domain.Interfaces.
- The types involved
HRM.Infra.CrossCutting.Identity.Presenters.ExchangeRefreshTokenPresenter→HRM.Domain.Interfaces.IOutputPortHRM.Infra.CrossCutting.Identity.Presenters.LoginPresenter→HRM.Domain.Interfaces.IOutputPort
- Direction
- Infra.CrossCutting.Identity.Presenters uses Domain.Interfaces, so a change to Domain.Interfaces can break Infra.CrossCutting.Identity.Presenters, while a change to Infra.CrossCutting.Identity.Presenters can't break Domain.Interfaces.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Presenters uses a module listed above it, which is the healthy direction.
30→17 Infra.Data.Repository uses Domain✕
- Connections
- 1 pair of types, where a type in Infra.Data.Repository uses a type in Domain.
- The types involved
HRM.Infra.Data.Repository.EmployeeRepository→HRM.Domain.Employee
- Direction
- Infra.Data.Repository uses Domain, so a change to Domain can break Infra.Data.Repository, while a change to Infra.Data.Repository can't break Domain.
- Position
- Below the diagonal: Infra.Data.Repository uses a module listed above it, which is the healthy direction.
30→24 Infra.Data.Repository uses Domain.Interfaces✕
- Connections
- 3 pairs of types, where a type in Infra.Data.Repository uses a type in Domain.Interfaces.
- The types involved
HRM.Infra.Data.Repository.EmployeeRepository→HRM.Domain.Interfaces.IEmployeeRepositoryHRM.Infra.Data.Repository.Repository→HRM.Domain.Interfaces.IRepositoryHRM.Infra.Data.Repository.Repository→HRM.Domain.Interfaces.ISpecification
- Direction
- Infra.Data.Repository uses Domain.Interfaces, so a change to Domain.Interfaces can break Infra.Data.Repository, while a change to Infra.Data.Repository can't break Domain.Interfaces.
- Position
- Below the diagonal: Infra.Data.Repository uses a module listed above it, which is the healthy direction.
30→25 Infra.Data.Repository uses Infra.Data.Context✕
- Connections
- 2 pairs of types, where a type in Infra.Data.Repository uses a type in Infra.Data.Context.
- The types involved
HRM.Infra.Data.Repository.EmployeeRepository→HRM.Infra.Data.Context.HRMContextHRM.Infra.Data.Repository.Repository→HRM.Infra.Data.Context.HRMContext
- Direction
- Infra.Data.Repository uses Infra.Data.Context, so a change to Infra.Data.Context can break Infra.Data.Repository, while a change to Infra.Data.Repository can't break Infra.Data.Context.
- Position
- Below the diagonal: Infra.Data.Repository uses a module listed above it, which is the healthy direction.
31→2 Infra.Data.Repository.EventSourcing uses Domain.Core.Events✕
- Connections
- 2 pairs of types, where a type in Infra.Data.Repository.EventSourcing uses a type in Domain.Core.Events.
- The types involved
HRM.Infra.Data.Repository.EventSourcing.EventStoreRepository→HRM.Domain.Core.Events.StoredEventHRM.Infra.Data.Repository.EventSourcing.IEventStoreRepository→HRM.Domain.Core.Events.StoredEvent
- Direction
- Infra.Data.Repository.EventSourcing uses Domain.Core.Events, so a change to Domain.Core.Events can break Infra.Data.Repository.EventSourcing, while a change to Infra.Data.Repository.EventSourcing can't break Domain.Core.Events.
- Position
- Below the diagonal: Infra.Data.Repository.EventSourcing uses a module listed above it, which is the healthy direction.
31→25 Infra.Data.Repository.EventSourcing uses Infra.Data.Context✕
- Connections
- 1 pair of types, where a type in Infra.Data.Repository.EventSourcing uses a type in Infra.Data.Context.
- The types involved
HRM.Infra.Data.Repository.EventSourcing.EventStoreRepository→HRM.Infra.Data.Context.EventSourcingContext
- Direction
- Infra.Data.Repository.EventSourcing uses Infra.Data.Context, so a change to Infra.Data.Context can break Infra.Data.Repository.EventSourcing, while a change to Infra.Data.Repository.EventSourcing can't break Infra.Data.Context.
- Position
- Below the diagonal: Infra.Data.Repository.EventSourcing uses a module listed above it, which is the healthy direction.
32→24 Infra.Data.Specifications uses Domain.Interfaces✕
- Connections
- 1 pair of types, where a type in Infra.Data.Specifications uses a type in Domain.Interfaces.
- The types involved
HRM.Infra.Data.Specifications.BaseSpecification→HRM.Domain.Interfaces.ISpecification
- Direction
- Infra.Data.Specifications uses Domain.Interfaces, so a change to Domain.Interfaces can break Infra.Data.Specifications, while a change to Infra.Data.Specifications can't break Domain.Interfaces.
- Position
- Below the diagonal: Infra.Data.Specifications uses a module listed above it, which is the healthy direction.
33→24 Infra.Data.UoW uses Domain.Interfaces✕
- Connections
- 1 pair of types, where a type in Infra.Data.UoW uses a type in Domain.Interfaces.
- The types involved
HRM.Infra.Data.UoW.UnitOfWork→HRM.Domain.Interfaces.IUnitOfWork
- Direction
- Infra.Data.UoW uses Domain.Interfaces, so a change to Domain.Interfaces can break Infra.Data.UoW, while a change to Infra.Data.UoW can't break Domain.Interfaces.
- Position
- Below the diagonal: Infra.Data.UoW uses a module listed above it, which is the healthy direction.
33→25 Infra.Data.UoW uses Infra.Data.Context✕
- Connections
- 1 pair of types, where a type in Infra.Data.UoW uses a type in Infra.Data.Context.
- The types involved
HRM.Infra.Data.UoW.UnitOfWork→HRM.Infra.Data.Context.HRMContext
- Direction
- Infra.Data.UoW uses Infra.Data.Context, so a change to Infra.Data.Context can break Infra.Data.UoW, while a change to Infra.Data.UoW can't break Infra.Data.Context.
- Position
- Below the diagonal: Infra.Data.UoW uses a module listed above it, which is the healthy direction.
34→1 WebApi.Controllers uses Domain.Core.Bus✕
- Connections
- 2 pairs of types, where a type in WebApi.Controllers uses a type in Domain.Core.Bus.
- The types involved
HRM.WebApi.Controllers.AccountController→HRM.Domain.Core.Bus.IMediatorHandlerHRM.WebApi.Controllers.ApiController→HRM.Domain.Core.Bus.IMediatorHandler
- Direction
- WebApi.Controllers uses Domain.Core.Bus, so a change to Domain.Core.Bus can break WebApi.Controllers, while a change to WebApi.Controllers can't break Domain.Core.Bus.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
34→7 WebApi.Controllers uses Domain.Core.Notifications✕
- Connections
- 3 pairs of types, where a type in WebApi.Controllers uses a type in Domain.Core.Notifications.
- The types involved
HRM.WebApi.Controllers.AccountController→HRM.Domain.Core.Notifications.DomainNotificationHRM.WebApi.Controllers.ApiController→HRM.Domain.Core.Notifications.DomainNotificationHRM.WebApi.Controllers.ApiController→HRM.Domain.Core.Notifications.DomainNotificationHandler
- Direction
- WebApi.Controllers uses Domain.Core.Notifications, so a change to Domain.Core.Notifications can break WebApi.Controllers, while a change to WebApi.Controllers can't break Domain.Core.Notifications.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
34→16 WebApi.Controllers uses Application.ViewModels✕
- Connections
- 3 pairs of types, where a type in WebApi.Controllers uses a type in Application.ViewModels.
- The types involved
HRM.WebApi.Controllers.AccountController→HRM.Application.ViewModels.LoginViewModelHRM.WebApi.Controllers.AccountController→HRM.Application.ViewModels.RefreshTokenViewModelHRM.WebApi.Controllers.AccountController→HRM.Application.ViewModels.RegisterUserViewModel
- Direction
- WebApi.Controllers uses Application.ViewModels, so a change to Application.ViewModels can break WebApi.Controllers, while a change to WebApi.Controllers can't break Application.ViewModels.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
34→23 WebApi.Controllers uses Application.Interfaces✕
- Connections
- 1 pair of types, where a type in WebApi.Controllers uses a type in Application.Interfaces.
- The types involved
HRM.WebApi.Controllers.AccountController→HRM.Application.Interfaces.IAccountAppService
- Direction
- WebApi.Controllers uses Application.Interfaces, so a change to Application.Interfaces can break WebApi.Controllers, while a change to WebApi.Controllers can't break Application.Interfaces.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
35→15 Application.Services uses Infra.CrossCutting.Identity.Responses✕
- Connections
- 2 pairs of types, where a type in Application.Services uses a type in Infra.CrossCutting.Identity.Responses.
- The types involved
HRM.Application.Services.AccountAppService→HRM.Infra.CrossCutting.Identity.Responses.ExchangeRefreshTokenResponseHRM.Application.Services.AccountAppService→HRM.Infra.CrossCutting.Identity.Responses.LoginResponse
- Direction
- Application.Services uses Infra.CrossCutting.Identity.Responses, so a change to Infra.CrossCutting.Identity.Responses can break Application.Services, while a change to Application.Services can't break Infra.CrossCutting.Identity.Responses.
- Position
- Below the diagonal: Application.Services uses a module listed above it, which is the healthy direction.
35→16 Application.Services uses Application.ViewModels✕
- Connections
- 3 pairs of types, where a type in Application.Services uses a type in Application.ViewModels.
- The types involved
HRM.Application.Services.AccountAppService→HRM.Application.ViewModels.LoginViewModelHRM.Application.Services.AccountAppService→HRM.Application.ViewModels.RefreshTokenViewModelHRM.Application.Services.AccountAppService→HRM.Application.ViewModels.RegisterUserViewModel
- Direction
- Application.Services uses Application.ViewModels, so a change to Application.ViewModels can break Application.Services, while a change to Application.Services can't break Application.ViewModels.
- Position
- Below the diagonal: Application.Services uses a module listed above it, which is the healthy direction.
35→23 Application.Services uses Application.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Services uses a type in Application.Interfaces.
- The types involved
HRM.Application.Services.AccountAppService→HRM.Application.Interfaces.IAccountAppService
- Direction
- Application.Services uses Application.Interfaces, so a change to Application.Interfaces can break Application.Services, while a change to Application.Services can't break Application.Interfaces.
- Position
- Below the diagonal: Application.Services uses a module listed above it, which is the healthy direction.
35→28 Application.Services uses Infra.CrossCutting.Identity.Interfaces✕
- Connections
- 3 pairs of types, where a type in Application.Services uses a type in Infra.CrossCutting.Identity.Interfaces.
- The types involved
HRM.Application.Services.AccountAppService→HRM.Infra.CrossCutting.Identity.Interfaces.IExchangeRefreshTokenHandlerHRM.Application.Services.AccountAppService→HRM.Infra.CrossCutting.Identity.Interfaces.ILoginHandlerHRM.Application.Services.AccountAppService→HRM.Infra.CrossCutting.Identity.Interfaces.IRegisterUserHandler
- Direction
- Application.Services uses Infra.CrossCutting.Identity.Interfaces, so a change to Infra.CrossCutting.Identity.Interfaces can break Application.Services, while a change to Application.Services can't break Infra.CrossCutting.Identity.Interfaces.
- Position
- Below the diagonal: Application.Services uses a module listed above it, which is the healthy direction.
35→29 Application.Services uses Infra.CrossCutting.Identity.Presenters✕
- Connections
- 2 pairs of types, where a type in Application.Services uses a type in Infra.CrossCutting.Identity.Presenters.
- The types involved
HRM.Application.Services.AccountAppService→HRM.Infra.CrossCutting.Identity.Presenters.ExchangeRefreshTokenPresenterHRM.Application.Services.AccountAppService→HRM.Infra.CrossCutting.Identity.Presenters.LoginPresenter
- Direction
- Application.Services uses Infra.CrossCutting.Identity.Presenters, so a change to Infra.CrossCutting.Identity.Presenters can break Application.Services, while a change to Application.Services can't break Infra.CrossCutting.Identity.Presenters.
- Position
- Below the diagonal: Application.Services uses a module listed above it, which is the healthy direction.
36→5 Infra.CrossCutting.Identity.Auth uses Infra.CrossCutting.Identity.Dto✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.Auth uses a type in Infra.CrossCutting.Identity.Dto.
- The types involved
HRM.Infra.CrossCutting.Identity.Auth.JwtFactory→HRM.Infra.CrossCutting.Identity.Dto.AccessToken
- Direction
- Infra.CrossCutting.Identity.Auth uses Infra.CrossCutting.Identity.Dto, so a change to Infra.CrossCutting.Identity.Dto can break Infra.CrossCutting.Identity.Auth, while a change to Infra.CrossCutting.Identity.Auth can't break Infra.CrossCutting.Identity.Dto.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Auth uses a module listed above it, which is the healthy direction.
36→13 Infra.CrossCutting.Identity.Auth uses Infra.CrossCutting.Identity.Interfaces.Services✕
- Connections
- 3 pairs of types, where a type in Infra.CrossCutting.Identity.Auth uses a type in Infra.CrossCutting.Identity.Interfaces.Services.
- The types involved
HRM.Infra.CrossCutting.Identity.Auth.JwtFactory→HRM.Infra.CrossCutting.Identity.Interfaces.Services.IJwtFactoryHRM.Infra.CrossCutting.Identity.Auth.JwtTokenValidator→HRM.Infra.CrossCutting.Identity.Interfaces.Services.IJwtTokenValidatorHRM.Infra.CrossCutting.Identity.Auth.TokenFactory→HRM.Infra.CrossCutting.Identity.Interfaces.Services.ITokenFactory
- Direction
- Infra.CrossCutting.Identity.Auth uses Infra.CrossCutting.Identity.Interfaces.Services, so a change to Infra.CrossCutting.Identity.Interfaces.Services can break Infra.CrossCutting.Identity.Auth, while a change to Infra.CrossCutting.Identity.Auth can't break Infra.CrossCutting.Identity.Interfaces.Services.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Auth uses a module listed above it, which is the healthy direction.
36→28 Infra.CrossCutting.Identity.Auth uses Infra.CrossCutting.Identity.Interfaces✕
- Connections
- 3 pairs of types, where a type in Infra.CrossCutting.Identity.Auth uses a type in Infra.CrossCutting.Identity.Interfaces.
- The types involved
HRM.Infra.CrossCutting.Identity.Auth.JwtFactory→HRM.Infra.CrossCutting.Identity.Interfaces.IJwtTokenHandlerHRM.Infra.CrossCutting.Identity.Auth.JwtTokenHandler→HRM.Infra.CrossCutting.Identity.Interfaces.IJwtTokenHandlerHRM.Infra.CrossCutting.Identity.Auth.JwtTokenValidator→HRM.Infra.CrossCutting.Identity.Interfaces.IJwtTokenHandler
- Direction
- Infra.CrossCutting.Identity.Auth uses Infra.CrossCutting.Identity.Interfaces, so a change to Infra.CrossCutting.Identity.Interfaces can break Infra.CrossCutting.Identity.Auth, while a change to Infra.CrossCutting.Identity.Auth can't break Infra.CrossCutting.Identity.Interfaces.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Auth uses a module listed above it, which is the healthy direction.
37→1 Infra.CrossCutting.Identity.AuthHandlers uses Domain.Core.Bus✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.AuthHandlers uses a type in Domain.Core.Bus.
- The types involved
HRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Domain.Core.Bus.IMediatorHandler
- Direction
- Infra.CrossCutting.Identity.AuthHandlers uses Domain.Core.Bus, so a change to Domain.Core.Bus can break Infra.CrossCutting.Identity.AuthHandlers, while a change to Infra.CrossCutting.Identity.AuthHandlers can't break Domain.Core.Bus.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.AuthHandlers uses a module listed above it, which is the healthy direction.
37→7 Infra.CrossCutting.Identity.AuthHandlers uses Domain.Core.Notifications✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.AuthHandlers uses a type in Domain.Core.Notifications.
- The types involved
HRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Domain.Core.Notifications.DomainNotification
- Direction
- Infra.CrossCutting.Identity.AuthHandlers uses Domain.Core.Notifications, so a change to Domain.Core.Notifications can break Infra.CrossCutting.Identity.AuthHandlers, while a change to Infra.CrossCutting.Identity.AuthHandlers can't break Domain.Core.Notifications.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.AuthHandlers uses a module listed above it, which is the healthy direction.
37→13 Infra.CrossCutting.Identity.AuthHandlers uses Infra.CrossCutting.Identity.Interfaces.Services✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.AuthHandlers uses a type in Infra.CrossCutting.Identity.Interfaces.Services.
- The types involved
HRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Infra.CrossCutting.Identity.Interfaces.Services.IJwtFactoryHRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Infra.CrossCutting.Identity.Interfaces.Services.ITokenFactory
- Direction
- Infra.CrossCutting.Identity.AuthHandlers uses Infra.CrossCutting.Identity.Interfaces.Services, so a change to Infra.CrossCutting.Identity.Interfaces.Services can break Infra.CrossCutting.Identity.AuthHandlers, while a change to Infra.CrossCutting.Identity.AuthHandlers can't break Infra.CrossCutting.Identity.Interfaces.Services.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.AuthHandlers uses a module listed above it, which is the healthy direction.
37→15 Infra.CrossCutting.Identity.AuthHandlers uses Infra.CrossCutting.Identity.Responses✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.AuthHandlers uses a type in Infra.CrossCutting.Identity.Responses.
- The types involved
HRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Infra.CrossCutting.Identity.Responses.LoginResponse
- Direction
- Infra.CrossCutting.Identity.AuthHandlers uses Infra.CrossCutting.Identity.Responses, so a change to Infra.CrossCutting.Identity.Responses can break Infra.CrossCutting.Identity.AuthHandlers, while a change to Infra.CrossCutting.Identity.AuthHandlers can't break Infra.CrossCutting.Identity.Responses.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.AuthHandlers uses a module listed above it, which is the healthy direction.
37→22 Infra.CrossCutting.Identity.AuthHandlers uses Infra.CrossCutting.Identity.Requests✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.AuthHandlers uses a type in Infra.CrossCutting.Identity.Requests.
- The types involved
HRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Infra.CrossCutting.Identity.Requests.LoginRequest
- Direction
- Infra.CrossCutting.Identity.AuthHandlers uses Infra.CrossCutting.Identity.Requests, so a change to Infra.CrossCutting.Identity.Requests can break Infra.CrossCutting.Identity.AuthHandlers, while a change to Infra.CrossCutting.Identity.AuthHandlers can't break Infra.CrossCutting.Identity.Requests.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.AuthHandlers uses a module listed above it, which is the healthy direction.
37→24 Infra.CrossCutting.Identity.AuthHandlers uses Domain.Interfaces✕
- Connections
- 3 pairs of types, where a type in Infra.CrossCutting.Identity.AuthHandlers uses a type in Domain.Interfaces.
- The types involved
HRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Domain.Interfaces.IOutputPortHRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Domain.Interfaces.IUnitOfWorkHRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Domain.Interfaces.IUserRepository
- Direction
- Infra.CrossCutting.Identity.AuthHandlers uses Domain.Interfaces, so a change to Domain.Interfaces can break Infra.CrossCutting.Identity.AuthHandlers, while a change to Infra.CrossCutting.Identity.AuthHandlers can't break Domain.Interfaces.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.AuthHandlers uses a module listed above it, which is the healthy direction.
37→27 Infra.CrossCutting.Identity.AuthHandlers uses Domain.CommandHandlers✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.AuthHandlers uses a type in Domain.CommandHandlers.
- The types involved
HRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Domain.CommandHandlers.CommandHandler
- Direction
- Infra.CrossCutting.Identity.AuthHandlers uses Domain.CommandHandlers, so a change to Domain.CommandHandlers can break Infra.CrossCutting.Identity.AuthHandlers, while a change to Infra.CrossCutting.Identity.AuthHandlers can't break Domain.CommandHandlers.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.AuthHandlers uses a module listed above it, which is the healthy direction.
37→28 Infra.CrossCutting.Identity.AuthHandlers uses Infra.CrossCutting.Identity.Interfaces✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.AuthHandlers uses a type in Infra.CrossCutting.Identity.Interfaces.
- The types involved
HRM.Infra.CrossCutting.Identity.AuthHandlers.LoginHandler→HRM.Infra.CrossCutting.Identity.Interfaces.ILoginHandler
- Direction
- Infra.CrossCutting.Identity.AuthHandlers uses Infra.CrossCutting.Identity.Interfaces, so a change to Infra.CrossCutting.Identity.Interfaces can break Infra.CrossCutting.Identity.AuthHandlers, while a change to Infra.CrossCutting.Identity.AuthHandlers can't break Infra.CrossCutting.Identity.Interfaces.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.AuthHandlers uses a module listed above it, which is the healthy direction.
38→14 Infra.CrossCutting.Identity.Repositories uses Infra.CrossCutting.Identity.Models✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.Repositories uses a type in Infra.CrossCutting.Identity.Models.
- The types involved
HRM.Infra.CrossCutting.Identity.Repositories.UserRepository→HRM.Infra.CrossCutting.Identity.Models.AppUser
- Direction
- Infra.CrossCutting.Identity.Repositories uses Infra.CrossCutting.Identity.Models, so a change to Infra.CrossCutting.Identity.Models can break Infra.CrossCutting.Identity.Repositories, while a change to Infra.CrossCutting.Identity.Repositories can't break Infra.CrossCutting.Identity.Models.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Repositories uses a module listed above it, which is the healthy direction.
38→20 Infra.CrossCutting.Identity.Repositories uses Domain.Models.Identity✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.Repositories uses a type in Domain.Models.Identity.
- The types involved
HRM.Infra.CrossCutting.Identity.Repositories.UserRepository→HRM.Domain.Models.Identity.User
- Direction
- Infra.CrossCutting.Identity.Repositories uses Domain.Models.Identity, so a change to Domain.Models.Identity can break Infra.CrossCutting.Identity.Repositories, while a change to Infra.CrossCutting.Identity.Repositories can't break Domain.Models.Identity.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Repositories uses a module listed above it, which is the healthy direction.
38→24 Infra.CrossCutting.Identity.Repositories uses Domain.Interfaces✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.Repositories uses a type in Domain.Interfaces.
- The types involved
HRM.Infra.CrossCutting.Identity.Repositories.UserRepository→HRM.Domain.Interfaces.IUserRepository
- Direction
- Infra.CrossCutting.Identity.Repositories uses Domain.Interfaces, so a change to Domain.Interfaces can break Infra.CrossCutting.Identity.Repositories, while a change to Infra.CrossCutting.Identity.Repositories can't break Domain.Interfaces.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Repositories uses a module listed above it, which is the healthy direction.
38→25 Infra.CrossCutting.Identity.Repositories uses Infra.Data.Context✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.Repositories uses a type in Infra.Data.Context.
- The types involved
HRM.Infra.CrossCutting.Identity.Repositories.UserRepository→HRM.Infra.Data.Context.HRMContext
- Direction
- Infra.CrossCutting.Identity.Repositories uses Infra.Data.Context, so a change to Infra.Data.Context can break Infra.CrossCutting.Identity.Repositories, while a change to Infra.CrossCutting.Identity.Repositories can't break Infra.Data.Context.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Repositories uses a module listed above it, which is the healthy direction.
38→30 Infra.CrossCutting.Identity.Repositories uses Infra.Data.Repository✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.Repositories uses a type in Infra.Data.Repository.
- The types involved
HRM.Infra.CrossCutting.Identity.Repositories.UserRepository→HRM.Infra.Data.Repository.Repository
- Direction
- Infra.CrossCutting.Identity.Repositories uses Infra.Data.Repository, so a change to Infra.Data.Repository can break Infra.CrossCutting.Identity.Repositories, while a change to Infra.CrossCutting.Identity.Repositories can't break Infra.Data.Repository.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.Repositories uses a module listed above it, which is the healthy direction.
39→1 Infra.CrossCutting.Identity.UseCaseHandlers uses Domain.Core.Bus✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.UseCaseHandlers uses a type in Domain.Core.Bus.
- The types involved
HRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Domain.Core.Bus.IMediatorHandlerHRM.Infra.CrossCutting.Identity.UseCaseHandlers.RegisterUserHandler→HRM.Domain.Core.Bus.IMediatorHandler
- Direction
- Infra.CrossCutting.Identity.UseCaseHandlers uses Domain.Core.Bus, so a change to Domain.Core.Bus can break Infra.CrossCutting.Identity.UseCaseHandlers, while a change to Infra.CrossCutting.Identity.UseCaseHandlers can't break Domain.Core.Bus.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.UseCaseHandlers uses a module listed above it, which is the healthy direction.
39→7 Infra.CrossCutting.Identity.UseCaseHandlers uses Domain.Core.Notifications✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.UseCaseHandlers uses a type in Domain.Core.Notifications.
- The types involved
HRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Domain.Core.Notifications.DomainNotificationHRM.Infra.CrossCutting.Identity.UseCaseHandlers.RegisterUserHandler→HRM.Domain.Core.Notifications.DomainNotification
- Direction
- Infra.CrossCutting.Identity.UseCaseHandlers uses Domain.Core.Notifications, so a change to Domain.Core.Notifications can break Infra.CrossCutting.Identity.UseCaseHandlers, while a change to Infra.CrossCutting.Identity.UseCaseHandlers can't break Domain.Core.Notifications.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.UseCaseHandlers uses a module listed above it, which is the healthy direction.
39→13 Infra.CrossCutting.Identity.UseCaseHandlers uses Infra.CrossCutting.Identity.Interfaces.Services✕
- Connections
- 3 pairs of types, where a type in Infra.CrossCutting.Identity.UseCaseHandlers uses a type in Infra.CrossCutting.Identity.Interfaces.Services.
- The types involved
HRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Infra.CrossCutting.Identity.Interfaces.Services.IJwtFactoryHRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Infra.CrossCutting.Identity.Interfaces.Services.IJwtTokenValidatorHRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Infra.CrossCutting.Identity.Interfaces.Services.ITokenFactory
- Direction
- Infra.CrossCutting.Identity.UseCaseHandlers uses Infra.CrossCutting.Identity.Interfaces.Services, so a change to Infra.CrossCutting.Identity.Interfaces.Services can break Infra.CrossCutting.Identity.UseCaseHandlers, while a change to Infra.CrossCutting.Identity.UseCaseHandlers can't break Infra.CrossCutting.Identity.Interfaces.Services.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.UseCaseHandlers uses a module listed above it, which is the healthy direction.
39→14 Infra.CrossCutting.Identity.UseCaseHandlers uses Infra.CrossCutting.Identity.Models✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.UseCaseHandlers uses a type in Infra.CrossCutting.Identity.Models.
- The types involved
HRM.Infra.CrossCutting.Identity.UseCaseHandlers.RegisterUserHandler→HRM.Infra.CrossCutting.Identity.Models.AppUser
- Direction
- Infra.CrossCutting.Identity.UseCaseHandlers uses Infra.CrossCutting.Identity.Models, so a change to Infra.CrossCutting.Identity.Models can break Infra.CrossCutting.Identity.UseCaseHandlers, while a change to Infra.CrossCutting.Identity.UseCaseHandlers can't break Infra.CrossCutting.Identity.Models.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.UseCaseHandlers uses a module listed above it, which is the healthy direction.
39→15 Infra.CrossCutting.Identity.UseCaseHandlers uses Infra.CrossCutting.Identity.Responses✕
- Connections
- 1 pair of types, where a type in Infra.CrossCutting.Identity.UseCaseHandlers uses a type in Infra.CrossCutting.Identity.Responses.
- The types involved
HRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Infra.CrossCutting.Identity.Responses.ExchangeRefreshTokenResponse
- Direction
- Infra.CrossCutting.Identity.UseCaseHandlers uses Infra.CrossCutting.Identity.Responses, so a change to Infra.CrossCutting.Identity.Responses can break Infra.CrossCutting.Identity.UseCaseHandlers, while a change to Infra.CrossCutting.Identity.UseCaseHandlers can't break Infra.CrossCutting.Identity.Responses.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.UseCaseHandlers uses a module listed above it, which is the healthy direction.
39→22 Infra.CrossCutting.Identity.UseCaseHandlers uses Infra.CrossCutting.Identity.Requests✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.UseCaseHandlers uses a type in Infra.CrossCutting.Identity.Requests.
- The types involved
HRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Infra.CrossCutting.Identity.Requests.ExchangeRefreshTokenRequestHRM.Infra.CrossCutting.Identity.UseCaseHandlers.RegisterUserHandler→HRM.Infra.CrossCutting.Identity.Requests.RegisterUserRequest
- Direction
- Infra.CrossCutting.Identity.UseCaseHandlers uses Infra.CrossCutting.Identity.Requests, so a change to Infra.CrossCutting.Identity.Requests can break Infra.CrossCutting.Identity.UseCaseHandlers, while a change to Infra.CrossCutting.Identity.UseCaseHandlers can't break Infra.CrossCutting.Identity.Requests.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.UseCaseHandlers uses a module listed above it, which is the healthy direction.
39→24 Infra.CrossCutting.Identity.UseCaseHandlers uses Domain.Interfaces✕
- Connections
- 5 pairs of types, where a type in Infra.CrossCutting.Identity.UseCaseHandlers uses a type in Domain.Interfaces.
- The types involved
HRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Domain.Interfaces.IOutputPortHRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Domain.Interfaces.IUnitOfWorkHRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Domain.Interfaces.IUserRepositoryHRM.Infra.CrossCutting.Identity.UseCaseHandlers.RegisterUserHandler→HRM.Domain.Interfaces.IUnitOfWorkHRM.Infra.CrossCutting.Identity.UseCaseHandlers.RegisterUserHandler→HRM.Domain.Interfaces.IUserRepository
- Direction
- Infra.CrossCutting.Identity.UseCaseHandlers uses Domain.Interfaces, so a change to Domain.Interfaces can break Infra.CrossCutting.Identity.UseCaseHandlers, while a change to Infra.CrossCutting.Identity.UseCaseHandlers can't break Domain.Interfaces.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.UseCaseHandlers uses a module listed above it, which is the healthy direction.
39→27 Infra.CrossCutting.Identity.UseCaseHandlers uses Domain.CommandHandlers✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.UseCaseHandlers uses a type in Domain.CommandHandlers.
- The types involved
HRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Domain.CommandHandlers.CommandHandlerHRM.Infra.CrossCutting.Identity.UseCaseHandlers.RegisterUserHandler→HRM.Domain.CommandHandlers.CommandHandler
- Direction
- Infra.CrossCutting.Identity.UseCaseHandlers uses Domain.CommandHandlers, so a change to Domain.CommandHandlers can break Infra.CrossCutting.Identity.UseCaseHandlers, while a change to Infra.CrossCutting.Identity.UseCaseHandlers can't break Domain.CommandHandlers.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.UseCaseHandlers uses a module listed above it, which is the healthy direction.
39→28 Infra.CrossCutting.Identity.UseCaseHandlers uses Infra.CrossCutting.Identity.Interfaces✕
- Connections
- 2 pairs of types, where a type in Infra.CrossCutting.Identity.UseCaseHandlers uses a type in Infra.CrossCutting.Identity.Interfaces.
- The types involved
HRM.Infra.CrossCutting.Identity.UseCaseHandlers.ExchangeRefreshTokenHandler→HRM.Infra.CrossCutting.Identity.Interfaces.IExchangeRefreshTokenHandlerHRM.Infra.CrossCutting.Identity.UseCaseHandlers.RegisterUserHandler→HRM.Infra.CrossCutting.Identity.Interfaces.IRegisterUserHandler
- Direction
- Infra.CrossCutting.Identity.UseCaseHandlers uses Infra.CrossCutting.Identity.Interfaces, so a change to Infra.CrossCutting.Identity.Interfaces can break Infra.CrossCutting.Identity.UseCaseHandlers, while a change to Infra.CrossCutting.Identity.UseCaseHandlers can't break Infra.CrossCutting.Identity.Interfaces.
- Position
- Below the diagonal: Infra.CrossCutting.Identity.UseCaseHandlers uses a module listed above it, which is the healthy direction.
40→2 Infra.Data.EventSourcing uses Domain.Core.Events✕
- Connections
- 1 pair of types, where a type in Infra.Data.EventSourcing uses a type in Domain.Core.Events.
- The types involved
HRM.Infra.Data.EventSourcing.SqlEventStore→HRM.Domain.Core.Events.IEventStore
- Direction
- Infra.Data.EventSourcing uses Domain.Core.Events, so a change to Domain.Core.Events can break Infra.Data.EventSourcing, while a change to Infra.Data.EventSourcing can't break Domain.Core.Events.
- Position
- Below the diagonal: Infra.Data.EventSourcing uses a module listed above it, which is the healthy direction.
40→24 Infra.Data.EventSourcing uses Domain.Interfaces✕
- Connections
- 1 pair of types, where a type in Infra.Data.EventSourcing uses a type in Domain.Interfaces.
- The types involved
HRM.Infra.Data.EventSourcing.SqlEventStore→HRM.Domain.Interfaces.IUser
- Direction
- Infra.Data.EventSourcing uses Domain.Interfaces, so a change to Domain.Interfaces can break Infra.Data.EventSourcing, while a change to Infra.Data.EventSourcing can't break Domain.Interfaces.
- Position
- Below the diagonal: Infra.Data.EventSourcing uses a module listed above it, which is the healthy direction.
40→31 Infra.Data.EventSourcing uses Infra.Data.Repository.EventSourcing✕
- Connections
- 1 pair of types, where a type in Infra.Data.EventSourcing uses a type in Infra.Data.Repository.EventSourcing.
- The types involved
HRM.Infra.Data.EventSourcing.SqlEventStore→HRM.Infra.Data.Repository.EventSourcing.IEventStoreRepository
- Direction
- Infra.Data.EventSourcing uses Infra.Data.Repository.EventSourcing, so a change to Infra.Data.Repository.EventSourcing can break Infra.Data.EventSourcing, while a change to Infra.Data.EventSourcing can't break Infra.Data.Repository.EventSourcing.
- Position
- Below the diagonal: Infra.Data.EventSourcing 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-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 19 | High / Critical |
| A05:2025 — Injection | 10 | Medium |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2); Resolve the 27 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (11), REDACTED (8), REDACTED (4); Resolve the 23 Outdated finding(s) in Dependency Hygiene — start with REDACTED (10), REDACTED (6), REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). | +8.0 pts | Low | Secret Scanning |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with UnitTest1.cs. | +2.9 pts | Low | Test Quality |
| Resolve the 27 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (11), REDACTED (8), REDACTED (4). | +5.4 pts | Medium | Dependency Hygiene |
| Resolve the 23 Outdated finding(s) in Dependency Hygiene — start with REDACTED (10), REDACTED (6), REDACTED (2). | +4.7 pts | Medium | Dependency Hygiene |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +4.2 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +4.2 pts | Medium | Security & performance tooling |
| Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/HRM.Domain/Entities/Identity/User.cs:17`. | +4.1 pts | Medium | Web-Security Posture |
| Resolve the 1 Skipped test finding(s) in Test Quality — start with LoginHandlerUnitTest.cs. | +1.9 pts | Low | Test Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.1 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.9 | Slop | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 4.0 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| src/HRM.Infra.CrossCutting.IoC/HRM.Infra.CrossCutting.IoC.csproj | 4.4 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp2.2 |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/HRM.Infra.IdentityTest/HRM.Infra.IdentityUnitTests.csproj | 6.4 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp2.2 |
| src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs | 6.4 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/HRM.Infrastructure.UnitTests/UnitTest1.cs | 6.5 | Mixed | Test Quality: No assertions (empty test): TestMethod1 |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/HRM.Domain/Interfaces/IUser.cs | 7.3 | Mixed | Explicit Debt: Dead code: IsAuthenticated |
| src/HRM.Application/Services/AccountAppService.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/HRM.Domain/HRM.Domain.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp2.2 |
| src/HRM.Infra.CrossCutting.Bus/HRM.Infra.CrossCutting.Bus.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp2.2 |
| src/HRM.Infrastructure.UnitTests/HRM.Infrastructure.UnitTests.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp2.2 |
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 85 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 85 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, 179 of 200 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- 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 reliability not scored — the test tier(s) ran but surfaced none of this repository's 12 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 11 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits for a meaningful bus factor (11 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D28 Secrets (history) — 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. D28's config-credential rule (REDACTED) parses each committed `.json` config as a document and reads credential-named values; `src/HRM.Infra.CrossCutting.Identity/appsettings.json`, `src/HRM.Infra.Data/appsettings.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (11 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 11 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- 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 ToolchainServer (src/HRM.WebApi). the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'REDACTED'`: hare/dotnet/ The following frameworks were found: 6.0.36 at [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] 7.0.20 at [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] 8.0.27 at [/usr/sha…; runtime evidence skipped (launch chosen because REDACTED is a Microsoft.NET.Sdk.Web project).
- 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.
- ED5 Idempotency — 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 classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
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
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with EmployeeValidation.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 3) finding(s) in Code Duplication — start with AppIdentityDbContext.cs. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
10 projects, 0 dependency cycle(s), 1 unstable depended-on project(s).
What to do
- Resolve the 2 Layer violation finding(s) in Coupling — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Unstable project HRM.Infra.CrossCutting.IoC finding(s) in Coupling — start with HRM.Infra.CrossCutting.IoC.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 14 classes have LCOM4 above 3.
D9 · Test Distribution
12 test methods: 12 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
1 skipped, 1 zero-assertion, 2 mock references across 14 tests.
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with UnitTest1.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Skipped test finding(s) in Test Quality — start with LoginHandlerUnitTest.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with UnitTest1.cs. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
31 outdated, 4 vulnerable, 20 deprecated, 1 prerelease packages.
What to do
- Resolve the 27 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (11), REDACTED (8), REDACTED (4). — One of this dimension's main actionable groups (27 warning-level).
- Resolve the 23 Outdated finding(s) in Dependency Hygiene — start with REDACTED (10), REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (23 recommendation-level).
- Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 265 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 34 direct `PackageReference`(s), and 216 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
4 deducted debt markers + 10 dead symbols across 3018 LoC in the .NET projects (1.3/KLoC) → score 7.4.
What to do
- Resolve the 4 WriteOnlyPrivateField finding(s) in Explicit Debt — start with EmployeeCommandHandler.cs (2), AccountAppService.cs, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 10 Dead code finding(s) in Explicit Debt — start with IUser.cs (2), RouteConvention.cs, Employee.cs. — One of this dimension's main actionable groups (10 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
10 projects, 121 source files, 3369 hand-written lines of code (3018 production / 351 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 836 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 20 inter-project edges.
D19 · Documentation Quality
0 of 2 documentation facets pass in full; short on: F2 example, F4 map. 1 document(s) read across 9 unit(s).
What to do
- Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). — One of this dimension's main actionable groups (2 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
8 of 48 judged comments only repeat the code they sit on (16.7 %). 1 comment(s) in another language or script were not judged.
What to do
- Resolve the 8 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (3), REDACTED (2), JwtFactory.cs. — One of this dimension's main actionable groups (8 recommendation-level).
D26 · Project Cohesion
0 of 10 projects flagged as possibly oversized/incoherent.
D27 · Navigability
98 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 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 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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)
10 finding(s): 0 critical, 0 high, 10 medium, 0 low.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3). — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D30 · Dependency Vulnerabilities
19 finding(s): 2 critical, 7 high, 10 medium, 0 low.
What to do
- Resolve the 10 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
1 of 228 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 11 platform declaration(s) and 0 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.
What to do
- Resolve the 11 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (11 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
- `HRM.Application` is a Application project but references `HRM.Infra.CrossCutting.Identity`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — REDACTED:17
- This Application file depends on the Infrastructure project `HRM.Infra.CrossCutting.Identity`: it names `HRM.Infra.CrossCutting.Identity.Requests`, `HRM.Infra.CrossCutting.Identity.Responses`, `LoginResponse`, `ExchangeRefreshTokenResponse`. The inward dependency rule is broken here. It is named again on lines 3, 14, 15. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/HRM.Application/Interfaces/IAccountAppService.cs:2
- This Application file depends on the Infrastructure project `HRM.Infra.CrossCutting.Identity`: it names `HRM.Infra.CrossCutting.Identity.Interfaces`, `HRM.Infra.CrossCutting.Identity.Presenters`, `HRM.Infra.CrossCutting.Identity.Requests`, `HRM.Infra.CrossCutting.Identity.Responses`, `HRM.Infra.CrossCutting.Identity.Settings`, `ILoginHandler`, `IExchangeRefreshTokenHandler`, `LoginPresenter`, …. The inward dependency rule is broken here. It is named again on lines 4, 5, 6, 7, 18, 19, 20, 21, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/HRM.Application/Services/AccountAppService.cs:3
- `HRM.Application` is a Application project but references `HRM.Infra.Data`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — REDACTED:18
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
- Authorization machinery exists but no [Authorize] usage and no imperative guard calls were found at handlers.
What to do
- Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `Employee`'s public constructor takes `firstName`, `lastName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Employee` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/HRM.Domain/Entities/Employee.cs:27
- `RefreshToken`'s public constructor takes `token`, `remoteIpAddress` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `RefreshToken` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/HRM.Domain/Entities/Identity/RefreshToken.cs:16
- `User`'s public constructor takes `firstName`, `lastName`, `identityId`, `email`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `User` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/HRM.Domain/Entities/Identity/User.cs:24
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
- `EmployeeValidation` reads `DateTime.Now` inside `HaveMinimumAge`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/HRM.Domain/Validations/EmployeeValidation.cs:44
- `RefreshToken` reads `DateTime.Now` inside `Active`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/HRM.Domain/Entities/Identity/RefreshToken.cs:13
- `User` reads `DateTime.UtcNow` inside `AddRefreshToken`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/HRM.Domain/Entities/Identity/User.cs:41
What to do
- Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM2 · Strongly-typed ids
- `RefreshToken.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/HRM.Domain/Entities/Identity/RefreshToken.cs:12
- `User.IdentityId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/HRM.Domain/Entities/Identity/User.cs:14
- `DomainNotification.DomainNotificationId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/HRM.Domain.Core/Notifications/DomainNotification.cs:10
- `DomainNotification.Key` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/HRM.Domain.Core/Notifications/DomainNotification.cs:11
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `RefreshToken` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/HRM.Domain/Entities/Identity/RefreshToken.cs:8
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `Employee` exposes publicly writable state (Email). — src/HRM.Domain/Entities/Employee.cs:8
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
- `IRepository` returns `IQueryable` from `GetAll`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked. — src/HRM.Domain/Interfaces/IRepository.cs:7
What to do
- Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED3 · Event naming
- `DomainNotification` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — src/HRM.Domain.Core/Notifications/DomainNotification.cs:8
What to do
- Name events in the past tense — they record facts that already happened.
ED4 · Outbox / dual-write
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×4) — src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:31, src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:36, src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:41, …
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `Handle` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×3) — src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:31, src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:36, src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:41
- `IsValid` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/HRM.Domain/Commands/UpdateEmployeeCommand.cs:9
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 3 of 8 project(s) that lack one — worth up to 0.8 pts.
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
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:8
What to do
- Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- Identifier 'PasswordHash' looks like a password-hash field/property, but no KDF (PBKDF2 / Argon2 / BCrypt / PasswordHasher) was found anywhere in the source — so passwords aren't protected by a salted key-derivation function (whether a fast/plain hash, or a client-hashed value stored and compared verbatim). Password storage needs a salted KDF and a constant-time compare. — src/HRM.Domain/Entities/Identity/User.cs:17
- `ValidateAudience`, `ValidateIssuer`, `ValidateLifetime` are all set to `false`, which means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. — REDACTED:22
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — src/HRM.WebApi/Program.cs:21
What to do
- Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/HRM.Domain/Entities/Identity/User.cs:17`.
- Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `_context` is never created by `EventStoreRepository` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 31). Its declared type `EventSourcingContext` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/HRM.Infra.Data/Repository/EventSourcing/EventStoreRepository.cs:31
- `DbContext` is never created by `Repository` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 83). Its declared type `HRMContext` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/HRM.Infra.Data/Repository/Repository.cs:83
- `_context` is never created by `UnitOfWork` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 22). Its declared type `HRMContext` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/HRM.Infra.Data/UoW/UnitOfWork.cs:22
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/17 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×17) — src/HRM.Application/Services/AccountAppService.cs:41, src/HRM.Application/Services/AccountAppService.cs:47, src/HRM.Application/Services/AccountAppService.cs:53, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. — src/HRM.Infra.CrossCutting.Identity/Auth/JwtTokenHandler.cs:41
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 60% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 73% | Strong | Solid. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 30% | Weak — gated by D13, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 32% | Weak — gated by C1, C2, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 54% | Adequate — gated by DM2, DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 6 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data (event-sourced storage — lifecycle is stream archival / event TTL, not row CASCADE) — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 41 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 — the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'REDACTED'`: hare/dotnet/ The following frameworks were found: 6.0.36 at [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] 7.0.20 at [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] 8.0.27 at [/usr/sha…; runtime evidence skipped (launch chosen because REDACTED is a Microsoft.NET.Sdk.Web project) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D11 Test Reliability — Test runner surfaced no tests
- D16 Bus Factor — too few commits for a meaningful bus factor
- D21 Naming Consistency — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (3,018 production LoC in the .NET projects) — bounded contexts are not needed at this size 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 (HRM.Domain), 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"]`.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED5 Idempotency — not scored — 3 of 4 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an append-only event-store seam (IEventStore/Append-of-events))
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) 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 — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- 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.
- X5 Nullable reference types — no NRT-eligible projects
- 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 — 22 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField src/HRM.Application/Services/AccountAppService.cs:23
- WriteOnlyPrivateField src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:19
- WriteOnlyPrivateField src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:20
- WriteOnlyPrivateField REDACTED:21
- Dependency-rule violation: HRM.Application (Application) → HRM.Infra.CrossCutting.Identity (Infrastructure) REDACTED:17
- Dependency-rule violation: HRM.Application (Application) → HRM.Infra.Data (Infrastructure) REDACTED:18
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Layer violation: Application → Infrastructure REDACTED:17
- Layer violation: Application → Infrastructure REDACTED:18
- No assertions (empty test): TestMethod1 src/HRM.Infrastructure.UnitTests/UnitTest1.cs:8
- REDACTED
- Password hashing without a KDF src/HRM.Domain/Entities/Identity/User.cs:17
Serious — 116 finding(s)
- Deprecated: Microsoft.NETCore.App REDACTED:13
- Deprecated: FluentValidation.AspNetCore REDACTED:12
- Deprecated: Microsoft.AspNetCore.App REDACTED:14
- Deprecated: Microsoft.AspNetCore.App REDACTED:18
- Deprecated: Microsoft.AspNetCore.Razor.Design REDACTED:15
- Deprecated: Microsoft.Extensions.Configuration.UserSecrets REDACTED:16
- Deprecated: xunit REDACTED:11
- Deprecated: xunit src/HRM.Infra.IdentityTest/HRM.Infra.IdentityUnitTests.csproj:12
- Deprecated: Microsoft.AspNetCore.Authorization REDACTED:15
- Deprecated: Microsoft.AspNetCore.Identity REDACTED:16
- Deprecated: Microsoft.AspNetCore.Identity.EntityFrameworkCore REDACTED:17
- Deprecated: Microsoft.EntityFrameworkCore.Design REDACTED:18
- Deprecated: Microsoft.EntityFrameworkCore.Design REDACTED:20
- Deprecated: Microsoft.EntityFrameworkCore.SqlServer REDACTED:19
- Deprecated: Microsoft.EntityFrameworkCore.SqlServer REDACTED:21
- Deprecated: Microsoft.EntityFrameworkCore.Tools REDACTED:20
- Deprecated: Microsoft.Extensions.Configuration REDACTED:24
- Deprecated: Microsoft.Extensions.Configuration REDACTED:22
- Deprecated: Microsoft.Extensions.Configuration.FileExtensions REDACTED:25
- Deprecated: Microsoft.Extensions.Configuration.FileExtensions REDACTED:24
- Deprecated: Microsoft.Extensions.Configuration.Json REDACTED:26
- Deprecated: Microsoft.Extensions.Configuration.Json REDACTED:25
- Deprecated: Microsoft.IdentityModel.Tokens REDACTED:27
- Deprecated: System.IdentityModel.Tokens.Jwt REDACTED:28
- Deprecated: Microsoft.Extensions.DependencyInjection.Abstractions src/HRM.Infra.CrossCutting.IoC/HRM.Infra.CrossCutting.IoC.csproj:8
- Async method without CancellationToken: Login src/HRM.Application/Services/AccountAppService.cs:41
- Async method without CancellationToken: RefreshToken src/HRM.Application/Services/AccountAppService.cs:47
- Async method without CancellationToken: Register src/HRM.Application/Services/AccountAppService.cs:53
- Async method without CancellationToken: Login REDACTED:35
- Async method without CancellationToken: RefreshToken REDACTED:49
- Async method without CancellationToken: Post REDACTED:58
- Async method without CancellationToken: SendCommand src/HRM.Infra.CrossCutting.Bus/InMemoryBus.cs:19
- Async method without CancellationToken: RaiseEvent src/HRM.Infra.CrossCutting.Bus/InMemoryBus.cs:24
- Async method without CancellationToken: Handle src/HRM.Infra.CrossCutting.Identity/AuthHandlers/ExchangeRefreshTokenHandler.cs:40
- Async method without CancellationToken: Handle src/HRM.Infra.CrossCutting.Identity/AuthHandlers/LoginHandler.cs:37
- Async method without CancellationToken: Handle src/HRM.Infra.CrossCutting.Identity/AuthHandlers/RegisterUserHandler.cs:40
- Async method without CancellationToken: FindByName src/HRM.Infra.CrossCutting.Identity/Repositories/UserRepository.cs:28
- Async method without CancellationToken: AddAsync src/HRM.Infra.Data/Repository/Repository.cs:22
- Async method without CancellationToken: GetByIdAsync src/HRM.Infra.Data/Repository/Repository.cs:27
- Async method without CancellationToken: GetSingleBySpec src/HRM.Infra.Data/Repository/Repository.cs:32
- Async method without CancellationToken: List src/HRM.Infra.Data/Repository/Repository.cs:38
- Async method without CancellationToken: SaveChangesAsync src/HRM.Infra.Data/Repository/Repository.cs:76
- End-of-life runtime: .NET netcoreapp2.2 REDACTED:4
- End-of-life runtime: .NET netcoreapp2.2 REDACTED:4
- End-of-life runtime: .NET netcoreapp2.2 REDACTED:4
- End-of-life runtime: .NET netcoreapp2.2 src/HRM.Domain/HRM.Domain.csproj:4
- End-of-life runtime: .NET netcoreapp2.2 src/HRM.Infra.CrossCutting.Bus/HRM.Infra.CrossCutting.Bus.csproj:4
- End-of-life runtime: .NET netcoreapp2.2 REDACTED:4
- End-of-life runtime: .NET netcoreapp2.2 src/HRM.Infra.CrossCutting.IoC/HRM.Infra.CrossCutting.IoC.csproj:4
- End-of-life runtime: .NET netcoreapp2.2 REDACTED:4
- End-of-life runtime: .NET netcoreapp2.2 src/HRM.Infra.IdentityTest/HRM.Infra.IdentityUnitTests.csproj:4
- End-of-life runtime: .NET netcoreapp2.2 src/HRM.Infrastructure.UnitTests/HRM.Infrastructure.UnitTests.csproj:4
- End-of-life runtime: .NET netcoreapp2.2 REDACTED:4
- Dead code: UseCentralRoutePrefix src/HRM.WebApi/Configurations/RouteConvention.cs:46
- Dead code: UpdateAddress src/HRM.Domain/Entities/Employee.cs:39
- Dead code: IHandler src/HRM.Domain/Interfaces/IHandler.cs:7
- Dead code: IsAuthenticated src/HRM.Domain/Interfaces/IUser.cs:10
- Dead code: GetClaimsIdentity src/HRM.Domain/Interfaces/IUser.cs:11
- Dead code: SendCommand src/HRM.Domain.Core/Bus/IMediatorHandler.cs:12
- Dead code: Request src/HRM.Domain.Core/Requests/Request.cs:8
- Dead code: SendEmailAsync src/HRM.Domain.Core/Services/IEmailSender.cs:10
- Dead code: SendSmsAsync src/HRM.Domain.Core/Services/ISmsSender.cs:10
- Dead code: Error src/HRM.Infra.CrossCutting.Identity/Dto/Error.cs:7
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unfinished stub — throws NotImplementedException src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:31
- Unfinished stub — throws NotImplementedException src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:36
- Unfinished stub — throws NotImplementedException src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:41
- Unfinished stub — throws NotImplementedException src/HRM.Domain/Commands/UpdateEmployeeCommand.cs:9
- Unfinished stub — throws NotImplementedException src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:31
- Unfinished stub — throws NotImplementedException src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:36
- Unfinished stub — throws NotImplementedException src/HRM.Domain/CommandHandlers/EmployeeCommandHandler.cs:41
- Unfinished stub — throws NotImplementedException src/HRM.Domain/Commands/UpdateEmployeeCommand.cs:9
- Constructible in an invalid state: Employee src/HRM.Domain/Entities/Employee.cs:27
- Constructible in an invalid state: RefreshToken src/HRM.Domain/Entities/Identity/RefreshToken.cs:16
- Constructible in an invalid state: User src/HRM.Domain/Entities/Identity/User.cs:24
- Domain type reads the wall clock: EmployeeValidation src/HRM.Domain/Validations/EmployeeValidation.cs:44
- Domain type reads the wall clock: RefreshToken src/HRM.Domain/Entities/Identity/RefreshToken.cs:13
- Domain type reads the wall clock: User src/HRM.Domain/Entities/Identity/User.cs:41
- Disposes a dependency it does not own src/HRM.Infra.Data/Repository/EventSourcing/EventStoreRepository.cs:31
- Disposes a dependency it does not own src/HRM.Infra.Data/Repository/Repository.cs:83
- Disposes a dependency it does not own src/HRM.Infra.Data/UoW/UnitOfWork.cs:22
- Dependency-rule violation: HRM.Application (Application) → HRM.Infra.CrossCutting.Identity (Infrastructure) src/HRM.Application/Interfaces/IAccountAppService.cs:2
- Dependency-rule violation: HRM.Application (Application) → HRM.Infra.CrossCutting.Identity (Infrastructure) src/HRM.Application/Services/AccountAppService.cs:3
- REDACTED
- REDACTED
- No data-protection/encryption
- Skipped test: Handle_GivenValidCredentials_ShouldSucceed src/HRM.Infrastructure.UnitTests/Handlers/LoginHandlerUnitTest.cs:23
- Test project verifies nothing: HRM.Infrastructure.UnitTests src/HRM.Infrastructure.UnitTests/UnitTest1.cs:8
- Prerelease dependency: Microsoft.VisualStudio.Web.CodeGeneration.Design
- Duplicated block (6 lines × 2) src/HRM.Domain/Validations/EmployeeValidation.cs:28
- Duplicated block (8 lines × 3) src/HRM.Infra.CrossCutting.Identity/Models/AppIdentityDbContext.cs:17
- Unstable project HRM.Infra.CrossCutting.IoC src/HRM.Infra.CrossCutting.IoC/HRM.Infra.CrossCutting.IoC.csproj:1
- Anemic entity: RefreshToken src/HRM.Domain/Entities/Identity/RefreshToken.cs:8
- Repository contract exposes a live query handle: IRepository src/HRM.Domain/Interfaces/IRepository.cs:7
- No CI pipeline
- Token validation disabled REDACTED:22
- NuGet dependencies are not locked
Minor — 52 finding(s)
- Outdated: AutoMapper REDACTED:8
- Outdated: AutoMapper.Extensions.Microsoft.DependencyInjection REDACTED:11
- Outdated: FluentValidation.AspNetCore REDACTED:12
- Outdated: MediatR.Extensions.Microsoft.DependencyInjection REDACTED:13
- Outdated: Microsoft.Extensions.Configuration.UserSecrets REDACTED:16
- Outdated: Microsoft.VisualStudio.Web.CodeGeneration.Design REDACTED:17
- Outdated: Swashbuckle.AspNetCore REDACTED:18
- Outdated: FluentValidation REDACTED:8
- Outdated: MediatR REDACTED:9
- Outdated: Microsoft.NET.Test.Sdk REDACTED:10
- Outdated: Microsoft.AspNetCore.Authorization REDACTED:15
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore REDACTED:17
- Outdated: Microsoft.EntityFrameworkCore.Design REDACTED:18
- Outdated: Microsoft.EntityFrameworkCore.SqlServer REDACTED:19
- Outdated: Microsoft.EntityFrameworkCore.Tools REDACTED:20
- Outdated: Microsoft.Extensions.Configuration REDACTED:24
- Outdated: Microsoft.Extensions.Configuration.FileExtensions REDACTED:25
- Outdated: Microsoft.Extensions.Configuration.Json REDACTED:26
- Outdated: Microsoft.IdentityModel.Tokens REDACTED:27
- Outdated: System.IdentityModel.Tokens.Jwt REDACTED:28
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions src/HRM.Infra.CrossCutting.IoC/HRM.Infra.CrossCutting.IoC.csproj:8
- Outdated: Microsoft.EntityFrameworkCore REDACTED:19
- Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables REDACTED:23
- redundant comment src/HRM.Infra.CrossCutting.Identity/Auth/JwtFactory.cs:39
- redundant comment src/HRM.Infra.CrossCutting.Identity/AuthHandlers/LoginHandler.cs:52
- redundant comment src/HRM.Infra.CrossCutting.Identity/AuthHandlers/RegisterUserHandler.cs:53
- redundant comment src/HRM.Infra.Data/Properties/AssemblyInfo.cs:4
- redundant comment src/HRM.Infra.Data/Properties/AssemblyInfo.cs:12
- redundant comment src/HRM.Infra.Data/Properties/AssemblyInfo.cs:17
- redundant comment REDACTED:59
- redundant comment REDACTED:63
- Primitive id on a domain type: RefreshToken.UserId src/HRM.Domain/Entities/Identity/RefreshToken.cs:12
- Primitive id on a domain type: User.IdentityId src/HRM.Domain/Entities/Identity/User.cs:14
- Primitive id on a domain type: DomainNotification.DomainNotificationId src/HRM.Domain.Core/Notifications/DomainNotification.cs:10
- Primitive id on a domain type: DomainNotification.Key src/HRM.Domain.Core/Notifications/DomainNotification.cs:11
- Documentation: no build, run or usage example README.md:1
- Documentation: no map of the repository's parts README.md:1
- No security response headers detected
- No security response headers detected src/HRM.WebApi/Program.cs:21
- Duplicated predicate src/HRM.Domain.Core/Model/Entity.cs:29
- Duplicated predicate src/HRM.Domain.Core/Model/Entity.cs:32
- Thin authorization enforcement
- No ADRs found
- REDACTED
- IL efficiency: 1 authored method(s) exceed the IL budget src/HRM.Infra.Data/Mappings/EmployeeMap.cs:11
- Mutable entity: Employee src/HRM.Domain/Entities/Employee.cs:8
- Event not named in past tense: DomainNotification src/HRM.Domain.Core/Notifications/DomainNotification.cs:8
- No ADRs
- No SAST
- No dependency-update automation REDACTED:8
- Not all async methods take a CancellationToken
- Interpolated log message defeats structured logging src/HRM.Infra.CrossCutting.Identity/Auth/JwtTokenHandler.cs:41
Minor — 10 finding(s)
- Outdated: Microsoft.AspNetCore.App
- Outdated: Microsoft.AspNetCore.Razor.Design
- Outdated: System.ComponentModel.Annotations
- Outdated: xunit
- Outdated: xunit.runner.visualstudio
- Outdated: Microsoft.AspNetCore.Identity
- Outdated: System.Reflection.TypeExtensions
- Outdated: Moq
- Mock framework: Moq
- Mock framework: Moq
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-e7b7cdf30ee64d769df3bb9d72766562/history.json --exit-code 0 --source . | 2 | 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-e7b7cdf30ee64d769df3bb9d72766562/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/HRM.Infra.CrossCutting.Identity/Migrations --exclude src/HRM.Infra.Data/Migrations . | 10 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list HRM.sln package --vulnerable --include-transitive --format json | 19 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-ff913a4ea82c4603b66f9d4a873696cf | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 12 field(s)
- EmployeeViewModel.FirstName src/HRM.Application/ViewModels/EmployeeViewModel.cs:17
- EmployeeViewModel.LastName src/HRM.Application/ViewModels/EmployeeViewModel.cs:23
- RegisterUserViewModel.FirstName src/HRM.Application/ViewModels/RegisterUserViewModel.cs:9
- RegisterUserViewModel.LastName src/HRM.Application/ViewModels/RegisterUserViewModel.cs:10
- EmployeeCommand.FirstName src/HRM.Domain/Commands/EmployeeCommand.cs:29
- EmployeeCommand.LastName src/HRM.Domain/Commands/EmployeeCommand.cs:31
- User.FirstName src/HRM.Domain/Entities/Identity/User.cs:12
- User.LastName src/HRM.Domain/Entities/Identity/User.cs:13
- Person.FirstName src/HRM.Domain/SharedKernel/Person.cs:10
- Person.LastName src/HRM.Domain/SharedKernel/Person.cs:12
- AuthRequest.FirstName src/HRM.Infra.CrossCutting.Identity/Requests/AuthRequest.cs:15
- AuthRequest.LastName src/HRM.Infra.CrossCutting.Identity/Requests/AuthRequest.cs:16
Email — 10 field(s)
- EmployeeViewModel.Email src/HRM.Application/ViewModels/EmployeeViewModel.cs:28
- LoginViewModel.Email src/HRM.Application/ViewModels/LoginViewModel.cs:12
- RegisterUserViewModel.Email src/HRM.Application/ViewModels/RegisterUserViewModel.cs:11
- EmployeeCommand.Email src/HRM.Domain/Commands/EmployeeCommand.cs:33
- Employee.Email src/HRM.Domain/Entities/Employee.cs:22
- User.Email src/HRM.Domain/Entities/Identity/User.cs:16
- EmployeeRegisteredEvent.Email src/HRM.Domain/Events/EmployeeRegisteredEvent.cs:20
- EmployeeUpdatedEvent.Email src/HRM.Domain/Events/EmployeeUpdatedEvent.cs:20
- UserRegisteredEvent.Email src/HRM.Infra.CrossCutting.Identity/Events/UserRegisteredEvent.cs:21
- AuthRequest.Email src/HRM.Infra.CrossCutting.Identity/Requests/AuthRequest.cs:13
Date of birth — 5 field(s)
- EmployeeViewModel.Dob src/HRM.Application/ViewModels/EmployeeViewModel.cs:34
- EmployeeCommand.Dob src/HRM.Domain/Commands/EmployeeCommand.cs:37
- EmployeeRegisteredEvent.BirthDate src/HRM.Domain/Events/EmployeeRegisteredEvent.cs:22
- EmployeeUpdatedEvent.BirthDate src/HRM.Domain/Events/EmployeeUpdatedEvent.cs:22
- Person.Dob src/HRM.Domain/SharedKernel/Person.cs:16
Address — 2 field(s)
- EmployeeCommand.ZipCode src/HRM.Domain/Commands/EmployeeCommand.cs:25
- Address.ZipCode src/HRM.Domain/SharedKernel/Address.cs:17