Executive summary
dnikolovv/cafe is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 40 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 24, is the weakest lens and counts most in the score. The best first steps are adding tests for the code no test reaches and adding automated security scanning, each worth about 4 points. Raising Production Readiness to 70 would lift the score to about 54.
119 known security holes in the packages the code depends on can be used by attackers. Two settings leave the servers or containers unsafe. Updating the vulnerable packages and correcting the unsafe settings would close both risks. The ten pieces of business logic tied to the database or web code need separating from the database and web code.
The product code is 9,435 lines, about €19,000 to rebuild.
If Production Readiness rose from 24 to 70, the lowest score rated Strong, the score would rise from 40 to about 54.
New since the last survey: 18 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 REDACTED
- Web-Security Posture · Secure cookie flags not detected REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAllUserAccounts REDACTED
- Cancellation propagation · Async method without CancellationToken: GetEmployedBaristas server/src/server/Cafe.Api/Controllers/BaristaController.cs
- Cancellation propagation · Async method without CancellationToken: GetEmployedCashiers server/src/server/Cafe.Api/Controllers/CashierController.cs
- Cancellation propagation · Async method without CancellationToken: GetEmployedManagers server/src/server/Cafe.Api/Controllers/ManagerController.cs
- Cancellation propagation · Async method without CancellationToken: GetMenuItems REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAllOrders server/src/server/Cafe.Api/Controllers/OrderController.cs
- Cancellation propagation · Async method without CancellationToken: GetAllOpenTabs server/src/server/Cafe.Api/Controllers/TabController.cs
- Cancellation propagation · Async method without CancellationToken: GetTabHistory server/src/server/Cafe.Api/Controllers/TabController.cs
- Cancellation propagation · Async method without CancellationToken: GetAllTables REDACTED
- Cancellation propagation · Async method without CancellationToken: GetEmployedWaiters server/src/server/Cafe.Api/Controllers/WaiterController.cs
Fixed since the last survey: 64 findings
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Platform End-of-Life · End-of-life runtime: .NET netcoreapp2.2 REDACTED
- Cancellation propagation · Async method without CancellationToken: AddDefaultAdminAccountIfNoneExisting server/src/server/Cafe.Api/Configuration/DatabaseConfiguration.cs
- Cancellation propagation · Async method without CancellationToken: Logout REDACTED
- Cancellation propagation · Async method without CancellationToken: ApiHome REDACTED
- Cancellation propagation · Async method without CancellationToken: ResourceContainerResult server/src/server/Cafe.Api/Controllers/_Base/ApiController.cs
- Cancellation propagation · Async method without CancellationToken: GetWaiterAccountsToNotify server/src/server/Cafe.Api/Dispatchers/TableActionsDispatcher.cs
- Cancellation propagation · Async method without CancellationToken: NotifyWaiterAtTable server/src/server/Cafe.Api/Dispatchers/TableActionsDispatcher.cs
- Cancellation propagation · Async method without CancellationToken: AccountShouldExist server/src/server/Cafe.Business/AuthContext/CommandHandlers/BaseAuthHandler.cs
- Cancellation propagation · Async method without CancellationToken: CheckPassword server/src/server/Cafe.Business/AuthContext/CommandHandlers/LoginHandler.cs
- Cancellation propagation · Async method without CancellationToken: CheckIfUserDoesntExist server/src/server/Cafe.Business/AuthContext/CommandHandlers/RegisterHandler.cs
- Cancellation propagation · Async method without CancellationToken: BaristaShouldNotExist server/src/server/Cafe.Business/BaristaContext/CommandHandlers/HireBaristaHandler.cs
- Cancellation propagation · Async method without CancellationToken: CashierShouldntExist server/src/server/Cafe.Business/CashierContext/CommandHandlers/HireCashierHandler.cs
- Cancellation propagation · Async method without CancellationToken: ManagerShouldntExist server/src/server/Cafe.Business/ManagerContext/CommandHandlers/HireManagerHandler.cs
- Cancellation propagation · Async method without CancellationToken: CheckIfNumbersAreNotConflicting server/src/server/Cafe.Business/MenuContext/CommandHandlers/AddMenuItemsHandler.cs
- Cancellation propagation · Async method without CancellationToken: OrderMustExist server/src/server/Cafe.Business/OrderContext/CommandHandlers/BaseOrderHandler.cs
- Cancellation propagation · Async method without CancellationToken: SetOrderStatus server/src/server/Cafe.Business/OrderContext/CommandHandlers/BaseOrderHandler.cs
- Cancellation propagation · Async method without CancellationToken: AssignOrderToBaristaIfAny server/src/server/Cafe.Business/OrderContext/CommandHandlers/CompleteToGoOrderHandler.cs
- Cancellation propagation · Async method without CancellationToken: CheckIfOrderIsNotExisting server/src/server/Cafe.Business/OrderContext/CommandHandlers/OrderToGoHandler.cs
- Cancellation propagation · Async method without CancellationToken: GetTabIfExists server/src/server/Cafe.Business/TabContext/CommandHandlers/BaseTabHandler.cs
- Cancellation propagation · Async method without CancellationToken: TabShouldNotExist server/src/server/Cafe.Business/TabContext/CommandHandlers/BaseTabHandler.cs
- Cancellation propagation · Async method without CancellationToken: TableShouldNotBeTaken server/src/server/Cafe.Business/TabContext/CommandHandlers/OpenTabHandler.cs
- Cancellation propagation · Async method without CancellationToken: TheTableShouldHaveAWaiterAssigned server/src/server/Cafe.Business/TabContext/CommandHandlers/OpenTabHandler.cs
- Cancellation propagation · Async method without CancellationToken: CheckIfNumberIsNotTaken server/src/server/Cafe.Business/TableContext/CommandHandlers/AddTableHandler.cs
- Cancellation propagation · Async method without CancellationToken: TableShouldExist server/src/server/Cafe.Business/TableContext/CommandHandlers/BaseTableHandler.cs
- Cancellation propagation · Async method without CancellationToken: WaiterShouldntExist server/src/server/Cafe.Business/WaiterContext/CommandHandlers/HireWaiterHandler.cs
- Cancellation propagation · Async method without CancellationToken: PersistWaiter server/src/server/Cafe.Business/WaiterContext/CommandHandlers/HireWaiterHandler.cs
- Cancellation propagation · Async method without CancellationToken: Publish server/src/server/Cafe.Business/_Base/EventBus.cs
- Cancellation propagation · Async method without CancellationToken: ItemsShouldExist server/src/server/Cafe.Business/_Kernel/MenuItemsService.cs
- Cancellation propagation · Async method without CancellationToken: Add server/src/server/Cafe.Persistance/Repositories/BaristaRepository.cs
- Cancellation propagation · Async method without CancellationToken: Get server/src/server/Cafe.Persistance/Repositories/BaristaRepository.cs
- Cancellation propagation · Async method without CancellationToken: Update server/src/server/Cafe.Persistance/Repositories/BaristaRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAll server/src/server/Cafe.Persistance/Repositories/BaristaViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: Add server/src/server/Cafe.Persistance/Repositories/CashierRepository.cs
- Cancellation propagation · Async method without CancellationToken: Get server/src/server/Cafe.Persistance/Repositories/CashierRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAll server/src/server/Cafe.Persistance/Repositories/CashierViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: Add server/src/server/Cafe.Persistance/Repositories/ManagerRepository.cs
- Cancellation propagation · Async method without CancellationToken: Get server/src/server/Cafe.Persistance/Repositories/ManagerRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAll server/src/server/Cafe.Persistance/Repositories/ManagerViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: Add server/src/server/Cafe.Persistance/Repositories/MenuItemRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAll server/src/server/Cafe.Persistance/Repositories/MenuItemRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAll server/src/server/Cafe.Persistance/Repositories/MenuItemViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: Add server/src/server/Cafe.Persistance/Repositories/TableRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetByNumber server/src/server/Cafe.Persistance/Repositories/TableRepository.cs
- Cancellation propagation · Async method without CancellationToken: Update server/src/server/Cafe.Persistance/Repositories/TableRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAll server/src/server/Cafe.Persistance/Repositories/TableViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: Get server/src/server/Cafe.Persistance/Repositories/TabRepository.cs
- Cancellation propagation · Async method without CancellationToken: Get server/src/server/Cafe.Persistance/Repositories/TabViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetTabs server/src/server/Cafe.Persistance/Repositories/TabViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: Add server/src/server/Cafe.Persistance/Repositories/ToGoOrderRepository.cs
- Cancellation propagation · Async method without CancellationToken: Get server/src/server/Cafe.Persistance/Repositories/ToGoOrderRepository.cs
- Cancellation propagation · Async method without CancellationToken: Update server/src/server/Cafe.Persistance/Repositories/ToGoOrderRepository.cs
- Cancellation propagation · Async method without CancellationToken: Get server/src/server/Cafe.Persistance/Repositories/ToGoOrderViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: FetchOrders server/src/server/Cafe.Persistance/Repositories/ToGoOrderViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAll server/src/server/Cafe.Persistance/Repositories/UserViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: Get server/src/server/Cafe.Persistance/Repositories/UserViewRepository.cs
- Cancellation propagation · Async method without CancellationToken: Add server/src/server/Cafe.Persistance/Repositories/WaiterRepository.cs
- Cancellation propagation · Async method without CancellationToken: Get server/src/server/Cafe.Persistance/Repositories/WaiterRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAll server/src/server/Cafe.Persistance/Repositories/WaiterViewRepository.cs
Rebuild cost: about €19,000 · Estimate
| Cost to rebuild | €6,300 to €31,000, for 105 to 327 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 40. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 9,435 lines of product code |
| Comment lines | The estimate prices 9,266 lines. Comment lines count towards the size of 9,435 lines but aren't priced as work. |
| 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.Hateoas.Resources | 2 Domain | 3 Domain.Views | 4 Domain.Events | 5 Domain.Entities | 6 Api.Hateoas.Resources.Order | 7 Core | 8 Domain.Repositories | 9 Persistance.EntityFramework | 10 Api.Configuration | 11 Api.Dispatchers | 12 Business | 13 Business.AuthContext.QueryHandlers | 14 Business.BaristaContext.QueryHandlers | 15 Business.CashierContext.QueryHandlers | 16 Business.ManagerContext.QueryHandlers | 17 Business.MenuContext.QueryHandlers | 18 Business.TabContext.QueryHandlers | 19 Business.TableContext.QueryHandlers | 20 Business.WaiterContext.QueryHandlers | 21 Core.AuthContext.Commands | 22 Core.BaristaContext.Commands | 23 Core.CashierContext.Commands | 24 Core.ManagerContext.Commands | 25 Core.MenuContext.Commands | 26 Core.OrderContext.Commands | 27 Core.OrderContext.Queries | 28 Persistance.Repositories | 29 Api | 30 Api.Controllers | 31 Business.AuthContext.CommandHandlers | 32 Business.BaristaContext.CommandHandlers | 33 Business.CashierContext.CommandHandlers | 34 Business.ManagerContext.CommandHandlers | 35 Business.MenuContext.CommandHandlers | 36 Business.OrderContext.CommandHandlers | 37 Business.OrderContext.QueryHandlers | 38 Business.TabContext.CommandHandlers | 39 Business.TableContext.CommandHandlers | 40 Business.WaiterContext.CommandHandlers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Api.Hateoas.Resources | ||||||||||||||||||||||||||||||||||||||||
| 2 Domain | ||||||||||||||||||||||||||||||||||||||||
| 3 Domain.Views | 5 | 2 | ||||||||||||||||||||||||||||||||||||||
| 4 Domain.Events | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 5 Domain.Entities | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 6 Api.Hateoas.Resources.Order | 10 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 7 Core | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 Domain.Repositories | 1 | 9 | 10 | |||||||||||||||||||||||||||||||||||||
| 9 Persistance.EntityFramework | 8 | |||||||||||||||||||||||||||||||||||||||
| 10 Api.Configuration | 8 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 Api.Dispatchers | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Business | 2 | 3 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 13 Business.AuthContext.QueryHandlers | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 14 Business.BaristaContext.QueryHandlers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 Business.CashierContext.QueryHandlers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 Business.ManagerContext.QueryHandlers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 Business.MenuContext.QueryHandlers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 Business.TabContext.QueryHandlers | 1 | 3 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 19 Business.TableContext.QueryHandlers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 Business.WaiterContext.QueryHandlers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 Core.AuthContext.Commands | 6 | |||||||||||||||||||||||||||||||||||||||
| 22 Core.BaristaContext.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Core.CashierContext.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Core.ManagerContext.Commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Core.MenuContext.Commands | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Core.OrderContext.Commands | 3 | |||||||||||||||||||||||||||||||||||||||
| 27 Core.OrderContext.Queries | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 28 Persistance.Repositories | 1 | 9 | 11 | 18 | 15 | |||||||||||||||||||||||||||||||||||
| 29 Api | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 Api.Controllers | 11 | 1 | 1 | 1 | 6 | 1 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||
| 31 Business.AuthContext.CommandHandlers | 7 | 1 | 6 | 6 | 1 | 11 | 1 | 6 | ||||||||||||||||||||||||||||||||
| 32 Business.BaristaContext.CommandHandlers | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 33 Business.CashierContext.CommandHandlers | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 Business.ManagerContext.CommandHandlers | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 Business.MenuContext.CommandHandlers | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 Business.OrderContext.CommandHandlers | 4 | 4 | 6 | 1 | 5 | 2 | 3 | |||||||||||||||||||||||||||||||||
| 37 Business.OrderContext.QueryHandlers | 1 | 3 | 3 | 3 | 3 | |||||||||||||||||||||||||||||||||||
| 38 Business.TabContext.CommandHandlers | 6 | 6 | 4 | 6 | 8 | 1 | ||||||||||||||||||||||||||||||||||
| 39 Business.TableContext.CommandHandlers | 4 | 4 | 3 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 40 Business.WaiterContext.CommandHandlers | 2 | 2 | 2 | 3 | 2 |
3→4 Domain.Views uses Domain.Events part of a loop✕
- Connections
- 5 pairs of types, where a type in Domain.Views uses a type in Domain.Events.
- The types involved
Cafe.Domain.Views.TabView→Cafe.Domain.Events.MenuItemsOrderedCafe.Domain.Views.TabView→Cafe.Domain.Events.MenuItemsRejectedCafe.Domain.Views.TabView→Cafe.Domain.Events.MenuItemsServedCafe.Domain.Views.TabView→Cafe.Domain.Events.TabClosedCafe.Domain.Views.TabView→Cafe.Domain.Events.TabOpened
- Direction
- Domain.Views uses Domain.Events, so a change to Domain.Events can break Domain.Views, while a change to Domain.Views can't break Domain.Events.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→5 Domain.Views uses Domain.Entities part of a loop✕
- Connections
- 2 pairs of types, where a type in Domain.Views uses a type in Domain.Entities.
- The types involved
Cafe.Domain.Views.MenuItemView→Cafe.Domain.Entities.MenuItemCafe.Domain.Views.ToGoOrderView→Cafe.Domain.Entities.ToGoOrderStatus
- Direction
- Domain.Views uses Domain.Entities, so a change to Domain.Entities can break Domain.Views, while a change to Domain.Views can't break Domain.Entities.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→3 Domain.Events uses Domain.Views✕
- Connections
- 2 pairs of types, where a type in Domain.Events uses a type in Domain.Views.
- The types involved
Cafe.Domain.Events.OrderConfirmed→Cafe.Domain.Views.ToGoOrderViewCafe.Domain.Events.WaiterHired→Cafe.Domain.Views.WaiterView
- Direction
- Domain.Events uses Domain.Views, so a change to Domain.Views can break Domain.Events, while a change to Domain.Events can't break Domain.Views.
- Position
- Below the diagonal: Domain.Events uses a module listed above it, which is the healthy direction.
4→5 Domain.Events uses Domain.Entities part of a loop✕
- Connections
- 3 pairs of types, where a type in Domain.Events uses a type in Domain.Entities.
- The types involved
Cafe.Domain.Events.MenuItemsOrdered→Cafe.Domain.Entities.MenuItemCafe.Domain.Events.MenuItemsRejected→Cafe.Domain.Entities.MenuItemCafe.Domain.Events.MenuItemsServed→Cafe.Domain.Entities.MenuItem
- Direction
- Domain.Events uses Domain.Entities, so a change to Domain.Entities can break Domain.Events, while a change to Domain.Events can't break Domain.Entities.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→2 Domain.Entities uses Domain✕
- Connections
- 1 pair of types, where a type in Domain.Entities uses a type in Domain.
- The types involved
Cafe.Domain.Entities.Tab→Cafe.Domain.IAggregate
- Direction
- Domain.Entities uses Domain, so a change to Domain can break Domain.Entities, while a change to Domain.Entities can't break Domain.
- Position
- Below the diagonal: Domain.Entities uses a module listed above it, which is the healthy direction.
5→4 Domain.Entities uses Domain.Events✕
- Connections
- 5 pairs of types, where a type in Domain.Entities uses a type in Domain.Events.
- The types involved
Cafe.Domain.Entities.Tab→Cafe.Domain.Events.MenuItemsOrderedCafe.Domain.Entities.Tab→Cafe.Domain.Events.MenuItemsRejectedCafe.Domain.Entities.Tab→Cafe.Domain.Events.MenuItemsServedCafe.Domain.Entities.Tab→Cafe.Domain.Events.TabClosedCafe.Domain.Entities.Tab→Cafe.Domain.Events.TabOpened
- Direction
- Domain.Entities uses Domain.Events, so a change to Domain.Events can break Domain.Entities, while a change to Domain.Entities can't break Domain.Events.
- Position
- Below the diagonal: Domain.Entities uses a module listed above it, which is the healthy direction.
6→1 Api.Hateoas.Resources.Order uses Api.Hateoas.Resources✕
- Connections
- 10 pairs of types, where a type in Api.Hateoas.Resources.Order uses a type in Api.Hateoas.Resources.
- The types involved
Cafe.Api.Hateoas.Resources.Order.CompleteToGoOrderResource→Cafe.Api.Hateoas.Resources.ResourceCafe.Api.Hateoas.Resources.Order.CompleteToGoOrderResourcePolicy→Cafe.Api.Hateoas.Resources.IPolicyCafe.Api.Hateoas.Resources.Order.ConfirmToGoOrderResource→Cafe.Api.Hateoas.Resources.ResourceCafe.Api.Hateoas.Resources.Order.ConfirmToGoOrderResourcePolicy→Cafe.Api.Hateoas.Resources.IPolicyCafe.Api.Hateoas.Resources.Order.OrderToGoResource→Cafe.Api.Hateoas.Resources.ResourceCafe.Api.Hateoas.Resources.Order.OrderToGoResourcePolicy→Cafe.Api.Hateoas.Resources.IPolicyCafe.Api.Hateoas.Resources.Order.ToGoOrderContainerResource→Cafe.Api.Hateoas.Resources.ResourceContainerCafe.Api.Hateoas.Resources.Order.ToGoOrderContainerResourcePolicy→Cafe.Api.Hateoas.Resources.IPolicyCafe.Api.Hateoas.Resources.Order.ToGoOrderResource→Cafe.Api.Hateoas.Resources.ResourceCafe.Api.Hateoas.Resources.Order.ToGoOrderResourcePolicy→Cafe.Api.Hateoas.Resources.IPolicy
- Direction
- Api.Hateoas.Resources.Order uses Api.Hateoas.Resources, so a change to Api.Hateoas.Resources can break Api.Hateoas.Resources.Order, while a change to Api.Hateoas.Resources.Order can't break Api.Hateoas.Resources.
- Position
- Below the diagonal: Api.Hateoas.Resources.Order uses a module listed above it, which is the healthy direction.
6→3 Api.Hateoas.Resources.Order uses Domain.Views✕
- Connections
- 1 pair of types, where a type in Api.Hateoas.Resources.Order uses a type in Domain.Views.
- The types involved
Cafe.Api.Hateoas.Resources.Order.ToGoOrderResource→Cafe.Domain.Views.MenuItemView
- Direction
- Api.Hateoas.Resources.Order uses Domain.Views, so a change to Domain.Views can break Api.Hateoas.Resources.Order, while a change to Api.Hateoas.Resources.Order can't break Domain.Views.
- Position
- Below the diagonal: Api.Hateoas.Resources.Order uses a module listed above it, which is the healthy direction.
6→5 Api.Hateoas.Resources.Order uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Api.Hateoas.Resources.Order uses a type in Domain.Entities.
- The types involved
Cafe.Api.Hateoas.Resources.Order.ToGoOrderResource→Cafe.Domain.Entities.ToGoOrderStatus
- Direction
- Api.Hateoas.Resources.Order uses Domain.Entities, so a change to Domain.Entities can break Api.Hateoas.Resources.Order, while a change to Api.Hateoas.Resources.Order can't break Domain.Entities.
- Position
- Below the diagonal: Api.Hateoas.Resources.Order uses a module listed above it, which is the healthy direction.
7→2 Core uses Domain✕
- Connections
- 1 pair of types, where a type in Core uses a type in Domain.
- The types involved
Cafe.Core.IMenuItemsService→Cafe.Domain.Error
- Direction
- Core uses Domain, so a change to Domain can break Core, while a change to Core can't break Domain.
- Position
- Below the diagonal: Core uses a module listed above it, which is the healthy direction.
7→5 Core uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Core uses a type in Domain.Entities.
- The types involved
Cafe.Core.IMenuItemsService→Cafe.Domain.Entities.MenuItem
- Direction
- Core uses Domain.Entities, so a change to Domain.Entities can break Core, while a change to Core can't break Domain.Entities.
- Position
- Below the diagonal: Core uses a module listed above it, which is the healthy direction.
8→2 Domain.Repositories uses Domain✕
- Connections
- 1 pair of types, where a type in Domain.Repositories uses a type in Domain.
- The types involved
Cafe.Domain.Repositories.IUserRepository→Cafe.Domain.Error
- Direction
- Domain.Repositories uses Domain, so a change to Domain can break Domain.Repositories, while a change to Domain.Repositories can't break Domain.
- Position
- Below the diagonal: Domain.Repositories uses a module listed above it, which is the healthy direction.
8→3 Domain.Repositories uses Domain.Views✕
- Connections
- 9 pairs of types, where a type in Domain.Repositories uses a type in Domain.Views.
- The types involved
Cafe.Domain.Repositories.IBaristaViewRepository→Cafe.Domain.Views.BaristaViewCafe.Domain.Repositories.ICashierViewRepository→Cafe.Domain.Views.CashierViewCafe.Domain.Repositories.IManagerViewRepository→Cafe.Domain.Views.ManagerViewCafe.Domain.Repositories.IMenuItemViewRepository→Cafe.Domain.Views.MenuItemViewCafe.Domain.Repositories.ITabViewRepository→Cafe.Domain.Views.TabViewCafe.Domain.Repositories.ITableViewRepository→Cafe.Domain.Views.TableViewCafe.Domain.Repositories.IToGoOrderViewRepository→Cafe.Domain.Views.ToGoOrderViewCafe.Domain.Repositories.IUserViewRepository→Cafe.Domain.Views.UserViewCafe.Domain.Repositories.IWaiterViewRepository→Cafe.Domain.Views.WaiterView
- Direction
- Domain.Repositories uses Domain.Views, so a change to Domain.Views can break Domain.Repositories, while a change to Domain.Repositories can't break Domain.Views.
- Position
- Below the diagonal: Domain.Repositories uses a module listed above it, which is the healthy direction.
8→5 Domain.Repositories uses Domain.Entities✕
- Connections
- 10 pairs of types, where a type in Domain.Repositories uses a type in Domain.Entities.
- The types involved
Cafe.Domain.Repositories.IBaristaRepository→Cafe.Domain.Entities.BaristaCafe.Domain.Repositories.ICashierRepository→Cafe.Domain.Entities.CashierCafe.Domain.Repositories.IManagerRepository→Cafe.Domain.Entities.ManagerCafe.Domain.Repositories.IMenuItemRepository→Cafe.Domain.Entities.MenuItemCafe.Domain.Repositories.ITabRepository→Cafe.Domain.Entities.TabCafe.Domain.Repositories.ITableRepository→Cafe.Domain.Entities.TableCafe.Domain.Repositories.IToGoOrderRepository→Cafe.Domain.Entities.ToGoOrderCafe.Domain.Repositories.IToGoOrderViewRepository→Cafe.Domain.Entities.ToGoOrderStatusCafe.Domain.Repositories.IUserRepository→Cafe.Domain.Entities.UserCafe.Domain.Repositories.IWaiterRepository→Cafe.Domain.Entities.Waiter
- Direction
- Domain.Repositories uses Domain.Entities, so a change to Domain.Entities can break Domain.Repositories, while a change to Domain.Repositories can't break Domain.Entities.
- Position
- Below the diagonal: Domain.Repositories uses a module listed above it, which is the healthy direction.
9→5 Persistance.EntityFramework uses Domain.Entities✕
- Connections
- 8 pairs of types, where a type in Persistance.EntityFramework uses a type in Domain.Entities.
- The types involved
Cafe.Persistance.EntityFramework.ApplicationDbContext→Cafe.Domain.Entities.BaristaCafe.Persistance.EntityFramework.ApplicationDbContext→Cafe.Domain.Entities.CashierCafe.Persistance.EntityFramework.ApplicationDbContext→Cafe.Domain.Entities.ManagerCafe.Persistance.EntityFramework.ApplicationDbContext→Cafe.Domain.Entities.MenuItemCafe.Persistance.EntityFramework.ApplicationDbContext→Cafe.Domain.Entities.TableCafe.Persistance.EntityFramework.ApplicationDbContext→Cafe.Domain.Entities.ToGoOrderCafe.Persistance.EntityFramework.ApplicationDbContext→Cafe.Domain.Entities.ToGoOrderMenuItemCafe.Persistance.EntityFramework.ApplicationDbContext→Cafe.Domain.Entities.Waiter
- Direction
- Persistance.EntityFramework uses Domain.Entities, so a change to Domain.Entities can break Persistance.EntityFramework, while a change to Persistance.EntityFramework can't break Domain.Entities.
- Position
- Below the diagonal: Persistance.EntityFramework uses a module listed above it, which is the healthy direction.
10→5 Api.Configuration uses Domain.Entities✕
- Connections
- 8 pairs of types, where a type in Api.Configuration uses a type in Domain.Entities.
- The types involved
Cafe.Api.Configuration.DatabaseConfiguration→Cafe.Domain.Entities.UserCafe.Api.Configuration.DatabaseSeeder→Cafe.Domain.Entities.BaristaCafe.Api.Configuration.DatabaseSeeder→Cafe.Domain.Entities.CashierCafe.Api.Configuration.DatabaseSeeder→Cafe.Domain.Entities.ManagerCafe.Api.Configuration.DatabaseSeeder→Cafe.Domain.Entities.MenuItemCafe.Api.Configuration.DatabaseSeeder→Cafe.Domain.Entities.TableCafe.Api.Configuration.DatabaseSeeder→Cafe.Domain.Entities.UserCafe.Api.Configuration.DatabaseSeeder→Cafe.Domain.Entities.Waiter
- Direction
- Api.Configuration uses Domain.Entities, so a change to Domain.Entities can break Api.Configuration, while a change to Api.Configuration can't break Domain.Entities.
- Position
- Below the diagonal: Api.Configuration uses a module listed above it, which is the healthy direction.
10→9 Api.Configuration uses Persistance.EntityFramework✕
- Connections
- 1 pair of types, where a type in Api.Configuration uses a type in Persistance.EntityFramework.
- The types involved
Cafe.Api.Configuration.DatabaseSeeder→Cafe.Persistance.EntityFramework.ApplicationDbContext
- Direction
- Api.Configuration uses Persistance.EntityFramework, so a change to Persistance.EntityFramework can break Api.Configuration, while a change to Api.Configuration can't break Persistance.EntityFramework.
- Position
- Below the diagonal: Api.Configuration uses a module listed above it, which is the healthy direction.
11→4 Api.Dispatchers uses Domain.Events✕
- Connections
- 4 pairs of types, where a type in Api.Dispatchers uses a type in Domain.Events.
- The types involved
Cafe.Api.Dispatchers.ConfirmedOrdersDispatcher→Cafe.Domain.Events.OrderConfirmedCafe.Api.Dispatchers.HiredWaitersDispatcher→Cafe.Domain.Events.WaiterHiredCafe.Api.Dispatchers.TableActionsDispatcher→Cafe.Domain.Events.BillRequestedCafe.Api.Dispatchers.TableActionsDispatcher→Cafe.Domain.Events.WaiterCalled
- Direction
- Api.Dispatchers uses Domain.Events, so a change to Domain.Events can break Api.Dispatchers, while a change to Api.Dispatchers can't break Domain.Events.
- Position
- Below the diagonal: Api.Dispatchers uses a module listed above it, which is the healthy direction.
11→9 Api.Dispatchers uses Persistance.EntityFramework✕
- Connections
- 1 pair of types, where a type in Api.Dispatchers uses a type in Persistance.EntityFramework.
- The types involved
Cafe.Api.Dispatchers.TableActionsDispatcher→Cafe.Persistance.EntityFramework.ApplicationDbContext
- Direction
- Api.Dispatchers uses Persistance.EntityFramework, so a change to Persistance.EntityFramework can break Api.Dispatchers, while a change to Api.Dispatchers can't break Persistance.EntityFramework.
- Position
- Below the diagonal: Api.Dispatchers uses a module listed above it, which is the healthy direction.
12→2 Business uses Domain✕
- Connections
- 2 pairs of types, where a type in Business uses a type in Domain.
- The types involved
Cafe.Business.BaseHandler→Cafe.Domain.ErrorCafe.Business.MenuItemsService→Cafe.Domain.Error
- Direction
- Business uses Domain, so a change to Domain can break Business, while a change to Business can't break Domain.
- Position
- Below the diagonal: Business uses a module listed above it, which is the healthy direction.
12→4 Business uses Domain.Events✕
- Connections
- 3 pairs of types, where a type in Business uses a type in Domain.Events.
- The types involved
Cafe.Business.BaseHandler→Cafe.Domain.Events.IEventCafe.Business.BaseHandler→Cafe.Domain.Events.IEventBusCafe.Business.EventBus→Cafe.Domain.Events.IEventBus
- Direction
- Business uses Domain.Events, so a change to Domain.Events can break Business, while a change to Business can't break Domain.Events.
- Position
- Below the diagonal: Business uses a module listed above it, which is the healthy direction.
12→5 Business uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Business uses a type in Domain.Entities.
- The types involved
Cafe.Business.MenuItemsService→Cafe.Domain.Entities.MenuItem
- Direction
- Business uses Domain.Entities, so a change to Domain.Entities can break Business, while a change to Business can't break Domain.Entities.
- Position
- Below the diagonal: Business uses a module listed above it, which is the healthy direction.
12→7 Business uses Core✕
- Connections
- 2 pairs of types, where a type in Business uses a type in Core.
- The types involved
Cafe.Business.BaseHandler→Cafe.Core.ICommandHandlerCafe.Business.MenuItemsService→Cafe.Core.IMenuItemsService
- Direction
- Business uses Core, so a change to Core can break Business, while a change to Business can't break Core.
- Position
- Below the diagonal: Business uses a module listed above it, which is the healthy direction.
12→8 Business uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business uses a type in Domain.Repositories.
- The types involved
Cafe.Business.MenuItemsService→Cafe.Domain.Repositories.IMenuItemRepository
- Direction
- Business uses Domain.Repositories, so a change to Domain.Repositories can break Business, while a change to Business can't break Domain.Repositories.
- Position
- Below the diagonal: Business uses a module listed above it, which is the healthy direction.
13→2 Business.AuthContext.QueryHandlers uses Domain✕
- Connections
- 1 pair of types, where a type in Business.AuthContext.QueryHandlers uses a type in Domain.
- The types involved
Cafe.Business.AuthContext.QueryHandlers.GetUserHandler→Cafe.Domain.Error
- Direction
- Business.AuthContext.QueryHandlers uses Domain, so a change to Domain can break Business.AuthContext.QueryHandlers, while a change to Business.AuthContext.QueryHandlers can't break Domain.
- Position
- Below the diagonal: Business.AuthContext.QueryHandlers uses a module listed above it, which is the healthy direction.
13→3 Business.AuthContext.QueryHandlers uses Domain.Views✕
- Connections
- 2 pairs of types, where a type in Business.AuthContext.QueryHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.AuthContext.QueryHandlers.GetAllUserAccountsHandler→Cafe.Domain.Views.UserViewCafe.Business.AuthContext.QueryHandlers.GetUserHandler→Cafe.Domain.Views.UserView
- Direction
- Business.AuthContext.QueryHandlers uses Domain.Views, so a change to Domain.Views can break Business.AuthContext.QueryHandlers, while a change to Business.AuthContext.QueryHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.AuthContext.QueryHandlers uses a module listed above it, which is the healthy direction.
13→7 Business.AuthContext.QueryHandlers uses Core✕
- Connections
- 2 pairs of types, where a type in Business.AuthContext.QueryHandlers uses a type in Core.
- The types involved
Cafe.Business.AuthContext.QueryHandlers.GetAllUserAccountsHandler→Cafe.Core.IQueryHandlerCafe.Business.AuthContext.QueryHandlers.GetUserHandler→Cafe.Core.IQueryHandler
- Direction
- Business.AuthContext.QueryHandlers uses Core, so a change to Core can break Business.AuthContext.QueryHandlers, while a change to Business.AuthContext.QueryHandlers can't break Core.
- Position
- Below the diagonal: Business.AuthContext.QueryHandlers uses a module listed above it, which is the healthy direction.
13→8 Business.AuthContext.QueryHandlers uses Domain.Repositories✕
- Connections
- 2 pairs of types, where a type in Business.AuthContext.QueryHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.AuthContext.QueryHandlers.GetAllUserAccountsHandler→Cafe.Domain.Repositories.IUserViewRepositoryCafe.Business.AuthContext.QueryHandlers.GetUserHandler→Cafe.Domain.Repositories.IUserViewRepository
- Direction
- Business.AuthContext.QueryHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.AuthContext.QueryHandlers, while a change to Business.AuthContext.QueryHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.AuthContext.QueryHandlers uses a module listed above it, which is the healthy direction.
14→3 Business.BaristaContext.QueryHandlers uses Domain.Views✕
- Connections
- 1 pair of types, where a type in Business.BaristaContext.QueryHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.BaristaContext.QueryHandlers.GetEmployedBaristasHandler→Cafe.Domain.Views.BaristaView
- Direction
- Business.BaristaContext.QueryHandlers uses Domain.Views, so a change to Domain.Views can break Business.BaristaContext.QueryHandlers, while a change to Business.BaristaContext.QueryHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.BaristaContext.QueryHandlers uses a module listed above it, which is the healthy direction.
14→7 Business.BaristaContext.QueryHandlers uses Core✕
- Connections
- 1 pair of types, where a type in Business.BaristaContext.QueryHandlers uses a type in Core.
- The types involved
Cafe.Business.BaristaContext.QueryHandlers.GetEmployedBaristasHandler→Cafe.Core.IQueryHandler
- Direction
- Business.BaristaContext.QueryHandlers uses Core, so a change to Core can break Business.BaristaContext.QueryHandlers, while a change to Business.BaristaContext.QueryHandlers can't break Core.
- Position
- Below the diagonal: Business.BaristaContext.QueryHandlers uses a module listed above it, which is the healthy direction.
14→8 Business.BaristaContext.QueryHandlers uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business.BaristaContext.QueryHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.BaristaContext.QueryHandlers.GetEmployedBaristasHandler→Cafe.Domain.Repositories.IBaristaViewRepository
- Direction
- Business.BaristaContext.QueryHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.BaristaContext.QueryHandlers, while a change to Business.BaristaContext.QueryHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.BaristaContext.QueryHandlers uses a module listed above it, which is the healthy direction.
15→3 Business.CashierContext.QueryHandlers uses Domain.Views✕
- Connections
- 1 pair of types, where a type in Business.CashierContext.QueryHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.CashierContext.QueryHandlers.GetEmployedCashiersHandler→Cafe.Domain.Views.CashierView
- Direction
- Business.CashierContext.QueryHandlers uses Domain.Views, so a change to Domain.Views can break Business.CashierContext.QueryHandlers, while a change to Business.CashierContext.QueryHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.CashierContext.QueryHandlers uses a module listed above it, which is the healthy direction.
15→7 Business.CashierContext.QueryHandlers uses Core✕
- Connections
- 1 pair of types, where a type in Business.CashierContext.QueryHandlers uses a type in Core.
- The types involved
Cafe.Business.CashierContext.QueryHandlers.GetEmployedCashiersHandler→Cafe.Core.IQueryHandler
- Direction
- Business.CashierContext.QueryHandlers uses Core, so a change to Core can break Business.CashierContext.QueryHandlers, while a change to Business.CashierContext.QueryHandlers can't break Core.
- Position
- Below the diagonal: Business.CashierContext.QueryHandlers uses a module listed above it, which is the healthy direction.
15→8 Business.CashierContext.QueryHandlers uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business.CashierContext.QueryHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.CashierContext.QueryHandlers.GetEmployedCashiersHandler→Cafe.Domain.Repositories.ICashierViewRepository
- Direction
- Business.CashierContext.QueryHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.CashierContext.QueryHandlers, while a change to Business.CashierContext.QueryHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.CashierContext.QueryHandlers uses a module listed above it, which is the healthy direction.
16→3 Business.ManagerContext.QueryHandlers uses Domain.Views✕
- Connections
- 1 pair of types, where a type in Business.ManagerContext.QueryHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.ManagerContext.QueryHandlers.GetEmployedManagersHandler→Cafe.Domain.Views.ManagerView
- Direction
- Business.ManagerContext.QueryHandlers uses Domain.Views, so a change to Domain.Views can break Business.ManagerContext.QueryHandlers, while a change to Business.ManagerContext.QueryHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.ManagerContext.QueryHandlers uses a module listed above it, which is the healthy direction.
16→7 Business.ManagerContext.QueryHandlers uses Core✕
- Connections
- 1 pair of types, where a type in Business.ManagerContext.QueryHandlers uses a type in Core.
- The types involved
Cafe.Business.ManagerContext.QueryHandlers.GetEmployedManagersHandler→Cafe.Core.IQueryHandler
- Direction
- Business.ManagerContext.QueryHandlers uses Core, so a change to Core can break Business.ManagerContext.QueryHandlers, while a change to Business.ManagerContext.QueryHandlers can't break Core.
- Position
- Below the diagonal: Business.ManagerContext.QueryHandlers uses a module listed above it, which is the healthy direction.
16→8 Business.ManagerContext.QueryHandlers uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business.ManagerContext.QueryHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.ManagerContext.QueryHandlers.GetEmployedManagersHandler→Cafe.Domain.Repositories.IManagerViewRepository
- Direction
- Business.ManagerContext.QueryHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.ManagerContext.QueryHandlers, while a change to Business.ManagerContext.QueryHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.ManagerContext.QueryHandlers uses a module listed above it, which is the healthy direction.
17→3 Business.MenuContext.QueryHandlers uses Domain.Views✕
- Connections
- 1 pair of types, where a type in Business.MenuContext.QueryHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.MenuContext.QueryHandlers.GetAllMenuItemsHandler→Cafe.Domain.Views.MenuItemView
- Direction
- Business.MenuContext.QueryHandlers uses Domain.Views, so a change to Domain.Views can break Business.MenuContext.QueryHandlers, while a change to Business.MenuContext.QueryHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.MenuContext.QueryHandlers uses a module listed above it, which is the healthy direction.
17→7 Business.MenuContext.QueryHandlers uses Core✕
- Connections
- 1 pair of types, where a type in Business.MenuContext.QueryHandlers uses a type in Core.
- The types involved
Cafe.Business.MenuContext.QueryHandlers.GetAllMenuItemsHandler→Cafe.Core.IQueryHandler
- Direction
- Business.MenuContext.QueryHandlers uses Core, so a change to Core can break Business.MenuContext.QueryHandlers, while a change to Business.MenuContext.QueryHandlers can't break Core.
- Position
- Below the diagonal: Business.MenuContext.QueryHandlers uses a module listed above it, which is the healthy direction.
17→8 Business.MenuContext.QueryHandlers uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business.MenuContext.QueryHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.MenuContext.QueryHandlers.GetAllMenuItemsHandler→Cafe.Domain.Repositories.IMenuItemViewRepository
- Direction
- Business.MenuContext.QueryHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.MenuContext.QueryHandlers, while a change to Business.MenuContext.QueryHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.MenuContext.QueryHandlers uses a module listed above it, which is the healthy direction.
18→2 Business.TabContext.QueryHandlers uses Domain✕
- Connections
- 1 pair of types, where a type in Business.TabContext.QueryHandlers uses a type in Domain.
- The types involved
Cafe.Business.TabContext.QueryHandlers.GetTabViewHandler→Cafe.Domain.Error
- Direction
- Business.TabContext.QueryHandlers uses Domain, so a change to Domain can break Business.TabContext.QueryHandlers, while a change to Business.TabContext.QueryHandlers can't break Domain.
- Position
- Below the diagonal: Business.TabContext.QueryHandlers uses a module listed above it, which is the healthy direction.
18→3 Business.TabContext.QueryHandlers uses Domain.Views✕
- Connections
- 3 pairs of types, where a type in Business.TabContext.QueryHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.TabContext.QueryHandlers.GetAllOpenTabsHandler→Cafe.Domain.Views.TabViewCafe.Business.TabContext.QueryHandlers.GetTabHistoryHandler→Cafe.Domain.Views.TabViewCafe.Business.TabContext.QueryHandlers.GetTabViewHandler→Cafe.Domain.Views.TabView
- Direction
- Business.TabContext.QueryHandlers uses Domain.Views, so a change to Domain.Views can break Business.TabContext.QueryHandlers, while a change to Business.TabContext.QueryHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.TabContext.QueryHandlers uses a module listed above it, which is the healthy direction.
18→7 Business.TabContext.QueryHandlers uses Core✕
- Connections
- 3 pairs of types, where a type in Business.TabContext.QueryHandlers uses a type in Core.
- The types involved
Cafe.Business.TabContext.QueryHandlers.GetAllOpenTabsHandler→Cafe.Core.IQueryHandlerCafe.Business.TabContext.QueryHandlers.GetTabHistoryHandler→Cafe.Core.IQueryHandlerCafe.Business.TabContext.QueryHandlers.GetTabViewHandler→Cafe.Core.IQueryHandler
- Direction
- Business.TabContext.QueryHandlers uses Core, so a change to Core can break Business.TabContext.QueryHandlers, while a change to Business.TabContext.QueryHandlers can't break Core.
- Position
- Below the diagonal: Business.TabContext.QueryHandlers uses a module listed above it, which is the healthy direction.
18→8 Business.TabContext.QueryHandlers uses Domain.Repositories✕
- Connections
- 3 pairs of types, where a type in Business.TabContext.QueryHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.TabContext.QueryHandlers.GetAllOpenTabsHandler→Cafe.Domain.Repositories.ITabViewRepositoryCafe.Business.TabContext.QueryHandlers.GetTabHistoryHandler→Cafe.Domain.Repositories.ITabViewRepositoryCafe.Business.TabContext.QueryHandlers.GetTabViewHandler→Cafe.Domain.Repositories.ITabViewRepository
- Direction
- Business.TabContext.QueryHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.TabContext.QueryHandlers, while a change to Business.TabContext.QueryHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.TabContext.QueryHandlers uses a module listed above it, which is the healthy direction.
19→3 Business.TableContext.QueryHandlers uses Domain.Views✕
- Connections
- 1 pair of types, where a type in Business.TableContext.QueryHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.TableContext.QueryHandlers.GetAllTablesHandler→Cafe.Domain.Views.TableView
- Direction
- Business.TableContext.QueryHandlers uses Domain.Views, so a change to Domain.Views can break Business.TableContext.QueryHandlers, while a change to Business.TableContext.QueryHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.TableContext.QueryHandlers uses a module listed above it, which is the healthy direction.
19→7 Business.TableContext.QueryHandlers uses Core✕
- Connections
- 1 pair of types, where a type in Business.TableContext.QueryHandlers uses a type in Core.
- The types involved
Cafe.Business.TableContext.QueryHandlers.GetAllTablesHandler→Cafe.Core.IQueryHandler
- Direction
- Business.TableContext.QueryHandlers uses Core, so a change to Core can break Business.TableContext.QueryHandlers, while a change to Business.TableContext.QueryHandlers can't break Core.
- Position
- Below the diagonal: Business.TableContext.QueryHandlers uses a module listed above it, which is the healthy direction.
19→8 Business.TableContext.QueryHandlers uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business.TableContext.QueryHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.TableContext.QueryHandlers.GetAllTablesHandler→Cafe.Domain.Repositories.ITableViewRepository
- Direction
- Business.TableContext.QueryHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.TableContext.QueryHandlers, while a change to Business.TableContext.QueryHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.TableContext.QueryHandlers uses a module listed above it, which is the healthy direction.
20→3 Business.WaiterContext.QueryHandlers uses Domain.Views✕
- Connections
- 1 pair of types, where a type in Business.WaiterContext.QueryHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.WaiterContext.QueryHandlers.GetEmployedWaitersHandler→Cafe.Domain.Views.WaiterView
- Direction
- Business.WaiterContext.QueryHandlers uses Domain.Views, so a change to Domain.Views can break Business.WaiterContext.QueryHandlers, while a change to Business.WaiterContext.QueryHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.WaiterContext.QueryHandlers uses a module listed above it, which is the healthy direction.
20→7 Business.WaiterContext.QueryHandlers uses Core✕
- Connections
- 1 pair of types, where a type in Business.WaiterContext.QueryHandlers uses a type in Core.
- The types involved
Cafe.Business.WaiterContext.QueryHandlers.GetEmployedWaitersHandler→Cafe.Core.IQueryHandler
- Direction
- Business.WaiterContext.QueryHandlers uses Core, so a change to Core can break Business.WaiterContext.QueryHandlers, while a change to Business.WaiterContext.QueryHandlers can't break Core.
- Position
- Below the diagonal: Business.WaiterContext.QueryHandlers uses a module listed above it, which is the healthy direction.
20→8 Business.WaiterContext.QueryHandlers uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business.WaiterContext.QueryHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.WaiterContext.QueryHandlers.GetEmployedWaitersHandler→Cafe.Domain.Repositories.IWaiterViewRepository
- Direction
- Business.WaiterContext.QueryHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.WaiterContext.QueryHandlers, while a change to Business.WaiterContext.QueryHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.WaiterContext.QueryHandlers uses a module listed above it, which is the healthy direction.
21→7 Core.AuthContext.Commands uses Core✕
- Connections
- 6 pairs of types, where a type in Core.AuthContext.Commands uses a type in Core.
- The types involved
Cafe.Core.AuthContext.Commands.AssignBaristaToAccount→Cafe.Core.ICommandCafe.Core.AuthContext.Commands.AssignCashierToAccount→Cafe.Core.ICommandCafe.Core.AuthContext.Commands.AssignManagerToAccount→Cafe.Core.ICommandCafe.Core.AuthContext.Commands.AssignWaiterToAccount→Cafe.Core.ICommandCafe.Core.AuthContext.Commands.Login→Cafe.Core.ICommandCafe.Core.AuthContext.Commands.Register→Cafe.Core.ICommand
- Direction
- Core.AuthContext.Commands uses Core, so a change to Core can break Core.AuthContext.Commands, while a change to Core.AuthContext.Commands can't break Core.
- Position
- Below the diagonal: Core.AuthContext.Commands uses a module listed above it, which is the healthy direction.
22→7 Core.BaristaContext.Commands uses Core✕
- Connections
- 1 pair of types, where a type in Core.BaristaContext.Commands uses a type in Core.
- The types involved
Cafe.Core.BaristaContext.Commands.HireBarista→Cafe.Core.ICommand
- Direction
- Core.BaristaContext.Commands uses Core, so a change to Core can break Core.BaristaContext.Commands, while a change to Core.BaristaContext.Commands can't break Core.
- Position
- Below the diagonal: Core.BaristaContext.Commands uses a module listed above it, which is the healthy direction.
23→7 Core.CashierContext.Commands uses Core✕
- Connections
- 1 pair of types, where a type in Core.CashierContext.Commands uses a type in Core.
- The types involved
Cafe.Core.CashierContext.Commands.HireCashier→Cafe.Core.ICommand
- Direction
- Core.CashierContext.Commands uses Core, so a change to Core can break Core.CashierContext.Commands, while a change to Core.CashierContext.Commands can't break Core.
- Position
- Below the diagonal: Core.CashierContext.Commands uses a module listed above it, which is the healthy direction.
24→7 Core.ManagerContext.Commands uses Core✕
- Connections
- 1 pair of types, where a type in Core.ManagerContext.Commands uses a type in Core.
- The types involved
Cafe.Core.ManagerContext.Commands.HireManager→Cafe.Core.ICommand
- Direction
- Core.ManagerContext.Commands uses Core, so a change to Core can break Core.ManagerContext.Commands, while a change to Core.ManagerContext.Commands can't break Core.
- Position
- Below the diagonal: Core.ManagerContext.Commands uses a module listed above it, which is the healthy direction.
25→3 Core.MenuContext.Commands uses Domain.Views✕
- Connections
- 1 pair of types, where a type in Core.MenuContext.Commands uses a type in Domain.Views.
- The types involved
Cafe.Core.MenuContext.Commands.AddMenuItems→Cafe.Domain.Views.MenuItemView
- Direction
- Core.MenuContext.Commands uses Domain.Views, so a change to Domain.Views can break Core.MenuContext.Commands, while a change to Core.MenuContext.Commands can't break Domain.Views.
- Position
- Below the diagonal: Core.MenuContext.Commands uses a module listed above it, which is the healthy direction.
25→7 Core.MenuContext.Commands uses Core✕
- Connections
- 1 pair of types, where a type in Core.MenuContext.Commands uses a type in Core.
- The types involved
Cafe.Core.MenuContext.Commands.AddMenuItems→Cafe.Core.ICommand
- Direction
- Core.MenuContext.Commands uses Core, so a change to Core can break Core.MenuContext.Commands, while a change to Core.MenuContext.Commands can't break Core.
- Position
- Below the diagonal: Core.MenuContext.Commands uses a module listed above it, which is the healthy direction.
26→7 Core.OrderContext.Commands uses Core✕
- Connections
- 3 pairs of types, where a type in Core.OrderContext.Commands uses a type in Core.
- The types involved
Cafe.Core.OrderContext.Commands.CompleteToGoOrder→Cafe.Core.ICommandCafe.Core.OrderContext.Commands.ConfirmToGoOrder→Cafe.Core.ICommandCafe.Core.OrderContext.Commands.OrderToGo→Cafe.Core.ICommand
- Direction
- Core.OrderContext.Commands uses Core, so a change to Core can break Core.OrderContext.Commands, while a change to Core.OrderContext.Commands can't break Core.
- Position
- Below the diagonal: Core.OrderContext.Commands uses a module listed above it, which is the healthy direction.
27→5 Core.OrderContext.Queries uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Core.OrderContext.Queries uses a type in Domain.Entities.
- The types involved
Cafe.Core.OrderContext.Queries.GetOrdersByStatus→Cafe.Domain.Entities.ToGoOrderStatus
- Direction
- Core.OrderContext.Queries uses Domain.Entities, so a change to Domain.Entities can break Core.OrderContext.Queries, while a change to Core.OrderContext.Queries can't break Domain.Entities.
- Position
- Below the diagonal: Core.OrderContext.Queries uses a module listed above it, which is the healthy direction.
27→7 Core.OrderContext.Queries uses Core✕
- Connections
- 3 pairs of types, where a type in Core.OrderContext.Queries uses a type in Core.
- The types involved
Cafe.Core.OrderContext.Queries.GetAllToGoOrders→Cafe.Core.IQueryCafe.Core.OrderContext.Queries.GetOrdersByStatus→Cafe.Core.IQueryCafe.Core.OrderContext.Queries.GetToGoOrder→Cafe.Core.IQuery
- Direction
- Core.OrderContext.Queries uses Core, so a change to Core can break Core.OrderContext.Queries, while a change to Core.OrderContext.Queries can't break Core.
- Position
- Below the diagonal: Core.OrderContext.Queries uses a module listed above it, which is the healthy direction.
28→2 Persistance.Repositories uses Domain✕
- Connections
- 1 pair of types, where a type in Persistance.Repositories uses a type in Domain.
- The types involved
Cafe.Persistance.Repositories.UserRepository→Cafe.Domain.Error
- Direction
- Persistance.Repositories uses Domain, so a change to Domain can break Persistance.Repositories, while a change to Persistance.Repositories can't break Domain.
- Position
- Below the diagonal: Persistance.Repositories uses a module listed above it, which is the healthy direction.
28→3 Persistance.Repositories uses Domain.Views✕
- Connections
- 9 pairs of types, where a type in Persistance.Repositories uses a type in Domain.Views.
- The types involved
Cafe.Persistance.Repositories.BaristaViewRepository→Cafe.Domain.Views.BaristaViewCafe.Persistance.Repositories.CashierViewRepository→Cafe.Domain.Views.CashierViewCafe.Persistance.Repositories.ManagerViewRepository→Cafe.Domain.Views.ManagerViewCafe.Persistance.Repositories.MenuItemViewRepository→Cafe.Domain.Views.MenuItemViewCafe.Persistance.Repositories.TabViewRepository→Cafe.Domain.Views.TabViewCafe.Persistance.Repositories.TableViewRepository→Cafe.Domain.Views.TableViewCafe.Persistance.Repositories.ToGoOrderViewRepository→Cafe.Domain.Views.ToGoOrderViewCafe.Persistance.Repositories.UserViewRepository→Cafe.Domain.Views.UserViewCafe.Persistance.Repositories.WaiterViewRepository→Cafe.Domain.Views.WaiterView
- Direction
- Persistance.Repositories uses Domain.Views, so a change to Domain.Views can break Persistance.Repositories, while a change to Persistance.Repositories can't break Domain.Views.
- Position
- Below the diagonal: Persistance.Repositories uses a module listed above it, which is the healthy direction.
28→5 Persistance.Repositories uses Domain.Entities✕
- Connections
- 11 pairs of types, where a type in Persistance.Repositories uses a type in Domain.Entities.
- The types involved
Cafe.Persistance.Repositories.BaristaRepository→Cafe.Domain.Entities.BaristaCafe.Persistance.Repositories.CashierRepository→Cafe.Domain.Entities.CashierCafe.Persistance.Repositories.ManagerRepository→Cafe.Domain.Entities.ManagerCafe.Persistance.Repositories.MenuItemRepository→Cafe.Domain.Entities.MenuItemCafe.Persistance.Repositories.TabRepository→Cafe.Domain.Entities.TabCafe.Persistance.Repositories.TableRepository→Cafe.Domain.Entities.TableCafe.Persistance.Repositories.ToGoOrderRepository→Cafe.Domain.Entities.ToGoOrderCafe.Persistance.Repositories.ToGoOrderViewRepository→Cafe.Domain.Entities.ToGoOrderCafe.Persistance.Repositories.ToGoOrderViewRepository→Cafe.Domain.Entities.ToGoOrderStatusCafe.Persistance.Repositories.UserRepository→Cafe.Domain.Entities.UserCafe.Persistance.Repositories.WaiterRepository→Cafe.Domain.Entities.Waiter
- Direction
- Persistance.Repositories uses Domain.Entities, so a change to Domain.Entities can break Persistance.Repositories, while a change to Persistance.Repositories can't break Domain.Entities.
- Position
- Below the diagonal: Persistance.Repositories uses a module listed above it, which is the healthy direction.
28→8 Persistance.Repositories uses Domain.Repositories✕
- Connections
- 18 pairs of types, where a type in Persistance.Repositories uses a type in Domain.Repositories.
- The types involved
Cafe.Persistance.Repositories.BaristaRepository→Cafe.Domain.Repositories.IBaristaRepositoryCafe.Persistance.Repositories.BaristaViewRepository→Cafe.Domain.Repositories.IBaristaViewRepositoryCafe.Persistance.Repositories.CashierRepository→Cafe.Domain.Repositories.ICashierRepositoryCafe.Persistance.Repositories.CashierViewRepository→Cafe.Domain.Repositories.ICashierViewRepositoryCafe.Persistance.Repositories.ManagerRepository→Cafe.Domain.Repositories.IManagerRepositoryCafe.Persistance.Repositories.ManagerViewRepository→Cafe.Domain.Repositories.IManagerViewRepositoryCafe.Persistance.Repositories.MenuItemRepository→Cafe.Domain.Repositories.IMenuItemRepositoryCafe.Persistance.Repositories.MenuItemViewRepository→Cafe.Domain.Repositories.IMenuItemViewRepositoryCafe.Persistance.Repositories.TabRepository→Cafe.Domain.Repositories.ITabRepositoryCafe.Persistance.Repositories.TabViewRepository→Cafe.Domain.Repositories.ITabViewRepositoryCafe.Persistance.Repositories.TableRepository→Cafe.Domain.Repositories.ITableRepositoryCafe.Persistance.Repositories.TableViewRepository→Cafe.Domain.Repositories.ITableViewRepositoryCafe.Persistance.Repositories.ToGoOrderRepository→Cafe.Domain.Repositories.IToGoOrderRepositoryCafe.Persistance.Repositories.ToGoOrderViewRepository→Cafe.Domain.Repositories.IToGoOrderViewRepositoryCafe.Persistance.Repositories.UserRepository→Cafe.Domain.Repositories.IUserRepositoryCafe.Persistance.Repositories.UserViewRepository→Cafe.Domain.Repositories.IUserViewRepositoryCafe.Persistance.Repositories.WaiterRepository→Cafe.Domain.Repositories.IWaiterRepositoryCafe.Persistance.Repositories.WaiterViewRepository→Cafe.Domain.Repositories.IWaiterViewRepository
- Direction
- Persistance.Repositories uses Domain.Repositories, so a change to Domain.Repositories can break Persistance.Repositories, while a change to Persistance.Repositories can't break Domain.Repositories.
- Position
- Below the diagonal: Persistance.Repositories uses a module listed above it, which is the healthy direction.
28→9 Persistance.Repositories uses Persistance.EntityFramework✕
- Connections
- 15 pairs of types, where a type in Persistance.Repositories uses a type in Persistance.EntityFramework.
- The types involved
Cafe.Persistance.Repositories.BaristaRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.BaristaViewRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.CashierRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.CashierViewRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.ManagerRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.ManagerViewRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.MenuItemRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.MenuItemViewRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.TableRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.TableViewRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.ToGoOrderRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.ToGoOrderViewRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.UserViewRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.WaiterRepository→Cafe.Persistance.EntityFramework.ApplicationDbContextCafe.Persistance.Repositories.WaiterViewRepository→Cafe.Persistance.EntityFramework.ApplicationDbContext
- Direction
- Persistance.Repositories uses Persistance.EntityFramework, so a change to Persistance.EntityFramework can break Persistance.Repositories, while a change to Persistance.Repositories can't break Persistance.EntityFramework.
- Position
- Below the diagonal: Persistance.Repositories uses a module listed above it, which is the healthy direction.
29→5 Api uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Api uses a type in Domain.Entities.
- The types involved
Cafe.Api.Startup→Cafe.Domain.Entities.User
- Direction
- Api uses Domain.Entities, so a change to Domain.Entities can break Api, while a change to Api can't break Domain.Entities.
- Position
- Below the diagonal: Api uses a module listed above it, which is the healthy direction.
29→9 Api uses Persistance.EntityFramework✕
- Connections
- 1 pair of types, where a type in Api uses a type in Persistance.EntityFramework.
- The types involved
Cafe.Api.Startup→Cafe.Persistance.EntityFramework.ApplicationDbContext
- Direction
- Api uses Persistance.EntityFramework, so a change to Persistance.EntityFramework can break Api, while a change to Api can't break Persistance.EntityFramework.
- Position
- Below the diagonal: Api uses a module listed above it, which is the healthy direction.
29→10 Api uses Api.Configuration✕
- Connections
- 1 pair of types, where a type in Api uses a type in Api.Configuration.
- The types involved
Cafe.Api.Startup→Cafe.Api.Configuration.DatabaseSeeder
- Direction
- Api uses Api.Configuration, so a change to Api.Configuration can break Api, while a change to Api can't break Api.Configuration.
- Position
- Below the diagonal: Api uses a module listed above it, which is the healthy direction.
30→1 Api.Controllers uses Api.Hateoas.Resources✕
- Connections
- 11 pairs of types, where a type in Api.Controllers uses a type in Api.Hateoas.Resources.
- The types involved
Cafe.Api.Controllers.ApiController→Cafe.Api.Hateoas.Resources.IResourceMapperCafe.Api.Controllers.AuthController→Cafe.Api.Hateoas.Resources.IResourceMapperCafe.Api.Controllers.BaristaController→Cafe.Api.Hateoas.Resources.IResourceMapperCafe.Api.Controllers.CashierController→Cafe.Api.Hateoas.Resources.IResourceMapperCafe.Api.Controllers.HomeController→Cafe.Api.Hateoas.Resources.IResourceMapperCafe.Api.Controllers.ManagerController→Cafe.Api.Hateoas.Resources.IResourceMapperCafe.Api.Controllers.MenuController→Cafe.Api.Hateoas.Resources.IResourceMapperCafe.Api.Controllers.OrderController→Cafe.Api.Hateoas.Resources.IResourceMapperCafe.Api.Controllers.TabController→Cafe.Api.Hateoas.Resources.IResourceMapperCafe.Api.Controllers.TableController→Cafe.Api.Hateoas.Resources.IResourceMapperCafe.Api.Controllers.WaiterController→Cafe.Api.Hateoas.Resources.IResourceMapper
- Direction
- Api.Controllers uses Api.Hateoas.Resources, so a change to Api.Hateoas.Resources can break Api.Controllers, while a change to Api.Controllers can't break Api.Hateoas.Resources.
- Position
- Below the diagonal: Api.Controllers uses a module listed above it, which is the healthy direction.
30→2 Api.Controllers uses Domain✕
- Connections
- 1 pair of types, where a type in Api.Controllers uses a type in Domain.
- The types involved
Cafe.Api.Controllers.ApiController→Cafe.Domain.Error
- Direction
- Api.Controllers uses Domain, so a change to Domain can break Api.Controllers, while a change to Api.Controllers can't break Domain.
- Position
- Below the diagonal: Api.Controllers uses a module listed above it, which is the healthy direction.
30→5 Api.Controllers uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Api.Controllers uses a type in Domain.Entities.
- The types involved
Cafe.Api.Controllers.OrderController→Cafe.Domain.Entities.ToGoOrderStatus
- Direction
- Api.Controllers uses Domain.Entities, so a change to Domain.Entities can break Api.Controllers, while a change to Api.Controllers can't break Domain.Entities.
- Position
- Below the diagonal: Api.Controllers uses a module listed above it, which is the healthy direction.
30→7 Api.Controllers uses Core✕
- Connections
- 1 pair of types, where a type in Api.Controllers uses a type in Core.
- The types involved
Cafe.Api.Controllers.ApiController→Cafe.Core.IQuery
- Direction
- Api.Controllers uses Core, so a change to Core can break Api.Controllers, while a change to Api.Controllers can't break Core.
- Position
- Below the diagonal: Api.Controllers uses a module listed above it, which is the healthy direction.
30→21 Api.Controllers uses Core.AuthContext.Commands✕
- Connections
- 6 pairs of types, where a type in Api.Controllers uses a type in Core.AuthContext.Commands.
- The types involved
Cafe.Api.Controllers.AuthController→Cafe.Core.AuthContext.Commands.AssignBaristaToAccountCafe.Api.Controllers.AuthController→Cafe.Core.AuthContext.Commands.AssignCashierToAccountCafe.Api.Controllers.AuthController→Cafe.Core.AuthContext.Commands.AssignManagerToAccountCafe.Api.Controllers.AuthController→Cafe.Core.AuthContext.Commands.AssignWaiterToAccountCafe.Api.Controllers.AuthController→Cafe.Core.AuthContext.Commands.LoginCafe.Api.Controllers.AuthController→Cafe.Core.AuthContext.Commands.Register
- Direction
- Api.Controllers uses Core.AuthContext.Commands, so a change to Core.AuthContext.Commands can break Api.Controllers, while a change to Api.Controllers can't break Core.AuthContext.Commands.
- Position
- Below the diagonal: Api.Controllers uses a module listed above it, which is the healthy direction.
30→22 Api.Controllers uses Core.BaristaContext.Commands✕
- Connections
- 1 pair of types, where a type in Api.Controllers uses a type in Core.BaristaContext.Commands.
- The types involved
Cafe.Api.Controllers.BaristaController→Cafe.Core.BaristaContext.Commands.HireBarista
- Direction
- Api.Controllers uses Core.BaristaContext.Commands, so a change to Core.BaristaContext.Commands can break Api.Controllers, while a change to Api.Controllers can't break Core.BaristaContext.Commands.
- Position
- Below the diagonal: Api.Controllers uses a module listed above it, which is the healthy direction.
30→23 Api.Controllers uses Core.CashierContext.Commands✕
- Connections
- 1 pair of types, where a type in Api.Controllers uses a type in Core.CashierContext.Commands.
- The types involved
Cafe.Api.Controllers.CashierController→Cafe.Core.CashierContext.Commands.HireCashier
- Direction
- Api.Controllers uses Core.CashierContext.Commands, so a change to Core.CashierContext.Commands can break Api.Controllers, while a change to Api.Controllers can't break Core.CashierContext.Commands.
- Position
- Below the diagonal: Api.Controllers uses a module listed above it, which is the healthy direction.
30→24 Api.Controllers uses Core.ManagerContext.Commands✕
- Connections
- 1 pair of types, where a type in Api.Controllers uses a type in Core.ManagerContext.Commands.
- The types involved
Cafe.Api.Controllers.ManagerController→Cafe.Core.ManagerContext.Commands.HireManager
- Direction
- Api.Controllers uses Core.ManagerContext.Commands, so a change to Core.ManagerContext.Commands can break Api.Controllers, while a change to Api.Controllers can't break Core.ManagerContext.Commands.
- Position
- Below the diagonal: Api.Controllers uses a module listed above it, which is the healthy direction.
30→25 Api.Controllers uses Core.MenuContext.Commands✕
- Connections
- 1 pair of types, where a type in Api.Controllers uses a type in Core.MenuContext.Commands.
- The types involved
Cafe.Api.Controllers.MenuController→Cafe.Core.MenuContext.Commands.AddMenuItems
- Direction
- Api.Controllers uses Core.MenuContext.Commands, so a change to Core.MenuContext.Commands can break Api.Controllers, while a change to Api.Controllers can't break Core.MenuContext.Commands.
- Position
- Below the diagonal: Api.Controllers uses a module listed above it, which is the healthy direction.
30→26 Api.Controllers uses Core.OrderContext.Commands✕
- Connections
- 3 pairs of types, where a type in Api.Controllers uses a type in Core.OrderContext.Commands.
- The types involved
Cafe.Api.Controllers.OrderController→Cafe.Core.OrderContext.Commands.CompleteToGoOrderCafe.Api.Controllers.OrderController→Cafe.Core.OrderContext.Commands.ConfirmToGoOrderCafe.Api.Controllers.OrderController→Cafe.Core.OrderContext.Commands.OrderToGo
- Direction
- Api.Controllers uses Core.OrderContext.Commands, so a change to Core.OrderContext.Commands can break Api.Controllers, while a change to Api.Controllers can't break Core.OrderContext.Commands.
- Position
- Below the diagonal: Api.Controllers uses a module listed above it, which is the healthy direction.
31→2 Business.AuthContext.CommandHandlers uses Domain✕
- Connections
- 7 pairs of types, where a type in Business.AuthContext.CommandHandlers uses a type in Domain.
- The types involved
Cafe.Business.AuthContext.CommandHandlers.AssignBaristaToAccountHandler→Cafe.Domain.ErrorCafe.Business.AuthContext.CommandHandlers.AssignCashierToAccountHandler→Cafe.Domain.ErrorCafe.Business.AuthContext.CommandHandlers.AssignManagerToAccountHandler→Cafe.Domain.ErrorCafe.Business.AuthContext.CommandHandlers.AssignWaiterToAccountHandler→Cafe.Domain.ErrorCafe.Business.AuthContext.CommandHandlers.BaseAuthHandler→Cafe.Domain.ErrorCafe.Business.AuthContext.CommandHandlers.LoginHandler→Cafe.Domain.ErrorCafe.Business.AuthContext.CommandHandlers.RegisterHandler→Cafe.Domain.Error
- Direction
- Business.AuthContext.CommandHandlers uses Domain, so a change to Domain can break Business.AuthContext.CommandHandlers, while a change to Business.AuthContext.CommandHandlers can't break Domain.
- Position
- Below the diagonal: Business.AuthContext.CommandHandlers uses a module listed above it, which is the healthy direction.
31→3 Business.AuthContext.CommandHandlers uses Domain.Views✕
- Connections
- 1 pair of types, where a type in Business.AuthContext.CommandHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.AuthContext.CommandHandlers.LoginHandler→Cafe.Domain.Views.JwtView
- Direction
- Business.AuthContext.CommandHandlers uses Domain.Views, so a change to Domain.Views can break Business.AuthContext.CommandHandlers, while a change to Business.AuthContext.CommandHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.AuthContext.CommandHandlers uses a module listed above it, which is the healthy direction.
31→4 Business.AuthContext.CommandHandlers uses Domain.Events✕
- Connections
- 6 pairs of types, where a type in Business.AuthContext.CommandHandlers uses a type in Domain.Events.
- The types involved
Cafe.Business.AuthContext.CommandHandlers.AssignBaristaToAccountHandler→Cafe.Domain.Events.IEventBusCafe.Business.AuthContext.CommandHandlers.AssignCashierToAccountHandler→Cafe.Domain.Events.IEventBusCafe.Business.AuthContext.CommandHandlers.AssignManagerToAccountHandler→Cafe.Domain.Events.IEventBusCafe.Business.AuthContext.CommandHandlers.AssignWaiterToAccountHandler→Cafe.Domain.Events.IEventBusCafe.Business.AuthContext.CommandHandlers.BaseAuthHandler→Cafe.Domain.Events.IEventBusCafe.Business.AuthContext.CommandHandlers.RegisterHandler→Cafe.Domain.Events.IEventBus
- Direction
- Business.AuthContext.CommandHandlers uses Domain.Events, so a change to Domain.Events can break Business.AuthContext.CommandHandlers, while a change to Business.AuthContext.CommandHandlers can't break Domain.Events.
- Position
- Below the diagonal: Business.AuthContext.CommandHandlers uses a module listed above it, which is the healthy direction.
31→5 Business.AuthContext.CommandHandlers uses Domain.Entities✕
- Connections
- 6 pairs of types, where a type in Business.AuthContext.CommandHandlers uses a type in Domain.Entities.
- The types involved
Cafe.Business.AuthContext.CommandHandlers.AssignBaristaToAccountHandler→Cafe.Domain.Entities.BaristaCafe.Business.AuthContext.CommandHandlers.AssignCashierToAccountHandler→Cafe.Domain.Entities.CashierCafe.Business.AuthContext.CommandHandlers.AssignManagerToAccountHandler→Cafe.Domain.Entities.ManagerCafe.Business.AuthContext.CommandHandlers.AssignWaiterToAccountHandler→Cafe.Domain.Entities.WaiterCafe.Business.AuthContext.CommandHandlers.BaseAuthHandler→Cafe.Domain.Entities.UserCafe.Business.AuthContext.CommandHandlers.LoginHandler→Cafe.Domain.Entities.User
- Direction
- Business.AuthContext.CommandHandlers uses Domain.Entities, so a change to Domain.Entities can break Business.AuthContext.CommandHandlers, while a change to Business.AuthContext.CommandHandlers can't break Domain.Entities.
- Position
- Below the diagonal: Business.AuthContext.CommandHandlers uses a module listed above it, which is the healthy direction.
31→7 Business.AuthContext.CommandHandlers uses Core✕
- Connections
- 1 pair of types, where a type in Business.AuthContext.CommandHandlers uses a type in Core.
- The types involved
Cafe.Business.AuthContext.CommandHandlers.LoginHandler→Cafe.Core.ICommandHandler
- Direction
- Business.AuthContext.CommandHandlers uses Core, so a change to Core can break Business.AuthContext.CommandHandlers, while a change to Business.AuthContext.CommandHandlers can't break Core.
- Position
- Below the diagonal: Business.AuthContext.CommandHandlers uses a module listed above it, which is the healthy direction.
31→8 Business.AuthContext.CommandHandlers uses Domain.Repositories✕
- Connections
- 11 pairs of types, where a type in Business.AuthContext.CommandHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.AuthContext.CommandHandlers.AssignBaristaToAccountHandler→Cafe.Domain.Repositories.IBaristaRepositoryCafe.Business.AuthContext.CommandHandlers.AssignBaristaToAccountHandler→Cafe.Domain.Repositories.IUserRepositoryCafe.Business.AuthContext.CommandHandlers.AssignCashierToAccountHandler→Cafe.Domain.Repositories.ICashierRepositoryCafe.Business.AuthContext.CommandHandlers.AssignCashierToAccountHandler→Cafe.Domain.Repositories.IUserRepositoryCafe.Business.AuthContext.CommandHandlers.AssignManagerToAccountHandler→Cafe.Domain.Repositories.IManagerRepositoryCafe.Business.AuthContext.CommandHandlers.AssignManagerToAccountHandler→Cafe.Domain.Repositories.IUserRepositoryCafe.Business.AuthContext.CommandHandlers.AssignWaiterToAccountHandler→Cafe.Domain.Repositories.IUserRepositoryCafe.Business.AuthContext.CommandHandlers.AssignWaiterToAccountHandler→Cafe.Domain.Repositories.IWaiterRepositoryCafe.Business.AuthContext.CommandHandlers.BaseAuthHandler→Cafe.Domain.Repositories.IUserRepositoryCafe.Business.AuthContext.CommandHandlers.LoginHandler→Cafe.Domain.Repositories.IUserRepositoryCafe.Business.AuthContext.CommandHandlers.RegisterHandler→Cafe.Domain.Repositories.IUserRepository
- Direction
- Business.AuthContext.CommandHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.AuthContext.CommandHandlers, while a change to Business.AuthContext.CommandHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.AuthContext.CommandHandlers uses a module listed above it, which is the healthy direction.
31→12 Business.AuthContext.CommandHandlers uses Business✕
- Connections
- 1 pair of types, where a type in Business.AuthContext.CommandHandlers uses a type in Business.
- The types involved
Cafe.Business.AuthContext.CommandHandlers.BaseAuthHandler→Cafe.Business.BaseHandler
- Direction
- Business.AuthContext.CommandHandlers uses Business, so a change to Business can break Business.AuthContext.CommandHandlers, while a change to Business.AuthContext.CommandHandlers can't break Business.
- Position
- Below the diagonal: Business.AuthContext.CommandHandlers uses a module listed above it, which is the healthy direction.
31→21 Business.AuthContext.CommandHandlers uses Core.AuthContext.Commands✕
- Connections
- 6 pairs of types, where a type in Business.AuthContext.CommandHandlers uses a type in Core.AuthContext.Commands.
- The types involved
Cafe.Business.AuthContext.CommandHandlers.AssignBaristaToAccountHandler→Cafe.Core.AuthContext.Commands.AssignBaristaToAccountCafe.Business.AuthContext.CommandHandlers.AssignCashierToAccountHandler→Cafe.Core.AuthContext.Commands.AssignCashierToAccountCafe.Business.AuthContext.CommandHandlers.AssignManagerToAccountHandler→Cafe.Core.AuthContext.Commands.AssignManagerToAccountCafe.Business.AuthContext.CommandHandlers.AssignWaiterToAccountHandler→Cafe.Core.AuthContext.Commands.AssignWaiterToAccountCafe.Business.AuthContext.CommandHandlers.LoginHandler→Cafe.Core.AuthContext.Commands.LoginCafe.Business.AuthContext.CommandHandlers.RegisterHandler→Cafe.Core.AuthContext.Commands.Register
- Direction
- Business.AuthContext.CommandHandlers uses Core.AuthContext.Commands, so a change to Core.AuthContext.Commands can break Business.AuthContext.CommandHandlers, while a change to Business.AuthContext.CommandHandlers can't break Core.AuthContext.Commands.
- Position
- Below the diagonal: Business.AuthContext.CommandHandlers uses a module listed above it, which is the healthy direction.
32→2 Business.BaristaContext.CommandHandlers uses Domain✕
- Connections
- 1 pair of types, where a type in Business.BaristaContext.CommandHandlers uses a type in Domain.
- The types involved
Cafe.Business.BaristaContext.CommandHandlers.HireBaristaHandler→Cafe.Domain.Error
- Direction
- Business.BaristaContext.CommandHandlers uses Domain, so a change to Domain can break Business.BaristaContext.CommandHandlers, while a change to Business.BaristaContext.CommandHandlers can't break Domain.
- Position
- Below the diagonal: Business.BaristaContext.CommandHandlers uses a module listed above it, which is the healthy direction.
32→4 Business.BaristaContext.CommandHandlers uses Domain.Events✕
- Connections
- 1 pair of types, where a type in Business.BaristaContext.CommandHandlers uses a type in Domain.Events.
- The types involved
Cafe.Business.BaristaContext.CommandHandlers.HireBaristaHandler→Cafe.Domain.Events.IEventBus
- Direction
- Business.BaristaContext.CommandHandlers uses Domain.Events, so a change to Domain.Events can break Business.BaristaContext.CommandHandlers, while a change to Business.BaristaContext.CommandHandlers can't break Domain.Events.
- Position
- Below the diagonal: Business.BaristaContext.CommandHandlers uses a module listed above it, which is the healthy direction.
32→5 Business.BaristaContext.CommandHandlers uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Business.BaristaContext.CommandHandlers uses a type in Domain.Entities.
- The types involved
Cafe.Business.BaristaContext.CommandHandlers.HireBaristaHandler→Cafe.Domain.Entities.Barista
- Direction
- Business.BaristaContext.CommandHandlers uses Domain.Entities, so a change to Domain.Entities can break Business.BaristaContext.CommandHandlers, while a change to Business.BaristaContext.CommandHandlers can't break Domain.Entities.
- Position
- Below the diagonal: Business.BaristaContext.CommandHandlers uses a module listed above it, which is the healthy direction.
32→8 Business.BaristaContext.CommandHandlers uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business.BaristaContext.CommandHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.BaristaContext.CommandHandlers.HireBaristaHandler→Cafe.Domain.Repositories.IBaristaRepository
- Direction
- Business.BaristaContext.CommandHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.BaristaContext.CommandHandlers, while a change to Business.BaristaContext.CommandHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.BaristaContext.CommandHandlers uses a module listed above it, which is the healthy direction.
32→12 Business.BaristaContext.CommandHandlers uses Business✕
- Connections
- 1 pair of types, where a type in Business.BaristaContext.CommandHandlers uses a type in Business.
- The types involved
Cafe.Business.BaristaContext.CommandHandlers.HireBaristaHandler→Cafe.Business.BaseHandler
- Direction
- Business.BaristaContext.CommandHandlers uses Business, so a change to Business can break Business.BaristaContext.CommandHandlers, while a change to Business.BaristaContext.CommandHandlers can't break Business.
- Position
- Below the diagonal: Business.BaristaContext.CommandHandlers uses a module listed above it, which is the healthy direction.
32→22 Business.BaristaContext.CommandHandlers uses Core.BaristaContext.Commands✕
- Connections
- 1 pair of types, where a type in Business.BaristaContext.CommandHandlers uses a type in Core.BaristaContext.Commands.
- The types involved
Cafe.Business.BaristaContext.CommandHandlers.HireBaristaHandler→Cafe.Core.BaristaContext.Commands.HireBarista
- Direction
- Business.BaristaContext.CommandHandlers uses Core.BaristaContext.Commands, so a change to Core.BaristaContext.Commands can break Business.BaristaContext.CommandHandlers, while a change to Business.BaristaContext.CommandHandlers can't break Core.BaristaContext.Commands.
- Position
- Below the diagonal: Business.BaristaContext.CommandHandlers uses a module listed above it, which is the healthy direction.
33→2 Business.CashierContext.CommandHandlers uses Domain✕
- Connections
- 1 pair of types, where a type in Business.CashierContext.CommandHandlers uses a type in Domain.
- The types involved
Cafe.Business.CashierContext.CommandHandlers.HireCashierHandler→Cafe.Domain.Error
- Direction
- Business.CashierContext.CommandHandlers uses Domain, so a change to Domain can break Business.CashierContext.CommandHandlers, while a change to Business.CashierContext.CommandHandlers can't break Domain.
- Position
- Below the diagonal: Business.CashierContext.CommandHandlers uses a module listed above it, which is the healthy direction.
33→4 Business.CashierContext.CommandHandlers uses Domain.Events✕
- Connections
- 1 pair of types, where a type in Business.CashierContext.CommandHandlers uses a type in Domain.Events.
- The types involved
Cafe.Business.CashierContext.CommandHandlers.HireCashierHandler→Cafe.Domain.Events.IEventBus
- Direction
- Business.CashierContext.CommandHandlers uses Domain.Events, so a change to Domain.Events can break Business.CashierContext.CommandHandlers, while a change to Business.CashierContext.CommandHandlers can't break Domain.Events.
- Position
- Below the diagonal: Business.CashierContext.CommandHandlers uses a module listed above it, which is the healthy direction.
33→8 Business.CashierContext.CommandHandlers uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business.CashierContext.CommandHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.CashierContext.CommandHandlers.HireCashierHandler→Cafe.Domain.Repositories.ICashierRepository
- Direction
- Business.CashierContext.CommandHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.CashierContext.CommandHandlers, while a change to Business.CashierContext.CommandHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.CashierContext.CommandHandlers uses a module listed above it, which is the healthy direction.
33→12 Business.CashierContext.CommandHandlers uses Business✕
- Connections
- 1 pair of types, where a type in Business.CashierContext.CommandHandlers uses a type in Business.
- The types involved
Cafe.Business.CashierContext.CommandHandlers.HireCashierHandler→Cafe.Business.BaseHandler
- Direction
- Business.CashierContext.CommandHandlers uses Business, so a change to Business can break Business.CashierContext.CommandHandlers, while a change to Business.CashierContext.CommandHandlers can't break Business.
- Position
- Below the diagonal: Business.CashierContext.CommandHandlers uses a module listed above it, which is the healthy direction.
33→23 Business.CashierContext.CommandHandlers uses Core.CashierContext.Commands✕
- Connections
- 1 pair of types, where a type in Business.CashierContext.CommandHandlers uses a type in Core.CashierContext.Commands.
- The types involved
Cafe.Business.CashierContext.CommandHandlers.HireCashierHandler→Cafe.Core.CashierContext.Commands.HireCashier
- Direction
- Business.CashierContext.CommandHandlers uses Core.CashierContext.Commands, so a change to Core.CashierContext.Commands can break Business.CashierContext.CommandHandlers, while a change to Business.CashierContext.CommandHandlers can't break Core.CashierContext.Commands.
- Position
- Below the diagonal: Business.CashierContext.CommandHandlers uses a module listed above it, which is the healthy direction.
34→2 Business.ManagerContext.CommandHandlers uses Domain✕
- Connections
- 1 pair of types, where a type in Business.ManagerContext.CommandHandlers uses a type in Domain.
- The types involved
Cafe.Business.ManagerContext.CommandHandlers.HireManagerHandler→Cafe.Domain.Error
- Direction
- Business.ManagerContext.CommandHandlers uses Domain, so a change to Domain can break Business.ManagerContext.CommandHandlers, while a change to Business.ManagerContext.CommandHandlers can't break Domain.
- Position
- Below the diagonal: Business.ManagerContext.CommandHandlers uses a module listed above it, which is the healthy direction.
34→4 Business.ManagerContext.CommandHandlers uses Domain.Events✕
- Connections
- 1 pair of types, where a type in Business.ManagerContext.CommandHandlers uses a type in Domain.Events.
- The types involved
Cafe.Business.ManagerContext.CommandHandlers.HireManagerHandler→Cafe.Domain.Events.IEventBus
- Direction
- Business.ManagerContext.CommandHandlers uses Domain.Events, so a change to Domain.Events can break Business.ManagerContext.CommandHandlers, while a change to Business.ManagerContext.CommandHandlers can't break Domain.Events.
- Position
- Below the diagonal: Business.ManagerContext.CommandHandlers uses a module listed above it, which is the healthy direction.
34→8 Business.ManagerContext.CommandHandlers uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business.ManagerContext.CommandHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.ManagerContext.CommandHandlers.HireManagerHandler→Cafe.Domain.Repositories.IManagerRepository
- Direction
- Business.ManagerContext.CommandHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.ManagerContext.CommandHandlers, while a change to Business.ManagerContext.CommandHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.ManagerContext.CommandHandlers uses a module listed above it, which is the healthy direction.
34→12 Business.ManagerContext.CommandHandlers uses Business✕
- Connections
- 1 pair of types, where a type in Business.ManagerContext.CommandHandlers uses a type in Business.
- The types involved
Cafe.Business.ManagerContext.CommandHandlers.HireManagerHandler→Cafe.Business.BaseHandler
- Direction
- Business.ManagerContext.CommandHandlers uses Business, so a change to Business can break Business.ManagerContext.CommandHandlers, while a change to Business.ManagerContext.CommandHandlers can't break Business.
- Position
- Below the diagonal: Business.ManagerContext.CommandHandlers uses a module listed above it, which is the healthy direction.
34→24 Business.ManagerContext.CommandHandlers uses Core.ManagerContext.Commands✕
- Connections
- 1 pair of types, where a type in Business.ManagerContext.CommandHandlers uses a type in Core.ManagerContext.Commands.
- The types involved
Cafe.Business.ManagerContext.CommandHandlers.HireManagerHandler→Cafe.Core.ManagerContext.Commands.HireManager
- Direction
- Business.ManagerContext.CommandHandlers uses Core.ManagerContext.Commands, so a change to Core.ManagerContext.Commands can break Business.ManagerContext.CommandHandlers, while a change to Business.ManagerContext.CommandHandlers can't break Core.ManagerContext.Commands.
- Position
- Below the diagonal: Business.ManagerContext.CommandHandlers uses a module listed above it, which is the healthy direction.
35→2 Business.MenuContext.CommandHandlers uses Domain✕
- Connections
- 1 pair of types, where a type in Business.MenuContext.CommandHandlers uses a type in Domain.
- The types involved
Cafe.Business.MenuContext.CommandHandlers.AddMenuItemsHandler→Cafe.Domain.Error
- Direction
- Business.MenuContext.CommandHandlers uses Domain, so a change to Domain can break Business.MenuContext.CommandHandlers, while a change to Business.MenuContext.CommandHandlers can't break Domain.
- Position
- Below the diagonal: Business.MenuContext.CommandHandlers uses a module listed above it, which is the healthy direction.
35→3 Business.MenuContext.CommandHandlers uses Domain.Views✕
- Connections
- 1 pair of types, where a type in Business.MenuContext.CommandHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.MenuContext.CommandHandlers.AddMenuItemsHandler→Cafe.Domain.Views.MenuItemView
- Direction
- Business.MenuContext.CommandHandlers uses Domain.Views, so a change to Domain.Views can break Business.MenuContext.CommandHandlers, while a change to Business.MenuContext.CommandHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.MenuContext.CommandHandlers uses a module listed above it, which is the healthy direction.
35→4 Business.MenuContext.CommandHandlers uses Domain.Events✕
- Connections
- 1 pair of types, where a type in Business.MenuContext.CommandHandlers uses a type in Domain.Events.
- The types involved
Cafe.Business.MenuContext.CommandHandlers.AddMenuItemsHandler→Cafe.Domain.Events.IEventBus
- Direction
- Business.MenuContext.CommandHandlers uses Domain.Events, so a change to Domain.Events can break Business.MenuContext.CommandHandlers, while a change to Business.MenuContext.CommandHandlers can't break Domain.Events.
- Position
- Below the diagonal: Business.MenuContext.CommandHandlers uses a module listed above it, which is the healthy direction.
35→8 Business.MenuContext.CommandHandlers uses Domain.Repositories✕
- Connections
- 1 pair of types, where a type in Business.MenuContext.CommandHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.MenuContext.CommandHandlers.AddMenuItemsHandler→Cafe.Domain.Repositories.IMenuItemRepository
- Direction
- Business.MenuContext.CommandHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.MenuContext.CommandHandlers, while a change to Business.MenuContext.CommandHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.MenuContext.CommandHandlers uses a module listed above it, which is the healthy direction.
35→12 Business.MenuContext.CommandHandlers uses Business✕
- Connections
- 1 pair of types, where a type in Business.MenuContext.CommandHandlers uses a type in Business.
- The types involved
Cafe.Business.MenuContext.CommandHandlers.AddMenuItemsHandler→Cafe.Business.BaseHandler
- Direction
- Business.MenuContext.CommandHandlers uses Business, so a change to Business can break Business.MenuContext.CommandHandlers, while a change to Business.MenuContext.CommandHandlers can't break Business.
- Position
- Below the diagonal: Business.MenuContext.CommandHandlers uses a module listed above it, which is the healthy direction.
35→25 Business.MenuContext.CommandHandlers uses Core.MenuContext.Commands✕
- Connections
- 1 pair of types, where a type in Business.MenuContext.CommandHandlers uses a type in Core.MenuContext.Commands.
- The types involved
Cafe.Business.MenuContext.CommandHandlers.AddMenuItemsHandler→Cafe.Core.MenuContext.Commands.AddMenuItems
- Direction
- Business.MenuContext.CommandHandlers uses Core.MenuContext.Commands, so a change to Core.MenuContext.Commands can break Business.MenuContext.CommandHandlers, while a change to Business.MenuContext.CommandHandlers can't break Core.MenuContext.Commands.
- Position
- Below the diagonal: Business.MenuContext.CommandHandlers uses a module listed above it, which is the healthy direction.
36→2 Business.OrderContext.CommandHandlers uses Domain✕
- Connections
- 4 pairs of types, where a type in Business.OrderContext.CommandHandlers uses a type in Domain.
- The types involved
Cafe.Business.OrderContext.CommandHandlers.BaseOrderHandler→Cafe.Domain.ErrorCafe.Business.OrderContext.CommandHandlers.CompleteToGoOrderHandler→Cafe.Domain.ErrorCafe.Business.OrderContext.CommandHandlers.ConfirmToGoOrderHandler→Cafe.Domain.ErrorCafe.Business.OrderContext.CommandHandlers.OrderToGoHandler→Cafe.Domain.Error
- Direction
- Business.OrderContext.CommandHandlers uses Domain, so a change to Domain can break Business.OrderContext.CommandHandlers, while a change to Business.OrderContext.CommandHandlers can't break Domain.
- Position
- Below the diagonal: Business.OrderContext.CommandHandlers uses a module listed above it, which is the healthy direction.
36→4 Business.OrderContext.CommandHandlers uses Domain.Events✕
- Connections
- 4 pairs of types, where a type in Business.OrderContext.CommandHandlers uses a type in Domain.Events.
- The types involved
Cafe.Business.OrderContext.CommandHandlers.BaseOrderHandler→Cafe.Domain.Events.IEventBusCafe.Business.OrderContext.CommandHandlers.CompleteToGoOrderHandler→Cafe.Domain.Events.IEventBusCafe.Business.OrderContext.CommandHandlers.ConfirmToGoOrderHandler→Cafe.Domain.Events.IEventBusCafe.Business.OrderContext.CommandHandlers.OrderToGoHandler→Cafe.Domain.Events.IEventBus
- Direction
- Business.OrderContext.CommandHandlers uses Domain.Events, so a change to Domain.Events can break Business.OrderContext.CommandHandlers, while a change to Business.OrderContext.CommandHandlers can't break Domain.Events.
- Position
- Below the diagonal: Business.OrderContext.CommandHandlers uses a module listed above it, which is the healthy direction.
36→5 Business.OrderContext.CommandHandlers uses Domain.Entities✕
- Connections
- 6 pairs of types, where a type in Business.OrderContext.CommandHandlers uses a type in Domain.Entities.
- The types involved
Cafe.Business.OrderContext.CommandHandlers.BaseOrderHandler→Cafe.Domain.Entities.ToGoOrderCafe.Business.OrderContext.CommandHandlers.BaseOrderHandler→Cafe.Domain.Entities.ToGoOrderStatusCafe.Business.OrderContext.CommandHandlers.CompleteToGoOrderHandler→Cafe.Domain.Entities.ToGoOrderCafe.Business.OrderContext.CommandHandlers.ConfirmToGoOrderHandler→Cafe.Domain.Entities.MenuItemCafe.Business.OrderContext.CommandHandlers.OrderToGoHandler→Cafe.Domain.Entities.MenuItemCafe.Business.OrderContext.CommandHandlers.OrderToGoHandler→Cafe.Domain.Entities.ToGoOrder
- Direction
- Business.OrderContext.CommandHandlers uses Domain.Entities, so a change to Domain.Entities can break Business.OrderContext.CommandHandlers, while a change to Business.OrderContext.CommandHandlers can't break Domain.Entities.
- Position
- Below the diagonal: Business.OrderContext.CommandHandlers uses a module listed above it, which is the healthy direction.
36→7 Business.OrderContext.CommandHandlers uses Core✕
- Connections
- 1 pair of types, where a type in Business.OrderContext.CommandHandlers uses a type in Core.
- The types involved
Cafe.Business.OrderContext.CommandHandlers.OrderToGoHandler→Cafe.Core.IMenuItemsService
- Direction
- Business.OrderContext.CommandHandlers uses Core, so a change to Core can break Business.OrderContext.CommandHandlers, while a change to Business.OrderContext.CommandHandlers can't break Core.
- Position
- Below the diagonal: Business.OrderContext.CommandHandlers uses a module listed above it, which is the healthy direction.
36→8 Business.OrderContext.CommandHandlers uses Domain.Repositories✕
- Connections
- 5 pairs of types, where a type in Business.OrderContext.CommandHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.OrderContext.CommandHandlers.BaseOrderHandler→Cafe.Domain.Repositories.IToGoOrderRepositoryCafe.Business.OrderContext.CommandHandlers.CompleteToGoOrderHandler→Cafe.Domain.Repositories.IBaristaRepositoryCafe.Business.OrderContext.CommandHandlers.CompleteToGoOrderHandler→Cafe.Domain.Repositories.IToGoOrderRepositoryCafe.Business.OrderContext.CommandHandlers.ConfirmToGoOrderHandler→Cafe.Domain.Repositories.IToGoOrderRepositoryCafe.Business.OrderContext.CommandHandlers.OrderToGoHandler→Cafe.Domain.Repositories.IToGoOrderRepository
- Direction
- Business.OrderContext.CommandHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.OrderContext.CommandHandlers, while a change to Business.OrderContext.CommandHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.OrderContext.CommandHandlers uses a module listed above it, which is the healthy direction.
36→12 Business.OrderContext.CommandHandlers uses Business✕
- Connections
- 2 pairs of types, where a type in Business.OrderContext.CommandHandlers uses a type in Business.
- The types involved
Cafe.Business.OrderContext.CommandHandlers.BaseOrderHandler→Cafe.Business.BaseHandlerCafe.Business.OrderContext.CommandHandlers.OrderToGoHandler→Cafe.Business.BaseHandler
- Direction
- Business.OrderContext.CommandHandlers uses Business, so a change to Business can break Business.OrderContext.CommandHandlers, while a change to Business.OrderContext.CommandHandlers can't break Business.
- Position
- Below the diagonal: Business.OrderContext.CommandHandlers uses a module listed above it, which is the healthy direction.
36→26 Business.OrderContext.CommandHandlers uses Core.OrderContext.Commands✕
- Connections
- 3 pairs of types, where a type in Business.OrderContext.CommandHandlers uses a type in Core.OrderContext.Commands.
- The types involved
Cafe.Business.OrderContext.CommandHandlers.CompleteToGoOrderHandler→Cafe.Core.OrderContext.Commands.CompleteToGoOrderCafe.Business.OrderContext.CommandHandlers.ConfirmToGoOrderHandler→Cafe.Core.OrderContext.Commands.ConfirmToGoOrderCafe.Business.OrderContext.CommandHandlers.OrderToGoHandler→Cafe.Core.OrderContext.Commands.OrderToGo
- Direction
- Business.OrderContext.CommandHandlers uses Core.OrderContext.Commands, so a change to Core.OrderContext.Commands can break Business.OrderContext.CommandHandlers, while a change to Business.OrderContext.CommandHandlers can't break Core.OrderContext.Commands.
- Position
- Below the diagonal: Business.OrderContext.CommandHandlers uses a module listed above it, which is the healthy direction.
37→2 Business.OrderContext.QueryHandlers uses Domain✕
- Connections
- 1 pair of types, where a type in Business.OrderContext.QueryHandlers uses a type in Domain.
- The types involved
Cafe.Business.OrderContext.QueryHandlers.GetToGoOrderHandler→Cafe.Domain.Error
- Direction
- Business.OrderContext.QueryHandlers uses Domain, so a change to Domain can break Business.OrderContext.QueryHandlers, while a change to Business.OrderContext.QueryHandlers can't break Domain.
- Position
- Below the diagonal: Business.OrderContext.QueryHandlers uses a module listed above it, which is the healthy direction.
37→3 Business.OrderContext.QueryHandlers uses Domain.Views✕
- Connections
- 3 pairs of types, where a type in Business.OrderContext.QueryHandlers uses a type in Domain.Views.
- The types involved
Cafe.Business.OrderContext.QueryHandlers.GetAllToGoOrdersHandler→Cafe.Domain.Views.ToGoOrderViewCafe.Business.OrderContext.QueryHandlers.GetOrdersByStatusHandler→Cafe.Domain.Views.ToGoOrderViewCafe.Business.OrderContext.QueryHandlers.GetToGoOrderHandler→Cafe.Domain.Views.ToGoOrderView
- Direction
- Business.OrderContext.QueryHandlers uses Domain.Views, so a change to Domain.Views can break Business.OrderContext.QueryHandlers, while a change to Business.OrderContext.QueryHandlers can't break Domain.Views.
- Position
- Below the diagonal: Business.OrderContext.QueryHandlers uses a module listed above it, which is the healthy direction.
37→7 Business.OrderContext.QueryHandlers uses Core✕
- Connections
- 3 pairs of types, where a type in Business.OrderContext.QueryHandlers uses a type in Core.
- The types involved
Cafe.Business.OrderContext.QueryHandlers.GetAllToGoOrdersHandler→Cafe.Core.IQueryHandlerCafe.Business.OrderContext.QueryHandlers.GetOrdersByStatusHandler→Cafe.Core.IQueryHandlerCafe.Business.OrderContext.QueryHandlers.GetToGoOrderHandler→Cafe.Core.IQueryHandler
- Direction
- Business.OrderContext.QueryHandlers uses Core, so a change to Core can break Business.OrderContext.QueryHandlers, while a change to Business.OrderContext.QueryHandlers can't break Core.
- Position
- Below the diagonal: Business.OrderContext.QueryHandlers uses a module listed above it, which is the healthy direction.
37→8 Business.OrderContext.QueryHandlers uses Domain.Repositories✕
- Connections
- 3 pairs of types, where a type in Business.OrderContext.QueryHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.OrderContext.QueryHandlers.GetAllToGoOrdersHandler→Cafe.Domain.Repositories.IToGoOrderViewRepositoryCafe.Business.OrderContext.QueryHandlers.GetOrdersByStatusHandler→Cafe.Domain.Repositories.IToGoOrderViewRepositoryCafe.Business.OrderContext.QueryHandlers.GetToGoOrderHandler→Cafe.Domain.Repositories.IToGoOrderViewRepository
- Direction
- Business.OrderContext.QueryHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.OrderContext.QueryHandlers, while a change to Business.OrderContext.QueryHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.OrderContext.QueryHandlers uses a module listed above it, which is the healthy direction.
37→27 Business.OrderContext.QueryHandlers uses Core.OrderContext.Queries✕
- Connections
- 3 pairs of types, where a type in Business.OrderContext.QueryHandlers uses a type in Core.OrderContext.Queries.
- The types involved
Cafe.Business.OrderContext.QueryHandlers.GetAllToGoOrdersHandler→Cafe.Core.OrderContext.Queries.GetAllToGoOrdersCafe.Business.OrderContext.QueryHandlers.GetOrdersByStatusHandler→Cafe.Core.OrderContext.Queries.GetOrdersByStatusCafe.Business.OrderContext.QueryHandlers.GetToGoOrderHandler→Cafe.Core.OrderContext.Queries.GetToGoOrder
- Direction
- Business.OrderContext.QueryHandlers uses Core.OrderContext.Queries, so a change to Core.OrderContext.Queries can break Business.OrderContext.QueryHandlers, while a change to Business.OrderContext.QueryHandlers can't break Core.OrderContext.Queries.
- Position
- Below the diagonal: Business.OrderContext.QueryHandlers uses a module listed above it, which is the healthy direction.
38→2 Business.TabContext.CommandHandlers uses Domain✕
- Connections
- 6 pairs of types, where a type in Business.TabContext.CommandHandlers uses a type in Domain.
- The types involved
Cafe.Business.TabContext.CommandHandlers.BaseTabHandler→Cafe.Domain.ErrorCafe.Business.TabContext.CommandHandlers.CloseTabHandler→Cafe.Domain.ErrorCafe.Business.TabContext.CommandHandlers.OpenTabHandler→Cafe.Domain.ErrorCafe.Business.TabContext.CommandHandlers.OrderMenuItemsHandler→Cafe.Domain.ErrorCafe.Business.TabContext.CommandHandlers.RejectMenuItemsHandler→Cafe.Domain.ErrorCafe.Business.TabContext.CommandHandlers.ServeMenuItemsHandler→Cafe.Domain.Error
- Direction
- Business.TabContext.CommandHandlers uses Domain, so a change to Domain can break Business.TabContext.CommandHandlers, while a change to Business.TabContext.CommandHandlers can't break Domain.
- Position
- Below the diagonal: Business.TabContext.CommandHandlers uses a module listed above it, which is the healthy direction.
38→4 Business.TabContext.CommandHandlers uses Domain.Events✕
- Connections
- 6 pairs of types, where a type in Business.TabContext.CommandHandlers uses a type in Domain.Events.
- The types involved
Cafe.Business.TabContext.CommandHandlers.BaseTabHandler→Cafe.Domain.Events.IEventBusCafe.Business.TabContext.CommandHandlers.CloseTabHandler→Cafe.Domain.Events.IEventBusCafe.Business.TabContext.CommandHandlers.OpenTabHandler→Cafe.Domain.Events.IEventBusCafe.Business.TabContext.CommandHandlers.OrderMenuItemsHandler→Cafe.Domain.Events.IEventBusCafe.Business.TabContext.CommandHandlers.RejectMenuItemsHandler→Cafe.Domain.Events.IEventBusCafe.Business.TabContext.CommandHandlers.ServeMenuItemsHandler→Cafe.Domain.Events.IEventBus
- Direction
- Business.TabContext.CommandHandlers uses Domain.Events, so a change to Domain.Events can break Business.TabContext.CommandHandlers, while a change to Business.TabContext.CommandHandlers can't break Domain.Events.
- Position
- Below the diagonal: Business.TabContext.CommandHandlers uses a module listed above it, which is the healthy direction.
38→5 Business.TabContext.CommandHandlers uses Domain.Entities✕
- Connections
- 4 pairs of types, where a type in Business.TabContext.CommandHandlers uses a type in Domain.Entities.
- The types involved
Cafe.Business.TabContext.CommandHandlers.BaseTabHandler→Cafe.Domain.Entities.MenuItemCafe.Business.TabContext.CommandHandlers.BaseTabHandler→Cafe.Domain.Entities.TabCafe.Business.TabContext.CommandHandlers.OpenTabHandler→Cafe.Domain.Entities.WaiterCafe.Business.TabContext.CommandHandlers.RejectMenuItemsHandler→Cafe.Domain.Entities.Tab
- Direction
- Business.TabContext.CommandHandlers uses Domain.Entities, so a change to Domain.Entities can break Business.TabContext.CommandHandlers, while a change to Business.TabContext.CommandHandlers can't break Domain.Entities.
- Position
- Below the diagonal: Business.TabContext.CommandHandlers uses a module listed above it, which is the healthy direction.
38→7 Business.TabContext.CommandHandlers uses Core✕
- Connections
- 6 pairs of types, where a type in Business.TabContext.CommandHandlers uses a type in Core.
- The types involved
Cafe.Business.TabContext.CommandHandlers.BaseTabHandler→Cafe.Core.IMenuItemsServiceCafe.Business.TabContext.CommandHandlers.CloseTabHandler→Cafe.Core.IMenuItemsServiceCafe.Business.TabContext.CommandHandlers.OpenTabHandler→Cafe.Core.IMenuItemsServiceCafe.Business.TabContext.CommandHandlers.OrderMenuItemsHandler→Cafe.Core.IMenuItemsServiceCafe.Business.TabContext.CommandHandlers.RejectMenuItemsHandler→Cafe.Core.IMenuItemsServiceCafe.Business.TabContext.CommandHandlers.ServeMenuItemsHandler→Cafe.Core.IMenuItemsService
- Direction
- Business.TabContext.CommandHandlers uses Core, so a change to Core can break Business.TabContext.CommandHandlers, while a change to Business.TabContext.CommandHandlers can't break Core.
- Position
- Below the diagonal: Business.TabContext.CommandHandlers uses a module listed above it, which is the healthy direction.
38→8 Business.TabContext.CommandHandlers uses Domain.Repositories✕
- Connections
- 8 pairs of types, where a type in Business.TabContext.CommandHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.TabContext.CommandHandlers.BaseTabHandler→Cafe.Domain.Repositories.ITabRepositoryCafe.Business.TabContext.CommandHandlers.CloseTabHandler→Cafe.Domain.Repositories.ITabRepositoryCafe.Business.TabContext.CommandHandlers.OpenTabHandler→Cafe.Domain.Repositories.ITabRepositoryCafe.Business.TabContext.CommandHandlers.OpenTabHandler→Cafe.Domain.Repositories.ITabViewRepositoryCafe.Business.TabContext.CommandHandlers.OpenTabHandler→Cafe.Domain.Repositories.ITableRepositoryCafe.Business.TabContext.CommandHandlers.OrderMenuItemsHandler→Cafe.Domain.Repositories.ITabRepositoryCafe.Business.TabContext.CommandHandlers.RejectMenuItemsHandler→Cafe.Domain.Repositories.ITabRepositoryCafe.Business.TabContext.CommandHandlers.ServeMenuItemsHandler→Cafe.Domain.Repositories.ITabRepository
- Direction
- Business.TabContext.CommandHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.TabContext.CommandHandlers, while a change to Business.TabContext.CommandHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.TabContext.CommandHandlers uses a module listed above it, which is the healthy direction.
38→12 Business.TabContext.CommandHandlers uses Business✕
- Connections
- 1 pair of types, where a type in Business.TabContext.CommandHandlers uses a type in Business.
- The types involved
Cafe.Business.TabContext.CommandHandlers.BaseTabHandler→Cafe.Business.BaseHandler
- Direction
- Business.TabContext.CommandHandlers uses Business, so a change to Business can break Business.TabContext.CommandHandlers, while a change to Business.TabContext.CommandHandlers can't break Business.
- Position
- Below the diagonal: Business.TabContext.CommandHandlers uses a module listed above it, which is the healthy direction.
39→2 Business.TableContext.CommandHandlers uses Domain✕
- Connections
- 4 pairs of types, where a type in Business.TableContext.CommandHandlers uses a type in Domain.
- The types involved
Cafe.Business.TableContext.CommandHandlers.AddTableHandler→Cafe.Domain.ErrorCafe.Business.TableContext.CommandHandlers.BaseTableHandler→Cafe.Domain.ErrorCafe.Business.TableContext.CommandHandlers.CallWaiterHandler→Cafe.Domain.ErrorCafe.Business.TableContext.CommandHandlers.RequestBillHandler→Cafe.Domain.Error
- Direction
- Business.TableContext.CommandHandlers uses Domain, so a change to Domain can break Business.TableContext.CommandHandlers, while a change to Business.TableContext.CommandHandlers can't break Domain.
- Position
- Below the diagonal: Business.TableContext.CommandHandlers uses a module listed above it, which is the healthy direction.
39→4 Business.TableContext.CommandHandlers uses Domain.Events✕
- Connections
- 4 pairs of types, where a type in Business.TableContext.CommandHandlers uses a type in Domain.Events.
- The types involved
Cafe.Business.TableContext.CommandHandlers.AddTableHandler→Cafe.Domain.Events.IEventBusCafe.Business.TableContext.CommandHandlers.BaseTableHandler→Cafe.Domain.Events.IEventBusCafe.Business.TableContext.CommandHandlers.CallWaiterHandler→Cafe.Domain.Events.IEventBusCafe.Business.TableContext.CommandHandlers.RequestBillHandler→Cafe.Domain.Events.IEventBus
- Direction
- Business.TableContext.CommandHandlers uses Domain.Events, so a change to Domain.Events can break Business.TableContext.CommandHandlers, while a change to Business.TableContext.CommandHandlers can't break Domain.Events.
- Position
- Below the diagonal: Business.TableContext.CommandHandlers uses a module listed above it, which is the healthy direction.
39→5 Business.TableContext.CommandHandlers uses Domain.Entities✕
- Connections
- 3 pairs of types, where a type in Business.TableContext.CommandHandlers uses a type in Domain.Entities.
- The types involved
Cafe.Business.TableContext.CommandHandlers.AddTableHandler→Cafe.Domain.Entities.TableCafe.Business.TableContext.CommandHandlers.BaseTableHandler→Cafe.Domain.Entities.TableCafe.Business.TableContext.CommandHandlers.BaseTableHandler→Cafe.Domain.Entities.Waiter
- Direction
- Business.TableContext.CommandHandlers uses Domain.Entities, so a change to Domain.Entities can break Business.TableContext.CommandHandlers, while a change to Business.TableContext.CommandHandlers can't break Domain.Entities.
- Position
- Below the diagonal: Business.TableContext.CommandHandlers uses a module listed above it, which is the healthy direction.
39→8 Business.TableContext.CommandHandlers uses Domain.Repositories✕
- Connections
- 4 pairs of types, where a type in Business.TableContext.CommandHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.TableContext.CommandHandlers.AddTableHandler→Cafe.Domain.Repositories.ITableRepositoryCafe.Business.TableContext.CommandHandlers.BaseTableHandler→Cafe.Domain.Repositories.ITableRepositoryCafe.Business.TableContext.CommandHandlers.CallWaiterHandler→Cafe.Domain.Repositories.ITableRepositoryCafe.Business.TableContext.CommandHandlers.RequestBillHandler→Cafe.Domain.Repositories.ITableRepository
- Direction
- Business.TableContext.CommandHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.TableContext.CommandHandlers, while a change to Business.TableContext.CommandHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.TableContext.CommandHandlers uses a module listed above it, which is the healthy direction.
39→12 Business.TableContext.CommandHandlers uses Business✕
- Connections
- 1 pair of types, where a type in Business.TableContext.CommandHandlers uses a type in Business.
- The types involved
Cafe.Business.TableContext.CommandHandlers.BaseTableHandler→Cafe.Business.BaseHandler
- Direction
- Business.TableContext.CommandHandlers uses Business, so a change to Business can break Business.TableContext.CommandHandlers, while a change to Business.TableContext.CommandHandlers can't break Business.
- Position
- Below the diagonal: Business.TableContext.CommandHandlers uses a module listed above it, which is the healthy direction.
40→2 Business.WaiterContext.CommandHandlers uses Domain✕
- Connections
- 2 pairs of types, where a type in Business.WaiterContext.CommandHandlers uses a type in Domain.
- The types involved
Cafe.Business.WaiterContext.CommandHandlers.AssignTableHandler→Cafe.Domain.ErrorCafe.Business.WaiterContext.CommandHandlers.HireWaiterHandler→Cafe.Domain.Error
- Direction
- Business.WaiterContext.CommandHandlers uses Domain, so a change to Domain can break Business.WaiterContext.CommandHandlers, while a change to Business.WaiterContext.CommandHandlers can't break Domain.
- Position
- Below the diagonal: Business.WaiterContext.CommandHandlers uses a module listed above it, which is the healthy direction.
40→4 Business.WaiterContext.CommandHandlers uses Domain.Events✕
- Connections
- 2 pairs of types, where a type in Business.WaiterContext.CommandHandlers uses a type in Domain.Events.
- The types involved
Cafe.Business.WaiterContext.CommandHandlers.AssignTableHandler→Cafe.Domain.Events.IEventBusCafe.Business.WaiterContext.CommandHandlers.HireWaiterHandler→Cafe.Domain.Events.IEventBus
- Direction
- Business.WaiterContext.CommandHandlers uses Domain.Events, so a change to Domain.Events can break Business.WaiterContext.CommandHandlers, while a change to Business.WaiterContext.CommandHandlers can't break Domain.Events.
- Position
- Below the diagonal: Business.WaiterContext.CommandHandlers uses a module listed above it, which is the healthy direction.
40→5 Business.WaiterContext.CommandHandlers uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Business.WaiterContext.CommandHandlers uses a type in Domain.Entities.
- The types involved
Cafe.Business.WaiterContext.CommandHandlers.AssignTableHandler→Cafe.Domain.Entities.TableCafe.Business.WaiterContext.CommandHandlers.AssignTableHandler→Cafe.Domain.Entities.Waiter
- Direction
- Business.WaiterContext.CommandHandlers uses Domain.Entities, so a change to Domain.Entities can break Business.WaiterContext.CommandHandlers, while a change to Business.WaiterContext.CommandHandlers can't break Domain.Entities.
- Position
- Below the diagonal: Business.WaiterContext.CommandHandlers uses a module listed above it, which is the healthy direction.
40→8 Business.WaiterContext.CommandHandlers uses Domain.Repositories✕
- Connections
- 3 pairs of types, where a type in Business.WaiterContext.CommandHandlers uses a type in Domain.Repositories.
- The types involved
Cafe.Business.WaiterContext.CommandHandlers.AssignTableHandler→Cafe.Domain.Repositories.ITableRepositoryCafe.Business.WaiterContext.CommandHandlers.AssignTableHandler→Cafe.Domain.Repositories.IWaiterRepositoryCafe.Business.WaiterContext.CommandHandlers.HireWaiterHandler→Cafe.Domain.Repositories.IWaiterRepository
- Direction
- Business.WaiterContext.CommandHandlers uses Domain.Repositories, so a change to Domain.Repositories can break Business.WaiterContext.CommandHandlers, while a change to Business.WaiterContext.CommandHandlers can't break Domain.Repositories.
- Position
- Below the diagonal: Business.WaiterContext.CommandHandlers uses a module listed above it, which is the healthy direction.
40→12 Business.WaiterContext.CommandHandlers uses Business✕
- Connections
- 2 pairs of types, where a type in Business.WaiterContext.CommandHandlers uses a type in Business.
- The types involved
Cafe.Business.WaiterContext.CommandHandlers.AssignTableHandler→Cafe.Business.BaseHandlerCafe.Business.WaiterContext.CommandHandlers.HireWaiterHandler→Cafe.Business.BaseHandler
- Direction
- Business.WaiterContext.CommandHandlers uses Business, so a change to Business can break Business.WaiterContext.CommandHandlers, while a change to Business.WaiterContext.CommandHandlers can't break Business.
- Position
- Below the diagonal: Business.WaiterContext.CommandHandlers 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 — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 169 | High / Critical |
| A05:2025 — Injection | 7 | Medium |
| A02:2025 — Security Misconfiguration | 7 | High / Critical |
| A08:2025 — Software or Data Integrity Failures | 2 | Medium |
Roadmap
Top priorities: Add tests that import the unreached modules (directly or through their public entry); Add a SAST step to CI running 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 — so a security regression fails the build instead of landing; Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, DatabaseSeeder.cs, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add tests that import the unreached modules (directly or through their public entry). | +4.2 pts | Medium | Test Coverage |
| Add a SAST step to CI running 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 — so a security regression fails the build instead of landing. | +4.2 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.9 pts | Low | ADR Quality |
| Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, DatabaseSeeder.cs, REDACTED. | +2.0 pts | Medium | Knowledge Freshness |
| 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. | +1.8 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.9 pts | Low | Knowledge Freshness |
| Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists. | +1.6 pts | Medium | CI/CD gates |
| Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly. | +1.6 pts | Medium | Schema migrations |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.3 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| server/src/server/Cafe.Api/Hateoas/Resources/Auth/UserResource.cs | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| server/tests/Cafe.Tests/Api/Controllers/MenuControllerTests.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| server/src/server/Cafe.Api/Controllers/OrderController.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| server/src/server/Cafe.Domain/Views/UserView.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| server/src/server/Cafe.Persistance/Repositories/UserViewRepository.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| server/src/server/Cafe.Business/AuthContext/CommandHandlers/LoginHandler.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| server/src/server/Cafe.Domain/Entities/Tab.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 96 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 — 96 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, 312 of 335 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, commit the Cobertura/OpenCover/lcov report your CI already produces and real coverage will be read. You can widen what we reach: optional: commit the Cobertura/OpenCover/lcov report your CI already produces, and the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 178 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D14 License Compliance — 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 repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 328 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'REDACTED' with message: Package 'Microsoft.AspNet.SignalR.Core 2.4.1' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.….
- 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `server/src/server/Cafe.Api/appsettings.Development.json`, `server/src/server/Cafe.Api/appsettings.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- 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 REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:18 -------------------- 16 | RUN cat appsettings.json 17 | 18 | >>> FROM microsoft/dotnet:2.2-sdk AS build 19 | 20 | WORKDIR /server -------------------- ERROR: failed to solve: microsoft/dotnet:2.2-sdk: failed to resolve source metadata for docker.io/microsoft/dotnet:2.2-sdk: docker.io/microsoft/dotnet:2.2-sdk: not found; runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- ES3 PII in the event store — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X2 Cancellation propagation — 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. 51 further occurrence(s) are not listed individually; the score already reflects all 91.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with ManageTabPage.js, ManageUserPage.js. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
4 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with HireCashierValidator.cs, RejectMenuItemsValidator.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (23 lines × 2) finding(s) in Code Duplication — start with TabResource.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with UserResource.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
6 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 29 classes have LCOM4 above 3.
D9 · Test Distribution
178 test methods: 178 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 2 mock references across 178 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 266 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 40 direct `PackageReference`(s), and 212 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
14 deducted debt markers + unmeasured dead symbols across 6648 LoC in the .NET projects (0.7/KLoC) → score 8.6. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with MenuControllerTests.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 9 TodoComment finding(s) in Explicit Debt — start with OrderController.cs, UserResource.cs, UserView.cs. — One of this dimension's main actionable groups (9 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
6 projects, 386 source files, 12462 hand-written lines of code (6648 production / 5814 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), 12 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 2 document(s) read across 7 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 60 judged comments only repeat the code they sit on (0.0 %). 1 comment(s) in another language or script were not judged.
D26 · Project Cohesion
1 of 6 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
86 % of calls cross a namespace and 11 % 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)
7 finding(s): 0 critical, 0 high, 7 medium, 0 low. semgrep hit a parse error in 1 file(s) — `codecov.yml` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
169 finding(s): 34 critical, 85 high, 39 medium, 11 low.
What to do
- Resolve the 84 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (67), REDACTED (8), REDACTED (6). — One of this dimension's main actionable groups (84 issue-level).
- Resolve the 33 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (30), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (33 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
7 finding(s): 0 critical, 2 high, 4 medium, 1 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
13 of 13 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 13 of the 316 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 13 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, DatabaseSeeder.cs, REDACTED. — One of this dimension's main actionable groups (13 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 Malicious package finding(s) in Malicious Dependencies — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 6 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 2 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX3 · Project dependency cycles
- The namespaces Cafe.Domain.Entities ↔ Cafe.Domain.Events ↔ Cafe.Domain.Views depend on each other. The lightest dependency in the cycle is Cafe.Domain.Events → Cafe.Domain.Views (Cafe.Domain.Events.OrderConfirmed → Cafe.Domain.Views.ToGoOrderView, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — server/src/server/Cafe.Domain/Events/OrderConfirmed.cs:1
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
- Access here is not default-deny: `AuthController.GetCurrentUser` declares no authorization while 6 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:28
- Access here is not default-deny: `AuthController.Login` declares no authorization while 6 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:43
- Access here is not default-deny: `AuthController.Register` declares no authorization while 6 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:75
- Access here is not default-deny: `HomeController.ApiHome` is in a controller that declares no authorization (on itself, a base controller or any action) while 6 sibling controllers do, and no fallback policy, global AuthorizeFilter or gated MapControllers covers it. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:23
- Access here is not default-deny: `TableController.GetAllTables` declares no authorization while 3 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:26
What to do
- Put every endpoint behind the guard its siblings carry — [Authorize(Policy = …)] on the action or its controller, RequireAuthorization on the route or its group, or a fallback policy with explicit [AllowAnonymous] opt-outs — so the open surface is only what is public on purpose.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `Tab` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — server/src/server/Cafe.Domain/Entities/Tab.cs:8
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `Tab` exposes publicly writable state (Id, CustomerName, WaiterName, IsOpen, ServedItemsValue, TableNumber, and 2 more). — server/src/server/Cafe.Domain/Entities/Tab.cs:8
- `MenuItem` exposes publicly writable state (Id, Number, Description, Price). — server/src/server/Cafe.Domain/Entities/MenuItem.cs:5
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
- `User` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — server/src/server/Cafe.Domain/Entities/User.cs:6
- `IUserRepository` (domain layer) names `User` from `Cafe.Domain.Entities` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×6) — server/src/server/Cafe.Domain/Repositories/IUserRepository.cs:13, server/src/server/Cafe.Domain/Repositories/IUserRepository.cs:15, server/src/server/Cafe.Domain/Repositories/IUserRepository.cs:17, …
- `TabViewProjection` (domain layer) names `ViewProjection` from `Marten.Events.Projections` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — server/src/server/Cafe.Domain/Views/TabViewProjection.cs:7
- The domain project `Cafe.Domain` references `Marten` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — REDACTED:14
- The domain project `Cafe.Domain` references `Microsoft.AspNetCore.Identity.EntityFrameworkCore` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — REDACTED:16
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM7 · Repository granularity
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED4 · Outbox / dual-write
ES1 · Fold determinism
ES2 · Immutable events
- This persisted event exposes settable or mutable-collection member(s) (TabId, CustomerName, WaiterName, TableNumber) — an event is an immutable historical fact. A public setter, or a List/array/dictionary behind an init-only member, lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields, and IReadOnlyList<T>/ImmutableArray<T> for collections. — server/src/server/Cafe.Domain/Events/TabOpened.cs:5
- This persisted event exposes settable or mutable-collection member(s) (TabId, AmountPaid, TipValue, OrderValue, WaiterName, TableNumber) — an event is an immutable historical fact. A public setter, or a List/array/dictionary behind an init-only member, lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields, and IReadOnlyList<T>/ImmutableArray<T> for collections. — server/src/server/Cafe.Domain/Events/TabClosed.cs:5
- This persisted event exposes settable or mutable-collection member(s) (TabId, MenuItems) — an event is an immutable historical fact. A public setter, or a List/array/dictionary behind an init-only member, lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields, and IReadOnlyList<T>/ImmutableArray<T> for collections. (×3) — server/src/server/Cafe.Domain/Events/MenuItemsOrdered.cs:7, server/src/server/Cafe.Domain/Events/MenuItemsServed.cs:7, server/src/server/Cafe.Domain/Events/MenuItemsRejected.cs:7
What to do
- Make every event type immutable: records with init-only properties, or classes with readonly fields set only in the constructor.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `README.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.
What to do
- Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 195 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:24
What to do
- Add a SAST step to CI running 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 — 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.
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P8 · Schema migrations
- `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely. — server/src/server/Cafe.Api/Startup.cs:95
What to do
- Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly.
PF3 · Async & latency hygiene
- 2 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — server/src/server/Cafe.Api/Startup.cs:100, server/src/server/Cafe.Api/Startup.cs:101
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
R1 · Type Safety
- 0 typed · 80 plain JS — the untyped files are client/src/api/apiClient.js, client/src/api/authService.js, client/src/api/baristaService.js, client/src/api/cashierService.js, client/src/api/managerService.js, client/src/api/menuItemsService.js (+74 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- 9 duplicated blocks under client/src/components/ have copies in at least two of the sibling directories admin, auth, barista, cashier, manager, waiter — 3 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — client/src/components/cashier/ToGoOrderForm.js:5
- client/src/components/common/FiniteSelectableMenu.js:4 · client/src/components/common/SelectableMenuDisplay.js:4 — the two spans are one implementation copied and then locally edited — 472 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — client/src/components/common/FiniteSelectableMenu.js:4
- client/src/components/admin/ManageUserPage.js:85 · client/src/components/admin/ManageUserPage.js:116 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — client/src/components/admin/ManageUserPage.js:85
- client/src/components/barista/WaitingOrdersList.js:11 · client/src/components/cashier/PendingOrdersList.js:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — client/src/components/barista/WaitingOrdersList.js:11
- client/src/components/manager/ManagerPage.js:18 · client/src/components/waiter/WaiterPage.js:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — client/src/components/manager/ManagerPage.js:18
- client/src/components/manager/AssignWaiterToTableForm.js:22 · client/src/components/waiter/OpenTabForm.js:22 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — client/src/components/manager/AssignWaiterToTableForm.js:22
- client/src/components/manager/ManagerPage.js:41 · client/src/components/manager/ManagerPage.js:51 · client/src/components/manager/ManagerPage.js:61 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — client/src/components/manager/ManagerPage.js:41
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- Header has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — client/src/components/common/Header.js:6
R3 · Large Files
R4 · Test Coverage
- 0% of 79 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
- Nothing imports this binding — it is safe to review for removal. (×9) — client/src/redux/actions/actionTypes.js:1, client/src/redux/actions/actionTypes.js:3, client/src/redux/actions/actionTypes.js:4, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — client/src/history.js:1
- Declared in client/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- 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. (×2) — server/src/server/Cafe.Api/Program.cs:16, server/src/server/Cafe.Api/Program.cs:33
- A cookie (`Cookies.Append`) carries who is signed in, and it is set without HttpOnly, Secure, SameSite. Without HttpOnly any script on the page can read it, so a single cross-site-scripting bug lets an attacker copy the cookie and act as that user. Without Secure the browser also sends it over plain http://, where anyone on the same network can read it. Without SameSite other websites can make the browser send it along with requests they trigger (cross-site request forgery). (−1.5 on this card.) — REDACTED:129
What to do
- 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.
- Lock down every session and sign-in cookie: `new CookieOptions { HttpOnly = true, Secure = true, SameSite = SameSiteMode.Lax }` on `Response.Cookies.Append`, leave `Cookie.HttpOnly` on and set `Cookie.SecurePolicy = CookieSecurePolicy.Always` in `AddCookie`/`AddSession`, or force both for every cookie with `app.UseCookiePolicy(new CookiePolicyOptions { HttpOnly = HttpOnlyPolicy.Always, Secure = CookieSecurePolicy.Always })`.
X1 · Async correctness
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×2) — server/src/server/Cafe.Api/Startup.cs:100, server/src/server/Cafe.Api/Startup.cs:101
What to do
- Sync-over-async (deadlock risk)
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
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 3/93 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. (×39) — server/src/server/Cafe.Api/Configuration/DatabaseSeeder.cs:143, server/src/server/Cafe.Api/Configuration/DatabaseSeeder.cs:165, server/src/server/Cafe.Api/Configuration/DatabaseSeeder.cs:190, …
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 | 56% | Adequate — gated by R1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 85% | Strong | Solid. |
| Maturity | 50% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 24% | Critical — gated by R4, R6, P1, P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 58% | Adequate — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 64% | Adequate — gated by DM4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Event Sourcing | 53% | Adequate — gated by ES2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 70% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- 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 — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data (event-sourced storage — lifecycle is stream archival / event TTL, not row CASCADE) — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- 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 — 44 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
- AX2 Stateful singletons — no singleton implementations detected
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:18 -------------------- 16 | RUN cat appsettings.json 17 | 18 | >>> FROM microsoft/dotnet:2.2-sdk AS build 19 | 20 | WORKDIR /server -------------------- ERROR: failed to solve: microsoft/dotnet:2.2-sdk: failed to resolve source metadata for docker.io/microsoft/dotnet:2.2-sdk: docker.io/microsoft/dotnet:2.2-sdk: not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D11 Test Reliability — Test runner surfaced no tests
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, html not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (6,648 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 (server), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — analyzer environment
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED3 Event naming — no domain or integration events detected — event-naming check not applicable
- ED5 Idempotency — not scored — 10 of 16 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES3 PII in the event store — This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- 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 — 143 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Domain depends on infrastructure: User server/src/server/Cafe.Domain/Entities/User.cs:6
- Domain depends on infrastructure: IUserRepository server/src/server/Cafe.Domain/Repositories/IUserRepository.cs:13
- Domain depends on infrastructure: IUserRepository server/src/server/Cafe.Domain/Repositories/IUserRepository.cs:15
- Domain depends on infrastructure: IUserRepository server/src/server/Cafe.Domain/Repositories/IUserRepository.cs:17
- Domain depends on infrastructure: IUserRepository server/src/server/Cafe.Domain/Repositories/IUserRepository.cs:19
- Domain depends on infrastructure: IUserRepository server/src/server/Cafe.Domain/Repositories/IUserRepository.cs:21
- Domain depends on infrastructure: IUserRepository server/src/server/Cafe.Domain/Repositories/IUserRepository.cs:23
- Domain depends on infrastructure: TabViewProjection server/src/server/Cafe.Domain/Views/TabViewProjection.cs:7
- Domain depends on infrastructure: Cafe.Domain REDACTED:14
- Domain depends on infrastructure: Cafe.Domain REDACTED:16
- Mutable event: TabOpened server/src/server/Cafe.Domain/Events/TabOpened.cs:5
- Mutable event: TabClosed server/src/server/Cafe.Domain/Events/TabClosed.cs:5
- Mutable event: MenuItemsOrdered server/src/server/Cafe.Domain/Events/MenuItemsOrdered.cs:7
- Mutable event: MenuItemsServed server/src/server/Cafe.Domain/Events/MenuItemsServed.cs:7
- Mutable event: MenuItemsRejected server/src/server/Cafe.Domain/Events/MenuItemsRejected.cs:7
- NoWarnInCsproj REDACTED:7
- NoWarnInCsproj REDACTED:7
- NoWarnInCsproj REDACTED:7
- NoWarnInCsproj REDACTED:7
- REDACTED
- REDACTED
- Namespace dependency cycle server/src/server/Cafe.Domain/Events/OrderConfirmed.cs:1
- WriteOnlyPrivateField server/tests/Cafe.Tests/Api/Controllers/MenuControllerTests.cs:21
- REDACTED
- REDACTED
- Unlisted import 'history' client/src/history.js:1
Serious — 134 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Async method without CancellationToken: SeedDatabase server/src/server/Cafe.Api/Configuration/DatabaseSeeder.cs:143
- Async method without CancellationToken: AssignWaitersToTables server/src/server/Cafe.Api/Configuration/DatabaseSeeder.cs:165
- Async method without CancellationToken: RegisterAccount server/src/server/Cafe.Api/Configuration/DatabaseSeeder.cs:190
- Async method without CancellationToken: GetCurrentUser REDACTED:28
- Async method without CancellationToken: Login REDACTED:43
- Async method without CancellationToken: Register REDACTED:75
- Async method without CancellationToken: GetAllUserAccounts REDACTED:85
- Async method without CancellationToken: AssignWaiterToAccount REDACTED:93
- Async method without CancellationToken: AssignManagerToAccount REDACTED:103
- Async method without CancellationToken: AssignCashierToAccount REDACTED:113
- Async method without CancellationToken: AssignBaristaToAccount REDACTED:123
- Async method without CancellationToken: HireBarista server/src/server/Cafe.Api/Controllers/BaristaController.cs:27
- Async method without CancellationToken: GetEmployedBaristas server/src/server/Cafe.Api/Controllers/BaristaController.cs:36
- Async method without CancellationToken: GetEmployedCashiers server/src/server/Cafe.Api/Controllers/CashierController.cs:27
- Async method without CancellationToken: HireCashier server/src/server/Cafe.Api/Controllers/CashierController.cs:35
- Async method without CancellationToken: GetEmployedManagers server/src/server/Cafe.Api/Controllers/ManagerController.cs:27
- Async method without CancellationToken: HireManager server/src/server/Cafe.Api/Controllers/ManagerController.cs:34
- Async method without CancellationToken: GetMenuItems REDACTED:26
- Async method without CancellationToken: AddMenuItems REDACTED:35
- Async method without CancellationToken: GetOrder server/src/server/Cafe.Api/Controllers/OrderController.cs:31
- Async method without CancellationToken: GetAllOrders server/src/server/Cafe.Api/Controllers/OrderController.cs:41
- Async method without CancellationToken: OrderToGo server/src/server/Cafe.Api/Controllers/OrderController.cs:56
- Async method without CancellationToken: ConfirmToGoOrder server/src/server/Cafe.Api/Controllers/OrderController.cs:66
- Async method without CancellationToken: CompleteToGoOrder server/src/server/Cafe.Api/Controllers/OrderController.cs:76
- Async method without CancellationToken: CloseTab server/src/server/Cafe.Api/Controllers/TabController.cs:28
- TodoComment server/src/server/Cafe.Api/Controllers/OrderController.cs:43
- TodoComment server/src/server/Cafe.Api/Hateoas/Resources/Auth/UserResource.cs:12
- TodoComment server/src/server/Cafe.Domain/Views/UserView.cs:12
- TodoComment server/src/server/Cafe.Persistance/Repositories/UserViewRepository.cs:73
- TodoComment server/src/server/Cafe.Business/AuthContext/CommandHandlers/LoginHandler.cs:65
- TodoComment server/src/server/Cafe.Domain/Entities/Tab.cs:119
- TodoComment server/src/server/Cafe.Domain/Views/TabView.cs:86
- TodoComment server/tests/Cafe.Tests/Api/Hubs/TableActionsHubTests.cs:13
- TodoComment server/tests/Cafe.Tests/Business/AuthContext/LoginHandlerTests.cs:39
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Sync-over-async blocking
- Sync-over-async blocking server/src/server/Cafe.Api/Startup.cs:100
- Sync-over-async blocking server/src/server/Cafe.Api/Startup.cs:101
- FunctionTooLong: ManageTabPage.ManageTabPage client/src/components/waiter/ManageTabPage.js:13
- FunctionTooLong: ManageUserPage.ManageUserPage client/src/components/admin/ManageUserPage.js:14
- Duplicated block (5 lines × 2) server/src/server/Cafe.Core/CashierContext/Commands/HireCashierValidator.cs:8
- Duplicated block (5 lines × 2) server/src/server/Cafe.Core/TabContext/Commands/RejectMenuItemsValidator.cs:8
- REDACTED
- REDACTED
- End-of-life runtime: .NET netcoreapp2.2 REDACTED:4
- End-of-life runtime: .NET netcoreapp2.2 REDACTED:4
- Sync-over-async (deadlock risk) server/src/server/Cafe.Api/Startup.cs:100
- Sync-over-async (deadlock risk) server/src/server/Cafe.Api/Startup.cs:101
- No data-protection/encryption
- REDACTED
- Duplicated block (23 lines × 2) server/src/server/Cafe.Api/Hateoas/Resources/Tab/TabResource.cs:9
- Duplicated block (10 lines × 2) server/src/server/Cafe.Api/Hateoas/Resources/Auth/UserResource.cs:7
- Anemic entity: Tab server/src/server/Cafe.Domain/Entities/Tab.cs:8
- CI pipeline targets a decommissioned service
- Coverage collected but not gated
- Schema created with EnsureCreated() (no migration path) server/src/server/Cafe.Api/Startup.cs:95
- Type Safety
- Duplication concentrated across 6 sibling directories (9 clone groups) client/src/components/cashier/ToGoOrderForm.js:5
- Duplicated block with local edits (82 matched lines × 2 locations) client/src/components/common/FiniteSelectableMenu.js:4
- Duplicated block (29 lines × 2 locations) client/src/components/admin/ManageUserPage.js:85
- Duplicated block (19 lines × 2 locations) client/src/components/barista/WaitingOrdersList.js:11
- Duplicated block (17 lines × 2 locations) client/src/components/manager/ManagerPage.js:18
- Duplicated block (15 lines × 2 locations) client/src/components/manager/AssignWaiterToTableForm.js:22
- Duplicated block (8 lines × 3 locations) client/src/components/manager/ManagerPage.js:41
- Complex function Header (cyclomatic 13, cognitive 11) client/src/components/common/Header.js:6
- Test Coverage
- No lint or typecheck script
- Unused dependency '@khanacademy/react-multi-select'
- Unused dependency '@opuscapita/react-signalr'
- Unused dependency 'i'
- Secure cookie flags not detected REDACTED:129
- NuGet dependencies are not locked
Minor — 54 finding(s)
- Orphaned file REDACTED:1
- Orphaned file server/src/server/Cafe.Api/Configuration/DatabaseSeeder.cs:1
- Orphaned file REDACTED:1
- Orphaned file server/src/server/Cafe.Api/Startup.cs:1
- Orphaned file server/src/server/Cafe.Domain/Entities/Tab.cs:1
- Orphaned file server/src/server/Cafe.Api/Controllers/TabController.cs:1
- Orphaned file server/src/server/Cafe.Persistance/Repositories/UserViewRepository.cs:1
- Orphaned file server/src/server/Cafe.Api/Controllers/_Base/ApiController.cs:1
- Orphaned file server/src/server/Cafe.Api/Controllers/OrderController.cs:1
- Orphaned file server/src/server/Cafe.Domain/Views/TabView.cs:1
- Orphaned file server/src/server/Cafe.Business/AuthContext/CommandHandlers/LoginHandler.cs:1
- Orphaned file server/src/server/Cafe.Api/Hateoas/LinkNames.cs:1
- Orphaned file server/src/server/Cafe.Business/TabContext/CommandHandlers/OpenTabHandler.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Endpoints outside the guard REDACTED:28
- Endpoints outside the guard REDACTED:43
- Endpoints outside the guard REDACTED:75
- Endpoints outside the guard REDACTED:23
- Endpoints outside the guard REDACTED:26
- No security response headers detected
- No security response headers detected server/src/server/Cafe.Api/Program.cs:16
- No security response headers detected server/src/server/Cafe.Api/Program.cs:33
- Mutable entity: Tab server/src/server/Cafe.Domain/Entities/Tab.cs:8
- Mutable entity: MenuItem server/src/server/Cafe.Domain/Entities/MenuItem.cs:5
- No ADRs found
- Projects may be oversized for their cohesion REDACTED:1
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation REDACTED:24
- No rollback/health safety
- Unused export 'LOGIN_REQUEST_SUCCESS' client/src/redux/actions/actionTypes.js:1
- Unused export 'LOAD_USERS' client/src/redux/actions/actionTypes.js:3
- Unused export 'LOAD_WAITERS' client/src/redux/actions/actionTypes.js:4
- Unused export 'LOAD_MENU_ITEMS' client/src/redux/actions/actionTypes.js:6
- Unused export 'LOAD_MANAGERS' client/src/redux/actions/actionTypes.js:8
- Unused export 'LOAD_CASHIERS' client/src/redux/actions/actionTypes.js:10
- Unused export 'LOAD_BARISTAS' client/src/redux/actions/actionTypes.js:12
- Unused export 'LOAD_TABLES' client/src/redux/actions/actionTypes.js:13
- Unused export 'LOAD_ORDERS' client/src/redux/actions/actionTypes.js:19
- Not all async methods take a CancellationToken
Minor — 4 finding(s)
- Mock framework: Moq
- Mock framework: FakeItEasy
- doc comments repeat the names REDACTED:33
- doc comments repeat the names server/tests/Cafe.Tests/Extensions/MoqExtensions.cs:15
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-16382d9364b147abbb7f8387c29cfec8/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-16382d9364b147abbb7f8387c29cfec8/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 . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list server/Cafe.sln package --vulnerable --include-transitive --format json | 169 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 7 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 2 | artifacts/raw/trivy-fs.json |
Appendix C — Personal-data map
Name — 8 field(s)
- UserResource.FirstName server/src/server/Cafe.Api/Hateoas/Resources/Auth/UserResource.cs:9
- UserResource.LastName server/src/server/Cafe.Api/Hateoas/Resources/Auth/UserResource.cs:10
- Register.FirstName server/src/server/Cafe.Core/AuthContext/Commands/Register.cs:9
- Register.LastName server/src/server/Cafe.Core/AuthContext/Commands/Register.cs:11
- User.FirstName server/src/server/Cafe.Domain/Entities/User.cs:8
- User.LastName server/src/server/Cafe.Domain/Entities/User.cs:10
- UserView.FirstName server/src/server/Cafe.Domain/Views/UserView.cs:9
- UserView.LastName server/src/server/Cafe.Domain/Views/UserView.cs:10
Email — 4 field(s)
- UserResource.Email server/src/server/Cafe.Api/Hateoas/Resources/Auth/UserResource.cs:8
- Login.Email server/src/server/Cafe.Core/AuthContext/Commands/Login.cs:7
- Register.Email server/src/server/Cafe.Core/AuthContext/Commands/Register.cs:13
- UserView.Email server/src/server/Cafe.Domain/Views/UserView.cs:8