Executive summary
mostafasharaby/E-Commerce-Microservices falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 44 out of 100 and is rated Weak, and none of its 26 critical findings concern security.
Production Readiness, at 26, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 4 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 58.
The 20 inner parts of the code that depend on an outer part need turning around so they point inward.
The product code is 6,469 lines, about €14,000 to rebuild.
If Production Readiness rose from 26 to 70, the lowest score rated Strong, the score would rise from 44 to about 58.
New since the last survey: 2 findings
- Test isolation · Production project references a test package: Shared → FluentAssertions src/SharedService/Shared/Shared.csproj
- Test isolation · Production project references a test package: Shared → Moq src/SharedService/Shared/Shared.csproj
Fixed since the last survey: 98 findings
- Boundary Type-Coupling · Cross-context type LowStockDto (InventoryService → ProductService) src/ProductService/ProductService.Infrastructure/Interfaces/IProductRepository.cs
- Boundary Type-Coupling · Cross-context type LowStockDto (InventoryService → ProductService) src/ProductService/ProductService.Infrastructure/Repositories/ProductRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/WishListService/WishlistService.Infrastructure/Repositories/WishlistRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetByUserIdAsync src/WishListService/WishlistService.Infrastructure/Repositories/WishlistRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddAsync src/WishListService/WishlistService.Infrastructure/Repositories/WishlistRepository.cs
- Cancellation propagation · Async method without CancellationToken: UpdateAsync src/WishListService/WishlistService.Infrastructure/Repositories/WishlistRepository.cs
- Cancellation propagation · Async method without CancellationToken: DeleteByUserIdAsync src/WishListService/WishlistService.Infrastructure/Repositories/WishlistRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddItemAsync src/WishListService/WishlistService.Infrastructure/Repositories/WishlistRepository.cs
- Cancellation propagation · Async method without CancellationToken: RemoveItemAsync src/WishListService/WishlistService.Infrastructure/Repositories/WishlistRepository.cs
- Cancellation propagation · Async method without CancellationToken: ValidateWishlistExistsAsync src/WishListService/WishlistService.Application/Validators/ValidateWishlistExists.cs
- Cancellation propagation · Async method without CancellationToken: GetWishlistById REDACTED
- Cancellation propagation · Async method without CancellationToken: GetWishlistByUserId REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAllWishlists REDACTED
- Cancellation propagation · Async method without CancellationToken: CreateWishlist REDACTED
- Cancellation propagation · Async method without CancellationToken: AddItemToWishlist REDACTED
- Cancellation propagation · Async method without CancellationToken: RemoveItemFromWishlist REDACTED
- Cancellation propagation · Async method without CancellationToken: UpdateWishlist REDACTED
- Cancellation propagation · Async method without CancellationToken: DeleteWishlist REDACTED
- Cancellation propagation · Async method without CancellationToken: DeleteWishlistByUserId REDACTED
- Cancellation propagation · Async method without CancellationToken: GetByProductIdAsync src/InventoryService/InventoryService.Infrastructure/Repositories/InventoryRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetLowStockAsync src/InventoryService/InventoryService.Infrastructure/Repositories/InventoryRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddAsync src/InventoryService/InventoryService.Infrastructure/Repositories/InventoryRepository.cs
- Cancellation propagation · Async method without CancellationToken: UpdateAsync src/InventoryService/InventoryService.Infrastructure/Repositories/InventoryRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/ProductService/ProductService.Infrastructure/Repositories/ProductRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddAsync src/ProductService/ProductService.Infrastructure/Repositories/ProductRepository.cs
- Cancellation propagation · Async method without CancellationToken: UpdateAsync src/ProductService/ProductService.Infrastructure/Repositories/ProductRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetLowStockProductsAsync src/ProductService/ProductService.Infrastructure/Repositories/ProductRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetProduct REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAllProducts REDACTED
- Cancellation propagation · Async method without CancellationToken: SearchProducts REDACTED
- Cancellation propagation · Async method without CancellationToken: GetProductStock REDACTED
- Cancellation propagation · Async method without CancellationToken: GetLowStockProducts REDACTED
- Cancellation propagation · Async method without CancellationToken: CreateProduct REDACTED
- Cancellation propagation · Async method without CancellationToken: UpdateProduct REDACTED
- Cancellation propagation · Async method without CancellationToken: DeleteProduct REDACTED
- Cancellation propagation · Async method without CancellationToken: GetCartItemsByUserIdAsync src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddAsync src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs
- Cancellation propagation · Async method without CancellationToken: UpdateAsync src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs
- Cancellation propagation · Async method without CancellationToken: ValidateCustomerAsync src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs
- Cancellation propagation · Async method without CancellationToken: FetchProductsAsync src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs
- Cancellation propagation · Async method without CancellationToken: DeleteByUserIdAsync src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetByUserIdAsync src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs
- Cancellation propagation · Async method without CancellationToken: ProcessPayment src/PaymentService/Payment.Infrastructure/Repositories/PaymentProcessor.cs
- Cancellation propagation · Async method without CancellationToken: GetByOrderIdAsync src/PaymentService/Payment.Infrastructure/Repositories/PaymentRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddAsync src/PaymentService/Payment.Infrastructure/Repositories/PaymentRepository.cs
- Cancellation propagation · Async method without CancellationToken: ValidateOrderAsync src/PaymentService/Payment.Infrastructure/Repositories/PaymentRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddAsync src/OrderService/OrderService.Infrastructure/Repositories/OrderRepository.cs
- Cancellation propagation · Async method without CancellationToken: ValidateCustomerAsync src/OrderService/OrderService.Infrastructure/Repositories/OrderRepository.cs
- Cancellation propagation · Async method without CancellationToken: FetchProductsAsync src/OrderService/OrderService.Infrastructure/Repositories/OrderRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync src/OrderService/OrderService.Infrastructure/Repositories/OrderRepository.cs
- Cancellation propagation · Async method without CancellationToken: ProcessPayment src/PaymentService/Payment.Application/Handlers/PaymentCommandHandler.cs
- Cancellation propagation · Async method without CancellationToken: GetPaymentById REDACTED
- Cancellation propagation · Async method without CancellationToken: GetPaymentsByOrderId REDACTED
- Cancellation propagation · Async method without CancellationToken: CreatePayment REDACTED
- Cancellation propagation · Async method without CancellationToken: UpdatePaymentStatus REDACTED
- Cancellation propagation · Async method without CancellationToken: GetOrderById REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAllOrders REDACTED
- Cancellation propagation · Async method without CancellationToken: CreateOrder REDACTED
- Cancellation propagation · Async method without CancellationToken: CreateOrderFromCart REDACTED
- Cancellation propagation · Async method without CancellationToken: UpdateOrder REDACTED
- Cancellation propagation · Async method without CancellationToken: DeleteOrder REDACTED
- Cancellation propagation · Async method without CancellationToken: GetStock REDACTED
- Cancellation propagation · Async method without CancellationToken: GetLowStock REDACTED
- Cancellation propagation · Async method without CancellationToken: AddStock REDACTED
- Cancellation propagation · Async method without CancellationToken: ReserveStock REDACTED
- Cancellation propagation · Async method without CancellationToken: ReleaseStock REDACTED
- Cancellation propagation · Async method without CancellationToken: ReconcileStock REDACTED
- Cancellation propagation · Async method without CancellationToken: UpdateStock REDACTED
- Cancellation propagation · Async method without CancellationToken: GetCartById REDACTED
- Cancellation propagation · Async method without CancellationToken: GetCartsByUserId REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAllCarts REDACTED
- Cancellation propagation · Async method without CancellationToken: CreateCart REDACTED
- Cancellation propagation · Async method without CancellationToken: UpdateCart REDACTED
- Cancellation propagation · Async method without CancellationToken: DeleteCart REDACTED
- Cancellation propagation · Async method without CancellationToken: DeleteCartByUserId REDACTED
- Cancellation propagation · Async method without CancellationToken: RegisterUserAsync src/AuthService/Auth.Application/Helpers/UserRegistrationHelper.cs
- Cancellation propagation · Async method without CancellationToken: DeleteAccount REDACTED
- Cancellation propagation · Async method without CancellationToken: DeleteUser REDACTED
- Cancellation propagation · Async method drops its CancellationToken: Handle src/WishListService/WishlistService.Application/Handlers/WishlistCommandHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/WishListService/WishlistService.Application/Handlers/WishlistCommandHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/WishListService/WishlistService.Application/Handlers/WishlistCommandHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/WishListService/WishlistService.Application/Handlers/WishlistCommandHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/WishListService/WishlistService.Application/Handlers/WishlistQueryHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/WishListService/WishlistService.Application/Handlers/WishlistQueryHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/OrderService/OrderService.Application/Handlers/OrderCommandHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/OrderService/OrderService.Application/Handlers/OrderCommandHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/AuthService/Auth.Application/Handlers/AppUserHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/AuthService/Auth.Application/Handlers/AppUserHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/AuthService/Auth.Application/Handlers/AppUserHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/AuthService/Auth.Application/Handlers/AppUserQueryHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle src/AuthService/Auth.Application/Handlers/AppUserQueryHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: Handle REDACTED
- Cancellation propagation · Async method drops its CancellationToken: Handle REDACTED
- Cancellation propagation · Async method drops its CancellationToken: Handle REDACTED
- Cancellation propagation · Async method drops its CancellationToken: Handle REDACTED
- Cancellation propagation · Async method drops its CancellationToken: Handle REDACTED
- Cancellation propagation · Async method drops its CancellationToken: IsValidToken src/AuthService/Auth.Application/Validators/ResetPasswordCommandValidator.cs
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,600 to €23,000, for 76 to 241 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 44. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,469 lines of product code, of which 43% is declarations and boilerplate, 40% straight logic and 17% logic with branches |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Auth.Domain.Entities | 2 Auth.Domain.Responses | 3 CartService.Domain.Dtos | 4 InventoryService.Domain.Dtos | 5 InventoryService.Domain.Entities | 6 Payment.Domain.Entities | 7 ProductService.Domain.Dtos | 8 ProductService.Domain.Entities | 9 Shared | 10 Shared.Bases | 11 Shared.Interfaces | 12 Shared.RedisCache | 13 Auth.Application.Commands | 14 Auth.Application.Queries | 15 Auth.Infrastructure.Interfaces | 16 CartService.Application.Commands | 17 CartService.Infrastructure.Interfaces | 18 InventoryService.Infrastructure.Interfaces | 19 OrderService.Infrastructure.Interfaces | 20 Payment.Application.Commands | 21 Payment.Infrastructure.Interfaces | 22 ProductService.Application.Commands | 23 ProductService.Infrastructure.Interfaces | 24 Shared.Repository | 25 WishlistService.Infrastructure.Interfaces | 26 Auth.Application.Helpers | 27 Auth.Infrastructure.Services | 28 CartService.Application.Handlers | 29 CartService.Infrastructure.Repositories | 30 InventoryService.Application.Handlers | 31 InventoryService.Infrastructure.Repositories | 32 OrderService.Application.Handlers | 33 OrderService.Infrastructure.Repositories | 34 Payment.Application.Handlers | 35 Payment.Infrastructure.Repositories | 36 ProductService.Application.Handlers | 37 ProductService.Infrastructure.Repositories | 38 WishlistService.Application.Handlers | 39 WishlistService.Infrastructure.Repositories | 40 Auth.Application.Handlers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Auth.Domain.Entities | ||||||||||||||||||||||||||||||||||||||||
| 2 Auth.Domain.Responses | ||||||||||||||||||||||||||||||||||||||||
| 3 CartService.Domain.Dtos | ||||||||||||||||||||||||||||||||||||||||
| 4 InventoryService.Domain.Dtos | ||||||||||||||||||||||||||||||||||||||||
| 5 InventoryService.Domain.Entities | ||||||||||||||||||||||||||||||||||||||||
| 6 Payment.Domain.Entities | ||||||||||||||||||||||||||||||||||||||||
| 7 ProductService.Domain.Dtos | ||||||||||||||||||||||||||||||||||||||||
| 8 ProductService.Domain.Entities | ||||||||||||||||||||||||||||||||||||||||
| 9 Shared | ||||||||||||||||||||||||||||||||||||||||
| 10 Shared.Bases | ||||||||||||||||||||||||||||||||||||||||
| 11 Shared.Interfaces | ||||||||||||||||||||||||||||||||||||||||
| 12 Shared.RedisCache | ||||||||||||||||||||||||||||||||||||||||
| 13 Auth.Application.Commands | 1 | 3 | 11 | |||||||||||||||||||||||||||||||||||||
| 14 Auth.Application.Queries | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Auth.Infrastructure.Interfaces | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 CartService.Application.Commands | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 CartService.Infrastructure.Interfaces | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 InventoryService.Infrastructure.Interfaces | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 OrderService.Infrastructure.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Payment.Application.Commands | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Payment.Infrastructure.Interfaces | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 ProductService.Application.Commands | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 ProductService.Infrastructure.Interfaces | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 Shared.Repository | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 WishlistService.Infrastructure.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Auth.Application.Helpers | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 Auth.Infrastructure.Services | 3 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 28 CartService.Application.Handlers | 2 | 4 | 4 | 2 | ||||||||||||||||||||||||||||||||||||
| 29 CartService.Infrastructure.Repositories | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 30 InventoryService.Application.Handlers | 2 | 4 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 InventoryService.Infrastructure.Repositories | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 OrderService.Application.Handlers | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 OrderService.Infrastructure.Repositories | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 Payment.Application.Handlers | 1 | 4 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 Payment.Infrastructure.Repositories | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 ProductService.Application.Handlers | 2 | 4 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 37 ProductService.Infrastructure.Repositories | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 WishlistService.Application.Handlers | 2 | |||||||||||||||||||||||||||||||||||||||
| 39 WishlistService.Infrastructure.Repositories | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 Auth.Application.Handlers | 3 | 1 | 6 | 13 | 2 | 3 | 1 |
13→1 Auth.Application.Commands uses Auth.Domain.Entities✕
- Connections
- 1 pair of types, where a type in Auth.Application.Commands uses a type in Auth.Domain.Entities.
- The types involved
Auth.Application.Commands.ConfirmEmailCommand→Auth.Domain.Entities.AppUser
- Direction
- Auth.Application.Commands uses Auth.Domain.Entities, so a change to Auth.Domain.Entities can break Auth.Application.Commands, while a change to Auth.Application.Commands can't break Auth.Domain.Entities.
- Position
- Below the diagonal: Auth.Application.Commands uses a module listed above it, which is the healthy direction.
13→2 Auth.Application.Commands uses Auth.Domain.Responses✕
- Connections
- 3 pairs of types, where a type in Auth.Application.Commands uses a type in Auth.Domain.Responses.
- The types involved
Auth.Application.Commands.GoogleLoginCallbackCommand→Auth.Domain.Responses.AuthResponseAuth.Application.Commands.LoginCommand→Auth.Domain.Responses.AuthResponseAuth.Application.Commands.RefreshTokenCommand→Auth.Domain.Responses.AuthResponse
- Direction
- Auth.Application.Commands uses Auth.Domain.Responses, so a change to Auth.Domain.Responses can break Auth.Application.Commands, while a change to Auth.Application.Commands can't break Auth.Domain.Responses.
- Position
- Below the diagonal: Auth.Application.Commands uses a module listed above it, which is the healthy direction.
13→10 Auth.Application.Commands uses Shared.Bases✕
- Connections
- 11 pairs of types, where a type in Auth.Application.Commands uses a type in Shared.Bases.
- The types involved
Auth.Application.Commands.ChangePasswordCommand→Shared.Bases.ResponseAuth.Application.Commands.ConfirmEmailCommand→Shared.Bases.ResponseAuth.Application.Commands.DeleteAppUserCommand→Shared.Bases.ResponseAuth.Application.Commands.ForgotPasswordCommand→Shared.Bases.ResponseAuth.Application.Commands.LoginCommand→Shared.Bases.ResponseAuth.Application.Commands.RefreshTokenCommand→Shared.Bases.ResponseAuth.Application.Commands.RegisterAdminCommand→Shared.Bases.ResponseAuth.Application.Commands.ResetPasswordCommand→Shared.Bases.ResponseAuth.Application.Commands.UpdateAppUserCommand→Shared.Bases.ResponseAuth.Application.Commands.UpdateProfileCommand→Shared.Bases.ResponseAuth.Application.Commands.UpdateProfileRequest→Shared.Bases.Response
- Direction
- Auth.Application.Commands uses Shared.Bases, so a change to Shared.Bases can break Auth.Application.Commands, while a change to Auth.Application.Commands can't break Shared.Bases.
- Position
- Below the diagonal: Auth.Application.Commands uses a module listed above it, which is the healthy direction.
14→10 Auth.Application.Queries uses Shared.Bases✕
- Connections
- 1 pair of types, where a type in Auth.Application.Queries uses a type in Shared.Bases.
- The types involved
Auth.Application.Queries.GetAppUserById→Shared.Bases.Response
- Direction
- Auth.Application.Queries uses Shared.Bases, so a change to Shared.Bases can break Auth.Application.Queries, while a change to Auth.Application.Queries can't break Shared.Bases.
- Position
- Below the diagonal: Auth.Application.Queries uses a module listed above it, which is the healthy direction.
15→1 Auth.Infrastructure.Interfaces uses Auth.Domain.Entities✕
- Connections
- 1 pair of types, where a type in Auth.Infrastructure.Interfaces uses a type in Auth.Domain.Entities.
- The types involved
Auth.Infrastructure.Interfaces.IJwtService→Auth.Domain.Entities.AppUser
- Direction
- Auth.Infrastructure.Interfaces uses Auth.Domain.Entities, so a change to Auth.Domain.Entities can break Auth.Infrastructure.Interfaces, while a change to Auth.Infrastructure.Interfaces can't break Auth.Domain.Entities.
- Position
- Below the diagonal: Auth.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
15→2 Auth.Infrastructure.Interfaces uses Auth.Domain.Responses✕
- Connections
- 2 pairs of types, where a type in Auth.Infrastructure.Interfaces uses a type in Auth.Domain.Responses.
- The types involved
Auth.Infrastructure.Interfaces.IGoogleService→Auth.Domain.Responses.AuthResponseAuth.Infrastructure.Interfaces.IJwtService→Auth.Domain.Responses.AuthResponse
- Direction
- Auth.Infrastructure.Interfaces uses Auth.Domain.Responses, so a change to Auth.Domain.Responses can break Auth.Infrastructure.Interfaces, while a change to Auth.Infrastructure.Interfaces can't break Auth.Domain.Responses.
- Position
- Below the diagonal: Auth.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
16→3 CartService.Application.Commands uses CartService.Domain.Dtos✕
- Connections
- 4 pairs of types, where a type in CartService.Application.Commands uses a type in CartService.Domain.Dtos.
- The types involved
CartService.Application.Commands.CreateCartCommand→CartService.Domain.Dtos.CartDtoCartService.Application.Commands.CreateCartCommand→CartService.Domain.Dtos.CartItemDtoCartService.Application.Commands.UpdateCartCommand→CartService.Domain.Dtos.CartDtoCartService.Application.Commands.UpdateCartCommand→CartService.Domain.Dtos.CartItemDto
- Direction
- CartService.Application.Commands uses CartService.Domain.Dtos, so a change to CartService.Domain.Dtos can break CartService.Application.Commands, while a change to CartService.Application.Commands can't break CartService.Domain.Dtos.
- Position
- Below the diagonal: CartService.Application.Commands uses a module listed above it, which is the healthy direction.
16→10 CartService.Application.Commands uses Shared.Bases✕
- Connections
- 2 pairs of types, where a type in CartService.Application.Commands uses a type in Shared.Bases.
- The types involved
CartService.Application.Commands.DeleteCartByUserIdCommand→Shared.Bases.ResponseCartService.Application.Commands.DeleteCartCommand→Shared.Bases.Response
- Direction
- CartService.Application.Commands uses Shared.Bases, so a change to Shared.Bases can break CartService.Application.Commands, while a change to CartService.Application.Commands can't break Shared.Bases.
- Position
- Below the diagonal: CartService.Application.Commands uses a module listed above it, which is the healthy direction.
17→3 CartService.Infrastructure.Interfaces uses CartService.Domain.Dtos✕
- Connections
- 1 pair of types, where a type in CartService.Infrastructure.Interfaces uses a type in CartService.Domain.Dtos.
- The types involved
CartService.Infrastructure.Interfaces.ICartRepository→CartService.Domain.Dtos.CartItemDto
- Direction
- CartService.Infrastructure.Interfaces uses CartService.Domain.Dtos, so a change to CartService.Domain.Dtos can break CartService.Infrastructure.Interfaces, while a change to CartService.Infrastructure.Interfaces can't break CartService.Domain.Dtos.
- Position
- Below the diagonal: CartService.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
17→11 CartService.Infrastructure.Interfaces uses Shared.Interfaces✕
- Connections
- 1 pair of types, where a type in CartService.Infrastructure.Interfaces uses a type in Shared.Interfaces.
- The types involved
CartService.Infrastructure.Interfaces.ICartRepository→Shared.Interfaces.IGenericRepository
- Direction
- CartService.Infrastructure.Interfaces uses Shared.Interfaces, so a change to Shared.Interfaces can break CartService.Infrastructure.Interfaces, while a change to CartService.Infrastructure.Interfaces can't break Shared.Interfaces.
- Position
- Below the diagonal: CartService.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
18→5 InventoryService.Infrastructure.Interfaces uses InventoryService.Domain.Entities✕
- Connections
- 1 pair of types, where a type in InventoryService.Infrastructure.Interfaces uses a type in InventoryService.Domain.Entities.
- The types involved
InventoryService.Infrastructure.Interfaces.IInventoryRepository→InventoryService.Domain.Entities.InventoryItem
- Direction
- InventoryService.Infrastructure.Interfaces uses InventoryService.Domain.Entities, so a change to InventoryService.Domain.Entities can break InventoryService.Infrastructure.Interfaces, while a change to InventoryService.Infrastructure.Interfaces can't break InventoryService.Domain.Entities.
- Position
- Below the diagonal: InventoryService.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
18→11 InventoryService.Infrastructure.Interfaces uses Shared.Interfaces✕
- Connections
- 1 pair of types, where a type in InventoryService.Infrastructure.Interfaces uses a type in Shared.Interfaces.
- The types involved
InventoryService.Infrastructure.Interfaces.IInventoryRepository→Shared.Interfaces.IGenericRepository
- Direction
- InventoryService.Infrastructure.Interfaces uses Shared.Interfaces, so a change to Shared.Interfaces can break InventoryService.Infrastructure.Interfaces, while a change to InventoryService.Infrastructure.Interfaces can't break Shared.Interfaces.
- Position
- Below the diagonal: InventoryService.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
19→11 OrderService.Infrastructure.Interfaces uses Shared.Interfaces✕
- Connections
- 1 pair of types, where a type in OrderService.Infrastructure.Interfaces uses a type in Shared.Interfaces.
- The types involved
OrderService.Infrastructure.Interfaces.IOrderRepository→Shared.Interfaces.IGenericRepository
- Direction
- OrderService.Infrastructure.Interfaces uses Shared.Interfaces, so a change to Shared.Interfaces can break OrderService.Infrastructure.Interfaces, while a change to OrderService.Infrastructure.Interfaces can't break Shared.Interfaces.
- Position
- Below the diagonal: OrderService.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
20→6 Payment.Application.Commands uses Payment.Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Payment.Application.Commands uses a type in Payment.Domain.Entities.
- The types involved
Payment.Application.Commands.CreatePaymentCommand→Payment.Domain.Entities.PaymentMethodTypePayment.Application.Commands.CreatePaymentCommand→Payment.Domain.Entities.PaymentStatus
- Direction
- Payment.Application.Commands uses Payment.Domain.Entities, so a change to Payment.Domain.Entities can break Payment.Application.Commands, while a change to Payment.Application.Commands can't break Payment.Domain.Entities.
- Position
- Below the diagonal: Payment.Application.Commands uses a module listed above it, which is the healthy direction.
20→10 Payment.Application.Commands uses Shared.Bases✕
- Connections
- 1 pair of types, where a type in Payment.Application.Commands uses a type in Shared.Bases.
- The types involved
Payment.Application.Commands.CreatePaymentCommand→Shared.Bases.Response
- Direction
- Payment.Application.Commands uses Shared.Bases, so a change to Shared.Bases can break Payment.Application.Commands, while a change to Payment.Application.Commands can't break Shared.Bases.
- Position
- Below the diagonal: Payment.Application.Commands uses a module listed above it, which is the healthy direction.
21→6 Payment.Infrastructure.Interfaces uses Payment.Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Payment.Infrastructure.Interfaces uses a type in Payment.Domain.Entities.
- The types involved
Payment.Infrastructure.Interfaces.IPaymentProcessor→Payment.Domain.Entities.PaymentPayment.Infrastructure.Interfaces.IPaymentRepository→Payment.Domain.Entities.Payment
- Direction
- Payment.Infrastructure.Interfaces uses Payment.Domain.Entities, so a change to Payment.Domain.Entities can break Payment.Infrastructure.Interfaces, while a change to Payment.Infrastructure.Interfaces can't break Payment.Domain.Entities.
- Position
- Below the diagonal: Payment.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
21→11 Payment.Infrastructure.Interfaces uses Shared.Interfaces✕
- Connections
- 1 pair of types, where a type in Payment.Infrastructure.Interfaces uses a type in Shared.Interfaces.
- The types involved
Payment.Infrastructure.Interfaces.IPaymentRepository→Shared.Interfaces.IGenericRepository
- Direction
- Payment.Infrastructure.Interfaces uses Shared.Interfaces, so a change to Shared.Interfaces can break Payment.Infrastructure.Interfaces, while a change to Payment.Infrastructure.Interfaces can't break Shared.Interfaces.
- Position
- Below the diagonal: Payment.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
22→7 ProductService.Application.Commands uses ProductService.Domain.Dtos✕
- Connections
- 1 pair of types, where a type in ProductService.Application.Commands uses a type in ProductService.Domain.Dtos.
- The types involved
ProductService.Application.Commands.CreateProductCommand→ProductService.Domain.Dtos.ProductDto
- Direction
- ProductService.Application.Commands uses ProductService.Domain.Dtos, so a change to ProductService.Domain.Dtos can break ProductService.Application.Commands, while a change to ProductService.Application.Commands can't break ProductService.Domain.Dtos.
- Position
- Below the diagonal: ProductService.Application.Commands uses a module listed above it, which is the healthy direction.
22→10 ProductService.Application.Commands uses Shared.Bases✕
- Connections
- 1 pair of types, where a type in ProductService.Application.Commands uses a type in Shared.Bases.
- The types involved
ProductService.Application.Commands.DeleteProductCommand→Shared.Bases.Response
- Direction
- ProductService.Application.Commands uses Shared.Bases, so a change to Shared.Bases can break ProductService.Application.Commands, while a change to ProductService.Application.Commands can't break Shared.Bases.
- Position
- Below the diagonal: ProductService.Application.Commands uses a module listed above it, which is the healthy direction.
23→4 ProductService.Infrastructure.Interfaces uses InventoryService.Domain.Dtos✕
- Connections
- 1 pair of types, where a type in ProductService.Infrastructure.Interfaces uses a type in InventoryService.Domain.Dtos.
- The types involved
ProductService.Infrastructure.Interfaces.IProductRepository→InventoryService.Domain.Dtos.LowStockDto
- Direction
- ProductService.Infrastructure.Interfaces uses InventoryService.Domain.Dtos, so a change to InventoryService.Domain.Dtos can break ProductService.Infrastructure.Interfaces, while a change to ProductService.Infrastructure.Interfaces can't break InventoryService.Domain.Dtos.
- Position
- Below the diagonal: ProductService.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
23→7 ProductService.Infrastructure.Interfaces uses ProductService.Domain.Dtos✕
- Connections
- 1 pair of types, where a type in ProductService.Infrastructure.Interfaces uses a type in ProductService.Domain.Dtos.
- The types involved
ProductService.Infrastructure.Interfaces.IProductRepository→ProductService.Domain.Dtos.ProductStockDto
- Direction
- ProductService.Infrastructure.Interfaces uses ProductService.Domain.Dtos, so a change to ProductService.Domain.Dtos can break ProductService.Infrastructure.Interfaces, while a change to ProductService.Infrastructure.Interfaces can't break ProductService.Domain.Dtos.
- Position
- Below the diagonal: ProductService.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
23→11 ProductService.Infrastructure.Interfaces uses Shared.Interfaces✕
- Connections
- 1 pair of types, where a type in ProductService.Infrastructure.Interfaces uses a type in Shared.Interfaces.
- The types involved
ProductService.Infrastructure.Interfaces.IProductRepository→Shared.Interfaces.IGenericRepository
- Direction
- ProductService.Infrastructure.Interfaces uses Shared.Interfaces, so a change to Shared.Interfaces can break ProductService.Infrastructure.Interfaces, while a change to ProductService.Infrastructure.Interfaces can't break Shared.Interfaces.
- Position
- Below the diagonal: ProductService.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
24→11 Shared.Repository uses Shared.Interfaces✕
- Connections
- 2 pairs of types, where a type in Shared.Repository uses a type in Shared.Interfaces.
- The types involved
Shared.Repository.GenericRepository→Shared.Interfaces.IGenericRepositoryShared.Repository.ValidationService→Shared.Interfaces.IValidationService
- Direction
- Shared.Repository uses Shared.Interfaces, so a change to Shared.Interfaces can break Shared.Repository, while a change to Shared.Repository can't break Shared.Interfaces.
- Position
- Below the diagonal: Shared.Repository uses a module listed above it, which is the healthy direction.
25→11 WishlistService.Infrastructure.Interfaces uses Shared.Interfaces✕
- Connections
- 1 pair of types, where a type in WishlistService.Infrastructure.Interfaces uses a type in Shared.Interfaces.
- The types involved
WishlistService.Infrastructure.Interfaces.IWishlistRepository→Shared.Interfaces.IGenericRepository
- Direction
- WishlistService.Infrastructure.Interfaces uses Shared.Interfaces, so a change to Shared.Interfaces can break WishlistService.Infrastructure.Interfaces, while a change to WishlistService.Infrastructure.Interfaces can't break Shared.Interfaces.
- Position
- Below the diagonal: WishlistService.Infrastructure.Interfaces uses a module listed above it, which is the healthy direction.
26→1 Auth.Application.Helpers uses Auth.Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Auth.Application.Helpers uses a type in Auth.Domain.Entities.
- The types involved
Auth.Application.Helpers.IUserRegistrationHelper→Auth.Domain.Entities.AppUserAuth.Application.Helpers.UserRegistrationHelper→Auth.Domain.Entities.AppUser
- Direction
- Auth.Application.Helpers uses Auth.Domain.Entities, so a change to Auth.Domain.Entities can break Auth.Application.Helpers, while a change to Auth.Application.Helpers can't break Auth.Domain.Entities.
- Position
- Below the diagonal: Auth.Application.Helpers uses a module listed above it, which is the healthy direction.
26→10 Auth.Application.Helpers uses Shared.Bases✕
- Connections
- 3 pairs of types, where a type in Auth.Application.Helpers uses a type in Shared.Bases.
- The types involved
Auth.Application.Helpers.IUserRegistrationHelper→Shared.Bases.ResponseAuth.Application.Helpers.UserRegistrationHelper→Shared.Bases.ResponseAuth.Application.Helpers.UserRegistrationHelper→Shared.Bases.ResponseHandler
- Direction
- Auth.Application.Helpers uses Shared.Bases, so a change to Shared.Bases can break Auth.Application.Helpers, while a change to Auth.Application.Helpers can't break Shared.Bases.
- Position
- Below the diagonal: Auth.Application.Helpers uses a module listed above it, which is the healthy direction.
26→15 Auth.Application.Helpers uses Auth.Infrastructure.Interfaces✕
- Connections
- 1 pair of types, where a type in Auth.Application.Helpers uses a type in Auth.Infrastructure.Interfaces.
- The types involved
Auth.Application.Helpers.UserRegistrationHelper→Auth.Infrastructure.Interfaces.IEmailService
- Direction
- Auth.Application.Helpers uses Auth.Infrastructure.Interfaces, so a change to Auth.Infrastructure.Interfaces can break Auth.Application.Helpers, while a change to Auth.Application.Helpers can't break Auth.Infrastructure.Interfaces.
- Position
- Below the diagonal: Auth.Application.Helpers uses a module listed above it, which is the healthy direction.
27→1 Auth.Infrastructure.Services uses Auth.Domain.Entities✕
- Connections
- 3 pairs of types, where a type in Auth.Infrastructure.Services uses a type in Auth.Domain.Entities.
- The types involved
Auth.Infrastructure.Services.GoogleService→Auth.Domain.Entities.AppUserAuth.Infrastructure.Services.JwtService→Auth.Domain.Entities.AppUserAuth.Infrastructure.Services.JwtService→Auth.Domain.Entities.RefreshToken
- Direction
- Auth.Infrastructure.Services uses Auth.Domain.Entities, so a change to Auth.Domain.Entities can break Auth.Infrastructure.Services, while a change to Auth.Infrastructure.Services can't break Auth.Domain.Entities.
- Position
- Below the diagonal: Auth.Infrastructure.Services uses a module listed above it, which is the healthy direction.
27→2 Auth.Infrastructure.Services uses Auth.Domain.Responses✕
- Connections
- 2 pairs of types, where a type in Auth.Infrastructure.Services uses a type in Auth.Domain.Responses.
- The types involved
Auth.Infrastructure.Services.GoogleService→Auth.Domain.Responses.AuthResponseAuth.Infrastructure.Services.JwtService→Auth.Domain.Responses.AuthResponse
- Direction
- Auth.Infrastructure.Services uses Auth.Domain.Responses, so a change to Auth.Domain.Responses can break Auth.Infrastructure.Services, while a change to Auth.Infrastructure.Services can't break Auth.Domain.Responses.
- Position
- Below the diagonal: Auth.Infrastructure.Services uses a module listed above it, which is the healthy direction.
27→15 Auth.Infrastructure.Services uses Auth.Infrastructure.Interfaces✕
- Connections
- 4 pairs of types, where a type in Auth.Infrastructure.Services uses a type in Auth.Infrastructure.Interfaces.
- The types involved
Auth.Infrastructure.Services.EmailService→Auth.Infrastructure.Interfaces.IEmailServiceAuth.Infrastructure.Services.GoogleService→Auth.Infrastructure.Interfaces.IGoogleServiceAuth.Infrastructure.Services.GoogleService→Auth.Infrastructure.Interfaces.IJwtServiceAuth.Infrastructure.Services.JwtService→Auth.Infrastructure.Interfaces.IJwtService
- Direction
- Auth.Infrastructure.Services uses Auth.Infrastructure.Interfaces, so a change to Auth.Infrastructure.Interfaces can break Auth.Infrastructure.Services, while a change to Auth.Infrastructure.Services can't break Auth.Infrastructure.Interfaces.
- Position
- Below the diagonal: Auth.Infrastructure.Services uses a module listed above it, which is the healthy direction.
28→3 CartService.Application.Handlers uses CartService.Domain.Dtos✕
- Connections
- 2 pairs of types, where a type in CartService.Application.Handlers uses a type in CartService.Domain.Dtos.
- The types involved
CartService.Application.Handlers.CartQueryHandler→CartService.Domain.Dtos.CartDtoCartService.Application.Handlers.CartQueryHandler→CartService.Domain.Dtos.CartItemDto
- Direction
- CartService.Application.Handlers uses CartService.Domain.Dtos, so a change to CartService.Domain.Dtos can break CartService.Application.Handlers, while a change to CartService.Application.Handlers can't break CartService.Domain.Dtos.
- Position
- Below the diagonal: CartService.Application.Handlers uses a module listed above it, which is the healthy direction.
28→10 CartService.Application.Handlers uses Shared.Bases✕
- Connections
- 4 pairs of types, where a type in CartService.Application.Handlers uses a type in Shared.Bases.
- The types involved
CartService.Application.Handlers.CartCommandHandler→Shared.Bases.ResponseCartService.Application.Handlers.CartCommandHandler→Shared.Bases.ResponseHandlerCartService.Application.Handlers.CartQueryHandler→Shared.Bases.ResponseCartService.Application.Handlers.CartQueryHandler→Shared.Bases.ResponseHandler
- Direction
- CartService.Application.Handlers uses Shared.Bases, so a change to Shared.Bases can break CartService.Application.Handlers, while a change to CartService.Application.Handlers can't break Shared.Bases.
- Position
- Below the diagonal: CartService.Application.Handlers uses a module listed above it, which is the healthy direction.
28→16 CartService.Application.Handlers uses CartService.Application.Commands✕
- Connections
- 4 pairs of types, where a type in CartService.Application.Handlers uses a type in CartService.Application.Commands.
- The types involved
CartService.Application.Handlers.CartCommandHandler→CartService.Application.Commands.CreateCartCommandCartService.Application.Handlers.CartCommandHandler→CartService.Application.Commands.DeleteCartByUserIdCommandCartService.Application.Handlers.CartCommandHandler→CartService.Application.Commands.DeleteCartCommandCartService.Application.Handlers.CartCommandHandler→CartService.Application.Commands.UpdateCartCommand
- Direction
- CartService.Application.Handlers uses CartService.Application.Commands, so a change to CartService.Application.Commands can break CartService.Application.Handlers, while a change to CartService.Application.Handlers can't break CartService.Application.Commands.
- Position
- Below the diagonal: CartService.Application.Handlers uses a module listed above it, which is the healthy direction.
28→17 CartService.Application.Handlers uses CartService.Infrastructure.Interfaces✕
- Connections
- 2 pairs of types, where a type in CartService.Application.Handlers uses a type in CartService.Infrastructure.Interfaces.
- The types involved
CartService.Application.Handlers.CartCommandHandler→CartService.Infrastructure.Interfaces.ICartRepositoryCartService.Application.Handlers.CartQueryHandler→CartService.Infrastructure.Interfaces.ICartRepository
- Direction
- CartService.Application.Handlers uses CartService.Infrastructure.Interfaces, so a change to CartService.Infrastructure.Interfaces can break CartService.Application.Handlers, while a change to CartService.Application.Handlers can't break CartService.Infrastructure.Interfaces.
- Position
- Below the diagonal: CartService.Application.Handlers uses a module listed above it, which is the healthy direction.
29→3 CartService.Infrastructure.Repositories uses CartService.Domain.Dtos✕
- Connections
- 1 pair of types, where a type in CartService.Infrastructure.Repositories uses a type in CartService.Domain.Dtos.
- The types involved
CartService.Infrastructure.Repositories.CartRepository→CartService.Domain.Dtos.CartItemDto
- Direction
- CartService.Infrastructure.Repositories uses CartService.Domain.Dtos, so a change to CartService.Domain.Dtos can break CartService.Infrastructure.Repositories, while a change to CartService.Infrastructure.Repositories can't break CartService.Domain.Dtos.
- Position
- Below the diagonal: CartService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
29→8 CartService.Infrastructure.Repositories uses ProductService.Domain.Entities✕
- Connections
- 1 pair of types, where a type in CartService.Infrastructure.Repositories uses a type in ProductService.Domain.Entities.
- The types involved
CartService.Infrastructure.Repositories.CartRepository→ProductService.Domain.Entities.Product
- Direction
- CartService.Infrastructure.Repositories uses ProductService.Domain.Entities, so a change to ProductService.Domain.Entities can break CartService.Infrastructure.Repositories, while a change to CartService.Infrastructure.Repositories can't break ProductService.Domain.Entities.
- Position
- Below the diagonal: CartService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
29→10 CartService.Infrastructure.Repositories uses Shared.Bases✕
- Connections
- 1 pair of types, where a type in CartService.Infrastructure.Repositories uses a type in Shared.Bases.
- The types involved
CartService.Infrastructure.Repositories.CartRepository→Shared.Bases.Response
- Direction
- CartService.Infrastructure.Repositories uses Shared.Bases, so a change to Shared.Bases can break CartService.Infrastructure.Repositories, while a change to CartService.Infrastructure.Repositories can't break Shared.Bases.
- Position
- Below the diagonal: CartService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
29→12 CartService.Infrastructure.Repositories uses Shared.RedisCache✕
- Connections
- 1 pair of types, where a type in CartService.Infrastructure.Repositories uses a type in Shared.RedisCache.
- The types involved
CartService.Infrastructure.Repositories.CartRepository→Shared.RedisCache.ICacheService
- Direction
- CartService.Infrastructure.Repositories uses Shared.RedisCache, so a change to Shared.RedisCache can break CartService.Infrastructure.Repositories, while a change to CartService.Infrastructure.Repositories can't break Shared.RedisCache.
- Position
- Below the diagonal: CartService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
29→17 CartService.Infrastructure.Repositories uses CartService.Infrastructure.Interfaces✕
- Connections
- 1 pair of types, where a type in CartService.Infrastructure.Repositories uses a type in CartService.Infrastructure.Interfaces.
- The types involved
CartService.Infrastructure.Repositories.CartRepository→CartService.Infrastructure.Interfaces.ICartRepository
- Direction
- CartService.Infrastructure.Repositories uses CartService.Infrastructure.Interfaces, so a change to CartService.Infrastructure.Interfaces can break CartService.Infrastructure.Repositories, while a change to CartService.Infrastructure.Repositories can't break CartService.Infrastructure.Interfaces.
- Position
- Below the diagonal: CartService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
29→24 CartService.Infrastructure.Repositories uses Shared.Repository✕
- Connections
- 1 pair of types, where a type in CartService.Infrastructure.Repositories uses a type in Shared.Repository.
- The types involved
CartService.Infrastructure.Repositories.CartRepository→Shared.Repository.GenericRepository
- Direction
- CartService.Infrastructure.Repositories uses Shared.Repository, so a change to Shared.Repository can break CartService.Infrastructure.Repositories, while a change to CartService.Infrastructure.Repositories can't break Shared.Repository.
- Position
- Below the diagonal: CartService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
30→4 InventoryService.Application.Handlers uses InventoryService.Domain.Dtos✕
- Connections
- 2 pairs of types, where a type in InventoryService.Application.Handlers uses a type in InventoryService.Domain.Dtos.
- The types involved
InventoryService.Application.Handlers.InventoryQueryHandler→InventoryService.Domain.Dtos.LowStockDtoInventoryService.Application.Handlers.InventoryQueryHandler→InventoryService.Domain.Dtos.StockDto
- Direction
- InventoryService.Application.Handlers uses InventoryService.Domain.Dtos, so a change to InventoryService.Domain.Dtos can break InventoryService.Application.Handlers, while a change to InventoryService.Application.Handlers can't break InventoryService.Domain.Dtos.
- Position
- Below the diagonal: InventoryService.Application.Handlers uses a module listed above it, which is the healthy direction.
30→10 InventoryService.Application.Handlers uses Shared.Bases✕
- Connections
- 4 pairs of types, where a type in InventoryService.Application.Handlers uses a type in Shared.Bases.
- The types involved
InventoryService.Application.Handlers.InventoryCommandHandler→Shared.Bases.ResponseInventoryService.Application.Handlers.InventoryCommandHandler→Shared.Bases.ResponseHandlerInventoryService.Application.Handlers.InventoryQueryHandler→Shared.Bases.ResponseInventoryService.Application.Handlers.InventoryQueryHandler→Shared.Bases.ResponseHandler
- Direction
- InventoryService.Application.Handlers uses Shared.Bases, so a change to Shared.Bases can break InventoryService.Application.Handlers, while a change to InventoryService.Application.Handlers can't break Shared.Bases.
- Position
- Below the diagonal: InventoryService.Application.Handlers uses a module listed above it, which is the healthy direction.
30→18 InventoryService.Application.Handlers uses InventoryService.Infrastructure.Interfaces✕
- Connections
- 2 pairs of types, where a type in InventoryService.Application.Handlers uses a type in InventoryService.Infrastructure.Interfaces.
- The types involved
InventoryService.Application.Handlers.InventoryCommandHandler→InventoryService.Infrastructure.Interfaces.IInventoryRepositoryInventoryService.Application.Handlers.InventoryQueryHandler→InventoryService.Infrastructure.Interfaces.IInventoryRepository
- Direction
- InventoryService.Application.Handlers uses InventoryService.Infrastructure.Interfaces, so a change to InventoryService.Infrastructure.Interfaces can break InventoryService.Application.Handlers, while a change to InventoryService.Application.Handlers can't break InventoryService.Infrastructure.Interfaces.
- Position
- Below the diagonal: InventoryService.Application.Handlers uses a module listed above it, which is the healthy direction.
31→5 InventoryService.Infrastructure.Repositories uses InventoryService.Domain.Entities✕
- Connections
- 1 pair of types, where a type in InventoryService.Infrastructure.Repositories uses a type in InventoryService.Domain.Entities.
- The types involved
InventoryService.Infrastructure.Repositories.InventoryRepository→InventoryService.Domain.Entities.InventoryItem
- Direction
- InventoryService.Infrastructure.Repositories uses InventoryService.Domain.Entities, so a change to InventoryService.Domain.Entities can break InventoryService.Infrastructure.Repositories, while a change to InventoryService.Infrastructure.Repositories can't break InventoryService.Domain.Entities.
- Position
- Below the diagonal: InventoryService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
31→12 InventoryService.Infrastructure.Repositories uses Shared.RedisCache✕
- Connections
- 1 pair of types, where a type in InventoryService.Infrastructure.Repositories uses a type in Shared.RedisCache.
- The types involved
InventoryService.Infrastructure.Repositories.InventoryRepository→Shared.RedisCache.ICacheService
- Direction
- InventoryService.Infrastructure.Repositories uses Shared.RedisCache, so a change to Shared.RedisCache can break InventoryService.Infrastructure.Repositories, while a change to InventoryService.Infrastructure.Repositories can't break Shared.RedisCache.
- Position
- Below the diagonal: InventoryService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
31→18 InventoryService.Infrastructure.Repositories uses InventoryService.Infrastructure.Interfaces✕
- Connections
- 1 pair of types, where a type in InventoryService.Infrastructure.Repositories uses a type in InventoryService.Infrastructure.Interfaces.
- The types involved
InventoryService.Infrastructure.Repositories.InventoryRepository→InventoryService.Infrastructure.Interfaces.IInventoryRepository
- Direction
- InventoryService.Infrastructure.Repositories uses InventoryService.Infrastructure.Interfaces, so a change to InventoryService.Infrastructure.Interfaces can break InventoryService.Infrastructure.Repositories, while a change to InventoryService.Infrastructure.Repositories can't break InventoryService.Infrastructure.Interfaces.
- Position
- Below the diagonal: InventoryService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
31→24 InventoryService.Infrastructure.Repositories uses Shared.Repository✕
- Connections
- 1 pair of types, where a type in InventoryService.Infrastructure.Repositories uses a type in Shared.Repository.
- The types involved
InventoryService.Infrastructure.Repositories.InventoryRepository→Shared.Repository.GenericRepository
- Direction
- InventoryService.Infrastructure.Repositories uses Shared.Repository, so a change to Shared.Repository can break InventoryService.Infrastructure.Repositories, while a change to InventoryService.Infrastructure.Repositories can't break Shared.Repository.
- Position
- Below the diagonal: InventoryService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
32→10 OrderService.Application.Handlers uses Shared.Bases✕
- Connections
- 4 pairs of types, where a type in OrderService.Application.Handlers uses a type in Shared.Bases.
- The types involved
OrderService.Application.Handlers.OrderCommandHandler→Shared.Bases.ResponseOrderService.Application.Handlers.OrderCommandHandler→Shared.Bases.ResponseHandlerOrderService.Application.Handlers.OrderQueryHandler→Shared.Bases.ResponseOrderService.Application.Handlers.OrderQueryHandler→Shared.Bases.ResponseHandler
- Direction
- OrderService.Application.Handlers uses Shared.Bases, so a change to Shared.Bases can break OrderService.Application.Handlers, while a change to OrderService.Application.Handlers can't break Shared.Bases.
- Position
- Below the diagonal: OrderService.Application.Handlers uses a module listed above it, which is the healthy direction.
32→19 OrderService.Application.Handlers uses OrderService.Infrastructure.Interfaces✕
- Connections
- 2 pairs of types, where a type in OrderService.Application.Handlers uses a type in OrderService.Infrastructure.Interfaces.
- The types involved
OrderService.Application.Handlers.OrderCommandHandler→OrderService.Infrastructure.Interfaces.IOrderRepositoryOrderService.Application.Handlers.OrderQueryHandler→OrderService.Infrastructure.Interfaces.IOrderRepository
- Direction
- OrderService.Application.Handlers uses OrderService.Infrastructure.Interfaces, so a change to OrderService.Infrastructure.Interfaces can break OrderService.Application.Handlers, while a change to OrderService.Application.Handlers can't break OrderService.Infrastructure.Interfaces.
- Position
- Below the diagonal: OrderService.Application.Handlers uses a module listed above it, which is the healthy direction.
33→8 OrderService.Infrastructure.Repositories uses ProductService.Domain.Entities✕
- Connections
- 1 pair of types, where a type in OrderService.Infrastructure.Repositories uses a type in ProductService.Domain.Entities.
- The types involved
OrderService.Infrastructure.Repositories.OrderRepository→ProductService.Domain.Entities.Product
- Direction
- OrderService.Infrastructure.Repositories uses ProductService.Domain.Entities, so a change to ProductService.Domain.Entities can break OrderService.Infrastructure.Repositories, while a change to OrderService.Infrastructure.Repositories can't break ProductService.Domain.Entities.
- Position
- Below the diagonal: OrderService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
33→10 OrderService.Infrastructure.Repositories uses Shared.Bases✕
- Connections
- 1 pair of types, where a type in OrderService.Infrastructure.Repositories uses a type in Shared.Bases.
- The types involved
OrderService.Infrastructure.Repositories.OrderRepository→Shared.Bases.Response
- Direction
- OrderService.Infrastructure.Repositories uses Shared.Bases, so a change to Shared.Bases can break OrderService.Infrastructure.Repositories, while a change to OrderService.Infrastructure.Repositories can't break Shared.Bases.
- Position
- Below the diagonal: OrderService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
33→19 OrderService.Infrastructure.Repositories uses OrderService.Infrastructure.Interfaces✕
- Connections
- 1 pair of types, where a type in OrderService.Infrastructure.Repositories uses a type in OrderService.Infrastructure.Interfaces.
- The types involved
OrderService.Infrastructure.Repositories.OrderRepository→OrderService.Infrastructure.Interfaces.IOrderRepository
- Direction
- OrderService.Infrastructure.Repositories uses OrderService.Infrastructure.Interfaces, so a change to OrderService.Infrastructure.Interfaces can break OrderService.Infrastructure.Repositories, while a change to OrderService.Infrastructure.Repositories can't break OrderService.Infrastructure.Interfaces.
- Position
- Below the diagonal: OrderService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
33→24 OrderService.Infrastructure.Repositories uses Shared.Repository✕
- Connections
- 1 pair of types, where a type in OrderService.Infrastructure.Repositories uses a type in Shared.Repository.
- The types involved
OrderService.Infrastructure.Repositories.OrderRepository→Shared.Repository.GenericRepository
- Direction
- OrderService.Infrastructure.Repositories uses Shared.Repository, so a change to Shared.Repository can break OrderService.Infrastructure.Repositories, while a change to OrderService.Infrastructure.Repositories can't break Shared.Repository.
- Position
- Below the diagonal: OrderService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
34→6 Payment.Application.Handlers uses Payment.Domain.Entities✕
- Connections
- 1 pair of types, where a type in Payment.Application.Handlers uses a type in Payment.Domain.Entities.
- The types involved
Payment.Application.Handlers.PaymentCommandHandler→Payment.Domain.Entities.Payment
- Direction
- Payment.Application.Handlers uses Payment.Domain.Entities, so a change to Payment.Domain.Entities can break Payment.Application.Handlers, while a change to Payment.Application.Handlers can't break Payment.Domain.Entities.
- Position
- Below the diagonal: Payment.Application.Handlers uses a module listed above it, which is the healthy direction.
34→10 Payment.Application.Handlers uses Shared.Bases✕
- Connections
- 4 pairs of types, where a type in Payment.Application.Handlers uses a type in Shared.Bases.
- The types involved
Payment.Application.Handlers.PaymentCommandHandler→Shared.Bases.ResponsePayment.Application.Handlers.PaymentCommandHandler→Shared.Bases.ResponseHandlerPayment.Application.Handlers.PaymentQueryHandler→Shared.Bases.ResponsePayment.Application.Handlers.PaymentQueryHandler→Shared.Bases.ResponseHandler
- Direction
- Payment.Application.Handlers uses Shared.Bases, so a change to Shared.Bases can break Payment.Application.Handlers, while a change to Payment.Application.Handlers can't break Shared.Bases.
- Position
- Below the diagonal: Payment.Application.Handlers uses a module listed above it, which is the healthy direction.
34→20 Payment.Application.Handlers uses Payment.Application.Commands✕
- Connections
- 2 pairs of types, where a type in Payment.Application.Handlers uses a type in Payment.Application.Commands.
- The types involved
Payment.Application.Handlers.PaymentCommandHandler→Payment.Application.Commands.CreatePaymentCommandPayment.Application.Handlers.PaymentCommandHandler→Payment.Application.Commands.UpdatePaymentStatusCommand
- Direction
- Payment.Application.Handlers uses Payment.Application.Commands, so a change to Payment.Application.Commands can break Payment.Application.Handlers, while a change to Payment.Application.Handlers can't break Payment.Application.Commands.
- Position
- Below the diagonal: Payment.Application.Handlers uses a module listed above it, which is the healthy direction.
34→21 Payment.Application.Handlers uses Payment.Infrastructure.Interfaces✕
- Connections
- 2 pairs of types, where a type in Payment.Application.Handlers uses a type in Payment.Infrastructure.Interfaces.
- The types involved
Payment.Application.Handlers.PaymentCommandHandler→Payment.Infrastructure.Interfaces.IPaymentRepositoryPayment.Application.Handlers.PaymentQueryHandler→Payment.Infrastructure.Interfaces.IPaymentRepository
- Direction
- Payment.Application.Handlers uses Payment.Infrastructure.Interfaces, so a change to Payment.Infrastructure.Interfaces can break Payment.Application.Handlers, while a change to Payment.Application.Handlers can't break Payment.Infrastructure.Interfaces.
- Position
- Below the diagonal: Payment.Application.Handlers uses a module listed above it, which is the healthy direction.
35→6 Payment.Infrastructure.Repositories uses Payment.Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Payment.Infrastructure.Repositories uses a type in Payment.Domain.Entities.
- The types involved
Payment.Infrastructure.Repositories.PaymentProcessor→Payment.Domain.Entities.PaymentPayment.Infrastructure.Repositories.PaymentRepository→Payment.Domain.Entities.Payment
- Direction
- Payment.Infrastructure.Repositories uses Payment.Domain.Entities, so a change to Payment.Domain.Entities can break Payment.Infrastructure.Repositories, while a change to Payment.Infrastructure.Repositories can't break Payment.Domain.Entities.
- Position
- Below the diagonal: Payment.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
35→21 Payment.Infrastructure.Repositories uses Payment.Infrastructure.Interfaces✕
- Connections
- 2 pairs of types, where a type in Payment.Infrastructure.Repositories uses a type in Payment.Infrastructure.Interfaces.
- The types involved
Payment.Infrastructure.Repositories.PaymentProcessor→Payment.Infrastructure.Interfaces.IPaymentProcessorPayment.Infrastructure.Repositories.PaymentRepository→Payment.Infrastructure.Interfaces.IPaymentRepository
- Direction
- Payment.Infrastructure.Repositories uses Payment.Infrastructure.Interfaces, so a change to Payment.Infrastructure.Interfaces can break Payment.Infrastructure.Repositories, while a change to Payment.Infrastructure.Repositories can't break Payment.Infrastructure.Interfaces.
- Position
- Below the diagonal: Payment.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
35→24 Payment.Infrastructure.Repositories uses Shared.Repository✕
- Connections
- 1 pair of types, where a type in Payment.Infrastructure.Repositories uses a type in Shared.Repository.
- The types involved
Payment.Infrastructure.Repositories.PaymentRepository→Shared.Repository.GenericRepository
- Direction
- Payment.Infrastructure.Repositories uses Shared.Repository, so a change to Shared.Repository can break Payment.Infrastructure.Repositories, while a change to Payment.Infrastructure.Repositories can't break Shared.Repository.
- Position
- Below the diagonal: Payment.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
36→7 ProductService.Application.Handlers uses ProductService.Domain.Dtos✕
- Connections
- 2 pairs of types, where a type in ProductService.Application.Handlers uses a type in ProductService.Domain.Dtos.
- The types involved
ProductService.Application.Handlers.ProductQueryHandler→ProductService.Domain.Dtos.ProductDtoProductService.Application.Handlers.ProductQueryHandler→ProductService.Domain.Dtos.ProductStockDto
- Direction
- ProductService.Application.Handlers uses ProductService.Domain.Dtos, so a change to ProductService.Domain.Dtos can break ProductService.Application.Handlers, while a change to ProductService.Application.Handlers can't break ProductService.Domain.Dtos.
- Position
- Below the diagonal: ProductService.Application.Handlers uses a module listed above it, which is the healthy direction.
36→10 ProductService.Application.Handlers uses Shared.Bases✕
- Connections
- 4 pairs of types, where a type in ProductService.Application.Handlers uses a type in Shared.Bases.
- The types involved
ProductService.Application.Handlers.ProductCommandHandler→Shared.Bases.ResponseProductService.Application.Handlers.ProductCommandHandler→Shared.Bases.ResponseHandlerProductService.Application.Handlers.ProductQueryHandler→Shared.Bases.ResponseProductService.Application.Handlers.ProductQueryHandler→Shared.Bases.ResponseHandler
- Direction
- ProductService.Application.Handlers uses Shared.Bases, so a change to Shared.Bases can break ProductService.Application.Handlers, while a change to ProductService.Application.Handlers can't break Shared.Bases.
- Position
- Below the diagonal: ProductService.Application.Handlers uses a module listed above it, which is the healthy direction.
36→22 ProductService.Application.Handlers uses ProductService.Application.Commands✕
- Connections
- 2 pairs of types, where a type in ProductService.Application.Handlers uses a type in ProductService.Application.Commands.
- The types involved
ProductService.Application.Handlers.ProductCommandHandler→ProductService.Application.Commands.CreateProductCommandProductService.Application.Handlers.ProductCommandHandler→ProductService.Application.Commands.DeleteProductCommand
- Direction
- ProductService.Application.Handlers uses ProductService.Application.Commands, so a change to ProductService.Application.Commands can break ProductService.Application.Handlers, while a change to ProductService.Application.Handlers can't break ProductService.Application.Commands.
- Position
- Below the diagonal: ProductService.Application.Handlers uses a module listed above it, which is the healthy direction.
36→23 ProductService.Application.Handlers uses ProductService.Infrastructure.Interfaces✕
- Connections
- 2 pairs of types, where a type in ProductService.Application.Handlers uses a type in ProductService.Infrastructure.Interfaces.
- The types involved
ProductService.Application.Handlers.ProductCommandHandler→ProductService.Infrastructure.Interfaces.IProductRepositoryProductService.Application.Handlers.ProductQueryHandler→ProductService.Infrastructure.Interfaces.IProductRepository
- Direction
- ProductService.Application.Handlers uses ProductService.Infrastructure.Interfaces, so a change to ProductService.Infrastructure.Interfaces can break ProductService.Application.Handlers, while a change to ProductService.Application.Handlers can't break ProductService.Infrastructure.Interfaces.
- Position
- Below the diagonal: ProductService.Application.Handlers uses a module listed above it, which is the healthy direction.
37→4 ProductService.Infrastructure.Repositories uses InventoryService.Domain.Dtos✕
- Connections
- 1 pair of types, where a type in ProductService.Infrastructure.Repositories uses a type in InventoryService.Domain.Dtos.
- The types involved
ProductService.Infrastructure.Repositories.ProductRepository→InventoryService.Domain.Dtos.LowStockDto
- Direction
- ProductService.Infrastructure.Repositories uses InventoryService.Domain.Dtos, so a change to InventoryService.Domain.Dtos can break ProductService.Infrastructure.Repositories, while a change to ProductService.Infrastructure.Repositories can't break InventoryService.Domain.Dtos.
- Position
- Below the diagonal: ProductService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
37→7 ProductService.Infrastructure.Repositories uses ProductService.Domain.Dtos✕
- Connections
- 1 pair of types, where a type in ProductService.Infrastructure.Repositories uses a type in ProductService.Domain.Dtos.
- The types involved
ProductService.Infrastructure.Repositories.ProductRepository→ProductService.Domain.Dtos.ProductStockDto
- Direction
- ProductService.Infrastructure.Repositories uses ProductService.Domain.Dtos, so a change to ProductService.Domain.Dtos can break ProductService.Infrastructure.Repositories, while a change to ProductService.Infrastructure.Repositories can't break ProductService.Domain.Dtos.
- Position
- Below the diagonal: ProductService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
37→8 ProductService.Infrastructure.Repositories uses ProductService.Domain.Entities✕
- Connections
- 1 pair of types, where a type in ProductService.Infrastructure.Repositories uses a type in ProductService.Domain.Entities.
- The types involved
ProductService.Infrastructure.Repositories.ProductRepository→ProductService.Domain.Entities.Product
- Direction
- ProductService.Infrastructure.Repositories uses ProductService.Domain.Entities, so a change to ProductService.Domain.Entities can break ProductService.Infrastructure.Repositories, while a change to ProductService.Infrastructure.Repositories can't break ProductService.Domain.Entities.
- Position
- Below the diagonal: ProductService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
37→12 ProductService.Infrastructure.Repositories uses Shared.RedisCache✕
- Connections
- 1 pair of types, where a type in ProductService.Infrastructure.Repositories uses a type in Shared.RedisCache.
- The types involved
ProductService.Infrastructure.Repositories.ProductRepository→Shared.RedisCache.ICacheService
- Direction
- ProductService.Infrastructure.Repositories uses Shared.RedisCache, so a change to Shared.RedisCache can break ProductService.Infrastructure.Repositories, while a change to ProductService.Infrastructure.Repositories can't break Shared.RedisCache.
- Position
- Below the diagonal: ProductService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
37→23 ProductService.Infrastructure.Repositories uses ProductService.Infrastructure.Interfaces✕
- Connections
- 1 pair of types, where a type in ProductService.Infrastructure.Repositories uses a type in ProductService.Infrastructure.Interfaces.
- The types involved
ProductService.Infrastructure.Repositories.ProductRepository→ProductService.Infrastructure.Interfaces.IProductRepository
- Direction
- ProductService.Infrastructure.Repositories uses ProductService.Infrastructure.Interfaces, so a change to ProductService.Infrastructure.Interfaces can break ProductService.Infrastructure.Repositories, while a change to ProductService.Infrastructure.Repositories can't break ProductService.Infrastructure.Interfaces.
- Position
- Below the diagonal: ProductService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
37→24 ProductService.Infrastructure.Repositories uses Shared.Repository✕
- Connections
- 1 pair of types, where a type in ProductService.Infrastructure.Repositories uses a type in Shared.Repository.
- The types involved
ProductService.Infrastructure.Repositories.ProductRepository→Shared.Repository.GenericRepository
- Direction
- ProductService.Infrastructure.Repositories uses Shared.Repository, so a change to Shared.Repository can break ProductService.Infrastructure.Repositories, while a change to ProductService.Infrastructure.Repositories can't break Shared.Repository.
- Position
- Below the diagonal: ProductService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
38→25 WishlistService.Application.Handlers uses WishlistService.Infrastructure.Interfaces✕
- Connections
- 2 pairs of types, where a type in WishlistService.Application.Handlers uses a type in WishlistService.Infrastructure.Interfaces.
- The types involved
WishlistService.Application.Handlers.WishlistCommandHandler→WishlistService.Infrastructure.Interfaces.IWishlistRepositoryWishlistService.Application.Handlers.WishlistQueryHandler→WishlistService.Infrastructure.Interfaces.IWishlistRepository
- Direction
- WishlistService.Application.Handlers uses WishlistService.Infrastructure.Interfaces, so a change to WishlistService.Infrastructure.Interfaces can break WishlistService.Application.Handlers, while a change to WishlistService.Application.Handlers can't break WishlistService.Infrastructure.Interfaces.
- Position
- Below the diagonal: WishlistService.Application.Handlers uses a module listed above it, which is the healthy direction.
39→12 WishlistService.Infrastructure.Repositories uses Shared.RedisCache✕
- Connections
- 1 pair of types, where a type in WishlistService.Infrastructure.Repositories uses a type in Shared.RedisCache.
- The types involved
WishlistService.Infrastructure.Repositories.WishlistRepository→Shared.RedisCache.ICacheService
- Direction
- WishlistService.Infrastructure.Repositories uses Shared.RedisCache, so a change to Shared.RedisCache can break WishlistService.Infrastructure.Repositories, while a change to WishlistService.Infrastructure.Repositories can't break Shared.RedisCache.
- Position
- Below the diagonal: WishlistService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
39→24 WishlistService.Infrastructure.Repositories uses Shared.Repository✕
- Connections
- 1 pair of types, where a type in WishlistService.Infrastructure.Repositories uses a type in Shared.Repository.
- The types involved
WishlistService.Infrastructure.Repositories.WishlistRepository→Shared.Repository.GenericRepository
- Direction
- WishlistService.Infrastructure.Repositories uses Shared.Repository, so a change to Shared.Repository can break WishlistService.Infrastructure.Repositories, while a change to WishlistService.Infrastructure.Repositories can't break Shared.Repository.
- Position
- Below the diagonal: WishlistService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
39→25 WishlistService.Infrastructure.Repositories uses WishlistService.Infrastructure.Interfaces✕
- Connections
- 1 pair of types, where a type in WishlistService.Infrastructure.Repositories uses a type in WishlistService.Infrastructure.Interfaces.
- The types involved
WishlistService.Infrastructure.Repositories.WishlistRepository→WishlistService.Infrastructure.Interfaces.IWishlistRepository
- Direction
- WishlistService.Infrastructure.Repositories uses WishlistService.Infrastructure.Interfaces, so a change to WishlistService.Infrastructure.Interfaces can break WishlistService.Infrastructure.Repositories, while a change to WishlistService.Infrastructure.Repositories can't break WishlistService.Infrastructure.Interfaces.
- Position
- Below the diagonal: WishlistService.Infrastructure.Repositories uses a module listed above it, which is the healthy direction.
40→1 Auth.Application.Handlers uses Auth.Domain.Entities✕
- Connections
- 3 pairs of types, where a type in Auth.Application.Handlers uses a type in Auth.Domain.Entities.
- The types involved
Auth.Application.Handlers.AppUserHandler→Auth.Domain.Entities.AppUserAuth.Application.Handlers.AppUserQueryHandler→Auth.Domain.Entities.AppUserAuth.Application.Handlers.AuthHandler→Auth.Domain.Entities.AppUser
- Direction
- Auth.Application.Handlers uses Auth.Domain.Entities, so a change to Auth.Domain.Entities can break Auth.Application.Handlers, while a change to Auth.Application.Handlers can't break Auth.Domain.Entities.
- Position
- Below the diagonal: Auth.Application.Handlers uses a module listed above it, which is the healthy direction.
40→2 Auth.Application.Handlers uses Auth.Domain.Responses✕
- Connections
- 1 pair of types, where a type in Auth.Application.Handlers uses a type in Auth.Domain.Responses.
- The types involved
Auth.Application.Handlers.AuthHandler→Auth.Domain.Responses.AuthResponse
- Direction
- Auth.Application.Handlers uses Auth.Domain.Responses, so a change to Auth.Domain.Responses can break Auth.Application.Handlers, while a change to Auth.Application.Handlers can't break Auth.Domain.Responses.
- Position
- Below the diagonal: Auth.Application.Handlers uses a module listed above it, which is the healthy direction.
40→10 Auth.Application.Handlers uses Shared.Bases✕
- Connections
- 6 pairs of types, where a type in Auth.Application.Handlers uses a type in Shared.Bases.
- The types involved
Auth.Application.Handlers.AppUserHandler→Shared.Bases.ResponseAuth.Application.Handlers.AppUserHandler→Shared.Bases.ResponseHandlerAuth.Application.Handlers.AppUserQueryHandler→Shared.Bases.ResponseAuth.Application.Handlers.AppUserQueryHandler→Shared.Bases.ResponseHandlerAuth.Application.Handlers.AuthHandler→Shared.Bases.ResponseAuth.Application.Handlers.AuthHandler→Shared.Bases.ResponseHandler
- Direction
- Auth.Application.Handlers uses Shared.Bases, so a change to Shared.Bases can break Auth.Application.Handlers, while a change to Auth.Application.Handlers can't break Shared.Bases.
- Position
- Below the diagonal: Auth.Application.Handlers uses a module listed above it, which is the healthy direction.
40→13 Auth.Application.Handlers uses Auth.Application.Commands✕
- Connections
- 13 pairs of types, where a type in Auth.Application.Handlers uses a type in Auth.Application.Commands.
- The types involved
Auth.Application.Handlers.AppUserHandler→Auth.Application.Commands.DeleteAppUserCommandAuth.Application.Handlers.AppUserHandler→Auth.Application.Commands.RegisterAdminCommandAuth.Application.Handlers.AppUserHandler→Auth.Application.Commands.RegisterUserCommandAuth.Application.Handlers.AppUserHandler→Auth.Application.Commands.UpdateAppUserCommandAuth.Application.Handlers.AppUserHandler→Auth.Application.Commands.UpdateProfileRequestAuth.Application.Handlers.AuthHandler→Auth.Application.Commands.ChangePasswordCommandAuth.Application.Handlers.AuthHandler→Auth.Application.Commands.ConfirmEmailCommandAuth.Application.Handlers.AuthHandler→Auth.Application.Commands.ForgotPasswordCommandAuth.Application.Handlers.AuthHandler→Auth.Application.Commands.GoogleLoginCallbackCommandAuth.Application.Handlers.AuthHandler→Auth.Application.Commands.GoogleLoginCommandAuth.Application.Handlers.AuthHandler→Auth.Application.Commands.LoginCommandAuth.Application.Handlers.AuthHandler→Auth.Application.Commands.RefreshTokenCommandAuth.Application.Handlers.AuthHandler→Auth.Application.Commands.ResetPasswordCommand
- Direction
- Auth.Application.Handlers uses Auth.Application.Commands, so a change to Auth.Application.Commands can break Auth.Application.Handlers, while a change to Auth.Application.Handlers can't break Auth.Application.Commands.
- Position
- Below the diagonal: Auth.Application.Handlers uses a module listed above it, which is the healthy direction.
40→14 Auth.Application.Handlers uses Auth.Application.Queries✕
- Connections
- 2 pairs of types, where a type in Auth.Application.Handlers uses a type in Auth.Application.Queries.
- The types involved
Auth.Application.Handlers.AppUserQueryHandler→Auth.Application.Queries.GetAllAppUsersAuth.Application.Handlers.AppUserQueryHandler→Auth.Application.Queries.GetAppUserById
- Direction
- Auth.Application.Handlers uses Auth.Application.Queries, so a change to Auth.Application.Queries can break Auth.Application.Handlers, while a change to Auth.Application.Handlers can't break Auth.Application.Queries.
- Position
- Below the diagonal: Auth.Application.Handlers uses a module listed above it, which is the healthy direction.
40→15 Auth.Application.Handlers uses Auth.Infrastructure.Interfaces✕
- Connections
- 3 pairs of types, where a type in Auth.Application.Handlers uses a type in Auth.Infrastructure.Interfaces.
- The types involved
Auth.Application.Handlers.AuthHandler→Auth.Infrastructure.Interfaces.IEmailServiceAuth.Application.Handlers.AuthHandler→Auth.Infrastructure.Interfaces.IGoogleServiceAuth.Application.Handlers.AuthHandler→Auth.Infrastructure.Interfaces.IJwtService
- Direction
- Auth.Application.Handlers uses Auth.Infrastructure.Interfaces, so a change to Auth.Infrastructure.Interfaces can break Auth.Application.Handlers, while a change to Auth.Application.Handlers can't break Auth.Infrastructure.Interfaces.
- Position
- Below the diagonal: Auth.Application.Handlers uses a module listed above it, which is the healthy direction.
40→26 Auth.Application.Handlers uses Auth.Application.Helpers✕
- Connections
- 1 pair of types, where a type in Auth.Application.Handlers uses a type in Auth.Application.Helpers.
- The types involved
Auth.Application.Handlers.AppUserHandler→Auth.Application.Helpers.IUserRegistrationHelper
- Direction
- Auth.Application.Handlers uses Auth.Application.Helpers, so a change to Auth.Application.Helpers can break Auth.Application.Handlers, while a change to Auth.Application.Handlers can't break Auth.Application.Helpers.
- Position
- Below the diagonal: Auth.Application.Handlers uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 52 | Medium |
| A02:2025 — Security Misconfiguration | 26 | Medium |
| A01:2025 — Broken Access Control | 1 | Medium |
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.9 pts | Low | ADR Quality |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +5.2 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +5.2 pts | Medium | Security & performance tooling |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +5.2 pts | Medium | DR & Backup |
| Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, CartRepository.cs, OrderCommandHandler.cs. | +3.9 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.7 pts | Medium | Architecture documentation |
| 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. | +2.4 pts | Medium | Observability |
| Resolve the 51 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (12), REDACTED (9), REDACTED (7). | +2.1 pts | Medium | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/ProductService/ProductService.Application/Handlers/ProductCommandHandler.cs | 5.8 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| src/OrderService/OrderService.Application/Handlers/OrderCommandHandler.cs | 5.8 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/SharedService/Shared/Interfaces/IGenericRepository.cs | 6.4 | Mixed | Explicit Debt: Dead code: DeleteRangeAsync |
| src/CartService/CartService.Application/CartService.Application.csproj | 7.0 | Mixed | Coupling: Layer violation: Application → Infrastructure |
| src/OrderService/OrderService.Application/OrderService.Application.csproj | 7.0 | Mixed | Coupling: Layer violation: Application → Infrastructure |
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 87 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 — 87 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, 303 of 320 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes, and real coverage will be read. You can widen what we reach: optional: your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes, and the real number is read on the next scan.
- 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. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
- 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 56 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.
- D18 Solution Shape — evaluation did not complete — Dimension evaluation failed — excluded from the score.
- 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.
- 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 — 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 measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D32 Data Compliance (PII/GDPR) — 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. `REDACTED`, `REDACTED`, `REDACTED`, `REDACTED`, `REDACTED`, … (+1 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 16 | RUN dotnet restore "./src/WishListService/WishlistService.Api/WishlistService.Api.csproj" 17 | COPY . . -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref da5637f0-a1cb-4ef5-9ef0-c46b38f6f280::rzsys70d6b8jsrv8b10qyw92y: "/src/WishListService/WishlistService.Api/WishlistService.Api.csproj": not found; runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — 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. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
- X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 97 further occurrence(s) are not listed individually; the score already reflects all 137.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- 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.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- 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.
- 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").
- 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.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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.
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
8 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with StockEventConsumer.cs, CartRepository.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with HttpClientServiceExtensions.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (12 lines × 3) finding(s) in Code Duplication — start with HttpClientServiceExtensions.cs. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
37 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 10 Layer violation finding(s) in Coupling — start with CartService.Application.csproj (2), OrderService.Application.csproj (2), ProductService.Application.csproj (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 5 Off the main sequence finding(s) in Coupling — start with Auth.Domain.csproj, InventoryService.Domain.csproj, CartService.Domain.csproj. — One of this dimension's main actionable groups (5 warning-level).
- Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 31 classes have LCOM4 above 3.
D9 · Test Distribution
86 test methods: 86 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 1 mock references across 86 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 294 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 33 direct `PackageReference`(s), and 217 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
17 deducted debt markers + 23 dead symbols across 6469 LoC in the .NET projects (1.4/KLoC) → score 7.1.
What to do
- Resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt — start with InventoryQueryHandler.cs, ProductCommandHandler.cs, OrderCommandHandler.cs. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 23 Dead code finding(s) in Explicit Debt — start with IGenericRepository.cs (10), Class1.cs (2), ResponseHandler.cs. — One of this dimension's main actionable groups (23 warning-level).
- Resolve the 8 CommentedOutCode finding(s) in Explicit Debt — start with WishlistCommandValidator.cs (2), REDACTED, ProductCommandHandler.cs. — One of this dimension's main actionable groups (8 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 31 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
2 domain type(s) cross context boundaries across 9 contexts; they are measured and withheld (not published, not scored). Contexts: ApiGateWay, AuthService, CartService, InventoryService, OrderService, PaymentService, ProductService, SharedService, WishListService.
D26 · Project Cohesion
0 of 37 projects flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
52 finding(s): 0 critical, 0 high, 52 medium, 0 low. semgrep hit a parse error in 6 file(s) — `REDACTED` (line 19, line 22, line 23, …), `REDACTED` (lines 11–12, line 65), `REDACTED` (lines 10–11, line 60), `REDACTED` (lines 10–11, line 46), `REDACTED` (lines 12–13, line 76), … (+1 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 6 of those file(s) — `REDACTED`, `REDACTED`, `REDACTED`, `REDACTED`, `REDACTED`, … (+1 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 6 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
What to do
- Resolve the 51 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (12), REDACTED (9), REDACTED (7). — One of this dimension's main actionable groups (51 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
26 finding(s): 0 critical, 0 high, 18 medium, 8 low.
What to do
- Resolve the 18 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (16), REDACTED, REDACTED. — One of this dimension's main actionable groups (18 warning-level).
- Resolve the 8 Low IaC finding(s) in IaC & Container Security — start with REDACTED (8). — One of this dimension's main actionable groups (8 recommendation-level).
D32 · Data Compliance (PII/GDPR)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 6 file(s) — `REDACTED`, `REDACTED`, `REDACTED`, `REDACTED`, `REDACTED`, … (+1 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
What to do
- Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
31 of 31 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 31 of the 235 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, CartRepository.cs, OrderCommandHandler.cs. — One of this dimension's main actionable groups (31 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 37 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
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
AX4 · Dependency direction
- `Auth.Application` is a Application project but references `Auth.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/AuthService/Auth.Application/Auth.Application.csproj:12
- This Application file depends on the Infrastructure project `Auth.Infrastructure`: it names `Auth.Infrastructure.Interfaces`, `IJwtService`, `IGoogleService`, `IEmailService`. The inward dependency rule is broken here. It is named again on lines 30, 31, 32, 34, 35. Depend on an abstraction the inner layer owns, implemented in the outer one. — REDACTED:5
- This Application file depends on the Infrastructure project `Auth.Infrastructure`: it names `Auth.Infrastructure.Interfaces`, `IEmailService`. The inward dependency rule is broken here. It is named again on lines 13, 17. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/AuthService/Auth.Application/Helpers/UserRegistrationHelper.cs:3
- `CartService.Application` is a Application project but references `InventoryService.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/CartService/CartService.Application/CartService.Application.csproj:10
- This Application file depends on the Infrastructure project `InventoryService.Infrastructure`: it names `InventoryService.Infrastructure.Interfaces`, `IInventoryRepository`. The inward dependency rule is broken here. It is named again on line 33. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/CartService/CartService.Application/BackgroundServices/StockEventConsumer.cs:2
- `CartService.Application` is a Application project but references `CartService.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/CartService/CartService.Application/CartService.Application.csproj:13
- This Application file depends on the Infrastructure project `CartService.Infrastructure`: it names `CartService.Infrastructure.Interfaces`, `ICartRepository`. The inward dependency rule is broken here. It is named again on lines 18, 25. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/CartService/CartService.Application/Handlers/CartCommandHandler.cs:5
- This Application file depends on the Infrastructure project `CartService.Infrastructure`: it names `CartService.Infrastructure.Interfaces`, `ICartRepository`. The inward dependency rule is broken here. It is named again on lines 15, 21. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/CartService/CartService.Application/Handlers/CartQueryHandler.cs:4
- This Application file depends on the Infrastructure project `CartService.Infrastructure`: it names `CartService.Infrastructure.Interfaces`, `ICartRepository`. The inward dependency rule is broken here. It is named again on lines 9, 11. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/CartService/CartService.Application/Validators/ValidateCartExists.cs:1
- `InventoryService.Application` is a Application project but references `InventoryService.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/InventoryService/InventoryService.Application/InventoryService.Application.csproj:12
- This Application file depends on the Infrastructure project `InventoryService.Infrastructure`: it names `InventoryService.Infrastructure.Interfaces`, `IInventoryRepository`. The inward dependency rule is broken here. It is named again on line 40. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/InventoryService/InventoryService.Application/BackgroundServices/ProductCreatedEventConsumer.cs:2
- This Application file depends on the Infrastructure project `InventoryService.Infrastructure`: it names `InventoryService.Infrastructure.Interfaces`, `IInventoryRepository`. The inward dependency rule is broken here. It is named again on lines 15, 18. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/InventoryService/InventoryService.Application/Handlers/InventoryCommandHandler.cs:3
- This Application file depends on the Infrastructure project `InventoryService.Infrastructure`: it names `InventoryService.Infrastructure.Interfaces`, `IInventoryRepository`. The inward dependency rule is broken here. It is named again on lines 15, 21. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/InventoryService/InventoryService.Application/Handlers/InventoryQueryHandler.cs:4
- `OrderService.Application` is a Application project but references `Payment.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/OrderService/OrderService.Application/OrderService.Application.csproj:13
- `OrderService.Application` is a Application project but references `OrderService.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/OrderService/OrderService.Application/OrderService.Application.csproj:15
- This Application file depends on the Infrastructure project `OrderService.Infrastructure`: it names `OrderService.Infrastructure.Interfaces`, `IOrderRepository`. The inward dependency rule is broken here. It is named again on lines 25, 34. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/OrderService/OrderService.Application/Handlers/OrderCommandHandler.cs:11
- This Application file depends on the Infrastructure project `OrderService.Infrastructure`: it names `OrderService.Infrastructure.Interfaces`, `IOrderRepository`. The inward dependency rule is broken here. It is named again on lines 14, 19. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/OrderService/OrderService.Application/Handlers/OrderQueryHandler.cs:5
- This Application file depends on the Infrastructure project `OrderService.Infrastructure`: it names `OrderService.Infrastructure.Interfaces`, `IOrderRepository`. The inward dependency rule is broken here. It is named again on lines 9, 11. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/OrderService/OrderService.Application/Validators/ValidateOrderExists.cs:1
- `Payment.Application` is a Application project but references `Payment.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/PaymentService/Payment.Application/Payment.Application.csproj:13
- This Application file depends on the Infrastructure project `Payment.Infrastructure`: it names `Payment.Infrastructure.Interfaces`, `IPaymentRepository`, `IPaymentProcessor`. The inward dependency rule is broken here. It is named again on lines 40, 41. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PaymentService/Payment.Application/BackgroundServices/OrderCreatedEventConsumer.cs:6
- This Application file depends on the Infrastructure project `Payment.Infrastructure`: it names `Payment.Infrastructure.Interfaces`, `IPaymentRepository`. The inward dependency rule is broken here. It is named again on line 37. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PaymentService/Payment.Application/BackgroundServices/PaymentProcessedEventConsumer.cs:4
- This Application file depends on the Infrastructure project `Payment.Infrastructure`: it names `Payment.Infrastructure.Interfaces`, `IPaymentRepository`. The inward dependency rule is broken here. It is named again on lines 14, 19. Depend on an abstraction the inner layer owns, implemented in the outer one. (×2) — src/PaymentService/Payment.Application/Handlers/PaymentCommandHandler.cs:5, src/PaymentService/Payment.Application/Handlers/PaymentQueryHandler.cs:5
- This Application file depends on the Infrastructure project `Payment.Infrastructure`: it names `Payment.Infrastructure.Interfaces`, `IPaymentRepository`. The inward dependency rule is broken here. It is named again on lines 9, 11. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/PaymentService/Payment.Application/Validators/ValidatePaymentExists.cs:1
- `ProductService.Application` is a Application project but references `InventoryService.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/ProductService/ProductService.Application/ProductService.Application.csproj:10
- `ProductService.Application` is a Application project but references `ProductService.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/ProductService/ProductService.Application/ProductService.Application.csproj:13
- This Application file depends on the Infrastructure project `ProductService.Infrastructure`: it names `ProductService.Infrastructure.Interfaces`, `IProductRepository`. The inward dependency rule is broken here. It is named again on lines 19, 26. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/ProductService/ProductService.Application/Handlers/ProductCommandHandler.cs:7
- This Application file depends on the Infrastructure project `ProductService.Infrastructure`: it names `ProductService.Infrastructure.Interfaces`, `IProductRepository`. The inward dependency rule is broken here. It is named again on lines 19, 24. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/ProductService/ProductService.Application/Handlers/ProductQueryHandler.cs:6
- This Application file depends on the Infrastructure project `ProductService.Infrastructure`: it names `ProductService.Infrastructure.Interfaces`, `IProductRepository`. The inward dependency rule is broken here. It is named again on lines 9, 11. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/ProductService/ProductService.Application/Validators/ValidateProductExists.cs:1
- `WishlistService.Application` is a Application project but references `WishlistService.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/WishListService/WishlistService.Application/WishlistService.Application.csproj:10
- This Application file depends on the Infrastructure project `WishlistService.Infrastructure`: it names `WishlistService.Infrastructure.Interfaces`, `IWishlistRepository`. The inward dependency rule is broken here. It is named again on lines 21, 27. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/WishListService/WishlistService.Application/Handlers/WishlistCommandHandler.cs:9
- This Application file depends on the Infrastructure project `WishlistService.Infrastructure`: it names `WishlistService.Infrastructure.Interfaces`, `IWishlistRepository`. The inward dependency rule is broken here. It is named again on lines 15, 19. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/WishListService/WishlistService.Application/Handlers/WishlistQueryHandler.cs:6
- This Application file depends on the Infrastructure project `WishlistService.Infrastructure`: it names `WishlistService.Infrastructure.Interfaces`, `IWishlistRepository`. The inward dependency rule is broken here. It is named again on lines 8, 11. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/WishListService/WishlistService.Application/Validators/ValidateWishlistExists.cs:2
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX5 · Architecture & structure
AX6 · Interface segregation
- `IGenericRepository<T>` declares 21 members: `GetAllAsync`, `GetByAsync`, `DeleteRangeAsync`, `GetByIdAsync`, `GetByIdStringAsync`, `ExistsAsync`, `GetByNameAsync`, `SaveChangesAsync`, `BeginTransaction`, `Commit`, `RollBack`, `GetTableNoTracking`, `GetTableAsTracking`, `AddAsync`, `AddRangeAsync`, `UpdateAsync`, `UpdateRangeAsync`, `DeleteAsync`, `DeleteByIdAsync`, `DeleteByIdStringAsync`, `Exsitance`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/SharedService/Shared/Interfaces/IGenericRepository.cs:6
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
- `Shared` ships in a production host and references `FluentAssertions`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. — src/SharedService/Shared/Shared.csproj:11
- `Shared` ships in a production host and references `Moq`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. — src/SharedService/Shared/Shared.csproj:29
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
C5 · Data-Subject Rights
- Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
What to do
- Implement data export/portability for a data subject (a machine-readable export of their personal data).
- Track GDPR consent (lawful basis) alongside the personal data it authorises.
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
DM5 · Encapsulated state
- `Payment` exposes publicly writable state (Id, OrderId, Amount, PaymentMethod, Status, CreatedAt). — src/PaymentService/Payment.Domain/Entities/Payment.cs:3
- `Order` exposes publicly writable state (CustomerId, Status). — src/OrderService/OrderService.Domain/Entities/Order.cs:5
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
- The domain project `Auth.Domain` references `Microsoft.AspNetCore.Identity.EntityFrameworkCore` — a persistence dependency; the domain should own a port and let an infrastructure project reference it. — src/AuthService/Auth.Domain/Auth.Domain.csproj:10
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM7 · Repository granularity
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED4 · Outbox / dual-write
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×40) — src/ApiGateWay/ApiGateWay.Api/Program.cs:13, REDACTED:98, REDACTED:100, …
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 30 of 30 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
- Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
- Only 5/37 projects share a common root namespace — the code's module identity is inconsistent.
What to do
- Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
- Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- Only 1/23 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 23, 8 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.
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `src/ApiGateWay/ApiGateWay.Api/ApiGateWay.Api.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/ApiGateWay/ApiGateWay.Api/ApiGateWay.Api.csproj:13
What to do
- Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — src/SharedService/Shared/AuthShared/JwtAuthenticationExtensions.cs:18
- `ValidateLifetime = false` means expired tokens keep working indefinitely, so a leaked or revoked token never stops being valid. — REDACTED:212
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×8) — src/ApiGateWay/ApiGateWay.Api/Program.cs:6, src/AuthService/Auth.Api/Program.cs:8, src/CartService/CartService.Api/Program.cs:7, …
What to do
- Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
- Re-enable token validation — `ValidateLifetime` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
- Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×2) — REDACTED:76, REDACTED:77
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 63/179 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×39) — src/SharedService/Shared/RedisCache/CacheService.cs:16, src/SharedService/Shared/RedisCache/CacheService.cs:22, src/SharedService/Shared/Repository/GenericRepository.cs:20, …
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
- `message.Body` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/AuthService/Auth.Infrastructure/Services/EmailService.cs:39
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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
- ~3.3 `!` suppressions per 1k syntax nodes — 147 suppression(s) across the 44471 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 `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 74% | Strong | Solid. |
| Architecture | 69% | Adequate | Acceptable, with room to improve. |
| Maturity | 51% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 26% | Weak — gated by P1, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 53% | Adequate — gated by D29, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 87% | Strong | Solid. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 43 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 16 | RUN dotnet restore "./src/WishListService/WishlistService.Api/WishlistService.Api.csproj" 17 | COPY . . -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref da5637f0-a1cb-4ef5-9ef0-c46b38f6f280::rzsys70d6b8jsrv8b10qyw92y: "WishListService/WishlistService.Api/WishlistService.Api.csproj": not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — Dimension evaluation failed
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1405 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D24 Comment Value — Too few judgeable comments (26 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — analyzer environment
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
- ED3 Event naming — no domain or integration events detected — event-naming check not applicable
- ED5 Idempotency — not scored — 4 of 4 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — no CI workflow found
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 26 finding(s)
- Dependency-rule violation: Auth.Application (Application) → Auth.Infrastructure (Infrastructure) src/AuthService/Auth.Application/Auth.Application.csproj:12
- Dependency-rule violation: CartService.Application (Application) → InventoryService.Infrastructure (Infrastructure) src/CartService/CartService.Application/CartService.Application.csproj:10
- Dependency-rule violation: CartService.Application (Application) → CartService.Infrastructure (Infrastructure) src/CartService/CartService.Application/CartService.Application.csproj:13
- Dependency-rule violation: InventoryService.Application (Application) → InventoryService.Infrastructure (Infrastructure) src/InventoryService/InventoryService.Application/InventoryService.Application.csproj:12
- Dependency-rule violation: OrderService.Application (Application) → Payment.Infrastructure (Infrastructure) src/OrderService/OrderService.Application/OrderService.Application.csproj:13
- Dependency-rule violation: OrderService.Application (Application) → OrderService.Infrastructure (Infrastructure) src/OrderService/OrderService.Application/OrderService.Application.csproj:15
- Dependency-rule violation: Payment.Application (Application) → Payment.Infrastructure (Infrastructure) src/PaymentService/Payment.Application/Payment.Application.csproj:13
- Dependency-rule violation: ProductService.Application (Application) → InventoryService.Infrastructure (Infrastructure) src/ProductService/ProductService.Application/ProductService.Application.csproj:10
- Dependency-rule violation: ProductService.Application (Application) → ProductService.Infrastructure (Infrastructure) src/ProductService/ProductService.Application/ProductService.Application.csproj:13
- Dependency-rule violation: WishlistService.Application (Application) → WishlistService.Infrastructure (Infrastructure) src/WishListService/WishlistService.Application/WishlistService.Application.csproj:10
- Layer violation: Application → Infrastructure src/AuthService/Auth.Application/Auth.Application.csproj:12
- Layer violation: Application → Infrastructure src/CartService/CartService.Application/CartService.Application.csproj:13
- Layer violation: Application → Infrastructure src/CartService/CartService.Application/CartService.Application.csproj:10
- Layer violation: Application → Infrastructure src/InventoryService/InventoryService.Application/InventoryService.Application.csproj:12
- Layer violation: Application → Infrastructure src/OrderService/OrderService.Application/OrderService.Application.csproj:15
- Layer violation: Application → Infrastructure src/OrderService/OrderService.Application/OrderService.Application.csproj:13
- Layer violation: Application → Infrastructure src/PaymentService/Payment.Application/Payment.Application.csproj:13
- Layer violation: Application → Infrastructure src/ProductService/ProductService.Application/ProductService.Application.csproj:10
- Layer violation: Application → Infrastructure src/ProductService/ProductService.Application/ProductService.Application.csproj:13
- Layer violation: Application → Infrastructure src/WishListService/WishlistService.Application/WishlistService.Application.csproj:10
- WriteOnlyPrivateField src/InventoryService/InventoryService.Application/Handlers/InventoryQueryHandler.cs:17
- WriteOnlyPrivateField src/ProductService/ProductService.Application/Handlers/ProductCommandHandler.cs:23
- WriteOnlyPrivateField src/OrderService/OrderService.Application/Handlers/OrderCommandHandler.cs:32
- Production project references a test package: Shared → FluentAssertions src/SharedService/Shared/Shared.csproj:11
- Production project references a test package: Shared → Moq src/SharedService/Shared/Shared.csproj:29
- Domain depends on infrastructure: Auth.Domain src/AuthService/Auth.Domain/Auth.Domain.csproj:10
Serious — 188 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Async method without CancellationToken: GetAsync src/SharedService/Shared/RedisCache/CacheService.cs:16
- Async method without CancellationToken: SetAsync src/SharedService/Shared/RedisCache/CacheService.cs:22
- Async method without CancellationToken: GetByAsync src/SharedService/Shared/Repository/GenericRepository.cs:20
- Async method without CancellationToken: GetByIdAsync src/SharedService/Shared/Repository/GenericRepository.cs:25
- Async method without CancellationToken: GetByIdStringAsync src/SharedService/Shared/Repository/GenericRepository.cs:30
- Async method without CancellationToken: GetByNameAsync src/SharedService/Shared/Repository/GenericRepository.cs:35
- Async method without CancellationToken: AddRangeAsync src/SharedService/Shared/Repository/GenericRepository.cs:45
- Async method without CancellationToken: AddAsync src/SharedService/Shared/Repository/GenericRepository.cs:51
- Async method without CancellationToken: UpdateAsync src/SharedService/Shared/Repository/GenericRepository.cs:58
- Async method without CancellationToken: DeleteAsync src/SharedService/Shared/Repository/GenericRepository.cs:66
- Async method without CancellationToken: DeleteByIdAsync src/SharedService/Shared/Repository/GenericRepository.cs:72
- Async method without CancellationToken: DeleteRangeAsync src/SharedService/Shared/Repository/GenericRepository.cs:97
- Async method without CancellationToken: SaveChangesAsync src/SharedService/Shared/Repository/GenericRepository.cs:103
- Async method without CancellationToken: UpdateRangeAsync src/SharedService/Shared/Repository/GenericRepository.cs:128
- Async method without CancellationToken: GetAllAsync src/SharedService/Shared/Repository/GenericRepository.cs:134
- Async method without CancellationToken: ExistsAsync src/SharedService/Shared/Repository/GenericRepository.cs:144
- Async method without CancellationToken: ValidateEntityExistsAsync src/SharedService/Shared/Repository/ValidationService.cs:7
- Async method without CancellationToken: ToPaginatedListAsync src/SharedService/Shared/Wrapper/QueryableExtensions.cs:7
- Async method without CancellationToken: EnsureRolesCreatedAsync src/AuthService/Auth.Infrastructure/AuthInfrastructureDependencyInjection.cs:110
- Async method without CancellationToken: GoogleLoginCallbackAsync src/AuthService/Auth.Infrastructure/Services/GoogleService.cs:30
- Async method without CancellationToken: RefreshToken REDACTED:115
- Async method without CancellationToken: UpdateUserTokens REDACTED:164
- Async method without CancellationToken: StoreRefreshToken REDACTED:172
- Async method without CancellationToken: RevokeRefreshTokenAsync REDACTED:185
- Async method without CancellationToken: ValidateRefreshToken REDACTED:194
- Dependency-rule violation: Auth.Application (Application) → Auth.Infrastructure (Infrastructure) REDACTED:5
- Dependency-rule violation: Auth.Application (Application) → Auth.Infrastructure (Infrastructure) src/AuthService/Auth.Application/Helpers/UserRegistrationHelper.cs:3
- Dependency-rule violation: CartService.Application (Application) → InventoryService.Infrastructure (Infrastructure) src/CartService/CartService.Application/BackgroundServices/StockEventConsumer.cs:2
- Dependency-rule violation: CartService.Application (Application) → CartService.Infrastructure (Infrastructure) src/CartService/CartService.Application/Handlers/CartCommandHandler.cs:5
- Dependency-rule violation: CartService.Application (Application) → CartService.Infrastructure (Infrastructure) src/CartService/CartService.Application/Handlers/CartQueryHandler.cs:4
- Dependency-rule violation: CartService.Application (Application) → CartService.Infrastructure (Infrastructure) src/CartService/CartService.Application/Validators/ValidateCartExists.cs:1
- Dependency-rule violation: InventoryService.Application (Application) → InventoryService.Infrastructure (Infrastructure) src/InventoryService/InventoryService.Application/BackgroundServices/ProductCreatedEventConsumer.cs:2
- Dependency-rule violation: InventoryService.Application (Application) → InventoryService.Infrastructure (Infrastructure) src/InventoryService/InventoryService.Application/Handlers/InventoryCommandHandler.cs:3
- Dependency-rule violation: InventoryService.Application (Application) → InventoryService.Infrastructure (Infrastructure) src/InventoryService/InventoryService.Application/Handlers/InventoryQueryHandler.cs:4
- Dependency-rule violation: OrderService.Application (Application) → OrderService.Infrastructure (Infrastructure) src/OrderService/OrderService.Application/Handlers/OrderCommandHandler.cs:11
- Dependency-rule violation: OrderService.Application (Application) → OrderService.Infrastructure (Infrastructure) src/OrderService/OrderService.Application/Handlers/OrderQueryHandler.cs:5
- Dependency-rule violation: OrderService.Application (Application) → OrderService.Infrastructure (Infrastructure) src/OrderService/OrderService.Application/Validators/ValidateOrderExists.cs:1
- Dependency-rule violation: Payment.Application (Application) → Payment.Infrastructure (Infrastructure) src/PaymentService/Payment.Application/BackgroundServices/OrderCreatedEventConsumer.cs:6
- Dependency-rule violation: Payment.Application (Application) → Payment.Infrastructure (Infrastructure) src/PaymentService/Payment.Application/BackgroundServices/PaymentProcessedEventConsumer.cs:4
- Dependency-rule violation: Payment.Application (Application) → Payment.Infrastructure (Infrastructure) src/PaymentService/Payment.Application/Handlers/PaymentCommandHandler.cs:5
- Dependency-rule violation: Payment.Application (Application) → Payment.Infrastructure (Infrastructure) src/PaymentService/Payment.Application/Handlers/PaymentQueryHandler.cs:5
- Dependency-rule violation: Payment.Application (Application) → Payment.Infrastructure (Infrastructure) src/PaymentService/Payment.Application/Validators/ValidatePaymentExists.cs:1
- Dependency-rule violation: ProductService.Application (Application) → ProductService.Infrastructure (Infrastructure) src/ProductService/ProductService.Application/Handlers/ProductCommandHandler.cs:7
- Dependency-rule violation: ProductService.Application (Application) → ProductService.Infrastructure (Infrastructure) src/ProductService/ProductService.Application/Handlers/ProductQueryHandler.cs:6
- Dependency-rule violation: ProductService.Application (Application) → ProductService.Infrastructure (Infrastructure) src/ProductService/ProductService.Application/Validators/ValidateProductExists.cs:1
- Dependency-rule violation: WishlistService.Application (Application) → WishlistService.Infrastructure (Infrastructure) src/WishListService/WishlistService.Application/Handlers/WishlistCommandHandler.cs:9
- Dependency-rule violation: WishlistService.Application (Application) → WishlistService.Infrastructure (Infrastructure) src/WishListService/WishlistService.Application/Handlers/WishlistQueryHandler.cs:6
- Dependency-rule violation: WishlistService.Application (Application) → WishlistService.Infrastructure (Infrastructure) src/WishListService/WishlistService.Application/Validators/ValidateWishlistExists.cs:2
- Dead code: Deleted src/SharedService/Shared/Bases/ResponseHandler.cs:16
- Dead code: DeleteRangeAsync src/SharedService/Shared/Interfaces/IGenericRepository.cs:10
- Dead code: ExistsAsync src/SharedService/Shared/Interfaces/IGenericRepository.cs:13
- Dead code: GetByNameAsync src/SharedService/Shared/Interfaces/IGenericRepository.cs:14
- Dead code: Commit src/SharedService/Shared/Interfaces/IGenericRepository.cs:17
- Dead code: RollBack src/SharedService/Shared/Interfaces/IGenericRepository.cs:18
- Dead code: GetTableNoTracking src/SharedService/Shared/Interfaces/IGenericRepository.cs:19
- Dead code: GetTableAsTracking src/SharedService/Shared/Interfaces/IGenericRepository.cs:20
- Dead code: UpdateRangeAsync src/SharedService/Shared/Interfaces/IGenericRepository.cs:24
- Dead code: DeleteByIdStringAsync src/SharedService/Shared/Interfaces/IGenericRepository.cs:27
- Dead code: Exsitance src/SharedService/Shared/Interfaces/IGenericRepository.cs:28
- Dead code: InvokeAsync src/SharedService/Shared/Middleware/ListenToOnlyApiGetWay.cs:17
- Dead code: RoleResponse src/AuthService/Auth.Domain/Responses/RoleResponse.cs:3
- Dead code: UserClaims src/AuthService/Auth.Domain/Responses/UserClaims.cs:3
- Dead code: UserRoles src/AuthService/Auth.Domain/Responses/UserRoles.cs:3
- Dead code: Class1 src/InventoryService/InventoryService.Domain/Class1.cs:3
- Dead code: InventoryItemDto src/InventoryService/InventoryService.Domain/Dtos/InventoryItemDto.cs:3
- Dead code: Deactivate src/ProductService/ProductService.Domain/Entities/Product.cs:30
- Dead code: CartExpirationBackgroundService src/CartService/CartService.Application/BackgroundServices/CartExpirationBackgroundService.cs:3
- Dead code: CartExpiredEvent src/CartService/CartService.Application/Events/CartExpiredEvent.cs:5
- Dead code: Class1 src/PaymentService/Payment.Domain/Class1.cs:3
- Dead code: PaymentPerOrder src/OrderService/OrderService.Application/Commands/PaymentRequest.cs:3
- Dead code: ValidatePaymentExistsAsync src/PaymentService/Payment.Application/Validators/IValidatePaymentExists.cs:5
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- CommentedOutCode REDACTED:98
- CommentedOutCode src/ProductService/ProductService.Application/Handlers/ProductCommandHandler.cs:42
- CommentedOutCode src/SharedService/Shared/SharedDependencyInjection.cs:18
- CommentedOutCode src/AuthService/Auth.Infrastructure/AuthInfrastructureDependencyInjection.cs:97
- CommentedOutCode src/OrderService/OrderService.Application/Handlers/OrderCommandHandler.cs:142
- CommentedOutCode src/SharedService/Shared/Messaging/RabbitMQProducer.cs:17
- CommentedOutCode src/WishListService/WishlistService.Application/Validators/WishlistCommandValidator.cs:26
- CommentedOutCode src/WishListService/WishlistService.Application/Validators/WishlistCommandValidator.cs:31
- Off the main sequence: Auth.Domain src/AuthService/Auth.Domain/Auth.Domain.csproj:1
- Off the main sequence: InventoryService.Domain src/InventoryService/InventoryService.Domain/InventoryService.Domain.csproj:1
- Off the main sequence: CartService.Domain src/CartService/CartService.Domain/CartService.Domain.csproj:1
- Off the main sequence: ProductService.Domain src/ProductService/ProductService.Domain/ProductService.Domain.csproj:1
- Off the main sequence: Payment.Domain src/PaymentService/Payment.Domain/Payment.Domain.csproj:1
- Whole file has no live code — 2 debt markers inside it src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:1
- Whole file has no live code — 2 debt markers inside it src/OrderService/OrderService.Application/EventHandlers/OrderCanceledEventHandler.cs:1
- Whole file has no live code — 2 debt markers inside it src/SharedService/Shared/Messaging/RabbitMQMessageBroker.cs:1
- Duplicated block (8 lines × 2) src/CartService/CartService.Application/BackgroundServices/StockEventConsumer.cs:29
- Duplicated block (8 lines × 2) src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs:184
- Sync-over-async (deadlock risk) through `.Result` REDACTED:76
- Sync-over-async (deadlock risk) through `.Result` REDACTED:77
- No data-protection/encryption
- REDACTED
- REDACTED
- Duplicated block (15 lines × 2) src/CartService/CartService.Infrastructure/Services/HttpClientServiceExtensions.cs:10
- Duplicated block (12 lines × 3) src/CartService/CartService.Infrastructure/Services/HttpClientServiceExtensions.cs:10
- Duplicated block (11 lines × 2) src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs:108
- Duplicated block (9 lines × 3) src/WishListService/WishlistService.Application/Handlers/WishlistCommandHandler.cs:91
- Duplicated block (7 lines × 2) src/InventoryService/InventoryService.Application/Handlers/InventoryCommandHandler.cs:80
- Duplicated block (13 lines × 2) src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs:129
- No CI pipeline
- No DR/backup evidence
- Token validation disabled REDACTED:212
- NuGet dependencies are not locked
- Untrusted text written into markup unescaped src/AuthService/Auth.Infrastructure/Services/EmailService.cs:39
Minor — 104 finding(s)
- Commented-out code src/ApiGateWay/ApiGateWay.Api/Program.cs:13
- Commented-out code REDACTED:98
- Commented-out code REDACTED:100
- Commented-out code REDACTED:113
- Commented-out code src/AuthService/Auth.Infrastructure/AuthInfrastructureDependencyInjection.cs:101
- Commented-out code src/AuthService/Auth.Infrastructure/AuthInfrastructureDependencyInjection.cs:106
- Commented-out code src/CartService/CartService.Application/CartApplicationDependencyInjection.cs:26
- Commented-out code src/CartService/CartService.Application/Handlers/CartCommandHandler.cs:102
- Commented-out code src/CartService/CartService.Application/Handlers/CartCommandHandler.cs:107
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:15
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:16
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:22
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:26
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:27
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:31
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:38
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:40
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:43
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:44
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:48
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:49
- Commented-out code src/InventoryService/InventoryService.Application/EventHandlers/ProductCreatedEventHandler.cs:51
- Commented-out code src/InventoryService/InventoryService.Application/InventoryApplicationDependencyInjection.cs:25
- Commented-out code src/InventoryService/InventoryService.Application/InventoryApplicationDependencyInjection.cs:26
- Commented-out code src/OrderService/OrderService.Application/ApplicationDependencyInjection.cs:26
- Orphaned file REDACTED:1
- Orphaned file src/CartService/CartService.Infrastructure/Repositories/CartRepository.cs:1
- Orphaned file src/OrderService/OrderService.Application/Handlers/OrderCommandHandler.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/WishListService/WishlistService.Application/Handlers/WishlistCommandHandler.cs:1
- Orphaned file src/WishListService/WishlistService.Infrastructure/Repositories/WishlistRepository.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/ProductService/ProductService.Infrastructure/Repositories/ProductRepository.cs:1
- Orphaned file src/CartService/CartService.Application/Handlers/CartCommandHandler.cs:1
- Orphaned file src/ProductService/ProductService.Application/Handlers/ProductQueryHandler.cs:1
- Orphaned file src/InventoryService/InventoryService.Application/Handlers/InventoryCommandHandler.cs:1
- Orphaned file src/AuthService/Auth.Infrastructure/AuthInfrastructureDependencyInjection.cs:1
- Orphaned file src/SharedService/Shared/Repository/GenericRepository.cs:1
- Orphaned file src/OrderService/OrderService.Infrastructure/Repositories/OrderRepository.cs:1
- Orphaned file src/SharedService/Shared/Middleware/ExceptionHandlingMiddleware.cs:1
- Orphaned file src/InventoryService/InventoryService.Infrastructure/Repositories/InventoryRepository.cs:1
- Orphaned file src/ProductService/ProductService.Application/Handlers/ProductCommandHandler.cs:1
- Orphaned file src/AuthService/Auth.Application/Handlers/AppUserHandler.cs:1
- Orphaned file src/PaymentService/Payment.Application/BackgroundServices/OrderCreatedEventConsumer.cs:1
- Orphaned file src/CartService/CartService.Application/BackgroundServices/StockEventConsumer.cs:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file src/PaymentService/Payment.Infrastructure/Repositories/PaymentRepository.cs:1
- Orphaned file src/InventoryService/InventoryService.Application/BackgroundServices/ProductCreatedEventConsumer.cs:1
- Orphaned file src/PaymentService/Payment.Application/BackgroundServices/PaymentProcessedEventConsumer.cs:1
- No security response headers detected
- No security response headers detected src/ApiGateWay/ApiGateWay.Api/Program.cs:6
- No security response headers detected src/AuthService/Auth.Api/Program.cs:8
- No security response headers detected src/CartService/CartService.Api/Program.cs:7
- No security response headers detected src/InventoryService/InventoryService.Api/Program.cs:4
- No security response headers detected src/OrderService/OrderService.Api/Program.cs:11
- No security response headers detected src/PaymentService/Payment.Api/Program.cs:5
- No security response headers detected src/ProductService/ProductService.Api/Program.cs:9
- No security response headers detected src/WishListService/WishlistService.Api/Program.cs:6
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Mutable entity: Payment src/PaymentService/Payment.Domain/Entities/Payment.cs:3
- Mutable entity: Order src/OrderService/OrderService.Domain/Entities/Order.cs:5
- Fat interface: IGenericRepository<T> (21 members) src/SharedService/Shared/Interfaces/IGenericRepository.cs:6
- Partial data-subject-rights support
- No ADRs found
- Dormant codebase
- No ADRs
- No tests/ separation
- Inconsistent root namespaces
- Logging is not universal
- No SAST
- No dependency-update automation src/ApiGateWay/ApiGateWay.Api/ApiGateWay.Api.csproj:13
- No rollback/health safety
- OIDC metadata fetched over HTTP src/SharedService/Shared/AuthShared/JwtAuthenticationExtensions.cs:18
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 2 finding(s)
- Mock framework: Moq
- Off the main sequence: Shared src/SharedService/Shared/Shared.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-00c080edc3264414ac2a3a79af93fe94/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-00c080edc3264414ac2a3a79af93fe94/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/AuthService/Auth.Infrastructure/Migrations --exclude src/CartService/CartService.Infrastructure/Migrations --exclude src/InventoryService/InventoryService.Infrastructure/Migrations --exclude src/OrderService/OrderService.Infrastructure/Migrations --exclude src/PaymentService/Payment.Infrastructure/Migrations --exclude src/ProductService/ProductService.Infrastructure/Migrations --exclude src/WishListService/WishlistService.Infrastructure/Migrations . | 52 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 26 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/AuthService/Auth.Infrastructure/Migrations --exclude src/CartService/CartService.Infrastructure/Migrations --exclude src/InventoryService/InventoryService.Infrastructure/Migrations --exclude src/OrderService/OrderService.Infrastructure/Migrations --exclude src/PaymentService/Payment.Infrastructure/Migrations --exclude src/ProductService/ProductService.Infrastructure/Migrations --exclude src/WishListService/WishlistService.Infrastructure/Migrations . | 1 | artifacts/raw/semgrep-gdpr.json |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-a4f2fde705f240978e09f5d9742b2f46 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 7 field(s)
- ForgotPasswordCommand.Email src/AuthService/Auth.Application/Commands/ForgotPasswordCommand.cs:6
- LoginCommand.Email src/AuthService/Auth.Application/Commands/LoginCommand.cs:7
- RegisterAdminCommand.Email src/AuthService/Auth.Application/Commands/RegisterAdminCommand.cs:6
- ResetPasswordCommand.Email src/AuthService/Auth.Application/Commands/ResetPasswordCommand.cs:6
- UpdateAppUserCommand.Email src/AuthService/Auth.Application/Commands/UpdateAppUserCommand.cs:7
- UpdateProfileCommand.Email src/AuthService/Auth.Application/Commands/UpdateAppUserCommand.cs:10
- AppUserDto.Email src/AuthService/Auth.Domain/Dtos/AppUserDto.cs:3
Phone — 3 field(s)
- UpdateAppUserCommand.PhoneNumber src/AuthService/Auth.Application/Commands/UpdateAppUserCommand.cs:7
- UpdateProfileCommand.PhoneNumber src/AuthService/Auth.Application/Commands/UpdateAppUserCommand.cs:10
- AppUserDto.PhoneNumber src/AuthService/Auth.Domain/Dtos/AppUserDto.cs:3