Executive summary
DavidEggenberger/ModularMonolith.SaaS.Template is rated At risk because critical security findings are open. Its score is held back in part because the project has no automated tests. It scores 36 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Production Readiness, at 27, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 7 points. Fixing the password or key in the code comes next, worth about 6 points. Raising Production Readiness to 52 would lift the score to about 42.
Five known security holes in the packages the code depends on can be used by attackers. Four weaknesses in the code could be used by an attacker, and three passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Replacing each exposed password or key, updating the vulnerable packages and fixing the weaknesses the scanner points to would close these risks. Pinning each tool to an exact version would fix the three pipeline tools referenced by a changeable name, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The 40 pieces of business logic tied to the database or web code need separating from the database and web code.
The product code is 4,256 lines, about €5,200 to rebuild.
If Production Readiness rose from 27 to 52, the lowest score rated Strong, the score would rise from 36 to about 42.
New since the last survey: 2 findings
- Static Analysis (SAST) · REDACTED
- Rich vs anemic model · Anemic entity: TenantMembership Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs
Fixed since the last survey: 74 findings
- Dependency Hygiene · Vulnerable: Microsoft.AspNetCore.Components.WebAssembly.Server
- Static Analysis (SAST) · Medium: watchdog-eol-dotnet-runtime-in-workflow REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net9.0 REDACTED
- Cancellation propagation · Async method without CancellationToken: OnGet Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs
- Cancellation propagation · Async method drops its CancellationToken: HandleAsync Source/Modules/Subscriptions/Features/Infrastructure/StripePayments/CreateStripeBillingPortalSession.cs
- Cancellation propagation · Async method drops its CancellationToken: HandleAsync Source/Modules/Subscriptions/Features/Infrastructure/StripePayments/CreateStripeCheckoutSession.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/UpdateTenantMembership.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/UpdateTenantMembership.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/UpdateTenantMembership.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/IntegrationMessageHandlers/TenantSubscriptionUpdatedIntegrationEventHandler.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/IntegrationMessageHandlers/TenantSubscriptionUpdatedIntegrationEventHandler.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetAllTenantMembershipsOfUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetAllTenantMembershipsOfUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetAllTenantMembershipsOfUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetTenant.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetTenant.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetTenant.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantInvitation.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/SelectTenant.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/SelectTenant.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/SelectTenant.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/UpdateUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetClaimsForExecutingUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetClaimsForExecutingUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetClaimsForExecutingUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetExecutingUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Misc Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetExecutingUser.cs
- Slice cohesion · Cross-slice coupling: DomainFeatures → Messaging Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetExecutingUser.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → Misc Source/Modules/TenantIdentity/Features/Infrastructure/Configuration/TenantIdentityConfiguration.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → Misc Source/Modules/TenantIdentity/Features/Infrastructure/Configuration/TenantIdentityConfigurationValidator.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → DomainFeatures Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → DomainFeatures Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → DomainFeatures Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → DomainFeatures Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → Misc Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → EFCore Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → EFCore Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → Misc Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → Misc Source/Modules/TenantIdentity/Features/Infrastructure/UserClaimsPrincipalFactory.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → DomainFeatures Source/Modules/TenantIdentity/Features/Infrastructure/UserClaimsPrincipalFactory.cs
- Slice cohesion · Cross-slice coupling: Infrastructure → DomainFeatures Source/Modules/TenantIdentity/Features/Infrastructure/UserClaimsPrincipalFactory.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/BaseDbContext.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/BaseDbContext.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/Configuration/EFCoreConfiguration.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/Configuration/EFCoreConfigurationValidator.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/DbSetExtensions.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/DbSetExtensions.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/DbUp/Registrator.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/ExecutionContextInterceptor.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/ExecutionContextInterceptor.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/ExecutionContextInterceptor.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/MultiTenancy/MultiTenancyEntityConfiguration.cs
- Slice cohesion · Cross-slice coupling: EFCore → Misc Source/Shared/Features/EFCore/Registrator.cs
- Slice cohesion · Cross-slice coupling: Messaging → Misc Source/Shared/Features/Messaging/Queries/QueryDispatcher.cs
- Slice cohesion · Cross-slice coupling: Misc → Messaging Source/Shared/Features/Misc/BaseController.cs
- Slice cohesion · Cross-slice coupling: Misc → Messaging Source/Shared/Features/Misc/BaseController.cs
- Slice cohesion · Cross-slice coupling: Misc → Messaging Source/Shared/Features/Misc/BaseController.cs
- Slice cohesion · Cross-slice coupling: Misc → Messaging Source/Shared/Features/Misc/ExecutionContext/ServerExecutionBase.cs
- Slice cohesion · Cross-slice coupling: Misc → Messaging Source/Shared/Features/Misc/ExecutionContext/ServerExecutionBase.cs
- Slice cohesion · Cross-slice coupling: Misc → Messaging Source/Shared/Features/Misc/ExecutionContext/ServerExecutionBase.cs
- Slice cohesion · Cross-slice coupling: Misc → SignalR Source/Shared/Features/Misc/ExecutionContext/ServerExecutionBase.cs
- Slice cohesion · Cross-slice coupling: Misc → Messaging Source/Shared/Features/Misc/Modules/Registrator.cs
- Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: GetAllTenantMembershipsOfUserQueryHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetAllTenantMembershipsOfUser.cs
- Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: GetTenantByIdQueryHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetTenant.cs
- Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: SelectedTenantCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/SelectTenant.cs
- Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: ClaimsForUserQueryHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetClaimsForExecutingUser.cs
- Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: CreateTrialingSubscriptionCommandHandler Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/CreateTrialingSubscription.cs
- Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: PauseActiveSubscriptionCommandHandler Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/PauseActiveSubscription.cs
- Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: UpdateSubscriptionPerioEndCommandHandler Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/UpdateSubscriptionPeriod.cs
Rebuild cost: about €5,200 · Estimate
| Cost to rebuild | €1,800 to €8,600, for 29 to 91 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 36. 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: 4,256 lines of product code, of which 48% is declarations and boilerplate, 44% straight logic and 9% logic with branches |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Shared.Features.Messaging.Commands | 2 Shared.Features.Messaging.IntegrationMessages | 3 Shared.Features.Messaging.Queries | 4 Shared.Features.Misc.Configuration | 5 Shared.Features.Misc.Modules | 6 Shared.Kernel.BuildingBlocks | 7 Shared.Kernel.DomainKernel | 8 Shared.Kernel.DomainKernel.Interfaces | 9 Modules.LandingPages.Web | 10 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Queries | 11 Modules.Subscriptions.Public.IntegrationMessages | 12 Modules.TenantIdentity.Features.Infrastructure.Configuration | 13 Modules.TenantIdentity.Public.DTOs.Tenant | 14 Modules.TenantIdentity.Public.DTOs.Tenant.Operations | 15 Modules.TenantIdentity.Public.IntegrationMessages | 16 Shared.Features.EFCore.Configuration | 17 Shared.Features.Misc.ExecutionContext | 18 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands | 19 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands | 20 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers | 21 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries | 22 Shared.Features.EFCore | 23 Shared.Features.Misc | 24 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers | 25 Modules.Subscriptions.Web.Server.Controllers | 26 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain | 27 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions | 28 Modules.TenantIdentity.Features.DomainFeatures.Users | 29 Modules.Subscriptions.Features.Infrastructure.EFCore | 30 Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands | 31 Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries | 32 Modules.TenantIdentity.Features.Infrastructure.EFCore | 33 Modules.TenantIdentity.Web.Server.Controllers | 34 Modules.TenantIdentity.Web.Server.Controllers.Infrastructure | 35 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers | 36 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries | 37 Modules.Subscriptions.Features.Infrastructure.StripePayments | 38 Modules.TenantIdentity.Features | 39 Modules.Subscriptions.Features.Infrastructure.Configuration | 40 Modules.Subscriptions.Features |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Shared.Features.Messaging.Commands | ||||||||||||||||||||||||||||||||||||||||
| 2 Shared.Features.Messaging.IntegrationMessages | ||||||||||||||||||||||||||||||||||||||||
| 3 Shared.Features.Messaging.Queries | ||||||||||||||||||||||||||||||||||||||||
| 4 Shared.Features.Misc.Configuration | ||||||||||||||||||||||||||||||||||||||||
| 5 Shared.Features.Misc.Modules | ||||||||||||||||||||||||||||||||||||||||
| 6 Shared.Kernel.BuildingBlocks | ||||||||||||||||||||||||||||||||||||||||
| 7 Shared.Kernel.DomainKernel | ||||||||||||||||||||||||||||||||||||||||
| 8 Shared.Kernel.DomainKernel.Interfaces | ||||||||||||||||||||||||||||||||||||||||
| 9 Modules.LandingPages.Web | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Queries | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Modules.Subscriptions.Public.IntegrationMessages | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Modules.TenantIdentity.Features.Infrastructure.Configuration | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 Modules.TenantIdentity.Public.DTOs.Tenant | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 Modules.TenantIdentity.Public.DTOs.Tenant.Operations | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 Modules.TenantIdentity.Public.IntegrationMessages | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 Shared.Features.EFCore.Configuration | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 Shared.Features.Misc.ExecutionContext | 4 | |||||||||||||||||||||||||||||||||||||||
| 18 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands | 6 | 3 | ||||||||||||||||||||||||||||||||||||||
| 19 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands | 10 | 2 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 20 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries | 4 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 Shared.Features.EFCore | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 Shared.Features.Misc | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Modules.Subscriptions.Web.Server.Controllers | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 26 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain | 4 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 27 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 Modules.TenantIdentity.Features.DomainFeatures.Users | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Modules.Subscriptions.Features.Infrastructure.EFCore | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands | 5 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 Modules.TenantIdentity.Features.Infrastructure.EFCore | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Modules.TenantIdentity.Web.Server.Controllers | 1 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 Modules.TenantIdentity.Web.Server.Controllers.Infrastructure | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 Modules.Subscriptions.Features.Infrastructure.StripePayments | 4 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 Modules.TenantIdentity.Features | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 Modules.Subscriptions.Features.Infrastructure.Configuration | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 Modules.Subscriptions.Features | 1 | 1 | 1 |
9→5 Modules.LandingPages.Web uses Shared.Features.Misc.Modules✕
- Connections
- 1 pair of types, where a type in Modules.LandingPages.Web uses a type in Shared.Features.Misc.Modules.
- The types involved
Modules.LandingPages.Web.LandingPagesModuleStartup→Shared.Features.Misc.Modules.IModuleStartup
- Direction
- Modules.LandingPages.Web uses Shared.Features.Misc.Modules, so a change to Shared.Features.Misc.Modules can break Modules.LandingPages.Web, while a change to Modules.LandingPages.Web can't break Shared.Features.Misc.Modules.
- Position
- Below the diagonal: Modules.LandingPages.Web uses a module listed above it, which is the healthy direction.
10→3 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Queries uses Shared.Features.Messaging.Queries✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Queries uses a type in Shared.Features.Messaging.Queries.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Queries.GetSubscriptionForTenant→Shared.Features.Messaging.Queries.Query
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Queries uses Shared.Features.Messaging.Queries, so a change to Shared.Features.Messaging.Queries can break Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Queries, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Queries can't break Shared.Features.Messaging.Queries.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Queries uses a module listed above it, which is the healthy direction.
11→6 Modules.Subscriptions.Public.IntegrationMessages uses Shared.Kernel.BuildingBlocks✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Public.IntegrationMessages uses a type in Shared.Kernel.BuildingBlocks.
- The types involved
Modules.Subscriptions.Public.IntegrationMessages.TenantSubscriptionPlanUpdatedEvent→Shared.Kernel.BuildingBlocks.IIntegrationEvent
- Direction
- Modules.Subscriptions.Public.IntegrationMessages uses Shared.Kernel.BuildingBlocks, so a change to Shared.Kernel.BuildingBlocks can break Modules.Subscriptions.Public.IntegrationMessages, while a change to Modules.Subscriptions.Public.IntegrationMessages can't break Shared.Kernel.BuildingBlocks.
- Position
- Below the diagonal: Modules.Subscriptions.Public.IntegrationMessages uses a module listed above it, which is the healthy direction.
11→7 Modules.Subscriptions.Public.IntegrationMessages uses Shared.Kernel.DomainKernel✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Public.IntegrationMessages uses a type in Shared.Kernel.DomainKernel.
- The types involved
Modules.Subscriptions.Public.IntegrationMessages.TenantSubscriptionPlanUpdatedEvent→Shared.Kernel.DomainKernel.SubscriptionPlanType
- Direction
- Modules.Subscriptions.Public.IntegrationMessages uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Modules.Subscriptions.Public.IntegrationMessages, while a change to Modules.Subscriptions.Public.IntegrationMessages can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Modules.Subscriptions.Public.IntegrationMessages uses a module listed above it, which is the healthy direction.
12→4 Modules.TenantIdentity.Features.Infrastructure.Configuration uses Shared.Features.Misc.Configuration✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Features.Infrastructure.Configuration uses a type in Shared.Features.Misc.Configuration.
- The types involved
Modules.TenantIdentity.Features.Infrastructure.Configuration.TenantIdentityConfiguration→Shared.Features.Misc.Configuration.ConfigurationObjectModules.TenantIdentity.Features.Infrastructure.Configuration.TenantIdentityConfigurationValidator→Shared.Features.Misc.Configuration.ConfigurationObjectValidator
- Direction
- Modules.TenantIdentity.Features.Infrastructure.Configuration uses Shared.Features.Misc.Configuration, so a change to Shared.Features.Misc.Configuration can break Modules.TenantIdentity.Features.Infrastructure.Configuration, while a change to Modules.TenantIdentity.Features.Infrastructure.Configuration can't break Shared.Features.Misc.Configuration.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.Infrastructure.Configuration uses a module listed above it, which is the healthy direction.
13→7 Modules.TenantIdentity.Public.DTOs.Tenant uses Shared.Kernel.DomainKernel✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Public.DTOs.Tenant uses a type in Shared.Kernel.DomainKernel.
- The types involved
Modules.TenantIdentity.Public.DTOs.Tenant.TenantDTO→Shared.Kernel.DomainKernel.SubscriptionPlanTypeModules.TenantIdentity.Public.DTOs.Tenant.TenantMembershipDTO→Shared.Kernel.DomainKernel.TenantRole
- Direction
- Modules.TenantIdentity.Public.DTOs.Tenant uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Modules.TenantIdentity.Public.DTOs.Tenant, while a change to Modules.TenantIdentity.Public.DTOs.Tenant can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Modules.TenantIdentity.Public.DTOs.Tenant uses a module listed above it, which is the healthy direction.
14→7 Modules.TenantIdentity.Public.DTOs.Tenant.Operations uses Shared.Kernel.DomainKernel✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Public.DTOs.Tenant.Operations uses a type in Shared.Kernel.DomainKernel.
- The types involved
Modules.TenantIdentity.Public.DTOs.Tenant.Operations.ChangeRoleOfTenantMemberDTO→Shared.Kernel.DomainKernel.TenantRoleModules.TenantIdentity.Public.DTOs.Tenant.Operations.InviteUserToTenantDTO→Shared.Kernel.DomainKernel.TenantRole
- Direction
- Modules.TenantIdentity.Public.DTOs.Tenant.Operations uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Modules.TenantIdentity.Public.DTOs.Tenant.Operations, while a change to Modules.TenantIdentity.Public.DTOs.Tenant.Operations can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Modules.TenantIdentity.Public.DTOs.Tenant.Operations uses a module listed above it, which is the healthy direction.
15→6 Modules.TenantIdentity.Public.IntegrationMessages uses Shared.Kernel.BuildingBlocks✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Public.IntegrationMessages uses a type in Shared.Kernel.BuildingBlocks.
- The types involved
Modules.TenantIdentity.Public.IntegrationMessages.TenantAdminCreatedEvent→Shared.Kernel.BuildingBlocks.IIntegrationEventModules.TenantIdentity.Public.IntegrationMessages.TenantAdminEmailUpdatedEvent→Shared.Kernel.BuildingBlocks.IIntegrationEvent
- Direction
- Modules.TenantIdentity.Public.IntegrationMessages uses Shared.Kernel.BuildingBlocks, so a change to Shared.Kernel.BuildingBlocks can break Modules.TenantIdentity.Public.IntegrationMessages, while a change to Modules.TenantIdentity.Public.IntegrationMessages can't break Shared.Kernel.BuildingBlocks.
- Position
- Below the diagonal: Modules.TenantIdentity.Public.IntegrationMessages uses a module listed above it, which is the healthy direction.
16→4 Shared.Features.EFCore.Configuration uses Shared.Features.Misc.Configuration✕
- Connections
- 2 pairs of types, where a type in Shared.Features.EFCore.Configuration uses a type in Shared.Features.Misc.Configuration.
- The types involved
Shared.Features.EFCore.Configuration.EFCoreConfiguration→Shared.Features.Misc.Configuration.ConfigurationObjectShared.Features.EFCore.Configuration.EFCoreConfigurationValidator→Shared.Features.Misc.Configuration.ConfigurationObjectValidator
- Direction
- Shared.Features.EFCore.Configuration uses Shared.Features.Misc.Configuration, so a change to Shared.Features.Misc.Configuration can break Shared.Features.EFCore.Configuration, while a change to Shared.Features.EFCore.Configuration can't break Shared.Features.Misc.Configuration.
- Position
- Below the diagonal: Shared.Features.EFCore.Configuration uses a module listed above it, which is the healthy direction.
17→7 Shared.Features.Misc.ExecutionContext uses Shared.Kernel.DomainKernel✕
- Connections
- 4 pairs of types, where a type in Shared.Features.Misc.ExecutionContext uses a type in Shared.Kernel.DomainKernel.
- The types involved
Shared.Features.Misc.ExecutionContext.IExecutionContext→Shared.Kernel.DomainKernel.SubscriptionPlanTypeShared.Features.Misc.ExecutionContext.IExecutionContext→Shared.Kernel.DomainKernel.TenantRoleShared.Features.Misc.ExecutionContext.ServerExecutionContext→Shared.Kernel.DomainKernel.SubscriptionPlanTypeShared.Features.Misc.ExecutionContext.ServerExecutionContext→Shared.Kernel.DomainKernel.TenantRole
- Direction
- Shared.Features.Misc.ExecutionContext uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Shared.Features.Misc.ExecutionContext, while a change to Shared.Features.Misc.ExecutionContext can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Shared.Features.Misc.ExecutionContext uses a module listed above it, which is the healthy direction.
18→1 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands uses Shared.Features.Messaging.Commands✕
- Connections
- 6 pairs of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands uses a type in Shared.Features.Messaging.Commands.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands.CreateTrialingSubscription→Shared.Features.Messaging.Commands.CommandModules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands.CreateTrialingSubscriptionCommandHandler→Shared.Features.Messaging.Commands.ICommandHandlerModules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands.PauseActiveSubscription→Shared.Features.Messaging.Commands.CommandModules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands.PauseActiveSubscriptionCommandHandler→Shared.Features.Messaging.Commands.ICommandHandlerModules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands.UpdateSubscriptionPerioEndCommandHandler→Shared.Features.Messaging.Commands.ICommandHandlerModules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands.UpdateSubscriptionPeriod→Shared.Features.Messaging.Commands.Command
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands uses Shared.Features.Messaging.Commands, so a change to Shared.Features.Messaging.Commands can break Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands can't break Shared.Features.Messaging.Commands.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands uses a module listed above it, which is the healthy direction.
18→17 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands uses Shared.Features.Misc.ExecutionContext✕
- Connections
- 3 pairs of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands uses a type in Shared.Features.Misc.ExecutionContext.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands.CreateTrialingSubscriptionCommandHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBaseModules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands.PauseActiveSubscriptionCommandHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBaseModules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands.UpdateSubscriptionPerioEndCommandHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBase
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands uses Shared.Features.Misc.ExecutionContext, so a change to Shared.Features.Misc.ExecutionContext can break Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands can't break Shared.Features.Misc.ExecutionContext.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.Application.Commands uses a module listed above it, which is the healthy direction.
19→1 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses Shared.Features.Messaging.Commands✕
- Connections
- 10 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses a type in Shared.Features.Messaging.Commands.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.AddMemberToTenant→Shared.Features.Messaging.Commands.CommandModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.AddMemberToTenantCommandHandler→Shared.Features.Messaging.Commands.ICommandHandlerModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.CreateTenant→Shared.Features.Messaging.Commands.CommandModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.CreateTenantWithAdminCommandHandler→Shared.Features.Messaging.Commands.ICommandHandlerModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.DeleteTenant→Shared.Features.Messaging.Commands.CommandModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.DeleteTenantCommandHandler→Shared.Features.Messaging.Commands.ICommandHandlerModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.RemoveMemberFromTenant→Shared.Features.Messaging.Commands.CommandModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.RemoveMemberFromTenantCommandHandler→Shared.Features.Messaging.Commands.ICommandHandlerModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.UpdateTenantMembership→Shared.Features.Messaging.Commands.CommandModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.UpdateTenantMembershipCommandHandler→Shared.Features.Messaging.Commands.ICommandHandler
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses Shared.Features.Messaging.Commands, so a change to Shared.Features.Messaging.Commands can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands can't break Shared.Features.Messaging.Commands.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses a module listed above it, which is the healthy direction.
19→7 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses Shared.Kernel.DomainKernel✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses a type in Shared.Kernel.DomainKernel.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.AddMemberToTenant→Shared.Kernel.DomainKernel.TenantRoleModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.UpdateTenantMembership→Shared.Kernel.DomainKernel.TenantRole
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses a module listed above it, which is the healthy direction.
19→13 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses Modules.TenantIdentity.Public.DTOs.Tenant✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses a type in Modules.TenantIdentity.Public.DTOs.Tenant.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.CreateTenantWithAdminCommandHandler→Modules.TenantIdentity.Public.DTOs.Tenant.TenantDTO
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses Modules.TenantIdentity.Public.DTOs.Tenant, so a change to Modules.TenantIdentity.Public.DTOs.Tenant can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands can't break Modules.TenantIdentity.Public.DTOs.Tenant.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses a module listed above it, which is the healthy direction.
19→17 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses Shared.Features.Misc.ExecutionContext✕
- Connections
- 5 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses a type in Shared.Features.Misc.ExecutionContext.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.AddMemberToTenantCommandHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBaseModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.CreateTenantWithAdminCommandHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBaseModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.DeleteTenantCommandHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBaseModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.RemoveMemberFromTenantCommandHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBaseModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands.UpdateTenantMembershipCommandHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBase
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses Shared.Features.Misc.ExecutionContext, so a change to Shared.Features.Misc.ExecutionContext can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands can't break Shared.Features.Misc.ExecutionContext.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Commands uses a module listed above it, which is the healthy direction.
20→2 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses Shared.Features.Messaging.IntegrationMessages✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses a type in Shared.Features.Messaging.IntegrationMessages.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers.TenantSubscriptionUpdatedIntegrationEventHandler→Shared.Features.Messaging.IntegrationMessages.IIntegrationEventHandler
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses Shared.Features.Messaging.IntegrationMessages, so a change to Shared.Features.Messaging.IntegrationMessages can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers can't break Shared.Features.Messaging.IntegrationMessages.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses a module listed above it, which is the healthy direction.
20→11 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses Modules.Subscriptions.Public.IntegrationMessages✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses a type in Modules.Subscriptions.Public.IntegrationMessages.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers.TenantSubscriptionUpdatedIntegrationEventHandler→Modules.Subscriptions.Public.IntegrationMessages.TenantSubscriptionPlanUpdatedEvent
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses Modules.Subscriptions.Public.IntegrationMessages, so a change to Modules.Subscriptions.Public.IntegrationMessages can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers can't break Modules.Subscriptions.Public.IntegrationMessages.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses a module listed above it, which is the healthy direction.
20→17 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses Shared.Features.Misc.ExecutionContext✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses a type in Shared.Features.Misc.ExecutionContext.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers.TenantSubscriptionUpdatedIntegrationEventHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBase
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses Shared.Features.Misc.ExecutionContext, so a change to Shared.Features.Misc.ExecutionContext can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers can't break Shared.Features.Misc.ExecutionContext.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.IntegrationMessageHandlers uses a module listed above it, which is the healthy direction.
21→3 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses Shared.Features.Messaging.Queries✕
- Connections
- 4 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses a type in Shared.Features.Messaging.Queries.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries.GetAllTenantMembershipsOfUser→Shared.Features.Messaging.Queries.QueryModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries.GetAllTenantMembershipsOfUserQueryHandler→Shared.Features.Messaging.Queries.IQueryHandlerModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries.GetTenant→Shared.Features.Messaging.Queries.QueryModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries.GetTenantByIdQueryHandler→Shared.Features.Messaging.Queries.IQueryHandler
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses Shared.Features.Messaging.Queries, so a change to Shared.Features.Messaging.Queries can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries can't break Shared.Features.Messaging.Queries.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses a module listed above it, which is the healthy direction.
21→13 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses Modules.TenantIdentity.Public.DTOs.Tenant✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses a type in Modules.TenantIdentity.Public.DTOs.Tenant.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries.GetAllTenantMembershipsOfUserQueryHandler→Modules.TenantIdentity.Public.DTOs.Tenant.TenantMembershipDTOModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries.GetTenantByIdQueryHandler→Modules.TenantIdentity.Public.DTOs.Tenant.TenantDTO
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses Modules.TenantIdentity.Public.DTOs.Tenant, so a change to Modules.TenantIdentity.Public.DTOs.Tenant can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries can't break Modules.TenantIdentity.Public.DTOs.Tenant.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses a module listed above it, which is the healthy direction.
21→17 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses Shared.Features.Misc.ExecutionContext✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses a type in Shared.Features.Misc.ExecutionContext.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries.GetAllTenantMembershipsOfUserQueryHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBaseModules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries.GetTenantByIdQueryHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBase
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses Shared.Features.Misc.ExecutionContext, so a change to Shared.Features.Misc.ExecutionContext can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries can't break Shared.Features.Misc.ExecutionContext.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Application.Queries uses a module listed above it, which is the healthy direction.
22→16 Shared.Features.EFCore uses Shared.Features.EFCore.Configuration✕
- Connections
- 1 pair of types, where a type in Shared.Features.EFCore uses a type in Shared.Features.EFCore.Configuration.
- The types involved
Shared.Features.EFCore.BaseDbContext→Shared.Features.EFCore.Configuration.EFCoreConfiguration
- Direction
- Shared.Features.EFCore uses Shared.Features.EFCore.Configuration, so a change to Shared.Features.EFCore.Configuration can break Shared.Features.EFCore, while a change to Shared.Features.EFCore can't break Shared.Features.EFCore.Configuration.
- Position
- Below the diagonal: Shared.Features.EFCore uses a module listed above it, which is the healthy direction.
22→17 Shared.Features.EFCore uses Shared.Features.Misc.ExecutionContext✕
- Connections
- 1 pair of types, where a type in Shared.Features.EFCore uses a type in Shared.Features.Misc.ExecutionContext.
- The types involved
Shared.Features.EFCore.BaseDbContext→Shared.Features.Misc.ExecutionContext.IExecutionContext
- Direction
- Shared.Features.EFCore uses Shared.Features.Misc.ExecutionContext, so a change to Shared.Features.Misc.ExecutionContext can break Shared.Features.EFCore, while a change to Shared.Features.EFCore can't break Shared.Features.Misc.ExecutionContext.
- Position
- Below the diagonal: Shared.Features.EFCore uses a module listed above it, which is the healthy direction.
23→7 Shared.Features.Misc uses Shared.Kernel.DomainKernel✕
- Connections
- 1 pair of types, where a type in Shared.Features.Misc uses a type in Shared.Kernel.DomainKernel.
- The types involved
Shared.Features.Misc.Entity→Shared.Kernel.DomainKernel.TenantRole
- Direction
- Shared.Features.Misc uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Shared.Features.Misc, while a change to Shared.Features.Misc can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Shared.Features.Misc uses a module listed above it, which is the healthy direction.
23→8 Shared.Features.Misc uses Shared.Kernel.DomainKernel.Interfaces✕
- Connections
- 3 pairs of types, where a type in Shared.Features.Misc uses a type in Shared.Kernel.DomainKernel.Interfaces.
- The types involved
Shared.Features.Misc.Entity→Shared.Kernel.DomainKernel.Interfaces.IAuditableShared.Features.Misc.Entity→Shared.Kernel.DomainKernel.Interfaces.IConcurrentShared.Features.Misc.Entity→Shared.Kernel.DomainKernel.Interfaces.IIdentifiable
- Direction
- Shared.Features.Misc uses Shared.Kernel.DomainKernel.Interfaces, so a change to Shared.Kernel.DomainKernel.Interfaces can break Shared.Features.Misc, while a change to Shared.Features.Misc can't break Shared.Kernel.DomainKernel.Interfaces.
- Position
- Below the diagonal: Shared.Features.Misc uses a module listed above it, which is the healthy direction.
23→17 Shared.Features.Misc uses Shared.Features.Misc.ExecutionContext✕
- Connections
- 1 pair of types, where a type in Shared.Features.Misc uses a type in Shared.Features.Misc.ExecutionContext.
- The types involved
Shared.Features.Misc.Entity→Shared.Features.Misc.ExecutionContext.IExecutionContext
- Direction
- Shared.Features.Misc uses Shared.Features.Misc.ExecutionContext, so a change to Shared.Features.Misc.ExecutionContext can break Shared.Features.Misc, while a change to Shared.Features.Misc can't break Shared.Features.Misc.ExecutionContext.
- Position
- Below the diagonal: Shared.Features.Misc uses a module listed above it, which is the healthy direction.
24→23 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers uses Shared.Features.Misc✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeCustomers uses a type in Shared.Features.Misc.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.StripeCustomer→Shared.Features.Misc.Entity
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeCustomers uses Shared.Features.Misc, so a change to Shared.Features.Misc can break Modules.Subscriptions.Features.DomainFeatures.StripeCustomers, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeCustomers can't break Shared.Features.Misc.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeCustomers uses a module listed above it, which is the healthy direction.
25→7 Modules.Subscriptions.Web.Server.Controllers uses Shared.Kernel.DomainKernel✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Web.Server.Controllers uses a type in Shared.Kernel.DomainKernel.
- The types involved
Modules.Subscriptions.Web.Server.Controllers.StripeSessionController→Shared.Kernel.DomainKernel.SubscriptionPlanType
- Direction
- Modules.Subscriptions.Web.Server.Controllers uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Modules.Subscriptions.Web.Server.Controllers, while a change to Modules.Subscriptions.Web.Server.Controllers can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Modules.Subscriptions.Web.Server.Controllers uses a module listed above it, which is the healthy direction.
25→8 Modules.Subscriptions.Web.Server.Controllers uses Shared.Kernel.DomainKernel.Interfaces✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Web.Server.Controllers uses a type in Shared.Kernel.DomainKernel.Interfaces.
- The types involved
Modules.Subscriptions.Web.Server.Controllers.StripeSuccessController→Shared.Kernel.DomainKernel.Interfaces.IApplicationUser
- Direction
- Modules.Subscriptions.Web.Server.Controllers uses Shared.Kernel.DomainKernel.Interfaces, so a change to Shared.Kernel.DomainKernel.Interfaces can break Modules.Subscriptions.Web.Server.Controllers, while a change to Modules.Subscriptions.Web.Server.Controllers can't break Shared.Kernel.DomainKernel.Interfaces.
- Position
- Below the diagonal: Modules.Subscriptions.Web.Server.Controllers uses a module listed above it, which is the healthy direction.
25→23 Modules.Subscriptions.Web.Server.Controllers uses Shared.Features.Misc✕
- Connections
- 3 pairs of types, where a type in Modules.Subscriptions.Web.Server.Controllers uses a type in Shared.Features.Misc.
- The types involved
Modules.Subscriptions.Web.Server.Controllers.StripeSessionController→Shared.Features.Misc.BaseControllerModules.Subscriptions.Web.Server.Controllers.StripeSubscriptionsController→Shared.Features.Misc.BaseControllerModules.Subscriptions.Web.Server.Controllers.StripeSuccessController→Shared.Features.Misc.BaseController
- Direction
- Modules.Subscriptions.Web.Server.Controllers uses Shared.Features.Misc, so a change to Shared.Features.Misc can break Modules.Subscriptions.Web.Server.Controllers, while a change to Modules.Subscriptions.Web.Server.Controllers can't break Shared.Features.Misc.
- Position
- Below the diagonal: Modules.Subscriptions.Web.Server.Controllers uses a module listed above it, which is the healthy direction.
26→7 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses Shared.Kernel.DomainKernel✕
- Connections
- 4 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses a type in Shared.Kernel.DomainKernel.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.Tenant→Shared.Kernel.DomainKernel.SubscriptionPlanTypeModules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.Tenant→Shared.Kernel.DomainKernel.TenantRoleModules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.TenantInvitation→Shared.Kernel.DomainKernel.TenantRoleModules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.TenantMembership→Shared.Kernel.DomainKernel.TenantRole
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses a module listed above it, which is the healthy direction.
26→13 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses Modules.TenantIdentity.Public.DTOs.Tenant✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses a type in Modules.TenantIdentity.Public.DTOs.Tenant.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.Tenant→Modules.TenantIdentity.Public.DTOs.Tenant.TenantDTOModules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.TenantMembership→Modules.TenantIdentity.Public.DTOs.Tenant.TenantMembershipDTO
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses Modules.TenantIdentity.Public.DTOs.Tenant, so a change to Modules.TenantIdentity.Public.DTOs.Tenant can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain can't break Modules.TenantIdentity.Public.DTOs.Tenant.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses a module listed above it, which is the healthy direction.
26→23 Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses Shared.Features.Misc✕
- Connections
- 3 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses a type in Shared.Features.Misc.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.Tenant→Shared.Features.Misc.EntityModules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.TenantInvitation→Shared.Features.Misc.EntityModules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.TenantMembership→Shared.Features.Misc.Entity
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses Shared.Features.Misc, so a change to Shared.Features.Misc can break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain, while a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain can't break Shared.Features.Misc.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain uses a module listed above it, which is the healthy direction.
27→7 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses Shared.Kernel.DomainKernel✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses a type in Shared.Kernel.DomainKernel.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.StripeSubscription→Shared.Kernel.DomainKernel.SubscriptionPlanType
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses a module listed above it, which is the healthy direction.
27→23 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses Shared.Features.Misc✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses a type in Shared.Features.Misc.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.StripeSubscription→Shared.Features.Misc.Entity
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses Shared.Features.Misc, so a change to Shared.Features.Misc can break Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions can't break Shared.Features.Misc.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses a module listed above it, which is the healthy direction.
27→24 Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses Modules.Subscriptions.Features.DomainFeatures.StripeCustomers✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses a type in Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.StripeSubscription→Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.StripeCustomer
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses Modules.Subscriptions.Features.DomainFeatures.StripeCustomers, so a change to Modules.Subscriptions.Features.DomainFeatures.StripeCustomers can break Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions can't break Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions uses a module listed above it, which is the healthy direction.
28→8 Modules.TenantIdentity.Features.DomainFeatures.Users uses Shared.Kernel.DomainKernel.Interfaces✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Users uses a type in Shared.Kernel.DomainKernel.Interfaces.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Users.ApplicationUser→Shared.Kernel.DomainKernel.Interfaces.IApplicationUser
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Users uses Shared.Kernel.DomainKernel.Interfaces, so a change to Shared.Kernel.DomainKernel.Interfaces can break Modules.TenantIdentity.Features.DomainFeatures.Users, while a change to Modules.TenantIdentity.Features.DomainFeatures.Users can't break Shared.Kernel.DomainKernel.Interfaces.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Users uses a module listed above it, which is the healthy direction.
28→26 Modules.TenantIdentity.Features.DomainFeatures.Users uses Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Users uses a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Users.ApplicationUser→Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.TenantMembership
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Users uses Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain, so a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain can break Modules.TenantIdentity.Features.DomainFeatures.Users, while a change to Modules.TenantIdentity.Features.DomainFeatures.Users can't break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Users uses a module listed above it, which is the healthy direction.
29→22 Modules.Subscriptions.Features.Infrastructure.EFCore uses Shared.Features.EFCore✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.Infrastructure.EFCore uses a type in Shared.Features.EFCore.
- The types involved
Modules.Subscriptions.Features.Infrastructure.EFCore.SubscriptionsDbContext→Shared.Features.EFCore.BaseDbContext
- Direction
- Modules.Subscriptions.Features.Infrastructure.EFCore uses Shared.Features.EFCore, so a change to Shared.Features.EFCore can break Modules.Subscriptions.Features.Infrastructure.EFCore, while a change to Modules.Subscriptions.Features.Infrastructure.EFCore can't break Shared.Features.EFCore.
- Position
- Below the diagonal: Modules.Subscriptions.Features.Infrastructure.EFCore uses a module listed above it, which is the healthy direction.
29→24 Modules.Subscriptions.Features.Infrastructure.EFCore uses Modules.Subscriptions.Features.DomainFeatures.StripeCustomers✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.Infrastructure.EFCore uses a type in Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.
- The types involved
Modules.Subscriptions.Features.Infrastructure.EFCore.SubscriptionsDbContext→Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.StripeCustomer
- Direction
- Modules.Subscriptions.Features.Infrastructure.EFCore uses Modules.Subscriptions.Features.DomainFeatures.StripeCustomers, so a change to Modules.Subscriptions.Features.DomainFeatures.StripeCustomers can break Modules.Subscriptions.Features.Infrastructure.EFCore, while a change to Modules.Subscriptions.Features.Infrastructure.EFCore can't break Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.
- Position
- Below the diagonal: Modules.Subscriptions.Features.Infrastructure.EFCore uses a module listed above it, which is the healthy direction.
29→27 Modules.Subscriptions.Features.Infrastructure.EFCore uses Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.Infrastructure.EFCore uses a type in Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.
- The types involved
Modules.Subscriptions.Features.Infrastructure.EFCore.SubscriptionsDbContext→Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.StripeSubscription
- Direction
- Modules.Subscriptions.Features.Infrastructure.EFCore uses Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions, so a change to Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions can break Modules.Subscriptions.Features.Infrastructure.EFCore, while a change to Modules.Subscriptions.Features.Infrastructure.EFCore can't break Modules.Subscriptions.Features.DomainFeatures.StripeSubscriptions.
- Position
- Below the diagonal: Modules.Subscriptions.Features.Infrastructure.EFCore uses a module listed above it, which is the healthy direction.
30→1 Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses Shared.Features.Messaging.Commands✕
- Connections
- 5 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses a type in Shared.Features.Messaging.Commands.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands.CreateNewUser→Shared.Features.Messaging.Commands.CommandModules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands.CreateNewUserCommandHandler→Shared.Features.Messaging.Commands.ICommandHandlerModules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands.SelectTenant→Shared.Features.Messaging.Commands.CommandModules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands.SelectedTenantCommandHandler→Shared.Features.Messaging.Commands.ICommandHandlerModules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands.UpdateUser→Shared.Features.Messaging.Commands.Command
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses Shared.Features.Messaging.Commands, so a change to Shared.Features.Messaging.Commands can break Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands, while a change to Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands can't break Shared.Features.Messaging.Commands.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses a module listed above it, which is the healthy direction.
30→17 Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses Shared.Features.Misc.ExecutionContext✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses a type in Shared.Features.Misc.ExecutionContext.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands.SelectedTenantCommandHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBase
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses Shared.Features.Misc.ExecutionContext, so a change to Shared.Features.Misc.ExecutionContext can break Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands, while a change to Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands can't break Shared.Features.Misc.ExecutionContext.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses a module listed above it, which is the healthy direction.
30→28 Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses Modules.TenantIdentity.Features.DomainFeatures.Users✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses a type in Modules.TenantIdentity.Features.DomainFeatures.Users.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands.CreateNewUser→Modules.TenantIdentity.Features.DomainFeatures.Users.ApplicationUserModules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands.CreateNewUserCommandHandler→Modules.TenantIdentity.Features.DomainFeatures.Users.ApplicationUser
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses Modules.TenantIdentity.Features.DomainFeatures.Users, so a change to Modules.TenantIdentity.Features.DomainFeatures.Users can break Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands, while a change to Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands can't break Modules.TenantIdentity.Features.DomainFeatures.Users.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Commands uses a module listed above it, which is the healthy direction.
31→3 Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses Shared.Features.Messaging.Queries✕
- Connections
- 4 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses a type in Shared.Features.Messaging.Queries.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries.ClaimsForUserQueryHandler→Shared.Features.Messaging.Queries.IQueryHandlerModules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries.GetClaimsForExecutingUser→Shared.Features.Messaging.Queries.QueryModules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries.GetExecutingUser→Shared.Features.Messaging.Queries.QueryModules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries.GetUserByIdHandler→Shared.Features.Messaging.Queries.IQueryHandler
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses Shared.Features.Messaging.Queries, so a change to Shared.Features.Messaging.Queries can break Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries, while a change to Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries can't break Shared.Features.Messaging.Queries.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses a module listed above it, which is the healthy direction.
31→17 Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses Shared.Features.Misc.ExecutionContext✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses a type in Shared.Features.Misc.ExecutionContext.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries.ClaimsForUserQueryHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBaseModules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries.GetUserByIdHandler→Shared.Features.Misc.ExecutionContext.ServerExecutionBase
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses Shared.Features.Misc.ExecutionContext, so a change to Shared.Features.Misc.ExecutionContext can break Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries, while a change to Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries can't break Shared.Features.Misc.ExecutionContext.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses a module listed above it, which is the healthy direction.
31→28 Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses Modules.TenantIdentity.Features.DomainFeatures.Users✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses a type in Modules.TenantIdentity.Features.DomainFeatures.Users.
- The types involved
Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries.GetUserByIdHandler→Modules.TenantIdentity.Features.DomainFeatures.Users.ApplicationUser
- Direction
- Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses Modules.TenantIdentity.Features.DomainFeatures.Users, so a change to Modules.TenantIdentity.Features.DomainFeatures.Users can break Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries, while a change to Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries can't break Modules.TenantIdentity.Features.DomainFeatures.Users.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.DomainFeatures.Users.Application.Queries uses a module listed above it, which is the healthy direction.
32→26 Modules.TenantIdentity.Features.Infrastructure.EFCore uses Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain✕
- Connections
- 3 pairs of types, where a type in Modules.TenantIdentity.Features.Infrastructure.EFCore uses a type in Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.
- The types involved
Modules.TenantIdentity.Features.Infrastructure.EFCore.TenantIdentityDbContext→Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.TenantModules.TenantIdentity.Features.Infrastructure.EFCore.TenantIdentityDbContext→Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.TenantInvitationModules.TenantIdentity.Features.Infrastructure.EFCore.TenantIdentityDbContext→Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.TenantMembership
- Direction
- Modules.TenantIdentity.Features.Infrastructure.EFCore uses Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain, so a change to Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain can break Modules.TenantIdentity.Features.Infrastructure.EFCore, while a change to Modules.TenantIdentity.Features.Infrastructure.EFCore can't break Modules.TenantIdentity.Features.DomainFeatures.Tenants.Domain.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.Infrastructure.EFCore uses a module listed above it, which is the healthy direction.
32→28 Modules.TenantIdentity.Features.Infrastructure.EFCore uses Modules.TenantIdentity.Features.DomainFeatures.Users✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features.Infrastructure.EFCore uses a type in Modules.TenantIdentity.Features.DomainFeatures.Users.
- The types involved
Modules.TenantIdentity.Features.Infrastructure.EFCore.TenantIdentityDbContext→Modules.TenantIdentity.Features.DomainFeatures.Users.ApplicationUser
- Direction
- Modules.TenantIdentity.Features.Infrastructure.EFCore uses Modules.TenantIdentity.Features.DomainFeatures.Users, so a change to Modules.TenantIdentity.Features.DomainFeatures.Users can break Modules.TenantIdentity.Features.Infrastructure.EFCore, while a change to Modules.TenantIdentity.Features.Infrastructure.EFCore can't break Modules.TenantIdentity.Features.DomainFeatures.Users.
- Position
- Below the diagonal: Modules.TenantIdentity.Features.Infrastructure.EFCore uses a module listed above it, which is the healthy direction.
33→13 Modules.TenantIdentity.Web.Server.Controllers uses Modules.TenantIdentity.Public.DTOs.Tenant✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Web.Server.Controllers uses a type in Modules.TenantIdentity.Public.DTOs.Tenant.
- The types involved
Modules.TenantIdentity.Web.Server.Controllers.TenantsController→Modules.TenantIdentity.Public.DTOs.Tenant.TenantDTO
- Direction
- Modules.TenantIdentity.Web.Server.Controllers uses Modules.TenantIdentity.Public.DTOs.Tenant, so a change to Modules.TenantIdentity.Public.DTOs.Tenant can break Modules.TenantIdentity.Web.Server.Controllers, while a change to Modules.TenantIdentity.Web.Server.Controllers can't break Modules.TenantIdentity.Public.DTOs.Tenant.
- Position
- Below the diagonal: Modules.TenantIdentity.Web.Server.Controllers uses a module listed above it, which is the healthy direction.
33→14 Modules.TenantIdentity.Web.Server.Controllers uses Modules.TenantIdentity.Public.DTOs.Tenant.Operations✕
- Connections
- 3 pairs of types, where a type in Modules.TenantIdentity.Web.Server.Controllers uses a type in Modules.TenantIdentity.Public.DTOs.Tenant.Operations.
- The types involved
Modules.TenantIdentity.Web.Server.Controllers.TenantsController→Modules.TenantIdentity.Public.DTOs.Tenant.Operations.ChangeRoleOfTenantMemberDTOModules.TenantIdentity.Web.Server.Controllers.TenantsController→Modules.TenantIdentity.Public.DTOs.Tenant.Operations.CreateTenantDTOModules.TenantIdentity.Web.Server.Controllers.TenantsController→Modules.TenantIdentity.Public.DTOs.Tenant.Operations.InviteUserToTenantDTO
- Direction
- Modules.TenantIdentity.Web.Server.Controllers uses Modules.TenantIdentity.Public.DTOs.Tenant.Operations, so a change to Modules.TenantIdentity.Public.DTOs.Tenant.Operations can break Modules.TenantIdentity.Web.Server.Controllers, while a change to Modules.TenantIdentity.Web.Server.Controllers can't break Modules.TenantIdentity.Public.DTOs.Tenant.Operations.
- Position
- Below the diagonal: Modules.TenantIdentity.Web.Server.Controllers uses a module listed above it, which is the healthy direction.
33→23 Modules.TenantIdentity.Web.Server.Controllers uses Shared.Features.Misc✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Web.Server.Controllers uses a type in Shared.Features.Misc.
- The types involved
Modules.TenantIdentity.Web.Server.Controllers.TenantsController→Shared.Features.Misc.BaseControllerModules.TenantIdentity.Web.Server.Controllers.UsersController→Shared.Features.Misc.BaseController
- Direction
- Modules.TenantIdentity.Web.Server.Controllers uses Shared.Features.Misc, so a change to Shared.Features.Misc can break Modules.TenantIdentity.Web.Server.Controllers, while a change to Modules.TenantIdentity.Web.Server.Controllers can't break Shared.Features.Misc.
- Position
- Below the diagonal: Modules.TenantIdentity.Web.Server.Controllers uses a module listed above it, which is the healthy direction.
33→28 Modules.TenantIdentity.Web.Server.Controllers uses Modules.TenantIdentity.Features.DomainFeatures.Users✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Web.Server.Controllers uses a type in Modules.TenantIdentity.Features.DomainFeatures.Users.
- The types involved
Modules.TenantIdentity.Web.Server.Controllers.TenantsController→Modules.TenantIdentity.Features.DomainFeatures.Users.ApplicationUser
- Direction
- Modules.TenantIdentity.Web.Server.Controllers uses Modules.TenantIdentity.Features.DomainFeatures.Users, so a change to Modules.TenantIdentity.Features.DomainFeatures.Users can break Modules.TenantIdentity.Web.Server.Controllers, while a change to Modules.TenantIdentity.Web.Server.Controllers can't break Modules.TenantIdentity.Features.DomainFeatures.Users.
- Position
- Below the diagonal: Modules.TenantIdentity.Web.Server.Controllers uses a module listed above it, which is the healthy direction.
34→23 Modules.TenantIdentity.Web.Server.Controllers.Infrastructure uses Shared.Features.Misc✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Web.Server.Controllers.Infrastructure uses a type in Shared.Features.Misc.
- The types involved
Modules.TenantIdentity.Web.Server.Controllers.Infrastructure.ExternalLoginCallbackController→Shared.Features.Misc.BaseControllerModules.TenantIdentity.Web.Server.Controllers.Infrastructure.IdentityOperationsController→Shared.Features.Misc.BaseController
- Direction
- Modules.TenantIdentity.Web.Server.Controllers.Infrastructure uses Shared.Features.Misc, so a change to Shared.Features.Misc can break Modules.TenantIdentity.Web.Server.Controllers.Infrastructure, while a change to Modules.TenantIdentity.Web.Server.Controllers.Infrastructure can't break Shared.Features.Misc.
- Position
- Below the diagonal: Modules.TenantIdentity.Web.Server.Controllers.Infrastructure uses a module listed above it, which is the healthy direction.
34→28 Modules.TenantIdentity.Web.Server.Controllers.Infrastructure uses Modules.TenantIdentity.Features.DomainFeatures.Users✕
- Connections
- 2 pairs of types, where a type in Modules.TenantIdentity.Web.Server.Controllers.Infrastructure uses a type in Modules.TenantIdentity.Features.DomainFeatures.Users.
- The types involved
Modules.TenantIdentity.Web.Server.Controllers.Infrastructure.ExternalLoginCallbackController→Modules.TenantIdentity.Features.DomainFeatures.Users.ApplicationUserModules.TenantIdentity.Web.Server.Controllers.Infrastructure.IdentityOperationsController→Modules.TenantIdentity.Features.DomainFeatures.Users.ApplicationUser
- Direction
- Modules.TenantIdentity.Web.Server.Controllers.Infrastructure uses Modules.TenantIdentity.Features.DomainFeatures.Users, so a change to Modules.TenantIdentity.Features.DomainFeatures.Users can break Modules.TenantIdentity.Web.Server.Controllers.Infrastructure, while a change to Modules.TenantIdentity.Web.Server.Controllers.Infrastructure can't break Modules.TenantIdentity.Features.DomainFeatures.Users.
- Position
- Below the diagonal: Modules.TenantIdentity.Web.Server.Controllers.Infrastructure uses a module listed above it, which is the healthy direction.
35→2 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses Shared.Features.Messaging.IntegrationMessages✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses a type in Shared.Features.Messaging.IntegrationMessages.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers.TenantAdminCreatedIntegrationEventHandler→Shared.Features.Messaging.IntegrationMessages.IIntegrationEventHandler
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses Shared.Features.Messaging.IntegrationMessages, so a change to Shared.Features.Messaging.IntegrationMessages can break Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers can't break Shared.Features.Messaging.IntegrationMessages.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses a module listed above it, which is the healthy direction.
35→15 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses Modules.TenantIdentity.Public.IntegrationMessages✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses a type in Modules.TenantIdentity.Public.IntegrationMessages.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers.TenantAdminCreatedIntegrationEventHandler→Modules.TenantIdentity.Public.IntegrationMessages.TenantAdminCreatedEvent
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses Modules.TenantIdentity.Public.IntegrationMessages, so a change to Modules.TenantIdentity.Public.IntegrationMessages can break Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers can't break Modules.TenantIdentity.Public.IntegrationMessages.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses a module listed above it, which is the healthy direction.
35→29 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses Modules.Subscriptions.Features.Infrastructure.EFCore✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses a type in Modules.Subscriptions.Features.Infrastructure.EFCore.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers.TenantAdminCreatedIntegrationEventHandler→Modules.Subscriptions.Features.Infrastructure.EFCore.SubscriptionsDbContext
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses Modules.Subscriptions.Features.Infrastructure.EFCore, so a change to Modules.Subscriptions.Features.Infrastructure.EFCore can break Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers can't break Modules.Subscriptions.Features.Infrastructure.EFCore.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.EventHandlers uses a module listed above it, which is the healthy direction.
36→3 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses Shared.Features.Messaging.Queries✕
- Connections
- 2 pairs of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses a type in Shared.Features.Messaging.Queries.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries.GetStripeCustomerByStripePortalId→Shared.Features.Messaging.Queries.QueryModules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries.GetStripeCustomerByStripePortalIdQueryHandler→Shared.Features.Messaging.Queries.IQueryHandler
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses Shared.Features.Messaging.Queries, so a change to Shared.Features.Messaging.Queries can break Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries can't break Shared.Features.Messaging.Queries.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses a module listed above it, which is the healthy direction.
36→24 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses Modules.Subscriptions.Features.DomainFeatures.StripeCustomers✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses a type in Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries.GetStripeCustomerByStripePortalIdQueryHandler→Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.StripeCustomer
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses Modules.Subscriptions.Features.DomainFeatures.StripeCustomers, so a change to Modules.Subscriptions.Features.DomainFeatures.StripeCustomers can break Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries can't break Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses a module listed above it, which is the healthy direction.
36→29 Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses Modules.Subscriptions.Features.Infrastructure.EFCore✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses a type in Modules.Subscriptions.Features.Infrastructure.EFCore.
- The types involved
Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries.GetStripeCustomerByStripePortalIdQueryHandler→Modules.Subscriptions.Features.Infrastructure.EFCore.SubscriptionsDbContext
- Direction
- Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses Modules.Subscriptions.Features.Infrastructure.EFCore, so a change to Modules.Subscriptions.Features.Infrastructure.EFCore can break Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries, while a change to Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries can't break Modules.Subscriptions.Features.Infrastructure.EFCore.
- Position
- Below the diagonal: Modules.Subscriptions.Features.DomainFeatures.StripeCustomers.Application.Queries uses a module listed above it, which is the healthy direction.
37→1 Modules.Subscriptions.Features.Infrastructure.StripePayments uses Shared.Features.Messaging.Commands✕
- Connections
- 4 pairs of types, where a type in Modules.Subscriptions.Features.Infrastructure.StripePayments uses a type in Shared.Features.Messaging.Commands.
- The types involved
Modules.Subscriptions.Features.Infrastructure.StripePayments.CreateStripeBillingPortalSession→Shared.Features.Messaging.Commands.CommandModules.Subscriptions.Features.Infrastructure.StripePayments.CreateStripeBillingPortalSessionCommandHandler→Shared.Features.Messaging.Commands.ICommandHandlerModules.Subscriptions.Features.Infrastructure.StripePayments.CreateStripeCheckoutSession→Shared.Features.Messaging.Commands.CommandModules.Subscriptions.Features.Infrastructure.StripePayments.CreateStripeCheckoutSessionCommandHandler→Shared.Features.Messaging.Commands.ICommandHandler
- Direction
- Modules.Subscriptions.Features.Infrastructure.StripePayments uses Shared.Features.Messaging.Commands, so a change to Shared.Features.Messaging.Commands can break Modules.Subscriptions.Features.Infrastructure.StripePayments, while a change to Modules.Subscriptions.Features.Infrastructure.StripePayments can't break Shared.Features.Messaging.Commands.
- Position
- Below the diagonal: Modules.Subscriptions.Features.Infrastructure.StripePayments uses a module listed above it, which is the healthy direction.
37→7 Modules.Subscriptions.Features.Infrastructure.StripePayments uses Shared.Kernel.DomainKernel✕
- Connections
- 2 pairs of types, where a type in Modules.Subscriptions.Features.Infrastructure.StripePayments uses a type in Shared.Kernel.DomainKernel.
- The types involved
Modules.Subscriptions.Features.Infrastructure.StripePayments.CreateStripeCheckoutSession→Shared.Kernel.DomainKernel.SubscriptionPlanTypeModules.Subscriptions.Features.Infrastructure.StripePayments.StripeSubscriptionPlan→Shared.Kernel.DomainKernel.SubscriptionPlanType
- Direction
- Modules.Subscriptions.Features.Infrastructure.StripePayments uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Modules.Subscriptions.Features.Infrastructure.StripePayments, while a change to Modules.Subscriptions.Features.Infrastructure.StripePayments can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Modules.Subscriptions.Features.Infrastructure.StripePayments uses a module listed above it, which is the healthy direction.
37→29 Modules.Subscriptions.Features.Infrastructure.StripePayments uses Modules.Subscriptions.Features.Infrastructure.EFCore✕
- Connections
- 2 pairs of types, where a type in Modules.Subscriptions.Features.Infrastructure.StripePayments uses a type in Modules.Subscriptions.Features.Infrastructure.EFCore.
- The types involved
Modules.Subscriptions.Features.Infrastructure.StripePayments.CreateStripeBillingPortalSessionCommandHandler→Modules.Subscriptions.Features.Infrastructure.EFCore.SubscriptionsDbContextModules.Subscriptions.Features.Infrastructure.StripePayments.CreateStripeCheckoutSessionCommandHandler→Modules.Subscriptions.Features.Infrastructure.EFCore.SubscriptionsDbContext
- Direction
- Modules.Subscriptions.Features.Infrastructure.StripePayments uses Modules.Subscriptions.Features.Infrastructure.EFCore, so a change to Modules.Subscriptions.Features.Infrastructure.EFCore can break Modules.Subscriptions.Features.Infrastructure.StripePayments, while a change to Modules.Subscriptions.Features.Infrastructure.StripePayments can't break Modules.Subscriptions.Features.Infrastructure.EFCore.
- Position
- Below the diagonal: Modules.Subscriptions.Features.Infrastructure.StripePayments uses a module listed above it, which is the healthy direction.
37→39 Modules.Subscriptions.Features.Infrastructure.StripePayments uses Modules.Subscriptions.Features.Infrastructure.Configuration part of a loop✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.Infrastructure.StripePayments uses a type in Modules.Subscriptions.Features.Infrastructure.Configuration.
- The types involved
Modules.Subscriptions.Features.Infrastructure.StripePayments.CreateStripeCheckoutSessionCommandHandler→Modules.Subscriptions.Features.Infrastructure.Configuration.SubscriptionsConfiguration
- Direction
- Modules.Subscriptions.Features.Infrastructure.StripePayments uses Modules.Subscriptions.Features.Infrastructure.Configuration, so a change to Modules.Subscriptions.Features.Infrastructure.Configuration can break Modules.Subscriptions.Features.Infrastructure.StripePayments, while a change to Modules.Subscriptions.Features.Infrastructure.StripePayments can't break Modules.Subscriptions.Features.Infrastructure.Configuration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→5 Modules.TenantIdentity.Features uses Shared.Features.Misc.Modules✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features uses a type in Shared.Features.Misc.Modules.
- The types involved
Modules.TenantIdentity.Features.TenantIdentityModule→Shared.Features.Misc.Modules.IModule
- Direction
- Modules.TenantIdentity.Features uses Shared.Features.Misc.Modules, so a change to Shared.Features.Misc.Modules can break Modules.TenantIdentity.Features, while a change to Modules.TenantIdentity.Features can't break Shared.Features.Misc.Modules.
- Position
- Below the diagonal: Modules.TenantIdentity.Features uses a module listed above it, which is the healthy direction.
38→12 Modules.TenantIdentity.Features uses Modules.TenantIdentity.Features.Infrastructure.Configuration✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features uses a type in Modules.TenantIdentity.Features.Infrastructure.Configuration.
- The types involved
Modules.TenantIdentity.Features.TenantIdentityModule→Modules.TenantIdentity.Features.Infrastructure.Configuration.TenantIdentityConfiguration
- Direction
- Modules.TenantIdentity.Features uses Modules.TenantIdentity.Features.Infrastructure.Configuration, so a change to Modules.TenantIdentity.Features.Infrastructure.Configuration can break Modules.TenantIdentity.Features, while a change to Modules.TenantIdentity.Features can't break Modules.TenantIdentity.Features.Infrastructure.Configuration.
- Position
- Below the diagonal: Modules.TenantIdentity.Features uses a module listed above it, which is the healthy direction.
38→32 Modules.TenantIdentity.Features uses Modules.TenantIdentity.Features.Infrastructure.EFCore✕
- Connections
- 1 pair of types, where a type in Modules.TenantIdentity.Features uses a type in Modules.TenantIdentity.Features.Infrastructure.EFCore.
- The types involved
Modules.TenantIdentity.Features.TenantIdentityModule→Modules.TenantIdentity.Features.Infrastructure.EFCore.TenantIdentityDbContext
- Direction
- Modules.TenantIdentity.Features uses Modules.TenantIdentity.Features.Infrastructure.EFCore, so a change to Modules.TenantIdentity.Features.Infrastructure.EFCore can break Modules.TenantIdentity.Features, while a change to Modules.TenantIdentity.Features can't break Modules.TenantIdentity.Features.Infrastructure.EFCore.
- Position
- Below the diagonal: Modules.TenantIdentity.Features uses a module listed above it, which is the healthy direction.
39→4 Modules.Subscriptions.Features.Infrastructure.Configuration uses Shared.Features.Misc.Configuration✕
- Connections
- 2 pairs of types, where a type in Modules.Subscriptions.Features.Infrastructure.Configuration uses a type in Shared.Features.Misc.Configuration.
- The types involved
Modules.Subscriptions.Features.Infrastructure.Configuration.SubscriptionsConfiguration→Shared.Features.Misc.Configuration.ConfigurationObjectModules.Subscriptions.Features.Infrastructure.Configuration.SubscriptionsConfigurationValidator→Shared.Features.Misc.Configuration.ConfigurationObjectValidator
- Direction
- Modules.Subscriptions.Features.Infrastructure.Configuration uses Shared.Features.Misc.Configuration, so a change to Shared.Features.Misc.Configuration can break Modules.Subscriptions.Features.Infrastructure.Configuration, while a change to Modules.Subscriptions.Features.Infrastructure.Configuration can't break Shared.Features.Misc.Configuration.
- Position
- Below the diagonal: Modules.Subscriptions.Features.Infrastructure.Configuration uses a module listed above it, which is the healthy direction.
39→7 Modules.Subscriptions.Features.Infrastructure.Configuration uses Shared.Kernel.DomainKernel✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.Infrastructure.Configuration uses a type in Shared.Kernel.DomainKernel.
- The types involved
Modules.Subscriptions.Features.Infrastructure.Configuration.SubscriptionsConfiguration→Shared.Kernel.DomainKernel.SubscriptionPlanType
- Direction
- Modules.Subscriptions.Features.Infrastructure.Configuration uses Shared.Kernel.DomainKernel, so a change to Shared.Kernel.DomainKernel can break Modules.Subscriptions.Features.Infrastructure.Configuration, while a change to Modules.Subscriptions.Features.Infrastructure.Configuration can't break Shared.Kernel.DomainKernel.
- Position
- Below the diagonal: Modules.Subscriptions.Features.Infrastructure.Configuration uses a module listed above it, which is the healthy direction.
39→37 Modules.Subscriptions.Features.Infrastructure.Configuration uses Modules.Subscriptions.Features.Infrastructure.StripePayments✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features.Infrastructure.Configuration uses a type in Modules.Subscriptions.Features.Infrastructure.StripePayments.
- The types involved
Modules.Subscriptions.Features.Infrastructure.Configuration.SubscriptionsConfiguration→Modules.Subscriptions.Features.Infrastructure.StripePayments.StripeSubscriptionPlan
- Direction
- Modules.Subscriptions.Features.Infrastructure.Configuration uses Modules.Subscriptions.Features.Infrastructure.StripePayments, so a change to Modules.Subscriptions.Features.Infrastructure.StripePayments can break Modules.Subscriptions.Features.Infrastructure.Configuration, while a change to Modules.Subscriptions.Features.Infrastructure.Configuration can't break Modules.Subscriptions.Features.Infrastructure.StripePayments.
- Position
- Below the diagonal: Modules.Subscriptions.Features.Infrastructure.Configuration uses a module listed above it, which is the healthy direction.
40→5 Modules.Subscriptions.Features uses Shared.Features.Misc.Modules✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features uses a type in Shared.Features.Misc.Modules.
- The types involved
Modules.Subscriptions.Features.SubscriptionsModule→Shared.Features.Misc.Modules.IModule
- Direction
- Modules.Subscriptions.Features uses Shared.Features.Misc.Modules, so a change to Shared.Features.Misc.Modules can break Modules.Subscriptions.Features, while a change to Modules.Subscriptions.Features can't break Shared.Features.Misc.Modules.
- Position
- Below the diagonal: Modules.Subscriptions.Features uses a module listed above it, which is the healthy direction.
40→29 Modules.Subscriptions.Features uses Modules.Subscriptions.Features.Infrastructure.EFCore✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features uses a type in Modules.Subscriptions.Features.Infrastructure.EFCore.
- The types involved
Modules.Subscriptions.Features.SubscriptionsModule→Modules.Subscriptions.Features.Infrastructure.EFCore.SubscriptionsDbContext
- Direction
- Modules.Subscriptions.Features uses Modules.Subscriptions.Features.Infrastructure.EFCore, so a change to Modules.Subscriptions.Features.Infrastructure.EFCore can break Modules.Subscriptions.Features, while a change to Modules.Subscriptions.Features can't break Modules.Subscriptions.Features.Infrastructure.EFCore.
- Position
- Below the diagonal: Modules.Subscriptions.Features uses a module listed above it, which is the healthy direction.
40→39 Modules.Subscriptions.Features uses Modules.Subscriptions.Features.Infrastructure.Configuration✕
- Connections
- 1 pair of types, where a type in Modules.Subscriptions.Features uses a type in Modules.Subscriptions.Features.Infrastructure.Configuration.
- The types involved
Modules.Subscriptions.Features.SubscriptionsModule→Modules.Subscriptions.Features.Infrastructure.Configuration.SubscriptionsConfiguration
- Direction
- Modules.Subscriptions.Features uses Modules.Subscriptions.Features.Infrastructure.Configuration, so a change to Modules.Subscriptions.Features.Infrastructure.Configuration can break Modules.Subscriptions.Features, while a change to Modules.Subscriptions.Features can't break Modules.Subscriptions.Features.Infrastructure.Configuration.
- Position
- Below the diagonal: Modules.Subscriptions.Features uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | High / Critical |
| A07:2025 — Authentication Failures | 5 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No tests found finding(s) in Test Distribution; Resolve the 10 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED (2), REDACTED (2); Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +7.3 pts | Low | Test Distribution |
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +6.2 pts | Low | REDACTED Scanning |
| Resolve the 10 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED (2), REDACTED (2). | +6.7 pts | Medium | Dependency Hygiene |
| Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with REDACTED, Modules.Subscriptions.Features.csproj. | +2.8 pts | Low | Dependency Hygiene |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +4.0 pts | Medium | DR & Backup |
| Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. | +1.7 pts | Low | Dependency Hygiene |
| 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. | +3.0 pts | Medium | Text alternatives |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.0 pts | Medium | Keyboard semantics |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | Static Analysis (SAST): High: REDACTED |
| Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs | 3.5 | Mixed | Explicit Debt: EmptyCatchBlock |
| REDACTED | 3.6 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.5 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.0 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 5.7 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 6.4 | Near-clean | Dependency Vulnerabilities: Medium CVE: REDACTED |
| Source/Shared/Client/BuildingBlocks/Http/HttpClientService.cs | 6.4 | Near-clean | Explicit Debt: EmptyCatchBlock |
| REDACTED.cs | 6.9 | Near-clean | Explicit Debt: CommentedOutCode |
| Source/Shared/Kernel/Extensions/ClaimsPrincipal/ClaimsPrincipalExtensions.cs | 6.9 | Near-clean | Explicit Debt: Dead code: HasUserIdClaim |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| Source/Shared/Client/BuildingBlocks/Auth/HostAuthenticationStateProvider.cs | 7.6 | Near-clean | Explicit Debt: EmptyCatchBlock |
| Source/Shared/Features/EFCore/MultiTenancy/Exceptions/CrossTenantUpdateException.cs | 7.6 | Near-clean | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| Source/Modules/TenantIdentity/Web/Server/Controllers/TenantsController.cs | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: TenantsController.cs ↔ IIntegrationEventHandler.cs |
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 97 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 — 97 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, 286 of 335 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- 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: Source/package.json — 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.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 295 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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.
- AX7 Slice cohesion — 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. 61 further occurrence(s) are not listed individually; the score already reflects all 101.
- 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. User interface: 13 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: the service booted and answers HTTP at http://127.0.0.1:40133, but serves no HTML page — nothing for the accessibility crawl.
- DM6 Domain ↔ infrastructure boundary — 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. 7 further occurrence(s) are not listed individually; the score already reflects all 47.
- 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.
- 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. 2 further occurrence(s) are not listed individually; the score already reflects all 42.
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.
- 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 REDACTED Scanning: REDACTED 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.
- 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.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
4 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with AuthorizedHttpClientService.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with AuthorizedHttpClientService.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with AuthorizedHttpClientService.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
13 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling — start with Modules.TenantIdentity.Public.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 15 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with TenantIdentityDbContext.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D12 · Dependency Hygiene
37 outdated, 1 vulnerable, 8 deprecated, 1 prerelease packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.
What to do
- Resolve the 10 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with REDACTED, Modules.Subscriptions.Features.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 260 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 41 direct `PackageReference`(s), and 209 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
10 deducted debt markers + 33 dead symbols across 4256 LoC in the .NET projects (2.4/KLoC) → score 5.1.
What to do
- Resolve the 33 Dead code finding(s) in Explicit Debt — start with ClaimsPrincipalExtensions.cs (3), IUserIdentifiable.cs, UserIdClaimNotFoundException.cs. — One of this dimension's main actionable groups (33 warning-level).
- Resolve the 5 EmptyCatchBlock finding(s) in Explicit Debt — start with AuthorizedHttpClientService.cs (2), HttpClientService.cs (2), HostAuthenticationStateProvider.cs. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with CrossTenantUpdateException.cs. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
13 projects, 175 source files, 4256 hand-written lines of code (4256 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 1040 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 24 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 15 unit(s).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (5 contexts). Contexts: LandingPages, Shared, Subscriptions, TenantIdentity, Web.
D26 · Project Cohesion
0 of 13 projects flagged as possibly oversized/incoherent.
D27 · Navigability
98 % of calls cross a namespace and 6 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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)
15 finding(s): 0 critical, 8 high, 7 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 3 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
6 finding(s): 1 critical, 4 high, 1 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
18 of 18 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Source/Modules/TenantIdentity/Web/Server/TenantIdentityModuleStartup.cs. Counted over 18 of the 175 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 18 Orphaned file finding(s) in Knowledge Freshness — start with TenantIdentityModuleStartup.cs, TenantIdentityDbContext.cs, BaseDbContext.cs. — One of this dimension's main actionable groups (18 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: TenantsController.cs↔IIntegrationEventHandler.cs 70%; IIntegrationEventHandler.cs↔BaseController.cs 60%; BaseController.cs↔ServerExecutionContext.cs 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with TenantsController.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with IIntegrationEventHandler.cs, BaseController.cs, Registrator.cs. — One of this dimension's main actionable groups (3 warning-level).
D39 · IL Efficiency
0 of 386 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
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 13 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
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. (×2) — Source/Shared/Client/Components/Modals/DeletionModal.razor:4, Source/Shared/Client/Components/Modals/ErrorModal.razor:4
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
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This layout renders the routed page body, so it is where the landmark belongs: wrap @Body in <main>. — Source/Shared/Client/Layouts/MainLayout/MainLayout.razor:6
- A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet). — Source/Web/Client/Pages/Index.razor:3
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
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — Source/Shared/Client/Layouts/MainLayout/NavMenu.razor:8
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
- `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — Source/Web/Server/wwwroot/css/site.css:2
- `input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — Source/Web/Server/wwwroot/css/site.css:49
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 13 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. — Source/package.json:1
What to do
- Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then 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 — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX2 · Stateful singletons
- `HostAuthenticationStateProvider` is a singleton (one shared instance) but mutates instance state outside any lock (cachedUser, userLastCheck; e.g. `cachedUser` at line 40). — Source/Shared/Client/BuildingBlocks/Auth/HostAuthenticationStateProvider.cs:12
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles
- The namespaces Modules.Subscriptions.Features.Infrastructure.Configuration ↔ Modules.Subscriptions.Features.Infrastructure.StripePayments depend on each other. The lightest dependency in the cycle is Modules.Subscriptions.Features.Infrastructure.Configuration → Modules.Subscriptions.Features.Infrastructure.StripePayments (Modules.Subscriptions.Features.Infrastructure.Configuration.SubscriptionsConfiguration → Modules.Subscriptions.Features.Infrastructure.StripePayments.StripeSubscriptionPlan, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Source/Modules/Subscriptions/Features/Infrastructure/Configuration/SubscriptionsConfiguration.cs:1
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX7 · Slice cohesion
- `TenantAdminCreatedIntegrationEventHandler` (slice 'DomainFeatures') depends on `IIntegrationEventHandler` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/EventHandlers/TenantAdminCreatedIntegrationEventHandler.cs:9
- `TenantAdminCreatedIntegrationEventHandler` (slice 'DomainFeatures') depends on `SubscriptionsDbContext` from slice 'Infrastructure'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/EventHandlers/TenantAdminCreatedIntegrationEventHandler.cs:11
- `GetStripeCustomerByStripePortalId` (slice 'DomainFeatures') depends on `Query` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:7
- `GetStripeCustomerByStripePortalIdQueryHandler` (slice 'DomainFeatures') depends on `IQueryHandler` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:12
- `GetStripeCustomerByStripePortalIdQueryHandler` (slice 'DomainFeatures') depends on `SubscriptionsDbContext` from slice 'Infrastructure'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:14
- `StripeCustomer` (slice 'DomainFeatures') depends on `Entity` from slice 'Misc'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/StripeCustomer.cs:7
- `CreateTrialingSubscription` (slice 'DomainFeatures') depends on `Command` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/CreateTrialingSubscription.cs:9
- `CreateTrialingSubscriptionCommandHandler` (slice 'DomainFeatures') depends on `ServerExecutionBase` from slice 'Misc'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/CreateTrialingSubscription.cs:16
- `CreateTrialingSubscriptionCommandHandler` (slice 'DomainFeatures') depends on `ICommandHandler` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/CreateTrialingSubscription.cs:16
- `PauseActiveSubscription` (slice 'DomainFeatures') depends on `Command` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/PauseActiveSubscription.cs:7
- `PauseActiveSubscriptionCommandHandler` (slice 'DomainFeatures') depends on `ServerExecutionBase` from slice 'Misc'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/PauseActiveSubscription.cs:12
- `PauseActiveSubscriptionCommandHandler` (slice 'DomainFeatures') depends on `ICommandHandler` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/PauseActiveSubscription.cs:12
- `UpdateSubscriptionPeriod` (slice 'DomainFeatures') depends on `Command` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/UpdateSubscriptionPeriod.cs:7
- `UpdateSubscriptionPerioEndCommandHandler` (slice 'DomainFeatures') depends on `ServerExecutionBase` from slice 'Misc'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/UpdateSubscriptionPeriod.cs:12
- `UpdateSubscriptionPerioEndCommandHandler` (slice 'DomainFeatures') depends on `ICommandHandler` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/UpdateSubscriptionPeriod.cs:12
- `GetSubscriptionForTenant` (slice 'DomainFeatures') depends on `Query` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Queries/GetSubscriptionForTenant.cs:5
- `StripeSubscription` (slice 'DomainFeatures') depends on `Entity` from slice 'Misc'. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/StripeSubscription.cs:9
- `SubscriptionsConfiguration` (slice 'Infrastructure') depends on `ConfigurationObject` from slice 'Misc'. — Source/Modules/Subscriptions/Features/Infrastructure/Configuration/SubscriptionsConfiguration.cs:7
- `SubscriptionsConfigurationValidator` (slice 'Infrastructure') depends on `ConfigurationObjectValidator` from slice 'Misc'. — Source/Modules/Subscriptions/Features/Infrastructure/Configuration/SubscriptionsConfigurationValidator.cs:6
- `SubscriptionsDbContext` (slice 'Infrastructure') depends on `BaseDbContext` from slice 'EFCore'. — Source/Modules/Subscriptions/Features/Infrastructure/EFCore/SubscriptionsDbContext.cs:8
- `SubscriptionsDbContext` (slice 'Infrastructure') depends on `StripeCustomer` from slice 'DomainFeatures'. — Source/Modules/Subscriptions/Features/Infrastructure/EFCore/SubscriptionsDbContext.cs:17
- `SubscriptionsDbContext` (slice 'Infrastructure') depends on `StripeSubscription` from slice 'DomainFeatures'. — Source/Modules/Subscriptions/Features/Infrastructure/EFCore/SubscriptionsDbContext.cs:18
- `CreateStripeBillingPortalSession` (slice 'Infrastructure') depends on `Command` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/Infrastructure/StripePayments/CreateStripeBillingPortalSession.cs:8
- `CreateStripeBillingPortalSessionCommandHandler` (slice 'Infrastructure') depends on `ICommandHandler` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/Infrastructure/StripePayments/CreateStripeBillingPortalSession.cs:14
- `CreateStripeCheckoutSession` (slice 'Infrastructure') depends on `Command` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/Infrastructure/StripePayments/CreateStripeCheckoutSession.cs:10
- `CreateStripeCheckoutSessionCommandHandler` (slice 'Infrastructure') depends on `ICommandHandler` from slice 'Messaging'. — Source/Modules/Subscriptions/Features/Infrastructure/StripePayments/CreateStripeCheckoutSession.cs:18
- `AddMemberToTenant` (slice 'DomainFeatures') depends on `Command` from slice 'Messaging'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/AddMemberToTenant.cs:9
- `AddMemberToTenantCommandHandler` (slice 'DomainFeatures') depends on `ServerExecutionBase` from slice 'Misc'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/AddMemberToTenant.cs:15
- `AddMemberToTenantCommandHandler` (slice 'DomainFeatures') depends on `ICommandHandler` from slice 'Messaging'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/AddMemberToTenant.cs:15
- `AddMemberToTenantCommandHandler` (slice 'DomainFeatures') depends on `DbSetExtensions` from slice 'EFCore'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/AddMemberToTenant.cs:21
- `CreateTenant` (slice 'DomainFeatures') depends on `Command` from slice 'Messaging'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/CreateTenant.cs:9
- `CreateTenantWithAdminCommandHandler` (slice 'DomainFeatures') depends on `ServerExecutionBase` from slice 'Misc'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/CreateTenant.cs:15
- `CreateTenantWithAdminCommandHandler` (slice 'DomainFeatures') depends on `ICommandHandler` from slice 'Messaging'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/CreateTenant.cs:15
- `DeleteTenant` (slice 'DomainFeatures') depends on `Command` from slice 'Messaging'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/DeleteTenant.cs:11
- `DeleteTenantCommandHandler` (slice 'DomainFeatures') depends on `ServerExecutionBase` from slice 'Misc'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/DeleteTenant.cs:16
- `DeleteTenantCommandHandler` (slice 'DomainFeatures') depends on `ICommandHandler` from slice 'Messaging'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/DeleteTenant.cs:16
- `DeleteTenantCommandHandler` (slice 'DomainFeatures') depends on `Error` from slice 'Misc'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/DeleteTenant.cs:25
- `RemoveMemberFromTenant` (slice 'DomainFeatures') depends on `Command` from slice 'Messaging'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/RemoveMemberFromTenant.cs:7
- `RemoveMemberFromTenantCommandHandler` (slice 'DomainFeatures') depends on `ServerExecutionBase` from slice 'Misc'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/RemoveMemberFromTenant.cs:13
- `RemoveMemberFromTenantCommandHandler` (slice 'DomainFeatures') depends on `ICommandHandler` from slice 'Messaging'. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/RemoveMemberFromTenant.cs:13
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
AX9 · CQS / query purity
C2 · Access Controls
- Access here is not default-deny: `StripeSuccessController.OrderSuccess` is in a controller that declares no authorization (on itself, a base controller or any action) while 4 sibling controllers do, and no fallback policy, global AuthorizeFilter or gated MapControllers covers it. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:25
What to do
- Put every endpoint behind the guard its siblings carry — [Authorize(Policy = …)] on the action or its controller, RequireAuthorization on the route or its group, or a fallback policy with explicit [AllowAnonymous] opt-outs — so the open surface is only what is public on purpose.
C3 · Audit Trail
- An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
What to do
- Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
DM1 · Aggregate boundaries
- `Tenant` references the aggregate root `TenantMembership` directly (via `Memberships`) — hold its `TenantMembershipId` instead. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:15
- `TenantMembership` references the aggregate root `Tenant` directly (via `Tenant`) — hold its `TenantId` instead. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs:19
- `ApplicationUser` references the aggregate root `TenantMembership` directly (via `TenantMemberships`) — hold its `TenantMembershipId` instead. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/ApplicationUser.cs:17
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `TenantMembership.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. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs:18
- `StripeCustomer.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. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/StripeCustomer.cs:9
- `StripeCustomer.StripePortalCustomerId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/StripeCustomer.cs:10
- `StripeSubscription.StripePortalSubscriptionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/StripeSubscription.cs:13
- `StripeSubscription.StripeCustomerId` 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. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/StripeSubscription.cs:14
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM3 · Integration-event coupling
DM4 · Rich vs anemic model
- `TenantMembership` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs:9
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `Tenant` exposes its own state through a mutable collection (Memberships, Invitations) — a caller can add to or remove from it directly, without passing through the methods that enforce the invariants. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:11
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
- `TenantAdminCreatedIntegrationEventHandler` (domain layer) names `SubscriptionsDbContext` from `Modules.Subscriptions.Features.Infrastructure.EFCore` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/EventHandlers/TenantAdminCreatedIntegrationEventHandler.cs:11, Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/EventHandlers/TenantAdminCreatedIntegrationEventHandler.cs:13
- `GetStripeCustomerByStripePortalIdQueryHandler` (domain layer) names `SubscriptionsDbContext` from `Modules.Subscriptions.Features.Infrastructure.EFCore` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:14, Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:16
- `StripeCustomerEFConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/StripeCustomer.cs:22
- `StripeCustomerEFConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/StripeCustomer.cs:24
- `StripeSubscriptionEFConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/StripeSubscription.cs:50
- `StripeSubscriptionEFConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/StripeSubscription.cs:52
- `DeleteTenantCommandHandler` (domain layer) names `EntityState` from `Microsoft.EntityFrameworkCore` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/DeleteTenant.cs:33
- `Tenant` (domain layer) names `StatusCodes` from `Microsoft.AspNetCore.Http` — a HTTP type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×6) — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:37, Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:51, Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:58, …
- `TenantEFConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:107
- `TenantEFConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:109
- `TenantInvitationEFConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantInvitation.cs:25
- `TenantInvitationEFConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantInvitation.cs:27
- `TenantMembershipEFConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs:38
- `TenantMembershipEFConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs:40
- `CreateNewUser` (domain layer) names `ApplicationUser` from `Modules.TenantIdentity.Features.DomainFeatures.Users` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs:9
- `CreateNewUser` (domain layer) names `ExternalLoginInfo` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs:10
- `CreateNewUserCommandHandler` (domain layer) names `UserManager` 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) — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs:15, Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs:16
- `UpdateUser` (domain layer) names `IFormFile` from `Microsoft.AspNetCore.Http` — a HTTP type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/UpdateUser.cs:9
- `GetExecutingUser` (domain layer) names `ApplicationUser` from `Modules.TenantIdentity.Features.DomainFeatures.Users` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetExecutingUser.cs:7
- `GetUserByIdHandler` (domain layer) names `ApplicationUser` from `Modules.TenantIdentity.Features.DomainFeatures.Users` — a persistence/infrastructure type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetExecutingUser.cs:10
- `GetUserByIdHandler` (domain layer) names `ApplicationUser` from `Modules.TenantIdentity.Features.DomainFeatures.Users` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetExecutingUser.cs:14
- `ApplicationUser` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/ApplicationUser.cs:9
- `ApplicationUser` (domain layer) names `IdentityUserLogin` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/ApplicationUser.cs:53
- `ApplicationUser` (domain layer) names `IdentityUserClaim` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/ApplicationUser.cs:54
- `ApplicationUser` (domain layer) names `IdentityUserToken` from `Microsoft.AspNetCore.Identity` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/ApplicationUser.cs:55
- `ApplicationUserEFConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/ApplicationUser.cs:58
- `ApplicationUserEFConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Source/Modules/TenantIdentity/Features/DomainFeatures/Users/ApplicationUser.cs:60
- `AddMemberToTenantCommandHandler` (domain layer) uses `EF Core` inside a method body — infrastructure reached without it appearing in any signature. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/AddMemberToTenant.cs:15
- `CreateTenantWithAdminCommandHandler` (domain layer) uses `EF Core` inside a method body — infrastructure reached without it appearing in any signature. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/CreateTenant.cs:15
- `RemoveMemberFromTenantCommandHandler` (domain layer) uses `DbContext` inside a method body — infrastructure reached without it appearing in any signature. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/RemoveMemberFromTenant.cs:13
- `UpdateTenantMembershipCommandHandler` (domain layer) uses `DbContext` inside a method body — infrastructure reached without it appearing in any signature. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/UpdateTenantMembership.cs:14
- `TenantSubscriptionUpdatedIntegrationEventHandler` (domain layer) uses `EF Core` inside a method body — infrastructure reached without it appearing in any signature. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/IntegrationMessageHandlers/TenantSubscriptionUpdatedIntegrationEventHandler.cs:9
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED3 · Event naming
ED4 · Outbox / dual-write
ED5 · Idempotency
- `Commands.CreateTenantWithAdminCommandHandler.HandleAsync` mutates persistent state (a database save) and inserts a new `Tenant` with no identity assigned (the store or its constructor generates a new one) (line 23), so a re-run inserts another one. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/CreateTenant.cs:19
- `Commands.CreateTrialingSubscriptionCommandHandler.HandleAsync` mutates persistent state (a database save) and inserts a new `StripeSubscription` with no identity assigned (the store or its constructor generates a new one) (line 37), so a re-run inserts another one. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/CreateTrialingSubscription.cs:20
What to do
- Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `OnInitializedAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED.cs:28
- `OnParametersSetAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED.cs:39
- `GetSubscription` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Source/Modules/Subscriptions/Web/Server/Controllers/StripeSubscriptionsController.cs:18
- `AddDbUpMigration` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Source/Shared/Features/EFCore/DbUp/Registrator.cs:12
- `HandleNotFoundException` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:48
- `HandleUnauthorizedException` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:58
- `HandleDomainException` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:68
- `HandleUnknownExceptionAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:79
- `OpenSignInModal` has an empty body — confirm it's an intentional no-op and not an unfinished method. — Source/Modules/LandingPages/Server/LandingPagesLayout.razor.cs:24
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×9) — Source/Modules/LandingPages/Server/LandingPagesLayout.razor.cs:31, REDACTED.cs:43, REDACTED.cs:48, …
- `OpenSignUpModal` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — REDACTED.cs:69, REDACTED.cs:16
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- 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 13 of 13 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
What to do
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
P1 · CI/CD gates
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P7 · Outbound HTTP resilience
- `builder.Services.AddHttpClient(HttpClientConstants.DefaultHttpClient, client ...` 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). — Source/Shared/Client/BuildingBlocks/Registrator.cs:21
- `builder.Services.AddHttpClient(HttpClientConstants.AuthenticatedHttpClient, c...` 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). — Source/Shared/Client/BuildingBlocks/Registrator.cs:27
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.
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
X1 · Async correctness
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 23/54 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. (×31) — Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs:67, Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs:76, Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs:86, …
- 9 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
- Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). (×7) — Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/DeleteTenant.cs:20, Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/RemoveMemberFromTenant.cs:17, Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/UpdateTenantMembership.cs:17, …
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
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — Source/Shared/Client/BuildingBlocks/Auth/HostAuthenticationStateProvider.cs:69, Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:27, Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:59, …
What to do
- Swallowed exception (empty catch)
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. — Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:35
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- This method contradicts itself about `domainException`: line 70 assigns it with `as DomainException`, which hands back null rather than throwing when the value is not a `DomainException`, but line 73 then dereferences it directly as `domainException.StatusCode` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `domainException` once before the first use and handle the null case, or cast with `(DomainException)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:73
- This method contradicts itself about `session`: line 33 assigns it with `as Stripe.Checkout.Session`, which hands back null rather than throwing when the value is not a `Stripe.Checkout.Session`, but line 35 then dereferences it directly as `session.SubscriptionId` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `session` once before the first use and handle the null case, or cast with `(Stripe.Checkout.Session)` so the failure is reported where it happens — rather than leaving the two readings side by side. — REDACTED:35
- This method contradicts itself about `invoice`: line 49 assigns it with `as Invoice`, which hands back null rather than throwing when the value is not a `Invoice`, but line 51 then dereferences it directly as `invoice.SubscriptionId` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `invoice` once before the first use and handle the null case, or cast with `(Invoice)` so the failure is reported where it happens — rather than leaving the two readings side by side. — REDACTED:51
- This method contradicts itself about `invoice`: line 63 assigns it with `as Invoice`, which hands back null rather than throwing when the value is not a `Invoice`, but line 65 then dereferences it directly as `invoice.SubscriptionId` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `invoice` once before the first use and handle the null case, or cast with `(Invoice)` so the failure is reported where it happens — rather than leaving the two readings side by side. — REDACTED:65
- 3/13 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
- Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
- 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 | 45% | Adequate — gated by X3, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 55% | Adequate — gated by AX2, AX7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 59% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 27% | Weak — gated by D9, P5, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 80% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 49% | Adequate — gated by DM1, DM2, DM6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Accessibility | 32% | Weak — gated by AC1, AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X8 JS interop contract — 2 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
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 33 check(s) not relevant to this codebase
- 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 — The runtime tier booted this repository's service, but the service booted and answers HTTP at http://127.0.0.1:40133, but serves no HTML page — nothing for the accessibility crawl. This repository also has a user interface (13 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — This is a dotnet-new template — at-rest encryption and key-vaulting are deferred to the application you build from it. Add ASP.NET Data Protection / column encryption + a key vault for your real data store when you productionise.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (967 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D24 Comment Value — Too few judgeable comments (8 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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 — This repo declares itself a template / kata / sample; tests are deferred to the application built from it, so coverage is not scored here.
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (command argument 1, install 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 73 finding(s)
- Domain depends on infrastructure: TenantAdminCreatedIntegrationEventHandler Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/EventHandlers/TenantAdminCreatedIntegrationEventHandler.cs:11
- Domain depends on infrastructure: TenantAdminCreatedIntegrationEventHandler Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/EventHandlers/TenantAdminCreatedIntegrationEventHandler.cs:13
- Domain depends on infrastructure: GetStripeCustomerByStripePortalIdQueryHandler Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:14
- Domain depends on infrastructure: GetStripeCustomerByStripePortalIdQueryHandler Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:16
- Domain depends on infrastructure: StripeCustomerEFConfiguration Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/StripeCustomer.cs:22
- Domain depends on infrastructure: StripeCustomerEFConfiguration Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/StripeCustomer.cs:24
- Domain depends on infrastructure: StripeSubscriptionEFConfiguration Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/StripeSubscription.cs:50
- Domain depends on infrastructure: StripeSubscriptionEFConfiguration Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/StripeSubscription.cs:52
- Domain depends on infrastructure: DeleteTenantCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/DeleteTenant.cs:33
- Domain depends on infrastructure: Tenant Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:37
- Domain depends on infrastructure: Tenant Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:51
- Domain depends on infrastructure: Tenant Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:58
- Domain depends on infrastructure: Tenant Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:70
- Domain depends on infrastructure: Tenant Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:76
- Domain depends on infrastructure: Tenant Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:88
- Domain depends on infrastructure: TenantEFConfiguration Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:107
- Domain depends on infrastructure: TenantEFConfiguration Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:109
- Domain depends on infrastructure: TenantInvitationEFConfiguration Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantInvitation.cs:25
- Domain depends on infrastructure: TenantInvitationEFConfiguration Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantInvitation.cs:27
- Domain depends on infrastructure: TenantMembershipEFConfiguration Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs:38
- Domain depends on infrastructure: TenantMembershipEFConfiguration Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs:40
- Domain depends on infrastructure: CreateNewUser Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs:9
- Domain depends on infrastructure: CreateNewUser Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs:10
- Domain depends on infrastructure: CreateNewUserCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs:15
- Domain depends on infrastructure: CreateNewUserCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs:16
- EmptyCatchBlock Source/Shared/Client/BuildingBlocks/Auth/HostAuthenticationStateProvider.cs:69
- EmptyCatchBlock Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:27
- EmptyCatchBlock Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:59
- EmptyCatchBlock Source/Shared/Client/BuildingBlocks/Http/HttpClientService.cs:24
- EmptyCatchBlock Source/Shared/Client/BuildingBlocks/Http/HttpClientService.cs:46
- Domain uses infrastructure in a method body: AddMemberToTenantCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/AddMemberToTenant.cs:15
- Domain uses infrastructure in a method body: CreateTenantWithAdminCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/CreateTenant.cs:15
- Domain uses infrastructure in a method body: RemoveMemberFromTenantCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/RemoveMemberFromTenant.cs:13
- Domain uses infrastructure in a method body: UpdateTenantMembershipCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/UpdateTenantMembership.cs:14
- Domain uses infrastructure in a method body: TenantSubscriptionUpdatedIntegrationEventHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/IntegrationMessageHandlers/TenantSubscriptionUpdatedIntegrationEventHandler.cs:9
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Aggregate holds a reference to another aggregate: Tenant.Memberships Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:15
- Aggregate holds a reference to another aggregate: TenantMembership.Tenant Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs:19
- Aggregate holds a reference to another aggregate: ApplicationUser.TenantMemberships Source/Modules/TenantIdentity/Features/DomainFeatures/Users/ApplicationUser.cs:17
- <img> without a text alternative Source/Shared/Client/Components/Modals/DeletionModal.razor:4
- <img> without a text alternative Source/Shared/Client/Components/Modals/ErrorModal.razor:4
- REDACTED
- REDACTED
- Routed page without a <PageTitle> Source/Web/Client/Pages/Index.razor:3
- Click handler on a non-interactive <div> Source/Shared/Client/Layouts/MainLayout/NavMenu.razor:8
- Namespace dependency cycle Source/Modules/Subscriptions/Features/Infrastructure/Configuration/SubscriptionsConfiguration.cs:1
- REDACTED
- WriteOnlyPrivateField Source/Shared/Features/EFCore/MultiTenancy/Exceptions/CrossTenantUpdateException.cs:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: TenantsController.cs ↔ IIntegrationEventHandler.cs Source/Modules/TenantIdentity/Web/Server/Controllers/TenantsController.cs:1
Serious — 176 finding(s)
- Cross-slice coupling: DomainFeatures → Messaging Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/EventHandlers/TenantAdminCreatedIntegrationEventHandler.cs:9
- Cross-slice coupling: DomainFeatures → Infrastructure Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/EventHandlers/TenantAdminCreatedIntegrationEventHandler.cs:11
- Cross-slice coupling: DomainFeatures → Messaging Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:7
- Cross-slice coupling: DomainFeatures → Messaging Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:12
- Cross-slice coupling: DomainFeatures → Infrastructure Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:14
- Cross-slice coupling: DomainFeatures → Misc Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/StripeCustomer.cs:7
- Cross-slice coupling: DomainFeatures → Messaging Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/CreateTrialingSubscription.cs:9
- Cross-slice coupling: DomainFeatures → Misc Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/CreateTrialingSubscription.cs:16
- Cross-slice coupling: DomainFeatures → Messaging Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/CreateTrialingSubscription.cs:16
- Cross-slice coupling: DomainFeatures → Messaging Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/PauseActiveSubscription.cs:7
- Cross-slice coupling: DomainFeatures → Misc Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/PauseActiveSubscription.cs:12
- Cross-slice coupling: DomainFeatures → Messaging Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/PauseActiveSubscription.cs:12
- Cross-slice coupling: DomainFeatures → Messaging Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/UpdateSubscriptionPeriod.cs:7
- Cross-slice coupling: DomainFeatures → Misc Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/UpdateSubscriptionPeriod.cs:12
- Cross-slice coupling: DomainFeatures → Messaging Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/UpdateSubscriptionPeriod.cs:12
- Cross-slice coupling: DomainFeatures → Messaging Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Queries/GetSubscriptionForTenant.cs:5
- Cross-slice coupling: DomainFeatures → Misc Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/StripeSubscription.cs:9
- Cross-slice coupling: Infrastructure → Misc Source/Modules/Subscriptions/Features/Infrastructure/Configuration/SubscriptionsConfiguration.cs:7
- Cross-slice coupling: Infrastructure → Misc Source/Modules/Subscriptions/Features/Infrastructure/Configuration/SubscriptionsConfigurationValidator.cs:6
- Cross-slice coupling: Infrastructure → EFCore Source/Modules/Subscriptions/Features/Infrastructure/EFCore/SubscriptionsDbContext.cs:8
- Cross-slice coupling: Infrastructure → DomainFeatures Source/Modules/Subscriptions/Features/Infrastructure/EFCore/SubscriptionsDbContext.cs:17
- Cross-slice coupling: Infrastructure → DomainFeatures Source/Modules/Subscriptions/Features/Infrastructure/EFCore/SubscriptionsDbContext.cs:18
- Cross-slice coupling: Infrastructure → Messaging Source/Modules/Subscriptions/Features/Infrastructure/StripePayments/CreateStripeBillingPortalSession.cs:8
- Cross-slice coupling: Infrastructure → Messaging Source/Modules/Subscriptions/Features/Infrastructure/StripePayments/CreateStripeBillingPortalSession.cs:14
- Cross-slice coupling: Infrastructure → Messaging Source/Modules/Subscriptions/Features/Infrastructure/StripePayments/CreateStripeCheckoutSession.cs:10
- Dead code: IUserIdentifiable Source/Shared/Kernel/DomainKernel/Interfaces/IUserIdentifiable.cs:3
- Dead code: HasUserIdClaim Source/Shared/Kernel/Extensions/ClaimsPrincipal/ClaimsPrincipalExtensions.cs:10
- Dead code: HasTenantIdClaim Source/Shared/Kernel/Extensions/ClaimsPrincipal/ClaimsPrincipalExtensions.cs:21
- Dead code: GetRoleClaim Source/Shared/Kernel/Extensions/ClaimsPrincipal/ClaimsPrincipalExtensions.cs:42
- Dead code: UserIdClaimNotFoundException Source/Shared/Kernel/Extensions/ClaimsPrincipal/Exceptions/UserIdClaimNotFoundException.cs:3
- Dead code: ToGuid Source/Shared/Kernel/Extensions/StringExtensions.cs:5
- Dead code: RevokeUserInvitationToTenantDTO Source/Modules/TenantIdentity/Public/DTOs/Tenant/Operations/RevokeUserInvitationToTenantDTO.cs:3
- Dead code: TenantExtendedDTO Source/Modules/TenantIdentity/Public/DTOs/Tenant/TenantExtendedDTO.cs:5
- Dead code: TenantAdminEmailUpdatedEvent Source/Modules/TenantIdentity/Public/IntegrationMessages/TenantAdminEmailUpdatedEvent.cs:6
- Dead code: AddMemberToTenantCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/AddMemberToTenant.cs:15
- Dead code: CreateTenantWithAdminCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/CreateTenant.cs:15
- Dead code: DeleteTenantCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/DeleteTenant.cs:16
- Dead code: RemoveMemberFromTenantCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/RemoveMemberFromTenant.cs:13
- Dead code: UpdateTenantMembershipCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/UpdateTenantMembership.cs:14
- Dead code: TenantSubscriptionUpdatedIntegrationEventHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/IntegrationMessageHandlers/TenantSubscriptionUpdatedIntegrationEventHandler.cs:9
- Dead code: GetAllTenantMembershipsOfUserQueryHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetAllTenantMembershipsOfUser.cs:11
- Dead code: GetTenantByIdQueryHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetTenant.cs:13
- Dead code: InviteUser Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:82
- Dead code: CreateNewUserCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/CreateNewUser.cs:13
- Dead code: SelectedTenantCommandHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/SelectTenant.cs:12
- Dead code: UpdateUser Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Commands/UpdateUser.cs:6
- Dead code: ClaimsForUserQueryHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetClaimsForExecutingUser.cs:13
- Dead code: GetUserByIdHandler Source/Modules/TenantIdentity/Features/DomainFeatures/Users/Application/Queries/GetExecutingUser.cs:10
- Dead code: SendIntegrationRequestAsync Source/Shared/Features/Messaging/IntegrationMessages/IIntegrationMessageDispatcher.cs:9
- Dead code: SendNotificationAsync Source/Shared/Features/SignalR/INotificationHubService.cs:5
- Async method without CancellationToken: GetAllTenantsForUser Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs:67
- Async method without CancellationToken: GetUserByIdAsync Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs:76
- Async method without CancellationToken: GetTenantByIdAsync Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs:86
- Async method without CancellationToken: GetTenantExtendedByIdAsync Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs:96
- Async method without CancellationToken: ExternalLoginCallback Source/Modules/TenantIdentity/Web/Server/Controllers/Infrastructure/ExternalLoginCallbackController.cs:28
- Async method without CancellationToken: SelectTenant Source/Modules/TenantIdentity/Web/Server/Controllers/Infrastructure/IdentityOperationsController.cs:46
- Async method without CancellationToken: GetTenant Source/Modules/TenantIdentity/Web/Server/Controllers/TenantsController.cs:30
- Async method without CancellationToken: CreateTenant Source/Modules/TenantIdentity/Web/Server/Controllers/TenantsController.cs:38
- Async method without CancellationToken: DeleteTenant Source/Modules/TenantIdentity/Web/Server/Controllers/TenantsController.cs:56
- Async method without CancellationToken: AddMemberToTenant Source/Modules/TenantIdentity/Web/Server/Controllers/TenantsController.cs:69
- Async method without CancellationToken: UpdateTenantMembership Source/Modules/TenantIdentity/Web/Server/Controllers/TenantsController.cs:84
- Async method without CancellationToken: RemoveMemberFromTenant Source/Modules/TenantIdentity/Web/Server/Controllers/TenantsController.cs:99
- Async method without CancellationToken: GetEntityAsync Source/Shared/Features/EFCore/DbSetExtensions.cs:10
- Async method without CancellationToken: GetEntityAsync Source/Shared/Features/EFCore/DbSetExtensions.cs:21
- Async method without CancellationToken: SendEmailAsync Source/Shared/Features/EmailSender/Services/SendGridEmailSender.cs:22
- Async method without CancellationToken: Execute Source/Shared/Features/EmailSender/Services/SendGridEmailSender.cs:31
- Async method without CancellationToken: SendNotificationAsync Source/Shared/Features/SignalR/NotificationHubService.cs:14
- Async method without CancellationToken: CarouselInitAsync REDACTED.cs:52
- Async method without CancellationToken: RedirectToStripePremiumSubscription Source/Modules/Subscriptions/Web/Server/Controllers/StripeSessionController.cs:18
- Async method without CancellationToken: Create Source/Modules/Subscriptions/Web/Server/Controllers/StripeSessionController.cs:35
- Async method without CancellationToken: OrderSuccess REDACTED:25
- Async method without CancellationToken: Index REDACTED:19
- Async method without CancellationToken: GetAntiforgeryTokenAsync Source/Shared/Client/BuildingBlocks/Auth/Antiforgery/AntiforgeryTokenService.cs:12
- Async method without CancellationToken: GetUser Source/Shared/Client/BuildingBlocks/Auth/HostAuthenticationStateProvider.cs:32
- Async method without CancellationToken: FetchUser Source/Shared/Client/BuildingBlocks/Auth/HostAuthenticationStateProvider.cs:46
- Deprecated: Azure.Identity REDACTED:9
- Deprecated: Microsoft.AspNetCore.Mvc.Versioning REDACTED:11
- Deprecated: Microsoft.AspNetCore.Mvc.Core REDACTED:10
- Deprecated: Microsoft.AspNetCore.Mvc.Core Source/Modules/TenantIdentity/Web/Server/Modules.TenantIdentity.Web.Server.csproj:8
- Deprecated: Microsoft.AspNetCore.Hosting.Server.Abstractions REDACTED:10
- Deprecated: Microsoft.AspNetCore.Http.Abstractions REDACTED:11
- Deprecated: Microsoft.AspNetCore.Identity REDACTED:12
- Deprecated: Microsoft.AspNetCore.Identity REDACTED:10
- Deprecated: Microsoft.AspNetCore.Mvc.ViewFeatures REDACTED:11
- Deprecated: Blazored.Modal Source/Shared/Client/Shared.Client.csproj:23
- Fake-async — async method never awaits REDACTED.cs:28
- Fake-async — async method never awaits REDACTED.cs:39
- Fake-async — async method never awaits Source/Modules/Subscriptions/Web/Server/Controllers/StripeSubscriptionsController.cs:18
- Fake-async — async method never awaits Source/Shared/Features/EFCore/DbUp/Registrator.cs:12
- Fake-async — async method never awaits Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:48
- Fake-async — async method never awaits Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:58
- Fake-async — async method never awaits Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:68
- Fake-async — async method never awaits Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:79
- Async method drops its CancellationToken: HandleAsync Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/DeleteTenant.cs:20
- Async method drops its CancellationToken: HandleAsync Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/RemoveMemberFromTenant.cs:17
- Async method drops its CancellationToken: HandleAsync Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/UpdateTenantMembership.cs:17
- Async method drops its CancellationToken: HandleAsync Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/IntegrationMessageHandlers/TenantSubscriptionUpdatedIntegrationEventHandler.cs:13
- Async method drops its CancellationToken: HandleAsync Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Queries/GetAllTenantMembershipsOfUser.cs:15
- Async method drops its CancellationToken: HandleAsync Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/EventHandlers/TenantAdminCreatedIntegrationEventHandler.cs:18
- Async method drops its CancellationToken: HandleAsync Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/Application/Queries/GetStripeCustomerByStripePortalId.cs:21
- Swallowed exception (empty catch) Source/Shared/Client/BuildingBlocks/Auth/HostAuthenticationStateProvider.cs:69
- Swallowed exception (empty catch) Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:27
- Swallowed exception (empty catch) Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:59
- Swallowed exception (empty catch) Source/Shared/Client/BuildingBlocks/Http/HttpClientService.cs:24
- Swallowed exception (empty catch) Source/Shared/Client/BuildingBlocks/Http/HttpClientService.cs:46
- CommentedOutCode REDACTED.cs:41
- CommentedOutCode REDACTED.cs:46
- CommentedOutCode REDACTED.cs:71
- CommentedOutCode REDACTED.cs:18
- Symbol treated as nullable, then dereferenced unguarded Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:73
- Symbol treated as nullable, then dereferenced unguarded REDACTED:35
- Symbol treated as nullable, then dereferenced unguarded REDACTED:51
- Symbol treated as nullable, then dereferenced unguarded REDACTED:65
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change coupling: IIntegrationEventHandler.cs ↔ BaseController.cs Source/Shared/Features/Messaging/IntegrationMessages/IIntegrationEventHandler.cs:1
- Change coupling: BaseController.cs ↔ ServerExecutionContext.cs Source/Shared/Features/Misc/BaseController.cs:1
- Change coupling: Registrator.cs ↔ Startup.cs Source/Shared/Features/Misc/Modules/Registrator.cs:1
- Focus outline removed in CSS without a :focus replacement Source/Web/Server/wwwroot/css/site.css:2
- Focus outline removed in CSS without a :focus replacement Source/Web/Server/wwwroot/css/site.css:49
- Non-idempotent mutation: Commands.CreateTenantWithAdminCommandHandler.HandleAsync Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Application/Commands/CreateTenant.cs:19
- Non-idempotent mutation: Commands.CreateTrialingSubscriptionCommandHandler.HandleAsync Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/Application/Commands/CreateTrialingSubscription.cs:20
- Outbound HTTP without resilience Source/Shared/Client/BuildingBlocks/Registrator.cs:21
- Outbound HTTP without resilience Source/Shared/Client/BuildingBlocks/Registrator.cs:27
- Unresolved JS interop binding Source/Shared/Client/BuildingBlocks/Auth/Antiforgery/AntiforgeryTokenService.cs:14
- Unresolved JS interop binding Source/Shared/Client/BuildingBlocks/Auth/Antiforgery/AntiforgeryTokenInput.razor:15
- Page without a main landmark Source/Shared/Client/Layouts/MainLayout/MainLayout.razor:6
- Accessibility enforcement below the top rung Source/package.json:1
- Stateful singleton: HostAuthenticationStateProvider Source/Shared/Client/BuildingBlocks/Auth/HostAuthenticationStateProvider.cs:12
- Prerelease dependency: Stripe.net
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:19
- Duplicated block (19 lines × 2) Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:52
- Duplicated block (15 lines × 2) Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:20
- Duplicated block (14 lines × 4) Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:21
- Duplicated block (11 lines × 2) Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:74
- Off the main sequence: Modules.TenantIdentity.Public Source/Modules/TenantIdentity/Public/Modules.TenantIdentity.Public.csproj:1
- Low cohesion: TenantIdentityDbContext (LCOM4 4) Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs:15
- Anemic entity: TenantMembership Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs:9
- No DR/backup evidence
- NuGet dependencies are not locked
Minor — 51 finding(s)
- Orphaned file Source/Modules/TenantIdentity/Web/Server/TenantIdentityModuleStartup.cs:1
- Orphaned file Source/Modules/TenantIdentity/Features/Infrastructure/EFCore/TenantIdentityDbContext.cs:1
- Orphaned file Source/Shared/Features/EFCore/BaseDbContext.cs:1
- Orphaned file Source/Modules/TenantIdentity/Web/Server/Controllers/TenantsController.cs:1
- Orphaned file Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:1
- Orphaned file Source/Shared/Client/BuildingBlocks/Auth/HostAuthenticationStateProvider.cs:1
- Orphaned file Source/Shared/Client/BuildingBlocks/Http/AuthorizedHttpClientService.cs:1
- Orphaned file Source/Shared/Client/BuildingBlocks/Http/HttpClientService.cs:1
- Orphaned file REDACTED:1
- Orphaned file Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:1
- Orphaned file Source/Shared/Client/Types/ProblemDetails.cs:1
- Orphaned file Source/Modules/Subscriptions/Features/Infrastructure/StripePayments/CreateStripeCheckoutSession.cs:1
- Orphaned file Source/Shared/Features/Messaging/Registrator.cs:1
- Orphaned file Source/Modules/TenantIdentity/Web/Server/Controllers/Infrastructure/IdentityOperationsController.cs:1
- Orphaned file REDACTED.cs:1
- Orphaned file Source/Shared/Kernel/Extensions/ClaimsPrincipal/ClaimsPrincipalExtensions.cs:1
- Orphaned file Source/Modules/TenantIdentity/Web/Server/Controllers/Infrastructure/ExternalLoginCallbackController.cs:1
- Orphaned file Source/Web/Server/Startup.cs:1
- Commented-out code Source/Modules/LandingPages/Server/LandingPagesLayout.razor.cs:31
- Commented-out code REDACTED.cs:43
- Commented-out code REDACTED.cs:48
- Commented-out code REDACTED.cs:76
- Commented-out code REDACTED.cs:23
- Commented-out code Source/Shared/Client/BuildingBlocks/Auth/HostAuthenticationStateProvider.cs:24
- Commented-out code Source/Shared/Features/EmailSender/Registrator.cs:11
- Commented-out code Source/Shared/Features/Misc/Services/ModelValidation/ValidationService.cs:23
- Commented-out code Source/Shared/Features/Misc/Services/ModelValidation/ValidationService.cs:38
- Primitive id on a domain type: TenantMembership.UserId Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantMembership.cs:18
- Primitive id on a domain type: StripeCustomer.UserId Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/StripeCustomer.cs:9
- Primitive id on a domain type: StripeCustomer.StripePortalCustomerId Source/Modules/Subscriptions/Features/DomainFeatures/StripeCustomers/StripeCustomer.cs:10
- Primitive id on a domain type: StripeSubscription.StripePortalSubscriptionId Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/StripeSubscription.cs:13
- Primitive id on a domain type: StripeSubscription.StripeCustomerId Source/Modules/Subscriptions/Features/DomainFeatures/StripeSubscriptions/StripeSubscription.cs:14
- Empty method body Source/Modules/LandingPages/Server/LandingPagesLayout.razor.cs:24
- Empty method body REDACTED.cs:69
- Empty method body REDACTED.cs:16
- Outdated: Swashbuckle.AspNetCore REDACTED:16
- Outdated: Stripe.net Source/Modules/Subscriptions/Features/Modules.Subscriptions.Features.csproj:10
- Endpoints outside the guard REDACTED:25
- Partial audit-trail evidence
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No tests — template/sample
- No tests found
- Mutable entity: Tenant Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/Tenant.cs:11
- No ADRs
- No rollback/health safety
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
- Interpolated log message defeats structured logging Source/Web/Server/BuildingBlocks/ExceptionHandling/ExceptionHandler.cs:35
- Nullable reference types not enabled everywhere
Minor — 35 finding(s)
- Outdated: Azure.Extensions.AspNetCore.Configuration.Secrets
- Outdated: Azure.Identity
- Outdated: Microsoft.AspNetCore.Components.WebAssembly.Server
- Outdated: Microsoft.EntityFrameworkCore.Design
- Outdated: Microsoft.AspNetCore.Components.WebAssembly
- Outdated: Microsoft.AspNetCore.Components.WebAssembly.DevServer
- Outdated: Microsoft.AspNetCore.Mvc.Core
- Outdated: Microsoft.Extensions.Http
- Outdated: System.Net.Http.Json
- Outdated: FluentValidation
- Outdated: Microsoft.AspNetCore.Authorization
- Outdated: Microsoft.AspNetCore.Hosting.Server.Abstractions
- Outdated: Microsoft.AspNetCore.Http.Abstractions
- Outdated: Microsoft.Extensions.Hosting
- Outdated: AspNet.Security.OAuth.LinkedIn
- Outdated: Microsoft.AspNetCore.Authentication.Google
- Outdated: Microsoft.AspNetCore.Authentication.MicrosoftAccount
- Outdated: Microsoft.AspNetCore.Authentication.OpenIdConnect
- Outdated: Microsoft.AspNetCore.Identity
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore
- Outdated: Microsoft.AspNetCore.Components
- Outdated: Microsoft.AspNetCore.Components.Authorization
- Outdated: dbup-core
- Outdated: dbup-sqlserver
- Outdated: Microsoft.EntityFrameworkCore
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-6dec0ca96b60493f98152fa42044c235/history.json --exit-code 0 --source . | 3 | 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-6dec0ca96b60493f98152fa42044c235/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude Source/Modules/TenantIdentity/Features/Migrations . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list ModularMonolith.sln package --vulnerable --include-transitive --format json | 6 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
Appendix C — Personal-data map
Email — 3 field(s)
- TenantInvitation.Email Source/Modules/TenantIdentity/Features/DomainFeatures/Tenants/Domain/TenantInvitation.cs:11
- TenantAdminCreatedEvent.Email Source/Modules/TenantIdentity/Public/IntegrationMessages/TenantAdminCreatedEvent.cs:10
- TenantAdminEmailUpdatedEvent.Email Source/Modules/TenantIdentity/Public/IntegrationMessages/TenantAdminEmailUpdatedEvent.cs:10