Executive summary
spaki/Pluto is rated At risk because critical security findings are open, all of them in the packages it uses. Its score is held back in part because the project has no automated tests. It scores 40 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 18, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 17 points. Updating the outdated dependencies comes next, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 56.
Eleven known security holes in the packages the code depends on can be used by attackers. The project has no automated tests, so a change can break it without warning. Adding automated tests and updating the vulnerable packages would close both risks. Referring to the other business object by its identifier would take care of the two business objects holding another business object directly.
The product code is 2,385 lines, about €2,500 to rebuild.
If Production Readiness rose from 18 to 70, the lowest score rated Strong, the score would rise from 40 to about 56.
New since the last survey: 4 findings
- Rich vs anemic model · Anemic entity: OrderItem Pluto.Domain/Models/OrderItem.cs
- Ambient inputs in the domain · Domain type reads the wall clock: Order Pluto.Domain/Models/Order.cs
- Ambient inputs in the domain · Domain type reads the wall clock: Order Pluto.Domain/Models/Order.cs
- Ambient inputs in the domain · Domain type reads the wall clock: Order Pluto.Domain/Models/Order.cs
Fixed since the last survey: 4 findings
- Dependency Hygiene · Vulnerable: Newtonsoft.Json
- Dependency Hygiene · Vulnerable: Microsoft.AspNetCore.App
- Dependency Hygiene · Vulnerable: Microsoft.NETCore.App
- Ambient inputs in the domain · Domain type reads the wall clock: Order Pluto.Domain/Models/Order.cs
Rebuild cost: about €2,500 · Estimate
| Cost to rebuild | €870 to €4,200, for 15 to 44 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.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: 2,385 lines of product code, of which 53% is declarations and boilerplate, 42% straight logic and 5% 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 API.Automapper | 2 API.Settings | 3 Domain.Constants | 4 Domain.Dtos | 5 Domain.Enums | 6 Domain.Events.Common | 7 Domain.Events.Interfaces | 8 Domain.Interfaces.Identity | 9 Domain.Models.Common | 10 Repository.Config | 11 Repository.Contexts | 12 Repository.Mapping.Common | 13 Utils.Cryptography | 14 Utils.Validations | 15 API | 16 API.Setup | 17 Domain.Commands.Common | 18 Domain.Events.Product | 19 Domain.Events.User | 20 Domain.Interfaces.Repositories.Common | 21 Domain.Models | 22 Domain.Notifications | 23 API.Auth | 24 Domain.Bus | 25 Domain.Commands.Order | 26 Domain.Commands.Product | 27 Domain.Commands.User | 28 Domain.Events.Order | 29 Domain.Interfaces.Repositories | 30 Repository.Mapping | 31 Repository.Repositories.Common | 32 Repository.UoW | 33 API.Controllers.Common | 34 Bus | 35 Domain.Handlers.Common | 36 Domain.Handlers.Events | 37 Repository.Repositories | 38 API.Controllers | 39 Domain.Handlers.Commands |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 API.Automapper | |||||||||||||||||||||||||||||||||||||||
| 2 API.Settings | |||||||||||||||||||||||||||||||||||||||
| 3 Domain.Constants | |||||||||||||||||||||||||||||||||||||||
| 4 Domain.Dtos | |||||||||||||||||||||||||||||||||||||||
| 5 Domain.Enums | |||||||||||||||||||||||||||||||||||||||
| 6 Domain.Events.Common | |||||||||||||||||||||||||||||||||||||||
| 7 Domain.Events.Interfaces | |||||||||||||||||||||||||||||||||||||||
| 8 Domain.Interfaces.Identity | |||||||||||||||||||||||||||||||||||||||
| 9 Domain.Models.Common | |||||||||||||||||||||||||||||||||||||||
| 10 Repository.Config | |||||||||||||||||||||||||||||||||||||||
| 11 Repository.Contexts | |||||||||||||||||||||||||||||||||||||||
| 12 Repository.Mapping.Common | |||||||||||||||||||||||||||||||||||||||
| 13 Utils.Cryptography | |||||||||||||||||||||||||||||||||||||||
| 14 Utils.Validations | |||||||||||||||||||||||||||||||||||||||
| 15 API | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 API.Setup | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 Domain.Commands.Common | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 Domain.Events.Product | 3 | ||||||||||||||||||||||||||||||||||||||
| 19 Domain.Events.User | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 20 Domain.Interfaces.Repositories.Common | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Domain.Models | 2 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 22 Domain.Notifications | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 API.Auth | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 24 Domain.Bus | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Domain.Commands.Order | 6 | ||||||||||||||||||||||||||||||||||||||
| 26 Domain.Commands.Product | 3 | ||||||||||||||||||||||||||||||||||||||
| 27 Domain.Commands.User | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 28 Domain.Events.Order | 6 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 Domain.Interfaces.Repositories | 4 | ||||||||||||||||||||||||||||||||||||||
| 30 Repository.Mapping | 6 | 6 | 6 | ||||||||||||||||||||||||||||||||||||
| 31 Repository.Repositories.Common | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 Repository.UoW | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 API.Controllers.Common | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 Bus | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 Domain.Handlers.Common | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 Domain.Handlers.Events | 3 | 4 | 6 | ||||||||||||||||||||||||||||||||||||
| 37 Repository.Repositories | 1 | 4 | 4 | 4 | |||||||||||||||||||||||||||||||||||
| 38 API.Controllers | 1 | 1 | 4 | 2 | 4 | 2 | 2 | 3 | 5 | 4 | |||||||||||||||||||||||||||||
| 39 Domain.Handlers.Commands | 3 | 2 | 3 | 3 | 6 | 3 | 4 | 5 | 3 |
15→2 API uses API.Settings✕
- Connections
- 1 pair of types, where a type in API uses a type in API.Settings.
- The types involved
Pluto.API.Startup→Pluto.API.Settings.AppSettings
- Direction
- API uses API.Settings, so a change to API.Settings can break API, while a change to API can't break API.Settings.
- Position
- Below the diagonal: API uses a module listed above it, which is the healthy direction.
16→2 API.Setup uses API.Settings✕
- Connections
- 1 pair of types, where a type in API.Setup uses a type in API.Settings.
- The types involved
Pluto.API.Setup.SetupHelper→Pluto.API.Settings.AppSettings
- Direction
- API.Setup uses API.Settings, so a change to API.Settings can break API.Setup, while a change to API.Setup can't break API.Settings.
- Position
- Below the diagonal: API.Setup uses a module listed above it, which is the healthy direction.
17→6 Domain.Commands.Common uses Domain.Events.Common✕
- Connections
- 1 pair of types, where a type in Domain.Commands.Common uses a type in Domain.Events.Common.
- The types involved
Pluto.Domain.Commands.Common.Command→Pluto.Domain.Events.Common.Message
- Direction
- Domain.Commands.Common uses Domain.Events.Common, so a change to Domain.Events.Common can break Domain.Commands.Common, while a change to Domain.Commands.Common can't break Domain.Events.Common.
- Position
- Below the diagonal: Domain.Commands.Common uses a module listed above it, which is the healthy direction.
18→6 Domain.Events.Product uses Domain.Events.Common✕
- Connections
- 3 pairs of types, where a type in Domain.Events.Product uses a type in Domain.Events.Common.
- The types involved
Pluto.Domain.Events.Product.CreateProductEvent→Pluto.Domain.Events.Common.EventPluto.Domain.Events.Product.DeleteProductEvent→Pluto.Domain.Events.Common.EventPluto.Domain.Events.Product.UpdateProductEvent→Pluto.Domain.Events.Common.Event
- Direction
- Domain.Events.Product uses Domain.Events.Common, so a change to Domain.Events.Common can break Domain.Events.Product, while a change to Domain.Events.Product can't break Domain.Events.Common.
- Position
- Below the diagonal: Domain.Events.Product uses a module listed above it, which is the healthy direction.
19→5 Domain.Events.User uses Domain.Enums✕
- Connections
- 2 pairs of types, where a type in Domain.Events.User uses a type in Domain.Enums.
- The types involved
Pluto.Domain.Events.User.CreateUserEvent→Pluto.Domain.Enums.UserProfilePluto.Domain.Events.User.UpdateUserEvent→Pluto.Domain.Enums.UserProfile
- Direction
- Domain.Events.User uses Domain.Enums, so a change to Domain.Enums can break Domain.Events.User, while a change to Domain.Events.User can't break Domain.Enums.
- Position
- Below the diagonal: Domain.Events.User uses a module listed above it, which is the healthy direction.
19→6 Domain.Events.User uses Domain.Events.Common✕
- Connections
- 4 pairs of types, where a type in Domain.Events.User uses a type in Domain.Events.Common.
- The types involved
Pluto.Domain.Events.User.ChangeUserPasswordEvent→Pluto.Domain.Events.Common.EventPluto.Domain.Events.User.CreateUserEvent→Pluto.Domain.Events.Common.EventPluto.Domain.Events.User.DeleteUserEvent→Pluto.Domain.Events.Common.EventPluto.Domain.Events.User.UpdateUserEvent→Pluto.Domain.Events.Common.Event
- Direction
- Domain.Events.User uses Domain.Events.Common, so a change to Domain.Events.Common can break Domain.Events.User, while a change to Domain.Events.User can't break Domain.Events.Common.
- Position
- Below the diagonal: Domain.Events.User uses a module listed above it, which is the healthy direction.
20→9 Domain.Interfaces.Repositories.Common uses Domain.Models.Common✕
- Connections
- 1 pair of types, where a type in Domain.Interfaces.Repositories.Common uses a type in Domain.Models.Common.
- The types involved
Pluto.Domain.Interfaces.Repositories.Common.ICrudRepository→Pluto.Domain.Models.Common.PagedResult
- Direction
- Domain.Interfaces.Repositories.Common uses Domain.Models.Common, so a change to Domain.Models.Common can break Domain.Interfaces.Repositories.Common, while a change to Domain.Interfaces.Repositories.Common can't break Domain.Models.Common.
- Position
- Below the diagonal: Domain.Interfaces.Repositories.Common uses a module listed above it, which is the healthy direction.
21→5 Domain.Models uses Domain.Enums✕
- Connections
- 2 pairs of types, where a type in Domain.Models uses a type in Domain.Enums.
- The types involved
Pluto.Domain.Models.Order→Pluto.Domain.Enums.OrderStatusPluto.Domain.Models.User→Pluto.Domain.Enums.UserProfile
- Direction
- Domain.Models uses Domain.Enums, so a change to Domain.Enums can break Domain.Models, while a change to Domain.Models can't break Domain.Enums.
- Position
- Below the diagonal: Domain.Models uses a module listed above it, which is the healthy direction.
21→6 Domain.Models uses Domain.Events.Common✕
- Connections
- 1 pair of types, where a type in Domain.Models uses a type in Domain.Events.Common.
- The types involved
Pluto.Domain.Models.StoredEvent→Pluto.Domain.Events.Common.Event
- Direction
- Domain.Models uses Domain.Events.Common, so a change to Domain.Events.Common can break Domain.Models, while a change to Domain.Models can't break Domain.Events.Common.
- Position
- Below the diagonal: Domain.Models uses a module listed above it, which is the healthy direction.
21→9 Domain.Models uses Domain.Models.Common✕
- Connections
- 6 pairs of types, where a type in Domain.Models uses a type in Domain.Models.Common.
- The types involved
Pluto.Domain.Models.Order→Pluto.Domain.Models.Common.EntityPluto.Domain.Models.OrderItem→Pluto.Domain.Models.Common.EntityPluto.Domain.Models.PictureUrl→Pluto.Domain.Models.Common.EntityPluto.Domain.Models.Product→Pluto.Domain.Models.Common.EntityPluto.Domain.Models.StoredEvent→Pluto.Domain.Models.Common.EntityPluto.Domain.Models.User→Pluto.Domain.Models.Common.Entity
- Direction
- Domain.Models uses Domain.Models.Common, so a change to Domain.Models.Common can break Domain.Models, while a change to Domain.Models can't break Domain.Models.Common.
- Position
- Below the diagonal: Domain.Models uses a module listed above it, which is the healthy direction.
22→6 Domain.Notifications uses Domain.Events.Common✕
- Connections
- 1 pair of types, where a type in Domain.Notifications uses a type in Domain.Events.Common.
- The types involved
Pluto.Domain.Notifications.DomainNotification→Pluto.Domain.Events.Common.Event
- Direction
- Domain.Notifications uses Domain.Events.Common, so a change to Domain.Events.Common can break Domain.Notifications, while a change to Domain.Notifications can't break Domain.Events.Common.
- Position
- Below the diagonal: Domain.Notifications uses a module listed above it, which is the healthy direction.
23→2 API.Auth uses API.Settings✕
- Connections
- 1 pair of types, where a type in API.Auth uses a type in API.Settings.
- The types involved
Pluto.API.Auth.AuthConfigHelper→Pluto.API.Settings.AppSettings
- Direction
- API.Auth uses API.Settings, so a change to API.Settings can break API.Auth, while a change to API.Auth can't break API.Settings.
- Position
- Below the diagonal: API.Auth uses a module listed above it, which is the healthy direction.
23→5 API.Auth uses Domain.Enums✕
- Connections
- 1 pair of types, where a type in API.Auth uses a type in Domain.Enums.
- The types involved
Pluto.API.Auth.BaererAuthorizeAttribute→Pluto.Domain.Enums.UserProfile
- Direction
- API.Auth uses Domain.Enums, so a change to Domain.Enums can break API.Auth, while a change to API.Auth can't break Domain.Enums.
- Position
- Below the diagonal: API.Auth uses a module listed above it, which is the healthy direction.
23→8 API.Auth uses Domain.Interfaces.Identity✕
- Connections
- 1 pair of types, where a type in API.Auth uses a type in Domain.Interfaces.Identity.
- The types involved
Pluto.API.Auth.UserControl→Pluto.Domain.Interfaces.Identity.IUser
- Direction
- API.Auth uses Domain.Interfaces.Identity, so a change to Domain.Interfaces.Identity can break API.Auth, while a change to API.Auth can't break Domain.Interfaces.Identity.
- Position
- Below the diagonal: API.Auth uses a module listed above it, which is the healthy direction.
23→21 API.Auth uses Domain.Models✕
- Connections
- 1 pair of types, where a type in API.Auth uses a type in Domain.Models.
- The types involved
Pluto.API.Auth.AuthConfigHelper→Pluto.Domain.Models.User
- Direction
- API.Auth uses Domain.Models, so a change to Domain.Models can break API.Auth, while a change to API.Auth can't break Domain.Models.
- Position
- Below the diagonal: API.Auth uses a module listed above it, which is the healthy direction.
24→17 Domain.Bus uses Domain.Commands.Common✕
- Connections
- 1 pair of types, where a type in Domain.Bus uses a type in Domain.Commands.Common.
- The types involved
Pluto.Domain.Bus.IMediatorHandler→Pluto.Domain.Commands.Common.RequestCommand
- Direction
- Domain.Bus uses Domain.Commands.Common, so a change to Domain.Commands.Common can break Domain.Bus, while a change to Domain.Bus can't break Domain.Commands.Common.
- Position
- Below the diagonal: Domain.Bus uses a module listed above it, which is the healthy direction.
25→17 Domain.Commands.Order uses Domain.Commands.Common✕
- Connections
- 6 pairs of types, where a type in Domain.Commands.Order uses a type in Domain.Commands.Common.
- The types involved
Pluto.Domain.Commands.Order.AddProductCommand→Pluto.Domain.Commands.Common.CommandPluto.Domain.Commands.Order.ApproveOrderCommand→Pluto.Domain.Commands.Common.CommandPluto.Domain.Commands.Order.CancelOrderCommand→Pluto.Domain.Commands.Common.CommandPluto.Domain.Commands.Order.CommitOrderCommand→Pluto.Domain.Commands.Common.CommandPluto.Domain.Commands.Order.CreateOrderCommand→Pluto.Domain.Commands.Common.RequestCommandPluto.Domain.Commands.Order.RemoveProductCommand→Pluto.Domain.Commands.Common.Command
- Direction
- Domain.Commands.Order uses Domain.Commands.Common, so a change to Domain.Commands.Common can break Domain.Commands.Order, while a change to Domain.Commands.Order can't break Domain.Commands.Common.
- Position
- Below the diagonal: Domain.Commands.Order uses a module listed above it, which is the healthy direction.
26→17 Domain.Commands.Product uses Domain.Commands.Common✕
- Connections
- 3 pairs of types, where a type in Domain.Commands.Product uses a type in Domain.Commands.Common.
- The types involved
Pluto.Domain.Commands.Product.CreateProductCommand→Pluto.Domain.Commands.Common.RequestCommandPluto.Domain.Commands.Product.DeleteProductCommand→Pluto.Domain.Commands.Common.CommandPluto.Domain.Commands.Product.UpdateProductCommand→Pluto.Domain.Commands.Common.Command
- Direction
- Domain.Commands.Product uses Domain.Commands.Common, so a change to Domain.Commands.Common can break Domain.Commands.Product, while a change to Domain.Commands.Product can't break Domain.Commands.Common.
- Position
- Below the diagonal: Domain.Commands.Product uses a module listed above it, which is the healthy direction.
27→5 Domain.Commands.User uses Domain.Enums✕
- Connections
- 2 pairs of types, where a type in Domain.Commands.User uses a type in Domain.Enums.
- The types involved
Pluto.Domain.Commands.User.CreateUserCommand→Pluto.Domain.Enums.UserProfilePluto.Domain.Commands.User.UpdateUserCommand→Pluto.Domain.Enums.UserProfile
- Direction
- Domain.Commands.User uses Domain.Enums, so a change to Domain.Enums can break Domain.Commands.User, while a change to Domain.Commands.User can't break Domain.Enums.
- Position
- Below the diagonal: Domain.Commands.User uses a module listed above it, which is the healthy direction.
27→17 Domain.Commands.User uses Domain.Commands.Common✕
- Connections
- 4 pairs of types, where a type in Domain.Commands.User uses a type in Domain.Commands.Common.
- The types involved
Pluto.Domain.Commands.User.ChangeUserPasswordCommand→Pluto.Domain.Commands.Common.CommandPluto.Domain.Commands.User.CreateUserCommand→Pluto.Domain.Commands.Common.CommandPluto.Domain.Commands.User.DeleteUserCommand→Pluto.Domain.Commands.Common.CommandPluto.Domain.Commands.User.UpdateUserCommand→Pluto.Domain.Commands.Common.Command
- Direction
- Domain.Commands.User uses Domain.Commands.Common, so a change to Domain.Commands.Common can break Domain.Commands.User, while a change to Domain.Commands.User can't break Domain.Commands.Common.
- Position
- Below the diagonal: Domain.Commands.User uses a module listed above it, which is the healthy direction.
28→6 Domain.Events.Order uses Domain.Events.Common✕
- Connections
- 6 pairs of types, where a type in Domain.Events.Order uses a type in Domain.Events.Common.
- The types involved
Pluto.Domain.Events.Order.AddProductEvent→Pluto.Domain.Events.Common.EventPluto.Domain.Events.Order.ApproveOrderEvent→Pluto.Domain.Events.Common.EventPluto.Domain.Events.Order.CancelOrderEvent→Pluto.Domain.Events.Common.EventPluto.Domain.Events.Order.CommitOrderEvent→Pluto.Domain.Events.Common.EventPluto.Domain.Events.Order.CreateOrderEvent→Pluto.Domain.Events.Common.EventPluto.Domain.Events.Order.RemoveProductEvent→Pluto.Domain.Events.Common.Event
- Direction
- Domain.Events.Order uses Domain.Events.Common, so a change to Domain.Events.Common can break Domain.Events.Order, while a change to Domain.Events.Order can't break Domain.Events.Common.
- Position
- Below the diagonal: Domain.Events.Order uses a module listed above it, which is the healthy direction.
28→21 Domain.Events.Order uses Domain.Models✕
- Connections
- 2 pairs of types, where a type in Domain.Events.Order uses a type in Domain.Models.
- The types involved
Pluto.Domain.Events.Order.AddProductEvent→Pluto.Domain.Models.OrderItemPluto.Domain.Events.Order.CreateOrderEvent→Pluto.Domain.Models.User
- Direction
- Domain.Events.Order uses Domain.Models, so a change to Domain.Models can break Domain.Events.Order, while a change to Domain.Events.Order can't break Domain.Models.
- Position
- Below the diagonal: Domain.Events.Order uses a module listed above it, which is the healthy direction.
29→20 Domain.Interfaces.Repositories uses Domain.Interfaces.Repositories.Common✕
- Connections
- 4 pairs of types, where a type in Domain.Interfaces.Repositories uses a type in Domain.Interfaces.Repositories.Common.
- The types involved
Pluto.Domain.Interfaces.Repositories.IOrderRepository→Pluto.Domain.Interfaces.Repositories.Common.ICrudRepositoryPluto.Domain.Interfaces.Repositories.IProductRepository→Pluto.Domain.Interfaces.Repositories.Common.ICrudRepositoryPluto.Domain.Interfaces.Repositories.IStoredEventRepository→Pluto.Domain.Interfaces.Repositories.Common.ICrudRepositoryPluto.Domain.Interfaces.Repositories.IUserRepository→Pluto.Domain.Interfaces.Repositories.Common.ICrudRepository
- Direction
- Domain.Interfaces.Repositories uses Domain.Interfaces.Repositories.Common, so a change to Domain.Interfaces.Repositories.Common can break Domain.Interfaces.Repositories, while a change to Domain.Interfaces.Repositories can't break Domain.Interfaces.Repositories.Common.
- Position
- Below the diagonal: Domain.Interfaces.Repositories uses a module listed above it, which is the healthy direction.
30→10 Repository.Mapping uses Repository.Config✕
- Connections
- 6 pairs of types, where a type in Repository.Mapping uses a type in Repository.Config.
- The types involved
Pluto.Repository.Mapping.OrderItemMap→Pluto.Repository.Config.DbEntityConfigurationPluto.Repository.Mapping.OrderMap→Pluto.Repository.Config.DbEntityConfigurationPluto.Repository.Mapping.PictureUrlMap→Pluto.Repository.Config.DbEntityConfigurationPluto.Repository.Mapping.ProductMap→Pluto.Repository.Config.DbEntityConfigurationPluto.Repository.Mapping.StoredEventMap→Pluto.Repository.Config.DbEntityConfigurationPluto.Repository.Mapping.UserMap→Pluto.Repository.Config.DbEntityConfiguration
- Direction
- Repository.Mapping uses Repository.Config, so a change to Repository.Config can break Repository.Mapping, while a change to Repository.Mapping can't break Repository.Config.
- Position
- Below the diagonal: Repository.Mapping uses a module listed above it, which is the healthy direction.
30→12 Repository.Mapping uses Repository.Mapping.Common✕
- Connections
- 6 pairs of types, where a type in Repository.Mapping uses a type in Repository.Mapping.Common.
- The types involved
Pluto.Repository.Mapping.OrderItemMap→Pluto.Repository.Mapping.Common.IEntityMapPluto.Repository.Mapping.OrderMap→Pluto.Repository.Mapping.Common.IEntityMapPluto.Repository.Mapping.PictureUrlMap→Pluto.Repository.Mapping.Common.IEntityMapPluto.Repository.Mapping.ProductMap→Pluto.Repository.Mapping.Common.IEntityMapPluto.Repository.Mapping.StoredEventMap→Pluto.Repository.Mapping.Common.IEventMapPluto.Repository.Mapping.UserMap→Pluto.Repository.Mapping.Common.IEntityMap
- Direction
- Repository.Mapping uses Repository.Mapping.Common, so a change to Repository.Mapping.Common can break Repository.Mapping, while a change to Repository.Mapping can't break Repository.Mapping.Common.
- Position
- Below the diagonal: Repository.Mapping uses a module listed above it, which is the healthy direction.
30→21 Repository.Mapping uses Domain.Models✕
- Connections
- 6 pairs of types, where a type in Repository.Mapping uses a type in Domain.Models.
- The types involved
Pluto.Repository.Mapping.OrderItemMap→Pluto.Domain.Models.OrderItemPluto.Repository.Mapping.OrderMap→Pluto.Domain.Models.OrderPluto.Repository.Mapping.PictureUrlMap→Pluto.Domain.Models.PictureUrlPluto.Repository.Mapping.ProductMap→Pluto.Domain.Models.ProductPluto.Repository.Mapping.StoredEventMap→Pluto.Domain.Models.StoredEventPluto.Repository.Mapping.UserMap→Pluto.Domain.Models.User
- Direction
- Repository.Mapping uses Domain.Models, so a change to Domain.Models can break Repository.Mapping, while a change to Repository.Mapping can't break Domain.Models.
- Position
- Below the diagonal: Repository.Mapping uses a module listed above it, which is the healthy direction.
31→9 Repository.Repositories.Common uses Domain.Models.Common✕
- Connections
- 1 pair of types, where a type in Repository.Repositories.Common uses a type in Domain.Models.Common.
- The types involved
Pluto.Repository.Repositories.Common.CrudRepository→Pluto.Domain.Models.Common.PagedResult
- Direction
- Repository.Repositories.Common uses Domain.Models.Common, so a change to Domain.Models.Common can break Repository.Repositories.Common, while a change to Repository.Repositories.Common can't break Domain.Models.Common.
- Position
- Below the diagonal: Repository.Repositories.Common uses a module listed above it, which is the healthy direction.
31→20 Repository.Repositories.Common uses Domain.Interfaces.Repositories.Common✕
- Connections
- 1 pair of types, where a type in Repository.Repositories.Common uses a type in Domain.Interfaces.Repositories.Common.
- The types involved
Pluto.Repository.Repositories.Common.CrudRepository→Pluto.Domain.Interfaces.Repositories.Common.ICrudRepository
- Direction
- Repository.Repositories.Common uses Domain.Interfaces.Repositories.Common, so a change to Domain.Interfaces.Repositories.Common can break Repository.Repositories.Common, while a change to Repository.Repositories.Common can't break Domain.Interfaces.Repositories.Common.
- Position
- Below the diagonal: Repository.Repositories.Common uses a module listed above it, which is the healthy direction.
32→11 Repository.UoW uses Repository.Contexts✕
- Connections
- 1 pair of types, where a type in Repository.UoW uses a type in Repository.Contexts.
- The types involved
Pluto.Repository.UoW.UnitOfWork→Pluto.Repository.Contexts.MainDbContext
- Direction
- Repository.UoW uses Repository.Contexts, so a change to Repository.Contexts can break Repository.UoW, while a change to Repository.UoW can't break Repository.Contexts.
- Position
- Below the diagonal: Repository.UoW uses a module listed above it, which is the healthy direction.
32→20 Repository.UoW uses Domain.Interfaces.Repositories.Common✕
- Connections
- 1 pair of types, where a type in Repository.UoW uses a type in Domain.Interfaces.Repositories.Common.
- The types involved
Pluto.Repository.UoW.UnitOfWork→Pluto.Domain.Interfaces.Repositories.Common.IUnitOfWork
- Direction
- Repository.UoW uses Domain.Interfaces.Repositories.Common, so a change to Domain.Interfaces.Repositories.Common can break Repository.UoW, while a change to Repository.UoW can't break Domain.Interfaces.Repositories.Common.
- Position
- Below the diagonal: Repository.UoW uses a module listed above it, which is the healthy direction.
33→22 API.Controllers.Common uses Domain.Notifications✕
- Connections
- 3 pairs of types, where a type in API.Controllers.Common uses a type in Domain.Notifications.
- The types involved
Pluto.API.Controllers.Common.AuthenticatedController→Pluto.Domain.Notifications.DomainNotificationPluto.API.Controllers.Common.BaseController→Pluto.Domain.Notifications.DomainNotificationPluto.API.Controllers.Common.BaseController→Pluto.Domain.Notifications.DomainNotificationHandler
- Direction
- API.Controllers.Common uses Domain.Notifications, so a change to Domain.Notifications can break API.Controllers.Common, while a change to API.Controllers.Common can't break Domain.Notifications.
- Position
- Below the diagonal: API.Controllers.Common uses a module listed above it, which is the healthy direction.
33→24 API.Controllers.Common uses Domain.Bus✕
- Connections
- 2 pairs of types, where a type in API.Controllers.Common uses a type in Domain.Bus.
- The types involved
Pluto.API.Controllers.Common.AuthenticatedController→Pluto.Domain.Bus.IMediatorHandlerPluto.API.Controllers.Common.BaseController→Pluto.Domain.Bus.IMediatorHandler
- Direction
- API.Controllers.Common uses Domain.Bus, so a change to Domain.Bus can break API.Controllers.Common, while a change to API.Controllers.Common can't break Domain.Bus.
- Position
- Below the diagonal: API.Controllers.Common uses a module listed above it, which is the healthy direction.
34→17 Bus uses Domain.Commands.Common✕
- Connections
- 1 pair of types, where a type in Bus uses a type in Domain.Commands.Common.
- The types involved
Pluto.Bus.InMemoryBus→Pluto.Domain.Commands.Common.RequestCommand
- Direction
- Bus uses Domain.Commands.Common, so a change to Domain.Commands.Common can break Bus, while a change to Bus can't break Domain.Commands.Common.
- Position
- Below the diagonal: Bus uses a module listed above it, which is the healthy direction.
34→24 Bus uses Domain.Bus✕
- Connections
- 1 pair of types, where a type in Bus uses a type in Domain.Bus.
- The types involved
Pluto.Bus.InMemoryBus→Pluto.Domain.Bus.IMediatorHandler
- Direction
- Bus uses Domain.Bus, so a change to Domain.Bus can break Bus, while a change to Bus can't break Domain.Bus.
- Position
- Below the diagonal: Bus uses a module listed above it, which is the healthy direction.
34→29 Bus uses Domain.Interfaces.Repositories✕
- Connections
- 1 pair of types, where a type in Bus uses a type in Domain.Interfaces.Repositories.
- The types involved
Pluto.Bus.InMemoryBus→Pluto.Domain.Interfaces.Repositories.IStoredEventRepository
- Direction
- Bus uses Domain.Interfaces.Repositories, so a change to Domain.Interfaces.Repositories can break Bus, while a change to Bus can't break Domain.Interfaces.Repositories.
- Position
- Below the diagonal: Bus uses a module listed above it, which is the healthy direction.
35→20 Domain.Handlers.Common uses Domain.Interfaces.Repositories.Common✕
- Connections
- 1 pair of types, where a type in Domain.Handlers.Common uses a type in Domain.Interfaces.Repositories.Common.
- The types involved
Pluto.Domain.Handlers.Common.CommandHandler→Pluto.Domain.Interfaces.Repositories.Common.IUnitOfWork
- Direction
- Domain.Handlers.Common uses Domain.Interfaces.Repositories.Common, so a change to Domain.Interfaces.Repositories.Common can break Domain.Handlers.Common, while a change to Domain.Handlers.Common can't break Domain.Interfaces.Repositories.Common.
- Position
- Below the diagonal: Domain.Handlers.Common uses a module listed above it, which is the healthy direction.
35→22 Domain.Handlers.Common uses Domain.Notifications✕
- Connections
- 2 pairs of types, where a type in Domain.Handlers.Common uses a type in Domain.Notifications.
- The types involved
Pluto.Domain.Handlers.Common.CommandHandler→Pluto.Domain.Notifications.DomainNotificationPluto.Domain.Handlers.Common.CommandHandler→Pluto.Domain.Notifications.DomainNotificationHandler
- Direction
- Domain.Handlers.Common uses Domain.Notifications, so a change to Domain.Notifications can break Domain.Handlers.Common, while a change to Domain.Handlers.Common can't break Domain.Notifications.
- Position
- Below the diagonal: Domain.Handlers.Common uses a module listed above it, which is the healthy direction.
35→24 Domain.Handlers.Common uses Domain.Bus✕
- Connections
- 1 pair of types, where a type in Domain.Handlers.Common uses a type in Domain.Bus.
- The types involved
Pluto.Domain.Handlers.Common.CommandHandler→Pluto.Domain.Bus.IMediatorHandler
- Direction
- Domain.Handlers.Common uses Domain.Bus, so a change to Domain.Bus can break Domain.Handlers.Common, while a change to Domain.Handlers.Common can't break Domain.Bus.
- Position
- Below the diagonal: Domain.Handlers.Common uses a module listed above it, which is the healthy direction.
36→18 Domain.Handlers.Events uses Domain.Events.Product✕
- Connections
- 3 pairs of types, where a type in Domain.Handlers.Events uses a type in Domain.Events.Product.
- The types involved
Pluto.Domain.Handlers.Events.ProductEventHandler→Pluto.Domain.Events.Product.CreateProductEventPluto.Domain.Handlers.Events.ProductEventHandler→Pluto.Domain.Events.Product.DeleteProductEventPluto.Domain.Handlers.Events.ProductEventHandler→Pluto.Domain.Events.Product.UpdateProductEvent
- Direction
- Domain.Handlers.Events uses Domain.Events.Product, so a change to Domain.Events.Product can break Domain.Handlers.Events, while a change to Domain.Handlers.Events can't break Domain.Events.Product.
- Position
- Below the diagonal: Domain.Handlers.Events uses a module listed above it, which is the healthy direction.
36→19 Domain.Handlers.Events uses Domain.Events.User✕
- Connections
- 4 pairs of types, where a type in Domain.Handlers.Events uses a type in Domain.Events.User.
- The types involved
Pluto.Domain.Handlers.Events.UserEventHandler→Pluto.Domain.Events.User.ChangeUserPasswordEventPluto.Domain.Handlers.Events.UserEventHandler→Pluto.Domain.Events.User.CreateUserEventPluto.Domain.Handlers.Events.UserEventHandler→Pluto.Domain.Events.User.DeleteUserEventPluto.Domain.Handlers.Events.UserEventHandler→Pluto.Domain.Events.User.UpdateUserEvent
- Direction
- Domain.Handlers.Events uses Domain.Events.User, so a change to Domain.Events.User can break Domain.Handlers.Events, while a change to Domain.Handlers.Events can't break Domain.Events.User.
- Position
- Below the diagonal: Domain.Handlers.Events uses a module listed above it, which is the healthy direction.
36→28 Domain.Handlers.Events uses Domain.Events.Order✕
- Connections
- 6 pairs of types, where a type in Domain.Handlers.Events uses a type in Domain.Events.Order.
- The types involved
Pluto.Domain.Handlers.Events.OrderEventHandler→Pluto.Domain.Events.Order.AddProductEventPluto.Domain.Handlers.Events.OrderEventHandler→Pluto.Domain.Events.Order.ApproveOrderEventPluto.Domain.Handlers.Events.OrderEventHandler→Pluto.Domain.Events.Order.CancelOrderEventPluto.Domain.Handlers.Events.OrderEventHandler→Pluto.Domain.Events.Order.CommitOrderEventPluto.Domain.Handlers.Events.OrderEventHandler→Pluto.Domain.Events.Order.CreateOrderEventPluto.Domain.Handlers.Events.OrderEventHandler→Pluto.Domain.Events.Order.RemoveProductEvent
- Direction
- Domain.Handlers.Events uses Domain.Events.Order, so a change to Domain.Events.Order can break Domain.Handlers.Events, while a change to Domain.Handlers.Events can't break Domain.Events.Order.
- Position
- Below the diagonal: Domain.Handlers.Events uses a module listed above it, which is the healthy direction.
37→8 Repository.Repositories uses Domain.Interfaces.Identity✕
- Connections
- 1 pair of types, where a type in Repository.Repositories uses a type in Domain.Interfaces.Identity.
- The types involved
Pluto.Repository.Repositories.StoredEventRepository→Pluto.Domain.Interfaces.Identity.IUser
- Direction
- Repository.Repositories uses Domain.Interfaces.Identity, so a change to Domain.Interfaces.Identity can break Repository.Repositories, while a change to Repository.Repositories can't break Domain.Interfaces.Identity.
- Position
- Below the diagonal: Repository.Repositories uses a module listed above it, which is the healthy direction.
37→11 Repository.Repositories uses Repository.Contexts✕
- Connections
- 4 pairs of types, where a type in Repository.Repositories uses a type in Repository.Contexts.
- The types involved
Pluto.Repository.Repositories.OrderRepository→Pluto.Repository.Contexts.MainDbContextPluto.Repository.Repositories.ProductRepository→Pluto.Repository.Contexts.MainDbContextPluto.Repository.Repositories.StoredEventRepository→Pluto.Repository.Contexts.EventStoreSQLContextPluto.Repository.Repositories.UserRepository→Pluto.Repository.Contexts.MainDbContext
- Direction
- Repository.Repositories uses Repository.Contexts, so a change to Repository.Contexts can break Repository.Repositories, while a change to Repository.Repositories can't break Repository.Contexts.
- Position
- Below the diagonal: Repository.Repositories uses a module listed above it, which is the healthy direction.
37→29 Repository.Repositories uses Domain.Interfaces.Repositories✕
- Connections
- 4 pairs of types, where a type in Repository.Repositories uses a type in Domain.Interfaces.Repositories.
- The types involved
Pluto.Repository.Repositories.OrderRepository→Pluto.Domain.Interfaces.Repositories.IOrderRepositoryPluto.Repository.Repositories.ProductRepository→Pluto.Domain.Interfaces.Repositories.IProductRepositoryPluto.Repository.Repositories.StoredEventRepository→Pluto.Domain.Interfaces.Repositories.IStoredEventRepositoryPluto.Repository.Repositories.UserRepository→Pluto.Domain.Interfaces.Repositories.IUserRepository
- Direction
- Repository.Repositories uses Domain.Interfaces.Repositories, so a change to Domain.Interfaces.Repositories can break Repository.Repositories, while a change to Repository.Repositories can't break Domain.Interfaces.Repositories.
- Position
- Below the diagonal: Repository.Repositories uses a module listed above it, which is the healthy direction.
37→31 Repository.Repositories uses Repository.Repositories.Common✕
- Connections
- 4 pairs of types, where a type in Repository.Repositories uses a type in Repository.Repositories.Common.
- The types involved
Pluto.Repository.Repositories.OrderRepository→Pluto.Repository.Repositories.Common.CrudRepositoryPluto.Repository.Repositories.ProductRepository→Pluto.Repository.Repositories.Common.CrudRepositoryPluto.Repository.Repositories.StoredEventRepository→Pluto.Repository.Repositories.Common.CrudRepositoryPluto.Repository.Repositories.UserRepository→Pluto.Repository.Repositories.Common.CrudRepository
- Direction
- Repository.Repositories uses Repository.Repositories.Common, so a change to Repository.Repositories.Common can break Repository.Repositories, while a change to Repository.Repositories can't break Repository.Repositories.Common.
- Position
- Below the diagonal: Repository.Repositories uses a module listed above it, which is the healthy direction.
38→2 API.Controllers uses API.Settings✕
- Connections
- 1 pair of types, where a type in API.Controllers uses a type in API.Settings.
- The types involved
Pluto.API.Controllers.AuthController→Pluto.API.Settings.AppSettings
- Direction
- API.Controllers uses API.Settings, so a change to API.Settings can break API.Controllers, while a change to API.Controllers can't break API.Settings.
- Position
- Below the diagonal: API.Controllers uses a module listed above it, which is the healthy direction.
38→21 API.Controllers uses Domain.Models✕
- Connections
- 1 pair of types, where a type in API.Controllers uses a type in Domain.Models.
- The types involved
Pluto.API.Controllers.AuthController→Pluto.Domain.Models.User
- Direction
- API.Controllers uses Domain.Models, so a change to Domain.Models can break API.Controllers, while a change to API.Controllers can't break Domain.Models.
- Position
- Below the diagonal: API.Controllers uses a module listed above it, which is the healthy direction.
38→22 API.Controllers uses Domain.Notifications✕
- Connections
- 4 pairs of types, where a type in API.Controllers uses a type in Domain.Notifications.
- The types involved
Pluto.API.Controllers.AuthController→Pluto.Domain.Notifications.DomainNotificationPluto.API.Controllers.OrderController→Pluto.Domain.Notifications.DomainNotificationPluto.API.Controllers.ProductController→Pluto.Domain.Notifications.DomainNotificationPluto.API.Controllers.UserController→Pluto.Domain.Notifications.DomainNotification
- Direction
- API.Controllers uses Domain.Notifications, so a change to Domain.Notifications can break API.Controllers, while a change to API.Controllers can't break Domain.Notifications.
- Position
- Below the diagonal: API.Controllers uses a module listed above it, which is the healthy direction.
38→23 API.Controllers uses API.Auth✕
- Connections
- 2 pairs of types, where a type in API.Controllers uses a type in API.Auth.
- The types involved
Pluto.API.Controllers.AuthController→Pluto.API.Auth.AuthRequestDtoPluto.API.Controllers.AuthController→Pluto.API.Auth.SigningConfigurations
- Direction
- API.Controllers uses API.Auth, so a change to API.Auth can break API.Controllers, while a change to API.Controllers can't break API.Auth.
- Position
- Below the diagonal: API.Controllers uses a module listed above it, which is the healthy direction.
38→24 API.Controllers uses Domain.Bus✕
- Connections
- 4 pairs of types, where a type in API.Controllers uses a type in Domain.Bus.
- The types involved
Pluto.API.Controllers.AuthController→Pluto.Domain.Bus.IMediatorHandlerPluto.API.Controllers.OrderController→Pluto.Domain.Bus.IMediatorHandlerPluto.API.Controllers.ProductController→Pluto.Domain.Bus.IMediatorHandlerPluto.API.Controllers.UserController→Pluto.Domain.Bus.IMediatorHandler
- Direction
- API.Controllers uses Domain.Bus, so a change to Domain.Bus can break API.Controllers, while a change to API.Controllers can't break Domain.Bus.
- Position
- Below the diagonal: API.Controllers uses a module listed above it, which is the healthy direction.
38→25 API.Controllers uses Domain.Commands.Order✕
- Connections
- 2 pairs of types, where a type in API.Controllers uses a type in Domain.Commands.Order.
- The types involved
Pluto.API.Controllers.OrderController→Pluto.Domain.Commands.Order.AddProductCommandPluto.API.Controllers.OrderController→Pluto.Domain.Commands.Order.RemoveProductCommand
- Direction
- API.Controllers uses Domain.Commands.Order, so a change to Domain.Commands.Order can break API.Controllers, while a change to API.Controllers can't break Domain.Commands.Order.
- Position
- Below the diagonal: API.Controllers uses a module listed above it, which is the healthy direction.
38→26 API.Controllers uses Domain.Commands.Product✕
- Connections
- 2 pairs of types, where a type in API.Controllers uses a type in Domain.Commands.Product.
- The types involved
Pluto.API.Controllers.ProductController→Pluto.Domain.Commands.Product.CreateProductCommandPluto.API.Controllers.ProductController→Pluto.Domain.Commands.Product.UpdateProductCommand
- Direction
- API.Controllers uses Domain.Commands.Product, so a change to Domain.Commands.Product can break API.Controllers, while a change to API.Controllers can't break Domain.Commands.Product.
- Position
- Below the diagonal: API.Controllers uses a module listed above it, which is the healthy direction.
38→27 API.Controllers uses Domain.Commands.User✕
- Connections
- 3 pairs of types, where a type in API.Controllers uses a type in Domain.Commands.User.
- The types involved
Pluto.API.Controllers.UserController→Pluto.Domain.Commands.User.ChangeUserPasswordCommandPluto.API.Controllers.UserController→Pluto.Domain.Commands.User.CreateUserCommandPluto.API.Controllers.UserController→Pluto.Domain.Commands.User.UpdateUserCommand
- Direction
- API.Controllers uses Domain.Commands.User, so a change to Domain.Commands.User can break API.Controllers, while a change to API.Controllers can't break Domain.Commands.User.
- Position
- Below the diagonal: API.Controllers uses a module listed above it, which is the healthy direction.
38→29 API.Controllers uses Domain.Interfaces.Repositories✕
- Connections
- 5 pairs of types, where a type in API.Controllers uses a type in Domain.Interfaces.Repositories.
- The types involved
Pluto.API.Controllers.AuthController→Pluto.Domain.Interfaces.Repositories.IUserRepositoryPluto.API.Controllers.OrderController→Pluto.Domain.Interfaces.Repositories.IOrderRepositoryPluto.API.Controllers.OrderController→Pluto.Domain.Interfaces.Repositories.IUserRepositoryPluto.API.Controllers.ProductController→Pluto.Domain.Interfaces.Repositories.IProductRepositoryPluto.API.Controllers.UserController→Pluto.Domain.Interfaces.Repositories.IUserRepository
- Direction
- API.Controllers uses Domain.Interfaces.Repositories, so a change to Domain.Interfaces.Repositories can break API.Controllers, while a change to API.Controllers can't break Domain.Interfaces.Repositories.
- Position
- Below the diagonal: API.Controllers uses a module listed above it, which is the healthy direction.
38→33 API.Controllers uses API.Controllers.Common✕
- Connections
- 4 pairs of types, where a type in API.Controllers uses a type in API.Controllers.Common.
- The types involved
Pluto.API.Controllers.AuthController→Pluto.API.Controllers.Common.BaseControllerPluto.API.Controllers.OrderController→Pluto.API.Controllers.Common.AuthenticatedControllerPluto.API.Controllers.ProductController→Pluto.API.Controllers.Common.BaseControllerPluto.API.Controllers.UserController→Pluto.API.Controllers.Common.BaseController
- Direction
- API.Controllers uses API.Controllers.Common, so a change to API.Controllers.Common can break API.Controllers, while a change to API.Controllers can't break API.Controllers.Common.
- Position
- Below the diagonal: API.Controllers uses a module listed above it, which is the healthy direction.
39→20 Domain.Handlers.Commands uses Domain.Interfaces.Repositories.Common✕
- Connections
- 3 pairs of types, where a type in Domain.Handlers.Commands uses a type in Domain.Interfaces.Repositories.Common.
- The types involved
Pluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Interfaces.Repositories.Common.IUnitOfWorkPluto.Domain.Handlers.Commands.ProductCommandHandler→Pluto.Domain.Interfaces.Repositories.Common.IUnitOfWorkPluto.Domain.Handlers.Commands.UserCommandHandler→Pluto.Domain.Interfaces.Repositories.Common.IUnitOfWork
- Direction
- Domain.Handlers.Commands uses Domain.Interfaces.Repositories.Common, so a change to Domain.Interfaces.Repositories.Common can break Domain.Handlers.Commands, while a change to Domain.Handlers.Commands can't break Domain.Interfaces.Repositories.Common.
- Position
- Below the diagonal: Domain.Handlers.Commands uses a module listed above it, which is the healthy direction.
39→21 Domain.Handlers.Commands uses Domain.Models✕
- Connections
- 2 pairs of types, where a type in Domain.Handlers.Commands uses a type in Domain.Models.
- The types involved
Pluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Models.OrderPluto.Domain.Handlers.Commands.ProductCommandHandler→Pluto.Domain.Models.Product
- Direction
- Domain.Handlers.Commands uses Domain.Models, so a change to Domain.Models can break Domain.Handlers.Commands, while a change to Domain.Handlers.Commands can't break Domain.Models.
- Position
- Below the diagonal: Domain.Handlers.Commands uses a module listed above it, which is the healthy direction.
39→22 Domain.Handlers.Commands uses Domain.Notifications✕
- Connections
- 3 pairs of types, where a type in Domain.Handlers.Commands uses a type in Domain.Notifications.
- The types involved
Pluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Notifications.DomainNotificationPluto.Domain.Handlers.Commands.ProductCommandHandler→Pluto.Domain.Notifications.DomainNotificationPluto.Domain.Handlers.Commands.UserCommandHandler→Pluto.Domain.Notifications.DomainNotification
- Direction
- Domain.Handlers.Commands uses Domain.Notifications, so a change to Domain.Notifications can break Domain.Handlers.Commands, while a change to Domain.Handlers.Commands can't break Domain.Notifications.
- Position
- Below the diagonal: Domain.Handlers.Commands uses a module listed above it, which is the healthy direction.
39→24 Domain.Handlers.Commands uses Domain.Bus✕
- Connections
- 3 pairs of types, where a type in Domain.Handlers.Commands uses a type in Domain.Bus.
- The types involved
Pluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Bus.IMediatorHandlerPluto.Domain.Handlers.Commands.ProductCommandHandler→Pluto.Domain.Bus.IMediatorHandlerPluto.Domain.Handlers.Commands.UserCommandHandler→Pluto.Domain.Bus.IMediatorHandler
- Direction
- Domain.Handlers.Commands uses Domain.Bus, so a change to Domain.Bus can break Domain.Handlers.Commands, while a change to Domain.Handlers.Commands can't break Domain.Bus.
- Position
- Below the diagonal: Domain.Handlers.Commands uses a module listed above it, which is the healthy direction.
39→25 Domain.Handlers.Commands uses Domain.Commands.Order✕
- Connections
- 6 pairs of types, where a type in Domain.Handlers.Commands uses a type in Domain.Commands.Order.
- The types involved
Pluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Commands.Order.AddProductCommandPluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Commands.Order.ApproveOrderCommandPluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Commands.Order.CancelOrderCommandPluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Commands.Order.CommitOrderCommandPluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Commands.Order.CreateOrderCommandPluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Commands.Order.RemoveProductCommand
- Direction
- Domain.Handlers.Commands uses Domain.Commands.Order, so a change to Domain.Commands.Order can break Domain.Handlers.Commands, while a change to Domain.Handlers.Commands can't break Domain.Commands.Order.
- Position
- Below the diagonal: Domain.Handlers.Commands uses a module listed above it, which is the healthy direction.
39→26 Domain.Handlers.Commands uses Domain.Commands.Product✕
- Connections
- 3 pairs of types, where a type in Domain.Handlers.Commands uses a type in Domain.Commands.Product.
- The types involved
Pluto.Domain.Handlers.Commands.ProductCommandHandler→Pluto.Domain.Commands.Product.CreateProductCommandPluto.Domain.Handlers.Commands.ProductCommandHandler→Pluto.Domain.Commands.Product.DeleteProductCommandPluto.Domain.Handlers.Commands.ProductCommandHandler→Pluto.Domain.Commands.Product.UpdateProductCommand
- Direction
- Domain.Handlers.Commands uses Domain.Commands.Product, so a change to Domain.Commands.Product can break Domain.Handlers.Commands, while a change to Domain.Handlers.Commands can't break Domain.Commands.Product.
- Position
- Below the diagonal: Domain.Handlers.Commands uses a module listed above it, which is the healthy direction.
39→27 Domain.Handlers.Commands uses Domain.Commands.User✕
- Connections
- 4 pairs of types, where a type in Domain.Handlers.Commands uses a type in Domain.Commands.User.
- The types involved
Pluto.Domain.Handlers.Commands.UserCommandHandler→Pluto.Domain.Commands.User.ChangeUserPasswordCommandPluto.Domain.Handlers.Commands.UserCommandHandler→Pluto.Domain.Commands.User.CreateUserCommandPluto.Domain.Handlers.Commands.UserCommandHandler→Pluto.Domain.Commands.User.DeleteUserCommandPluto.Domain.Handlers.Commands.UserCommandHandler→Pluto.Domain.Commands.User.UpdateUserCommand
- Direction
- Domain.Handlers.Commands uses Domain.Commands.User, so a change to Domain.Commands.User can break Domain.Handlers.Commands, while a change to Domain.Handlers.Commands can't break Domain.Commands.User.
- Position
- Below the diagonal: Domain.Handlers.Commands uses a module listed above it, which is the healthy direction.
39→29 Domain.Handlers.Commands uses Domain.Interfaces.Repositories✕
- Connections
- 5 pairs of types, where a type in Domain.Handlers.Commands uses a type in Domain.Interfaces.Repositories.
- The types involved
Pluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Interfaces.Repositories.IOrderRepositoryPluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Interfaces.Repositories.IProductRepositoryPluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Interfaces.Repositories.IUserRepositoryPluto.Domain.Handlers.Commands.ProductCommandHandler→Pluto.Domain.Interfaces.Repositories.IProductRepositoryPluto.Domain.Handlers.Commands.UserCommandHandler→Pluto.Domain.Interfaces.Repositories.IUserRepository
- Direction
- Domain.Handlers.Commands uses Domain.Interfaces.Repositories, so a change to Domain.Interfaces.Repositories can break Domain.Handlers.Commands, while a change to Domain.Handlers.Commands can't break Domain.Interfaces.Repositories.
- Position
- Below the diagonal: Domain.Handlers.Commands uses a module listed above it, which is the healthy direction.
39→35 Domain.Handlers.Commands uses Domain.Handlers.Common✕
- Connections
- 3 pairs of types, where a type in Domain.Handlers.Commands uses a type in Domain.Handlers.Common.
- The types involved
Pluto.Domain.Handlers.Commands.OrderCommandHandler→Pluto.Domain.Handlers.Common.CommandHandlerPluto.Domain.Handlers.Commands.ProductCommandHandler→Pluto.Domain.Handlers.Common.CommandHandlerPluto.Domain.Handlers.Commands.UserCommandHandler→Pluto.Domain.Handlers.Common.CommandHandler
- Direction
- Domain.Handlers.Commands uses Domain.Handlers.Common, so a change to Domain.Handlers.Common can break Domain.Handlers.Commands, while a change to Domain.Handlers.Commands can't break Domain.Handlers.Common.
- Position
- Below the diagonal: Domain.Handlers.Commands 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 | 18 | High / Critical |
| A05:2025 — Injection | 11 | Medium |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No tests found finding(s) in Test Distribution; Resolve the 8 Outdated finding(s) in Dependency Hygiene — start with REDACTED (4), REDACTED (3), Pluto.Domain.csproj.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +16.5 pts | Low | Test Distribution |
| Resolve the 8 Outdated finding(s) in Dependency Hygiene — start with REDACTED (4), REDACTED (3), Pluto.Domain.csproj. | +8.0 pts | Low | Dependency Hygiene |
| Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4), REDACTED (2). | +7.0 pts | Low | Dependency Hygiene |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +16.5 pts | High | Code Coverage |
| Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). | +3.4 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.4 pts | Low | ADR Quality |
| Resolve the 1 `GetOpenenedOrderFromUser` returns an awaitable but lacks the `Async`… finding(s) in Naming Consistency — start with OrderCommandHandler.cs. | +3.0 pts | Low | Naming Consistency |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +5.1 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.5 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| Pluto.API/Controllers/OrderController.cs | 5.8 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| Pluto.Domain/Events/Interfaces/IHandler.cs | 8.2 | Near-clean | Explicit Debt: Dead code: IHandler |
| Pluto.Utils/Cryptography/Cryptography.cs | 8.2 | Near-clean | Explicit Debt: Dead code: Decrypt |
| Pluto.Utils/Validations/Validation.cs | 8.2 | Near-clean | Explicit Debt: Dead code: WriteToConsole |
| README.md | 9.3 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
| Pluto.Domain/Pluto.Domain.csproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: MediatR |
| Pluto.Domain/Handlers/Commands/OrderCommandHandler.cs | 9.5 | Near-clean | Naming Consistency: `GetOpenenedOrderFromUser` returns an awaitable but lacks the `Async` suffix its 13 peers carry |
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 84 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 — 84 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, 138 of 154 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
- 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 16 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 (16 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 — 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. 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.
- 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 (16 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 16 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 (Pluto.API). 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.
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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D5 · Coupling
5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 11 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate Code Coverage 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.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D12 · Dependency Hygiene
11 outdated, 3 vulnerable, 7 deprecated packages.
What to do
- Resolve the 8 Outdated finding(s) in Dependency Hygiene — start with REDACTED (4), REDACTED (3), Pluto.Domain.csproj. — One of this dimension's main actionable groups (8 recommendation-level).
- Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (7 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
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 175 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 12 direct `PackageReference`(s), and 164 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
2 deducted debt markers + 3 dead symbols across 2385 LoC in the .NET projects (0.4/KLoC) → score 9.2.
What to do
- Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with OrderController.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Dead code finding(s) in Explicit Debt — start with IHandler.cs, Cryptography.cs, Validation.cs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with OrderController.cs. — One of this dimension's main actionable groups (1 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
5 projects, 104 source files, 2385 hand-written lines of code (2385 production / 0 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 822 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 6 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 6 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).
D21 · Naming Consistency
1 naming inconsistencies among 14 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `GetOpenenedOrderFromUser` returns an awaitable but lacks the `Async`… finding(s) in Naming Consistency — start with OrderCommandHandler.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 5 projects flagged as possibly oversized/incoherent.
D27 · Navigability
96 % of calls cross a namespace and 12 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 0 high, 11 medium, 0 low.
What to do
- Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (5). — One of this dimension's main actionable groups (11 warning-level).
D30 · Dependency Vulnerabilities
18 finding(s): 2 critical, 9 high, 7 medium, 0 low.
What to do
- Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 7 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — 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
0 of 231 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 5 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 1 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls
DM1 · Aggregate boundaries
- `Order` references the aggregate root `User` directly (via `Customer`) — hold its `UserId` instead. — Pluto.Domain/Models/Order.cs:32
- `Order` references the aggregate root `User` directly (via `Editor`) — hold its `UserId` instead. — Pluto.Domain/Models/Order.cs:33
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `OrderItem`'s public constructor takes `quantity` 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 `OrderItem` 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. — Pluto.Domain/Models/OrderItem.cs:13
- `PictureUrl`'s public constructor takes `url` 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 `PictureUrl` 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. — Pluto.Domain/Models/PictureUrl.cs:13
- `Product`'s public constructor takes `name`, `description`, `price` 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 `Product` 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. — Pluto.Domain/Models/Product.cs:16
- `StoredEvent`'s public constructor takes `data`, `user` 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 `StoredEvent` 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. — Pluto.Domain/Models/StoredEvent.cs:15
- `User`'s public constructor takes `name`, `email`, `password` 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. — Pluto.Domain/Models/User.cs:15
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
- `Order` reads `DateTime.UtcNow` inside `Commit`. 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`. — Pluto.Domain/Models/Order.cs:66
- `Order` reads `DateTime.UtcNow` inside `Approve`. 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`. — Pluto.Domain/Models/Order.cs:76
- `Order` reads `DateTime.UtcNow` inside `Cancel`. 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`. — Pluto.Domain/Models/Order.cs:86
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
- `ApproveOrderEvent.OrderId` 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. — Pluto.Domain/Events/Order/ApproveOrderEvent.cs:16
- `ApproveOrderEvent.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. — Pluto.Domain/Events/Order/ApproveOrderEvent.cs:17
- `CancelOrderEvent.OrderId` 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. — Pluto.Domain/Events/Order/CancelOrderEvent.cs:16
- `CancelOrderEvent.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. — Pluto.Domain/Events/Order/CancelOrderEvent.cs:17
- `CommitOrderEvent.OrderId` 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. — Pluto.Domain/Events/Order/CommitOrderEvent.cs:16
- `CommitOrderEvent.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. — Pluto.Domain/Events/Order/CommitOrderEvent.cs:17
- `RemoveProductEvent.OrderId` 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. — Pluto.Domain/Events/Order/RemoveProductEvent.cs:16
- `RemoveProductEvent.ProductId` 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. — Pluto.Domain/Events/Order/RemoveProductEvent.cs:17
- `StoredEvent.AggregateId` 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. — Pluto.Domain/Models/StoredEvent.cs:24
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
- `OrderItem` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Pluto.Domain/Models/OrderItem.cs:5
- `PictureUrl` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Pluto.Domain/Models/PictureUrl.cs:5
- `StoredEvent` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Pluto.Domain/Models/StoredEvent.cs:7
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
- `Order` exposes its own state through a mutable collection (Items) — a caller can add to or remove from it directly, without passing through the methods that enforce the invariants. — Pluto.Domain/Models/Order.cs:9
- `Product` exposes its own state through a mutable collection (Pictures) — a caller can add to or remove from it directly, without passing through the methods that enforce the invariants. — Pluto.Domain/Models/Product.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
- `IStoredEventRepository` is a repository over `StoredEvent`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `StoredEvent` through its owning aggregate instead. — Pluto.Domain/Interfaces/Repositories/IStoredEventRepository.cs:8
- `ICrudRepository` returns `IQueryable` from `Query`, `Query`. 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. — Pluto.Domain/Interfaces/Repositories/Common/ICrudRepository.cs:10
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
- `AddProductEvent` 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. — Pluto.Domain/Events/Order/AddProductEvent.cs:5
- `ApproveOrderEvent` 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. — Pluto.Domain/Events/Order/ApproveOrderEvent.cs:6
- `CancelOrderEvent` 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. — Pluto.Domain/Events/Order/CancelOrderEvent.cs:6
- `CommitOrderEvent` 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. — Pluto.Domain/Events/Order/CommitOrderEvent.cs:6
- `CreateOrderEvent` 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. — Pluto.Domain/Events/Order/CreateOrderEvent.cs:6
- `RemoveProductEvent` 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. — Pluto.Domain/Events/Order/RemoveProductEvent.cs:6
- `CreateProductEvent` 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. — Pluto.Domain/Events/Product/CreateProductEvent.cs:6
- `DeleteProductEvent` 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. — Pluto.Domain/Events/Product/DeleteProductEvent.cs:6
- `UpdateProductEvent` 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. — Pluto.Domain/Events/Product/UpdateProductEvent.cs:6
- `ChangeUserPasswordEvent` 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. — Pluto.Domain/Events/User/ChangeUserPasswordEvent.cs:6
- `DeleteUserEvent` 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. — Pluto.Domain/Events/User/DeleteUserEvent.cs:6
- `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. — Pluto.Domain/Notifications/DomainNotification.cs:5
What to do
- Name events in the past tense — they record facts that already happened.
ED4 · Outbox / dual-write
ED5 · Idempotency
- `Commands.ProductCommandHandler.Handle` mutates persistent state (a repository write) and inserts a new `Product` with no identity assigned (the store or its constructor generates a new one) (line 42), so a re-run inserts another one. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Pluto.Domain/Handlers/Commands/ProductCommandHandler.cs:30
What to do
- Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `Handle` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — Pluto.Domain/Handlers/Events/UserEventHandler.cs:10, Pluto.Domain/Notifications/DomainNotificationHandler.cs:13
- `UpdateAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Pluto.Repository/Repositories/Common/CrudRepository.cs:55
What to do
- Remove the dead code that still moves this score: delete dead if(false) / #if false branches and either do the real async work or drop the async keyword from fake-async methods.
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 5 of 5 project(s) that lack one — worth up to 2 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
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
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
- No logging call was found in the 125 `.cs` file(s) this check read. Each was searched for the framework names `ILogger`, `Serilog`, `NLog` and `log4net`; for a call on a receiver whose name ends in `Logger`; for a `System.Diagnostics` write; for a level-gated log facade; and for the builder spellings that CONFIGURE logging for everyone else (`AddLogging(`, `ConfigureLogging(`, `UseSerilog(`, `UseNLog(`, `.Logging.Add…(`); and for emission through an `EventSource`, `ActivitySource` or `DiagnosticSource` (`WriteEvent(`, `StartActivity(`, `.Write("event", …)`). That walk sees only `.cs` documents from projects the workspace loaded, so it cannot see logging in source that did not load, in another language, or through a repo-local wrapper whose name does not end in `Logger` — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt ILogger (or Serilog) and log at meaningful points across the projects.
- 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:12
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
- MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — Pluto.Utils/Cryptography/Cryptography.cs:40
- DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes. — Pluto.Utils/Cryptography/Cryptography.cs:48
- 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. — Pluto.API/Program.cs:14
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
- Replace DES/3DES (and bare RijndaelManaged) with AES-GCM via `Aes.Create()`.
- 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
- Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×2) — Pluto.Domain/Handlers/Commands/UserCommandHandler.cs:42, Pluto.Domain/Handlers/Commands/UserCommandHandler.cs:66
What to do
- Sync-over-async (deadlock risk) through `.Result`
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
- `productRepository` is never created by `ProductCommandHandler` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 84). Its declared type `IProductRepository` is an interface, 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. — Pluto.Domain/Handlers/Commands/ProductCommandHandler.cs:84
- `userRepository` is never created by `UserCommandHandler` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 116). Its declared type `IUserRepository` is an interface, 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. — Pluto.Domain/Handlers/Commands/UserCommandHandler.cs:116
- `context` is never created by `CrudRepository` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 70). Its declared type `DbContext` 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. — Pluto.Repository/Repositories/Common/CrudRepository.cs:70
- `context` is never created by `UnitOfWork` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 21). Its declared type `DbContext` 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. — Pluto.Repository/UoW/UnitOfWork.cs:21
- `encryptor` is a `ICryptoTransform`, which implements `IDisposable`, and it is created here (line 15). Every use of it in `Encrypt` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var encryptor = …;`), which releases it at the end of the scope on every path including a throw. — Pluto.Utils/Cryptography/Cryptography.cs:15
- `decryptor` is a `ICryptoTransform`, which implements `IDisposable`, and it is created here (line 29). Every use of it in `Decrypt` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var decryptor = …;`), which releases it at the end of the scope on every path including a throw. — Pluto.Utils/Cryptography/Cryptography.cs:29
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 15/48 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. (×33) — Pluto.Domain/Handlers/Commands/OrderCommandHandler.cs:155, Pluto.Repository/Repositories/Common/CrudRepository.cs:23, Pluto.Repository/Repositories/Common/CrudRepository.cs:33, …
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
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Strong | Solid. |
| Architecture | 86% | Strong | Solid. |
| Maturity | 53% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 18% | Critical — gated by D8, D9, P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73% | Strong | Solid. |
| Domain Modelling | 46% | Weak — gated by DM1, DM2 | 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 — 1 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.
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 — 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 — 43 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.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — 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.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — too few commits for a meaningful bus factor
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (2,385 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 (Pluto.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"]`.
- D24 Comment Value — Too few judgeable comments (19 of at least 30); comment value is not applicable here.
- 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
- 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)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Aggregate holds a reference to another aggregate: Order.Customer Pluto.Domain/Models/Order.cs:32
- Aggregate holds a reference to another aggregate: Order.Editor Pluto.Domain/Models/Order.cs:33
- WriteOnlyPrivateField Pluto.API/Controllers/OrderController.cs:18
- No automated tests
Serious — 93 finding(s)
- Async method without CancellationToken: GetOpenenedOrderFromUser Pluto.Domain/Handlers/Commands/OrderCommandHandler.cs:155
- Async method without CancellationToken: DeleteAsync Pluto.Repository/Repositories/Common/CrudRepository.cs:23
- Async method without CancellationToken: GetAsync Pluto.Repository/Repositories/Common/CrudRepository.cs:33
- Async method without CancellationToken: FirstOrDefaultAsync Pluto.Repository/Repositories/Common/CrudRepository.cs:35
- Async method without CancellationToken: SaveAsync Pluto.Repository/Repositories/Common/CrudRepository.cs:41
- Async method without CancellationToken: AnyAsync Pluto.Repository/Repositories/Common/CrudRepository.cs:49
- Async method without CancellationToken: AnyAsync Pluto.Repository/Repositories/Common/CrudRepository.cs:51
- Async method without CancellationToken: AddAsync Pluto.Repository/Repositories/Common/CrudRepository.cs:53
- Async method without CancellationToken: AddEventAsync Pluto.Repository/Repositories/StoredEventRepository.cs:18
- Async method without CancellationToken: SendAsync Pluto.Bus/InMemoryBus.cs:22
- Async method without CancellationToken: RequestAsync Pluto.Bus/InMemoryBus.cs:24
- Async method without CancellationToken: InvokeAsync Pluto.Bus/InMemoryBus.cs:26
- Async method without CancellationToken: InvokeDomainNotificationAsync Pluto.Bus/InMemoryBus.cs:34
- Async method without CancellationToken: Get Pluto.API/Controllers/AuthController.cs:48
- Async method without CancellationToken: Post Pluto.API/Controllers/AuthController.cs:57
- Async method without CancellationToken: GetUserByEmailAndPassword Pluto.API/Controllers/AuthController.cs:71
- Async method without CancellationToken: GetUserByRefreshToken Pluto.API/Controllers/AuthController.cs:87
- Async method without CancellationToken: GetUserByEmail Pluto.API/Controllers/AuthController.cs:108
- Async method without CancellationToken: Get Pluto.API/Controllers/OrderController.cs:44
- Async method without CancellationToken: AddProduct Pluto.API/Controllers/OrderController.cs:61
- Async method without CancellationToken: RemoveProduct Pluto.API/Controllers/OrderController.cs:71
- Async method without CancellationToken: Approve Pluto.API/Controllers/OrderController.cs:80
- Async method without CancellationToken: Cancel Pluto.API/Controllers/OrderController.cs:87
- Async method without CancellationToken: Commit Pluto.API/Controllers/OrderController.cs:94
- Async method without CancellationToken: Get REDACTED:34
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Deprecated: Microsoft.EntityFrameworkCore REDACTED:8
- Deprecated: Microsoft.EntityFrameworkCore.Design REDACTED:9
- Deprecated: Microsoft.EntityFrameworkCore.Proxies REDACTED:10
- Deprecated: Microsoft.EntityFrameworkCore.SqlServer REDACTED:11
- Deprecated: Microsoft.AspNetCore.App REDACTED:14
- Deprecated: Microsoft.AspNetCore.Razor.Design REDACTED:15
- Deprecated: Microsoft.NETCore.App
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Constructible in an invalid state: OrderItem Pluto.Domain/Models/OrderItem.cs:13
- Constructible in an invalid state: PictureUrl Pluto.Domain/Models/PictureUrl.cs:13
- Constructible in an invalid state: Product Pluto.Domain/Models/Product.cs:16
- Constructible in an invalid state: StoredEvent Pluto.Domain/Models/StoredEvent.cs:15
- Constructible in an invalid state: User Pluto.Domain/Models/User.cs:15
- Disposes a dependency it does not own Pluto.Domain/Handlers/Commands/ProductCommandHandler.cs:84
- Disposes a dependency it does not own Pluto.Domain/Handlers/Commands/UserCommandHandler.cs:116
- Disposes a dependency it does not own Pluto.Repository/Repositories/Common/CrudRepository.cs:70
- Disposes a dependency it does not own Pluto.Repository/UoW/UnitOfWork.cs:21
- Dead code: IHandler Pluto.Domain/Events/Interfaces/IHandler.cs:5
- Dead code: Decrypt Pluto.Utils/Cryptography/Cryptography.cs:23
- Dead code: WriteToConsole Pluto.Utils/Validations/Validation.cs:9
- Domain type reads the wall clock: Order Pluto.Domain/Models/Order.cs:66
- Domain type reads the wall clock: Order Pluto.Domain/Models/Order.cs:76
- Domain type reads the wall clock: Order Pluto.Domain/Models/Order.cs:86
- Anemic entity: OrderItem Pluto.Domain/Models/OrderItem.cs:5
- Anemic entity: PictureUrl Pluto.Domain/Models/PictureUrl.cs:5
- Anemic entity: StoredEvent Pluto.Domain/Models/StoredEvent.cs:7
- Fake-async — async method never awaits Pluto.Domain/Handlers/Events/UserEventHandler.cs:10
- Fake-async — async method never awaits Pluto.Domain/Notifications/DomainNotificationHandler.cs:13
- Fake-async — async method never awaits Pluto.Repository/Repositories/Common/CrudRepository.cs:55
- Sync-over-async (deadlock risk) through `.Result` Pluto.Domain/Handlers/Commands/UserCommandHandler.cs:42
- Sync-over-async (deadlock risk) through `.Result` Pluto.Domain/Handlers/Commands/UserCommandHandler.cs:66
- Disposable created and abandoned in the method that made it Pluto.Utils/Cryptography/Cryptography.cs:15
- Disposable created and abandoned in the method that made it Pluto.Utils/Cryptography/Cryptography.cs:29
- TodoComment Pluto.API/Controllers/OrderController.cs:33
- End-of-life runtime: .NET netcoreapp2.2 REDACTED:4
- Repository for a non-root entity: IStoredEventRepository → StoredEvent Pluto.Domain/Interfaces/Repositories/IStoredEventRepository.cs:8
- Repository contract exposes a live query handle: ICrudRepository Pluto.Domain/Interfaces/Repositories/Common/ICrudRepository.cs:10
- Non-idempotent mutation: Commands.ProductCommandHandler.Handle Pluto.Domain/Handlers/Commands/ProductCommandHandler.cs:30
- No CI pipeline
- No structured logging
- Weak hash algorithm Pluto.Utils/Cryptography/Cryptography.cs:40
- Weak cipher Pluto.Utils/Cryptography/Cryptography.cs:48
- NuGet dependencies are not locked
Minor — 43 finding(s)
- Event not named in past tense: AddProductEvent Pluto.Domain/Events/Order/AddProductEvent.cs:5
- Event not named in past tense: ApproveOrderEvent Pluto.Domain/Events/Order/ApproveOrderEvent.cs:6
- Event not named in past tense: CancelOrderEvent Pluto.Domain/Events/Order/CancelOrderEvent.cs:6
- Event not named in past tense: CommitOrderEvent Pluto.Domain/Events/Order/CommitOrderEvent.cs:6
- Event not named in past tense: CreateOrderEvent Pluto.Domain/Events/Order/CreateOrderEvent.cs:6
- Event not named in past tense: RemoveProductEvent Pluto.Domain/Events/Order/RemoveProductEvent.cs:6
- Event not named in past tense: CreateProductEvent Pluto.Domain/Events/Product/CreateProductEvent.cs:6
- Event not named in past tense: DeleteProductEvent Pluto.Domain/Events/Product/DeleteProductEvent.cs:6
- Event not named in past tense: UpdateProductEvent Pluto.Domain/Events/Product/UpdateProductEvent.cs:6
- Event not named in past tense: ChangeUserPasswordEvent Pluto.Domain/Events/User/ChangeUserPasswordEvent.cs:6
- Event not named in past tense: DeleteUserEvent Pluto.Domain/Events/User/DeleteUserEvent.cs:6
- Event not named in past tense: DomainNotification Pluto.Domain/Notifications/DomainNotification.cs:5
- Primitive id on a domain type: ApproveOrderEvent.OrderId Pluto.Domain/Events/Order/ApproveOrderEvent.cs:16
- Primitive id on a domain type: ApproveOrderEvent.UserId Pluto.Domain/Events/Order/ApproveOrderEvent.cs:17
- Primitive id on a domain type: CancelOrderEvent.OrderId Pluto.Domain/Events/Order/CancelOrderEvent.cs:16
- Primitive id on a domain type: CancelOrderEvent.UserId Pluto.Domain/Events/Order/CancelOrderEvent.cs:17
- Primitive id on a domain type: CommitOrderEvent.OrderId Pluto.Domain/Events/Order/CommitOrderEvent.cs:16
- Primitive id on a domain type: CommitOrderEvent.UserId Pluto.Domain/Events/Order/CommitOrderEvent.cs:17
- Primitive id on a domain type: RemoveProductEvent.OrderId Pluto.Domain/Events/Order/RemoveProductEvent.cs:16
- Primitive id on a domain type: RemoveProductEvent.ProductId Pluto.Domain/Events/Order/RemoveProductEvent.cs:17
- Primitive id on a domain type: StoredEvent.AggregateId Pluto.Domain/Models/StoredEvent.cs:24
- Outdated: MediatR Pluto.Domain/Pluto.Domain.csproj:8
- Outdated: Microsoft.EntityFrameworkCore REDACTED:8
- Outdated: Microsoft.EntityFrameworkCore.Design REDACTED:9
- Outdated: Microsoft.EntityFrameworkCore.Proxies REDACTED:10
- Outdated: Microsoft.EntityFrameworkCore.SqlServer REDACTED:11
- Outdated: AutoMapper.Extensions.Microsoft.DependencyInjection REDACTED:12
- Outdated: MediatR.Extensions.Microsoft.DependencyInjection REDACTED:13
- Outdated: Swashbuckle.AspNetCore REDACTED:16
- Documentation: no build, run or usage example README.md:1
- Documentation: no map of the repository's parts README.md:1
- Mutable entity: Order Pluto.Domain/Models/Order.cs:9
- Mutable entity: Product Pluto.Domain/Models/Product.cs:8
- No security response headers detected
- No security response headers detected Pluto.API/Program.cs:14
- No ADRs found
- `GetOpenenedOrderFromUser` returns an awaitable but lacks the `Async` suffix its 13 peers carry Pluto.Domain/Handlers/Commands/OrderCommandHandler.cs:155
- No tests found
- No ADRs
- No src/ separation
- No SAST
- No dependency-update automation REDACTED:12
- Not all async methods take a CancellationToken
Minor — 3 finding(s)
- Outdated: Newtonsoft.Json
- Outdated: Microsoft.AspNetCore.Razor.Design
- Outdated: System.ComponentModel.Annotations
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-0c83e8757d544b078ffc0d21c30aaafc/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0c83e8757d544b078ffc0d21c30aaafc/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude Pluto.Repository/Migrations . | 11 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Pluto.sln package --vulnerable --include-transitive --format json | 18 | 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-0629ef3bfb5e41fb80b2a492307a7924 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 10 field(s)
- AuthRequestDto.Email Pluto.API/Auth/AuthRequestDto.cs:5
- RefreshTokenData.Email Pluto.API/Auth/RefreshTokenData.cs:6
- UserControl.Email Pluto.API/Auth/UserControl.cs:18
- CreateUserCommand.Email Pluto.Domain/Commands/User/CreateUserCommand.cs:9
- UpdateUserCommand.Email Pluto.Domain/Commands/User/UpdateUserCommand.cs:11
- User.Email Pluto.Domain/Dtos/User.cs:9
- CreateUserEvent.Email Pluto.Domain/Events/User/CreateUserEvent.cs:22
- UpdateUserEvent.Email Pluto.Domain/Events/User/UpdateUserEvent.cs:21
- IUser.Email Pluto.Domain/Interfaces/Identity/IUser.cs:11
- User.Email Pluto.Domain/Models/User.cs:24