Executive summary
amantinband/clean-architecture falls short of our standard for a template or a sample because its Explicit debt dimensions are rated Critical, and it has analysis rules switched off in the settings. It scores 57 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Code Health, at 50, is the weakest lens and counts most in the score. The best first steps are handling the discarded errors and removing the unread values, each worth about 6 points. Raising Code Health to 63 would lift the score to about 62.
Nine passwords or keys are open to anyone who can read the repository. Six known security holes in the packages the code depends on can be used by attackers. Replacing each exposed password or key and updating the vulnerable packages would close both risks. Pinning each tool to an exact version would fix the five pipeline tools referenced by a changeable name, and limiting each secret to its own step would deal with the two secrets exposed to more of the pipeline than needed. The 18 analysis rules switched off in the settings need switching back on in the settings file.
The product code is 1,781 lines, about €6,700 to rebuild.
If Code Health rose from 50 to 63, the lowest score rated Strong, the score would rise from 57 to about 62.
New since the last survey: 1 finding
- Test Reliability · Flaky test: CleanArchitecture.Api.IntegrationTests::CleanArchitecture.Api.IntegrationTests.Controllers.CreateSubscriptionTests.CleanArchitecture.Api.IntegrationTests.Controllers.CreateSubscriptionTests.CreateSubscriptionForSelf_WhenHasPermission_ShouldCreateSubscription(subscriptionType: Pro) tests/CleanArchitecture.Api.IntegrationTests/Controllers/SubscriptionControllers.CreateSubscriptionTests.cs
Fixed since the last survey: 25 findings
- Static Analysis (SAST) · Medium: missing-or-broken-authorization src/CleanArchitecture.Api/Controllers/TokensController.cs
- Rich vs anemic model · Anemic entity: Subscription src/CleanArchitecture.Domain/Users/Subscription.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Common/Persistence/AppDbContext.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Common/Persistence/AppDbContext.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Common/Persistence/AppDbContext.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Common/Persistence/AppDbContext.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/ReminderEmailBackgroundService.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Reminders/Persistence/RemindersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Reminders/Persistence/RemindersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Reminders/Persistence/RemindersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Reminders/Persistence/RemindersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Reminders/Persistence/RemindersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Reminders/Persistence/RemindersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Reminders/Persistence/RemindersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Users/Persistence/UsersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Users/Persistence/UsersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Users/Persistence/UsersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Users/Persistence/UsersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Users/Persistence/UsersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/CleanArchitecture.Infrastructure/Users/Persistence/UsersRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tests/TestCommon/Reminders/MediatorExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tests/TestCommon/Reminders/MediatorExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tests/TestCommon/Reminders/MediatorExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tests/TestCommon/Subscriptions/MediatorExtensions.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) tests/TestCommon/Subscriptions/MediatorExtensions.cs
Rebuild cost: about €6,700 · Estimate
| Cost to rebuild | €2,200 to €11,000, for 37 to 118 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.8 at a score of 57. 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 | Very small: 1,781 lines of product code, of which 53% is declarations and boilerplate, 31% straight logic and 16% 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 CleanArchitecture.Api | 3 CleanArchitecture.Application | 4 CleanArchitecture.Application.Common.Security.Request | 5 CleanArchitecture.Contracts.Common | 6 CleanArchitecture.Contracts.Reminders | 7 CleanArchitecture.Domain.Common | 8 CleanArchitecture.Infrastructure.Security.CurrentUserProvider | 9 CleanArchitecture.Contracts.Subscriptions | 10 CleanArchitecture.Contracts.Tokens | 11 CleanArchitecture.Domain.Reminders | 12 CleanArchitecture.Domain.Subscriptions | 13 CleanArchitecture.Infrastructure.Security.PolicyEnforcer | 14 CleanArchitecture.Domain.Users | 15 CleanArchitecture.Application.Authentication.Queries.Login | 16 CleanArchitecture.Application.Common.Interfaces | 17 CleanArchitecture.Application.Subscriptions.Common | 18 CleanArchitecture.Domain.Users.Events | 19 CleanArchitecture.Infrastructure.Common | 20 CleanArchitecture.Api.Controllers | 21 CleanArchitecture.Application.Common.Behaviors | 22 CleanArchitecture.Application.Reminders.Commands.DeleteReminder | 23 CleanArchitecture.Application.Reminders.Commands.DismissReminder | 24 CleanArchitecture.Application.Reminders.Commands.SetReminder | 25 CleanArchitecture.Application.Reminders.Events | 26 CleanArchitecture.Application.Reminders.Queries.GetReminder | 27 CleanArchitecture.Application.Reminders.Queries.ListReminders | 28 CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription | 29 CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription | 30 CleanArchitecture.Application.Subscriptions.Events | 31 CleanArchitecture.Application.Subscriptions.Queries.GetSubscription | 32 CleanArchitecture.Application.Tokens.Queries.Generate | 33 CleanArchitecture.Infrastructure.Common.Middleware | 34 CleanArchitecture.Infrastructure.Reminders.BackgroundServices | 35 CleanArchitecture.Infrastructure.Reminders.Persistence | 36 CleanArchitecture.Infrastructure.Security | 37 CleanArchitecture.Infrastructure.Security.TokenGenerator | 38 CleanArchitecture.Infrastructure.Services | 39 CleanArchitecture.Infrastructure.Users.Persistence | 40 CleanArchitecture.Infrastructure.Security.TokenValidation |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 CleanArchitecture.Api | ||||||||||||||||||||||||||||||||||||||||
| 3 CleanArchitecture.Application | ||||||||||||||||||||||||||||||||||||||||
| 4 CleanArchitecture.Application.Common.Security.Request | ||||||||||||||||||||||||||||||||||||||||
| 5 CleanArchitecture.Contracts.Common | ||||||||||||||||||||||||||||||||||||||||
| 6 CleanArchitecture.Contracts.Reminders | ||||||||||||||||||||||||||||||||||||||||
| 7 CleanArchitecture.Domain.Common | ||||||||||||||||||||||||||||||||||||||||
| 8 CleanArchitecture.Infrastructure.Security.CurrentUserProvider | ||||||||||||||||||||||||||||||||||||||||
| 9 CleanArchitecture.Contracts.Subscriptions | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 CleanArchitecture.Contracts.Tokens | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 CleanArchitecture.Domain.Reminders | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 CleanArchitecture.Domain.Subscriptions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 CleanArchitecture.Infrastructure.Security.PolicyEnforcer | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 CleanArchitecture.Domain.Users | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 CleanArchitecture.Application.Authentication.Queries.Login | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 CleanArchitecture.Application.Common.Interfaces | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 CleanArchitecture.Application.Subscriptions.Common | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 CleanArchitecture.Domain.Users.Events | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 CleanArchitecture.Infrastructure.Common | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 CleanArchitecture.Api.Controllers | 2 | 2 | 2 | 2 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 21 CleanArchitecture.Application.Common.Behaviors | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 CleanArchitecture.Application.Reminders.Commands.DeleteReminder | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 CleanArchitecture.Application.Reminders.Commands.DismissReminder | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 CleanArchitecture.Application.Reminders.Commands.SetReminder | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 25 CleanArchitecture.Application.Reminders.Events | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 26 CleanArchitecture.Application.Reminders.Queries.GetReminder | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 CleanArchitecture.Application.Reminders.Queries.ListReminders | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 CleanArchitecture.Application.Subscriptions.Events | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 CleanArchitecture.Application.Subscriptions.Queries.GetSubscription | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 CleanArchitecture.Application.Tokens.Queries.Generate | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 CleanArchitecture.Infrastructure.Common.Middleware | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 CleanArchitecture.Infrastructure.Reminders.BackgroundServices | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 CleanArchitecture.Infrastructure.Reminders.Persistence | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 CleanArchitecture.Infrastructure.Security | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 CleanArchitecture.Infrastructure.Security.TokenGenerator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 CleanArchitecture.Infrastructure.Services | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 CleanArchitecture.Infrastructure.Users.Persistence | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 CleanArchitecture.Infrastructure.Security.TokenValidation | 1 |
9→5 CleanArchitecture.Contracts.Subscriptions uses CleanArchitecture.Contracts.Common✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Contracts.Subscriptions uses a type in CleanArchitecture.Contracts.Common.
- The types involved
CleanArchitecture.Contracts.Subscriptions.CreateSubscriptionRequest→CleanArchitecture.Contracts.Common.SubscriptionTypeCleanArchitecture.Contracts.Subscriptions.SubscriptionResponse→CleanArchitecture.Contracts.Common.SubscriptionType
- Direction
- CleanArchitecture.Contracts.Subscriptions uses CleanArchitecture.Contracts.Common, so a change to CleanArchitecture.Contracts.Common can break CleanArchitecture.Contracts.Subscriptions, while a change to CleanArchitecture.Contracts.Subscriptions can't break CleanArchitecture.Contracts.Common.
- Position
- Below the diagonal: CleanArchitecture.Contracts.Subscriptions uses a module listed above it, which is the healthy direction.
10→5 CleanArchitecture.Contracts.Tokens uses CleanArchitecture.Contracts.Common✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Contracts.Tokens uses a type in CleanArchitecture.Contracts.Common.
- The types involved
CleanArchitecture.Contracts.Tokens.GenerateTokenRequest→CleanArchitecture.Contracts.Common.SubscriptionTypeCleanArchitecture.Contracts.Tokens.TokenResponse→CleanArchitecture.Contracts.Common.SubscriptionType
- Direction
- CleanArchitecture.Contracts.Tokens uses CleanArchitecture.Contracts.Common, so a change to CleanArchitecture.Contracts.Common can break CleanArchitecture.Contracts.Tokens, while a change to CleanArchitecture.Contracts.Tokens can't break CleanArchitecture.Contracts.Common.
- Position
- Below the diagonal: CleanArchitecture.Contracts.Tokens uses a module listed above it, which is the healthy direction.
11→7 CleanArchitecture.Domain.Reminders uses CleanArchitecture.Domain.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Domain.Reminders uses a type in CleanArchitecture.Domain.Common.
- The types involved
CleanArchitecture.Domain.Reminders.Reminder→CleanArchitecture.Domain.Common.Entity
- Direction
- CleanArchitecture.Domain.Reminders uses CleanArchitecture.Domain.Common, so a change to CleanArchitecture.Domain.Common can break CleanArchitecture.Domain.Reminders, while a change to CleanArchitecture.Domain.Reminders can't break CleanArchitecture.Domain.Common.
- Position
- Below the diagonal: CleanArchitecture.Domain.Reminders uses a module listed above it, which is the healthy direction.
12→7 CleanArchitecture.Domain.Subscriptions uses CleanArchitecture.Domain.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Domain.Subscriptions uses a type in CleanArchitecture.Domain.Common.
- The types involved
CleanArchitecture.Domain.Subscriptions.Subscription→CleanArchitecture.Domain.Common.Entity
- Direction
- CleanArchitecture.Domain.Subscriptions uses CleanArchitecture.Domain.Common, so a change to CleanArchitecture.Domain.Common can break CleanArchitecture.Domain.Subscriptions, while a change to CleanArchitecture.Domain.Subscriptions can't break CleanArchitecture.Domain.Common.
- Position
- Below the diagonal: CleanArchitecture.Domain.Subscriptions uses a module listed above it, which is the healthy direction.
12→14 CleanArchitecture.Domain.Subscriptions uses CleanArchitecture.Domain.Users part of a loop✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Domain.Subscriptions uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Domain.Subscriptions.Subscription→CleanArchitecture.Domain.Users.SubscriptionType
- Direction
- CleanArchitecture.Domain.Subscriptions uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Domain.Subscriptions, while a change to CleanArchitecture.Domain.Subscriptions can't break CleanArchitecture.Domain.Users.
- 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.
13→4 CleanArchitecture.Infrastructure.Security.PolicyEnforcer uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Security.PolicyEnforcer uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Infrastructure.Security.PolicyEnforcer.IPolicyEnforcer→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequestCleanArchitecture.Infrastructure.Security.PolicyEnforcer.PolicyEnforcer→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Infrastructure.Security.PolicyEnforcer uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Infrastructure.Security.PolicyEnforcer, while a change to CleanArchitecture.Infrastructure.Security.PolicyEnforcer can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Security.PolicyEnforcer uses a module listed above it, which is the healthy direction.
13→8 CleanArchitecture.Infrastructure.Security.PolicyEnforcer uses CleanArchitecture.Infrastructure.Security.CurrentUserProvider✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Security.PolicyEnforcer uses a type in CleanArchitecture.Infrastructure.Security.CurrentUserProvider.
- The types involved
CleanArchitecture.Infrastructure.Security.PolicyEnforcer.IPolicyEnforcer→CleanArchitecture.Infrastructure.Security.CurrentUserProvider.CurrentUserCleanArchitecture.Infrastructure.Security.PolicyEnforcer.PolicyEnforcer→CleanArchitecture.Infrastructure.Security.CurrentUserProvider.CurrentUser
- Direction
- CleanArchitecture.Infrastructure.Security.PolicyEnforcer uses CleanArchitecture.Infrastructure.Security.CurrentUserProvider, so a change to CleanArchitecture.Infrastructure.Security.CurrentUserProvider can break CleanArchitecture.Infrastructure.Security.PolicyEnforcer, while a change to CleanArchitecture.Infrastructure.Security.PolicyEnforcer can't break CleanArchitecture.Infrastructure.Security.CurrentUserProvider.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Security.PolicyEnforcer uses a module listed above it, which is the healthy direction.
14→7 CleanArchitecture.Domain.Users uses CleanArchitecture.Domain.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Domain.Users uses a type in CleanArchitecture.Domain.Common.
- The types involved
CleanArchitecture.Domain.Users.User→CleanArchitecture.Domain.Common.Entity
- Direction
- CleanArchitecture.Domain.Users uses CleanArchitecture.Domain.Common, so a change to CleanArchitecture.Domain.Common can break CleanArchitecture.Domain.Users, while a change to CleanArchitecture.Domain.Users can't break CleanArchitecture.Domain.Common.
- Position
- Below the diagonal: CleanArchitecture.Domain.Users uses a module listed above it, which is the healthy direction.
14→11 CleanArchitecture.Domain.Users uses CleanArchitecture.Domain.Reminders✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Domain.Users uses a type in CleanArchitecture.Domain.Reminders.
- The types involved
CleanArchitecture.Domain.Users.User→CleanArchitecture.Domain.Reminders.Reminder
- Direction
- CleanArchitecture.Domain.Users uses CleanArchitecture.Domain.Reminders, so a change to CleanArchitecture.Domain.Reminders can break CleanArchitecture.Domain.Users, while a change to CleanArchitecture.Domain.Users can't break CleanArchitecture.Domain.Reminders.
- Position
- Below the diagonal: CleanArchitecture.Domain.Users uses a module listed above it, which is the healthy direction.
14→12 CleanArchitecture.Domain.Users uses CleanArchitecture.Domain.Subscriptions✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Domain.Users uses a type in CleanArchitecture.Domain.Subscriptions.
- The types involved
CleanArchitecture.Domain.Users.User→CleanArchitecture.Domain.Subscriptions.Subscription
- Direction
- CleanArchitecture.Domain.Users uses CleanArchitecture.Domain.Subscriptions, so a change to CleanArchitecture.Domain.Subscriptions can break CleanArchitecture.Domain.Users, while a change to CleanArchitecture.Domain.Users can't break CleanArchitecture.Domain.Subscriptions.
- Position
- Below the diagonal: CleanArchitecture.Domain.Users uses a module listed above it, which is the healthy direction.
15→14 CleanArchitecture.Application.Authentication.Queries.Login uses CleanArchitecture.Domain.Users✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Authentication.Queries.Login uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Application.Authentication.Queries.Login.GenerateTokenResult→CleanArchitecture.Domain.Users.SubscriptionType
- Direction
- CleanArchitecture.Application.Authentication.Queries.Login uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Application.Authentication.Queries.Login, while a change to CleanArchitecture.Application.Authentication.Queries.Login can't break CleanArchitecture.Domain.Users.
- Position
- Below the diagonal: CleanArchitecture.Application.Authentication.Queries.Login uses a module listed above it, which is the healthy direction.
16→4 CleanArchitecture.Application.Common.Interfaces uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Common.Interfaces uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Application.Common.Interfaces.IAuthorizationService→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Application.Common.Interfaces uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Application.Common.Interfaces, while a change to CleanArchitecture.Application.Common.Interfaces can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Application.Common.Interfaces uses a module listed above it, which is the healthy direction.
16→11 CleanArchitecture.Application.Common.Interfaces uses CleanArchitecture.Domain.Reminders✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Common.Interfaces uses a type in CleanArchitecture.Domain.Reminders.
- The types involved
CleanArchitecture.Application.Common.Interfaces.IRemindersRepository→CleanArchitecture.Domain.Reminders.Reminder
- Direction
- CleanArchitecture.Application.Common.Interfaces uses CleanArchitecture.Domain.Reminders, so a change to CleanArchitecture.Domain.Reminders can break CleanArchitecture.Application.Common.Interfaces, while a change to CleanArchitecture.Application.Common.Interfaces can't break CleanArchitecture.Domain.Reminders.
- Position
- Below the diagonal: CleanArchitecture.Application.Common.Interfaces uses a module listed above it, which is the healthy direction.
16→14 CleanArchitecture.Application.Common.Interfaces uses CleanArchitecture.Domain.Users✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Common.Interfaces uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Application.Common.Interfaces.IJwtTokenGenerator→CleanArchitecture.Domain.Users.SubscriptionTypeCleanArchitecture.Application.Common.Interfaces.IUsersRepository→CleanArchitecture.Domain.Users.User
- Direction
- CleanArchitecture.Application.Common.Interfaces uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Application.Common.Interfaces, while a change to CleanArchitecture.Application.Common.Interfaces can't break CleanArchitecture.Domain.Users.
- Position
- Below the diagonal: CleanArchitecture.Application.Common.Interfaces uses a module listed above it, which is the healthy direction.
17→14 CleanArchitecture.Application.Subscriptions.Common uses CleanArchitecture.Domain.Users✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Subscriptions.Common uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Application.Subscriptions.Common.SubscriptionResult→CleanArchitecture.Domain.Users.SubscriptionTypeCleanArchitecture.Application.Subscriptions.Common.SubscriptionResult→CleanArchitecture.Domain.Users.User
- Direction
- CleanArchitecture.Application.Subscriptions.Common uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Application.Subscriptions.Common, while a change to CleanArchitecture.Application.Subscriptions.Common can't break CleanArchitecture.Domain.Users.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Common uses a module listed above it, which is the healthy direction.
18→7 CleanArchitecture.Domain.Users.Events uses CleanArchitecture.Domain.Common✕
- Connections
- 4 pairs of types, where a type in CleanArchitecture.Domain.Users.Events uses a type in CleanArchitecture.Domain.Common.
- The types involved
CleanArchitecture.Domain.Users.Events.ReminderDeletedEvent→CleanArchitecture.Domain.Common.IDomainEventCleanArchitecture.Domain.Users.Events.ReminderDismissedEvent→CleanArchitecture.Domain.Common.IDomainEventCleanArchitecture.Domain.Users.Events.ReminderSetEvent→CleanArchitecture.Domain.Common.IDomainEventCleanArchitecture.Domain.Users.Events.SubscriptionCanceledEvent→CleanArchitecture.Domain.Common.IDomainEvent
- Direction
- CleanArchitecture.Domain.Users.Events uses CleanArchitecture.Domain.Common, so a change to CleanArchitecture.Domain.Common can break CleanArchitecture.Domain.Users.Events, while a change to CleanArchitecture.Domain.Users.Events can't break CleanArchitecture.Domain.Common.
- Position
- Below the diagonal: CleanArchitecture.Domain.Users.Events uses a module listed above it, which is the healthy direction.
18→11 CleanArchitecture.Domain.Users.Events uses CleanArchitecture.Domain.Reminders✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Domain.Users.Events uses a type in CleanArchitecture.Domain.Reminders.
- The types involved
CleanArchitecture.Domain.Users.Events.ReminderSetEvent→CleanArchitecture.Domain.Reminders.Reminder
- Direction
- CleanArchitecture.Domain.Users.Events uses CleanArchitecture.Domain.Reminders, so a change to CleanArchitecture.Domain.Reminders can break CleanArchitecture.Domain.Users.Events, while a change to CleanArchitecture.Domain.Users.Events can't break CleanArchitecture.Domain.Reminders.
- Position
- Below the diagonal: CleanArchitecture.Domain.Users.Events uses a module listed above it, which is the healthy direction.
18→14 CleanArchitecture.Domain.Users.Events uses CleanArchitecture.Domain.Users✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Domain.Users.Events uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Domain.Users.Events.SubscriptionCanceledEvent→CleanArchitecture.Domain.Users.User
- Direction
- CleanArchitecture.Domain.Users.Events uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Domain.Users.Events, while a change to CleanArchitecture.Domain.Users.Events can't break CleanArchitecture.Domain.Users.
- Position
- Below the diagonal: CleanArchitecture.Domain.Users.Events uses a module listed above it, which is the healthy direction.
19→7 CleanArchitecture.Infrastructure.Common uses CleanArchitecture.Domain.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Common uses a type in CleanArchitecture.Domain.Common.
- The types involved
CleanArchitecture.Infrastructure.Common.AppDbContext→CleanArchitecture.Domain.Common.IDomainEvent
- Direction
- CleanArchitecture.Infrastructure.Common uses CleanArchitecture.Domain.Common, so a change to CleanArchitecture.Domain.Common can break CleanArchitecture.Infrastructure.Common, while a change to CleanArchitecture.Infrastructure.Common can't break CleanArchitecture.Domain.Common.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Common uses a module listed above it, which is the healthy direction.
19→11 CleanArchitecture.Infrastructure.Common uses CleanArchitecture.Domain.Reminders✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Common uses a type in CleanArchitecture.Domain.Reminders.
- The types involved
CleanArchitecture.Infrastructure.Common.AppDbContext→CleanArchitecture.Domain.Reminders.Reminder
- Direction
- CleanArchitecture.Infrastructure.Common uses CleanArchitecture.Domain.Reminders, so a change to CleanArchitecture.Domain.Reminders can break CleanArchitecture.Infrastructure.Common, while a change to CleanArchitecture.Infrastructure.Common can't break CleanArchitecture.Domain.Reminders.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Common uses a module listed above it, which is the healthy direction.
19→14 CleanArchitecture.Infrastructure.Common uses CleanArchitecture.Domain.Users✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Common uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Infrastructure.Common.AppDbContext→CleanArchitecture.Domain.Users.User
- Direction
- CleanArchitecture.Infrastructure.Common uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Infrastructure.Common, while a change to CleanArchitecture.Infrastructure.Common can't break CleanArchitecture.Domain.Users.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Common uses a module listed above it, which is the healthy direction.
20→5 CleanArchitecture.Api.Controllers uses CleanArchitecture.Contracts.Common✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Api.Controllers uses a type in CleanArchitecture.Contracts.Common.
- The types involved
CleanArchitecture.Api.Controllers.SubscriptionsController→CleanArchitecture.Contracts.Common.SubscriptionTypeCleanArchitecture.Api.Controllers.TokensController→CleanArchitecture.Contracts.Common.SubscriptionType
- Direction
- CleanArchitecture.Api.Controllers uses CleanArchitecture.Contracts.Common, so a change to CleanArchitecture.Contracts.Common can break CleanArchitecture.Api.Controllers, while a change to CleanArchitecture.Api.Controllers can't break CleanArchitecture.Contracts.Common.
- Position
- Below the diagonal: CleanArchitecture.Api.Controllers uses a module listed above it, which is the healthy direction.
20→6 CleanArchitecture.Api.Controllers uses CleanArchitecture.Contracts.Reminders✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Api.Controllers uses a type in CleanArchitecture.Contracts.Reminders.
- The types involved
CleanArchitecture.Api.Controllers.RemindersController→CleanArchitecture.Contracts.Reminders.CreateReminderRequestCleanArchitecture.Api.Controllers.RemindersController→CleanArchitecture.Contracts.Reminders.ReminderResponse
- Direction
- CleanArchitecture.Api.Controllers uses CleanArchitecture.Contracts.Reminders, so a change to CleanArchitecture.Contracts.Reminders can break CleanArchitecture.Api.Controllers, while a change to CleanArchitecture.Api.Controllers can't break CleanArchitecture.Contracts.Reminders.
- Position
- Below the diagonal: CleanArchitecture.Api.Controllers uses a module listed above it, which is the healthy direction.
20→9 CleanArchitecture.Api.Controllers uses CleanArchitecture.Contracts.Subscriptions✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Api.Controllers uses a type in CleanArchitecture.Contracts.Subscriptions.
- The types involved
CleanArchitecture.Api.Controllers.SubscriptionsController→CleanArchitecture.Contracts.Subscriptions.CreateSubscriptionRequestCleanArchitecture.Api.Controllers.SubscriptionsController→CleanArchitecture.Contracts.Subscriptions.SubscriptionResponse
- Direction
- CleanArchitecture.Api.Controllers uses CleanArchitecture.Contracts.Subscriptions, so a change to CleanArchitecture.Contracts.Subscriptions can break CleanArchitecture.Api.Controllers, while a change to CleanArchitecture.Api.Controllers can't break CleanArchitecture.Contracts.Subscriptions.
- Position
- Below the diagonal: CleanArchitecture.Api.Controllers uses a module listed above it, which is the healthy direction.
20→10 CleanArchitecture.Api.Controllers uses CleanArchitecture.Contracts.Tokens✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Api.Controllers uses a type in CleanArchitecture.Contracts.Tokens.
- The types involved
CleanArchitecture.Api.Controllers.TokensController→CleanArchitecture.Contracts.Tokens.GenerateTokenRequestCleanArchitecture.Api.Controllers.TokensController→CleanArchitecture.Contracts.Tokens.TokenResponse
- Direction
- CleanArchitecture.Api.Controllers uses CleanArchitecture.Contracts.Tokens, so a change to CleanArchitecture.Contracts.Tokens can break CleanArchitecture.Api.Controllers, while a change to CleanArchitecture.Api.Controllers can't break CleanArchitecture.Contracts.Tokens.
- Position
- Below the diagonal: CleanArchitecture.Api.Controllers uses a module listed above it, which is the healthy direction.
20→11 CleanArchitecture.Api.Controllers uses CleanArchitecture.Domain.Reminders✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Api.Controllers uses a type in CleanArchitecture.Domain.Reminders.
- The types involved
CleanArchitecture.Api.Controllers.RemindersController→CleanArchitecture.Domain.Reminders.Reminder
- Direction
- CleanArchitecture.Api.Controllers uses CleanArchitecture.Domain.Reminders, so a change to CleanArchitecture.Domain.Reminders can break CleanArchitecture.Api.Controllers, while a change to CleanArchitecture.Api.Controllers can't break CleanArchitecture.Domain.Reminders.
- Position
- Below the diagonal: CleanArchitecture.Api.Controllers uses a module listed above it, which is the healthy direction.
20→14 CleanArchitecture.Api.Controllers uses CleanArchitecture.Domain.Users✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Api.Controllers uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Api.Controllers.SubscriptionsController→CleanArchitecture.Domain.Users.SubscriptionTypeCleanArchitecture.Api.Controllers.TokensController→CleanArchitecture.Domain.Users.SubscriptionType
- Direction
- CleanArchitecture.Api.Controllers uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Api.Controllers, while a change to CleanArchitecture.Api.Controllers can't break CleanArchitecture.Domain.Users.
- Position
- Below the diagonal: CleanArchitecture.Api.Controllers uses a module listed above it, which is the healthy direction.
20→15 CleanArchitecture.Api.Controllers uses CleanArchitecture.Application.Authentication.Queries.Login✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Api.Controllers uses a type in CleanArchitecture.Application.Authentication.Queries.Login.
- The types involved
CleanArchitecture.Api.Controllers.TokensController→CleanArchitecture.Application.Authentication.Queries.Login.GenerateTokenResult
- Direction
- CleanArchitecture.Api.Controllers uses CleanArchitecture.Application.Authentication.Queries.Login, so a change to CleanArchitecture.Application.Authentication.Queries.Login can break CleanArchitecture.Api.Controllers, while a change to CleanArchitecture.Api.Controllers can't break CleanArchitecture.Application.Authentication.Queries.Login.
- Position
- Below the diagonal: CleanArchitecture.Api.Controllers uses a module listed above it, which is the healthy direction.
20→17 CleanArchitecture.Api.Controllers uses CleanArchitecture.Application.Subscriptions.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Api.Controllers uses a type in CleanArchitecture.Application.Subscriptions.Common.
- The types involved
CleanArchitecture.Api.Controllers.SubscriptionsController→CleanArchitecture.Application.Subscriptions.Common.SubscriptionResult
- Direction
- CleanArchitecture.Api.Controllers uses CleanArchitecture.Application.Subscriptions.Common, so a change to CleanArchitecture.Application.Subscriptions.Common can break CleanArchitecture.Api.Controllers, while a change to CleanArchitecture.Api.Controllers can't break CleanArchitecture.Application.Subscriptions.Common.
- Position
- Below the diagonal: CleanArchitecture.Api.Controllers uses a module listed above it, which is the healthy direction.
21→16 CleanArchitecture.Application.Common.Behaviors uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Common.Behaviors uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Common.Behaviors.AuthorizationBehavior→CleanArchitecture.Application.Common.Interfaces.IAuthorizationService
- Direction
- CleanArchitecture.Application.Common.Behaviors uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Common.Behaviors, while a change to CleanArchitecture.Application.Common.Behaviors can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Common.Behaviors uses a module listed above it, which is the healthy direction.
22→4 CleanArchitecture.Application.Reminders.Commands.DeleteReminder uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Commands.DeleteReminder uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Application.Reminders.Commands.DeleteReminder.DeleteReminderCommand→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Application.Reminders.Commands.DeleteReminder uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Application.Reminders.Commands.DeleteReminder, while a change to CleanArchitecture.Application.Reminders.Commands.DeleteReminder can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Commands.DeleteReminder uses a module listed above it, which is the healthy direction.
22→16 CleanArchitecture.Application.Reminders.Commands.DeleteReminder uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Reminders.Commands.DeleteReminder uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Reminders.Commands.DeleteReminder.DeleteReminderCommandHandler→CleanArchitecture.Application.Common.Interfaces.IRemindersRepositoryCleanArchitecture.Application.Reminders.Commands.DeleteReminder.DeleteReminderCommandHandler→CleanArchitecture.Application.Common.Interfaces.IUsersRepository
- Direction
- CleanArchitecture.Application.Reminders.Commands.DeleteReminder uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Reminders.Commands.DeleteReminder, while a change to CleanArchitecture.Application.Reminders.Commands.DeleteReminder can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Commands.DeleteReminder uses a module listed above it, which is the healthy direction.
23→4 CleanArchitecture.Application.Reminders.Commands.DismissReminder uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Commands.DismissReminder uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Application.Reminders.Commands.DismissReminder.DismissReminderCommand→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Application.Reminders.Commands.DismissReminder uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Application.Reminders.Commands.DismissReminder, while a change to CleanArchitecture.Application.Reminders.Commands.DismissReminder can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Commands.DismissReminder uses a module listed above it, which is the healthy direction.
23→16 CleanArchitecture.Application.Reminders.Commands.DismissReminder uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Commands.DismissReminder uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Reminders.Commands.DismissReminder.DismissReminderCommandHandler→CleanArchitecture.Application.Common.Interfaces.IUsersRepository
- Direction
- CleanArchitecture.Application.Reminders.Commands.DismissReminder uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Reminders.Commands.DismissReminder, while a change to CleanArchitecture.Application.Reminders.Commands.DismissReminder can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Commands.DismissReminder uses a module listed above it, which is the healthy direction.
24→4 CleanArchitecture.Application.Reminders.Commands.SetReminder uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Commands.SetReminder uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Application.Reminders.Commands.SetReminder.SetReminderCommand→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Application.Reminders.Commands.SetReminder uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Application.Reminders.Commands.SetReminder, while a change to CleanArchitecture.Application.Reminders.Commands.SetReminder can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Commands.SetReminder uses a module listed above it, which is the healthy direction.
24→11 CleanArchitecture.Application.Reminders.Commands.SetReminder uses CleanArchitecture.Domain.Reminders✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Commands.SetReminder uses a type in CleanArchitecture.Domain.Reminders.
- The types involved
CleanArchitecture.Application.Reminders.Commands.SetReminder.SetReminderCommandHandler→CleanArchitecture.Domain.Reminders.Reminder
- Direction
- CleanArchitecture.Application.Reminders.Commands.SetReminder uses CleanArchitecture.Domain.Reminders, so a change to CleanArchitecture.Domain.Reminders can break CleanArchitecture.Application.Reminders.Commands.SetReminder, while a change to CleanArchitecture.Application.Reminders.Commands.SetReminder can't break CleanArchitecture.Domain.Reminders.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Commands.SetReminder uses a module listed above it, which is the healthy direction.
24→16 CleanArchitecture.Application.Reminders.Commands.SetReminder uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Application.Reminders.Commands.SetReminder uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Reminders.Commands.SetReminder.SetReminderCommandHandler→CleanArchitecture.Application.Common.Interfaces.IUsersRepositoryCleanArchitecture.Application.Reminders.Commands.SetReminder.SetReminderCommandValidator→CleanArchitecture.Application.Common.Interfaces.IDateTimeProvider
- Direction
- CleanArchitecture.Application.Reminders.Commands.SetReminder uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Reminders.Commands.SetReminder, while a change to CleanArchitecture.Application.Reminders.Commands.SetReminder can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Commands.SetReminder uses a module listed above it, which is the healthy direction.
25→16 CleanArchitecture.Application.Reminders.Events uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 3 pairs of types, where a type in CleanArchitecture.Application.Reminders.Events uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Reminders.Events.ReminderDeletedEventHandler→CleanArchitecture.Application.Common.Interfaces.IRemindersRepositoryCleanArchitecture.Application.Reminders.Events.ReminderDismissedEventHandler→CleanArchitecture.Application.Common.Interfaces.IRemindersRepositoryCleanArchitecture.Application.Reminders.Events.ReminderSetEventHandler→CleanArchitecture.Application.Common.Interfaces.IRemindersRepository
- Direction
- CleanArchitecture.Application.Reminders.Events uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Reminders.Events, while a change to CleanArchitecture.Application.Reminders.Events can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Events uses a module listed above it, which is the healthy direction.
25→18 CleanArchitecture.Application.Reminders.Events uses CleanArchitecture.Domain.Users.Events✕
- Connections
- 3 pairs of types, where a type in CleanArchitecture.Application.Reminders.Events uses a type in CleanArchitecture.Domain.Users.Events.
- The types involved
CleanArchitecture.Application.Reminders.Events.ReminderDeletedEventHandler→CleanArchitecture.Domain.Users.Events.ReminderDeletedEventCleanArchitecture.Application.Reminders.Events.ReminderDismissedEventHandler→CleanArchitecture.Domain.Users.Events.ReminderDismissedEventCleanArchitecture.Application.Reminders.Events.ReminderSetEventHandler→CleanArchitecture.Domain.Users.Events.ReminderSetEvent
- Direction
- CleanArchitecture.Application.Reminders.Events uses CleanArchitecture.Domain.Users.Events, so a change to CleanArchitecture.Domain.Users.Events can break CleanArchitecture.Application.Reminders.Events, while a change to CleanArchitecture.Application.Reminders.Events can't break CleanArchitecture.Domain.Users.Events.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Events uses a module listed above it, which is the healthy direction.
26→4 CleanArchitecture.Application.Reminders.Queries.GetReminder uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Queries.GetReminder uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Application.Reminders.Queries.GetReminder.GetReminderQuery→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Application.Reminders.Queries.GetReminder uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Application.Reminders.Queries.GetReminder, while a change to CleanArchitecture.Application.Reminders.Queries.GetReminder can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Queries.GetReminder uses a module listed above it, which is the healthy direction.
26→11 CleanArchitecture.Application.Reminders.Queries.GetReminder uses CleanArchitecture.Domain.Reminders✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Queries.GetReminder uses a type in CleanArchitecture.Domain.Reminders.
- The types involved
CleanArchitecture.Application.Reminders.Queries.GetReminder.GetReminderQueryHandler→CleanArchitecture.Domain.Reminders.Reminder
- Direction
- CleanArchitecture.Application.Reminders.Queries.GetReminder uses CleanArchitecture.Domain.Reminders, so a change to CleanArchitecture.Domain.Reminders can break CleanArchitecture.Application.Reminders.Queries.GetReminder, while a change to CleanArchitecture.Application.Reminders.Queries.GetReminder can't break CleanArchitecture.Domain.Reminders.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Queries.GetReminder uses a module listed above it, which is the healthy direction.
26→16 CleanArchitecture.Application.Reminders.Queries.GetReminder uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Queries.GetReminder uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Reminders.Queries.GetReminder.GetReminderQueryHandler→CleanArchitecture.Application.Common.Interfaces.IRemindersRepository
- Direction
- CleanArchitecture.Application.Reminders.Queries.GetReminder uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Reminders.Queries.GetReminder, while a change to CleanArchitecture.Application.Reminders.Queries.GetReminder can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Queries.GetReminder uses a module listed above it, which is the healthy direction.
27→4 CleanArchitecture.Application.Reminders.Queries.ListReminders uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Queries.ListReminders uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Application.Reminders.Queries.ListReminders.ListRemindersQuery→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Application.Reminders.Queries.ListReminders uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Application.Reminders.Queries.ListReminders, while a change to CleanArchitecture.Application.Reminders.Queries.ListReminders can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Queries.ListReminders uses a module listed above it, which is the healthy direction.
27→11 CleanArchitecture.Application.Reminders.Queries.ListReminders uses CleanArchitecture.Domain.Reminders✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Queries.ListReminders uses a type in CleanArchitecture.Domain.Reminders.
- The types involved
CleanArchitecture.Application.Reminders.Queries.ListReminders.ListRemindersQueryHandler→CleanArchitecture.Domain.Reminders.Reminder
- Direction
- CleanArchitecture.Application.Reminders.Queries.ListReminders uses CleanArchitecture.Domain.Reminders, so a change to CleanArchitecture.Domain.Reminders can break CleanArchitecture.Application.Reminders.Queries.ListReminders, while a change to CleanArchitecture.Application.Reminders.Queries.ListReminders can't break CleanArchitecture.Domain.Reminders.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Queries.ListReminders uses a module listed above it, which is the healthy direction.
27→16 CleanArchitecture.Application.Reminders.Queries.ListReminders uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Reminders.Queries.ListReminders uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Reminders.Queries.ListReminders.ListRemindersQueryHandler→CleanArchitecture.Application.Common.Interfaces.IRemindersRepository
- Direction
- CleanArchitecture.Application.Reminders.Queries.ListReminders uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Reminders.Queries.ListReminders, while a change to CleanArchitecture.Application.Reminders.Queries.ListReminders can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Reminders.Queries.ListReminders uses a module listed above it, which is the healthy direction.
28→4 CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription.CancelSubscriptionCommand→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription, while a change to CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription uses a module listed above it, which is the healthy direction.
28→16 CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription.CancelSubscriptionCommandHandler→CleanArchitecture.Application.Common.Interfaces.IUsersRepository
- Direction
- CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription, while a change to CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Commands.CancelSubscription uses a module listed above it, which is the healthy direction.
29→4 CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription.CreateSubscriptionCommand→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription, while a change to CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses a module listed above it, which is the healthy direction.
29→14 CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses CleanArchitecture.Domain.Users✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription.CreateSubscriptionCommand→CleanArchitecture.Domain.Users.SubscriptionType
- Direction
- CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription, while a change to CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription can't break CleanArchitecture.Domain.Users.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses a module listed above it, which is the healthy direction.
29→16 CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription.CreateSubscriptionCommandHandler→CleanArchitecture.Application.Common.Interfaces.IUsersRepository
- Direction
- CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription, while a change to CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses a module listed above it, which is the healthy direction.
29→17 CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses CleanArchitecture.Application.Subscriptions.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses a type in CleanArchitecture.Application.Subscriptions.Common.
- The types involved
CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription.CreateSubscriptionCommandHandler→CleanArchitecture.Application.Subscriptions.Common.SubscriptionResult
- Direction
- CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses CleanArchitecture.Application.Subscriptions.Common, so a change to CleanArchitecture.Application.Subscriptions.Common can break CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription, while a change to CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription can't break CleanArchitecture.Application.Subscriptions.Common.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Commands.CreateSubscription uses a module listed above it, which is the healthy direction.
30→16 CleanArchitecture.Application.Subscriptions.Events uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Events uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Subscriptions.Events.SubscriptionCanceledEventHandler→CleanArchitecture.Application.Common.Interfaces.IUsersRepository
- Direction
- CleanArchitecture.Application.Subscriptions.Events uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Subscriptions.Events, while a change to CleanArchitecture.Application.Subscriptions.Events can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Events uses a module listed above it, which is the healthy direction.
30→18 CleanArchitecture.Application.Subscriptions.Events uses CleanArchitecture.Domain.Users.Events✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Events uses a type in CleanArchitecture.Domain.Users.Events.
- The types involved
CleanArchitecture.Application.Subscriptions.Events.SubscriptionCanceledEventHandler→CleanArchitecture.Domain.Users.Events.SubscriptionCanceledEvent
- Direction
- CleanArchitecture.Application.Subscriptions.Events uses CleanArchitecture.Domain.Users.Events, so a change to CleanArchitecture.Domain.Users.Events can break CleanArchitecture.Application.Subscriptions.Events, while a change to CleanArchitecture.Application.Subscriptions.Events can't break CleanArchitecture.Domain.Users.Events.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Events uses a module listed above it, which is the healthy direction.
31→4 CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Application.Subscriptions.Queries.GetSubscription.GetSubscriptionQuery→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Application.Subscriptions.Queries.GetSubscription, while a change to CleanArchitecture.Application.Subscriptions.Queries.GetSubscription can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses a module listed above it, which is the healthy direction.
31→16 CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Subscriptions.Queries.GetSubscription.GetSubscriptionQueryHandler→CleanArchitecture.Application.Common.Interfaces.IUsersRepository
- Direction
- CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Subscriptions.Queries.GetSubscription, while a change to CleanArchitecture.Application.Subscriptions.Queries.GetSubscription can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses a module listed above it, which is the healthy direction.
31→17 CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses CleanArchitecture.Application.Subscriptions.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses a type in CleanArchitecture.Application.Subscriptions.Common.
- The types involved
CleanArchitecture.Application.Subscriptions.Queries.GetSubscription.GetSubscriptionQueryHandler→CleanArchitecture.Application.Subscriptions.Common.SubscriptionResult
- Direction
- CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses CleanArchitecture.Application.Subscriptions.Common, so a change to CleanArchitecture.Application.Subscriptions.Common can break CleanArchitecture.Application.Subscriptions.Queries.GetSubscription, while a change to CleanArchitecture.Application.Subscriptions.Queries.GetSubscription can't break CleanArchitecture.Application.Subscriptions.Common.
- Position
- Below the diagonal: CleanArchitecture.Application.Subscriptions.Queries.GetSubscription uses a module listed above it, which is the healthy direction.
32→14 CleanArchitecture.Application.Tokens.Queries.Generate uses CleanArchitecture.Domain.Users✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Tokens.Queries.Generate uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Application.Tokens.Queries.Generate.GenerateTokenQuery→CleanArchitecture.Domain.Users.SubscriptionType
- Direction
- CleanArchitecture.Application.Tokens.Queries.Generate uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Application.Tokens.Queries.Generate, while a change to CleanArchitecture.Application.Tokens.Queries.Generate can't break CleanArchitecture.Domain.Users.
- Position
- Below the diagonal: CleanArchitecture.Application.Tokens.Queries.Generate uses a module listed above it, which is the healthy direction.
32→15 CleanArchitecture.Application.Tokens.Queries.Generate uses CleanArchitecture.Application.Authentication.Queries.Login✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Tokens.Queries.Generate uses a type in CleanArchitecture.Application.Authentication.Queries.Login.
- The types involved
CleanArchitecture.Application.Tokens.Queries.Generate.GenerateTokenQueryHandler→CleanArchitecture.Application.Authentication.Queries.Login.GenerateTokenResult
- Direction
- CleanArchitecture.Application.Tokens.Queries.Generate uses CleanArchitecture.Application.Authentication.Queries.Login, so a change to CleanArchitecture.Application.Authentication.Queries.Login can break CleanArchitecture.Application.Tokens.Queries.Generate, while a change to CleanArchitecture.Application.Tokens.Queries.Generate can't break CleanArchitecture.Application.Authentication.Queries.Login.
- Position
- Below the diagonal: CleanArchitecture.Application.Tokens.Queries.Generate uses a module listed above it, which is the healthy direction.
32→16 CleanArchitecture.Application.Tokens.Queries.Generate uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Application.Tokens.Queries.Generate uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Application.Tokens.Queries.Generate.GenerateTokenQueryHandler→CleanArchitecture.Application.Common.Interfaces.IJwtTokenGenerator
- Direction
- CleanArchitecture.Application.Tokens.Queries.Generate uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Application.Tokens.Queries.Generate, while a change to CleanArchitecture.Application.Tokens.Queries.Generate can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Application.Tokens.Queries.Generate uses a module listed above it, which is the healthy direction.
33→19 CleanArchitecture.Infrastructure.Common.Middleware uses CleanArchitecture.Infrastructure.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Common.Middleware uses a type in CleanArchitecture.Infrastructure.Common.
- The types involved
CleanArchitecture.Infrastructure.Common.Middleware.EventualConsistencyMiddleware→CleanArchitecture.Infrastructure.Common.AppDbContext
- Direction
- CleanArchitecture.Infrastructure.Common.Middleware uses CleanArchitecture.Infrastructure.Common, so a change to CleanArchitecture.Infrastructure.Common can break CleanArchitecture.Infrastructure.Common.Middleware, while a change to CleanArchitecture.Infrastructure.Common.Middleware can't break CleanArchitecture.Infrastructure.Common.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Common.Middleware uses a module listed above it, which is the healthy direction.
34→16 CleanArchitecture.Infrastructure.Reminders.BackgroundServices uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Reminders.BackgroundServices uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Infrastructure.Reminders.BackgroundServices.ReminderEmailBackgroundService→CleanArchitecture.Application.Common.Interfaces.IDateTimeProvider
- Direction
- CleanArchitecture.Infrastructure.Reminders.BackgroundServices uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Infrastructure.Reminders.BackgroundServices, while a change to CleanArchitecture.Infrastructure.Reminders.BackgroundServices can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Reminders.BackgroundServices uses a module listed above it, which is the healthy direction.
34→19 CleanArchitecture.Infrastructure.Reminders.BackgroundServices uses CleanArchitecture.Infrastructure.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Reminders.BackgroundServices uses a type in CleanArchitecture.Infrastructure.Common.
- The types involved
CleanArchitecture.Infrastructure.Reminders.BackgroundServices.ReminderEmailBackgroundService→CleanArchitecture.Infrastructure.Common.AppDbContext
- Direction
- CleanArchitecture.Infrastructure.Reminders.BackgroundServices uses CleanArchitecture.Infrastructure.Common, so a change to CleanArchitecture.Infrastructure.Common can break CleanArchitecture.Infrastructure.Reminders.BackgroundServices, while a change to CleanArchitecture.Infrastructure.Reminders.BackgroundServices can't break CleanArchitecture.Infrastructure.Common.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Reminders.BackgroundServices uses a module listed above it, which is the healthy direction.
35→11 CleanArchitecture.Infrastructure.Reminders.Persistence uses CleanArchitecture.Domain.Reminders✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Reminders.Persistence uses a type in CleanArchitecture.Domain.Reminders.
- The types involved
CleanArchitecture.Infrastructure.Reminders.Persistence.ReminderConfigurations→CleanArchitecture.Domain.Reminders.ReminderCleanArchitecture.Infrastructure.Reminders.Persistence.RemindersRepository→CleanArchitecture.Domain.Reminders.Reminder
- Direction
- CleanArchitecture.Infrastructure.Reminders.Persistence uses CleanArchitecture.Domain.Reminders, so a change to CleanArchitecture.Domain.Reminders can break CleanArchitecture.Infrastructure.Reminders.Persistence, while a change to CleanArchitecture.Infrastructure.Reminders.Persistence can't break CleanArchitecture.Domain.Reminders.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Reminders.Persistence uses a module listed above it, which is the healthy direction.
35→16 CleanArchitecture.Infrastructure.Reminders.Persistence uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Reminders.Persistence uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Infrastructure.Reminders.Persistence.RemindersRepository→CleanArchitecture.Application.Common.Interfaces.IRemindersRepository
- Direction
- CleanArchitecture.Infrastructure.Reminders.Persistence uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Infrastructure.Reminders.Persistence, while a change to CleanArchitecture.Infrastructure.Reminders.Persistence can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Reminders.Persistence uses a module listed above it, which is the healthy direction.
35→19 CleanArchitecture.Infrastructure.Reminders.Persistence uses CleanArchitecture.Infrastructure.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Reminders.Persistence uses a type in CleanArchitecture.Infrastructure.Common.
- The types involved
CleanArchitecture.Infrastructure.Reminders.Persistence.RemindersRepository→CleanArchitecture.Infrastructure.Common.AppDbContext
- Direction
- CleanArchitecture.Infrastructure.Reminders.Persistence uses CleanArchitecture.Infrastructure.Common, so a change to CleanArchitecture.Infrastructure.Common can break CleanArchitecture.Infrastructure.Reminders.Persistence, while a change to CleanArchitecture.Infrastructure.Reminders.Persistence can't break CleanArchitecture.Infrastructure.Common.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Reminders.Persistence uses a module listed above it, which is the healthy direction.
36→4 CleanArchitecture.Infrastructure.Security uses CleanArchitecture.Application.Common.Security.Request✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Security uses a type in CleanArchitecture.Application.Common.Security.Request.
- The types involved
CleanArchitecture.Infrastructure.Security.AuthorizationService→CleanArchitecture.Application.Common.Security.Request.IAuthorizeableRequest
- Direction
- CleanArchitecture.Infrastructure.Security uses CleanArchitecture.Application.Common.Security.Request, so a change to CleanArchitecture.Application.Common.Security.Request can break CleanArchitecture.Infrastructure.Security, while a change to CleanArchitecture.Infrastructure.Security can't break CleanArchitecture.Application.Common.Security.Request.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Security uses a module listed above it, which is the healthy direction.
36→8 CleanArchitecture.Infrastructure.Security uses CleanArchitecture.Infrastructure.Security.CurrentUserProvider✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Security uses a type in CleanArchitecture.Infrastructure.Security.CurrentUserProvider.
- The types involved
CleanArchitecture.Infrastructure.Security.AuthorizationService→CleanArchitecture.Infrastructure.Security.CurrentUserProvider.ICurrentUserProvider
- Direction
- CleanArchitecture.Infrastructure.Security uses CleanArchitecture.Infrastructure.Security.CurrentUserProvider, so a change to CleanArchitecture.Infrastructure.Security.CurrentUserProvider can break CleanArchitecture.Infrastructure.Security, while a change to CleanArchitecture.Infrastructure.Security can't break CleanArchitecture.Infrastructure.Security.CurrentUserProvider.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Security uses a module listed above it, which is the healthy direction.
36→13 CleanArchitecture.Infrastructure.Security uses CleanArchitecture.Infrastructure.Security.PolicyEnforcer✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Security uses a type in CleanArchitecture.Infrastructure.Security.PolicyEnforcer.
- The types involved
CleanArchitecture.Infrastructure.Security.AuthorizationService→CleanArchitecture.Infrastructure.Security.PolicyEnforcer.IPolicyEnforcer
- Direction
- CleanArchitecture.Infrastructure.Security uses CleanArchitecture.Infrastructure.Security.PolicyEnforcer, so a change to CleanArchitecture.Infrastructure.Security.PolicyEnforcer can break CleanArchitecture.Infrastructure.Security, while a change to CleanArchitecture.Infrastructure.Security can't break CleanArchitecture.Infrastructure.Security.PolicyEnforcer.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Security uses a module listed above it, which is the healthy direction.
36→16 CleanArchitecture.Infrastructure.Security uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Security uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Infrastructure.Security.AuthorizationService→CleanArchitecture.Application.Common.Interfaces.IAuthorizationService
- Direction
- CleanArchitecture.Infrastructure.Security uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Infrastructure.Security, while a change to CleanArchitecture.Infrastructure.Security can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Security uses a module listed above it, which is the healthy direction.
37→14 CleanArchitecture.Infrastructure.Security.TokenGenerator uses CleanArchitecture.Domain.Users✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Security.TokenGenerator uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Infrastructure.Security.TokenGenerator.JwtTokenGenerator→CleanArchitecture.Domain.Users.SubscriptionType
- Direction
- CleanArchitecture.Infrastructure.Security.TokenGenerator uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Infrastructure.Security.TokenGenerator, while a change to CleanArchitecture.Infrastructure.Security.TokenGenerator can't break CleanArchitecture.Domain.Users.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Security.TokenGenerator uses a module listed above it, which is the healthy direction.
37→16 CleanArchitecture.Infrastructure.Security.TokenGenerator uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Security.TokenGenerator uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Infrastructure.Security.TokenGenerator.JwtTokenGenerator→CleanArchitecture.Application.Common.Interfaces.IJwtTokenGenerator
- Direction
- CleanArchitecture.Infrastructure.Security.TokenGenerator uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Infrastructure.Security.TokenGenerator, while a change to CleanArchitecture.Infrastructure.Security.TokenGenerator can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Security.TokenGenerator uses a module listed above it, which is the healthy direction.
38→16 CleanArchitecture.Infrastructure.Services uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Services uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Infrastructure.Services.SystemDateTimeProvider→CleanArchitecture.Application.Common.Interfaces.IDateTimeProvider
- Direction
- CleanArchitecture.Infrastructure.Services uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Infrastructure.Services, while a change to CleanArchitecture.Infrastructure.Services can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Services uses a module listed above it, which is the healthy direction.
39→14 CleanArchitecture.Infrastructure.Users.Persistence uses CleanArchitecture.Domain.Users✕
- Connections
- 2 pairs of types, where a type in CleanArchitecture.Infrastructure.Users.Persistence uses a type in CleanArchitecture.Domain.Users.
- The types involved
CleanArchitecture.Infrastructure.Users.Persistence.UserConfigurations→CleanArchitecture.Domain.Users.UserCleanArchitecture.Infrastructure.Users.Persistence.UsersRepository→CleanArchitecture.Domain.Users.User
- Direction
- CleanArchitecture.Infrastructure.Users.Persistence uses CleanArchitecture.Domain.Users, so a change to CleanArchitecture.Domain.Users can break CleanArchitecture.Infrastructure.Users.Persistence, while a change to CleanArchitecture.Infrastructure.Users.Persistence can't break CleanArchitecture.Domain.Users.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Users.Persistence uses a module listed above it, which is the healthy direction.
39→16 CleanArchitecture.Infrastructure.Users.Persistence uses CleanArchitecture.Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Users.Persistence uses a type in CleanArchitecture.Application.Common.Interfaces.
- The types involved
CleanArchitecture.Infrastructure.Users.Persistence.UsersRepository→CleanArchitecture.Application.Common.Interfaces.IUsersRepository
- Direction
- CleanArchitecture.Infrastructure.Users.Persistence uses CleanArchitecture.Application.Common.Interfaces, so a change to CleanArchitecture.Application.Common.Interfaces can break CleanArchitecture.Infrastructure.Users.Persistence, while a change to CleanArchitecture.Infrastructure.Users.Persistence can't break CleanArchitecture.Application.Common.Interfaces.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Users.Persistence uses a module listed above it, which is the healthy direction.
39→19 CleanArchitecture.Infrastructure.Users.Persistence uses CleanArchitecture.Infrastructure.Common✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Users.Persistence uses a type in CleanArchitecture.Infrastructure.Common.
- The types involved
CleanArchitecture.Infrastructure.Users.Persistence.UsersRepository→CleanArchitecture.Infrastructure.Common.AppDbContext
- Direction
- CleanArchitecture.Infrastructure.Users.Persistence uses CleanArchitecture.Infrastructure.Common, so a change to CleanArchitecture.Infrastructure.Common can break CleanArchitecture.Infrastructure.Users.Persistence, while a change to CleanArchitecture.Infrastructure.Users.Persistence can't break CleanArchitecture.Infrastructure.Common.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Users.Persistence uses a module listed above it, which is the healthy direction.
40→37 CleanArchitecture.Infrastructure.Security.TokenValidation uses CleanArchitecture.Infrastructure.Security.TokenGenerator✕
- Connections
- 1 pair of types, where a type in CleanArchitecture.Infrastructure.Security.TokenValidation uses a type in CleanArchitecture.Infrastructure.Security.TokenGenerator.
- The types involved
CleanArchitecture.Infrastructure.Security.TokenValidation.JwtBearerTokenValidationConfiguration→CleanArchitecture.Infrastructure.Security.TokenGenerator.JwtSettings
- Direction
- CleanArchitecture.Infrastructure.Security.TokenValidation uses CleanArchitecture.Infrastructure.Security.TokenGenerator, so a change to CleanArchitecture.Infrastructure.Security.TokenGenerator can break CleanArchitecture.Infrastructure.Security.TokenValidation, while a change to CleanArchitecture.Infrastructure.Security.TokenValidation can't break CleanArchitecture.Infrastructure.Security.TokenGenerator.
- Position
- Below the diagonal: CleanArchitecture.Infrastructure.Security.TokenValidation uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 10 | High / Critical |
| A05:2025 — Injection | 9 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 18 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (18); Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with EventualConsistencyMiddleware.cs; Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with CreateSubscription.ValidationTests.cs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with EventualConsistencyMiddleware.cs. | +5.6 pts | Low | Explicit Debt |
| Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with CreateSubscription.ValidationTests.cs. | +5.6 pts | Low | Explicit Debt |
| Resolve the 18 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (18). | +6.2 pts | Medium | Explicit Debt |
| Swallowed exception (empty catch) | +4.5 pts | Medium | Exception handling |
| Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props (5). | +1.8 pts | Low | Dependency Hygiene |
| Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2). | +1.3 pts | Low | Dependency Hygiene |
| async void method: SendEmailNotifications | +1.7 pts | Medium | Async correctness |
| Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers. | +1.6 pts | Medium | Library API & versioning |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.5 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| .editorconfig | 5.2 | Mixed | Explicit Debt: AnalyzerSeverityNone |
| src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs | 5.8 | Mixed | Explicit Debt: EmptyCatchBlock |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| Directory.Packages.props | 6.3 | Near-clean | Dependency Hygiene: Deprecated: FluentValidation.AspNetCore |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| tests/CleanArchitecture.Application.SubcutaneousTests/Subscriptions/Commands/CreateSubscription/CreateSubscription.ValidationTests.cs | 7.6 | Near-clean | Explicit Debt: WriteOnlyPrivateField |
| tests/CleanArchitecture.Api.IntegrationTests/Controllers/SubscriptionControllers.CreateSubscriptionTests.cs | 8.0 | Near-clean | Test Reliability: Flaky test: CleanArchitecture.Api.IntegrationTests::CleanArchitecture.Api.IntegrationTests.Controllers.CreateSubscriptionTests.CleanArchitecture.Api.IntegrationTests.Controllers.CreateSubscriptionTests.CreateSubscriptionForSelf_WhenHasPermission_ShouldCreateSubscription(subscriptionType: Pro) |
| src/CleanArchitecture.Application/Common/Interfaces/IRemindersRepository.cs | 8.2 | Near-clean | Explicit Debt: Dead code: RemoveRangeAsync |
| src/CleanArchitecture.Domain/Users/Calendar.cs | 8.2 | Near-clean | Explicit Debt: Dead code: SetEventCount |
| src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| src/CleanArchitecture.Domain/CleanArchitecture.Domain.csproj | 8.5 | Near-clean | Coupling: Off the main sequence: CleanArchitecture.Domain |
| src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/ReminderEmailBackgroundService.cs | 8.5 | Near-clean | Code Coverage: Low coverage: src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/ReminderEmailBackgroundService.cs |
| src/CleanArchitecture.Api/Controllers/ApiController.cs | 8.5 | Near-clean | Code Coverage: Low coverage: src/CleanArchitecture.Api/Controllers/ApiController.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 93 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 93 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, 133 of 190 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
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 67 commit(s) sampled, automation and bot accounts excluded). One of them holds 93% of the history; the other 4 hold 1.8% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/CleanArchitecture.Api/Controllers/RemindersController.cs`, `src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs`, `src/CleanArchitecture.Api/Controllers/TokensController.cs`, `src/CleanArchitecture.Application/Common/Behaviors/AuthorizationBehavior.cs`, `src/CleanArchitecture.Application/Common/Behaviors/ValidationBehavior.cs`, … (+25 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- PF3 Async & latency 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. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with SubscriptionsController.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
10 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 CleanArchitecture.Domain.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)
0 of 7 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 79.1% — 3 file(s) below 50%.
What to do
- Resolve the 3 Low coverage finding(s) in Code Coverage — start with ReminderEmailBackgroundService.cs, ApiController.cs, RemindersController.cs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
76 test methods: 72 unit, 4 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 2 mock references across 76 tests.
D11 · Test Reliability
1 flaky across 3 measured tier(s). unit: measured (0 flaky); integration: measured (1 flaky); other: measured (0 flaky).
What to do
- Resolve the 1 Flaky test finding(s) in Test Reliability — start with SubscriptionControllers.CreateSubscriptionTests.cs. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
26 outdated, 0 vulnerable, 5 deprecated, 1 prerelease packages.
What to do
- Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2). — 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
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 29 direct `PackageReference`(s), and 221 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
20 deducted debt markers + 3 dead symbols across 1781 LoC in the .NET projects (5.5/KLoC) → score 0.0.
What to do
- Resolve the 18 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (18). — One of this dimension's main actionable groups (18 issue-level).
- Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with EventualConsistencyMiddleware.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with CreateSubscription.ValidationTests.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
10 projects, 143 source files, 3835 hand-written lines of code (1781 production / 2054 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 250 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 16 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 6 unit(s).
D26 · Project Cohesion
0 of 10 projects flagged as possibly oversized/incoherent.
D27 · Navigability
96 % of calls cross a namespace and 11 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
9 finding(s): 0 critical, 9 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 9 REDACTED finding(s) in Secrets (history) — start with REDACTED (6), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 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)
9 finding(s): 0 critical, 7 high, 2 medium, 0 low. semgrep hit a parse error in 30 file(s) — `src/CleanArchitecture.Api/Controllers/RemindersController.cs` (line 16), `src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs` (line 17), `src/CleanArchitecture.Api/Controllers/TokensController.cs` (line 17), `src/CleanArchitecture.Application/Common/Behaviors/AuthorizationBehavior.cs` (lines 12–13), `src/CleanArchitecture.Application/Common/Behaviors/ValidationBehavior.cs` (line 9), … (+25 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 30 of those file(s) — `src/CleanArchitecture.Api/Controllers/RemindersController.cs`, `src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs`, `src/CleanArchitecture.Api/Controllers/TokensController.cs`, `src/CleanArchitecture.Application/Common/Behaviors/AuthorizationBehavior.cs`, `src/CleanArchitecture.Application/Common/Behaviors/ValidationBehavior.cs`, … (+25 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 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).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
7 finding(s): 0 critical, 6 high, 1 medium, 0 low.
What to do
- Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 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
4 finding(s): 0 critical, 1 high, 2 medium, 1 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).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
5 of 5 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/CleanArchitecture.Infrastructure/DependencyInjection.cs. Counted over 5 of the 107 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 5 Orphaned file finding(s) in Knowledge Freshness — start with DependencyInjection.cs, User.cs, RemindersController.cs. — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
0 of 191 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 3 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
- The namespaces CleanArchitecture.Domain.Subscriptions ↔ CleanArchitecture.Domain.Users depend on each other. The lightest dependency in the cycle is CleanArchitecture.Domain.Subscriptions → CleanArchitecture.Domain.Users (CleanArchitecture.Domain.Subscriptions.Subscription → CleanArchitecture.Domain.Users.SubscriptionType, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/CleanArchitecture.Domain/Users/Subscription.cs:2
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
AX8 · Test isolation
AX9 · CQS / query purity
C2 · Access Controls
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.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `Reminder`'s public constructor takes `text` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Reminder` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/CleanArchitecture.Domain/Reminders/Reminder.cs:21
- `User`'s public constructor takes `firstName`, `lastName`, `email` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `User` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/CleanArchitecture.Domain/Users/User.cs:28
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `Reminder.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. — src/CleanArchitecture.Domain/Reminders/Reminder.cs:9
- `Reminder.SubscriptionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/CleanArchitecture.Domain/Reminders/Reminder.cs:11
- `ReminderDeletedEvent.ReminderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/CleanArchitecture.Domain/Users/Events/ReminderDeletedEvent.cs:5
- `ReminderDismissedEvent.ReminderId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/CleanArchitecture.Domain/Users/Events/ReminderDismissedEvent.cs:5
- `SubscriptionCanceledEvent.SubscriptionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/CleanArchitecture.Domain/Users/Events/SubscriptionCanceledEvent.cs:5
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED3 · Event naming
ED4 · Outbox / dual-write
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a README to the 6 of 6 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 13/14 types (93%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
- No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
What to do
- Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
- Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
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.
- Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
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.
P8 · Schema migrations
P9 · Domain vs controller coverage
What to do
- Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
- Only 0/62 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
- `await _mediator.Send(command)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×5) — src/CleanArchitecture.Api/Controllers/RemindersController.cs:23, src/CleanArchitecture.Api/Controllers/RemindersController.cs:38, src/CleanArchitecture.Api/Controllers/RemindersController.cs:50, …
- `await _mediator.Send(query)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×4) — src/CleanArchitecture.Api/Controllers/RemindersController.cs:62, src/CleanArchitecture.Api/Controllers/RemindersController.cs:74, src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs:63, …
- `await next()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×4) — src/CleanArchitecture.Application/Common/Behaviors/AuthorizationBehavior.cs:29, src/CleanArchitecture.Application/Common/Behaviors/AuthorizationBehavior.cs:52, src/CleanArchitecture.Application/Common/Behaviors/ValidationBehavior.cs:23, …
- `await _validator.ValidateAsync(request, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Application/Common/Behaviors/ValidationBehavior.cs:26
- `await _remindersRepository.GetByIdAsync(request.ReminderId, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Application/Reminders/Commands/DeleteReminder/DeleteReminderCommandHandler.cs:15
- `await _usersRepository.GetByIdAsync(request.UserId, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×5) — src/CleanArchitecture.Application/Reminders/Commands/DeleteReminder/DeleteReminderCommandHandler.cs:17, src/CleanArchitecture.Application/Reminders/Commands/DismissReminder/DismissReminderCommandHandler.cs:15, src/CleanArchitecture.Application/Subscriptions/Commands/CancelSubscription/CancelSubscriptionCommandHandler.cs:14, …
- `await _usersRepository.UpdateAsync(user, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×4) — src/CleanArchitecture.Application/Reminders/Commands/DeleteReminder/DeleteReminderCommandHandler.cs:31, src/CleanArchitecture.Application/Reminders/Commands/DismissReminder/DismissReminderCommandHandler.cs:29, src/CleanArchitecture.Application/Reminders/Commands/SetReminder/SetReminderCommandHandler.cs:35, …
- `await _usersRepository.GetBySubscriptionIdAsync(command.SubscriptionId, cancellatio...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Application/Reminders/Commands/SetReminder/SetReminderCommandHandler.cs:21
- `await _remindersRepository.GetByIdAsync(notification.ReminderId, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/CleanArchitecture.Application/Reminders/Events/ReminderDeletedEventHandler.cs:12, src/CleanArchitecture.Application/Reminders/Events/ReminderDismissedEventHandler.cs:12
- `await _remindersRepository.RemoveAsync(reminder, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Application/Reminders/Events/ReminderDeletedEventHandler.cs:15
- `await _remindersRepository.UpdateAsync(reminder, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Application/Reminders/Events/ReminderDismissedEventHandler.cs:17
- `await _remindersRepository.AddAsync(@event.Reminder, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Application/Reminders/Events/ReminderSetEventHandler.cs:12
- `await _remindersRepository.GetByIdAsync(query.ReminderId, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Application/Reminders/Queries/GetReminder/GetReminderQueryHandler.cs:15
- `await _remindersRepository.ListBySubscriptionIdAsync(request.SubscriptionId, cancel...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Application/Reminders/Queries/ListReminders/ListRemindersQueryHandler.cs:14
- `await _usersRepository.AddAsync(user, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Application/Subscriptions/Commands/CreateSubscription/CreateSubscriptionCommandHandler.cs:31
- `await _usersRepository.RemoveAsync(notification.User, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Application/Subscriptions/Events/SubscriptionCanceledEventHandler.cs:15
- `await dbContext.Database.BeginTransactionAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:15
- `await publisher.Publish(nextEvent)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:24
- `await transaction.CommitAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:28
- `await transaction.DisposeAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:35
- `await _next(context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:39
What to do
- In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — src/CleanArchitecture.Api/Program.cs:5
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
- `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/ReminderEmailBackgroundService.cs:40
What to do
- async void method: SendEmailNotifications
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
- `serviceScopeFactory.CreateScope()` (line 17) creates an `IServiceScope`, and it is dropped: `CreateScope().ServiceProvider` never names the scope, so nothing can release it. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`. — src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/ReminderEmailBackgroundService.cs:17
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 26/37 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. (×10) — src/CleanArchitecture.Api/Controllers/RemindersController.cs:19, src/CleanArchitecture.Api/Controllers/RemindersController.cs:34, src/CleanArchitecture.Api/Controllers/RemindersController.cs:46, …
- 1 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.
- Its signature is fixed by the framework, and the token it carries (`context.RequestAborted`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `context.RequestAborted` to them. — src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:13
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. — src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:30
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
X5 · Nullable reference types
- ~2.4 `!` suppressions per 1k syntax nodes — 26 suppression(s) across the 10879 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 50% | Adequate — gated by D17, X3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 88% | Exemplary | Solid. |
| Maturity | 68% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59% | Adequate — gated by P10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 70% | Adequate — gated by D28, D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 72% | Adequate — gated by DM2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 100% | Exemplary | Strongest area. |
| Performance | 60% | Strong | Solid. |
Unscored — 4 check(s) recorded observations but carry no score
- AXH1 Runtime security headers — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXI1 Runtime container hardening — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 3 control(s) we could not find positive evidence for
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 40 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXO1 Runtime API surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- D16 Bus Factor — single-maintainer 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 (622 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — N/A — too few peer members to establish a convention across 13 exposed C# types.
- D23 Boundary Type-Coupling — small single-context codebase (1,781 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (CleanArchitecture.Domain), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (15 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 30 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
- 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
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED5 Idempotency — not scored — 7 of 9 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P2 Observability — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. Structured logging, tracing/metrics and health checks 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.
- 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.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 45 finding(s)
- AnalyzerSeverityNone .editorconfig:369
- AnalyzerSeverityNone .editorconfig:372
- AnalyzerSeverityNone .editorconfig:375
- AnalyzerSeverityNone .editorconfig:378
- AnalyzerSeverityNone .editorconfig:381
- AnalyzerSeverityNone .editorconfig:384
- AnalyzerSeverityNone .editorconfig:387
- AnalyzerSeverityNone .editorconfig:390
- AnalyzerSeverityNone .editorconfig:393
- AnalyzerSeverityNone .editorconfig:396
- AnalyzerSeverityNone .editorconfig:399
- AnalyzerSeverityNone .editorconfig:402
- AnalyzerSeverityNone .editorconfig:405
- AnalyzerSeverityNone .editorconfig:408
- AnalyzerSeverityNone .editorconfig:411
- AnalyzerSeverityNone .editorconfig:414
- AnalyzerSeverityNone .editorconfig:417
- AnalyzerSeverityNone .editorconfig:420
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle src/CleanArchitecture.Domain/Users/Subscription.cs:2
- Flaky test: CleanArchitecture.Api.IntegrationTests::CleanArchitecture.Api.IntegrationTests.Controllers.CreateSubscriptionTests.CleanArchitecture.Api.IntegrationTests.Controllers.CreateSubscriptionTests.CreateSubscriptionForSelf_WhenHasPermission_ShouldCreateSubscription(subscriptionType: Pro) tests/CleanArchitecture.Api.IntegrationTests/Controllers/SubscriptionControllers.CreateSubscriptionTests.cs:23
- EmptyCatchBlock src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:30
- WriteOnlyPrivateField tests/CleanArchitecture.Application.SubcutaneousTests/Subscriptions/Commands/CreateSubscription/CreateSubscription.ValidationTests.cs:6
- REDACTED
- REDACTED
- REDACTED
Serious — 90 finding(s)
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Api/Controllers/RemindersController.cs:23
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Api/Controllers/RemindersController.cs:38
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Api/Controllers/RemindersController.cs:50
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Api/Controllers/RemindersController.cs:62
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Api/Controllers/RemindersController.cs:74
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs:36
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs:51
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs:63
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Api/Controllers/TokensController.cs:38
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Common/Behaviors/AuthorizationBehavior.cs:29
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Common/Behaviors/AuthorizationBehavior.cs:52
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Common/Behaviors/ValidationBehavior.cs:23
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Common/Behaviors/ValidationBehavior.cs:26
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Common/Behaviors/ValidationBehavior.cs:30
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Reminders/Commands/DeleteReminder/DeleteReminderCommandHandler.cs:15
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Reminders/Commands/DeleteReminder/DeleteReminderCommandHandler.cs:17
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Reminders/Commands/DeleteReminder/DeleteReminderCommandHandler.cs:31
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Reminders/Commands/DismissReminder/DismissReminderCommandHandler.cs:15
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Reminders/Commands/DismissReminder/DismissReminderCommandHandler.cs:29
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Reminders/Commands/SetReminder/SetReminderCommandHandler.cs:21
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Reminders/Commands/SetReminder/SetReminderCommandHandler.cs:35
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Reminders/Events/ReminderDeletedEventHandler.cs:12
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Reminders/Events/ReminderDeletedEventHandler.cs:15
- Awaits without ConfigureAwait(false) src/CleanArchitecture.Application/Reminders/Events/ReminderDismissedEventHandler.cs:12
- Runtime security header not set: content-security-policy
- Runtime security header not set: cross-origin-embedder-policy
- Runtime security header not set: cross-origin-opener-policy
- Runtime security header not set: cross-origin-resource-policy
- Runtime security header not set: permissions-policy
- Runtime security header not set: referrer-policy
- Runtime security header not set: strict-transport-security
- Runtime security header not set: x-content-type-options
- Runtime security header not set: x-dns-prefetch-control
- Runtime security header not set: x-frame-options
- Runtime security header not set: x-permitted-cross-domain-policies
- Async method without CancellationToken: CreateReminder src/CleanArchitecture.Api/Controllers/RemindersController.cs:19
- Async method without CancellationToken: DismissReminder src/CleanArchitecture.Api/Controllers/RemindersController.cs:34
- Async method without CancellationToken: DeleteReminder src/CleanArchitecture.Api/Controllers/RemindersController.cs:46
- Async method without CancellationToken: GetReminder src/CleanArchitecture.Api/Controllers/RemindersController.cs:58
- Async method without CancellationToken: ListReminders src/CleanArchitecture.Api/Controllers/RemindersController.cs:70
- Async method without CancellationToken: CreateSubscription src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs:20
- Async method without CancellationToken: DeleteSubscription src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs:47
- Async method without CancellationToken: GetSubscription src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs:59
- Async method without CancellationToken: GenerateToken src/CleanArchitecture.Api/Controllers/TokensController.cs:20
- Async method without CancellationToken: PublishDomainEvents src/CleanArchitecture.Infrastructure/Common/Persistence/AppDbContext.cs:44
- Deprecated: FluentValidation.AspNetCore Directory.Packages.props:24
- Deprecated: Microsoft.AspNetCore.Authentication Directory.Packages.props:41
- Deprecated: Microsoft.AspNetCore.Mvc Directory.Packages.props:9
- Deprecated: System.IdentityModel.Tokens.Jwt Directory.Packages.props:40
- Deprecated: xunit Directory.Packages.props:34
- Dead code: RemoveRangeAsync src/CleanArchitecture.Application/Common/Interfaces/IRemindersRepository.cs:11
- Dead code: SetEventCount src/CleanArchitecture.Domain/Users/Calendar.cs:35
- Dead code: InvokeAsync src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:13
- Low coverage: src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/ReminderEmailBackgroundService.cs src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/ReminderEmailBackgroundService.cs:1
- Low coverage: src/CleanArchitecture.Api/Controllers/ApiController.cs src/CleanArchitecture.Api/Controllers/ApiController.cs:1
- Low coverage: src/CleanArchitecture.Api/Controllers/RemindersController.cs src/CleanArchitecture.Api/Controllers/RemindersController.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Constructible in an invalid state: Reminder src/CleanArchitecture.Domain/Reminders/Reminder.cs:21
- Constructible in an invalid state: User src/CleanArchitecture.Domain/Users/User.cs:28
- Container process runs as root: clean-architecture-api
- WCAG 2.4.2 reproducibly failed in a rendered surface
- WCAG 3.1.1 reproducibly failed in a rendered surface
- Prerelease dependency: StyleCop.Analyzers
- REDACTED
- Duplicated block (6 lines × 2) src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs:71
- Off the main sequence: CleanArchitecture.Domain src/CleanArchitecture.Domain/CleanArchitecture.Domain.csproj:1
- Coverage collected but not gated
- async void method: SendEmailNotifications src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/ReminderEmailBackgroundService.cs:40
- DI scope created and never disposed src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/ReminderEmailBackgroundService.cs:17
- Async method drops its ambient CancellationToken: InvokeAsync src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:13
- Swallowed exception (empty catch) src/CleanArchitecture.Infrastructure/Common/Middleware/EventualConsistencyMiddleware.cs:30
Minor — 28 finding(s)
- Orphaned file src/CleanArchitecture.Infrastructure/DependencyInjection.cs:1
- Orphaned file src/CleanArchitecture.Domain/Users/User.cs:1
- Orphaned file src/CleanArchitecture.Api/Controllers/RemindersController.cs:1
- Orphaned file src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs:1
- Orphaned file src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/ReminderEmailBackgroundService.cs:1
- Primitive id on a domain type: Reminder.UserId src/CleanArchitecture.Domain/Reminders/Reminder.cs:9
- Primitive id on a domain type: Reminder.SubscriptionId src/CleanArchitecture.Domain/Reminders/Reminder.cs:11
- Primitive id on a domain type: ReminderDeletedEvent.ReminderId src/CleanArchitecture.Domain/Users/Events/ReminderDeletedEvent.cs:5
- Primitive id on a domain type: ReminderDismissedEvent.ReminderId src/CleanArchitecture.Domain/Users/Events/ReminderDismissedEvent.cs:5
- Primitive id on a domain type: SubscriptionCanceledEvent.SubscriptionId src/CleanArchitecture.Domain/Users/Events/SubscriptionCanceledEvent.cs:5
- Outdated: Swashbuckle.AspNetCore Directory.Packages.props:14
- Outdated: coverlet.collector Directory.Packages.props:36
- No security response headers detected
- No security response headers detected src/CleanArchitecture.Api/Program.cs:5
- Partial audit-trail evidence
- Partial data-retention evidence
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- No ADRs
- Large public API surface
- No explicit versioning
- No rollback/health safety
- No release approval gate
- No performance benchmarks
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 27 finding(s)
- Outdated: Microsoft.AspNetCore.OpenApi
- Outdated: Microsoft.EntityFrameworkCore.Design
- Outdated: FluentValidation
- Outdated: FluentValidation.AspNetCore
- Outdated: Ardalis.SmartEnum
- Outdated: ErrorOr
- Outdated: MediatR
- Outdated: Microsoft.AspNetCore.Authentication
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore
- Outdated: Microsoft.AspNetCore.Mvc
- Outdated: Microsoft.EntityFrameworkCore
- Outdated: Microsoft.EntityFrameworkCore.Sqlite
- Outdated: Microsoft.Extensions.Configuration.Abstractions
- Outdated: Microsoft.Extensions.Configuration.Binder
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions
- Outdated: Microsoft.Extensions.Identity.Core
- Outdated: System.IdentityModel.Tokens.Jwt
- Outdated: FluentAssertions
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: xunit
- Outdated: xunit.runner.visualstudio
- Outdated: NSubstitute
- Outdated: Microsoft.AspNetCore.Mvc.Testing
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Off the main sequence: CleanArchitecture.Contracts src/CleanArchitecture.Contracts/CleanArchitecture.Contracts.csproj:1
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fceac16d661c488e931a03104a08be7a/history.json --exit-code 0 --source . | 9 | 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-fceac16d661c488e931a03104a08be7a/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 src/CleanArchitecture.Infrastructure/Migrations . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list CleanArchitecture.sln package --vulnerable --include-transitive --format json | 7 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 30 file(s) — `src/CleanArchitecture.Api/Controllers/RemindersController.cs`, `src/CleanArchitecture.Api/Controllers/SubscriptionsController.cs`, `src/CleanArchitecture.Api/Controllers/TokensController.cs`, `src/CleanArchitecture.Application/Common/Behaviors/AuthorizationBehavior.cs`, `src/CleanArchitecture.Application/Common/Behaviors/ValidationBehavior.cs`, … (+25 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-b83766e45d114384b06b27deb5c36c3a | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 16 field(s)
- CreateSubscriptionCommand.FirstName src/CleanArchitecture.Application/Subscriptions/Commands/CreateSubscription/CreateSubscriptionCommand.cs:14
- CreateSubscriptionCommand.LastName src/CleanArchitecture.Application/Subscriptions/Commands/CreateSubscription/CreateSubscriptionCommand.cs:15
- GenerateTokenQuery.FirstName src/CleanArchitecture.Application/Tokens/Queries/Generate/GenerateTokenQuery.cs:12
- GenerateTokenQuery.LastName src/CleanArchitecture.Application/Tokens/Queries/Generate/GenerateTokenQuery.cs:13
- GenerateTokenResult.FirstName src/CleanArchitecture.Application/Tokens/Queries/Generate/GenerateTokenResult.cs:7
- GenerateTokenResult.LastName src/CleanArchitecture.Application/Tokens/Queries/Generate/GenerateTokenResult.cs:8
- CreateSubscriptionRequest.FirstName src/CleanArchitecture.Contracts/Subscriptions/CreateSubscriptionRequest.cs:6
- CreateSubscriptionRequest.LastName src/CleanArchitecture.Contracts/Subscriptions/CreateSubscriptionRequest.cs:7
- GenerateTokenRequest.FirstName src/CleanArchitecture.Contracts/Tokens/GenerateTokenRequest.cs:7
- GenerateTokenRequest.LastName src/CleanArchitecture.Contracts/Tokens/GenerateTokenRequest.cs:8
- TokenResponse.FirstName src/CleanArchitecture.Contracts/Tokens/TokenResponse.cs:7
- TokenResponse.LastName src/CleanArchitecture.Contracts/Tokens/TokenResponse.cs:8
- User.FirstName src/CleanArchitecture.Domain/Users/User.cs:24
- User.LastName src/CleanArchitecture.Domain/Users/User.cs:26
- CurrentUser.FirstName src/CleanArchitecture.Infrastructure/Security/CurrentUserProvider/CurrentUser.cs:5
- CurrentUser.LastName src/CleanArchitecture.Infrastructure/Security/CurrentUserProvider/CurrentUser.cs:6
Email — 9 field(s)
- CreateSubscriptionCommand.Email src/CleanArchitecture.Application/Subscriptions/Commands/CreateSubscription/CreateSubscriptionCommand.cs:16
- GenerateTokenQuery.Email src/CleanArchitecture.Application/Tokens/Queries/Generate/GenerateTokenQuery.cs:14
- GenerateTokenResult.Email src/CleanArchitecture.Application/Tokens/Queries/Generate/GenerateTokenResult.cs:9
- CreateSubscriptionRequest.Email src/CleanArchitecture.Contracts/Subscriptions/CreateSubscriptionRequest.cs:8
- GenerateTokenRequest.Email src/CleanArchitecture.Contracts/Tokens/GenerateTokenRequest.cs:9
- TokenResponse.Email src/CleanArchitecture.Contracts/Tokens/TokenResponse.cs:9
- User.Email src/CleanArchitecture.Domain/Users/User.cs:22
- EmailSettings.DefaultFromEmail src/CleanArchitecture.Infrastructure/Reminders/BackgroundServices/EmailSettings.cs:9
- CurrentUser.Email src/CleanArchitecture.Infrastructure/Security/CurrentUserProvider/CurrentUser.cs:7