Executive summary
evgenirusev/Distributed-eStore is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because eight passwords or keys sit in the current code and we found no working pipeline that builds or tests changes to the code. It scores 37 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 26, is the weakest lens and counts most in the score. The best first step is replacing the eight exposed passwords or keys and switching the old ones off, worth about 9 points. Making the tests check their results comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 47.
Eighty-five known security holes in the packages the code depends on can be used by attackers. Seventeen settings leave the servers or containers unsafe, and eight passwords or keys in the code and four in the code's history are open to anyone who can read the repository. Updating the vulnerable packages, correcting the unsafe settings and replacing each exposed password or key would close these risks. The eight data fields that are written but never read need removing.
The product code is 6,757 lines, about €6,700 to rebuild.
If Production Readiness rose from 26 to 70, the lowest score rated Strong, the score would rise from 37 to about 47.
New since the last survey: 15 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net5.0 Distributed-eStore.Api.Gateway/src/Distributed-eStore.Api.Gateway.csproj
- Platform End-of-Life · End-of-life runtime: .NET net5.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net5.0 Distributed-eStore.Services.Order/src/Distributed-eStore.Services.Order.csproj
- Platform End-of-Life · End-of-life runtime: .NET net5.0 Distributed-eStore.Services.Product/src/Distributed-eStore.Services.Product.csproj
- Platform End-of-Life · End-of-life runtime: .NET net5.0 Distributed-eStore.UI/src/Distributed-eStore.UI.csproj
- Stateful singletons · Process-global static state: MongoDbInitializer Distributed-eStore.Common/Mongo/MongoDbInitializer.cs
Fixed since the last survey: 59 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Dependency Hygiene · Vulnerable: Microsoft.AspNetCore.Authentication.JwtBearer
- Dependency Hygiene · Vulnerable: MongoDB.Driver
- Dependency Hygiene · Vulnerable: System.IdentityModel.Tokens.Jwt
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net5.0 Distributed-eStore.UI/src/Distributed-eStore.UI.csproj
- Cancellation propagation · Async method without CancellationToken: UpdateAsync Distributed-eStore.Common/Mongo/MongoRepository.cs
- Cancellation propagation · Async method without CancellationToken: DeleteAsync Distributed-eStore.Common/Mongo/MongoRepository.cs
- Cancellation propagation · Async method without CancellationToken: ExistsAsync Distributed-eStore.Common/Mongo/MongoRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync Distributed-eStore.Common/Mongo/MongoRepository.cs
- Cancellation propagation · Async method without CancellationToken: PaginateAsync Distributed-eStore.Common/Mongo/Pagination.cs
- Cancellation propagation · Async method without CancellationToken: PaginateAsync Distributed-eStore.Common/Mongo/Pagination.cs
- Cancellation propagation · Async method without CancellationToken: QueryAsync Distributed-eStore.Common/Mvc/BaseController.cs
- Cancellation propagation · Async method without CancellationToken: HandleErrorAsync REDACTED
- Cancellation propagation · Async method without CancellationToken: SendAsync Distributed-eStore.Common/RabbitMq/BusPublisher.cs
- Cancellation propagation · Async method without CancellationToken: PublishAsync Distributed-eStore.Common/RabbitMq/BusPublisher.cs
- Cancellation propagation · Async method without CancellationToken: TryHandleAsync Distributed-eStore.Common/RabbitMq/BusSubscriber.cs
- Cancellation propagation · Async method without CancellationToken: TryHandleWithRequeuingAsync Distributed-eStore.Common/RabbitMq/BusSubscriber.cs
- Cancellation propagation · Async method without CancellationToken: InitializeAsync Distributed-eStore.Common/StartupInitializer.cs
- Cancellation propagation · Async method without CancellationToken: SendAsync Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs
- Cancellation propagation · Async method without CancellationToken: Post REDACTED
- Cancellation propagation · Async method without CancellationToken: Post REDACTED
- Cancellation propagation · Async method without CancellationToken: Post REDACTED
- Cancellation propagation · Async method without CancellationToken: Get Distributed-eStore.Api.Gateway/src/Controllers/ProductsController.cs
- Cancellation propagation · Async method without CancellationToken: GetProductById Distributed-eStore.Api.Gateway/src/Controllers/ProductsController.cs
- Cancellation propagation · Async method without CancellationToken: Post Distributed-eStore.Api.Gateway/src/Controllers/ProductsController.cs
- Cancellation propagation · Async method without CancellationToken: Get Distributed-eStore.Services.Product/src/Controllers/ProductsController.cs
- Cancellation propagation · Async method without CancellationToken: GetAsync Distributed-eStore.Services.Product/src/Controllers/ProductsController.cs
- Cancellation propagation · Async method without CancellationToken: HandleAsync Distributed-eStore.Services.Product/src/Handlers/BrowseProductsHandler.cs
- Cancellation propagation · Async method without CancellationToken: HandleAsync Distributed-eStore.Services.Product/src/Handlers/CreateProductHandler.cs
- Cancellation propagation · Async method without CancellationToken: HandleAsync Distributed-eStore.Services.Product/src/Handlers/GetProductHandler.cs
- Cancellation propagation · Async method without CancellationToken: GetAsync Distributed-eStore.Services.Product/src/Repositories/ProductsRepository.cs
- Cancellation propagation · Async method without CancellationToken: ExistsAsync Distributed-eStore.Services.Product/src/Repositories/ProductsRepository.cs
- Cancellation propagation · Async method without CancellationToken: ExistsAsync Distributed-eStore.Services.Product/src/Repositories/ProductsRepository.cs
- Cancellation propagation · Async method without CancellationToken: BrowseAsync Distributed-eStore.Services.Product/src/Repositories/ProductsRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddAsync Distributed-eStore.Services.Product/src/Repositories/ProductsRepository.cs
- Cancellation propagation · Async method without CancellationToken: UpdateAsync Distributed-eStore.Services.Product/src/Repositories/ProductsRepository.cs
- Cancellation propagation · Async method without CancellationToken: DeleteAsync Distributed-eStore.Services.Product/src/Repositories/ProductsRepository.cs
- Cancellation propagation · Async method without CancellationToken: SeedProductsAsync Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs
- Cancellation propagation · Async method without CancellationToken: Post Distributed-eStore.UI/src/Controllers/IdentityController.cs
- Cancellation propagation · Async method without CancellationToken: Post Distributed-eStore.UI/src/Controllers/IdentityController.cs
- Cancellation propagation · Async method without CancellationToken: Post Distributed-eStore.UI/src/Controllers/OrdersController.cs
- Cancellation propagation · Async method without CancellationToken: Get Distributed-eStore.UI/src/Controllers/ProductsController.cs
- Cancellation propagation · Async method without CancellationToken: Get Distributed-eStore.UI/src/Controllers/ProductsController.cs
- Cancellation propagation · Async method without CancellationToken: HandleAsync Distributed-eStore.Services.Order/src/Handlers/CreateOrderHandler.cs
- Cancellation propagation · Async method without CancellationToken: GetAsync Distributed-eStore.Services.Order/src/Repositories/OrdersRepository.cs
- Cancellation propagation · Async method without CancellationToken: AddAsync Distributed-eStore.Services.Order/src/Repositories/OrdersRepository.cs
- Cancellation propagation · Async method without CancellationToken: UpdateAsync Distributed-eStore.Services.Order/src/Repositories/OrdersRepository.cs
- Cancellation propagation · Async method without CancellationToken: DeleteAsync Distributed-eStore.Services.Order/src/Repositories/OrdersRepository.cs
- Cancellation propagation · Async method without CancellationToken: GetAllAsync Distributed-eStore.Services.Order/src/Repositories/OrdersRepository.cs
Rebuild cost: about €6,700 · Estimate
| Cost to rebuild | €2,300 to €11,000, for 38 to 118 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 37. 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,757 lines of product code |
| Comment lines | The estimate prices 6,714 lines. Comment lines count towards the size of 6,757 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes | 2 Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes | 3 Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes | 4 DistributedEStore.Common | 5 DistributedEStore.Common.Authentication | 6 DistributedEStore.Common.Commands.Identity | 7 DistributedEStore.Common.Messages | 8 DistributedEStore.Common.Models | 9 DistributedEStore.Common.Models.Products | 10 DistributedEStore.Common.Queries | 11 DistributedEStore.Common.Types | 12 Distributed-eStore_UI.src.ClientApp.src.state | 13 DistributedEStore.Api.Services | 14 DistributedEStore.Common.Dispatchers | 15 DistributedEStore.Common.Messages.Orders | 16 DistributedEStore.Common.Messages.Products | 17 DistributedEStore.Common.Mongo | 18 DistributedEStore.Common.RabbitMq | 19 DistributedEStore.Services.Identity.Domain | 20 DistributedEStore.Services.Identity.Messages.Commands | 21 DistributedEStore.Services.Orders.DomainEntities | 22 DistributedEStore.Services.Orders.Queries | 23 DistributedEStore.Services.Product.Queries | 24 DistributedEStore.Services.Products.DomainEntities | 25 DistributedEStore.Services.Products.Queries | 26 Distributed-eStore_UI.src.ClientApp.src.containers.Cart | 27 Distributed-eStore_UI.src.ClientApp.src.state.Products | 28 DistributedEStore.Api.Gateway | 29 DistributedEStore.Common.Handlers | 30 DistributedEStore.Common.Mvc | 31 DistributedEStore.Services.Identity.Repositories | 32 DistributedEStore.Services.Orders.Repositories | 33 DistributedEStore.Services.Products.Repositories | 34 DistributedEStore.UI.Controllers | 35 DistributedEStore.Api.Gateway.Controllers | 36 DistributedEStore.Services.Identity.Services | 37 DistributedEStore.Services.Orders.Handlers | 38 DistributedEStore.Services.Product.Controllers | 39 DistributedEStore.Services.Products.Handlers | 40 DistributedEStore.Services.Identity.Controllers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes | ||||||||||||||||||||||||||||||||||||||||
| 2 Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes | ||||||||||||||||||||||||||||||||||||||||
| 3 Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes | ||||||||||||||||||||||||||||||||||||||||
| 4 DistributedEStore.Common | ||||||||||||||||||||||||||||||||||||||||
| 5 DistributedEStore.Common.Authentication | ||||||||||||||||||||||||||||||||||||||||
| 6 DistributedEStore.Common.Commands.Identity | ||||||||||||||||||||||||||||||||||||||||
| 7 DistributedEStore.Common.Messages | ||||||||||||||||||||||||||||||||||||||||
| 8 DistributedEStore.Common.Models | ||||||||||||||||||||||||||||||||||||||||
| 9 DistributedEStore.Common.Models.Products | ||||||||||||||||||||||||||||||||||||||||
| 10 DistributedEStore.Common.Queries | ||||||||||||||||||||||||||||||||||||||||
| 11 DistributedEStore.Common.Types | ||||||||||||||||||||||||||||||||||||||||
| 12 Distributed-eStore_UI.src.ClientApp.src.state | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 DistributedEStore.Api.Services | 2 | 4 | 3 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 14 DistributedEStore.Common.Dispatchers | 4 | |||||||||||||||||||||||||||||||||||||||
| 15 DistributedEStore.Common.Messages.Orders | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 DistributedEStore.Common.Messages.Products | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 DistributedEStore.Common.Mongo | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 18 DistributedEStore.Common.RabbitMq | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 DistributedEStore.Services.Identity.Domain | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 DistributedEStore.Services.Identity.Messages.Commands | 4 | |||||||||||||||||||||||||||||||||||||||
| 21 DistributedEStore.Services.Orders.DomainEntities | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 DistributedEStore.Services.Orders.Queries | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 DistributedEStore.Services.Product.Queries | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 DistributedEStore.Services.Products.DomainEntities | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 DistributedEStore.Services.Products.Queries | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Distributed-eStore_UI.src.ClientApp.src.containers.Cart | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Distributed-eStore_UI.src.ClientApp.src.state.Products | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 DistributedEStore.Api.Gateway | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 DistributedEStore.Common.Handlers | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 DistributedEStore.Common.Mvc | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 DistributedEStore.Services.Identity.Repositories | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 32 DistributedEStore.Services.Orders.Repositories | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 DistributedEStore.Services.Products.Repositories | 2 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 DistributedEStore.UI.Controllers | 1 | 2 | 2 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||
| 35 DistributedEStore.Api.Gateway.Controllers | 1 | 2 | 1 | 1 | 1 | 1 | 3 | 1 | 1 | 4 | 4 | |||||||||||||||||||||||||||||
| 36 DistributedEStore.Services.Identity.Services | 6 | 2 | 2 | 2 | 4 | |||||||||||||||||||||||||||||||||||
| 37 DistributedEStore.Services.Orders.Handlers | 1 | 2 | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 38 DistributedEStore.Services.Product.Controllers | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 39 DistributedEStore.Services.Products.Handlers | 1 | 1 | 1 | 1 | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||
| 40 DistributedEStore.Services.Identity.Controllers | 2 | 2 | 1 | 4 | 2 |
12→1 Distributed-eStore_UI.src.ClientApp.src.state uses Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes✕
- Connections
- 1 pair of types, where a type in Distributed-eStore_UI.src.ClientApp.src.state uses a type in Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes.
- The types involved
Distributed-eStore_UI.src.ClientApp.src.state.IApplicationState→Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes.IProductsListState
- Direction
- Distributed-eStore_UI.src.ClientApp.src.state uses Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes, so a change to Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes can break Distributed-eStore_UI.src.ClientApp.src.state, while a change to Distributed-eStore_UI.src.ClientApp.src.state can't break Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes.
- Position
- Below the diagonal: Distributed-eStore_UI.src.ClientApp.src.state uses a module listed above it, which is the healthy direction.
12→2 Distributed-eStore_UI.src.ClientApp.src.state uses Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes✕
- Connections
- 1 pair of types, where a type in Distributed-eStore_UI.src.ClientApp.src.state uses a type in Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes.
- The types involved
Distributed-eStore_UI.src.ClientApp.src.state.IApplicationState→Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes.ICartState
- Direction
- Distributed-eStore_UI.src.ClientApp.src.state uses Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes, so a change to Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes can break Distributed-eStore_UI.src.ClientApp.src.state, while a change to Distributed-eStore_UI.src.ClientApp.src.state can't break Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes.
- Position
- Below the diagonal: Distributed-eStore_UI.src.ClientApp.src.state uses a module listed above it, which is the healthy direction.
12→3 Distributed-eStore_UI.src.ClientApp.src.state uses Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes✕
- Connections
- 1 pair of types, where a type in Distributed-eStore_UI.src.ClientApp.src.state uses a type in Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes.
- The types involved
Distributed-eStore_UI.src.ClientApp.src.state.IApplicationState→Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes.IUserState
- Direction
- Distributed-eStore_UI.src.ClientApp.src.state uses Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes, so a change to Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes can break Distributed-eStore_UI.src.ClientApp.src.state, while a change to Distributed-eStore_UI.src.ClientApp.src.state can't break Distributed-eStore_UI.src.ClientApp.src.state.user.userTypes.
- Position
- Below the diagonal: Distributed-eStore_UI.src.ClientApp.src.state uses a module listed above it, which is the healthy direction.
13→5 DistributedEStore.Api.Services uses DistributedEStore.Common.Authentication✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Api.Services uses a type in DistributedEStore.Common.Authentication.
- The types involved
DistributedEStore.Api.Services.IApiGatewayService→DistributedEStore.Common.Authentication.JsonWebTokenDistributedEStore.Api.Services.IIdentityService→DistributedEStore.Common.Authentication.JsonWebToken
- Direction
- DistributedEStore.Api.Services uses DistributedEStore.Common.Authentication, so a change to DistributedEStore.Common.Authentication can break DistributedEStore.Api.Services, while a change to DistributedEStore.Api.Services can't break DistributedEStore.Common.Authentication.
- Position
- Below the diagonal: DistributedEStore.Api.Services uses a module listed above it, which is the healthy direction.
13→6 DistributedEStore.Api.Services uses DistributedEStore.Common.Commands.Identity✕
- Connections
- 4 pairs of types, where a type in DistributedEStore.Api.Services uses a type in DistributedEStore.Common.Commands.Identity.
- The types involved
DistributedEStore.Api.Services.IApiGatewayService→DistributedEStore.Common.Commands.Identity.SignInCommandDistributedEStore.Api.Services.IApiGatewayService→DistributedEStore.Common.Commands.Identity.SignUpCommandDistributedEStore.Api.Services.IIdentityService→DistributedEStore.Common.Commands.Identity.SignInCommandDistributedEStore.Api.Services.IIdentityService→DistributedEStore.Common.Commands.Identity.SignUpCommand
- Direction
- DistributedEStore.Api.Services uses DistributedEStore.Common.Commands.Identity, so a change to DistributedEStore.Common.Commands.Identity can break DistributedEStore.Api.Services, while a change to DistributedEStore.Api.Services can't break DistributedEStore.Common.Commands.Identity.
- Position
- Below the diagonal: DistributedEStore.Api.Services uses a module listed above it, which is the healthy direction.
13→8 DistributedEStore.Api.Services uses DistributedEStore.Common.Models✕
- Connections
- 3 pairs of types, where a type in DistributedEStore.Api.Services uses a type in DistributedEStore.Common.Models.
- The types involved
DistributedEStore.Api.Services.IApiGatewayService→DistributedEStore.Common.Models.CreateOrderDistributedEStore.Api.Services.IApiGatewayService→DistributedEStore.Common.Models.RegisterUserResponseDistributedEStore.Api.Services.IIdentityService→DistributedEStore.Common.Models.RegisterUserResponse
- Direction
- DistributedEStore.Api.Services uses DistributedEStore.Common.Models, so a change to DistributedEStore.Common.Models can break DistributedEStore.Api.Services, while a change to DistributedEStore.Api.Services can't break DistributedEStore.Common.Models.
- Position
- Below the diagonal: DistributedEStore.Api.Services uses a module listed above it, which is the healthy direction.
13→9 DistributedEStore.Api.Services uses DistributedEStore.Common.Models.Products✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Api.Services uses a type in DistributedEStore.Common.Models.Products.
- The types involved
DistributedEStore.Api.Services.IApiGatewayService→DistributedEStore.Common.Models.Products.ProductDistributedEStore.Api.Services.IProductsService→DistributedEStore.Common.Models.Products.Product
- Direction
- DistributedEStore.Api.Services uses DistributedEStore.Common.Models.Products, so a change to DistributedEStore.Common.Models.Products can break DistributedEStore.Api.Services, while a change to DistributedEStore.Api.Services can't break DistributedEStore.Common.Models.Products.
- Position
- Below the diagonal: DistributedEStore.Api.Services uses a module listed above it, which is the healthy direction.
13→10 DistributedEStore.Api.Services uses DistributedEStore.Common.Queries✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Api.Services uses a type in DistributedEStore.Common.Queries.
- The types involved
DistributedEStore.Api.Services.IApiGatewayService→DistributedEStore.Common.Queries.BrowseProductsDistributedEStore.Api.Services.IProductsService→DistributedEStore.Common.Queries.BrowseProducts
- Direction
- DistributedEStore.Api.Services uses DistributedEStore.Common.Queries, so a change to DistributedEStore.Common.Queries can break DistributedEStore.Api.Services, while a change to DistributedEStore.Api.Services can't break DistributedEStore.Common.Queries.
- Position
- Below the diagonal: DistributedEStore.Api.Services uses a module listed above it, which is the healthy direction.
13→11 DistributedEStore.Api.Services uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Api.Services uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Api.Services.IApiGatewayService→DistributedEStore.Common.Types.PagedResultDistributedEStore.Api.Services.IProductsService→DistributedEStore.Common.Types.PagedResult
- Direction
- DistributedEStore.Api.Services uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Api.Services, while a change to DistributedEStore.Api.Services can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Api.Services uses a module listed above it, which is the healthy direction.
14→11 DistributedEStore.Common.Dispatchers uses DistributedEStore.Common.Types✕
- Connections
- 4 pairs of types, where a type in DistributedEStore.Common.Dispatchers uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Common.Dispatchers.Dispatcher→DistributedEStore.Common.Types.IQueryDistributedEStore.Common.Dispatchers.IDispatcher→DistributedEStore.Common.Types.IQueryDistributedEStore.Common.Dispatchers.IQueryDispatcher→DistributedEStore.Common.Types.IQueryDistributedEStore.Common.Dispatchers.QueryDispatcher→DistributedEStore.Common.Types.IQuery
- Direction
- DistributedEStore.Common.Dispatchers uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Common.Dispatchers, while a change to DistributedEStore.Common.Dispatchers can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Common.Dispatchers uses a module listed above it, which is the healthy direction.
15→7 DistributedEStore.Common.Messages.Orders uses DistributedEStore.Common.Messages✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Common.Messages.Orders uses a type in DistributedEStore.Common.Messages.
- The types involved
DistributedEStore.Common.Messages.Orders.CreateOrder→DistributedEStore.Common.Messages.ICommand
- Direction
- DistributedEStore.Common.Messages.Orders uses DistributedEStore.Common.Messages, so a change to DistributedEStore.Common.Messages can break DistributedEStore.Common.Messages.Orders, while a change to DistributedEStore.Common.Messages.Orders can't break DistributedEStore.Common.Messages.
- Position
- Below the diagonal: DistributedEStore.Common.Messages.Orders uses a module listed above it, which is the healthy direction.
16→7 DistributedEStore.Common.Messages.Products uses DistributedEStore.Common.Messages✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Common.Messages.Products uses a type in DistributedEStore.Common.Messages.
- The types involved
DistributedEStore.Common.Messages.Products.CreateProduct→DistributedEStore.Common.Messages.ICommand
- Direction
- DistributedEStore.Common.Messages.Products uses DistributedEStore.Common.Messages, so a change to DistributedEStore.Common.Messages can break DistributedEStore.Common.Messages.Products, while a change to DistributedEStore.Common.Messages.Products can't break DistributedEStore.Common.Messages.
- Position
- Below the diagonal: DistributedEStore.Common.Messages.Products uses a module listed above it, which is the healthy direction.
17→4 DistributedEStore.Common.Mongo uses DistributedEStore.Common✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Common.Mongo uses a type in DistributedEStore.Common.
- The types involved
DistributedEStore.Common.Mongo.IMongoDbInitializer→DistributedEStore.Common.IInitializer
- Direction
- DistributedEStore.Common.Mongo uses DistributedEStore.Common, so a change to DistributedEStore.Common can break DistributedEStore.Common.Mongo, while a change to DistributedEStore.Common.Mongo can't break DistributedEStore.Common.
- Position
- Below the diagonal: DistributedEStore.Common.Mongo uses a module listed above it, which is the healthy direction.
17→11 DistributedEStore.Common.Mongo uses DistributedEStore.Common.Types✕
- Connections
- 4 pairs of types, where a type in DistributedEStore.Common.Mongo uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Common.Mongo.IMongoRepository→DistributedEStore.Common.Types.PagedResultDistributedEStore.Common.Mongo.MongoRepository→DistributedEStore.Common.Types.PagedResultDistributedEStore.Common.Mongo.Pagination→DistributedEStore.Common.Types.PagedQueryBaseDistributedEStore.Common.Mongo.Pagination→DistributedEStore.Common.Types.PagedResult
- Direction
- DistributedEStore.Common.Mongo uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Common.Mongo, while a change to DistributedEStore.Common.Mongo can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Common.Mongo uses a module listed above it, which is the healthy direction.
18→7 DistributedEStore.Common.RabbitMq uses DistributedEStore.Common.Messages✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Common.RabbitMq uses a type in DistributedEStore.Common.Messages.
- The types involved
DistributedEStore.Common.RabbitMq.BusSubscriber→DistributedEStore.Common.Messages.IRejectedEventDistributedEStore.Common.RabbitMq.IBusSubscriber→DistributedEStore.Common.Messages.IRejectedEvent
- Direction
- DistributedEStore.Common.RabbitMq uses DistributedEStore.Common.Messages, so a change to DistributedEStore.Common.Messages can break DistributedEStore.Common.RabbitMq, while a change to DistributedEStore.Common.RabbitMq can't break DistributedEStore.Common.Messages.
- Position
- Below the diagonal: DistributedEStore.Common.RabbitMq uses a module listed above it, which is the healthy direction.
18→11 DistributedEStore.Common.RabbitMq uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Common.RabbitMq uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Common.RabbitMq.BusSubscriber→DistributedEStore.Common.Types.DistributedEStoreExceptionDistributedEStore.Common.RabbitMq.IBusSubscriber→DistributedEStore.Common.Types.DistributedEStoreException
- Direction
- DistributedEStore.Common.RabbitMq uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Common.RabbitMq, while a change to DistributedEStore.Common.RabbitMq can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Common.RabbitMq uses a module listed above it, which is the healthy direction.
19→11 DistributedEStore.Services.Identity.Domain uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Identity.Domain uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Services.Identity.Domain.RefreshToken→DistributedEStore.Common.Types.IIdentifiableDistributedEStore.Services.Identity.Domain.User→DistributedEStore.Common.Types.IIdentifiable
- Direction
- DistributedEStore.Services.Identity.Domain uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Services.Identity.Domain, while a change to DistributedEStore.Services.Identity.Domain can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Domain uses a module listed above it, which is the healthy direction.
20→7 DistributedEStore.Services.Identity.Messages.Commands uses DistributedEStore.Common.Messages✕
- Connections
- 4 pairs of types, where a type in DistributedEStore.Services.Identity.Messages.Commands uses a type in DistributedEStore.Common.Messages.
- The types involved
DistributedEStore.Services.Identity.Messages.Commands.ChangePassword→DistributedEStore.Common.Messages.ICommandDistributedEStore.Services.Identity.Messages.Commands.RefreshAccessToken→DistributedEStore.Common.Messages.ICommandDistributedEStore.Services.Identity.Messages.Commands.RevokeAccessToken→DistributedEStore.Common.Messages.ICommandDistributedEStore.Services.Identity.Messages.Commands.RevokeRefreshToken→DistributedEStore.Common.Messages.ICommand
- Direction
- DistributedEStore.Services.Identity.Messages.Commands uses DistributedEStore.Common.Messages, so a change to DistributedEStore.Common.Messages can break DistributedEStore.Services.Identity.Messages.Commands, while a change to DistributedEStore.Services.Identity.Messages.Commands can't break DistributedEStore.Common.Messages.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Messages.Commands uses a module listed above it, which is the healthy direction.
21→11 DistributedEStore.Services.Orders.DomainEntities uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Orders.DomainEntities uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Services.Orders.DomainEntities.Order→DistributedEStore.Common.Types.BaseEntityDistributedEStore.Services.Orders.DomainEntities.OrderItem→DistributedEStore.Common.Types.BaseEntity
- Direction
- DistributedEStore.Services.Orders.DomainEntities uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Services.Orders.DomainEntities, while a change to DistributedEStore.Services.Orders.DomainEntities can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.DomainEntities uses a module listed above it, which is the healthy direction.
22→11 DistributedEStore.Services.Orders.Queries uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Orders.Queries uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Services.Orders.Queries.BrowseOrders→DistributedEStore.Common.Types.IQueryDistributedEStore.Services.Orders.Queries.BrowseOrders→DistributedEStore.Common.Types.PagedQueryBase
- Direction
- DistributedEStore.Services.Orders.Queries uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Services.Orders.Queries, while a change to DistributedEStore.Services.Orders.Queries can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.Queries uses a module listed above it, which is the healthy direction.
23→11 DistributedEStore.Services.Product.Queries uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Product.Queries uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Services.Product.Queries.BrowseProducts→DistributedEStore.Common.Types.IQueryDistributedEStore.Services.Product.Queries.BrowseProducts→DistributedEStore.Common.Types.PagedQueryBase
- Direction
- DistributedEStore.Services.Product.Queries uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Services.Product.Queries, while a change to DistributedEStore.Services.Product.Queries can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Services.Product.Queries uses a module listed above it, which is the healthy direction.
24→11 DistributedEStore.Services.Products.DomainEntities uses DistributedEStore.Common.Types✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Products.DomainEntities uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Services.Products.DomainEntities.Product→DistributedEStore.Common.Types.BaseEntity
- Direction
- DistributedEStore.Services.Products.DomainEntities uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Services.Products.DomainEntities, while a change to DistributedEStore.Services.Products.DomainEntities can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Services.Products.DomainEntities uses a module listed above it, which is the healthy direction.
25→11 DistributedEStore.Services.Products.Queries uses DistributedEStore.Common.Types✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Products.Queries uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Services.Products.Queries.GetProduct→DistributedEStore.Common.Types.IQuery
- Direction
- DistributedEStore.Services.Products.Queries uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Services.Products.Queries, while a change to DistributedEStore.Services.Products.Queries can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Queries uses a module listed above it, which is the healthy direction.
26→2 Distributed-eStore_UI.src.ClientApp.src.containers.Cart uses Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes✕
- Connections
- 2 pairs of types, where a type in Distributed-eStore_UI.src.ClientApp.src.containers.Cart uses a type in Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes.
- The types involved
Distributed-eStore_UI.src.ClientApp.src.containers.Cart.Cart→Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes.ICartStateDistributed-eStore_UI.src.ClientApp.src.containers.Cart.Cart→Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes.IOrder
- Direction
- Distributed-eStore_UI.src.ClientApp.src.containers.Cart uses Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes, so a change to Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes can break Distributed-eStore_UI.src.ClientApp.src.containers.Cart, while a change to Distributed-eStore_UI.src.ClientApp.src.containers.Cart can't break Distributed-eStore_UI.src.ClientApp.src.state.cart.cartTypes.
- Position
- Below the diagonal: Distributed-eStore_UI.src.ClientApp.src.containers.Cart uses a module listed above it, which is the healthy direction.
26→12 Distributed-eStore_UI.src.ClientApp.src.containers.Cart uses Distributed-eStore_UI.src.ClientApp.src.state✕
- Connections
- 1 pair of types, where a type in Distributed-eStore_UI.src.ClientApp.src.containers.Cart uses a type in Distributed-eStore_UI.src.ClientApp.src.state.
- The types involved
Distributed-eStore_UI.src.ClientApp.src.containers.Cart.Cart→Distributed-eStore_UI.src.ClientApp.src.state.IApplicationState
- Direction
- Distributed-eStore_UI.src.ClientApp.src.containers.Cart uses Distributed-eStore_UI.src.ClientApp.src.state, so a change to Distributed-eStore_UI.src.ClientApp.src.state can break Distributed-eStore_UI.src.ClientApp.src.containers.Cart, while a change to Distributed-eStore_UI.src.ClientApp.src.containers.Cart can't break Distributed-eStore_UI.src.ClientApp.src.state.
- Position
- Below the diagonal: Distributed-eStore_UI.src.ClientApp.src.containers.Cart uses a module listed above it, which is the healthy direction.
27→1 Distributed-eStore_UI.src.ClientApp.src.state.Products uses Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes✕
- Connections
- 2 pairs of types, where a type in Distributed-eStore_UI.src.ClientApp.src.state.Products uses a type in Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes.
- The types involved
Distributed-eStore_UI.src.ClientApp.src.state.Products.productsActions→Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes.ProductsActionTypesDistributed-eStore_UI.src.ClientApp.src.state.Products.productsReducers→Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes.IProductsListState
- Direction
- Distributed-eStore_UI.src.ClientApp.src.state.Products uses Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes, so a change to Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes can break Distributed-eStore_UI.src.ClientApp.src.state.Products, while a change to Distributed-eStore_UI.src.ClientApp.src.state.Products can't break Distributed-eStore_UI.src.ClientApp.src.state.Products.productsTypes.
- Position
- Below the diagonal: Distributed-eStore_UI.src.ClientApp.src.state.Products uses a module listed above it, which is the healthy direction.
27→12 Distributed-eStore_UI.src.ClientApp.src.state.Products uses Distributed-eStore_UI.src.ClientApp.src.state✕
- Connections
- 1 pair of types, where a type in Distributed-eStore_UI.src.ClientApp.src.state.Products uses a type in Distributed-eStore_UI.src.ClientApp.src.state.
- The types involved
Distributed-eStore_UI.src.ClientApp.src.state.Products.productsActions→Distributed-eStore_UI.src.ClientApp.src.state.IApplicationState
- Direction
- Distributed-eStore_UI.src.ClientApp.src.state.Products uses Distributed-eStore_UI.src.ClientApp.src.state, so a change to Distributed-eStore_UI.src.ClientApp.src.state can break Distributed-eStore_UI.src.ClientApp.src.state.Products, while a change to Distributed-eStore_UI.src.ClientApp.src.state.Products can't break Distributed-eStore_UI.src.ClientApp.src.state.
- Position
- Below the diagonal: Distributed-eStore_UI.src.ClientApp.src.state.Products uses a module listed above it, which is the healthy direction.
28→4 DistributedEStore.Api.Gateway uses DistributedEStore.Common✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Api.Gateway uses a type in DistributedEStore.Common.
- The types involved
DistributedEStore.Api.Gateway.Startup→DistributedEStore.Common.IStartupInitializer
- Direction
- DistributedEStore.Api.Gateway uses DistributedEStore.Common, so a change to DistributedEStore.Common can break DistributedEStore.Api.Gateway, while a change to DistributedEStore.Api.Gateway can't break DistributedEStore.Common.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway uses a module listed above it, which is the healthy direction.
28→11 DistributedEStore.Api.Gateway uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Api.Gateway uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Api.Gateway.BaseController→DistributedEStore.Common.Types.PagedResultDistributedEStore.Api.Gateway.BaseController→DistributedEStore.Common.Types.PagedResultBase
- Direction
- DistributedEStore.Api.Gateway uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Api.Gateway, while a change to DistributedEStore.Api.Gateway can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway uses a module listed above it, which is the healthy direction.
28→18 DistributedEStore.Api.Gateway uses DistributedEStore.Common.RabbitMq✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Api.Gateway uses a type in DistributedEStore.Common.RabbitMq.
- The types involved
DistributedEStore.Api.Gateway.BaseController→DistributedEStore.Common.RabbitMq.IBusPublisherDistributedEStore.Api.Gateway.BaseController→DistributedEStore.Common.RabbitMq.ICorrelationContext
- Direction
- DistributedEStore.Api.Gateway uses DistributedEStore.Common.RabbitMq, so a change to DistributedEStore.Common.RabbitMq can break DistributedEStore.Api.Gateway, while a change to DistributedEStore.Api.Gateway can't break DistributedEStore.Common.RabbitMq.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway uses a module listed above it, which is the healthy direction.
29→11 DistributedEStore.Common.Handlers uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Common.Handlers uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Common.Handlers.Handler→DistributedEStore.Common.Types.DistributedEStoreExceptionDistributedEStore.Common.Handlers.IHandler→DistributedEStore.Common.Types.DistributedEStoreException
- Direction
- DistributedEStore.Common.Handlers uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Common.Handlers, while a change to DistributedEStore.Common.Handlers can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Common.Handlers uses a module listed above it, which is the healthy direction.
29→18 DistributedEStore.Common.Handlers uses DistributedEStore.Common.RabbitMq✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Common.Handlers uses a type in DistributedEStore.Common.RabbitMq.
- The types involved
DistributedEStore.Common.Handlers.ICommandHandler→DistributedEStore.Common.RabbitMq.ICorrelationContextDistributedEStore.Common.Handlers.IEventHandler→DistributedEStore.Common.RabbitMq.ICorrelationContext
- Direction
- DistributedEStore.Common.Handlers uses DistributedEStore.Common.RabbitMq, so a change to DistributedEStore.Common.RabbitMq can break DistributedEStore.Common.Handlers, while a change to DistributedEStore.Common.Handlers can't break DistributedEStore.Common.RabbitMq.
- Position
- Below the diagonal: DistributedEStore.Common.Handlers uses a module listed above it, which is the healthy direction.
30→11 DistributedEStore.Common.Mvc uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Common.Mvc uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Common.Mvc.BaseController→DistributedEStore.Common.Types.IQueryDistributedEStore.Common.Mvc.BaseController→DistributedEStore.Common.Types.PagedResult
- Direction
- DistributedEStore.Common.Mvc uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Common.Mvc, while a change to DistributedEStore.Common.Mvc can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Common.Mvc uses a module listed above it, which is the healthy direction.
30→14 DistributedEStore.Common.Mvc uses DistributedEStore.Common.Dispatchers✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Common.Mvc uses a type in DistributedEStore.Common.Dispatchers.
- The types involved
DistributedEStore.Common.Mvc.BaseController→DistributedEStore.Common.Dispatchers.IDispatcher
- Direction
- DistributedEStore.Common.Mvc uses DistributedEStore.Common.Dispatchers, so a change to DistributedEStore.Common.Dispatchers can break DistributedEStore.Common.Mvc, while a change to DistributedEStore.Common.Mvc can't break DistributedEStore.Common.Dispatchers.
- Position
- Below the diagonal: DistributedEStore.Common.Mvc uses a module listed above it, which is the healthy direction.
31→17 DistributedEStore.Services.Identity.Repositories uses DistributedEStore.Common.Mongo✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Identity.Repositories uses a type in DistributedEStore.Common.Mongo.
- The types involved
DistributedEStore.Services.Identity.Repositories.RefreshTokenRepository→DistributedEStore.Common.Mongo.IMongoRepositoryDistributedEStore.Services.Identity.Repositories.UserRepository→DistributedEStore.Common.Mongo.IMongoRepository
- Direction
- DistributedEStore.Services.Identity.Repositories uses DistributedEStore.Common.Mongo, so a change to DistributedEStore.Common.Mongo can break DistributedEStore.Services.Identity.Repositories, while a change to DistributedEStore.Services.Identity.Repositories can't break DistributedEStore.Common.Mongo.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Repositories uses a module listed above it, which is the healthy direction.
31→19 DistributedEStore.Services.Identity.Repositories uses DistributedEStore.Services.Identity.Domain✕
- Connections
- 4 pairs of types, where a type in DistributedEStore.Services.Identity.Repositories uses a type in DistributedEStore.Services.Identity.Domain.
- The types involved
DistributedEStore.Services.Identity.Repositories.IRefreshTokenRepository→DistributedEStore.Services.Identity.Domain.RefreshTokenDistributedEStore.Services.Identity.Repositories.IUserRepository→DistributedEStore.Services.Identity.Domain.UserDistributedEStore.Services.Identity.Repositories.RefreshTokenRepository→DistributedEStore.Services.Identity.Domain.RefreshTokenDistributedEStore.Services.Identity.Repositories.UserRepository→DistributedEStore.Services.Identity.Domain.User
- Direction
- DistributedEStore.Services.Identity.Repositories uses DistributedEStore.Services.Identity.Domain, so a change to DistributedEStore.Services.Identity.Domain can break DistributedEStore.Services.Identity.Repositories, while a change to DistributedEStore.Services.Identity.Repositories can't break DistributedEStore.Services.Identity.Domain.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Repositories uses a module listed above it, which is the healthy direction.
32→17 DistributedEStore.Services.Orders.Repositories uses DistributedEStore.Common.Mongo✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Orders.Repositories uses a type in DistributedEStore.Common.Mongo.
- The types involved
DistributedEStore.Services.Orders.Repositories.OrdersRepository→DistributedEStore.Common.Mongo.IMongoRepository
- Direction
- DistributedEStore.Services.Orders.Repositories uses DistributedEStore.Common.Mongo, so a change to DistributedEStore.Common.Mongo can break DistributedEStore.Services.Orders.Repositories, while a change to DistributedEStore.Services.Orders.Repositories can't break DistributedEStore.Common.Mongo.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.Repositories uses a module listed above it, which is the healthy direction.
32→21 DistributedEStore.Services.Orders.Repositories uses DistributedEStore.Services.Orders.DomainEntities✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Orders.Repositories uses a type in DistributedEStore.Services.Orders.DomainEntities.
- The types involved
DistributedEStore.Services.Orders.Repositories.IOrdersRepository→DistributedEStore.Services.Orders.DomainEntities.OrderDistributedEStore.Services.Orders.Repositories.OrdersRepository→DistributedEStore.Services.Orders.DomainEntities.Order
- Direction
- DistributedEStore.Services.Orders.Repositories uses DistributedEStore.Services.Orders.DomainEntities, so a change to DistributedEStore.Services.Orders.DomainEntities can break DistributedEStore.Services.Orders.Repositories, while a change to DistributedEStore.Services.Orders.Repositories can't break DistributedEStore.Services.Orders.DomainEntities.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.Repositories uses a module listed above it, which is the healthy direction.
33→11 DistributedEStore.Services.Products.Repositories uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Products.Repositories uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Services.Products.Repositories.IProductsRepository→DistributedEStore.Common.Types.PagedResultDistributedEStore.Services.Products.Repositories.ProductsRepository→DistributedEStore.Common.Types.PagedResult
- Direction
- DistributedEStore.Services.Products.Repositories uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Services.Products.Repositories, while a change to DistributedEStore.Services.Products.Repositories can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Repositories uses a module listed above it, which is the healthy direction.
33→17 DistributedEStore.Services.Products.Repositories uses DistributedEStore.Common.Mongo✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Products.Repositories uses a type in DistributedEStore.Common.Mongo.
- The types involved
DistributedEStore.Services.Products.Repositories.ProductsRepository→DistributedEStore.Common.Mongo.IMongoRepository
- Direction
- DistributedEStore.Services.Products.Repositories uses DistributedEStore.Common.Mongo, so a change to DistributedEStore.Common.Mongo can break DistributedEStore.Services.Products.Repositories, while a change to DistributedEStore.Services.Products.Repositories can't break DistributedEStore.Common.Mongo.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Repositories uses a module listed above it, which is the healthy direction.
33→23 DistributedEStore.Services.Products.Repositories uses DistributedEStore.Services.Product.Queries✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Products.Repositories uses a type in DistributedEStore.Services.Product.Queries.
- The types involved
DistributedEStore.Services.Products.Repositories.IProductsRepository→DistributedEStore.Services.Product.Queries.BrowseProductsDistributedEStore.Services.Products.Repositories.ProductsRepository→DistributedEStore.Services.Product.Queries.BrowseProducts
- Direction
- DistributedEStore.Services.Products.Repositories uses DistributedEStore.Services.Product.Queries, so a change to DistributedEStore.Services.Product.Queries can break DistributedEStore.Services.Products.Repositories, while a change to DistributedEStore.Services.Products.Repositories can't break DistributedEStore.Services.Product.Queries.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Repositories uses a module listed above it, which is the healthy direction.
33→24 DistributedEStore.Services.Products.Repositories uses DistributedEStore.Services.Products.DomainEntities✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Products.Repositories uses a type in DistributedEStore.Services.Products.DomainEntities.
- The types involved
DistributedEStore.Services.Products.Repositories.IProductsRepository→DistributedEStore.Services.Products.DomainEntities.ProductDistributedEStore.Services.Products.Repositories.ProductsRepository→DistributedEStore.Services.Products.DomainEntities.Product
- Direction
- DistributedEStore.Services.Products.Repositories uses DistributedEStore.Services.Products.DomainEntities, so a change to DistributedEStore.Services.Products.DomainEntities can break DistributedEStore.Services.Products.Repositories, while a change to DistributedEStore.Services.Products.Repositories can't break DistributedEStore.Services.Products.DomainEntities.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Repositories uses a module listed above it, which is the healthy direction.
34→5 DistributedEStore.UI.Controllers uses DistributedEStore.Common.Authentication✕
- Connections
- 1 pair of types, where a type in DistributedEStore.UI.Controllers uses a type in DistributedEStore.Common.Authentication.
- The types involved
DistributedEStore.UI.Controllers.IdentityController→DistributedEStore.Common.Authentication.JsonWebToken
- Direction
- DistributedEStore.UI.Controllers uses DistributedEStore.Common.Authentication, so a change to DistributedEStore.Common.Authentication can break DistributedEStore.UI.Controllers, while a change to DistributedEStore.UI.Controllers can't break DistributedEStore.Common.Authentication.
- Position
- Below the diagonal: DistributedEStore.UI.Controllers uses a module listed above it, which is the healthy direction.
34→6 DistributedEStore.UI.Controllers uses DistributedEStore.Common.Commands.Identity✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.UI.Controllers uses a type in DistributedEStore.Common.Commands.Identity.
- The types involved
DistributedEStore.UI.Controllers.IdentityController→DistributedEStore.Common.Commands.Identity.SignInCommandDistributedEStore.UI.Controllers.IdentityController→DistributedEStore.Common.Commands.Identity.SignUpCommand
- Direction
- DistributedEStore.UI.Controllers uses DistributedEStore.Common.Commands.Identity, so a change to DistributedEStore.Common.Commands.Identity can break DistributedEStore.UI.Controllers, while a change to DistributedEStore.UI.Controllers can't break DistributedEStore.Common.Commands.Identity.
- Position
- Below the diagonal: DistributedEStore.UI.Controllers uses a module listed above it, which is the healthy direction.
34→8 DistributedEStore.UI.Controllers uses DistributedEStore.Common.Models✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.UI.Controllers uses a type in DistributedEStore.Common.Models.
- The types involved
DistributedEStore.UI.Controllers.OrdersController→DistributedEStore.Common.Models.CreateOrderDistributedEStore.UI.Controllers.OrdersController→DistributedEStore.Common.Models.CreateOrderRequest
- Direction
- DistributedEStore.UI.Controllers uses DistributedEStore.Common.Models, so a change to DistributedEStore.Common.Models can break DistributedEStore.UI.Controllers, while a change to DistributedEStore.UI.Controllers can't break DistributedEStore.Common.Models.
- Position
- Below the diagonal: DistributedEStore.UI.Controllers uses a module listed above it, which is the healthy direction.
34→10 DistributedEStore.UI.Controllers uses DistributedEStore.Common.Queries✕
- Connections
- 1 pair of types, where a type in DistributedEStore.UI.Controllers uses a type in DistributedEStore.Common.Queries.
- The types involved
DistributedEStore.UI.Controllers.ProductsController→DistributedEStore.Common.Queries.BrowseProducts
- Direction
- DistributedEStore.UI.Controllers uses DistributedEStore.Common.Queries, so a change to DistributedEStore.Common.Queries can break DistributedEStore.UI.Controllers, while a change to DistributedEStore.UI.Controllers can't break DistributedEStore.Common.Queries.
- Position
- Below the diagonal: DistributedEStore.UI.Controllers uses a module listed above it, which is the healthy direction.
34→11 DistributedEStore.UI.Controllers uses DistributedEStore.Common.Types✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.UI.Controllers uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.UI.Controllers.BaseController→DistributedEStore.Common.Types.PagedResultDistributedEStore.UI.Controllers.BaseController→DistributedEStore.Common.Types.PagedResultBase
- Direction
- DistributedEStore.UI.Controllers uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.UI.Controllers, while a change to DistributedEStore.UI.Controllers can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.UI.Controllers uses a module listed above it, which is the healthy direction.
34→13 DistributedEStore.UI.Controllers uses DistributedEStore.Api.Services✕
- Connections
- 3 pairs of types, where a type in DistributedEStore.UI.Controllers uses a type in DistributedEStore.Api.Services.
- The types involved
DistributedEStore.UI.Controllers.IdentityController→DistributedEStore.Api.Services.IApiGatewayServiceDistributedEStore.UI.Controllers.OrdersController→DistributedEStore.Api.Services.IApiGatewayServiceDistributedEStore.UI.Controllers.ProductsController→DistributedEStore.Api.Services.IApiGatewayService
- Direction
- DistributedEStore.UI.Controllers uses DistributedEStore.Api.Services, so a change to DistributedEStore.Api.Services can break DistributedEStore.UI.Controllers, while a change to DistributedEStore.UI.Controllers can't break DistributedEStore.Api.Services.
- Position
- Below the diagonal: DistributedEStore.UI.Controllers uses a module listed above it, which is the healthy direction.
35→5 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Authentication✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Common.Authentication.
- The types involved
DistributedEStore.Api.Gateway.Controllers.IdentityController→DistributedEStore.Common.Authentication.JsonWebToken
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Authentication, so a change to DistributedEStore.Common.Authentication can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Common.Authentication.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
35→6 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Commands.Identity✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Common.Commands.Identity.
- The types involved
DistributedEStore.Api.Gateway.Controllers.IdentityController→DistributedEStore.Common.Commands.Identity.SignInCommandDistributedEStore.Api.Gateway.Controllers.IdentityController→DistributedEStore.Common.Commands.Identity.SignUpCommand
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Commands.Identity, so a change to DistributedEStore.Common.Commands.Identity can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Common.Commands.Identity.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
35→8 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Models✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Common.Models.
- The types involved
DistributedEStore.Api.Gateway.Controllers.IdentityController→DistributedEStore.Common.Models.RegisterUserResponse
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Models, so a change to DistributedEStore.Common.Models can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Common.Models.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
35→9 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Models.Products✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Common.Models.Products.
- The types involved
DistributedEStore.Api.Gateway.Controllers.ProductsController→DistributedEStore.Common.Models.Products.Product
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Models.Products, so a change to DistributedEStore.Common.Models.Products can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Common.Models.Products.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
35→10 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Queries✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Common.Queries.
- The types involved
DistributedEStore.Api.Gateway.Controllers.ProductsController→DistributedEStore.Common.Queries.BrowseProducts
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Queries, so a change to DistributedEStore.Common.Queries can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Common.Queries.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
35→11 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Types✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Api.Gateway.Controllers.ProductsController→DistributedEStore.Common.Types.PagedResult
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
35→13 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Api.Services✕
- Connections
- 3 pairs of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Api.Services.
- The types involved
DistributedEStore.Api.Gateway.Controllers.IdentityController→DistributedEStore.Api.Services.IIdentityServiceDistributedEStore.Api.Gateway.Controllers.OrdersController→DistributedEStore.Api.Services.IOrdersServiceDistributedEStore.Api.Gateway.Controllers.ProductsController→DistributedEStore.Api.Services.IProductsService
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Api.Services, so a change to DistributedEStore.Api.Services can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Api.Services.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
35→15 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Messages.Orders✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Common.Messages.Orders.
- The types involved
DistributedEStore.Api.Gateway.Controllers.OrdersController→DistributedEStore.Common.Messages.Orders.CreateOrder
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Messages.Orders, so a change to DistributedEStore.Common.Messages.Orders can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Common.Messages.Orders.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
35→16 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Messages.Products✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Common.Messages.Products.
- The types involved
DistributedEStore.Api.Gateway.Controllers.ProductsController→DistributedEStore.Common.Messages.Products.CreateProduct
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.Messages.Products, so a change to DistributedEStore.Common.Messages.Products can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Common.Messages.Products.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
35→18 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.RabbitMq✕
- Connections
- 4 pairs of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Common.RabbitMq.
- The types involved
DistributedEStore.Api.Gateway.Controllers.HomeController→DistributedEStore.Common.RabbitMq.IBusPublisherDistributedEStore.Api.Gateway.Controllers.IdentityController→DistributedEStore.Common.RabbitMq.IBusPublisherDistributedEStore.Api.Gateway.Controllers.OrdersController→DistributedEStore.Common.RabbitMq.IBusPublisherDistributedEStore.Api.Gateway.Controllers.ProductsController→DistributedEStore.Common.RabbitMq.IBusPublisher
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Common.RabbitMq, so a change to DistributedEStore.Common.RabbitMq can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Common.RabbitMq.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
35→28 DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Api.Gateway✕
- Connections
- 4 pairs of types, where a type in DistributedEStore.Api.Gateway.Controllers uses a type in DistributedEStore.Api.Gateway.
- The types involved
DistributedEStore.Api.Gateway.Controllers.HomeController→DistributedEStore.Api.Gateway.BaseControllerDistributedEStore.Api.Gateway.Controllers.IdentityController→DistributedEStore.Api.Gateway.BaseControllerDistributedEStore.Api.Gateway.Controllers.OrdersController→DistributedEStore.Api.Gateway.BaseControllerDistributedEStore.Api.Gateway.Controllers.ProductsController→DistributedEStore.Api.Gateway.BaseController
- Direction
- DistributedEStore.Api.Gateway.Controllers uses DistributedEStore.Api.Gateway, so a change to DistributedEStore.Api.Gateway can break DistributedEStore.Api.Gateway.Controllers, while a change to DistributedEStore.Api.Gateway.Controllers can't break DistributedEStore.Api.Gateway.
- Position
- Below the diagonal: DistributedEStore.Api.Gateway.Controllers uses a module listed above it, which is the healthy direction.
36→5 DistributedEStore.Services.Identity.Services uses DistributedEStore.Common.Authentication✕
- Connections
- 6 pairs of types, where a type in DistributedEStore.Services.Identity.Services uses a type in DistributedEStore.Common.Authentication.
- The types involved
DistributedEStore.Services.Identity.Services.IIdentityService→DistributedEStore.Common.Authentication.JsonWebTokenDistributedEStore.Services.Identity.Services.IRefreshTokenService→DistributedEStore.Common.Authentication.JsonWebTokenDistributedEStore.Services.Identity.Services.IdentityService→DistributedEStore.Common.Authentication.IJwtHandlerDistributedEStore.Services.Identity.Services.IdentityService→DistributedEStore.Common.Authentication.JsonWebTokenDistributedEStore.Services.Identity.Services.RefreshTokenService→DistributedEStore.Common.Authentication.IJwtHandlerDistributedEStore.Services.Identity.Services.RefreshTokenService→DistributedEStore.Common.Authentication.JsonWebToken
- Direction
- DistributedEStore.Services.Identity.Services uses DistributedEStore.Common.Authentication, so a change to DistributedEStore.Common.Authentication can break DistributedEStore.Services.Identity.Services, while a change to DistributedEStore.Services.Identity.Services can't break DistributedEStore.Common.Authentication.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Services uses a module listed above it, which is the healthy direction.
36→8 DistributedEStore.Services.Identity.Services uses DistributedEStore.Common.Models✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Identity.Services uses a type in DistributedEStore.Common.Models.
- The types involved
DistributedEStore.Services.Identity.Services.IIdentityService→DistributedEStore.Common.Models.RegisterUserResponseDistributedEStore.Services.Identity.Services.IdentityService→DistributedEStore.Common.Models.RegisterUserResponse
- Direction
- DistributedEStore.Services.Identity.Services uses DistributedEStore.Common.Models, so a change to DistributedEStore.Common.Models can break DistributedEStore.Services.Identity.Services, while a change to DistributedEStore.Services.Identity.Services can't break DistributedEStore.Common.Models.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Services uses a module listed above it, which is the healthy direction.
36→18 DistributedEStore.Services.Identity.Services uses DistributedEStore.Common.RabbitMq✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Identity.Services uses a type in DistributedEStore.Common.RabbitMq.
- The types involved
DistributedEStore.Services.Identity.Services.IdentityService→DistributedEStore.Common.RabbitMq.IBusPublisherDistributedEStore.Services.Identity.Services.RefreshTokenService→DistributedEStore.Common.RabbitMq.IBusPublisher
- Direction
- DistributedEStore.Services.Identity.Services uses DistributedEStore.Common.RabbitMq, so a change to DistributedEStore.Common.RabbitMq can break DistributedEStore.Services.Identity.Services, while a change to DistributedEStore.Services.Identity.Services can't break DistributedEStore.Common.RabbitMq.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Services uses a module listed above it, which is the healthy direction.
36→19 DistributedEStore.Services.Identity.Services uses DistributedEStore.Services.Identity.Domain✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Identity.Services uses a type in DistributedEStore.Services.Identity.Domain.
- The types involved
DistributedEStore.Services.Identity.Services.IdentityService→DistributedEStore.Services.Identity.Domain.UserDistributedEStore.Services.Identity.Services.RefreshTokenService→DistributedEStore.Services.Identity.Domain.User
- Direction
- DistributedEStore.Services.Identity.Services uses DistributedEStore.Services.Identity.Domain, so a change to DistributedEStore.Services.Identity.Domain can break DistributedEStore.Services.Identity.Services, while a change to DistributedEStore.Services.Identity.Services can't break DistributedEStore.Services.Identity.Domain.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Services uses a module listed above it, which is the healthy direction.
36→31 DistributedEStore.Services.Identity.Services uses DistributedEStore.Services.Identity.Repositories✕
- Connections
- 4 pairs of types, where a type in DistributedEStore.Services.Identity.Services uses a type in DistributedEStore.Services.Identity.Repositories.
- The types involved
DistributedEStore.Services.Identity.Services.IdentityService→DistributedEStore.Services.Identity.Repositories.IRefreshTokenRepositoryDistributedEStore.Services.Identity.Services.IdentityService→DistributedEStore.Services.Identity.Repositories.IUserRepositoryDistributedEStore.Services.Identity.Services.RefreshTokenService→DistributedEStore.Services.Identity.Repositories.IRefreshTokenRepositoryDistributedEStore.Services.Identity.Services.RefreshTokenService→DistributedEStore.Services.Identity.Repositories.IUserRepository
- Direction
- DistributedEStore.Services.Identity.Services uses DistributedEStore.Services.Identity.Repositories, so a change to DistributedEStore.Services.Identity.Repositories can break DistributedEStore.Services.Identity.Services, while a change to DistributedEStore.Services.Identity.Services can't break DistributedEStore.Services.Identity.Repositories.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Services uses a module listed above it, which is the healthy direction.
37→11 DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Common.Types✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Orders.Handlers uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Services.Orders.Handlers.BrowseOrdersHandler→DistributedEStore.Common.Types.PagedResult
- Direction
- DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Services.Orders.Handlers, while a change to DistributedEStore.Services.Orders.Handlers can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.Handlers uses a module listed above it, which is the healthy direction.
37→15 DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Common.Messages.Orders✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Orders.Handlers uses a type in DistributedEStore.Common.Messages.Orders.
- The types involved
DistributedEStore.Services.Orders.Handlers.CreateOrderHandler→DistributedEStore.Common.Messages.Orders.CreateOrderDistributedEStore.Services.Orders.Handlers.CreateOrderHandler→DistributedEStore.Common.Messages.Orders.OrderItem
- Direction
- DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Common.Messages.Orders, so a change to DistributedEStore.Common.Messages.Orders can break DistributedEStore.Services.Orders.Handlers, while a change to DistributedEStore.Services.Orders.Handlers can't break DistributedEStore.Common.Messages.Orders.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.Handlers uses a module listed above it, which is the healthy direction.
37→18 DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Common.RabbitMq✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Orders.Handlers uses a type in DistributedEStore.Common.RabbitMq.
- The types involved
DistributedEStore.Services.Orders.Handlers.CreateOrderHandler→DistributedEStore.Common.RabbitMq.ICorrelationContext
- Direction
- DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Common.RabbitMq, so a change to DistributedEStore.Common.RabbitMq can break DistributedEStore.Services.Orders.Handlers, while a change to DistributedEStore.Services.Orders.Handlers can't break DistributedEStore.Common.RabbitMq.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.Handlers uses a module listed above it, which is the healthy direction.
37→21 DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Services.Orders.DomainEntities✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Orders.Handlers uses a type in DistributedEStore.Services.Orders.DomainEntities.
- The types involved
DistributedEStore.Services.Orders.Handlers.CreateOrderHandler→DistributedEStore.Services.Orders.DomainEntities.OrderItem
- Direction
- DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Services.Orders.DomainEntities, so a change to DistributedEStore.Services.Orders.DomainEntities can break DistributedEStore.Services.Orders.Handlers, while a change to DistributedEStore.Services.Orders.Handlers can't break DistributedEStore.Services.Orders.DomainEntities.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.Handlers uses a module listed above it, which is the healthy direction.
37→22 DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Services.Orders.Queries✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Orders.Handlers uses a type in DistributedEStore.Services.Orders.Queries.
- The types involved
DistributedEStore.Services.Orders.Handlers.BrowseOrdersHandler→DistributedEStore.Services.Orders.Queries.BrowseOrders
- Direction
- DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Services.Orders.Queries, so a change to DistributedEStore.Services.Orders.Queries can break DistributedEStore.Services.Orders.Handlers, while a change to DistributedEStore.Services.Orders.Handlers can't break DistributedEStore.Services.Orders.Queries.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.Handlers uses a module listed above it, which is the healthy direction.
37→29 DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Common.Handlers✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Orders.Handlers uses a type in DistributedEStore.Common.Handlers.
- The types involved
DistributedEStore.Services.Orders.Handlers.BrowseOrdersHandler→DistributedEStore.Common.Handlers.IQueryHandlerDistributedEStore.Services.Orders.Handlers.CreateOrderHandler→DistributedEStore.Common.Handlers.ICommandHandler
- Direction
- DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Common.Handlers, so a change to DistributedEStore.Common.Handlers can break DistributedEStore.Services.Orders.Handlers, while a change to DistributedEStore.Services.Orders.Handlers can't break DistributedEStore.Common.Handlers.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.Handlers uses a module listed above it, which is the healthy direction.
37→32 DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Services.Orders.Repositories✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Orders.Handlers uses a type in DistributedEStore.Services.Orders.Repositories.
- The types involved
DistributedEStore.Services.Orders.Handlers.BrowseOrdersHandler→DistributedEStore.Services.Orders.Repositories.IOrdersRepositoryDistributedEStore.Services.Orders.Handlers.CreateOrderHandler→DistributedEStore.Services.Orders.Repositories.IOrdersRepository
- Direction
- DistributedEStore.Services.Orders.Handlers uses DistributedEStore.Services.Orders.Repositories, so a change to DistributedEStore.Services.Orders.Repositories can break DistributedEStore.Services.Orders.Handlers, while a change to DistributedEStore.Services.Orders.Handlers can't break DistributedEStore.Services.Orders.Repositories.
- Position
- Below the diagonal: DistributedEStore.Services.Orders.Handlers uses a module listed above it, which is the healthy direction.
38→11 DistributedEStore.Services.Product.Controllers uses DistributedEStore.Common.Types✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Product.Controllers uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Services.Product.Controllers.ProductsController→DistributedEStore.Common.Types.PagedResult
- Direction
- DistributedEStore.Services.Product.Controllers uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Services.Product.Controllers, while a change to DistributedEStore.Services.Product.Controllers can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Services.Product.Controllers uses a module listed above it, which is the healthy direction.
38→14 DistributedEStore.Services.Product.Controllers uses DistributedEStore.Common.Dispatchers✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Product.Controllers uses a type in DistributedEStore.Common.Dispatchers.
- The types involved
DistributedEStore.Services.Product.Controllers.OrdersController→DistributedEStore.Common.Dispatchers.IDispatcherDistributedEStore.Services.Product.Controllers.ProductsController→DistributedEStore.Common.Dispatchers.IDispatcher
- Direction
- DistributedEStore.Services.Product.Controllers uses DistributedEStore.Common.Dispatchers, so a change to DistributedEStore.Common.Dispatchers can break DistributedEStore.Services.Product.Controllers, while a change to DistributedEStore.Services.Product.Controllers can't break DistributedEStore.Common.Dispatchers.
- Position
- Below the diagonal: DistributedEStore.Services.Product.Controllers uses a module listed above it, which is the healthy direction.
38→23 DistributedEStore.Services.Product.Controllers uses DistributedEStore.Services.Product.Queries✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Product.Controllers uses a type in DistributedEStore.Services.Product.Queries.
- The types involved
DistributedEStore.Services.Product.Controllers.ProductsController→DistributedEStore.Services.Product.Queries.BrowseProducts
- Direction
- DistributedEStore.Services.Product.Controllers uses DistributedEStore.Services.Product.Queries, so a change to DistributedEStore.Services.Product.Queries can break DistributedEStore.Services.Product.Controllers, while a change to DistributedEStore.Services.Product.Controllers can't break DistributedEStore.Services.Product.Queries.
- Position
- Below the diagonal: DistributedEStore.Services.Product.Controllers uses a module listed above it, which is the healthy direction.
38→25 DistributedEStore.Services.Product.Controllers uses DistributedEStore.Services.Products.Queries✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Product.Controllers uses a type in DistributedEStore.Services.Products.Queries.
- The types involved
DistributedEStore.Services.Product.Controllers.ProductsController→DistributedEStore.Services.Products.Queries.GetProduct
- Direction
- DistributedEStore.Services.Product.Controllers uses DistributedEStore.Services.Products.Queries, so a change to DistributedEStore.Services.Products.Queries can break DistributedEStore.Services.Product.Controllers, while a change to DistributedEStore.Services.Product.Controllers can't break DistributedEStore.Services.Products.Queries.
- Position
- Below the diagonal: DistributedEStore.Services.Product.Controllers uses a module listed above it, which is the healthy direction.
38→30 DistributedEStore.Services.Product.Controllers uses DistributedEStore.Common.Mvc✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Product.Controllers uses a type in DistributedEStore.Common.Mvc.
- The types involved
DistributedEStore.Services.Product.Controllers.OrdersController→DistributedEStore.Common.Mvc.BaseControllerDistributedEStore.Services.Product.Controllers.ProductsController→DistributedEStore.Common.Mvc.BaseController
- Direction
- DistributedEStore.Services.Product.Controllers uses DistributedEStore.Common.Mvc, so a change to DistributedEStore.Common.Mvc can break DistributedEStore.Services.Product.Controllers, while a change to DistributedEStore.Services.Product.Controllers can't break DistributedEStore.Common.Mvc.
- Position
- Below the diagonal: DistributedEStore.Services.Product.Controllers uses a module listed above it, which is the healthy direction.
39→11 DistributedEStore.Services.Products.Handlers uses DistributedEStore.Common.Types✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Products.Handlers uses a type in DistributedEStore.Common.Types.
- The types involved
DistributedEStore.Services.Products.Handlers.BrowseProductsHandler→DistributedEStore.Common.Types.PagedResult
- Direction
- DistributedEStore.Services.Products.Handlers uses DistributedEStore.Common.Types, so a change to DistributedEStore.Common.Types can break DistributedEStore.Services.Products.Handlers, while a change to DistributedEStore.Services.Products.Handlers can't break DistributedEStore.Common.Types.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Handlers uses a module listed above it, which is the healthy direction.
39→16 DistributedEStore.Services.Products.Handlers uses DistributedEStore.Common.Messages.Products✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Products.Handlers uses a type in DistributedEStore.Common.Messages.Products.
- The types involved
DistributedEStore.Services.Products.Handlers.CreateProductHandler→DistributedEStore.Common.Messages.Products.CreateProduct
- Direction
- DistributedEStore.Services.Products.Handlers uses DistributedEStore.Common.Messages.Products, so a change to DistributedEStore.Common.Messages.Products can break DistributedEStore.Services.Products.Handlers, while a change to DistributedEStore.Services.Products.Handlers can't break DistributedEStore.Common.Messages.Products.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Handlers uses a module listed above it, which is the healthy direction.
39→18 DistributedEStore.Services.Products.Handlers uses DistributedEStore.Common.RabbitMq✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Products.Handlers uses a type in DistributedEStore.Common.RabbitMq.
- The types involved
DistributedEStore.Services.Products.Handlers.CreateProductHandler→DistributedEStore.Common.RabbitMq.ICorrelationContext
- Direction
- DistributedEStore.Services.Products.Handlers uses DistributedEStore.Common.RabbitMq, so a change to DistributedEStore.Common.RabbitMq can break DistributedEStore.Services.Products.Handlers, while a change to DistributedEStore.Services.Products.Handlers can't break DistributedEStore.Common.RabbitMq.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Handlers uses a module listed above it, which is the healthy direction.
39→23 DistributedEStore.Services.Products.Handlers uses DistributedEStore.Services.Product.Queries✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Products.Handlers uses a type in DistributedEStore.Services.Product.Queries.
- The types involved
DistributedEStore.Services.Products.Handlers.BrowseProductsHandler→DistributedEStore.Services.Product.Queries.BrowseProducts
- Direction
- DistributedEStore.Services.Products.Handlers uses DistributedEStore.Services.Product.Queries, so a change to DistributedEStore.Services.Product.Queries can break DistributedEStore.Services.Products.Handlers, while a change to DistributedEStore.Services.Products.Handlers can't break DistributedEStore.Services.Product.Queries.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Handlers uses a module listed above it, which is the healthy direction.
39→25 DistributedEStore.Services.Products.Handlers uses DistributedEStore.Services.Products.Queries✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Products.Handlers uses a type in DistributedEStore.Services.Products.Queries.
- The types involved
DistributedEStore.Services.Products.Handlers.GetProductHandler→DistributedEStore.Services.Products.Queries.GetProduct
- Direction
- DistributedEStore.Services.Products.Handlers uses DistributedEStore.Services.Products.Queries, so a change to DistributedEStore.Services.Products.Queries can break DistributedEStore.Services.Products.Handlers, while a change to DistributedEStore.Services.Products.Handlers can't break DistributedEStore.Services.Products.Queries.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Handlers uses a module listed above it, which is the healthy direction.
39→29 DistributedEStore.Services.Products.Handlers uses DistributedEStore.Common.Handlers✕
- Connections
- 3 pairs of types, where a type in DistributedEStore.Services.Products.Handlers uses a type in DistributedEStore.Common.Handlers.
- The types involved
DistributedEStore.Services.Products.Handlers.BrowseProductsHandler→DistributedEStore.Common.Handlers.IQueryHandlerDistributedEStore.Services.Products.Handlers.CreateProductHandler→DistributedEStore.Common.Handlers.ICommandHandlerDistributedEStore.Services.Products.Handlers.GetProductHandler→DistributedEStore.Common.Handlers.IQueryHandler
- Direction
- DistributedEStore.Services.Products.Handlers uses DistributedEStore.Common.Handlers, so a change to DistributedEStore.Common.Handlers can break DistributedEStore.Services.Products.Handlers, while a change to DistributedEStore.Services.Products.Handlers can't break DistributedEStore.Common.Handlers.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Handlers uses a module listed above it, which is the healthy direction.
39→33 DistributedEStore.Services.Products.Handlers uses DistributedEStore.Services.Products.Repositories✕
- Connections
- 3 pairs of types, where a type in DistributedEStore.Services.Products.Handlers uses a type in DistributedEStore.Services.Products.Repositories.
- The types involved
DistributedEStore.Services.Products.Handlers.BrowseProductsHandler→DistributedEStore.Services.Products.Repositories.IProductsRepositoryDistributedEStore.Services.Products.Handlers.CreateProductHandler→DistributedEStore.Services.Products.Repositories.IProductsRepositoryDistributedEStore.Services.Products.Handlers.GetProductHandler→DistributedEStore.Services.Products.Repositories.IProductsRepository
- Direction
- DistributedEStore.Services.Products.Handlers uses DistributedEStore.Services.Products.Repositories, so a change to DistributedEStore.Services.Products.Repositories can break DistributedEStore.Services.Products.Handlers, while a change to DistributedEStore.Services.Products.Handlers can't break DistributedEStore.Services.Products.Repositories.
- Position
- Below the diagonal: DistributedEStore.Services.Products.Handlers uses a module listed above it, which is the healthy direction.
40→5 DistributedEStore.Services.Identity.Controllers uses DistributedEStore.Common.Authentication✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Identity.Controllers uses a type in DistributedEStore.Common.Authentication.
- The types involved
DistributedEStore.Services.Identity.Controllers.IdentityController→DistributedEStore.Common.Authentication.JsonWebTokenDistributedEStore.Services.Identity.Controllers.TokensController→DistributedEStore.Common.Authentication.IAccessTokenService
- Direction
- DistributedEStore.Services.Identity.Controllers uses DistributedEStore.Common.Authentication, so a change to DistributedEStore.Common.Authentication can break DistributedEStore.Services.Identity.Controllers, while a change to DistributedEStore.Services.Identity.Controllers can't break DistributedEStore.Common.Authentication.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Controllers uses a module listed above it, which is the healthy direction.
40→6 DistributedEStore.Services.Identity.Controllers uses DistributedEStore.Common.Commands.Identity✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Identity.Controllers uses a type in DistributedEStore.Common.Commands.Identity.
- The types involved
DistributedEStore.Services.Identity.Controllers.IdentityController→DistributedEStore.Common.Commands.Identity.SignInCommandDistributedEStore.Services.Identity.Controllers.IdentityController→DistributedEStore.Common.Commands.Identity.SignUpCommand
- Direction
- DistributedEStore.Services.Identity.Controllers uses DistributedEStore.Common.Commands.Identity, so a change to DistributedEStore.Common.Commands.Identity can break DistributedEStore.Services.Identity.Controllers, while a change to DistributedEStore.Services.Identity.Controllers can't break DistributedEStore.Common.Commands.Identity.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Controllers uses a module listed above it, which is the healthy direction.
40→8 DistributedEStore.Services.Identity.Controllers uses DistributedEStore.Common.Models✕
- Connections
- 1 pair of types, where a type in DistributedEStore.Services.Identity.Controllers uses a type in DistributedEStore.Common.Models.
- The types involved
DistributedEStore.Services.Identity.Controllers.IdentityController→DistributedEStore.Common.Models.RegisterUserResponse
- Direction
- DistributedEStore.Services.Identity.Controllers uses DistributedEStore.Common.Models, so a change to DistributedEStore.Common.Models can break DistributedEStore.Services.Identity.Controllers, while a change to DistributedEStore.Services.Identity.Controllers can't break DistributedEStore.Common.Models.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Controllers uses a module listed above it, which is the healthy direction.
40→20 DistributedEStore.Services.Identity.Controllers uses DistributedEStore.Services.Identity.Messages.Commands✕
- Connections
- 4 pairs of types, where a type in DistributedEStore.Services.Identity.Controllers uses a type in DistributedEStore.Services.Identity.Messages.Commands.
- The types involved
DistributedEStore.Services.Identity.Controllers.IdentityController→DistributedEStore.Services.Identity.Messages.Commands.ChangePasswordDistributedEStore.Services.Identity.Controllers.TokensController→DistributedEStore.Services.Identity.Messages.Commands.RefreshAccessTokenDistributedEStore.Services.Identity.Controllers.TokensController→DistributedEStore.Services.Identity.Messages.Commands.RevokeAccessTokenDistributedEStore.Services.Identity.Controllers.TokensController→DistributedEStore.Services.Identity.Messages.Commands.RevokeRefreshToken
- Direction
- DistributedEStore.Services.Identity.Controllers uses DistributedEStore.Services.Identity.Messages.Commands, so a change to DistributedEStore.Services.Identity.Messages.Commands can break DistributedEStore.Services.Identity.Controllers, while a change to DistributedEStore.Services.Identity.Controllers can't break DistributedEStore.Services.Identity.Messages.Commands.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Controllers uses a module listed above it, which is the healthy direction.
40→36 DistributedEStore.Services.Identity.Controllers uses DistributedEStore.Services.Identity.Services✕
- Connections
- 2 pairs of types, where a type in DistributedEStore.Services.Identity.Controllers uses a type in DistributedEStore.Services.Identity.Services.
- The types involved
DistributedEStore.Services.Identity.Controllers.IdentityController→DistributedEStore.Services.Identity.Services.IIdentityServiceDistributedEStore.Services.Identity.Controllers.TokensController→DistributedEStore.Services.Identity.Services.IRefreshTokenService
- Direction
- DistributedEStore.Services.Identity.Controllers uses DistributedEStore.Services.Identity.Services, so a change to DistributedEStore.Services.Identity.Services can break DistributedEStore.Services.Identity.Controllers, while a change to DistributedEStore.Services.Identity.Controllers can't break DistributedEStore.Services.Identity.Services.
- Position
- Below the diagonal: DistributedEStore.Services.Identity.Controllers 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 129 | High / Critical |
| A02:2025 — Security Misconfiguration | 48 | High / Critical |
| A07:2025 — Authentication Failures | 13 | High / Critical |
| A05:2025 — Injection | 8 | Medium |
| A01:2025 — Broken Access Control | 1 | Medium |
Roadmap
Top priorities: Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (8); Resolve the 30 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (19), REDACTED (3), Distributed-eStore.Services.Order.csproj (3); Resolve the 15 Outdated finding(s) in Dependency Hygiene — start with REDACTED (11), REDACTED (2), Distributed-eStore.UI.csproj (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (8). | +9.2 pts | Low | Secret Scanning |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with App.test.tsx. | +4.5 pts | Low | Test Quality |
| Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with App.test.tsx. | +4.3 pts | Low | Test Quality |
| Resolve the 30 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (19), REDACTED (3), Distributed-eStore.Services.Order.csproj (3). | +8.3 pts | Medium | Dependency Hygiene |
| Resolve the 15 Outdated finding(s) in Dependency Hygiene — start with REDACTED (11), REDACTED (2), Distributed-eStore.UI.csproj (2). | +5.6 pts | Medium | Dependency Hygiene |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +4.4 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +4.4 pts | Medium | Security & performance tooling |
| Resolve the 10 Prerelease dependency finding(s) in Dependency Hygiene. | +4.2 pts | Medium | Dependency Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.0 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 4.3 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| Distributed-eStore.UI/src/Distributed-eStore.UI.csproj | 4.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net5.0 |
| Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs | 4.9 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| Distributed-eStore.Services.Order/src/Distributed-eStore.Services.Order.csproj | 5.3 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net5.0 |
| REDACTED | 5.5 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| Distributed-eStore.UI/src/Controllers/BaseController.cs | 5.5 | Mixed | Explicit Debt: WriteOnlyPrivateField |
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 107 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 — 107 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, 438 of 485 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 — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.tsx) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but the runner its test command uses is one the re-runner has no executor for (`react-scripts`). Read from the manifests: `Distributed-eStore.UI/src/ClientApp` has a `scripts.test` of `cross-env CI=true react-scripts test --env=jsdom` and declares `react-scripts`. So flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's runner coverage, not a missing .tsx runner and not a finding about this repository.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares npm dependencies as well as NuGet ones — manifest: REDACTED — and the counts on this row cover the NuGet side ONLY. This dimension reads dependency currency from `<PackageReference>` elements via `dotnet list package`; it does not read it, so the npm packages declared there were not checked for newer, deprecated or unmaintained releases. Their absence from the counts above is a gap in this analyzer's ecosystem coverage — not a finding that those dependencies are current.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 310 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Distributed-eStore.UI/src/Distributed-eStore.UI.csproj' with message: The target framework 'net5.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- 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) — 3 | 4 | ADD Distributed-eStore.UI Distributed-eStore.UI 5 | >>> ADD Distributed-eStore.Common Distributed-eStore.Common 6 | 7 | WORKDIR /app/Distributed-eStore.UI -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 2c0a303d-29bf-4210-a943-b07ca26a3feb::uj3xqtk3d9ubpv6qilgmmmsmu: "/Distributed-eStore.Common": 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.
- M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
- 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. 44 further occurrence(s) are not listed individually; the score already reflects all 84.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RegisterPage.render at 18.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with RegisterPage.render (cyclomatic 18). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
- Stand up a CI pipeline, then gate Cyclomatic Complexity 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.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with ProductsSeeder.cs. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate God Classes 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.
D4 · Code Duplication
8 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with REDACTED, BaseController.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with BaseController.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with BaseController.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
6 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 22 classes have LCOM4 above 3.
D9 · Test Distribution
1 test methods: 1 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 1 `it`/`test` case(s) across 1 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1 tests.
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with App.test.tsx. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with App.test.tsx. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
32 outdated, 3 vulnerable, 22 deprecated, 10 prerelease packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.
What to do
- Resolve the 30 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (19), REDACTED (3), Distributed-eStore.Services.Order.csproj (3). — One of this dimension's main actionable groups (30 warning-level).
- Resolve the 15 Outdated finding(s) in Dependency Hygiene — start with REDACTED (11), REDACTED (2), Distributed-eStore.UI.csproj (2). — One of this dimension's main actionable groups (15 recommendation-level).
- Resolve the 10 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (10 warning-level).
- Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
8 secret(s) detected.
What to do
- Resolve the 8 Leaked secret finding(s) in Secret Scanning — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 260 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 43 direct `PackageReference`(s), and 207 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
10 deducted debt markers + unmeasured dead symbols across 5145 LoC in the .NET projects (1.2/KLoC) → score 7.7. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 8 WriteOnlyPrivateField finding(s) in Explicit Debt — start with BaseController.cs (4), REDACTED, MongoDbInitializer.cs. — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with BrowseOrdersHandler.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with BrowseOrdersHandler.cs. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
6 projects, 183 source files, 5145 hand-written lines of code (5145 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 5 inter-project edges.
D19 · Documentation Quality
0 of 2 documentation facets pass in full; short on: F2 example, F4 map. 2 document(s) read across 8 unit(s).
What to do
- Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). — One of this dimension's main actionable groups (2 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
2 naming inconsistencies among 51 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `IsCurrentActiveToken` returns an awaitable but lacks the `Async` suffix… finding(s) in Naming Consistency — start with IAccessTokenService.cs. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `Invoke` returns an awaitable but lacks the `Async` suffix its 35 peers… finding(s) in Naming Consistency — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (6 contexts). Contexts: Distributed-eStore, Distributed-eStore.Api.Gateway, Distributed-eStore.Common, Distributed-eStore.Services.Identity, Distributed-eStore.Services.Order, Distributed-eStore.Services.Product.
D26 · Project Cohesion
0 of 6 projects flagged as possibly oversized/incoherent.
D27 · Navigability
90 % of calls cross a namespace and 19 % go through an interface, but 96 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Pass-through layer finding(s) in Navigability — start with OrdersRepository.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 0 high, 8 medium, 0 low.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
129 finding(s): 21 critical, 64 high, 36 medium, 8 low.
What to do
- Resolve the 63 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (56), REDACTED (5), REDACTED (2). — One of this dimension's main actionable groups (63 issue-level).
- Resolve the 20 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (17), REDACTED (2). — One of this dimension's main actionable groups (20 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
48 finding(s): 0 critical, 17 high, 13 medium, 18 low.
What to do
- Resolve the 18 Low IaC finding(s) in IaC & Container Security — start with REDACTED (18). — One of this dimension's main actionable groups (18 recommendation-level).
- Resolve the 17 High IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED (8). — One of this dimension's main actionable groups (17 issue-level).
- Resolve the 13 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (12), REDACTED. — One of this dimension's main actionable groups (13 warning-level).
D32 · Data Compliance (PII/GDPR)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
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
21 of 21 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs. Counted over 21 of the 183 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 21 Orphaned file finding(s) in Knowledge Freshness — start with Startup.cs (5), Extensions.cs (4), BaseController.cs (2). — One of this dimension's main actionable groups (21 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
Strongest change-coupling: CartProduct.tsx↔Cart.tsx 73%; productsActions.ts↔productsReducers.ts 54%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with CartProduct.tsx, productsActions.ts. — One of this dimension's main actionable groups (2 warning-level).
D39 · IL Efficiency
1 of 408 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 6 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 5 End-of-life runtime finding(s) in Platform End-of-Life — start with Distributed-eStore.Api.Gateway.csproj, REDACTED, Distributed-eStore.Services.Order.csproj. — One of this dimension's main actionable groups (5 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×4) — Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:25, Distributed-eStore.UI/src/ClientApp/src/components/products/Product/Product.tsx:26, Distributed-eStore.UI/src/ClientApp/src/containers/NavMenu/NavMenu.tsx:29, …
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×2) — Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:13, Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:45
- This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×7) — Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:37, Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:60, Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:67, …
- This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — Distributed-eStore.UI/src/ClientApp/src/components/products/ColorBox/ColorBox.tsx:16
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — Distributed-eStore.UI/src/ClientApp/public/index.html:2
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — Distributed-eStore.UI/src/ClientApp/src/components/OrderCreatedPage/OrderCreatedPage.tsx:7, Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:24
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- The repo's own CSS styles .cart-products__button__text with `cursor: pointer`, so this <span> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProducts/CartProducts.tsx:39
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. — Distributed-eStore.UI/src/ClientApp/src/components/products/ColorBox/ColorBox.tsx:16
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 27 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — REDACTED:41
What to do
- Accessibility linting is already configured — assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `MongoDbInitializer` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_initialized; e.g. `_initialized` at line 34). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Distributed-eStore.Common/Mongo/MongoDbInitializer.cs:11
What to do
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
- `RefreshToken` reads `DateTime.UtcNow` inside `Revoke`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:35
What to do
- Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM2 · Strongly-typed ids
- `RefreshToken.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:10
- `AccessTokenRefreshed.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/AccessTokenRefreshed.cs:9
- `AccessTokenRevoked.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/AccessTokenRevoked.cs:9
- `PasswordChanged.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/PasswordChanged.cs:9
- `RefreshAccessTokenRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/RefreshAccessTokenRejected.cs:9
- `RefreshTokenRevoked.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/RefreshTokenRevoked.cs:9
- `RevokeAccessTokenRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/RevokeAccessTokenRejected.cs:9
- `RevokeRefreshTokenRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/RevokeRefreshTokenRejected.cs:9
- `SignedIn.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/SignedIn.cs:9
- `SignedUp.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/SignedUp.cs:9
- `SignUpRejected.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Identity/src/Messages/Events/SignUpRejected.cs:9
- `Order.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Order/src/DomainEntities/Order.cs:8
- `OrderItem.ProductId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Distributed-eStore.Services.Order/src/DomainEntities/OrderItem.cs:8
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
DM5 · Encapsulated state
- `Product` exposes publicly writable state (Name, Description, Price, Category, ImageURLs, Colors). — Distributed-eStore.Services.Product/src/DomainEntities/Product.cs:6
- `Order` exposes publicly writable state (CustomerId, OrderItems). — Distributed-eStore.Services.Order/src/DomainEntities/Order.cs:6
- `OrderItem` exposes publicly writable state (ProductId, Quantity, Size). — Distributed-eStore.Services.Order/src/DomainEntities/OrderItem.cs:6
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
- `RefreshToken` (domain layer) names `IPasswordHasher` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:20, Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:38
- `User` (domain layer) names `IPasswordHasher` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — Distributed-eStore.Services.Identity/src/Domain/User.cs:49, Distributed-eStore.Services.Identity/src/Domain/User.cs:59
- `User` (domain layer) names `PasswordVerificationResult` from `Microsoft.AspNetCore.Identity` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. — Distributed-eStore.Services.Identity/src/Domain/User.cs:60
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
ED5 · Idempotency
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:19
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `HandleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:19
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×3) — Distributed-eStore.Common/RestEase/QueryParamSerializer.cs:68, Distributed-eStore.Services.Identity/src/Startup.cs:66, Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:22
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- 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
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 6 of 6 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
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 2/6 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 6, 5 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.
- `Distributed-eStore.Api.Gateway/src/Distributed-eStore.Api.Gateway.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`. — Distributed-eStore.Api.Gateway/src/Distributed-eStore.Api.Gateway.csproj:12
What to do
- Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `services.AddHttpClient<IConsulHttpClient, ConsulHttpClient>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — Distributed-eStore.Common/Consul/Extensions.cs:29
- `services.AddHttpClient<IFabioHttpClient, FabioHttpClient>()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — Distributed-eStore.Common/Fabio/Extensions.cs:17
- `services.AddHttpClient(clientName)` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). (×2) — Distributed-eStore.Common/RestEase/Extensions.cs:52, Distributed-eStore.Common/RestEase/Extensions.cs:61
- `services.AddHttpClient(clientName, client => { var service = options.Services...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — Distributed-eStore.Common/RestEase/Extensions.cs:69
What to do
- Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:25 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:29 — the two spans are one implementation copied and then locally edited — 410 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:25
- Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:16 · Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:29 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:16
- Distributed-eStore.UI/src/ClientApp/src/containers/AccessoriesProductsPage/AccessoriesProductsPage.tsx:24 · Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Distributed-eStore.UI/src/ClientApp/src/containers/AccessoriesProductsPage/AccessoriesProductsPage.tsx:24
- Distributed-eStore.UI/src/ClientApp/src/containers/FemaleProductsPage/FemaleProductsPage.tsx:24 · Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Distributed-eStore.UI/src/ClientApp/src/containers/FemaleProductsPage/FemaleProductsPage.tsx:24
- Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31 · Distributed-eStore.UI/src/ClientApp/src/containers/MaleProductsPage/MaleProductsPage.tsx:24 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31
- Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:58 · Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:65 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:58
- Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:67 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:74 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:81 · Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:88 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:67
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×5) — Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts:1, Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts:1, Distributed-eStore.UI/src/ClientApp/src/services/api/products.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 36 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add `tsc --noEmit` as REDACTED scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 1 application, 1 tooling and 1 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts, Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts
- no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/services/api/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — Distributed-eStore.UI/src/ClientApp/src/services/api/products.ts
- no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts, Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts, Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — Distributed-eStore.UI/src/ClientApp/src/state/Products/productsTypes.ts
- no import path from any entry point (1 application, 1 tooling, 1 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — Distributed-eStore.UI/src/ClientApp/src/components/routing/PrivateRoute.jsx, Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts, Distributed-eStore.UI/src/ClientApp/src/containers/index.tsx
- no import path from any entry point (1 application, 1 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — Distributed-eStore.UI/src/ClientApp/src/services/api/index.ts
- Nothing imports this binding — it is safe to review for removal. — Distributed-eStore.UI/src/ClientApp/src/registerServiceWorker.ts:99
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- Distributed-eStore.UI/src/ClientApp/src/components/products/index.ts → Distributed-eStore.UI/src/ClientApp/src/components/products/ColorSwitcher/ColorSwitcher.tsx → Distributed-eStore.UI/src/ClientApp/src/components/products/index.ts (one verified cycle inside a mutually-dependent group of 11 files) — Distributed-eStore.UI/src/ClientApp/src/components/products/index.ts:2
- Distributed-eStore.UI/src/ClientApp/src/services/api/createOrder.ts → Distributed-eStore.UI/src/ClientApp/src/state/cart/index.ts → Distributed-eStore.UI/src/ClientApp/src/state/cart/cartActions.ts → Distributed-eStore.UI/src/ClientApp/src/services/api/createOrder.ts — Distributed-eStore.UI/src/ClientApp/src/services/api/createOrder.ts:3
- Distributed-eStore.UI/src/ClientApp/src/services/auth/authUtils.ts → Distributed-eStore.UI/src/ClientApp/src/state/user/index.ts → REDACTED → Distributed-eStore.UI/src/ClientApp/src/services/auth/index.ts → Distributed-eStore.UI/src/ClientApp/src/services/auth/authUtils.ts — Distributed-eStore.UI/src/ClientApp/src/services/auth/authUtils.ts:3
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×9) — Distributed-eStore.Api.Gateway/src/Program.cs:12, Distributed-eStore.Api.Gateway/src/Program.cs:25, Distributed-eStore.Services.Identity/src/Program.cs:12, …
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
- `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:11
- 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. — Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:19
What to do
- async void method: SeedProductsAsync
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 4/87 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) — Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:29, Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:37, Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:42, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×9) — REDACTED:31, Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:116, Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:117, …
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 0/5 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 49% | Weak — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 68% | Adequate — gated by R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 66% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 26% | Weak — gated by D13, P1, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 61% | Adequate — gated by D31 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 52% | Adequate — gated by DM2, DM5, DM6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 37% | Weak — gated by AC1, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 30 check(s) not relevant to this codebase
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- 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) — 3 | 4 | ADD Distributed-eStore.UI Distributed-eStore.UI 5 | >>> ADD Distributed-eStore.Common Distributed-eStore.Common 6 | 7 | WORKDIR /app/Distributed-eStore.UI -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 2c0a303d-29bf-4210-a943-b07ca26a3feb::uj3xqtk3d9ubpv6qilgmmmsmu: "/Distributed-eStore.Common": not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D11 Test Reliability — Test reliability not included — no executor for the `react-scripts` test runner
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D24 Comment Value — Too few judgeable comments (28 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 CQRS handler(s))
- 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
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- 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 — 147 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField REDACTED:13
- WriteOnlyPrivateField Distributed-eStore.Common/Mongo/MongoDbInitializer.cs:15
- WriteOnlyPrivateField Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:14
- WriteOnlyPrivateField Distributed-eStore.UI/src/Controllers/BaseController.cs:12
- WriteOnlyPrivateField Distributed-eStore.UI/src/Controllers/BaseController.cs:13
- WriteOnlyPrivateField Distributed-eStore.UI/src/Controllers/BaseController.cs:14
- WriteOnlyPrivateField Distributed-eStore.UI/src/Controllers/BaseController.cs:15
- WriteOnlyPrivateField REDACTED:15
- <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:37
- <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:60
- <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:67
- <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:69
- <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:76
- <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:83
- <input> without a programmatic label Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:90
- Domain depends on infrastructure: RefreshToken Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:20
- Domain depends on infrastructure: RefreshToken Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:38
- Domain depends on infrastructure: User Distributed-eStore.Services.Identity/src/Domain/User.cs:49
- Domain depends on infrastructure: User Distributed-eStore.Services.Identity/src/Domain/User.cs:59
- Domain depends on infrastructure: User Distributed-eStore.Services.Identity/src/Domain/User.cs:60
- <img> without a text alternative Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:25
- <img> without a text alternative Distributed-eStore.UI/src/ClientApp/src/components/products/Product/Product.tsx:26
- <img> without a text alternative Distributed-eStore.UI/src/ClientApp/src/containers/NavMenu/NavMenu.tsx:29
- <img> without a text alternative Distributed-eStore.UI/src/ClientApp/src/containers/ProductView/ProductView.tsx:57
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Link with no accessible name Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:13
- Link with no accessible name Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:45
- Custom control with no accessible name on <span> Distributed-eStore.UI/src/ClientApp/src/components/products/ColorBox/ColorBox.tsx:16
- Clickable element isn't keyboard-operable Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProducts/CartProducts.tsx:39
- Click handler on a non-interactive <span> Distributed-eStore.UI/src/ClientApp/src/components/products/ColorBox/ColorBox.tsx:16
- No assertions (empty test): renders without crashing Distributed-eStore.UI/src/ClientApp/src/App.test.tsx:7
- REDACTED
- REDACTED
- Import cycle (2 files) Distributed-eStore.UI/src/ClientApp/src/components/products/index.ts:2
- Import cycle (3 files) Distributed-eStore.UI/src/ClientApp/src/services/api/createOrder.ts:3
- Import cycle (4 files) Distributed-eStore.UI/src/ClientApp/src/services/auth/authUtils.ts:3
Serious — 201 finding(s)
- Async method without CancellationToken: SignUp Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:29
- Async method without CancellationToken: SignIn Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:37
- Async method without CancellationToken: ChangePassword Distributed-eStore.Services.Identity/src/Controllers/IdentityController.cs:42
- Async method without CancellationToken: RefreshAccessToken REDACTED:28
- Async method without CancellationToken: RevokeAccessToken REDACTED:32
- Async method without CancellationToken: RevokeRefreshToken REDACTED:41
- Async method without CancellationToken: GetAsync Distributed-eStore.Services.Identity/src/Repositories/RefreshTokenRepository.cs:19
- Async method without CancellationToken: AddAsync Distributed-eStore.Services.Identity/src/Repositories/RefreshTokenRepository.cs:22
- Async method without CancellationToken: UpdateAsync Distributed-eStore.Services.Identity/src/Repositories/RefreshTokenRepository.cs:25
- Async method without CancellationToken: GetAsync Distributed-eStore.Services.Identity/src/Repositories/UserRepository.cs:17
- Async method without CancellationToken: GetAsync Distributed-eStore.Services.Identity/src/Repositories/UserRepository.cs:20
- Async method without CancellationToken: AddAsync Distributed-eStore.Services.Identity/src/Repositories/UserRepository.cs:23
- Async method without CancellationToken: UpdateAsync Distributed-eStore.Services.Identity/src/Repositories/UserRepository.cs:26
- Async method without CancellationToken: SignUpAsync Distributed-eStore.Services.Identity/src/Services/IdentityService.cs:38
- Async method without CancellationToken: SignInAsync Distributed-eStore.Services.Identity/src/Services/IdentityService.cs:68
- Async method without CancellationToken: ChangePasswordAsync Distributed-eStore.Services.Identity/src/Services/IdentityService.cs:85
- Async method without CancellationToken: AddAsync Distributed-eStore.Services.Identity/src/Services/RefreshTokenService.cs:37
- Async method without CancellationToken: CreateAccessTokenAsync Distributed-eStore.Services.Identity/src/Services/RefreshTokenService.cs:48
- Async method without CancellationToken: RevokeAsync Distributed-eStore.Services.Identity/src/Services/RefreshTokenService.cs:75
- Async method without CancellationToken: IsCurrentActiveToken Distributed-eStore.Common/Authentication/AccessTokenService.cs:26
- Async method without CancellationToken: DeactivateCurrentAsync Distributed-eStore.Common/Authentication/AccessTokenService.cs:29
- Async method without CancellationToken: IsActiveAsync Distributed-eStore.Common/Authentication/AccessTokenService.cs:32
- Async method without CancellationToken: DeactivateAsync Distributed-eStore.Common/Authentication/AccessTokenService.cs:35
- Async method without CancellationToken: GetAsync REDACTED:16
- Async method without CancellationToken: GetRequestUriAsync Distributed-eStore.Common/Consul/ConsulServiceDiscoveryMessageHandler.cs:59
- 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
- Deprecated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:11
- Deprecated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:79
- Deprecated: Microsoft.AspNetCore.Authentication.JwtBearer Distributed-eStore.Services.Order/src/Distributed-eStore.Services.Order.csproj:11
- Deprecated: Microsoft.AspNetCore.Authentication.OpenIdConnect REDACTED:12
- Deprecated: Microsoft.AspNetCore.Authentication.OpenIdConnect Distributed-eStore.Services.Order/src/Distributed-eStore.Services.Order.csproj:12
- Deprecated: OpenTracing.Contrib.NetCore REDACTED:25
- Deprecated: OpenTracing.Contrib.NetCore Distributed-eStore.Api.Gateway/src/Distributed-eStore.Api.Gateway.csproj:19
- Deprecated: OpenTracing.Contrib.NetCore Distributed-eStore.Services.Product/src/Distributed-eStore.Services.Product.csproj:18
- Deprecated: OpenTracing.Contrib.NetCore Distributed-eStore.UI/src/Distributed-eStore.UI.csproj:105
- Deprecated: OpenTracing.Contrib.NetCore Distributed-eStore.Services.Order/src/Distributed-eStore.Services.Order.csproj:15
- Deprecated: Microsoft.AspNetCore REDACTED:17
- Deprecated: Microsoft.AspNetCore.Authentication REDACTED:78
- Deprecated: Microsoft.AspNetCore.Authorization REDACTED:80
- Deprecated: Microsoft.AspNetCore.Hosting REDACTED:20
- Deprecated: Microsoft.AspNetCore.Identity REDACTED:77
- Deprecated: Microsoft.AspNetCore.Mvc REDACTED:23
- Deprecated: Microsoft.AspNetCore.Mvc.Core REDACTED:26
- Deprecated: Microsoft.AspNetCore.Mvc.DataAnnotations REDACTED:29
- Deprecated: Microsoft.AspNetCore.Server.Kestrel REDACTED:32
- Deprecated: Microsoft.AspNetCore.StaticFiles REDACTED:35
- Deprecated: Microsoft.Extensions.Configuration.Binder REDACTED:38
- Deprecated: Microsoft.Extensions.Configuration.EnvironmentVariables REDACTED:41
- Deprecated: Microsoft.Extensions.Configuration.FileExtensions REDACTED:44
- Deprecated: Microsoft.Extensions.Configuration.Json REDACTED:47
- Deprecated: Microsoft.Extensions.DependencyInjection REDACTED:50
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Prerelease dependency: RawRabbit
- Prerelease dependency: RawRabbit.DependencyInjection.Autofac
- Prerelease dependency: RawRabbit.DependencyInjection.ServiceCollection
- Prerelease dependency: RawRabbit.Enrichers.Attributes
- Prerelease dependency: RawRabbit.Enrichers.MessageContext
- Prerelease dependency: RawRabbit.Enrichers.MessageContext.Subscribe
- Prerelease dependency: RawRabbit.Enrichers.Polly
- Prerelease dependency: RawRabbit.Enrichers.RetryLater
- Prerelease dependency: RawRabbit.Operations.Publish
- Prerelease dependency: RawRabbit.Operations.Subscribe
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- End-of-life runtime: .NET net5.0 Distributed-eStore.Api.Gateway/src/Distributed-eStore.Api.Gateway.csproj:4
- End-of-life runtime: .NET net5.0 REDACTED:4
- End-of-life runtime: .NET net5.0 Distributed-eStore.Services.Order/src/Distributed-eStore.Services.Order.csproj:4
- End-of-life runtime: .NET net5.0 Distributed-eStore.Services.Product/src/Distributed-eStore.Services.Product.csproj:4
- End-of-life runtime: .NET net5.0 Distributed-eStore.UI/src/Distributed-eStore.UI.csproj:4
- Outbound HTTP without resilience Distributed-eStore.Common/Consul/Extensions.cs:29
- Outbound HTTP without resilience Distributed-eStore.Common/Fabio/Extensions.cs:17
- Outbound HTTP without resilience Distributed-eStore.Common/RestEase/Extensions.cs:52
- Outbound HTTP without resilience Distributed-eStore.Common/RestEase/Extensions.cs:61
- Outbound HTTP without resilience Distributed-eStore.Common/RestEase/Extensions.cs:69
- No test reaches this file Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts:1
- No test reaches this file Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts:1
- No test reaches this file Distributed-eStore.UI/src/ClientApp/src/services/api/products.ts:1
- No test reaches this file Distributed-eStore.UI/src/ClientApp/src/state/Products/productsTypes.ts:1
- No test reaches this file Distributed-eStore.UI/src/ClientApp/src/components/routing/PrivateRoute.jsx:1
- Mutable entity: Product Distributed-eStore.Services.Product/src/DomainEntities/Product.cs:6
- Mutable entity: Order Distributed-eStore.Services.Order/src/DomainEntities/Order.cs:6
- Mutable entity: OrderItem Distributed-eStore.Services.Order/src/DomainEntities/OrderItem.cs:6
- Duplicated block with local edits (7 matched lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/containers/AccessoriesProductsPage/AccessoriesProductsPage.tsx:24
- Duplicated block with local edits (7 matched lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/containers/FemaleProductsPage/FemaleProductsPage.tsx:24
- Duplicated block with local edits (7 matched lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:31
- REDACTED
- REDACTED
- Change coupling: CartProduct.tsx ↔ Cart.tsx Distributed-eStore.UI/src/ClientApp/src/components/cart/cartProduct/CartProduct.tsx:1
- Change coupling: productsActions.ts ↔ productsReducers.ts Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts:1
- Duplicated block (11 lines × 2) REDACTED:18
- Duplicated block (11 lines × 2) Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:131
- Page without a main landmark Distributed-eStore.UI/src/ClientApp/public/index.html:2
- Heading level jumps from h2 to h4 Distributed-eStore.UI/src/ClientApp/src/components/OrderCreatedPage/OrderCreatedPage.tsx:7
- Heading level jumps from h1 to h3 Distributed-eStore.UI/src/ClientApp/src/containers/HomePage/HomePage.tsx:24
- Process-global static state: MongoDbInitializer Distributed-eStore.Common/Mongo/MongoDbInitializer.cs:11
- RegisterPage.render (cyclomatic 18) Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:58
- Test project verifies nothing: Distributed-eStore.UI/src/ClientApp Distributed-eStore.UI/src/ClientApp/src/App.test.tsx:7
- TodoComment Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:21
- CommentedOutCode Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:22
- REDACTED
- MethodTooLong: ProductsSeeder.GetProducts Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:28
- REDACTED
- Duplicated block (18 lines × 2) Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:46
- Duplicated block (16 lines × 2) Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:112
- Duplicated block (13 lines × 2) Distributed-eStore.Services.Order/src/Startup.cs:29
- Duplicated block (7 lines × 3) Distributed-eStore.Common/Messages/Products/CreateProduct.cs:9
- Duplicated block (7 lines × 2) Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:118
- Duplicated block (12 lines × 2) Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:31
- Domain type reads the wall clock: RefreshToken Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:35
- Unfinished stub — throws NotImplementedException Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:19
- Unfinished stub — throws NotImplementedException Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:19
- No CI pipeline
- Duplicated block with local edits (53 matched lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:25
- Duplicated block (13 lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/components/Footer/Footer.tsx:16
- Duplicated block (7 lines × 2 locations) Distributed-eStore.UI/src/ClientApp/src/containers/Login/Login.tsx:58
- Duplicated block (7 lines × 4 locations) Distributed-eStore.UI/src/ClientApp/src/containers/Register/Register.tsx:67
- Dependency Freshness
- No typecheck script
- Dead file (~76 LoC) Distributed-eStore.UI/src/ClientApp/src/state/Products/productsActions.ts
- Dead file (~74 LoC) Distributed-eStore.UI/src/ClientApp/src/state/Products/productsReducers.ts
- Dead file (~31 LoC) Distributed-eStore.UI/src/ClientApp/src/services/api/products.ts
- Dead file (~25 LoC) Distributed-eStore.UI/src/ClientApp/src/state/Products/productsTypes.ts
- Dead file (~13 LoC) Distributed-eStore.UI/src/ClientApp/src/components/routing/PrivateRoute.jsx
- Dead file (~3 LoC) Distributed-eStore.UI/src/ClientApp/src/state/Products/index.ts
- Dead file (~2 LoC) Distributed-eStore.UI/src/ClientApp/src/containers/index.tsx
- Dead file (~1 LoC) Distributed-eStore.UI/src/ClientApp/src/services/api/index.ts
- Unused dependency '@fortawesome/fontawesome-free'
- Unused dependency '@reduxjs/toolkit'
- Unused dependency 'merge'
- NuGet dependencies are not locked
- async void method: SeedProductsAsync Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:11
- Sync-over-async (deadlock risk) through `.Result` Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:19
Minor — 120 finding(s)
- Orphaned file Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:1
- Orphaned file Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:1
- Orphaned file Distributed-eStore.Common/RabbitMq/Extensions.cs:1
- Orphaned file Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:1
- Orphaned file Distributed-eStore.Common/Consul/Extensions.cs:1
- Orphaned file Distributed-eStore.Common/Mvc/Extensions.cs:1
- Orphaned file Distributed-eStore.Services.Identity/src/Services/IdentityService.cs:1
- Orphaned file Distributed-eStore.Common/Authentication/JwtHandler.cs:1
- Orphaned file Distributed-eStore.Services.Identity/src/Services/RefreshTokenService.cs:1
- Orphaned file Distributed-eStore.Common/RestEase/Extensions.cs:1
- Orphaned file Distributed-eStore.UI/src/Controllers/BaseController.cs:1
- Orphaned file Distributed-eStore.Common/Consul/ConsulServiceDiscoveryMessageHandler.cs:1
- Orphaned file Distributed-eStore.Common/Mvc/JsonParser.cs:1
- Orphaned file Distributed-eStore.Common/RestEase/QueryParamSerializer.cs:1
- Orphaned file Distributed-eStore.UI/src/Startup.cs:1
- Orphaned file Distributed-eStore.Services.Identity/src/Startup.cs:1
- Orphaned file Distributed-eStore.Api.Gateway/src/Startup.cs:1
- Orphaned file Distributed-eStore.Services.Product/src/Startup.cs:1
- Orphaned file Distributed-eStore.Services.Order/src/Startup.cs:1
- Orphaned file Distributed-eStore.Services.Identity/src/Domain/User.cs:1
- Orphaned file Distributed-eStore.Common/RabbitMq/CorrelationContext.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:79
- Outdated: Microsoft.AspNetCore.Authentication.OpenIdConnect REDACTED:12
- Outdated: Swashbuckle.AspNetCore REDACTED:14
- Outdated: Autofac REDACTED:8
- Outdated: Autofac.Extensions.DependencyInjection REDACTED:11
- Outdated: Microsoft.AspNetCore.Authorization REDACTED:80
- Outdated: Microsoft.Extensions.Configuration.Binder REDACTED:38
- Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables REDACTED:41
- Outdated: Microsoft.Extensions.Configuration.FileExtensions REDACTED:44
- Outdated: Microsoft.Extensions.Configuration.Json REDACTED:47
- Outdated: Microsoft.Extensions.DependencyInjection REDACTED:50
- Outdated: Microsoft.Extensions.Http REDACTED:53
- Outdated: System.IdentityModel.Tokens.Jwt REDACTED:76
- Outdated: Microsoft.AspNetCore.SpaServices.Extensions Distributed-eStore.UI/src/Distributed-eStore.UI.csproj:14
- Outdated: Microsoft.TypeScript.MSBuild Distributed-eStore.UI/src/Distributed-eStore.UI.csproj:15
- Primitive id on a domain type: RefreshToken.UserId Distributed-eStore.Services.Identity/src/Domain/RefreshToken.cs:10
- Primitive id on a domain type: AccessTokenRefreshed.UserId Distributed-eStore.Services.Identity/src/Messages/Events/AccessTokenRefreshed.cs:9
- Primitive id on a domain type: AccessTokenRevoked.UserId Distributed-eStore.Services.Identity/src/Messages/Events/AccessTokenRevoked.cs:9
- Primitive id on a domain type: PasswordChanged.UserId Distributed-eStore.Services.Identity/src/Messages/Events/PasswordChanged.cs:9
- Primitive id on a domain type: RefreshAccessTokenRejected.UserId Distributed-eStore.Services.Identity/src/Messages/Events/RefreshAccessTokenRejected.cs:9
- Primitive id on a domain type: RefreshTokenRevoked.UserId Distributed-eStore.Services.Identity/src/Messages/Events/RefreshTokenRevoked.cs:9
- Primitive id on a domain type: RevokeAccessTokenRejected.UserId Distributed-eStore.Services.Identity/src/Messages/Events/RevokeAccessTokenRejected.cs:9
- Primitive id on a domain type: RevokeRefreshTokenRejected.UserId Distributed-eStore.Services.Identity/src/Messages/Events/RevokeRefreshTokenRejected.cs:9
- Primitive id on a domain type: SignedIn.UserId Distributed-eStore.Services.Identity/src/Messages/Events/SignedIn.cs:9
- Primitive id on a domain type: SignedUp.UserId Distributed-eStore.Services.Identity/src/Messages/Events/SignedUp.cs:9
- Primitive id on a domain type: SignUpRejected.UserId Distributed-eStore.Services.Identity/src/Messages/Events/SignUpRejected.cs:9
- Primitive id on a domain type: Order.CustomerId Distributed-eStore.Services.Order/src/DomainEntities/Order.cs:8
- Primitive id on a domain type: OrderItem.ProductId Distributed-eStore.Services.Order/src/DomainEntities/OrderItem.cs:8
- No security response headers detected
- No security response headers detected Distributed-eStore.Api.Gateway/src/Program.cs:12
- No security response headers detected Distributed-eStore.Api.Gateway/src/Program.cs:25
- No security response headers detected Distributed-eStore.Services.Identity/src/Program.cs:12
- No security response headers detected Distributed-eStore.Services.Identity/src/Program.cs:25
- No security response headers detected Distributed-eStore.Services.Order/src/Program.cs:12
- No security response headers detected Distributed-eStore.Services.Order/src/Program.cs:25
- No security response headers detected Distributed-eStore.Services.Product/src/Program.cs:12
- No security response headers detected Distributed-eStore.Services.Product/src/Program.cs:25
- No security response headers detected Distributed-eStore.UI/src/Program.cs:14
- Interpolated log message defeats structured logging REDACTED:31
- Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:116
- Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:117
- Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:124
- Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:150
- Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:156
- Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:163
- Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:168
- Interpolated log message defeats structured logging Distributed-eStore.Common/RabbitMq/BusSubscriber.cs:184
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Commented-out code Distributed-eStore.Common/RestEase/QueryParamSerializer.cs:68
- Commented-out code Distributed-eStore.Services.Identity/src/Startup.cs:66
- Commented-out code Distributed-eStore.Services.Order/src/Handlers/BrowseOrdersHandler.cs:22
- Duplicated predicate Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:50
- Duplicated predicate Distributed-eStore.UI/src/ClientApp/src/state/cart/cartActions.ts:42
- Duplicated predicate Distributed-eStore.Api.Gateway/src/Controllers/BaseController.cs:116
- Documentation: no build, run or usage example README.md:1
- Documentation: no map of the repository's parts README.md:1
- Accessibility enforcement below the top rung REDACTED:41
- Partial data-retention evidence
- No ADRs found
- `IsCurrentActiveToken` returns an awaitable but lacks the `Async` suffix its 35 peers carry Distributed-eStore.Common/Authentication/IAccessTokenService.cs:7
- `Invoke` returns an awaitable but lacks the `Async` suffix its 35 peers carry REDACTED:23
- Pass-through layer Distributed-eStore.Services.Order/src/Repositories/OrdersRepository.cs:8
- REDACTED
- Dormant codebase
- IL efficiency: 1 authored method(s) exceed the IL budget Distributed-eStore.Services.Product/src/Seed/ProductsSeeder.cs:30
- No ADRs
- Logging is not universal
- No SAST
- No dependency-update automation Distributed-eStore.Api.Gateway/src/Distributed-eStore.Api.Gateway.csproj:12
- No rollback/health safety
- No changelog
- Unused export 'unregister' Distributed-eStore.UI/src/ClientApp/src/registerServiceWorker.ts:99
- Not all async methods take a CancellationToken
- Nullable reference types not enabled everywhere
Minor — 17 finding(s)
- Outdated: Microsoft.VisualStudio.Azure.Containers.Tools.Targets
- Outdated: OpenTracing.Contrib.NetCore
- Outdated: Consul
- Outdated: Jaeger
- Outdated: Microsoft.AspNetCore
- Outdated: Microsoft.AspNetCore.Authentication
- Outdated: Microsoft.AspNetCore.Hosting
- Outdated: Microsoft.AspNetCore.Identity
- Outdated: Microsoft.AspNetCore.Mvc
- Outdated: Microsoft.AspNetCore.Mvc.Core
- Outdated: Microsoft.AspNetCore.Mvc.DataAnnotations
- Outdated: Microsoft.AspNetCore.Server.Kestrel
- Outdated: Microsoft.AspNetCore.StaticFiles
- Outdated: Microsoft.NETCore.UniversalWindowsPlatform
- Outdated: MongoDB.Driver
- Outdated: Polly
- Outdated: RestEase
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-4542eb5eda7a4685b6a30e1079e466e0/history.json --exit-code 0 --source . | 4 | 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-4542eb5eda7a4685b6a30e1079e466e0/tree.json --exit-code 0 --source . | 4 | 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 . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Distributed-eStore.sln package --vulnerable --include-transitive --format json | 129 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 48 | 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 . | 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
Appendix C — Personal-data map
Email — 5 field(s)
- SignInCommand.Email Distributed-eStore.Common/Commands/Identity/SignInCommand.cs:5
- SignUpCommand.Email Distributed-eStore.Common/Commands/Identity/SignUpCommand.cs:8
- User.Email Distributed-eStore.Services.Identity/src/Domain/User.cs:16
- SignInRejected.Email Distributed-eStore.Services.Identity/src/Messages/Events/SignInRejected.cs:9
- SignedUp.Email Distributed-eStore.Services.Identity/src/Messages/Events/SignedUp.cs:10
Name — 4 field(s)
- SignUpCommand.FirstName Distributed-eStore.Common/Commands/Identity/SignUpCommand.cs:9
- SignUpCommand.LastName Distributed-eStore.Common/Commands/Identity/SignUpCommand.cs:10
- User.FirstName Distributed-eStore.Services.Identity/src/Domain/User.cs:17
- User.LastName Distributed-eStore.Services.Identity/src/Domain/User.cs:18