Executive summary
amasen02/freshcart-backend falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 65 out of 100 and is rated Adequate, and 109 of its 129 critical findings are security problems.
Accessibility, at 60, is the weakest lens and counts most in the score. The best first step is automating accessibility checks, worth about 4 points. Fixing focus, motion and contrast comes next, worth about 3 points. Raising Accessibility to 70 would lift the score to about 68.
Forty-four passwords or keys in the code and two in the code's history are open to anyone who can read the repository. Twenty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and twenty-three settings leave the servers or containers unsafe. Replacing each exposed password or key, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Passing outside input through environment variables would fix the five pipeline steps that put outside input straight into a shell command, and limiting each secret to its own step would deal with the four secrets exposed to more of the pipeline than needed. 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 25,543 lines, about €78,000 to rebuild.
If Accessibility rose from 60 to 70, the lowest score rated Strong, the score would rise from 65 to about 68.
New since the last survey: 9 findings
- Handler temporal coupling · Temporal coupling in handler: CaptureOrderPaymentConsumer.Consume src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Consumers/CaptureOrderPaymentConsumer.cs
- Handler temporal coupling · Temporal coupling in handler: ReserveOrderStockConsumer.Consume src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Consumers/ReserveOrderStockConsumer.cs
- Outbox / dual-write · Dual write (no outbox): CatalogDataSeeder.StartAsync src/Services/Catalog/FreshCart.Catalog.Api/Seeding/CatalogDataSeeder.cs
- Outbox / dual-write · Dual write (no outbox): MarkOrderStockReservedActivity.Execute src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Activities/MarkOrderStockReservedActivity.cs
- Cancellation propagation · Async delegate without CancellationToken: AddDeliveryHealthChecks src/Services/Delivery/FreshCart.Delivery.Api/Configuration/DeliveryHealthChecks.cs
- Ambient inputs in the domain · Domain type reads the wall clock: RefreshToken src/Services/Identity/FreshCart.Identity.Domain/RefreshTokens/RefreshToken.cs
- Visual & motion safety · Low contrast colour pair in CSS (3.2:1) REDACTED
- Visual & motion safety · Low contrast colour pair in CSS (3.9:1) REDACTED
- Visual & motion safety · Low contrast colour pair in CSS (3.2:1) REDACTED
Fixed since the last survey: 3 findings
- Schema migrations · Schema created with EnsureCreated() (no migration path) src/Services/Inventory/FreshCart.Inventory.Api/Persistence/InventorySchemaInitializer.cs
- Schema migrations · Schema created with EnsureCreated() (no migration path) src/Services/Payment/FreshCart.Payment.Infrastructure/PaymentPersistenceInitializer.cs
- Schema migrations · Schema created with EnsureCreated() (no migration path) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/ReportingWarehouseInitializer.cs
Rebuild cost: about €78,000 · Estimate
| Cost to rebuild | €26,000 to €130,000, for 431 to 1,369 hours of work, about 0.5 person-years for 1 to 2 engineers |
|---|---|
| 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.9 at a score of 65. 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 | Medium: 25,543 lines of product code |
| Comment lines | The estimate prices 22,619 lines. Comment lines count towards the size of 25,543 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 — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Basket.Api.Domain | 2 BuildingBlocks.CQRS | 3 BuildingBlocks.Messaging.Events | 4 BuildingBlocks.Pagination | 5 Catalog.Api.Models | 6 Delivery.Domain.Deliveries | 7 Delivery.Domain.Slots | 8 Delivery.Domain.Zones | 9 Identity.Domain.Users | 10 Ordering.Domain.Orders | 11 Payment.Domain | 12 Reporting.Domain.Invoices | 13 Reporting.Domain.Kpis | 14 Reporting.Domain.Sales | 15 Basket.Api.Persistence | 16 Basket.Api.Pricing | 17 BuildingBlocks.Messaging.IntegrationEvents | 18 Catalog.Api.Data | 19 Identity.Application.Common.Abstractions | 20 Inventory.Api.Services | 21 Ordering.Application.Abstractions | 22 Payment.Application.Payments.Models | 23 Reporting.Application.Common.Models | 24 Reviews.Api.Persistence | 25 Basket.Api.Features.ShoppingBaskets.AddItem | 26 Basket.Api.Features.ShoppingBaskets.ApplyCoupon | 27 Basket.Api.Features.ShoppingBaskets.Checkout | 28 Basket.Api.Features.ShoppingBaskets.GetBasket | 29 Delivery.Application.Shipments | 30 Identity.Infrastructure.Persistence | 31 Notification.Api.Notifications | 32 Payment.Application.Abstractions | 33 Reporting.Application.Common.Abstractions | 34 Delivery.Application.Abstractions | 35 Delivery.Infrastructure.Persistence.Mapping | 36 Reporting.Application.Products.Queries | 37 Reporting.Application.Sales.Queries | 38 Reporting.Infrastructure.Persistence.Warehouse | 39 Delivery.Infrastructure.Persistence | 40 Delivery.Infrastructure.Persistence.Repositories |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Basket.Api.Domain | ||||||||||||||||||||||||||||||||||||||||
| 2 BuildingBlocks.CQRS | ||||||||||||||||||||||||||||||||||||||||
| 3 BuildingBlocks.Messaging.Events | ||||||||||||||||||||||||||||||||||||||||
| 4 BuildingBlocks.Pagination | ||||||||||||||||||||||||||||||||||||||||
| 5 Catalog.Api.Models | ||||||||||||||||||||||||||||||||||||||||
| 6 Delivery.Domain.Deliveries | ||||||||||||||||||||||||||||||||||||||||
| 7 Delivery.Domain.Slots | ||||||||||||||||||||||||||||||||||||||||
| 8 Delivery.Domain.Zones | ||||||||||||||||||||||||||||||||||||||||
| 9 Identity.Domain.Users | ||||||||||||||||||||||||||||||||||||||||
| 10 Ordering.Domain.Orders | ||||||||||||||||||||||||||||||||||||||||
| 11 Payment.Domain | ||||||||||||||||||||||||||||||||||||||||
| 12 Reporting.Domain.Invoices | ||||||||||||||||||||||||||||||||||||||||
| 13 Reporting.Domain.Kpis | ||||||||||||||||||||||||||||||||||||||||
| 14 Reporting.Domain.Sales | ||||||||||||||||||||||||||||||||||||||||
| 15 Basket.Api.Persistence | 9 | |||||||||||||||||||||||||||||||||||||||
| 16 Basket.Api.Pricing | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 BuildingBlocks.Messaging.IntegrationEvents | 13 | |||||||||||||||||||||||||||||||||||||||
| 18 Catalog.Api.Data | 6 | |||||||||||||||||||||||||||||||||||||||
| 19 Identity.Application.Common.Abstractions | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Inventory.Api.Services | 4 | |||||||||||||||||||||||||||||||||||||||
| 21 Ordering.Application.Abstractions | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 Payment.Application.Payments.Models | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Reporting.Application.Common.Models | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Reviews.Api.Persistence | 4 | |||||||||||||||||||||||||||||||||||||||
| 25 Basket.Api.Features.ShoppingBaskets.AddItem | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 Basket.Api.Features.ShoppingBaskets.ApplyCoupon | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 Basket.Api.Features.ShoppingBaskets.Checkout | 2 | 2 | 3 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 28 Basket.Api.Features.ShoppingBaskets.GetBasket | 2 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 29 Delivery.Application.Shipments | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 Identity.Infrastructure.Persistence | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 Notification.Api.Notifications | 2 | 7 | ||||||||||||||||||||||||||||||||||||||
| 32 Payment.Application.Abstractions | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 Reporting.Application.Common.Abstractions | 4 | 2 | 6 | 5 | ||||||||||||||||||||||||||||||||||||
| 34 Delivery.Application.Abstractions | 1 | 3 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 35 Delivery.Infrastructure.Persistence.Mapping | 2 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 Reporting.Application.Products.Queries | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 Reporting.Application.Sales.Queries | 6 | 2 | 8 | 3 | 5 | |||||||||||||||||||||||||||||||||||
| 38 Reporting.Infrastructure.Persistence.Warehouse | 6 | 2 | 6 | 5 | 11 | |||||||||||||||||||||||||||||||||||
| 39 Delivery.Infrastructure.Persistence | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 Delivery.Infrastructure.Persistence.Repositories | 1 | 1 | 2 | 1 | 5 | 5 |
15→1 Basket.Api.Persistence uses Basket.Api.Domain✕
- Connections
- 9 pairs of types, where a type in Basket.Api.Persistence uses a type in Basket.Api.Domain.
- The types involved
FreshCart.Basket.Api.Persistence.CachedBasketRepository→FreshCart.Basket.Api.Domain.ArchivedBasketFreshCart.Basket.Api.Persistence.CachedBasketRepository→FreshCart.Basket.Api.Domain.ShoppingBasketFreshCart.Basket.Api.Persistence.IBasketRepository→FreshCart.Basket.Api.Domain.ArchivedBasketFreshCart.Basket.Api.Persistence.IBasketRepository→FreshCart.Basket.Api.Domain.ShoppingBasketFreshCart.Basket.Api.Persistence.IBasketUnitOfWork→FreshCart.Basket.Api.Domain.ArchivedBasketFreshCart.Basket.Api.Persistence.MartenBasketPriceRefresher→FreshCart.Basket.Api.Domain.ShoppingBasketFreshCart.Basket.Api.Persistence.MartenBasketRepository→FreshCart.Basket.Api.Domain.ArchivedBasketFreshCart.Basket.Api.Persistence.MartenBasketRepository→FreshCart.Basket.Api.Domain.ShoppingBasketFreshCart.Basket.Api.Persistence.MartenBasketUnitOfWork→FreshCart.Basket.Api.Domain.ArchivedBasket
- Direction
- Basket.Api.Persistence uses Basket.Api.Domain, so a change to Basket.Api.Domain can break Basket.Api.Persistence, while a change to Basket.Api.Persistence can't break Basket.Api.Domain.
- Position
- Below the diagonal: Basket.Api.Persistence uses a module listed above it, which is the healthy direction.
16→1 Basket.Api.Pricing uses Basket.Api.Domain✕
- Connections
- 1 pair of types, where a type in Basket.Api.Pricing uses a type in Basket.Api.Domain.
- The types involved
FreshCart.Basket.Api.Pricing.BasketPricingRequest→FreshCart.Basket.Api.Domain.ShoppingBasket
- Direction
- Basket.Api.Pricing uses Basket.Api.Domain, so a change to Basket.Api.Domain can break Basket.Api.Pricing, while a change to Basket.Api.Pricing can't break Basket.Api.Domain.
- Position
- Below the diagonal: Basket.Api.Pricing uses a module listed above it, which is the healthy direction.
17→3 BuildingBlocks.Messaging.IntegrationEvents uses BuildingBlocks.Messaging.Events✕
- Connections
- 13 pairs of types, where a type in BuildingBlocks.Messaging.IntegrationEvents uses a type in BuildingBlocks.Messaging.Events.
- The types involved
FreshCart.BuildingBlocks.Messaging.IntegrationEvents.BasketCheckoutStartedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.DeliveryCompletedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.DeliveryScheduledIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderCancelledIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderConfirmedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderPlacedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderRefundedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.PaymentCapturedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.PaymentFailedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.ProductCreatedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.ProductPriceChangedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.StockReservationFailedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEventFreshCart.BuildingBlocks.Messaging.IntegrationEvents.StockReservedIntegrationEvent→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEvent
- Direction
- BuildingBlocks.Messaging.IntegrationEvents uses BuildingBlocks.Messaging.Events, so a change to BuildingBlocks.Messaging.Events can break BuildingBlocks.Messaging.IntegrationEvents, while a change to BuildingBlocks.Messaging.IntegrationEvents can't break BuildingBlocks.Messaging.Events.
- Position
- Below the diagonal: BuildingBlocks.Messaging.IntegrationEvents uses a module listed above it, which is the healthy direction.
18→5 Catalog.Api.Data uses Catalog.Api.Models✕
- Connections
- 6 pairs of types, where a type in Catalog.Api.Data uses a type in Catalog.Api.Models.
- The types involved
FreshCart.Catalog.Api.Data.ICatalogQueries→FreshCart.Catalog.Api.Models.BrandFreshCart.Catalog.Api.Data.ICatalogQueries→FreshCart.Catalog.Api.Models.CategoryFreshCart.Catalog.Api.Data.ICatalogQueries→FreshCart.Catalog.Api.Models.ProductFreshCart.Catalog.Api.Data.MartenCatalogQueries→FreshCart.Catalog.Api.Models.BrandFreshCart.Catalog.Api.Data.MartenCatalogQueries→FreshCart.Catalog.Api.Models.CategoryFreshCart.Catalog.Api.Data.MartenCatalogQueries→FreshCart.Catalog.Api.Models.Product
- Direction
- Catalog.Api.Data uses Catalog.Api.Models, so a change to Catalog.Api.Models can break Catalog.Api.Data, while a change to Catalog.Api.Data can't break Catalog.Api.Models.
- Position
- Below the diagonal: Catalog.Api.Data uses a module listed above it, which is the healthy direction.
19→9 Identity.Application.Common.Abstractions uses Identity.Domain.Users✕
- Connections
- 1 pair of types, where a type in Identity.Application.Common.Abstractions uses a type in Identity.Domain.Users.
- The types involved
FreshCart.Identity.Application.Common.Abstractions.IAccessTokenIssuer→FreshCart.Identity.Domain.Users.ApplicationUser
- Direction
- Identity.Application.Common.Abstractions uses Identity.Domain.Users, so a change to Identity.Domain.Users can break Identity.Application.Common.Abstractions, while a change to Identity.Application.Common.Abstractions can't break Identity.Domain.Users.
- Position
- Below the diagonal: Identity.Application.Common.Abstractions uses a module listed above it, which is the healthy direction.
20→4 Inventory.Api.Services uses BuildingBlocks.Pagination✕
- Connections
- 4 pairs of types, where a type in Inventory.Api.Services uses a type in BuildingBlocks.Pagination.
- The types involved
FreshCart.Inventory.Api.Services.IStockLevelService→FreshCart.BuildingBlocks.Pagination.PaginatedResultFreshCart.Inventory.Api.Services.IStockLevelService→FreshCart.BuildingBlocks.Pagination.PaginationRequestFreshCart.Inventory.Api.Services.StockLevelService→FreshCart.BuildingBlocks.Pagination.PaginatedResultFreshCart.Inventory.Api.Services.StockLevelService→FreshCart.BuildingBlocks.Pagination.PaginationRequest
- Direction
- Inventory.Api.Services uses BuildingBlocks.Pagination, so a change to BuildingBlocks.Pagination can break Inventory.Api.Services, while a change to Inventory.Api.Services can't break BuildingBlocks.Pagination.
- Position
- Below the diagonal: Inventory.Api.Services uses a module listed above it, which is the healthy direction.
21→4 Ordering.Application.Abstractions uses BuildingBlocks.Pagination✕
- Connections
- 2 pairs of types, where a type in Ordering.Application.Abstractions uses a type in BuildingBlocks.Pagination.
- The types involved
FreshCart.Ordering.Application.Abstractions.IOrderReadQueries→FreshCart.BuildingBlocks.Pagination.PaginatedResultFreshCart.Ordering.Application.Abstractions.IOrderReadQueries→FreshCart.BuildingBlocks.Pagination.PaginationRequest
- Direction
- Ordering.Application.Abstractions uses BuildingBlocks.Pagination, so a change to BuildingBlocks.Pagination can break Ordering.Application.Abstractions, while a change to Ordering.Application.Abstractions can't break BuildingBlocks.Pagination.
- Position
- Below the diagonal: Ordering.Application.Abstractions uses a module listed above it, which is the healthy direction.
21→10 Ordering.Application.Abstractions uses Ordering.Domain.Orders✕
- Connections
- 2 pairs of types, where a type in Ordering.Application.Abstractions uses a type in Ordering.Domain.Orders.
- The types involved
FreshCart.Ordering.Application.Abstractions.IOrderRepository→FreshCart.Ordering.Domain.Orders.OrderFreshCart.Ordering.Application.Abstractions.IOrderRepository→FreshCart.Ordering.Domain.Orders.OrderStatus
- Direction
- Ordering.Application.Abstractions uses Ordering.Domain.Orders, so a change to Ordering.Domain.Orders can break Ordering.Application.Abstractions, while a change to Ordering.Application.Abstractions can't break Ordering.Domain.Orders.
- Position
- Below the diagonal: Ordering.Application.Abstractions uses a module listed above it, which is the healthy direction.
22→11 Payment.Application.Payments.Models uses Payment.Domain✕
- Connections
- 2 pairs of types, where a type in Payment.Application.Payments.Models uses a type in Payment.Domain.
- The types involved
FreshCart.Payment.Application.Payments.Models.PaymentReadModel→FreshCart.Payment.Domain.PaymentAggregateFreshCart.Payment.Application.Payments.Models.PaymentReadModel→FreshCart.Payment.Domain.PaymentStatus
- Direction
- Payment.Application.Payments.Models uses Payment.Domain, so a change to Payment.Domain can break Payment.Application.Payments.Models, while a change to Payment.Application.Payments.Models can't break Payment.Domain.
- Position
- Below the diagonal: Payment.Application.Payments.Models uses a module listed above it, which is the healthy direction.
23→14 Reporting.Application.Common.Models uses Reporting.Domain.Sales✕
- Connections
- 1 pair of types, where a type in Reporting.Application.Common.Models uses a type in Reporting.Domain.Sales.
- The types involved
FreshCart.Reporting.Application.Common.Models.PeriodSelector→FreshCart.Reporting.Domain.Sales.ReportingPeriod
- Direction
- Reporting.Application.Common.Models uses Reporting.Domain.Sales, so a change to Reporting.Domain.Sales can break Reporting.Application.Common.Models, while a change to Reporting.Application.Common.Models can't break Reporting.Domain.Sales.
- Position
- Below the diagonal: Reporting.Application.Common.Models uses a module listed above it, which is the healthy direction.
24→4 Reviews.Api.Persistence uses BuildingBlocks.Pagination✕
- Connections
- 4 pairs of types, where a type in Reviews.Api.Persistence uses a type in BuildingBlocks.Pagination.
- The types involved
FreshCart.Reviews.Api.Persistence.IReviewRepository→FreshCart.BuildingBlocks.Pagination.PaginatedResultFreshCart.Reviews.Api.Persistence.IReviewRepository→FreshCart.BuildingBlocks.Pagination.PaginationRequestFreshCart.Reviews.Api.Persistence.MongoReviewRepository→FreshCart.BuildingBlocks.Pagination.PaginatedResultFreshCart.Reviews.Api.Persistence.MongoReviewRepository→FreshCart.BuildingBlocks.Pagination.PaginationRequest
- Direction
- Reviews.Api.Persistence uses BuildingBlocks.Pagination, so a change to BuildingBlocks.Pagination can break Reviews.Api.Persistence, while a change to Reviews.Api.Persistence can't break BuildingBlocks.Pagination.
- Position
- Below the diagonal: Reviews.Api.Persistence uses a module listed above it, which is the healthy direction.
25→1 Basket.Api.Features.ShoppingBaskets.AddItem uses Basket.Api.Domain✕
- Connections
- 1 pair of types, where a type in Basket.Api.Features.ShoppingBaskets.AddItem uses a type in Basket.Api.Domain.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.AddItem.AddItemCommandHandler→FreshCart.Basket.Api.Domain.ShoppingBasket
- Direction
- Basket.Api.Features.ShoppingBaskets.AddItem uses Basket.Api.Domain, so a change to Basket.Api.Domain can break Basket.Api.Features.ShoppingBaskets.AddItem, while a change to Basket.Api.Features.ShoppingBaskets.AddItem can't break Basket.Api.Domain.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.AddItem uses a module listed above it, which is the healthy direction.
25→2 Basket.Api.Features.ShoppingBaskets.AddItem uses BuildingBlocks.CQRS✕
- Connections
- 2 pairs of types, where a type in Basket.Api.Features.ShoppingBaskets.AddItem uses a type in BuildingBlocks.CQRS.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.AddItem.AddItemCommand→FreshCart.BuildingBlocks.CQRS.ICommandFreshCart.Basket.Api.Features.ShoppingBaskets.AddItem.AddItemCommandHandler→FreshCart.BuildingBlocks.CQRS.ICommandHandler
- Direction
- Basket.Api.Features.ShoppingBaskets.AddItem uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Basket.Api.Features.ShoppingBaskets.AddItem, while a change to Basket.Api.Features.ShoppingBaskets.AddItem can't break BuildingBlocks.CQRS.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.AddItem uses a module listed above it, which is the healthy direction.
25→15 Basket.Api.Features.ShoppingBaskets.AddItem uses Basket.Api.Persistence✕
- Connections
- 1 pair of types, where a type in Basket.Api.Features.ShoppingBaskets.AddItem uses a type in Basket.Api.Persistence.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.AddItem.AddItemCommandHandler→FreshCart.Basket.Api.Persistence.IBasketRepository
- Direction
- Basket.Api.Features.ShoppingBaskets.AddItem uses Basket.Api.Persistence, so a change to Basket.Api.Persistence can break Basket.Api.Features.ShoppingBaskets.AddItem, while a change to Basket.Api.Features.ShoppingBaskets.AddItem can't break Basket.Api.Persistence.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.AddItem uses a module listed above it, which is the healthy direction.
26→1 Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses Basket.Api.Domain✕
- Connections
- 1 pair of types, where a type in Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses a type in Basket.Api.Domain.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.ApplyCoupon.ApplyCouponCommandHandler→FreshCart.Basket.Api.Domain.ShoppingBasket
- Direction
- Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses Basket.Api.Domain, so a change to Basket.Api.Domain can break Basket.Api.Features.ShoppingBaskets.ApplyCoupon, while a change to Basket.Api.Features.ShoppingBaskets.ApplyCoupon can't break Basket.Api.Domain.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses a module listed above it, which is the healthy direction.
26→2 Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses BuildingBlocks.CQRS✕
- Connections
- 2 pairs of types, where a type in Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses a type in BuildingBlocks.CQRS.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.ApplyCoupon.ApplyCouponCommand→FreshCart.BuildingBlocks.CQRS.ICommandFreshCart.Basket.Api.Features.ShoppingBaskets.ApplyCoupon.ApplyCouponCommandHandler→FreshCart.BuildingBlocks.CQRS.ICommandHandler
- Direction
- Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Basket.Api.Features.ShoppingBaskets.ApplyCoupon, while a change to Basket.Api.Features.ShoppingBaskets.ApplyCoupon can't break BuildingBlocks.CQRS.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses a module listed above it, which is the healthy direction.
26→15 Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses Basket.Api.Persistence✕
- Connections
- 1 pair of types, where a type in Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses a type in Basket.Api.Persistence.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.ApplyCoupon.ApplyCouponCommandHandler→FreshCart.Basket.Api.Persistence.IBasketRepository
- Direction
- Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses Basket.Api.Persistence, so a change to Basket.Api.Persistence can break Basket.Api.Features.ShoppingBaskets.ApplyCoupon, while a change to Basket.Api.Features.ShoppingBaskets.ApplyCoupon can't break Basket.Api.Persistence.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses a module listed above it, which is the healthy direction.
26→16 Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses Basket.Api.Pricing✕
- Connections
- 1 pair of types, where a type in Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses a type in Basket.Api.Pricing.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.ApplyCoupon.ApplyCouponCommandHandler→FreshCart.Basket.Api.Pricing.IBasketPricingClient
- Direction
- Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses Basket.Api.Pricing, so a change to Basket.Api.Pricing can break Basket.Api.Features.ShoppingBaskets.ApplyCoupon, while a change to Basket.Api.Features.ShoppingBaskets.ApplyCoupon can't break Basket.Api.Pricing.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.ApplyCoupon uses a module listed above it, which is the healthy direction.
27→1 Basket.Api.Features.ShoppingBaskets.Checkout uses Basket.Api.Domain✕
- Connections
- 2 pairs of types, where a type in Basket.Api.Features.ShoppingBaskets.Checkout uses a type in Basket.Api.Domain.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommandHandler→FreshCart.Basket.Api.Domain.ArchivedBasketFreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommandHandler→FreshCart.Basket.Api.Domain.ShoppingBasket
- Direction
- Basket.Api.Features.ShoppingBaskets.Checkout uses Basket.Api.Domain, so a change to Basket.Api.Domain can break Basket.Api.Features.ShoppingBaskets.Checkout, while a change to Basket.Api.Features.ShoppingBaskets.Checkout can't break Basket.Api.Domain.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.Checkout uses a module listed above it, which is the healthy direction.
27→2 Basket.Api.Features.ShoppingBaskets.Checkout uses BuildingBlocks.CQRS✕
- Connections
- 2 pairs of types, where a type in Basket.Api.Features.ShoppingBaskets.Checkout uses a type in BuildingBlocks.CQRS.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommand→FreshCart.BuildingBlocks.CQRS.ICommandFreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommandHandler→FreshCart.BuildingBlocks.CQRS.ICommandHandler
- Direction
- Basket.Api.Features.ShoppingBaskets.Checkout uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Basket.Api.Features.ShoppingBaskets.Checkout, while a change to Basket.Api.Features.ShoppingBaskets.Checkout can't break BuildingBlocks.CQRS.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.Checkout uses a module listed above it, which is the healthy direction.
27→15 Basket.Api.Features.ShoppingBaskets.Checkout uses Basket.Api.Persistence✕
- Connections
- 3 pairs of types, where a type in Basket.Api.Features.ShoppingBaskets.Checkout uses a type in Basket.Api.Persistence.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommandHandler→FreshCart.Basket.Api.Persistence.IBasketCacheInvalidatorFreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommandHandler→FreshCart.Basket.Api.Persistence.IBasketRepositoryFreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommandHandler→FreshCart.Basket.Api.Persistence.IBasketUnitOfWork
- Direction
- Basket.Api.Features.ShoppingBaskets.Checkout uses Basket.Api.Persistence, so a change to Basket.Api.Persistence can break Basket.Api.Features.ShoppingBaskets.Checkout, while a change to Basket.Api.Features.ShoppingBaskets.Checkout can't break Basket.Api.Persistence.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.Checkout uses a module listed above it, which is the healthy direction.
27→16 Basket.Api.Features.ShoppingBaskets.Checkout uses Basket.Api.Pricing✕
- Connections
- 2 pairs of types, where a type in Basket.Api.Features.ShoppingBaskets.Checkout uses a type in Basket.Api.Pricing.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommandHandler→FreshCart.Basket.Api.Pricing.BasketPricingResultFreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommandHandler→FreshCart.Basket.Api.Pricing.IBasketPricingClient
- Direction
- Basket.Api.Features.ShoppingBaskets.Checkout uses Basket.Api.Pricing, so a change to Basket.Api.Pricing can break Basket.Api.Features.ShoppingBaskets.Checkout, while a change to Basket.Api.Features.ShoppingBaskets.Checkout can't break Basket.Api.Pricing.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.Checkout uses a module listed above it, which is the healthy direction.
27→17 Basket.Api.Features.ShoppingBaskets.Checkout uses BuildingBlocks.Messaging.IntegrationEvents✕
- Connections
- 4 pairs of types, where a type in Basket.Api.Features.ShoppingBaskets.Checkout uses a type in BuildingBlocks.Messaging.IntegrationEvents.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommand→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.CheckoutAddressFreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommandHandler→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.BasketCheckoutStartedIntegrationEventFreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutCommandHandler→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.CheckoutLineFreshCart.Basket.Api.Features.ShoppingBaskets.Checkout.CheckoutRequest→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.CheckoutAddress
- Direction
- Basket.Api.Features.ShoppingBaskets.Checkout uses BuildingBlocks.Messaging.IntegrationEvents, so a change to BuildingBlocks.Messaging.IntegrationEvents can break Basket.Api.Features.ShoppingBaskets.Checkout, while a change to Basket.Api.Features.ShoppingBaskets.Checkout can't break BuildingBlocks.Messaging.IntegrationEvents.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.Checkout uses a module listed above it, which is the healthy direction.
28→1 Basket.Api.Features.ShoppingBaskets.GetBasket uses Basket.Api.Domain✕
- Connections
- 2 pairs of types, where a type in Basket.Api.Features.ShoppingBaskets.GetBasket uses a type in Basket.Api.Domain.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.GetBasket.GetBasketQueryHandler→FreshCart.Basket.Api.Domain.BasketItemFreshCart.Basket.Api.Features.ShoppingBaskets.GetBasket.GetBasketQueryHandler→FreshCart.Basket.Api.Domain.ShoppingBasket
- Direction
- Basket.Api.Features.ShoppingBaskets.GetBasket uses Basket.Api.Domain, so a change to Basket.Api.Domain can break Basket.Api.Features.ShoppingBaskets.GetBasket, while a change to Basket.Api.Features.ShoppingBaskets.GetBasket can't break Basket.Api.Domain.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.GetBasket uses a module listed above it, which is the healthy direction.
28→2 Basket.Api.Features.ShoppingBaskets.GetBasket uses BuildingBlocks.CQRS✕
- Connections
- 2 pairs of types, where a type in Basket.Api.Features.ShoppingBaskets.GetBasket uses a type in BuildingBlocks.CQRS.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.GetBasket.GetBasketQuery→FreshCart.BuildingBlocks.CQRS.IQueryFreshCart.Basket.Api.Features.ShoppingBaskets.GetBasket.GetBasketQueryHandler→FreshCart.BuildingBlocks.CQRS.IQueryHandler
- Direction
- Basket.Api.Features.ShoppingBaskets.GetBasket uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Basket.Api.Features.ShoppingBaskets.GetBasket, while a change to Basket.Api.Features.ShoppingBaskets.GetBasket can't break BuildingBlocks.CQRS.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.GetBasket uses a module listed above it, which is the healthy direction.
28→15 Basket.Api.Features.ShoppingBaskets.GetBasket uses Basket.Api.Persistence✕
- Connections
- 1 pair of types, where a type in Basket.Api.Features.ShoppingBaskets.GetBasket uses a type in Basket.Api.Persistence.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.GetBasket.GetBasketQueryHandler→FreshCart.Basket.Api.Persistence.IBasketRepository
- Direction
- Basket.Api.Features.ShoppingBaskets.GetBasket uses Basket.Api.Persistence, so a change to Basket.Api.Persistence can break Basket.Api.Features.ShoppingBaskets.GetBasket, while a change to Basket.Api.Features.ShoppingBaskets.GetBasket can't break Basket.Api.Persistence.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.GetBasket uses a module listed above it, which is the healthy direction.
28→16 Basket.Api.Features.ShoppingBaskets.GetBasket uses Basket.Api.Pricing✕
- Connections
- 3 pairs of types, where a type in Basket.Api.Features.ShoppingBaskets.GetBasket uses a type in Basket.Api.Pricing.
- The types involved
FreshCart.Basket.Api.Features.ShoppingBaskets.GetBasket.GetBasketQueryHandler→FreshCart.Basket.Api.Pricing.BasketPricingResultFreshCart.Basket.Api.Features.ShoppingBaskets.GetBasket.GetBasketQueryHandler→FreshCart.Basket.Api.Pricing.IBasketPricingClientFreshCart.Basket.Api.Features.ShoppingBaskets.GetBasket.GetBasketQueryHandler→FreshCart.Basket.Api.Pricing.PricedBasketLine
- Direction
- Basket.Api.Features.ShoppingBaskets.GetBasket uses Basket.Api.Pricing, so a change to Basket.Api.Pricing can break Basket.Api.Features.ShoppingBaskets.GetBasket, while a change to Basket.Api.Features.ShoppingBaskets.GetBasket can't break Basket.Api.Pricing.
- Position
- Below the diagonal: Basket.Api.Features.ShoppingBaskets.GetBasket uses a module listed above it, which is the healthy direction.
29→6 Delivery.Application.Shipments uses Delivery.Domain.Deliveries✕
- Connections
- 2 pairs of types, where a type in Delivery.Application.Shipments uses a type in Delivery.Domain.Deliveries.
- The types involved
FreshCart.Delivery.Application.Shipments.BasketCheckoutStartedConsumer→FreshCart.Delivery.Domain.Deliveries.DeliveryAddressFreshCart.Delivery.Application.Shipments.PendingShipment→FreshCart.Delivery.Domain.Deliveries.DeliveryAddress
- Direction
- Delivery.Application.Shipments uses Delivery.Domain.Deliveries, so a change to Delivery.Domain.Deliveries can break Delivery.Application.Shipments, while a change to Delivery.Application.Shipments can't break Delivery.Domain.Deliveries.
- Position
- Below the diagonal: Delivery.Application.Shipments uses a module listed above it, which is the healthy direction.
29→17 Delivery.Application.Shipments uses BuildingBlocks.Messaging.IntegrationEvents✕
- Connections
- 2 pairs of types, where a type in Delivery.Application.Shipments uses a type in BuildingBlocks.Messaging.IntegrationEvents.
- The types involved
FreshCart.Delivery.Application.Shipments.BasketCheckoutStartedConsumer→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.BasketCheckoutStartedIntegrationEventFreshCart.Delivery.Application.Shipments.BasketCheckoutStartedConsumer→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.CheckoutAddress
- Direction
- Delivery.Application.Shipments uses BuildingBlocks.Messaging.IntegrationEvents, so a change to BuildingBlocks.Messaging.IntegrationEvents can break Delivery.Application.Shipments, while a change to Delivery.Application.Shipments can't break BuildingBlocks.Messaging.IntegrationEvents.
- Position
- Below the diagonal: Delivery.Application.Shipments uses a module listed above it, which is the healthy direction.
29→34 Delivery.Application.Shipments uses Delivery.Application.Abstractions part of a loop✕
- Connections
- 1 pair of types, where a type in Delivery.Application.Shipments uses a type in Delivery.Application.Abstractions.
- The types involved
FreshCart.Delivery.Application.Shipments.BasketCheckoutStartedConsumer→FreshCart.Delivery.Application.Abstractions.IPendingShipmentRepository
- Direction
- Delivery.Application.Shipments uses Delivery.Application.Abstractions, so a change to Delivery.Application.Abstractions can break Delivery.Application.Shipments, while a change to Delivery.Application.Shipments can't break Delivery.Application.Abstractions.
- 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.
30→9 Identity.Infrastructure.Persistence uses Identity.Domain.Users✕
- Connections
- 1 pair of types, where a type in Identity.Infrastructure.Persistence uses a type in Identity.Domain.Users.
- The types involved
FreshCart.Identity.Infrastructure.Persistence.IdentityDataSeeder→FreshCart.Identity.Domain.Users.ApplicationUser
- Direction
- Identity.Infrastructure.Persistence uses Identity.Domain.Users, so a change to Identity.Domain.Users can break Identity.Infrastructure.Persistence, while a change to Identity.Infrastructure.Persistence can't break Identity.Domain.Users.
- Position
- Below the diagonal: Identity.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
30→19 Identity.Infrastructure.Persistence uses Identity.Application.Common.Abstractions✕
- Connections
- 1 pair of types, where a type in Identity.Infrastructure.Persistence uses a type in Identity.Application.Common.Abstractions.
- The types involved
FreshCart.Identity.Infrastructure.Persistence.EntityFrameworkAuditLog→FreshCart.Identity.Application.Common.Abstractions.IIdentityAuditLog
- Direction
- Identity.Infrastructure.Persistence uses Identity.Application.Common.Abstractions, so a change to Identity.Application.Common.Abstractions can break Identity.Infrastructure.Persistence, while a change to Identity.Infrastructure.Persistence can't break Identity.Application.Common.Abstractions.
- Position
- Below the diagonal: Identity.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
31→4 Notification.Api.Notifications uses BuildingBlocks.Pagination✕
- Connections
- 2 pairs of types, where a type in Notification.Api.Notifications uses a type in BuildingBlocks.Pagination.
- The types involved
FreshCart.Notification.Api.Notifications.INotificationStore→FreshCart.BuildingBlocks.Pagination.PaginatedResultFreshCart.Notification.Api.Notifications.INotificationStore→FreshCart.BuildingBlocks.Pagination.PaginationRequest
- Direction
- Notification.Api.Notifications uses BuildingBlocks.Pagination, so a change to BuildingBlocks.Pagination can break Notification.Api.Notifications, while a change to Notification.Api.Notifications can't break BuildingBlocks.Pagination.
- Position
- Below the diagonal: Notification.Api.Notifications uses a module listed above it, which is the healthy direction.
31→17 Notification.Api.Notifications uses BuildingBlocks.Messaging.IntegrationEvents✕
- Connections
- 7 pairs of types, where a type in Notification.Api.Notifications uses a type in BuildingBlocks.Messaging.IntegrationEvents.
- The types involved
FreshCart.Notification.Api.Notifications.NotificationContentFactory→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.DeliveryCompletedIntegrationEventFreshCart.Notification.Api.Notifications.NotificationContentFactory→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.DeliveryScheduledIntegrationEventFreshCart.Notification.Api.Notifications.NotificationContentFactory→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderCancelledIntegrationEventFreshCart.Notification.Api.Notifications.NotificationContentFactory→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderConfirmedIntegrationEventFreshCart.Notification.Api.Notifications.NotificationContentFactory→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderPlacedIntegrationEventFreshCart.Notification.Api.Notifications.NotificationContentFactory→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderRefundedIntegrationEventFreshCart.Notification.Api.Notifications.NotificationContentFactory→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.PaymentFailedIntegrationEvent
- Direction
- Notification.Api.Notifications uses BuildingBlocks.Messaging.IntegrationEvents, so a change to BuildingBlocks.Messaging.IntegrationEvents can break Notification.Api.Notifications, while a change to Notification.Api.Notifications can't break BuildingBlocks.Messaging.IntegrationEvents.
- Position
- Below the diagonal: Notification.Api.Notifications uses a module listed above it, which is the healthy direction.
32→4 Payment.Application.Abstractions uses BuildingBlocks.Pagination✕
- Connections
- 2 pairs of types, where a type in Payment.Application.Abstractions uses a type in BuildingBlocks.Pagination.
- The types involved
FreshCart.Payment.Application.Abstractions.IPaymentReadQueries→FreshCart.BuildingBlocks.Pagination.PaginatedResultFreshCart.Payment.Application.Abstractions.IPaymentReadQueries→FreshCart.BuildingBlocks.Pagination.PaginationRequest
- Direction
- Payment.Application.Abstractions uses BuildingBlocks.Pagination, so a change to BuildingBlocks.Pagination can break Payment.Application.Abstractions, while a change to Payment.Application.Abstractions can't break BuildingBlocks.Pagination.
- Position
- Below the diagonal: Payment.Application.Abstractions uses a module listed above it, which is the healthy direction.
32→22 Payment.Application.Abstractions uses Payment.Application.Payments.Models✕
- Connections
- 2 pairs of types, where a type in Payment.Application.Abstractions uses a type in Payment.Application.Payments.Models.
- The types involved
FreshCart.Payment.Application.Abstractions.IPaymentReadModelWriter→FreshCart.Payment.Application.Payments.Models.PaymentReadModelFreshCart.Payment.Application.Abstractions.IPaymentReadQueries→FreshCart.Payment.Application.Payments.Models.PaymentReadModel
- Direction
- Payment.Application.Abstractions uses Payment.Application.Payments.Models, so a change to Payment.Application.Payments.Models can break Payment.Application.Abstractions, while a change to Payment.Application.Abstractions can't break Payment.Application.Payments.Models.
- Position
- Below the diagonal: Payment.Application.Abstractions uses a module listed above it, which is the healthy direction.
33→12 Reporting.Application.Common.Abstractions uses Reporting.Domain.Invoices✕
- Connections
- 4 pairs of types, where a type in Reporting.Application.Common.Abstractions uses a type in Reporting.Domain.Invoices.
- The types involved
FreshCart.Reporting.Application.Common.Abstractions.IInvoiceRenderer→FreshCart.Reporting.Domain.Invoices.InvoiceFreshCart.Reporting.Application.Common.Abstractions.IInvoiceRepository→FreshCart.Reporting.Domain.Invoices.InvoiceFreshCart.Reporting.Application.Common.Abstractions.IInvoiceRepository→FreshCart.Reporting.Domain.Invoices.InvoiceKindFreshCart.Reporting.Application.Common.Abstractions.IInvoiceRepository→FreshCart.Reporting.Domain.Invoices.InvoiceNumber
- Direction
- Reporting.Application.Common.Abstractions uses Reporting.Domain.Invoices, so a change to Reporting.Domain.Invoices can break Reporting.Application.Common.Abstractions, while a change to Reporting.Application.Common.Abstractions can't break Reporting.Domain.Invoices.
- Position
- Below the diagonal: Reporting.Application.Common.Abstractions uses a module listed above it, which is the healthy direction.
33→13 Reporting.Application.Common.Abstractions uses Reporting.Domain.Kpis✕
- Connections
- 2 pairs of types, where a type in Reporting.Application.Common.Abstractions uses a type in Reporting.Domain.Kpis.
- The types involved
FreshCart.Reporting.Application.Common.Abstractions.ICustomerReadWarehouse→FreshCart.Reporting.Domain.Kpis.TopEntityRankingFreshCart.Reporting.Application.Common.Abstractions.IProductReadWarehouse→FreshCart.Reporting.Domain.Kpis.TopEntityRanking
- Direction
- Reporting.Application.Common.Abstractions uses Reporting.Domain.Kpis, so a change to Reporting.Domain.Kpis can break Reporting.Application.Common.Abstractions, while a change to Reporting.Application.Common.Abstractions can't break Reporting.Domain.Kpis.
- Position
- Below the diagonal: Reporting.Application.Common.Abstractions uses a module listed above it, which is the healthy direction.
33→14 Reporting.Application.Common.Abstractions uses Reporting.Domain.Sales✕
- Connections
- 6 pairs of types, where a type in Reporting.Application.Common.Abstractions uses a type in Reporting.Domain.Sales.
- The types involved
FreshCart.Reporting.Application.Common.Abstractions.ICustomerReadWarehouse→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Application.Common.Abstractions.IDeliveryReadWarehouse→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Application.Common.Abstractions.IProductReadWarehouse→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Application.Common.Abstractions.ISalesReadWarehouse→FreshCart.Reporting.Domain.Sales.AggregationBucketFreshCart.Reporting.Application.Common.Abstractions.ISalesReadWarehouse→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Application.Common.Abstractions.ISalesReadWarehouse→FreshCart.Reporting.Domain.Sales.SalesSnapshot
- Direction
- Reporting.Application.Common.Abstractions uses Reporting.Domain.Sales, so a change to Reporting.Domain.Sales can break Reporting.Application.Common.Abstractions, while a change to Reporting.Application.Common.Abstractions can't break Reporting.Domain.Sales.
- Position
- Below the diagonal: Reporting.Application.Common.Abstractions uses a module listed above it, which is the healthy direction.
33→17 Reporting.Application.Common.Abstractions uses BuildingBlocks.Messaging.IntegrationEvents✕
- Connections
- 5 pairs of types, where a type in Reporting.Application.Common.Abstractions uses a type in BuildingBlocks.Messaging.IntegrationEvents.
- The types involved
FreshCart.Reporting.Application.Common.Abstractions.IProjectionWriter→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.DeliveryCompletedIntegrationEventFreshCart.Reporting.Application.Common.Abstractions.IProjectionWriter→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.DeliveryScheduledIntegrationEventFreshCart.Reporting.Application.Common.Abstractions.IProjectionWriter→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderConfirmedIntegrationEventFreshCart.Reporting.Application.Common.Abstractions.IProjectionWriter→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderRefundedIntegrationEventFreshCart.Reporting.Application.Common.Abstractions.IProjectionWriter→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.ProductCreatedIntegrationEvent
- Direction
- Reporting.Application.Common.Abstractions uses BuildingBlocks.Messaging.IntegrationEvents, so a change to BuildingBlocks.Messaging.IntegrationEvents can break Reporting.Application.Common.Abstractions, while a change to Reporting.Application.Common.Abstractions can't break BuildingBlocks.Messaging.IntegrationEvents.
- Position
- Below the diagonal: Reporting.Application.Common.Abstractions uses a module listed above it, which is the healthy direction.
34→3 Delivery.Application.Abstractions uses BuildingBlocks.Messaging.Events✕
- Connections
- 1 pair of types, where a type in Delivery.Application.Abstractions uses a type in BuildingBlocks.Messaging.Events.
- The types involved
FreshCart.Delivery.Application.Abstractions.IDeliveryUnitOfWork→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEvent
- Direction
- Delivery.Application.Abstractions uses BuildingBlocks.Messaging.Events, so a change to BuildingBlocks.Messaging.Events can break Delivery.Application.Abstractions, while a change to Delivery.Application.Abstractions can't break BuildingBlocks.Messaging.Events.
- Position
- Below the diagonal: Delivery.Application.Abstractions uses a module listed above it, which is the healthy direction.
34→6 Delivery.Application.Abstractions uses Delivery.Domain.Deliveries✕
- Connections
- 3 pairs of types, where a type in Delivery.Application.Abstractions uses a type in Delivery.Domain.Deliveries.
- The types involved
FreshCart.Delivery.Application.Abstractions.IDeliveryRepository→FreshCart.Delivery.Domain.Deliveries.DeliveryFreshCart.Delivery.Application.Abstractions.IDeliveryUnitOfWork→FreshCart.Delivery.Domain.Deliveries.DeliveryFreshCart.Delivery.Application.Abstractions.IGeocodingService→FreshCart.Delivery.Domain.Deliveries.DeliveryAddress
- Direction
- Delivery.Application.Abstractions uses Delivery.Domain.Deliveries, so a change to Delivery.Domain.Deliveries can break Delivery.Application.Abstractions, while a change to Delivery.Application.Abstractions can't break Delivery.Domain.Deliveries.
- Position
- Below the diagonal: Delivery.Application.Abstractions uses a module listed above it, which is the healthy direction.
34→7 Delivery.Application.Abstractions uses Delivery.Domain.Slots✕
- Connections
- 1 pair of types, where a type in Delivery.Application.Abstractions uses a type in Delivery.Domain.Slots.
- The types involved
FreshCart.Delivery.Application.Abstractions.ISlotRepository→FreshCart.Delivery.Domain.Slots.DeliverySlot
- Direction
- Delivery.Application.Abstractions uses Delivery.Domain.Slots, so a change to Delivery.Domain.Slots can break Delivery.Application.Abstractions, while a change to Delivery.Application.Abstractions can't break Delivery.Domain.Slots.
- Position
- Below the diagonal: Delivery.Application.Abstractions uses a module listed above it, which is the healthy direction.
34→8 Delivery.Application.Abstractions uses Delivery.Domain.Zones✕
- Connections
- 3 pairs of types, where a type in Delivery.Application.Abstractions uses a type in Delivery.Domain.Zones.
- The types involved
FreshCart.Delivery.Application.Abstractions.IGeocodingService→FreshCart.Delivery.Domain.Zones.GeoCoordinateFreshCart.Delivery.Application.Abstractions.IZoneRepository→FreshCart.Delivery.Domain.Zones.DeliveryZoneFreshCart.Delivery.Application.Abstractions.IZoneRepository→FreshCart.Delivery.Domain.Zones.GeoCoordinate
- Direction
- Delivery.Application.Abstractions uses Delivery.Domain.Zones, so a change to Delivery.Domain.Zones can break Delivery.Application.Abstractions, while a change to Delivery.Application.Abstractions can't break Delivery.Domain.Zones.
- Position
- Below the diagonal: Delivery.Application.Abstractions uses a module listed above it, which is the healthy direction.
34→29 Delivery.Application.Abstractions uses Delivery.Application.Shipments✕
- Connections
- 1 pair of types, where a type in Delivery.Application.Abstractions uses a type in Delivery.Application.Shipments.
- The types involved
FreshCart.Delivery.Application.Abstractions.IPendingShipmentRepository→FreshCart.Delivery.Application.Shipments.PendingShipment
- Direction
- Delivery.Application.Abstractions uses Delivery.Application.Shipments, so a change to Delivery.Application.Shipments can break Delivery.Application.Abstractions, while a change to Delivery.Application.Abstractions can't break Delivery.Application.Shipments.
- Position
- Below the diagonal: Delivery.Application.Abstractions uses a module listed above it, which is the healthy direction.
35→6 Delivery.Infrastructure.Persistence.Mapping uses Delivery.Domain.Deliveries✕
- Connections
- 2 pairs of types, where a type in Delivery.Infrastructure.Persistence.Mapping uses a type in Delivery.Domain.Deliveries.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.Mapping.DocumentMapper→FreshCart.Delivery.Domain.Deliveries.DeliveryFreshCart.Delivery.Infrastructure.Persistence.Mapping.DocumentMapper→FreshCart.Delivery.Domain.Deliveries.DeliveryAddress
- Direction
- Delivery.Infrastructure.Persistence.Mapping uses Delivery.Domain.Deliveries, so a change to Delivery.Domain.Deliveries can break Delivery.Infrastructure.Persistence.Mapping, while a change to Delivery.Infrastructure.Persistence.Mapping can't break Delivery.Domain.Deliveries.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence.Mapping uses a module listed above it, which is the healthy direction.
35→7 Delivery.Infrastructure.Persistence.Mapping uses Delivery.Domain.Slots✕
- Connections
- 1 pair of types, where a type in Delivery.Infrastructure.Persistence.Mapping uses a type in Delivery.Domain.Slots.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.Mapping.DocumentMapper→FreshCart.Delivery.Domain.Slots.DeliverySlot
- Direction
- Delivery.Infrastructure.Persistence.Mapping uses Delivery.Domain.Slots, so a change to Delivery.Domain.Slots can break Delivery.Infrastructure.Persistence.Mapping, while a change to Delivery.Infrastructure.Persistence.Mapping can't break Delivery.Domain.Slots.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence.Mapping uses a module listed above it, which is the healthy direction.
35→8 Delivery.Infrastructure.Persistence.Mapping uses Delivery.Domain.Zones✕
- Connections
- 3 pairs of types, where a type in Delivery.Infrastructure.Persistence.Mapping uses a type in Delivery.Domain.Zones.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.Mapping.DocumentMapper→FreshCart.Delivery.Domain.Zones.DeliveryZoneFreshCart.Delivery.Infrastructure.Persistence.Mapping.DocumentMapper→FreshCart.Delivery.Domain.Zones.GeoCoordinateFreshCart.Delivery.Infrastructure.Persistence.Mapping.DocumentMapper→FreshCart.Delivery.Domain.Zones.ZonePolygon
- Direction
- Delivery.Infrastructure.Persistence.Mapping uses Delivery.Domain.Zones, so a change to Delivery.Domain.Zones can break Delivery.Infrastructure.Persistence.Mapping, while a change to Delivery.Infrastructure.Persistence.Mapping can't break Delivery.Domain.Zones.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence.Mapping uses a module listed above it, which is the healthy direction.
35→29 Delivery.Infrastructure.Persistence.Mapping uses Delivery.Application.Shipments✕
- Connections
- 1 pair of types, where a type in Delivery.Infrastructure.Persistence.Mapping uses a type in Delivery.Application.Shipments.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.Mapping.DocumentMapper→FreshCart.Delivery.Application.Shipments.PendingShipment
- Direction
- Delivery.Infrastructure.Persistence.Mapping uses Delivery.Application.Shipments, so a change to Delivery.Application.Shipments can break Delivery.Infrastructure.Persistence.Mapping, while a change to Delivery.Infrastructure.Persistence.Mapping can't break Delivery.Application.Shipments.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence.Mapping uses a module listed above it, which is the healthy direction.
36→2 Reporting.Application.Products.Queries uses BuildingBlocks.CQRS✕
- Connections
- 2 pairs of types, where a type in Reporting.Application.Products.Queries uses a type in BuildingBlocks.CQRS.
- The types involved
FreshCart.Reporting.Application.Products.Queries.GetTopProductsQuery→FreshCart.BuildingBlocks.CQRS.IQueryFreshCart.Reporting.Application.Products.Queries.GetTopProductsQueryHandler→FreshCart.BuildingBlocks.CQRS.IQueryHandler
- Direction
- Reporting.Application.Products.Queries uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Reporting.Application.Products.Queries, while a change to Reporting.Application.Products.Queries can't break BuildingBlocks.CQRS.
- Position
- Below the diagonal: Reporting.Application.Products.Queries uses a module listed above it, which is the healthy direction.
36→13 Reporting.Application.Products.Queries uses Reporting.Domain.Kpis✕
- Connections
- 1 pair of types, where a type in Reporting.Application.Products.Queries uses a type in Reporting.Domain.Kpis.
- The types involved
FreshCart.Reporting.Application.Products.Queries.TopProductsDto→FreshCart.Reporting.Domain.Kpis.TopEntityRanking
- Direction
- Reporting.Application.Products.Queries uses Reporting.Domain.Kpis, so a change to Reporting.Domain.Kpis can break Reporting.Application.Products.Queries, while a change to Reporting.Application.Products.Queries can't break Reporting.Domain.Kpis.
- Position
- Below the diagonal: Reporting.Application.Products.Queries uses a module listed above it, which is the healthy direction.
36→14 Reporting.Application.Products.Queries uses Reporting.Domain.Sales✕
- Connections
- 1 pair of types, where a type in Reporting.Application.Products.Queries uses a type in Reporting.Domain.Sales.
- The types involved
FreshCart.Reporting.Application.Products.Queries.TopProductsDto→FreshCart.Reporting.Domain.Sales.ReportingPeriod
- Direction
- Reporting.Application.Products.Queries uses Reporting.Domain.Sales, so a change to Reporting.Domain.Sales can break Reporting.Application.Products.Queries, while a change to Reporting.Application.Products.Queries can't break Reporting.Domain.Sales.
- Position
- Below the diagonal: Reporting.Application.Products.Queries uses a module listed above it, which is the healthy direction.
36→23 Reporting.Application.Products.Queries uses Reporting.Application.Common.Models✕
- Connections
- 1 pair of types, where a type in Reporting.Application.Products.Queries uses a type in Reporting.Application.Common.Models.
- The types involved
FreshCart.Reporting.Application.Products.Queries.GetTopProductsQuery→FreshCart.Reporting.Application.Common.Models.PeriodSelector
- Direction
- Reporting.Application.Products.Queries uses Reporting.Application.Common.Models, so a change to Reporting.Application.Common.Models can break Reporting.Application.Products.Queries, while a change to Reporting.Application.Products.Queries can't break Reporting.Application.Common.Models.
- Position
- Below the diagonal: Reporting.Application.Products.Queries uses a module listed above it, which is the healthy direction.
36→33 Reporting.Application.Products.Queries uses Reporting.Application.Common.Abstractions✕
- Connections
- 1 pair of types, where a type in Reporting.Application.Products.Queries uses a type in Reporting.Application.Common.Abstractions.
- The types involved
FreshCart.Reporting.Application.Products.Queries.GetTopProductsQueryHandler→FreshCart.Reporting.Application.Common.Abstractions.IProductReadWarehouse
- Direction
- Reporting.Application.Products.Queries uses Reporting.Application.Common.Abstractions, so a change to Reporting.Application.Common.Abstractions can break Reporting.Application.Products.Queries, while a change to Reporting.Application.Products.Queries can't break Reporting.Application.Common.Abstractions.
- Position
- Below the diagonal: Reporting.Application.Products.Queries uses a module listed above it, which is the healthy direction.
37→2 Reporting.Application.Sales.Queries uses BuildingBlocks.CQRS✕
- Connections
- 6 pairs of types, where a type in Reporting.Application.Sales.Queries uses a type in BuildingBlocks.CQRS.
- The types involved
FreshCart.Reporting.Application.Sales.Queries.GetRevenueBreakdownQuery→FreshCart.BuildingBlocks.CQRS.IQueryFreshCart.Reporting.Application.Sales.Queries.GetRevenueBreakdownQueryHandler→FreshCart.BuildingBlocks.CQRS.IQueryHandlerFreshCart.Reporting.Application.Sales.Queries.GetSalesOverviewQuery→FreshCart.BuildingBlocks.CQRS.IQueryFreshCart.Reporting.Application.Sales.Queries.GetSalesOverviewQueryHandler→FreshCart.BuildingBlocks.CQRS.IQueryHandlerFreshCart.Reporting.Application.Sales.Queries.GetSalesTimeSeriesQuery→FreshCart.BuildingBlocks.CQRS.IQueryFreshCart.Reporting.Application.Sales.Queries.GetSalesTimeSeriesQueryHandler→FreshCart.BuildingBlocks.CQRS.IQueryHandler
- Direction
- Reporting.Application.Sales.Queries uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Reporting.Application.Sales.Queries, while a change to Reporting.Application.Sales.Queries can't break BuildingBlocks.CQRS.
- Position
- Below the diagonal: Reporting.Application.Sales.Queries uses a module listed above it, which is the healthy direction.
37→13 Reporting.Application.Sales.Queries uses Reporting.Domain.Kpis✕
- Connections
- 2 pairs of types, where a type in Reporting.Application.Sales.Queries uses a type in Reporting.Domain.Kpis.
- The types involved
FreshCart.Reporting.Application.Sales.Queries.GetSalesOverviewQueryHandler→FreshCart.Reporting.Domain.Kpis.KpiMetricFreshCart.Reporting.Application.Sales.Queries.SalesOverviewDto→FreshCart.Reporting.Domain.Kpis.KpiMetric
- Direction
- Reporting.Application.Sales.Queries uses Reporting.Domain.Kpis, so a change to Reporting.Domain.Kpis can break Reporting.Application.Sales.Queries, while a change to Reporting.Application.Sales.Queries can't break Reporting.Domain.Kpis.
- Position
- Below the diagonal: Reporting.Application.Sales.Queries uses a module listed above it, which is the healthy direction.
37→14 Reporting.Application.Sales.Queries uses Reporting.Domain.Sales✕
- Connections
- 8 pairs of types, where a type in Reporting.Application.Sales.Queries uses a type in Reporting.Domain.Sales.
- The types involved
FreshCart.Reporting.Application.Sales.Queries.GetSalesOverviewQueryHandler→FreshCart.Reporting.Domain.Sales.SalesSnapshotFreshCart.Reporting.Application.Sales.Queries.GetSalesTimeSeriesQuery→FreshCart.Reporting.Domain.Sales.AggregationBucketFreshCart.Reporting.Application.Sales.Queries.RevenueBreakdownDto→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Application.Sales.Queries.SalesOverviewDto→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Application.Sales.Queries.SalesOverviewDto→FreshCart.Reporting.Domain.Sales.SalesSnapshotFreshCart.Reporting.Application.Sales.Queries.SalesTimeSeriesDto→FreshCart.Reporting.Domain.Sales.AggregationBucketFreshCart.Reporting.Application.Sales.Queries.SalesTimeSeriesDto→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Application.Sales.Queries.SalesTimeSeriesDto→FreshCart.Reporting.Domain.Sales.SalesSnapshot
- Direction
- Reporting.Application.Sales.Queries uses Reporting.Domain.Sales, so a change to Reporting.Domain.Sales can break Reporting.Application.Sales.Queries, while a change to Reporting.Application.Sales.Queries can't break Reporting.Domain.Sales.
- Position
- Below the diagonal: Reporting.Application.Sales.Queries uses a module listed above it, which is the healthy direction.
37→23 Reporting.Application.Sales.Queries uses Reporting.Application.Common.Models✕
- Connections
- 3 pairs of types, where a type in Reporting.Application.Sales.Queries uses a type in Reporting.Application.Common.Models.
- The types involved
FreshCart.Reporting.Application.Sales.Queries.GetRevenueBreakdownQuery→FreshCart.Reporting.Application.Common.Models.PeriodSelectorFreshCart.Reporting.Application.Sales.Queries.GetSalesOverviewQuery→FreshCart.Reporting.Application.Common.Models.PeriodSelectorFreshCart.Reporting.Application.Sales.Queries.GetSalesTimeSeriesQuery→FreshCart.Reporting.Application.Common.Models.PeriodSelector
- Direction
- Reporting.Application.Sales.Queries uses Reporting.Application.Common.Models, so a change to Reporting.Application.Common.Models can break Reporting.Application.Sales.Queries, while a change to Reporting.Application.Sales.Queries can't break Reporting.Application.Common.Models.
- Position
- Below the diagonal: Reporting.Application.Sales.Queries uses a module listed above it, which is the healthy direction.
37→33 Reporting.Application.Sales.Queries uses Reporting.Application.Common.Abstractions✕
- Connections
- 5 pairs of types, where a type in Reporting.Application.Sales.Queries uses a type in Reporting.Application.Common.Abstractions.
- The types involved
FreshCart.Reporting.Application.Sales.Queries.GetRevenueBreakdownQueryHandler→FreshCart.Reporting.Application.Common.Abstractions.ISalesReadWarehouseFreshCart.Reporting.Application.Sales.Queries.GetSalesOverviewQueryHandler→FreshCart.Reporting.Application.Common.Abstractions.ISalesReadWarehouseFreshCart.Reporting.Application.Sales.Queries.GetSalesTimeSeriesQueryHandler→FreshCart.Reporting.Application.Common.Abstractions.ISalesReadWarehouseFreshCart.Reporting.Application.Sales.Queries.RevenueBreakdownDto→FreshCart.Reporting.Application.Common.Abstractions.RevenueByCategoryRowFreshCart.Reporting.Application.Sales.Queries.RevenueBreakdownDto→FreshCart.Reporting.Application.Common.Abstractions.RevenueByPaymentMethodRow
- Direction
- Reporting.Application.Sales.Queries uses Reporting.Application.Common.Abstractions, so a change to Reporting.Application.Common.Abstractions can break Reporting.Application.Sales.Queries, while a change to Reporting.Application.Sales.Queries can't break Reporting.Application.Common.Abstractions.
- Position
- Below the diagonal: Reporting.Application.Sales.Queries uses a module listed above it, which is the healthy direction.
38→12 Reporting.Infrastructure.Persistence.Warehouse uses Reporting.Domain.Invoices✕
- Connections
- 6 pairs of types, where a type in Reporting.Infrastructure.Persistence.Warehouse uses a type in Reporting.Domain.Invoices.
- The types involved
FreshCart.Reporting.Infrastructure.Persistence.Warehouse.InvoiceNumberSequence→FreshCart.Reporting.Domain.Invoices.InvoiceKindFreshCart.Reporting.Infrastructure.Persistence.Warehouse.InvoiceRecord→FreshCart.Reporting.Domain.Invoices.InvoiceAddressFreshCart.Reporting.Infrastructure.Persistence.Warehouse.InvoiceRecord→FreshCart.Reporting.Domain.Invoices.InvoiceKindFreshCart.Reporting.Infrastructure.Persistence.Warehouse.InvoiceRepository→FreshCart.Reporting.Domain.Invoices.InvoiceFreshCart.Reporting.Infrastructure.Persistence.Warehouse.InvoiceRepository→FreshCart.Reporting.Domain.Invoices.InvoiceKindFreshCart.Reporting.Infrastructure.Persistence.Warehouse.InvoiceRepository→FreshCart.Reporting.Domain.Invoices.InvoiceNumber
- Direction
- Reporting.Infrastructure.Persistence.Warehouse uses Reporting.Domain.Invoices, so a change to Reporting.Domain.Invoices can break Reporting.Infrastructure.Persistence.Warehouse, while a change to Reporting.Infrastructure.Persistence.Warehouse can't break Reporting.Domain.Invoices.
- Position
- Below the diagonal: Reporting.Infrastructure.Persistence.Warehouse uses a module listed above it, which is the healthy direction.
38→13 Reporting.Infrastructure.Persistence.Warehouse uses Reporting.Domain.Kpis✕
- Connections
- 2 pairs of types, where a type in Reporting.Infrastructure.Persistence.Warehouse uses a type in Reporting.Domain.Kpis.
- The types involved
FreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperCustomerReadWarehouse→FreshCart.Reporting.Domain.Kpis.TopEntityRankingFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperProductReadWarehouse→FreshCart.Reporting.Domain.Kpis.TopEntityRanking
- Direction
- Reporting.Infrastructure.Persistence.Warehouse uses Reporting.Domain.Kpis, so a change to Reporting.Domain.Kpis can break Reporting.Infrastructure.Persistence.Warehouse, while a change to Reporting.Infrastructure.Persistence.Warehouse can't break Reporting.Domain.Kpis.
- Position
- Below the diagonal: Reporting.Infrastructure.Persistence.Warehouse uses a module listed above it, which is the healthy direction.
38→14 Reporting.Infrastructure.Persistence.Warehouse uses Reporting.Domain.Sales✕
- Connections
- 6 pairs of types, where a type in Reporting.Infrastructure.Persistence.Warehouse uses a type in Reporting.Domain.Sales.
- The types involved
FreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperCustomerReadWarehouse→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperDeliveryReadWarehouse→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperProductReadWarehouse→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperSalesReadWarehouse→FreshCart.Reporting.Domain.Sales.AggregationBucketFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperSalesReadWarehouse→FreshCart.Reporting.Domain.Sales.ReportingPeriodFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperSalesReadWarehouse→FreshCart.Reporting.Domain.Sales.SalesSnapshot
- Direction
- Reporting.Infrastructure.Persistence.Warehouse uses Reporting.Domain.Sales, so a change to Reporting.Domain.Sales can break Reporting.Infrastructure.Persistence.Warehouse, while a change to Reporting.Infrastructure.Persistence.Warehouse can't break Reporting.Domain.Sales.
- Position
- Below the diagonal: Reporting.Infrastructure.Persistence.Warehouse uses a module listed above it, which is the healthy direction.
38→17 Reporting.Infrastructure.Persistence.Warehouse uses BuildingBlocks.Messaging.IntegrationEvents✕
- Connections
- 5 pairs of types, where a type in Reporting.Infrastructure.Persistence.Warehouse uses a type in BuildingBlocks.Messaging.IntegrationEvents.
- The types involved
FreshCart.Reporting.Infrastructure.Persistence.Warehouse.WarehouseProjectionWriter→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.DeliveryCompletedIntegrationEventFreshCart.Reporting.Infrastructure.Persistence.Warehouse.WarehouseProjectionWriter→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.DeliveryScheduledIntegrationEventFreshCart.Reporting.Infrastructure.Persistence.Warehouse.WarehouseProjectionWriter→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderConfirmedIntegrationEventFreshCart.Reporting.Infrastructure.Persistence.Warehouse.WarehouseProjectionWriter→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.OrderRefundedIntegrationEventFreshCart.Reporting.Infrastructure.Persistence.Warehouse.WarehouseProjectionWriter→FreshCart.BuildingBlocks.Messaging.IntegrationEvents.ProductCreatedIntegrationEvent
- Direction
- Reporting.Infrastructure.Persistence.Warehouse uses BuildingBlocks.Messaging.IntegrationEvents, so a change to BuildingBlocks.Messaging.IntegrationEvents can break Reporting.Infrastructure.Persistence.Warehouse, while a change to Reporting.Infrastructure.Persistence.Warehouse can't break BuildingBlocks.Messaging.IntegrationEvents.
- Position
- Below the diagonal: Reporting.Infrastructure.Persistence.Warehouse uses a module listed above it, which is the healthy direction.
38→33 Reporting.Infrastructure.Persistence.Warehouse uses Reporting.Application.Common.Abstractions✕
- Connections
- 11 pairs of types, where a type in Reporting.Infrastructure.Persistence.Warehouse uses a type in Reporting.Application.Common.Abstractions.
- The types involved
FreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperCustomerReadWarehouse→FreshCart.Reporting.Application.Common.Abstractions.CustomerAcquisitionSummaryFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperCustomerReadWarehouse→FreshCart.Reporting.Application.Common.Abstractions.ICustomerReadWarehouseFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperDeliveryReadWarehouse→FreshCart.Reporting.Application.Common.Abstractions.DeliveryPerformanceSummaryFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperDeliveryReadWarehouse→FreshCart.Reporting.Application.Common.Abstractions.IDeliveryReadWarehouseFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperProductReadWarehouse→FreshCart.Reporting.Application.Common.Abstractions.IProductReadWarehouseFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperProductReadWarehouse→FreshCart.Reporting.Application.Common.Abstractions.InventoryHealthSummaryFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperSalesReadWarehouse→FreshCart.Reporting.Application.Common.Abstractions.ISalesReadWarehouseFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperSalesReadWarehouse→FreshCart.Reporting.Application.Common.Abstractions.RevenueByCategoryRowFreshCart.Reporting.Infrastructure.Persistence.Warehouse.DapperSalesReadWarehouse→FreshCart.Reporting.Application.Common.Abstractions.RevenueByPaymentMethodRowFreshCart.Reporting.Infrastructure.Persistence.Warehouse.InvoiceRepository→FreshCart.Reporting.Application.Common.Abstractions.IInvoiceRepositoryFreshCart.Reporting.Infrastructure.Persistence.Warehouse.WarehouseProjectionWriter→FreshCart.Reporting.Application.Common.Abstractions.IProjectionWriter
- Direction
- Reporting.Infrastructure.Persistence.Warehouse uses Reporting.Application.Common.Abstractions, so a change to Reporting.Application.Common.Abstractions can break Reporting.Infrastructure.Persistence.Warehouse, while a change to Reporting.Infrastructure.Persistence.Warehouse can't break Reporting.Application.Common.Abstractions.
- Position
- Below the diagonal: Reporting.Infrastructure.Persistence.Warehouse uses a module listed above it, which is the healthy direction.
39→3 Delivery.Infrastructure.Persistence uses BuildingBlocks.Messaging.Events✕
- Connections
- 1 pair of types, where a type in Delivery.Infrastructure.Persistence uses a type in BuildingBlocks.Messaging.Events.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.MongoDeliveryUnitOfWork→FreshCart.BuildingBlocks.Messaging.Events.IntegrationEvent
- Direction
- Delivery.Infrastructure.Persistence uses BuildingBlocks.Messaging.Events, so a change to BuildingBlocks.Messaging.Events can break Delivery.Infrastructure.Persistence, while a change to Delivery.Infrastructure.Persistence can't break BuildingBlocks.Messaging.Events.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
39→6 Delivery.Infrastructure.Persistence uses Delivery.Domain.Deliveries✕
- Connections
- 1 pair of types, where a type in Delivery.Infrastructure.Persistence uses a type in Delivery.Domain.Deliveries.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.MongoDeliveryUnitOfWork→FreshCart.Delivery.Domain.Deliveries.Delivery
- Direction
- Delivery.Infrastructure.Persistence uses Delivery.Domain.Deliveries, so a change to Delivery.Domain.Deliveries can break Delivery.Infrastructure.Persistence, while a change to Delivery.Infrastructure.Persistence can't break Delivery.Domain.Deliveries.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
39→34 Delivery.Infrastructure.Persistence uses Delivery.Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Delivery.Infrastructure.Persistence uses a type in Delivery.Application.Abstractions.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.MongoDeliveryUnitOfWork→FreshCart.Delivery.Application.Abstractions.IDeliveryUnitOfWork
- Direction
- Delivery.Infrastructure.Persistence uses Delivery.Application.Abstractions, so a change to Delivery.Application.Abstractions can break Delivery.Infrastructure.Persistence, while a change to Delivery.Infrastructure.Persistence can't break Delivery.Application.Abstractions.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
40→6 Delivery.Infrastructure.Persistence.Repositories uses Delivery.Domain.Deliveries✕
- Connections
- 1 pair of types, where a type in Delivery.Infrastructure.Persistence.Repositories uses a type in Delivery.Domain.Deliveries.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoDeliveryRepository→FreshCart.Delivery.Domain.Deliveries.Delivery
- Direction
- Delivery.Infrastructure.Persistence.Repositories uses Delivery.Domain.Deliveries, so a change to Delivery.Domain.Deliveries can break Delivery.Infrastructure.Persistence.Repositories, while a change to Delivery.Infrastructure.Persistence.Repositories can't break Delivery.Domain.Deliveries.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→7 Delivery.Infrastructure.Persistence.Repositories uses Delivery.Domain.Slots✕
- Connections
- 1 pair of types, where a type in Delivery.Infrastructure.Persistence.Repositories uses a type in Delivery.Domain.Slots.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoSlotRepository→FreshCart.Delivery.Domain.Slots.DeliverySlot
- Direction
- Delivery.Infrastructure.Persistence.Repositories uses Delivery.Domain.Slots, so a change to Delivery.Domain.Slots can break Delivery.Infrastructure.Persistence.Repositories, while a change to Delivery.Infrastructure.Persistence.Repositories can't break Delivery.Domain.Slots.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→8 Delivery.Infrastructure.Persistence.Repositories uses Delivery.Domain.Zones✕
- Connections
- 2 pairs of types, where a type in Delivery.Infrastructure.Persistence.Repositories uses a type in Delivery.Domain.Zones.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoZoneRepository→FreshCart.Delivery.Domain.Zones.DeliveryZoneFreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoZoneRepository→FreshCart.Delivery.Domain.Zones.GeoCoordinate
- Direction
- Delivery.Infrastructure.Persistence.Repositories uses Delivery.Domain.Zones, so a change to Delivery.Domain.Zones can break Delivery.Infrastructure.Persistence.Repositories, while a change to Delivery.Infrastructure.Persistence.Repositories can't break Delivery.Domain.Zones.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→29 Delivery.Infrastructure.Persistence.Repositories uses Delivery.Application.Shipments✕
- Connections
- 1 pair of types, where a type in Delivery.Infrastructure.Persistence.Repositories uses a type in Delivery.Application.Shipments.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoPendingShipmentRepository→FreshCart.Delivery.Application.Shipments.PendingShipment
- Direction
- Delivery.Infrastructure.Persistence.Repositories uses Delivery.Application.Shipments, so a change to Delivery.Application.Shipments can break Delivery.Infrastructure.Persistence.Repositories, while a change to Delivery.Infrastructure.Persistence.Repositories can't break Delivery.Application.Shipments.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→34 Delivery.Infrastructure.Persistence.Repositories uses Delivery.Application.Abstractions✕
- Connections
- 5 pairs of types, where a type in Delivery.Infrastructure.Persistence.Repositories uses a type in Delivery.Application.Abstractions.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoDeliveryRepository→FreshCart.Delivery.Application.Abstractions.IDeliveryRepositoryFreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoDriverRepository→FreshCart.Delivery.Application.Abstractions.IDriverRepositoryFreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoPendingShipmentRepository→FreshCart.Delivery.Application.Abstractions.IPendingShipmentRepositoryFreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoSlotRepository→FreshCart.Delivery.Application.Abstractions.ISlotRepositoryFreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoZoneRepository→FreshCart.Delivery.Application.Abstractions.IZoneRepository
- Direction
- Delivery.Infrastructure.Persistence.Repositories uses Delivery.Application.Abstractions, so a change to Delivery.Application.Abstractions can break Delivery.Infrastructure.Persistence.Repositories, while a change to Delivery.Infrastructure.Persistence.Repositories can't break Delivery.Application.Abstractions.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
40→39 Delivery.Infrastructure.Persistence.Repositories uses Delivery.Infrastructure.Persistence✕
- Connections
- 5 pairs of types, where a type in Delivery.Infrastructure.Persistence.Repositories uses a type in Delivery.Infrastructure.Persistence.
- The types involved
FreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoDeliveryRepository→FreshCart.Delivery.Infrastructure.Persistence.DeliveryMongoContextFreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoDriverRepository→FreshCart.Delivery.Infrastructure.Persistence.DeliveryMongoContextFreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoPendingShipmentRepository→FreshCart.Delivery.Infrastructure.Persistence.DeliveryMongoContextFreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoSlotRepository→FreshCart.Delivery.Infrastructure.Persistence.DeliveryMongoContextFreshCart.Delivery.Infrastructure.Persistence.Repositories.MongoZoneRepository→FreshCart.Delivery.Infrastructure.Persistence.DeliveryMongoContext
- Direction
- Delivery.Infrastructure.Persistence.Repositories uses Delivery.Infrastructure.Persistence, so a change to Delivery.Infrastructure.Persistence can break Delivery.Infrastructure.Persistence.Repositories, while a change to Delivery.Infrastructure.Persistence.Repositories can't break Delivery.Infrastructure.Persistence.
- Position
- Below the diagonal: Delivery.Infrastructure.Persistence.Repositories 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 238 | High / Critical |
| A05:2025 — Injection | 51 | High / Critical |
| A07:2025 — Authentication Failures | 47 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 16 | Medium |
Roadmap
Top priorities: Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Resolve the 44 Leaked secret finding(s) in Secret Scanning — start with REDACTED (21), REDACTED (21), REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +3.9 pts | Medium | A11y enforcement |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +3.4 pts | Medium | Visual & motion safety |
| Resolve the 44 Leaked secret finding(s) in Secret Scanning — start with REDACTED (21), REDACTED (21), REDACTED (2). | +2.6 pts | Medium | Secret Scanning |
| Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly. | +2.4 pts | Medium | Schema migrations |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.1 pts | Medium | Page structure |
| Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. | +0.6 pts | Low | Test Distribution |
| Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets. | +0.8 pts | Medium | Security & performance tooling |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +0.8 pts | Medium | DR & Backup |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 2.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 109 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 — 109 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, 476 of 502 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 .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — tests/e2e/ (@playwright/test) — a gap in the analyzer, not something this repository is missing. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D10 Test 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. The 748 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 5 test source file(s) (.ts) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — 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. Test reliability is scored on the 1 tier(s) that produced comparable repeat runs; 1 tier(s) did not, and are excluded from the measurement rather than counted (unit: measured (0 flaky); integration: not included — too large to re-run within its budget). This is OUR limitation, not a defect in the repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `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.
- 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-contributor repository — bus factor is not applicable (1 contributor(s) across 69 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. 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.
- D23 Boundary Type-Coupling — 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. Large codebase (25,423 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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"]`.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/ApiGateways/FreshCart.Gateway.Yarp/Middleware/AntiforgeryValidationMiddleware.cs`, `src/AspireAppHost/FreshCart.AppHost/MongoDirectReadinessCheck.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/Outbox/OutboxPublisher.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/LoggingBehavior.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/ValidationBehavior.cs`, … (+156 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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.
- D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Deploy/helm/basket/templates/deployment.yaml:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2 and 2 more did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- 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 AspireAppHost (src/AspireAppHost/FreshCart.AppHost/FreshCart.AppHost.csproj). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
- 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.
- 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.
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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
25 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 2 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with DependencyInjection.cs, DapperSalesReadWarehouse.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (22 lines × 2) finding(s) in Code Duplication — start with SqlConnectionFactory.cs, ClaimsPrincipalExtensions.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (17 lines × 3) finding(s) in Code Duplication — start with DependencyInjection.cs (2). — One of this dimension's main actionable groups (2 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
46 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
3 of 126 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with CancelOrderOnPaymentFailureActivity.cs, CancelOrderOnStockFailureActivity.cs, ConfirmOrderActivity.cs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D7 · Architectural Integrity
All 4 mechanizable ADR(s) are enforced: 4 by analyzers, 0 by tests. Cycles found: 0.
D9 · Test Distribution
752 test methods: 146 unit, 602 integration, 0 BDD, 4 e2e. The JavaScript/TypeScript suite contributes 4 `it`/`test` case(s) across 3 test file(s) declaring at least one beside 748 .NET test method(s); its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, 14 mock references across 748 tests. Measured on the C# suite only — at least 5 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
Only 1 of 2 test tiers measured — the score covers those alone. 0 flaky across 1 measured tier(s). unit: measured (0 flaky); integration: not included — too large to re-run within its budget.
D13 · Secret Scanning
22 secret(s) detected.
What to do
- Resolve the 44 Leaked secret finding(s) in Secret Scanning — start with REDACTED (21), REDACTED (21), REDACTED (2). — One of this dimension's main actionable groups (44 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 90 direct `PackageReference`(s), and 160 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
4 deducted debt markers + 4 dead symbols across 25423 LoC in the .NET projects (0.2/KLoC) → score 9.6.
What to do
- Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 4 Dead code finding(s) in Explicit Debt — start with Driver.cs (2), IDriverRepository.cs, IAgentAvailabilityRegistry.cs. — One of this dimension's main actionable groups (4 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
46 projects, 965 source files, 39251 hand-written lines of code (25423 production / 13828 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), 86 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 25 document(s) read across 33 unit(s).
D20 · ADR Quality
0 of 4 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D21 · Naming Consistency
0 naming inconsistencies among 233 declarations measured against a convention their peers follow.
D24 · Comment Value
0 of 157 judged comments only repeat the code they sit on (0.0 %).
D26 · Project Cohesion
0 of 46 projects flagged as possibly oversized/incoherent.
D27 · Navigability
91 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
51 finding(s): 0 critical, 40 high, 5 medium, 6 low. 27 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 351 file(s) — `.github/scripts/freshcart-e2e-stack.sh` (lines 2–144), `.github/scripts/test-freshcart-e2e-stack.sh` (lines 147–155), `deploy/helm/basket/Chart.yaml`, `deploy/helm/basket/templates/configmap.yaml`, `REDACTED`, … (+346 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 184 of those file(s) — `src/AspireAppHost/FreshCart.AppHost/MongoDirectReadinessCheck.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/Outbox/OutboxPublisher.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks.Tests/Security/OutboundUrlAllowListHandlerTests.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/LoggingBehavior.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/ValidationBehavior.cs`, … (+179 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 2 of those file(s) — `src/Services/Catalog/FreshCart.Catalog.Tests/Products/ProductQueryFiltersTests.cs`, `src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 27 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (27 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 2 ecosystem(s) that were scanned (npm,osv). Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
238 finding(s): 0 critical, 23 high, 188 medium, 27 low.
What to do
- Resolve the 188 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (109), REDACTED (26), REDACTED (12). — One of this dimension's main actionable groups (188 warning-level).
- Resolve the 23 High IaC finding(s) in IaC & Container Security — start with REDACTED (13), REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (23 issue-level).
- Resolve the 27 Low IaC finding(s) in IaC & Container Security — start with REDACTED (14), REDACTED (13). — One of this dimension's main actionable groups (27 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 148 of the 748 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 13 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D40 · Network Egress Confinement
Kubernetes workloads are covered by a network policy that restricts egress.
D41 · Kernel & Syscall Confinement
12/12 workload(s) run every container under a seccomp profile; 0/12 declare an AppArmor/SELinux profile.
What to do
- Improve Kernel & Syscall Confinement — currently 8.0/10. — 12/12 workload(s) run every container under a seccomp profile; 0/12 declare an AppArmor/SELinux profile.
D42 · Runtime Threat Enforcement
1/2 runtime-enforcement controls present (threat detection, admission control).
What to do
- Improve Runtime Threat Enforcement — currently 8.0/10. — 1/2 runtime-enforcement controls present (threat detection, admission control).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — REDACTED:2
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×6) — REDACTED:654, REDACTED:1055, REDACTED:1069, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `.mini-card` moves (`transition: transform .2s,border-color .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:59
- `.sub-tab-btn.active` sets color: #fff on background-color: #4f8cff — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:46
- `.af-n` sets color: #6b7094 on background-color: #0f1117 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:86
- `.steps li::before` sets color: #fff on background-color: #4f8cff — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — REDACTED:150
- <span> moves — its inline style sets `animation: pulse 1.8s infinite ease-in-out` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — REDACTED:246
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 1 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX2 · Stateful singletons
AX3 · Project dependency cycles
- The namespaces FreshCart.Delivery.Application.Abstractions ↔ FreshCart.Delivery.Application.Shipments depend on each other. The lightest dependency in the cycle is FreshCart.Delivery.Application.Abstractions → FreshCart.Delivery.Application.Shipments (FreshCart.Delivery.Application.Abstractions.IPendingShipmentRepository → FreshCart.Delivery.Application.Shipments.PendingShipment, 1 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. — src/Services/Delivery/FreshCart.Delivery.Application/Abstractions/IPendingShipmentRepository.cs:1
- The namespaces FreshCart.Notification.Api.Channels ↔ FreshCart.Notification.Api.Hubs ↔ FreshCart.Notification.Api.Notifications depend on each other. The lightest dependency in the cycle is FreshCart.Notification.Api.Channels → FreshCart.Notification.Api.Hubs (FreshCart.Notification.Api.Channels.SignalRNotificationChannel → FreshCart.Notification.Api.Hubs.NotificationHub, 1 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. — src/Services/Notification/FreshCart.Notification.Api/Channels/SignalRNotificationChannel.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.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX7 · Slice cohesion
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls
C3 · Audit Trail
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
- `MartenBasketUnitOfWork.CommitCheckoutAsync` saves `ArchivedBasket`, `OutboxMessage` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenBasketUnitOfWork.cs:13
- `GenerateInvoiceCommandHandler.Handle` saves `IDocumentStore`, `IInvoiceRepository` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/Services/Reporting/FreshCart.Reporting.Application/Invoices/Commands/GenerateInvoice/GenerateInvoiceCommandHandler.cs:26
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
- `RefreshToken` reads `DateTimeOffset.UtcNow` inside `IsActive` — while this repo already declares a clock seam that the rest of the code injects. This site bypasses it, so the rule it feeds still cannot be exercised at a chosen instant, and two reads within one operation can disagree. Take the instant through the seam the repo already has. — src/Services/Identity/FreshCart.Identity.Domain/RefreshTokens/RefreshToken.cs:36
What to do
- Route the listed sites through the clock abstraction this repo already declares, so the domain's rules can be exercised at a chosen instant.
DM2 · Strongly-typed ids
- `Order.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:24
- `Order.ReservationId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:50
- `Order.PaymentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:52
- `OrderCancelledDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderCancelledDomainEvent.cs:6
- `OrderCancelledDomainEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderCancelledDomainEvent.cs:7
- `OrderConfirmedDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderConfirmedDomainEvent.cs:7
- `OrderConfirmedDomainEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderConfirmedDomainEvent.cs:9
- `OrderRefundedDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderRefundedDomainEvent.cs:6
- `OrderSubmittedDomainEvent.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderSubmittedDomainEvent.cs:6
- `OrderSubmittedDomainEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderSubmittedDomainEvent.cs:7
- `Delivery.OrderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:39
- `Delivery.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:41
- `Delivery.DriverId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:51
- `DeliverySlot.ZoneId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/Delivery/FreshCart.Delivery.Domain/Slots/DeliverySlot.cs:52
- `ChatSession.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Domain/ChatSession.cs:32
- `ChatSession.AgentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Domain/ChatSession.cs:36
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM3 · Integration-event coupling
DM4 · Rich vs anemic model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
- `ApplicationRole` (domain layer) names `IdentityRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/Services/Identity/FreshCart.Identity.Domain/Roles/ApplicationRole.cs:14
- `ApplicationUser` (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. — src/Services/Identity/FreshCart.Identity.Domain/Users/ApplicationUser.cs:14
- `ProductReview` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:15
- `ProductReview` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×3) — src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:32, src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:35, src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:38
- `ProductReview` (domain layer) names `BsonIgnoreIfNullAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:39, src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:42
- `PurchaseRecord` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Services/Reviews/FreshCart.Reviews.Api/Domain/PurchaseRecord.cs:14
- `PurchaseRecord` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/Services/Reviews/FreshCart.Reviews.Api/Domain/PurchaseRecord.cs:23
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
- FreshCart.Delivery.Domain.Zones.GeoCoordinate's [Latitude, Longitude] are built independently in FreshCart.Delivery.Infrastructure.Geocoding.DeterministicGeocodingAdapter, FreshCart.Delivery.Infrastructure.Seeding.DevelopmentSeedData — the same reading, produced twice. Two producers can disagree without either looking wrong on its own: whichever population, filter or rounding one of them applies, the other need not, and nothing compares them. Give the measurement ONE producer and let the other call it.
What to do
- Give each measurement ONE producer — the others call it. Centralising the judgement is not enough on its own: two producers of the same numbers can disagree while every rule reading them is correct.
ED1 · Handler temporal coupling
- `CaptureOrderPaymentConsumer.Consume` makes a synchronous remote call (an HTTP call via `IPaymentClient.CapturePaymentAsync`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler. — src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Consumers/CaptureOrderPaymentConsumer.cs:19
- `ReserveOrderStockConsumer.Consume` makes a synchronous remote call (a gRPC call via `IInventoryClient.ReserveStockAsync`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler. — src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Consumers/ReserveOrderStockConsumer.cs:19
What to do
- Remove synchronous remote calls from message handlers — react by publishing further messages, so services stay temporally decoupled.
ED2 · Event/command shape
ED3 · Event naming
ED4 · Outbox / dual-write
- `CreateProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandHandler.cs:26
- `UpdateProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandHandler.cs:24
- `CatalogDataSeeder.StartAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Services/Catalog/FreshCart.Catalog.Api/Seeding/CatalogDataSeeder.cs:19
- `MarkOrderStockReservedActivity.Execute` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Activities/MarkOrderStockReservedActivity.cs:22
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
ED5 · Idempotency
- `SignIn.SignInCommandHandler.Handle` mutates persistent state (a repository write) and inserts a new `RefreshToken` with no identity assigned (the store or its constructor generates a new one) (line 40), so a re-run inserts another one. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Services/Identity/FreshCart.Identity.Application/Authentication/Commands/SignIn/SignInCommandHandler.cs:26
What to do
- Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A placeholder e-mail address ("demo@freshcart.test") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:30
- A placeholder e-mail address ("support@freshcart.test") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:31
- A placeholder e-mail address ("admin@freshcart.test") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:32
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Add a README to the 32 of 32 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 4) — reach 8 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md links to `gitops/`, but `gitops` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:266
What to do
- Reconcile the README with reality: README.md links to `gitops/`, but `gitops` does not exist.
P1 · CI/CD gates
P2 · Observability
- Only 26/27 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 27, 14 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
P7 · Outbound HTTP resilience
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. (×4) — src/Services/Pricing/FreshCart.Pricing.Grpc/Persistence/PricingDatabaseInitializer.cs:26, src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/OrderingDatabaseInitializer.cs:22, src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/ReportingWarehouseInitializer.cs:30, …
What to do
- Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly.
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- Set: Content-Security-Policy, Cross-Origin-Embedder-Policy, Cross-Origin-Opener-Policy, Cross-Origin-Resource-Policy, Permissions-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.) — src/BuildingBlocks/FreshCart.BuildingBlocks/Security/SecurityHeadersMiddleware.cs:24
What to do
- Add Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
X1 · Async correctness
- Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — src/Services/Reporting/FreshCart.Reporting.Application/Sales/Queries/GetRevenueBreakdownQueryHandler.cs:20
What to do
- Sync-over-async (deadlock risk) through `.Result`
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 285/300 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. (×4) — src/Services/Catalog/FreshCart.Catalog.Api/DependencyInjection.cs:122, src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:161, src/Services/Notification/FreshCart.Notification.Api/Configuration/NotificationHealthChecks.cs:44, …
- No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×9) — REDACTED:22, REDACTED:55, src/Services/Inventory/FreshCart.Inventory.Api/Grpc/InventoryGrpcService.cs:14, …
- Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`). — src/Services/Delivery/FreshCart.Delivery.Api/Configuration/DeliveryHealthChecks.cs:41
- No CancellationToken parameter, and the token `httpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `httpContext.RequestAborted` on, or take a CancellationToken. — src/ApiGateways/FreshCart.Gateway.Yarp/Middleware/AntiforgeryValidationMiddleware.cs:83
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
X5 · Nullable reference types
- ~0.2 `!` suppressions per 1k syntax nodes — 31 suppression(s) across the 125649 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 92% | Exemplary | Strongest area. |
| Architecture | 84% | Strong | Solid. |
| Maturity | 82% | Strong | Solid. |
| Readiness | 63% | Adequate — gated by D13, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Adequate — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 71% | Adequate — gated by DM2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 73% | Strong | Solid. |
| Accessibility | 60% | Adequate | Largest drag on the score — prioritise here. |
| Performance | 77% | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 12 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- 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.
Not included — 22 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence 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.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D25 ADR Conformance — None of 4 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D32 Data Compliance (PII/GDPR) — 161 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D8 Code Coverage — Coverage not measured — .NET and JavaScript/TypeScript suite
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): an event-store package (Marten/EventStore); an append-only event-store seam (IEventStore/Append-of-events)
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- 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
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — 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 — 129 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
- 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: ApplicationRole src/Services/Identity/FreshCart.Identity.Domain/Roles/ApplicationRole.cs:14
- Domain depends on infrastructure: ApplicationUser src/Services/Identity/FreshCart.Identity.Domain/Users/ApplicationUser.cs:14
- Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:15
- Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:32
- Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:35
- Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:38
- Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:39
- Domain depends on infrastructure: ProductReview src/Services/Reviews/FreshCart.Reviews.Api/Domain/ProductReview.cs:42
- Domain depends on infrastructure: PurchaseRecord src/Services/Reviews/FreshCart.Reviews.Api/Domain/PurchaseRecord.cs:14
- Domain depends on infrastructure: PurchaseRecord src/Services/Reviews/FreshCart.Reviews.Api/Domain/PurchaseRecord.cs:23
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj Directory.Build.props:23
- NoWarnInCsproj Directory.Build.props:23
- NoWarnInCsproj Directory.Build.props:23
- NoWarnInCsproj Directory.Build.props:26
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dual write (no outbox): CreateProductCommandHandler.Handle src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandHandler.cs:26
- Dual write (no outbox): UpdateProductCommandHandler.Handle src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/UpdateProduct/UpdateProductCommandHandler.cs:24
- Dual write (no outbox): CatalogDataSeeder.StartAsync src/Services/Catalog/FreshCart.Catalog.Api/Seeding/CatalogDataSeeder.cs:19
- Dual write (no outbox): MarkOrderStockReservedActivity.Execute src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Activities/MarkOrderStockReservedActivity.cs:22
- Namespace dependency cycle src/Services/Delivery/FreshCart.Delivery.Application/Abstractions/IPendingShipmentRepository.cs:1
- Namespace dependency cycle src/Services/Notification/FreshCart.Notification.Api/Channels/SignalRNotificationChannel.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 271 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
- Heading level jumps from h2 to h4 REDACTED:654
- Heading level jumps from h2 to h4 REDACTED:1055
- Heading level jumps from h2 to h4 REDACTED:1069
- Heading level jumps from h2 to h4 REDACTED:1084
- Heading level jumps from h2 to h4 REDACTED:1098
- Heading level jumps from h2 to h4 REDACTED:1717
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Async method without CancellationToken: CreateBrokerProbeConnectionAsync src/Services/Catalog/FreshCart.Catalog.Api/DependencyInjection.cs:122
- Async method without CancellationToken: CreateBrokerProbeConnectionAsync src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:161
- Async method without CancellationToken: CreateBrokerProbeConnectionAsync src/Services/Notification/FreshCart.Notification.Api/Configuration/NotificationHealthChecks.cs:44
- Async method without CancellationToken: CreateBrokerProbeConnectionAsync src/Services/Reviews/FreshCart.Reviews.Api/DependencyInjection.cs:84
- Async method without CancellationToken: WriteAntiforgeryFailureAsync src/ApiGateways/FreshCart.Gateway.Yarp/Middleware/AntiforgeryValidationMiddleware.cs:83
- Dead code: Deactivate src/Services/Delivery/FreshCart.Delivery.Domain/Drivers/Driver.cs:36
- Dead code: Reactivate src/Services/Delivery/FreshCart.Delivery.Domain/Drivers/Driver.cs:38
- Dead code: HasAnyDriversAsync src/Services/Delivery/FreshCart.Delivery.Application/Abstractions/IDriverRepository.cs:18
- Dead code: CountOnlineAsync src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Assignment/IAgentAvailabilityRegistry.cs:19
- Schema created with EnsureCreated() (no migration path) src/Services/Pricing/FreshCart.Pricing.Grpc/Persistence/PricingDatabaseInitializer.cs:26
- Schema created with EnsureCreated() (no migration path) src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/OrderingDatabaseInitializer.cs:22
- Schema created with EnsureCreated() (no migration path) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/ReportingWarehouseInitializer.cs:30
- Schema created with EnsureCreated() (no migration path) src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:54
- Low cohesion: CancelOrderOnPaymentFailureActivity (LCOM4 4) src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Activities/CancelOrderOnPaymentFailureActivity.cs:14
- Low cohesion: CancelOrderOnStockFailureActivity (LCOM4 4) src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Activities/CancelOrderOnStockFailureActivity.cs:13
- Low cohesion: ConfirmOrderActivity (LCOM4 4) src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Activities/ConfirmOrderActivity.cs:13
- Animation without a prefers-reduced-motion guard REDACTED:59
- Animation without a prefers-reduced-motion guard REDACTED:246
- Low contrast colour pair in CSS (3.2:1) REDACTED:46
- Low contrast colour pair in CSS (3.2:1) REDACTED:150
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:162
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:17
- Duplicated block (22 lines × 2) src/Services/Inventory/FreshCart.Inventory.Api/Repositories/SqlConnectionFactory.cs:41
- Duplicated block (22 lines × 2) src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Authentication/ClaimsPrincipalExtensions.cs:17
- Duplicated block (17 lines × 3) src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:163
- Duplicated block (17 lines × 3) src/Services/Ordering/FreshCart.Ordering.Application/DependencyInjection.cs:13
- Duplicated block (9 lines × 2) src/Services/Ordering/FreshCart.Ordering.Application/Orders/Dtos/OrderDetailDto.cs:17
- Duplicated block (9 lines × 2) src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Persistence/SupportChatGuidSerialization.cs:18
- Duplicated block (5 lines × 2) src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandHandler.cs:35
- Duplicated block (5 lines × 2) src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Authentication/SupportUserIdProvider.cs:17
- One operation mutates 2 aggregates: MartenBasketUnitOfWork.CommitCheckoutAsync src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenBasketUnitOfWork.cs:13
- One operation mutates 2 aggregates: GenerateInvoiceCommandHandler.Handle src/Services/Reporting/FreshCart.Reporting.Application/Invoices/Commands/GenerateInvoice/GenerateInvoiceCommandHandler.cs:26
- Temporal coupling in handler: CaptureOrderPaymentConsumer.Consume src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Consumers/CaptureOrderPaymentConsumer.cs:19
- Temporal coupling in handler: ReserveOrderStockConsumer.Consume src/Services/Ordering/FreshCart.Ordering.Application/Checkout/Consumers/ReserveOrderStockConsumer.cs:19
- Page without a main landmark REDACTED:2
- Low contrast colour pair in CSS (3.9:1) REDACTED:86
- Accessibility enforcement below the top rung
- REDACTED
- Duplicated block (28–29 lines × 2) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperProductReadWarehouse.cs:15
- Duplicated block (28 lines × 2) src/Services/Identity/FreshCart.Identity.Application/Account/Commands/DisableMultiFactor/DisableMultiFactorCommandHandler.cs:21
- Duplicated block (25 lines × 2) src/Services/Basket/FreshCart.Basket.Api/Pricing/PricingGrpcChannelFactory.cs:21
- Duplicated block (22 lines × 3) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:17
- Duplicated block (13–21 lines × 2) src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/MassTransit/MessageBrokerExtensions.cs:31
- Duplicated block (20–21 lines × 2) src/ApiGateways/FreshCart.Gateway.Yarp/Configuration/GatewayAuthenticationConfiguration.cs:35
- Duplicated block (17 lines × 2) src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs:25
- Duplicated block (14 lines × 4) src/Services/Basket/FreshCart.Basket.Api/DependencyInjection.cs:170
- Duplicated block (14 lines × 2) src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:41
- Duplicated block (8–15 lines × 2) src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/BasketCheckoutStartedIntegrationEvent.cs:12
- Duplicated block (11 lines × 2) src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:26
- Duplicated block (10 lines × 3) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:92
- Duplicated block (12 lines × 2) src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs:21
- Duplicated block (10 lines × 4) src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/DapperSalesReadWarehouse.cs:33
- Duplicated block (16 lines × 2) src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/MassTransit/MessageBrokerExtensions.cs:72
- Duplicated block (6 lines × 2) src/Services/Payment/FreshCart.Payment.Application/Payments/Commands/CapturePayment/CapturePaymentCommandHandler.cs:133
- Duplicated block (8 lines × 2) src/Services/Identity/FreshCart.Identity.Application/Account/Commands/DisableMultiFactor/DisableMultiFactorCommandValidator.cs:9
- Domain type reads the wall clock: RefreshToken src/Services/Identity/FreshCart.Identity.Domain/RefreshTokens/RefreshToken.cs:36
- Non-idempotent mutation: SignIn.SignInCommandHandler.Handle src/Services/Identity/FreshCart.Identity.Application/Authentication/Commands/SignIn/SignInCommandHandler.cs:26
- Sync-over-async (deadlock risk) through `.Result` src/Services/Reporting/FreshCart.Reporting.Application/Sales/Queries/GetRevenueBreakdownQueryHandler.cs:20
- Async delegate without CancellationToken: AddDeliveryHealthChecks src/Services/Delivery/FreshCart.Delivery.Api/Configuration/DeliveryHealthChecks.cs:41
Minor — 86 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
- Primitive id on a domain type: Order.CustomerId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:24
- Primitive id on a domain type: Order.ReservationId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:50
- Primitive id on a domain type: Order.PaymentId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:52
- Primitive id on a domain type: OrderCancelledDomainEvent.OrderId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderCancelledDomainEvent.cs:6
- Primitive id on a domain type: OrderCancelledDomainEvent.CustomerId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderCancelledDomainEvent.cs:7
- Primitive id on a domain type: OrderConfirmedDomainEvent.OrderId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderConfirmedDomainEvent.cs:7
- Primitive id on a domain type: OrderConfirmedDomainEvent.CustomerId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderConfirmedDomainEvent.cs:9
- Primitive id on a domain type: OrderRefundedDomainEvent.OrderId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderRefundedDomainEvent.cs:6
- Primitive id on a domain type: OrderSubmittedDomainEvent.OrderId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderSubmittedDomainEvent.cs:6
- Primitive id on a domain type: OrderSubmittedDomainEvent.CustomerId src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderSubmittedDomainEvent.cs:7
- Primitive id on a domain type: Delivery.OrderId src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:39
- Primitive id on a domain type: Delivery.CustomerId src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:41
- Primitive id on a domain type: Delivery.DriverId src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/Delivery.cs:51
- Primitive id on a domain type: DeliverySlot.ZoneId src/Services/Delivery/FreshCart.Delivery.Domain/Slots/DeliverySlot.cs:52
- Primitive id on a domain type: ChatSession.CustomerId src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Domain/ChatSession.cs:32
- Primitive id on a domain type: ChatSession.AgentId src/Services/CustomerSupport/FreshCart.CustomerSupport.Api/Domain/ChatSession.cs:36
- Duplicated predicate src/Services/Inventory/FreshCart.Inventory.Api/Repositories/SqlConnectionFactory.cs:49
- Duplicated predicate src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:50
- Duplicated predicate src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs:37
- Duplicated predicate src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs:36
- Duplicated predicate src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutCommandHandler.cs:34
- Duplicated predicate src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:42
- Duplicated predicate src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:44
- Duplicated predicate src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs:45
- Duplicated predicate src/Services/Basket/FreshCart.Basket.Api/Persistence/MartenOutboxStore.cs:21
- Duplicated predicate src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs:39
- Duplicated predicate src/BuildingBlocks/FreshCart.ServiceDefaults/DevelopmentCertificateValidation.cs:30
- Duplicated predicate src/Services/Catalog/FreshCart.Catalog.Api/Features/Products/CreateProduct/CreateProductCommandValidator.cs:32
- Mock-dominated test: SeedsCategoriesBrandsAndProductsOnFirstDevelopmentStart src/Services/Catalog/FreshCart.Catalog.Tests/Seeding/CatalogDataSeederTests.cs:34
- Mock-dominated test: SkipsSeedingWhenTheCatalogAlreadyContainsCategoriesSoRestartsNeverDuplicate src/Services/Catalog/FreshCart.Catalog.Tests/Seeding/CatalogDataSeederTests.cs:60
- Mock-dominated test: ArchiveOutboxMessageAndLiveBasketDeletionRideOneUnitOfWorkCommit src/Services/Basket/FreshCart.Basket.Tests/Features/Checkout/CheckoutCommandHandlerTests.cs:78
- Mock-dominated test: BasketIsRepricedBeforeTheCommitAndTheCacheIsEvictedAfterIt src/Services/Basket/FreshCart.Basket.Tests/Features/Checkout/CheckoutCommandHandlerTests.cs:97
- Mock-dominated test: SchedulesADeliveryAndStagesTheScheduledEventForADeliverableOrder src/Services/Delivery/FreshCart.Delivery.Tests/Application/OrderConfirmedConsumerTests.cs:57
- Mock-dominated test: SkipsADigitalOnlyOrderWithoutSchedulingOrStaging src/Services/Delivery/FreshCart.Delivery.Tests/Application/OrderConfirmedConsumerTests.cs:79
- Mock-dominated test: IsIdempotentWhenADeliveryAlreadyExistsForTheOrder src/Services/Delivery/FreshCart.Delivery.Tests/Application/OrderConfirmedConsumerTests.cs:119
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Placeholder data left in code src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:30
- Placeholder data left in code src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:31
- Placeholder data left in code src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:32
- Silent fallback default on configuration miss src/ApiGateways/FreshCart.Gateway.Yarp/Configuration/GatewayCorsConfiguration.cs:22
- Silent fallback default on configuration miss src/ApiGateways/FreshCart.Gateway.Yarp/Configuration/GatewayForwardedHeadersConfiguration.cs:34
- Partial data-retention evidence
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- Measurement [Latitude, Longitude] produced in 2 places
- README/code drift README.md:266
- Logging is not universal
- No performance benchmarks
- Security headers incomplete src/BuildingBlocks/FreshCart.BuildingBlocks/Security/SecurityHeadersMiddleware.cs:24
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
- Silent fallback default in catch src/Services/Notification/FreshCart.Notification.Api/Notifications/Mongo/MongoNotificationStore.cs:66
Minor — 16 finding(s)
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Off the main sequence: FreshCart.BuildingBlocks.Messaging src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/FreshCart.BuildingBlocks.Messaging.csproj:1
- Off the main sequence: FreshCart.BuildingBlocks src/BuildingBlocks/FreshCart.BuildingBlocks/FreshCart.BuildingBlocks.csproj:1
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-d92bbe81b50a4fb98432e1b6d6218b50/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-d92bbe81b50a4fb98432e1b6d6218b50/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 . | 51 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 238 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 161 file(s) — `src/ApiGateways/FreshCart.Gateway.Yarp/Middleware/AntiforgeryValidationMiddleware.cs`, `src/AspireAppHost/FreshCart.AppHost/MongoDirectReadinessCheck.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/Outbox/OutboxPublisher.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/LoggingBehavior.cs`, `src/BuildingBlocks/FreshCart.BuildingBlocks/Behaviors/ValidationBehavior.cs`, … (+156 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 | 0 | artifacts/raw/trivy-fs.json |
Appendix C — Personal-data map
Email — 23 field(s)
- DownstreamPrincipal.Email src/ApiGateways/FreshCart.Gateway.Yarp/Auth/DownstreamPrincipal.cs:10
- BasketCheckoutStartedIntegrationEvent.CustomerEmail src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/BasketCheckoutStartedIntegrationEvent.cs:9
- OrderPlacedIntegrationEvent.CustomerEmail src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/OrderPlacedIntegrationEvent.cs:9
- CheckoutCommand.CustomerEmail src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutCommand.cs:8
- CurrentUserResponse.Email src/Services/Identity/FreshCart.Identity.Api/Endpoints/Account/CurrentUserResponse.cs:8
- AuthenticationProfileDto.Email src/Services/Identity/FreshCart.Identity.Api/Endpoints/Authentication/AuthenticationProfileDto.cs:8
- SignInRequest.Email src/Services/Identity/FreshCart.Identity.Api/Endpoints/Authentication/SignInRequest.cs:7
- SignUpRequest.Email src/Services/Identity/FreshCart.Identity.Api/Endpoints/Authentication/SignUpRequest.cs:8
- SignUpResponse.Email src/Services/Identity/FreshCart.Identity.Api/Endpoints/Authentication/SignUpResponse.cs:8
- SignInCommand.Email src/Services/Identity/FreshCart.Identity.Application/Authentication/Commands/SignIn/SignInCommand.cs:11
- SignUpCommand.Email src/Services/Identity/FreshCart.Identity.Application/Authentication/Commands/SignUp/SignUpCommand.cs:11
- SignUpResult.Email src/Services/Identity/FreshCart.Identity.Application/Authentication/Commands/SignUp/SignUpResult.cs:10
- AuthenticationProfile.Email src/Services/Identity/FreshCart.Identity.Application/Common/Models/AuthenticationProfile.cs:9
- DemoAccount.Email src/Services/Identity/FreshCart.Identity.Infrastructure/Persistence/IdentityDataSeeder.cs:133
- OrderDetailDto.CustomerEmail src/Services/Ordering/FreshCart.Ordering.Application/Orders/Dtos/OrderDetailDto.cs:11
- OrderSubmittedDomainEvent.CustomerEmail src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Events/OrderSubmittedDomainEvent.cs:8
- Order.CustomerEmail src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:26
- OrderSubmission.CustomerEmail src/Services/Ordering/FreshCart.Ordering.Domain/Orders/OrderSubmission.cs:14
- OrderDetailRow.CustomerEmail src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/Reads/OrderDetailRow.cs:17
- GenerateInvoiceRequest.CustomerEmail src/Services/Reporting/FreshCart.Reporting.Api/Endpoints/Invoices/GenerateInvoiceRequest.cs:13
- GenerateInvoiceCommand.CustomerEmail src/Services/Reporting/FreshCart.Reporting.Application/Invoices/Commands/GenerateInvoice/GenerateInvoiceCommand.cs:13
- Invoice.CustomerEmail src/Services/Reporting/FreshCart.Reporting.Domain/Invoices/Invoice.cs:24
- InvoiceRecord.CustomerEmail src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/InvoiceRecord.cs:15
Address — 19 field(s)
- BasketCheckoutStartedIntegrationEvent.BillingAddress src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/BasketCheckoutStartedIntegrationEvent.cs:19
- CheckoutAddress.PostalCode src/BuildingBlocks/FreshCart.BuildingBlocks.Messaging/IntegrationEvents/CheckoutAddress.cs:3
- CheckoutCommand.BillingAddress src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutCommand.cs:11
- CheckoutRequest.BillingAddress src/Services/Basket/FreshCart.Basket.Api/Features/ShoppingBaskets/Checkout/CheckoutRequest.cs:7
- DeliveryAddressDto.PostalCode src/Services/Delivery/FreshCart.Delivery.Application/Tracking/DeliveryAddressDto.cs:11
- DeliveryAddress.PostalCode src/Services/Delivery/FreshCart.Delivery.Domain/Deliveries/DeliveryAddress.cs:35
- AddressDocument.PostalCode src/Services/Delivery/FreshCart.Delivery.Infrastructure/Persistence/Documents/AddressDocument.cs:14
- OrderAddressDto.PostalCode src/Services/Ordering/FreshCart.Ordering.Application/Orders/Dtos/OrderAddressDto.cs:7
- OrderDetailDto.BillingAddress src/Services/Ordering/FreshCart.Ordering.Application/Orders/Dtos/OrderDetailDto.cs:29
- Address.PostalCode src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Address.cs:7
- Order.BillingAddress src/Services/Ordering/FreshCart.Ordering.Domain/Orders/Order.cs:46
- OrderSubmission.BillingAddress src/Services/Ordering/FreshCart.Ordering.Domain/Orders/OrderSubmission.cs:32
- OrderDetailRow.BillingPostalCode src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/Reads/OrderDetailRow.cs:49
- OrderDetailRow.ShippingPostalCode src/Services/Ordering/FreshCart.Ordering.Infrastructure/Persistence/Reads/OrderDetailRow.cs:59
- GenerateInvoiceRequest.BillingAddress src/Services/Reporting/FreshCart.Reporting.Api/Endpoints/Invoices/GenerateInvoiceRequest.cs:16
- GenerateInvoiceCommand.BillingAddress src/Services/Reporting/FreshCart.Reporting.Application/Invoices/Commands/GenerateInvoice/GenerateInvoiceCommand.cs:16
- Invoice.BillingAddress src/Services/Reporting/FreshCart.Reporting.Domain/Invoices/Invoice.cs:28
- InvoiceAddress.PostalCode src/Services/Reporting/FreshCart.Reporting.Domain/Invoices/InvoiceAddress.cs:12
- InvoiceRecord.BillingAddress src/Services/Reporting/FreshCart.Reporting.Infrastructure/Persistence/Warehouse/InvoiceRecord.cs:17
Name — 1 field(s)
- InvoiceAddress.FullName src/Services/Reporting/FreshCart.Reporting.Domain/Invoices/InvoiceAddress.cs:7