Executive summary
haxnted/pet-family-backend-new falls short of our standard for production because we found no encryption of stored data, no key vault and no enforced HTTPS, and it has unsafe settings in infrastructure or container files. It scores 52 out of 100 and is rated Adequate, and 34 of its 77 critical findings are security problems.
Security and Compliance, at 41, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 8 points. Replacing the six exposed passwords or keys and switching the old ones off comes next, worth about 4 points. Raising Security and Compliance to 70 would lift the score to about 60.
Twenty settings leave the servers or containers unsafe. Six passwords or keys in the code and five in the code's history are open to anyone who can read the repository, and two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Correcting the unsafe settings, replacing each exposed password or key and pinning each tool to an exact version would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. The 33 analysis rules switched off in the settings need switching back on in the settings file.
The product code is 18,654 lines, about €33,000 to rebuild.
If Security and Compliance rose from 41 to 70, the lowest score rated Strong, the score would rise from 52 to about 60.
New since the last survey: 5 findings
- Outbox / dual-write · Dual write (no outbox): AuthService.RegisterAsync Solution/Auth/Auth.Application/Services/AuthService.cs
- Outbox / dual-write · Dual write (no outbox): DevDataSeeder.SeedAsync Solution/Auth/Auth.Infrastructure/Services/DevDataSeeder.cs
- Outbox / dual-write · Dual write (no outbox): EmailService.SendAsync Solution/Notification/Notification.Infrastructure/Services/Email/EmailService.cs
- Cancellation propagation · Async delegate without CancellationToken: AddRabbitMqHealthCheck REDACTED
- Rich vs anemic model · Anemic entity: Account Solution/Account/Account.Domain/Aggregates/Account.cs
Fixed since the last survey: 2 findings
- Rich vs anemic model · Anemic entity: Chat Solution/Conversation/Conversation.Domain/Aggregates/Chat.cs
- Rich vs anemic model · Anemic entity: Species Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/AnimalKinds/Species.cs
Rebuild cost: about €33,000 · Estimate
| Cost to rebuild | €11,000 to €54,000, for 181 to 572 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 18,654 lines of product code, of which 39% is declarations and boilerplate, 48% straight logic and 13% logic with branches |
| Comment lines | The estimate prices 15,267 lines. Comment lines count towards the size of 18,654 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Auth.Contracts.Dtos | 2 Auth.Infrastructure.Common | 3 FileStorage.Application.Services | 4 Notification.Core.Models | 5 PetFamily.SharedKernel.Contracts.Events.Auth | 6 PetFamily.SharedKernel.Domain.Primitives | 7 PetFamily.SharedKernel.Infrastructure.Abstractions | 8 PetFamily.SharedKernel.Infrastructure.Caching | 9 PetFamily.SharedKernel.Infrastructure.Configurations | 10 PetFamily.SharedKernel.WebApi.Services | 11 VolunteerManagement.Services.Volunteers.Dtos | 12 Account.Domain.Aggregates | 13 Auth.Infrastructure.Services | 14 Conversation.Domain.Aggregates.Entities | 15 Notification.Application.Services | 16 Notification.Hosts.Consumers.Consumers | 17 PetFamily.SharedKernel.Infrastructure | 18 VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties | 19 VolunteerManagement.Domain.Aggregates.Shelters.Entities | 20 VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties | 21 Account.Services | 22 Auth.Application.Services | 23 Auth.Infrastructure.Services.Keycloak | 24 Conversation.Domain.Aggregates | 25 VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities | 26 VolunteerManagement.Domain.Aggregates.Shelters | 27 VolunteerManagement.Domain.Aggregates.Volunteers.Entities | 28 Conversation.Services | 29 VolunteerManagement.Domain.Aggregates.AnimalKinds | 30 VolunteerManagement.Domain.Aggregates.Volunteers | 31 VolunteerManagement.Services.Shelters | 32 VolunteerManagement.Handlers.MappingExtensions | 33 VolunteerManagement.Hosts.Consumers.Consumers | 34 VolunteerManagement.Infrastructure.Common.Configurations | 35 VolunteerManagement.Infrastructure.Common.Contexts | 36 VolunteerManagement.Services.AnimalKinds | 37 VolunteerManagement.Services.Volunteers | 38 VolunteerManagement.Services.Volunteers.Adoption | 39 VolunteerManagement.Services.Volunteers.Pets | 40 VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Auth.Contracts.Dtos | ||||||||||||||||||||||||||||||||||||||||
| 2 Auth.Infrastructure.Common | ||||||||||||||||||||||||||||||||||||||||
| 3 FileStorage.Application.Services | ||||||||||||||||||||||||||||||||||||||||
| 4 Notification.Core.Models | ||||||||||||||||||||||||||||||||||||||||
| 5 PetFamily.SharedKernel.Contracts.Events.Auth | ||||||||||||||||||||||||||||||||||||||||
| 6 PetFamily.SharedKernel.Domain.Primitives | ||||||||||||||||||||||||||||||||||||||||
| 7 PetFamily.SharedKernel.Infrastructure.Abstractions | ||||||||||||||||||||||||||||||||||||||||
| 8 PetFamily.SharedKernel.Infrastructure.Caching | ||||||||||||||||||||||||||||||||||||||||
| 9 PetFamily.SharedKernel.Infrastructure.Configurations | ||||||||||||||||||||||||||||||||||||||||
| 10 PetFamily.SharedKernel.WebApi.Services | ||||||||||||||||||||||||||||||||||||||||
| 11 VolunteerManagement.Services.Volunteers.Dtos | ||||||||||||||||||||||||||||||||||||||||
| 12 Account.Domain.Aggregates | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Auth.Infrastructure.Services | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 Conversation.Domain.Aggregates.Entities | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Notification.Application.Services | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 Notification.Hosts.Consumers.Consumers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 PetFamily.SharedKernel.Infrastructure | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 VolunteerManagement.Domain.Aggregates.Shelters.Entities | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties | 9 | |||||||||||||||||||||||||||||||||||||||
| 21 Account.Services | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 Auth.Application.Services | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 Auth.Infrastructure.Services.Keycloak | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Conversation.Domain.Aggregates | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 VolunteerManagement.Domain.Aggregates.Shelters | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 27 VolunteerManagement.Domain.Aggregates.Volunteers.Entities | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 28 Conversation.Services | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 VolunteerManagement.Domain.Aggregates.AnimalKinds | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 VolunteerManagement.Domain.Aggregates.Volunteers | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 VolunteerManagement.Services.Shelters | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 32 VolunteerManagement.Handlers.MappingExtensions | 2 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 33 VolunteerManagement.Hosts.Consumers.Consumers | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 34 VolunteerManagement.Infrastructure.Common.Configurations | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 VolunteerManagement.Infrastructure.Common.Contexts | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 VolunteerManagement.Services.AnimalKinds | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 VolunteerManagement.Services.Volunteers | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 VolunteerManagement.Services.Volunteers.Adoption | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 VolunteerManagement.Services.Volunteers.Pets | 2 | 2 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add | 1 | 1 | 2 | 1 |
12→6 Account.Domain.Aggregates uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 1 pair of types, where a type in Account.Domain.Aggregates uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
Account.Domain.Aggregates.Account→PetFamily.SharedKernel.Domain.Primitives.Entity
- Direction
- Account.Domain.Aggregates uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break Account.Domain.Aggregates, while a change to Account.Domain.Aggregates can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: Account.Domain.Aggregates uses a module listed above it, which is the healthy direction.
13→1 Auth.Infrastructure.Services uses Auth.Contracts.Dtos✕
- Connections
- 1 pair of types, where a type in Auth.Infrastructure.Services uses a type in Auth.Contracts.Dtos.
- The types involved
Auth.Infrastructure.Services.IKeycloakService→Auth.Contracts.Dtos.AuthTokenResponse
- Direction
- Auth.Infrastructure.Services uses Auth.Contracts.Dtos, so a change to Auth.Contracts.Dtos can break Auth.Infrastructure.Services, while a change to Auth.Infrastructure.Services can't break Auth.Contracts.Dtos.
- Position
- Below the diagonal: Auth.Infrastructure.Services uses a module listed above it, which is the healthy direction.
13→2 Auth.Infrastructure.Services uses Auth.Infrastructure.Common✕
- Connections
- 1 pair of types, where a type in Auth.Infrastructure.Services uses a type in Auth.Infrastructure.Common.
- The types involved
Auth.Infrastructure.Services.DevDataSeeder→Auth.Infrastructure.Common.AuthDbContext
- Direction
- Auth.Infrastructure.Services uses Auth.Infrastructure.Common, so a change to Auth.Infrastructure.Common can break Auth.Infrastructure.Services, while a change to Auth.Infrastructure.Services can't break Auth.Infrastructure.Common.
- Position
- Below the diagonal: Auth.Infrastructure.Services uses a module listed above it, which is the healthy direction.
14→6 Conversation.Domain.Aggregates.Entities uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 1 pair of types, where a type in Conversation.Domain.Aggregates.Entities uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
Conversation.Domain.Aggregates.Entities.Message→PetFamily.SharedKernel.Domain.Primitives.Entity
- Direction
- Conversation.Domain.Aggregates.Entities uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break Conversation.Domain.Aggregates.Entities, while a change to Conversation.Domain.Aggregates.Entities can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: Conversation.Domain.Aggregates.Entities uses a module listed above it, which is the healthy direction.
15→4 Notification.Application.Services uses Notification.Core.Models✕
- Connections
- 1 pair of types, where a type in Notification.Application.Services uses a type in Notification.Core.Models.
- The types involved
Notification.Application.Services.NotificationSettingsService→Notification.Core.Models.UserNotificationSettings
- Direction
- Notification.Application.Services uses Notification.Core.Models, so a change to Notification.Core.Models can break Notification.Application.Services, while a change to Notification.Application.Services can't break Notification.Core.Models.
- Position
- Below the diagonal: Notification.Application.Services uses a module listed above it, which is the healthy direction.
15→7 Notification.Application.Services uses PetFamily.SharedKernel.Infrastructure.Abstractions✕
- Connections
- 1 pair of types, where a type in Notification.Application.Services uses a type in PetFamily.SharedKernel.Infrastructure.Abstractions.
- The types involved
Notification.Application.Services.NotificationSettingsService→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepository
- Direction
- Notification.Application.Services uses PetFamily.SharedKernel.Infrastructure.Abstractions, so a change to PetFamily.SharedKernel.Infrastructure.Abstractions can break Notification.Application.Services, while a change to Notification.Application.Services can't break PetFamily.SharedKernel.Infrastructure.Abstractions.
- Position
- Below the diagonal: Notification.Application.Services uses a module listed above it, which is the healthy direction.
16→4 Notification.Hosts.Consumers.Consumers uses Notification.Core.Models✕
- Connections
- 1 pair of types, where a type in Notification.Hosts.Consumers.Consumers uses a type in Notification.Core.Models.
- The types involved
Notification.Hosts.Consumers.Consumers.UserCreatedEventConsumer→Notification.Core.Models.UserNotificationSettings
- Direction
- Notification.Hosts.Consumers.Consumers uses Notification.Core.Models, so a change to Notification.Core.Models can break Notification.Hosts.Consumers.Consumers, while a change to Notification.Hosts.Consumers.Consumers can't break Notification.Core.Models.
- Position
- Below the diagonal: Notification.Hosts.Consumers.Consumers uses a module listed above it, which is the healthy direction.
16→5 Notification.Hosts.Consumers.Consumers uses PetFamily.SharedKernel.Contracts.Events.Auth✕
- Connections
- 1 pair of types, where a type in Notification.Hosts.Consumers.Consumers uses a type in PetFamily.SharedKernel.Contracts.Events.Auth.
- The types involved
Notification.Hosts.Consumers.Consumers.UserCreatedEventConsumer→PetFamily.SharedKernel.Contracts.Events.Auth.UserCreatedEvent
- Direction
- Notification.Hosts.Consumers.Consumers uses PetFamily.SharedKernel.Contracts.Events.Auth, so a change to PetFamily.SharedKernel.Contracts.Events.Auth can break Notification.Hosts.Consumers.Consumers, while a change to Notification.Hosts.Consumers.Consumers can't break PetFamily.SharedKernel.Contracts.Events.Auth.
- Position
- Below the diagonal: Notification.Hosts.Consumers.Consumers uses a module listed above it, which is the healthy direction.
16→7 Notification.Hosts.Consumers.Consumers uses PetFamily.SharedKernel.Infrastructure.Abstractions✕
- Connections
- 1 pair of types, where a type in Notification.Hosts.Consumers.Consumers uses a type in PetFamily.SharedKernel.Infrastructure.Abstractions.
- The types involved
Notification.Hosts.Consumers.Consumers.UserCreatedEventConsumer→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepository
- Direction
- Notification.Hosts.Consumers.Consumers uses PetFamily.SharedKernel.Infrastructure.Abstractions, so a change to PetFamily.SharedKernel.Infrastructure.Abstractions can break Notification.Hosts.Consumers.Consumers, while a change to Notification.Hosts.Consumers.Consumers can't break PetFamily.SharedKernel.Infrastructure.Abstractions.
- Position
- Below the diagonal: Notification.Hosts.Consumers.Consumers uses a module listed above it, which is the healthy direction.
17→7 PetFamily.SharedKernel.Infrastructure uses PetFamily.SharedKernel.Infrastructure.Abstractions✕
- Connections
- 1 pair of types, where a type in PetFamily.SharedKernel.Infrastructure uses a type in PetFamily.SharedKernel.Infrastructure.Abstractions.
- The types involved
PetFamily.SharedKernel.Infrastructure.EntityFrameworkRepository→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepository
- Direction
- PetFamily.SharedKernel.Infrastructure uses PetFamily.SharedKernel.Infrastructure.Abstractions, so a change to PetFamily.SharedKernel.Infrastructure.Abstractions can break PetFamily.SharedKernel.Infrastructure, while a change to PetFamily.SharedKernel.Infrastructure can't break PetFamily.SharedKernel.Infrastructure.Abstractions.
- Position
- Below the diagonal: PetFamily.SharedKernel.Infrastructure uses a module listed above it, which is the healthy direction.
18→6 VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 2 pairs of types, where a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties.AnimalKind→PetFamily.SharedKernel.Domain.Primitives.ValueObjectVolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties.BreedName→PetFamily.SharedKernel.Domain.Primitives.ValueObject
- Direction
- VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties, while a change to VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties uses a module listed above it, which is the healthy direction.
19→6 VolunteerManagement.Domain.Aggregates.Shelters.Entities uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.Shelters.Entities uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
VolunteerManagement.Domain.Aggregates.Shelters.Entities.VolunteerAssignment→PetFamily.SharedKernel.Domain.Primitives.Entity
- Direction
- VolunteerManagement.Domain.Aggregates.Shelters.Entities uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break VolunteerManagement.Domain.Aggregates.Shelters.Entities, while a change to VolunteerManagement.Domain.Aggregates.Shelters.Entities can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.Shelters.Entities uses a module listed above it, which is the healthy direction.
20→6 VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 9 pairs of types, where a type in VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.Address→PetFamily.SharedKernel.Domain.Primitives.ValueObjectVolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.Description→PetFamily.SharedKernel.Domain.Primitives.ValueObjectVolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.FullName→PetFamily.SharedKernel.Domain.Primitives.ValueObjectVolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.NickName→PetFamily.SharedKernel.Domain.Primitives.ValueObjectVolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.PetPhysicalAttributes→PetFamily.SharedKernel.Domain.Primitives.ValueObjectVolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.PhoneNumber→PetFamily.SharedKernel.Domain.Primitives.ValueObjectVolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.Photo→PetFamily.SharedKernel.Domain.Primitives.ValueObjectVolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.Position→PetFamily.SharedKernel.Domain.Primitives.ValueObjectVolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.Requisite→PetFamily.SharedKernel.Domain.Primitives.ValueObject
- Direction
- VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties, while a change to VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties uses a module listed above it, which is the healthy direction.
21→7 Account.Services uses PetFamily.SharedKernel.Infrastructure.Abstractions✕
- Connections
- 1 pair of types, where a type in Account.Services uses a type in PetFamily.SharedKernel.Infrastructure.Abstractions.
- The types involved
Account.Services.AccountService→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepository
- Direction
- Account.Services uses PetFamily.SharedKernel.Infrastructure.Abstractions, so a change to PetFamily.SharedKernel.Infrastructure.Abstractions can break Account.Services, while a change to Account.Services can't break PetFamily.SharedKernel.Infrastructure.Abstractions.
- Position
- Below the diagonal: Account.Services uses a module listed above it, which is the healthy direction.
21→12 Account.Services uses Account.Domain.Aggregates✕
- Connections
- 2 pairs of types, where a type in Account.Services uses a type in Account.Domain.Aggregates.
- The types involved
Account.Services.AccountService→Account.Domain.Aggregates.AccountAccount.Services.IAccountService→Account.Domain.Aggregates.Account
- Direction
- Account.Services uses Account.Domain.Aggregates, so a change to Account.Domain.Aggregates can break Account.Services, while a change to Account.Services can't break Account.Domain.Aggregates.
- Position
- Below the diagonal: Account.Services uses a module listed above it, which is the healthy direction.
22→1 Auth.Application.Services uses Auth.Contracts.Dtos✕
- Connections
- 4 pairs of types, where a type in Auth.Application.Services uses a type in Auth.Contracts.Dtos.
- The types involved
Auth.Application.Services.AuthService→Auth.Contracts.Dtos.AuthTokenResponseAuth.Application.Services.AuthService→Auth.Contracts.Dtos.UserDtoAuth.Application.Services.IAuthService→Auth.Contracts.Dtos.AuthTokenResponseAuth.Application.Services.IAuthService→Auth.Contracts.Dtos.UserDto
- Direction
- Auth.Application.Services uses Auth.Contracts.Dtos, so a change to Auth.Contracts.Dtos can break Auth.Application.Services, while a change to Auth.Application.Services can't break Auth.Contracts.Dtos.
- Position
- Below the diagonal: Auth.Application.Services uses a module listed above it, which is the healthy direction.
22→2 Auth.Application.Services uses Auth.Infrastructure.Common✕
- Connections
- 1 pair of types, where a type in Auth.Application.Services uses a type in Auth.Infrastructure.Common.
- The types involved
Auth.Application.Services.AuthService→Auth.Infrastructure.Common.AuthDbContext
- Direction
- Auth.Application.Services uses Auth.Infrastructure.Common, so a change to Auth.Infrastructure.Common can break Auth.Application.Services, while a change to Auth.Application.Services can't break Auth.Infrastructure.Common.
- Position
- Below the diagonal: Auth.Application.Services uses a module listed above it, which is the healthy direction.
22→13 Auth.Application.Services uses Auth.Infrastructure.Services✕
- Connections
- 1 pair of types, where a type in Auth.Application.Services uses a type in Auth.Infrastructure.Services.
- The types involved
Auth.Application.Services.AuthService→Auth.Infrastructure.Services.IKeycloakService
- Direction
- Auth.Application.Services uses Auth.Infrastructure.Services, so a change to Auth.Infrastructure.Services can break Auth.Application.Services, while a change to Auth.Application.Services can't break Auth.Infrastructure.Services.
- Position
- Below the diagonal: Auth.Application.Services uses a module listed above it, which is the healthy direction.
23→1 Auth.Infrastructure.Services.Keycloak uses Auth.Contracts.Dtos✕
- Connections
- 1 pair of types, where a type in Auth.Infrastructure.Services.Keycloak uses a type in Auth.Contracts.Dtos.
- The types involved
Auth.Infrastructure.Services.Keycloak.KeycloakServiceAdapter→Auth.Contracts.Dtos.AuthTokenResponse
- Direction
- Auth.Infrastructure.Services.Keycloak uses Auth.Contracts.Dtos, so a change to Auth.Contracts.Dtos can break Auth.Infrastructure.Services.Keycloak, while a change to Auth.Infrastructure.Services.Keycloak can't break Auth.Contracts.Dtos.
- Position
- Below the diagonal: Auth.Infrastructure.Services.Keycloak uses a module listed above it, which is the healthy direction.
23→13 Auth.Infrastructure.Services.Keycloak uses Auth.Infrastructure.Services✕
- Connections
- 1 pair of types, where a type in Auth.Infrastructure.Services.Keycloak uses a type in Auth.Infrastructure.Services.
- The types involved
Auth.Infrastructure.Services.Keycloak.KeycloakServiceAdapter→Auth.Infrastructure.Services.IKeycloakService
- Direction
- Auth.Infrastructure.Services.Keycloak uses Auth.Infrastructure.Services, so a change to Auth.Infrastructure.Services can break Auth.Infrastructure.Services.Keycloak, while a change to Auth.Infrastructure.Services.Keycloak can't break Auth.Infrastructure.Services.
- Position
- Below the diagonal: Auth.Infrastructure.Services.Keycloak uses a module listed above it, which is the healthy direction.
24→6 Conversation.Domain.Aggregates uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 1 pair of types, where a type in Conversation.Domain.Aggregates uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
Conversation.Domain.Aggregates.Chat→PetFamily.SharedKernel.Domain.Primitives.Entity
- Direction
- Conversation.Domain.Aggregates uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break Conversation.Domain.Aggregates, while a change to Conversation.Domain.Aggregates can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: Conversation.Domain.Aggregates uses a module listed above it, which is the healthy direction.
24→14 Conversation.Domain.Aggregates uses Conversation.Domain.Aggregates.Entities✕
- Connections
- 1 pair of types, where a type in Conversation.Domain.Aggregates uses a type in Conversation.Domain.Aggregates.Entities.
- The types involved
Conversation.Domain.Aggregates.Chat→Conversation.Domain.Aggregates.Entities.Message
- Direction
- Conversation.Domain.Aggregates uses Conversation.Domain.Aggregates.Entities, so a change to Conversation.Domain.Aggregates.Entities can break Conversation.Domain.Aggregates, while a change to Conversation.Domain.Aggregates can't break Conversation.Domain.Aggregates.Entities.
- Position
- Below the diagonal: Conversation.Domain.Aggregates uses a module listed above it, which is the healthy direction.
25→6 VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.Breed→PetFamily.SharedKernel.Domain.Primitives.SoftDeletableEntity
- Direction
- VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities, while a change to VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities uses a module listed above it, which is the healthy direction.
25→18 VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities uses VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities uses a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties.
- The types involved
VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.Breed→VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties.BreedName
- Direction
- VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities uses VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties, so a change to VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties can break VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities, while a change to VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities can't break VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities uses a module listed above it, which is the healthy direction.
26→6 VolunteerManagement.Domain.Aggregates.Shelters uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.Shelters uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
VolunteerManagement.Domain.Aggregates.Shelters.Shelter→PetFamily.SharedKernel.Domain.Primitives.SoftDeletableEntity
- Direction
- VolunteerManagement.Domain.Aggregates.Shelters uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break VolunteerManagement.Domain.Aggregates.Shelters, while a change to VolunteerManagement.Domain.Aggregates.Shelters can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.Shelters uses a module listed above it, which is the healthy direction.
26→19 VolunteerManagement.Domain.Aggregates.Shelters uses VolunteerManagement.Domain.Aggregates.Shelters.Entities✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.Shelters uses a type in VolunteerManagement.Domain.Aggregates.Shelters.Entities.
- The types involved
VolunteerManagement.Domain.Aggregates.Shelters.Shelter→VolunteerManagement.Domain.Aggregates.Shelters.Entities.VolunteerAssignment
- Direction
- VolunteerManagement.Domain.Aggregates.Shelters uses VolunteerManagement.Domain.Aggregates.Shelters.Entities, so a change to VolunteerManagement.Domain.Aggregates.Shelters.Entities can break VolunteerManagement.Domain.Aggregates.Shelters, while a change to VolunteerManagement.Domain.Aggregates.Shelters can't break VolunteerManagement.Domain.Aggregates.Shelters.Entities.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.Shelters uses a module listed above it, which is the healthy direction.
26→20 VolunteerManagement.Domain.Aggregates.Shelters uses VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties✕
- Connections
- 3 pairs of types, where a type in VolunteerManagement.Domain.Aggregates.Shelters uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.
- The types involved
VolunteerManagement.Domain.Aggregates.Shelters.Shelter→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.AddressVolunteerManagement.Domain.Aggregates.Shelters.Shelter→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.DescriptionVolunteerManagement.Domain.Aggregates.Shelters.Shelter→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.PhoneNumber
- Direction
- VolunteerManagement.Domain.Aggregates.Shelters uses VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties, so a change to VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties can break VolunteerManagement.Domain.Aggregates.Shelters, while a change to VolunteerManagement.Domain.Aggregates.Shelters can't break VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.Shelters uses a module listed above it, which is the healthy direction.
27→6 VolunteerManagement.Domain.Aggregates.Volunteers.Entities uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.Volunteers.Entities uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
VolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet→PetFamily.SharedKernel.Domain.Primitives.SoftDeletableEntity
- Direction
- VolunteerManagement.Domain.Aggregates.Volunteers.Entities uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break VolunteerManagement.Domain.Aggregates.Volunteers.Entities, while a change to VolunteerManagement.Domain.Aggregates.Volunteers.Entities can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.Volunteers.Entities uses a module listed above it, which is the healthy direction.
27→20 VolunteerManagement.Domain.Aggregates.Volunteers.Entities uses VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties✕
- Connections
- 6 pairs of types, where a type in VolunteerManagement.Domain.Aggregates.Volunteers.Entities uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.
- The types involved
VolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.DescriptionVolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.NickNameVolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.PetPhysicalAttributesVolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.PhotoVolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.PositionVolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.Requisite
- Direction
- VolunteerManagement.Domain.Aggregates.Volunteers.Entities uses VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties, so a change to VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties can break VolunteerManagement.Domain.Aggregates.Volunteers.Entities, while a change to VolunteerManagement.Domain.Aggregates.Volunteers.Entities can't break VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.Volunteers.Entities uses a module listed above it, which is the healthy direction.
28→7 Conversation.Services uses PetFamily.SharedKernel.Infrastructure.Abstractions✕
- Connections
- 1 pair of types, where a type in Conversation.Services uses a type in PetFamily.SharedKernel.Infrastructure.Abstractions.
- The types involved
Conversation.Services.ChatService→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepository
- Direction
- Conversation.Services uses PetFamily.SharedKernel.Infrastructure.Abstractions, so a change to PetFamily.SharedKernel.Infrastructure.Abstractions can break Conversation.Services, while a change to Conversation.Services can't break PetFamily.SharedKernel.Infrastructure.Abstractions.
- Position
- Below the diagonal: Conversation.Services uses a module listed above it, which is the healthy direction.
28→24 Conversation.Services uses Conversation.Domain.Aggregates✕
- Connections
- 2 pairs of types, where a type in Conversation.Services uses a type in Conversation.Domain.Aggregates.
- The types involved
Conversation.Services.ChatService→Conversation.Domain.Aggregates.ChatConversation.Services.IChatService→Conversation.Domain.Aggregates.Chat
- Direction
- Conversation.Services uses Conversation.Domain.Aggregates, so a change to Conversation.Domain.Aggregates can break Conversation.Services, while a change to Conversation.Services can't break Conversation.Domain.Aggregates.
- Position
- Below the diagonal: Conversation.Services uses a module listed above it, which is the healthy direction.
29→6 VolunteerManagement.Domain.Aggregates.AnimalKinds uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.AnimalKinds uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
VolunteerManagement.Domain.Aggregates.AnimalKinds.Species→PetFamily.SharedKernel.Domain.Primitives.SoftDeletableEntity
- Direction
- VolunteerManagement.Domain.Aggregates.AnimalKinds uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break VolunteerManagement.Domain.Aggregates.AnimalKinds, while a change to VolunteerManagement.Domain.Aggregates.AnimalKinds can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.AnimalKinds uses a module listed above it, which is the healthy direction.
29→18 VolunteerManagement.Domain.Aggregates.AnimalKinds uses VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.AnimalKinds uses a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties.
- The types involved
VolunteerManagement.Domain.Aggregates.AnimalKinds.Species→VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties.AnimalKind
- Direction
- VolunteerManagement.Domain.Aggregates.AnimalKinds uses VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties, so a change to VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties can break VolunteerManagement.Domain.Aggregates.AnimalKinds, while a change to VolunteerManagement.Domain.Aggregates.AnimalKinds can't break VolunteerManagement.Domain.Aggregates.AnimalKinds.ValueObjects.Properties.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.AnimalKinds uses a module listed above it, which is the healthy direction.
29→25 VolunteerManagement.Domain.Aggregates.AnimalKinds uses VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.AnimalKinds uses a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.
- The types involved
VolunteerManagement.Domain.Aggregates.AnimalKinds.Species→VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.Breed
- Direction
- VolunteerManagement.Domain.Aggregates.AnimalKinds uses VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities, so a change to VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities can break VolunteerManagement.Domain.Aggregates.AnimalKinds, while a change to VolunteerManagement.Domain.Aggregates.AnimalKinds can't break VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.AnimalKinds uses a module listed above it, which is the healthy direction.
30→6 VolunteerManagement.Domain.Aggregates.Volunteers uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.Volunteers uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
VolunteerManagement.Domain.Aggregates.Volunteers.Volunteer→PetFamily.SharedKernel.Domain.Primitives.SoftDeletableEntity
- Direction
- VolunteerManagement.Domain.Aggregates.Volunteers uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break VolunteerManagement.Domain.Aggregates.Volunteers, while a change to VolunteerManagement.Domain.Aggregates.Volunteers can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.Volunteers uses a module listed above it, which is the healthy direction.
30→20 VolunteerManagement.Domain.Aggregates.Volunteers uses VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties✕
- Connections
- 2 pairs of types, where a type in VolunteerManagement.Domain.Aggregates.Volunteers uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.
- The types involved
VolunteerManagement.Domain.Aggregates.Volunteers.Volunteer→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.FullNameVolunteerManagement.Domain.Aggregates.Volunteers.Volunteer→VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.Position
- Direction
- VolunteerManagement.Domain.Aggregates.Volunteers uses VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties, so a change to VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties can break VolunteerManagement.Domain.Aggregates.Volunteers, while a change to VolunteerManagement.Domain.Aggregates.Volunteers can't break VolunteerManagement.Domain.Aggregates.Volunteers.ValueObjects.Properties.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.Volunteers uses a module listed above it, which is the healthy direction.
30→27 VolunteerManagement.Domain.Aggregates.Volunteers uses VolunteerManagement.Domain.Aggregates.Volunteers.Entities✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Domain.Aggregates.Volunteers uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.Entities.
- The types involved
VolunteerManagement.Domain.Aggregates.Volunteers.Volunteer→VolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet
- Direction
- VolunteerManagement.Domain.Aggregates.Volunteers uses VolunteerManagement.Domain.Aggregates.Volunteers.Entities, so a change to VolunteerManagement.Domain.Aggregates.Volunteers.Entities can break VolunteerManagement.Domain.Aggregates.Volunteers, while a change to VolunteerManagement.Domain.Aggregates.Volunteers can't break VolunteerManagement.Domain.Aggregates.Volunteers.Entities.
- Position
- Below the diagonal: VolunteerManagement.Domain.Aggregates.Volunteers uses a module listed above it, which is the healthy direction.
31→7 VolunteerManagement.Services.Shelters uses PetFamily.SharedKernel.Infrastructure.Abstractions✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Services.Shelters uses a type in PetFamily.SharedKernel.Infrastructure.Abstractions.
- The types involved
VolunteerManagement.Services.Shelters.ShelterService→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepository
- Direction
- VolunteerManagement.Services.Shelters uses PetFamily.SharedKernel.Infrastructure.Abstractions, so a change to PetFamily.SharedKernel.Infrastructure.Abstractions can break VolunteerManagement.Services.Shelters, while a change to VolunteerManagement.Services.Shelters can't break PetFamily.SharedKernel.Infrastructure.Abstractions.
- Position
- Below the diagonal: VolunteerManagement.Services.Shelters uses a module listed above it, which is the healthy direction.
31→26 VolunteerManagement.Services.Shelters uses VolunteerManagement.Domain.Aggregates.Shelters✕
- Connections
- 2 pairs of types, where a type in VolunteerManagement.Services.Shelters uses a type in VolunteerManagement.Domain.Aggregates.Shelters.
- The types involved
VolunteerManagement.Services.Shelters.IShelterService→VolunteerManagement.Domain.Aggregates.Shelters.ShelterVolunteerManagement.Services.Shelters.ShelterService→VolunteerManagement.Domain.Aggregates.Shelters.Shelter
- Direction
- VolunteerManagement.Services.Shelters uses VolunteerManagement.Domain.Aggregates.Shelters, so a change to VolunteerManagement.Domain.Aggregates.Shelters can break VolunteerManagement.Services.Shelters, while a change to VolunteerManagement.Services.Shelters can't break VolunteerManagement.Domain.Aggregates.Shelters.
- Position
- Below the diagonal: VolunteerManagement.Services.Shelters uses a module listed above it, which is the healthy direction.
32→11 VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Services.Volunteers.Dtos✕
- Connections
- 2 pairs of types, where a type in VolunteerManagement.Handlers.MappingExtensions uses a type in VolunteerManagement.Services.Volunteers.Dtos.
- The types involved
VolunteerManagement.Handlers.MappingExtensions.PetMappingExtensions→VolunteerManagement.Services.Volunteers.Dtos.PetDtoVolunteerManagement.Handlers.MappingExtensions.VolunteerMappingExtensions→VolunteerManagement.Services.Volunteers.Dtos.VolunteerDto
- Direction
- VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Services.Volunteers.Dtos, so a change to VolunteerManagement.Services.Volunteers.Dtos can break VolunteerManagement.Handlers.MappingExtensions, while a change to VolunteerManagement.Handlers.MappingExtensions can't break VolunteerManagement.Services.Volunteers.Dtos.
- Position
- Below the diagonal: VolunteerManagement.Handlers.MappingExtensions uses a module listed above it, which is the healthy direction.
32→19 VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.Shelters.Entities✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Handlers.MappingExtensions uses a type in VolunteerManagement.Domain.Aggregates.Shelters.Entities.
- The types involved
VolunteerManagement.Handlers.MappingExtensions.ShelterMappingExtensions→VolunteerManagement.Domain.Aggregates.Shelters.Entities.VolunteerAssignment
- Direction
- VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.Shelters.Entities, so a change to VolunteerManagement.Domain.Aggregates.Shelters.Entities can break VolunteerManagement.Handlers.MappingExtensions, while a change to VolunteerManagement.Handlers.MappingExtensions can't break VolunteerManagement.Domain.Aggregates.Shelters.Entities.
- Position
- Below the diagonal: VolunteerManagement.Handlers.MappingExtensions uses a module listed above it, which is the healthy direction.
32→25 VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Handlers.MappingExtensions uses a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.
- The types involved
VolunteerManagement.Handlers.MappingExtensions.SpeciesMappingExtensions→VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.Breed
- Direction
- VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities, so a change to VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities can break VolunteerManagement.Handlers.MappingExtensions, while a change to VolunteerManagement.Handlers.MappingExtensions can't break VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.
- Position
- Below the diagonal: VolunteerManagement.Handlers.MappingExtensions uses a module listed above it, which is the healthy direction.
32→26 VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.Shelters✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Handlers.MappingExtensions uses a type in VolunteerManagement.Domain.Aggregates.Shelters.
- The types involved
VolunteerManagement.Handlers.MappingExtensions.ShelterMappingExtensions→VolunteerManagement.Domain.Aggregates.Shelters.Shelter
- Direction
- VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.Shelters, so a change to VolunteerManagement.Domain.Aggregates.Shelters can break VolunteerManagement.Handlers.MappingExtensions, while a change to VolunteerManagement.Handlers.MappingExtensions can't break VolunteerManagement.Domain.Aggregates.Shelters.
- Position
- Below the diagonal: VolunteerManagement.Handlers.MappingExtensions uses a module listed above it, which is the healthy direction.
32→27 VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.Volunteers.Entities✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Handlers.MappingExtensions uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.Entities.
- The types involved
VolunteerManagement.Handlers.MappingExtensions.PetMappingExtensions→VolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet
- Direction
- VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.Volunteers.Entities, so a change to VolunteerManagement.Domain.Aggregates.Volunteers.Entities can break VolunteerManagement.Handlers.MappingExtensions, while a change to VolunteerManagement.Handlers.MappingExtensions can't break VolunteerManagement.Domain.Aggregates.Volunteers.Entities.
- Position
- Below the diagonal: VolunteerManagement.Handlers.MappingExtensions uses a module listed above it, which is the healthy direction.
32→29 VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.AnimalKinds✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Handlers.MappingExtensions uses a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.
- The types involved
VolunteerManagement.Handlers.MappingExtensions.SpeciesMappingExtensions→VolunteerManagement.Domain.Aggregates.AnimalKinds.Species
- Direction
- VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.AnimalKinds, so a change to VolunteerManagement.Domain.Aggregates.AnimalKinds can break VolunteerManagement.Handlers.MappingExtensions, while a change to VolunteerManagement.Handlers.MappingExtensions can't break VolunteerManagement.Domain.Aggregates.AnimalKinds.
- Position
- Below the diagonal: VolunteerManagement.Handlers.MappingExtensions uses a module listed above it, which is the healthy direction.
32→30 VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.Volunteers✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Handlers.MappingExtensions uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.
- The types involved
VolunteerManagement.Handlers.MappingExtensions.VolunteerMappingExtensions→VolunteerManagement.Domain.Aggregates.Volunteers.Volunteer
- Direction
- VolunteerManagement.Handlers.MappingExtensions uses VolunteerManagement.Domain.Aggregates.Volunteers, so a change to VolunteerManagement.Domain.Aggregates.Volunteers can break VolunteerManagement.Handlers.MappingExtensions, while a change to VolunteerManagement.Handlers.MappingExtensions can't break VolunteerManagement.Domain.Aggregates.Volunteers.
- Position
- Below the diagonal: VolunteerManagement.Handlers.MappingExtensions uses a module listed above it, which is the healthy direction.
33→5 VolunteerManagement.Hosts.Consumers.Consumers uses PetFamily.SharedKernel.Contracts.Events.Auth✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Hosts.Consumers.Consumers uses a type in PetFamily.SharedKernel.Contracts.Events.Auth.
- The types involved
VolunteerManagement.Hosts.Consumers.Consumers.UserCreatedEventConsumer→PetFamily.SharedKernel.Contracts.Events.Auth.UserCreatedEvent
- Direction
- VolunteerManagement.Hosts.Consumers.Consumers uses PetFamily.SharedKernel.Contracts.Events.Auth, so a change to PetFamily.SharedKernel.Contracts.Events.Auth can break VolunteerManagement.Hosts.Consumers.Consumers, while a change to VolunteerManagement.Hosts.Consumers.Consumers can't break PetFamily.SharedKernel.Contracts.Events.Auth.
- Position
- Below the diagonal: VolunteerManagement.Hosts.Consumers.Consumers uses a module listed above it, which is the healthy direction.
33→7 VolunteerManagement.Hosts.Consumers.Consumers uses PetFamily.SharedKernel.Infrastructure.Abstractions✕
- Connections
- 3 pairs of types, where a type in VolunteerManagement.Hosts.Consumers.Consumers uses a type in PetFamily.SharedKernel.Infrastructure.Abstractions.
- The types involved
VolunteerManagement.Hosts.Consumers.Consumers.AdoptPetConsumer→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepositoryVolunteerManagement.Hosts.Consumers.Consumers.ReservePetConsumer→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepositoryVolunteerManagement.Hosts.Consumers.Consumers.UnreservePetConsumer→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepository
- Direction
- VolunteerManagement.Hosts.Consumers.Consumers uses PetFamily.SharedKernel.Infrastructure.Abstractions, so a change to PetFamily.SharedKernel.Infrastructure.Abstractions can break VolunteerManagement.Hosts.Consumers.Consumers, while a change to VolunteerManagement.Hosts.Consumers.Consumers can't break PetFamily.SharedKernel.Infrastructure.Abstractions.
- Position
- Below the diagonal: VolunteerManagement.Hosts.Consumers.Consumers uses a module listed above it, which is the healthy direction.
33→30 VolunteerManagement.Hosts.Consumers.Consumers uses VolunteerManagement.Domain.Aggregates.Volunteers✕
- Connections
- 3 pairs of types, where a type in VolunteerManagement.Hosts.Consumers.Consumers uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.
- The types involved
VolunteerManagement.Hosts.Consumers.Consumers.AdoptPetConsumer→VolunteerManagement.Domain.Aggregates.Volunteers.VolunteerVolunteerManagement.Hosts.Consumers.Consumers.ReservePetConsumer→VolunteerManagement.Domain.Aggregates.Volunteers.VolunteerVolunteerManagement.Hosts.Consumers.Consumers.UnreservePetConsumer→VolunteerManagement.Domain.Aggregates.Volunteers.Volunteer
- Direction
- VolunteerManagement.Hosts.Consumers.Consumers uses VolunteerManagement.Domain.Aggregates.Volunteers, so a change to VolunteerManagement.Domain.Aggregates.Volunteers can break VolunteerManagement.Hosts.Consumers.Consumers, while a change to VolunteerManagement.Hosts.Consumers.Consumers can't break VolunteerManagement.Domain.Aggregates.Volunteers.
- Position
- Below the diagonal: VolunteerManagement.Hosts.Consumers.Consumers uses a module listed above it, which is the healthy direction.
34→19 VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.Shelters.Entities✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Infrastructure.Common.Configurations uses a type in VolunteerManagement.Domain.Aggregates.Shelters.Entities.
- The types involved
VolunteerManagement.Infrastructure.Common.Configurations.VolunteerAssignmentConfiguration→VolunteerManagement.Domain.Aggregates.Shelters.Entities.VolunteerAssignment
- Direction
- VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.Shelters.Entities, so a change to VolunteerManagement.Domain.Aggregates.Shelters.Entities can break VolunteerManagement.Infrastructure.Common.Configurations, while a change to VolunteerManagement.Infrastructure.Common.Configurations can't break VolunteerManagement.Domain.Aggregates.Shelters.Entities.
- Position
- Below the diagonal: VolunteerManagement.Infrastructure.Common.Configurations uses a module listed above it, which is the healthy direction.
34→25 VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Infrastructure.Common.Configurations uses a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.
- The types involved
VolunteerManagement.Infrastructure.Common.Configurations.BreedConfiguration→VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.Breed
- Direction
- VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities, so a change to VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities can break VolunteerManagement.Infrastructure.Common.Configurations, while a change to VolunteerManagement.Infrastructure.Common.Configurations can't break VolunteerManagement.Domain.Aggregates.AnimalKinds.Entities.
- Position
- Below the diagonal: VolunteerManagement.Infrastructure.Common.Configurations uses a module listed above it, which is the healthy direction.
34→26 VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.Shelters✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Infrastructure.Common.Configurations uses a type in VolunteerManagement.Domain.Aggregates.Shelters.
- The types involved
VolunteerManagement.Infrastructure.Common.Configurations.ShelterConfiguration→VolunteerManagement.Domain.Aggregates.Shelters.Shelter
- Direction
- VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.Shelters, so a change to VolunteerManagement.Domain.Aggregates.Shelters can break VolunteerManagement.Infrastructure.Common.Configurations, while a change to VolunteerManagement.Infrastructure.Common.Configurations can't break VolunteerManagement.Domain.Aggregates.Shelters.
- Position
- Below the diagonal: VolunteerManagement.Infrastructure.Common.Configurations uses a module listed above it, which is the healthy direction.
34→27 VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.Volunteers.Entities✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Infrastructure.Common.Configurations uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.Entities.
- The types involved
VolunteerManagement.Infrastructure.Common.Configurations.PetConfiguration→VolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet
- Direction
- VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.Volunteers.Entities, so a change to VolunteerManagement.Domain.Aggregates.Volunteers.Entities can break VolunteerManagement.Infrastructure.Common.Configurations, while a change to VolunteerManagement.Infrastructure.Common.Configurations can't break VolunteerManagement.Domain.Aggregates.Volunteers.Entities.
- Position
- Below the diagonal: VolunteerManagement.Infrastructure.Common.Configurations uses a module listed above it, which is the healthy direction.
34→29 VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.AnimalKinds✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Infrastructure.Common.Configurations uses a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.
- The types involved
VolunteerManagement.Infrastructure.Common.Configurations.SpeciesConfiguration→VolunteerManagement.Domain.Aggregates.AnimalKinds.Species
- Direction
- VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.AnimalKinds, so a change to VolunteerManagement.Domain.Aggregates.AnimalKinds can break VolunteerManagement.Infrastructure.Common.Configurations, while a change to VolunteerManagement.Infrastructure.Common.Configurations can't break VolunteerManagement.Domain.Aggregates.AnimalKinds.
- Position
- Below the diagonal: VolunteerManagement.Infrastructure.Common.Configurations uses a module listed above it, which is the healthy direction.
34→30 VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.Volunteers✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Infrastructure.Common.Configurations uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.
- The types involved
VolunteerManagement.Infrastructure.Common.Configurations.VolunteerConfiguration→VolunteerManagement.Domain.Aggregates.Volunteers.Volunteer
- Direction
- VolunteerManagement.Infrastructure.Common.Configurations uses VolunteerManagement.Domain.Aggregates.Volunteers, so a change to VolunteerManagement.Domain.Aggregates.Volunteers can break VolunteerManagement.Infrastructure.Common.Configurations, while a change to VolunteerManagement.Infrastructure.Common.Configurations can't break VolunteerManagement.Domain.Aggregates.Volunteers.
- Position
- Below the diagonal: VolunteerManagement.Infrastructure.Common.Configurations uses a module listed above it, which is the healthy direction.
35→26 VolunteerManagement.Infrastructure.Common.Contexts uses VolunteerManagement.Domain.Aggregates.Shelters✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Infrastructure.Common.Contexts uses a type in VolunteerManagement.Domain.Aggregates.Shelters.
- The types involved
VolunteerManagement.Infrastructure.Common.Contexts.VolunteerManagementDbContext→VolunteerManagement.Domain.Aggregates.Shelters.Shelter
- Direction
- VolunteerManagement.Infrastructure.Common.Contexts uses VolunteerManagement.Domain.Aggregates.Shelters, so a change to VolunteerManagement.Domain.Aggregates.Shelters can break VolunteerManagement.Infrastructure.Common.Contexts, while a change to VolunteerManagement.Infrastructure.Common.Contexts can't break VolunteerManagement.Domain.Aggregates.Shelters.
- Position
- Below the diagonal: VolunteerManagement.Infrastructure.Common.Contexts uses a module listed above it, which is the healthy direction.
35→27 VolunteerManagement.Infrastructure.Common.Contexts uses VolunteerManagement.Domain.Aggregates.Volunteers.Entities✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Infrastructure.Common.Contexts uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.Entities.
- The types involved
VolunteerManagement.Infrastructure.Common.Contexts.VolunteerManagementDbContext→VolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet
- Direction
- VolunteerManagement.Infrastructure.Common.Contexts uses VolunteerManagement.Domain.Aggregates.Volunteers.Entities, so a change to VolunteerManagement.Domain.Aggregates.Volunteers.Entities can break VolunteerManagement.Infrastructure.Common.Contexts, while a change to VolunteerManagement.Infrastructure.Common.Contexts can't break VolunteerManagement.Domain.Aggregates.Volunteers.Entities.
- Position
- Below the diagonal: VolunteerManagement.Infrastructure.Common.Contexts uses a module listed above it, which is the healthy direction.
35→29 VolunteerManagement.Infrastructure.Common.Contexts uses VolunteerManagement.Domain.Aggregates.AnimalKinds✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Infrastructure.Common.Contexts uses a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.
- The types involved
VolunteerManagement.Infrastructure.Common.Contexts.VolunteerManagementDbContext→VolunteerManagement.Domain.Aggregates.AnimalKinds.Species
- Direction
- VolunteerManagement.Infrastructure.Common.Contexts uses VolunteerManagement.Domain.Aggregates.AnimalKinds, so a change to VolunteerManagement.Domain.Aggregates.AnimalKinds can break VolunteerManagement.Infrastructure.Common.Contexts, while a change to VolunteerManagement.Infrastructure.Common.Contexts can't break VolunteerManagement.Domain.Aggregates.AnimalKinds.
- Position
- Below the diagonal: VolunteerManagement.Infrastructure.Common.Contexts uses a module listed above it, which is the healthy direction.
35→30 VolunteerManagement.Infrastructure.Common.Contexts uses VolunteerManagement.Domain.Aggregates.Volunteers✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Infrastructure.Common.Contexts uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.
- The types involved
VolunteerManagement.Infrastructure.Common.Contexts.VolunteerManagementDbContext→VolunteerManagement.Domain.Aggregates.Volunteers.Volunteer
- Direction
- VolunteerManagement.Infrastructure.Common.Contexts uses VolunteerManagement.Domain.Aggregates.Volunteers, so a change to VolunteerManagement.Domain.Aggregates.Volunteers can break VolunteerManagement.Infrastructure.Common.Contexts, while a change to VolunteerManagement.Infrastructure.Common.Contexts can't break VolunteerManagement.Domain.Aggregates.Volunteers.
- Position
- Below the diagonal: VolunteerManagement.Infrastructure.Common.Contexts uses a module listed above it, which is the healthy direction.
36→7 VolunteerManagement.Services.AnimalKinds uses PetFamily.SharedKernel.Infrastructure.Abstractions✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Services.AnimalKinds uses a type in PetFamily.SharedKernel.Infrastructure.Abstractions.
- The types involved
VolunteerManagement.Services.AnimalKinds.SpeciesService→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepository
- Direction
- VolunteerManagement.Services.AnimalKinds uses PetFamily.SharedKernel.Infrastructure.Abstractions, so a change to PetFamily.SharedKernel.Infrastructure.Abstractions can break VolunteerManagement.Services.AnimalKinds, while a change to VolunteerManagement.Services.AnimalKinds can't break PetFamily.SharedKernel.Infrastructure.Abstractions.
- Position
- Below the diagonal: VolunteerManagement.Services.AnimalKinds uses a module listed above it, which is the healthy direction.
36→29 VolunteerManagement.Services.AnimalKinds uses VolunteerManagement.Domain.Aggregates.AnimalKinds✕
- Connections
- 2 pairs of types, where a type in VolunteerManagement.Services.AnimalKinds uses a type in VolunteerManagement.Domain.Aggregates.AnimalKinds.
- The types involved
VolunteerManagement.Services.AnimalKinds.ISpeciesService→VolunteerManagement.Domain.Aggregates.AnimalKinds.SpeciesVolunteerManagement.Services.AnimalKinds.SpeciesService→VolunteerManagement.Domain.Aggregates.AnimalKinds.Species
- Direction
- VolunteerManagement.Services.AnimalKinds uses VolunteerManagement.Domain.Aggregates.AnimalKinds, so a change to VolunteerManagement.Domain.Aggregates.AnimalKinds can break VolunteerManagement.Services.AnimalKinds, while a change to VolunteerManagement.Services.AnimalKinds can't break VolunteerManagement.Domain.Aggregates.AnimalKinds.
- Position
- Below the diagonal: VolunteerManagement.Services.AnimalKinds uses a module listed above it, which is the healthy direction.
37→7 VolunteerManagement.Services.Volunteers uses PetFamily.SharedKernel.Infrastructure.Abstractions✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Services.Volunteers uses a type in PetFamily.SharedKernel.Infrastructure.Abstractions.
- The types involved
VolunteerManagement.Services.Volunteers.VolunteerService→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepository
- Direction
- VolunteerManagement.Services.Volunteers uses PetFamily.SharedKernel.Infrastructure.Abstractions, so a change to PetFamily.SharedKernel.Infrastructure.Abstractions can break VolunteerManagement.Services.Volunteers, while a change to VolunteerManagement.Services.Volunteers can't break PetFamily.SharedKernel.Infrastructure.Abstractions.
- Position
- Below the diagonal: VolunteerManagement.Services.Volunteers uses a module listed above it, which is the healthy direction.
37→30 VolunteerManagement.Services.Volunteers uses VolunteerManagement.Domain.Aggregates.Volunteers✕
- Connections
- 2 pairs of types, where a type in VolunteerManagement.Services.Volunteers uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.
- The types involved
VolunteerManagement.Services.Volunteers.IVolunteerService→VolunteerManagement.Domain.Aggregates.Volunteers.VolunteerVolunteerManagement.Services.Volunteers.VolunteerService→VolunteerManagement.Domain.Aggregates.Volunteers.Volunteer
- Direction
- VolunteerManagement.Services.Volunteers uses VolunteerManagement.Domain.Aggregates.Volunteers, so a change to VolunteerManagement.Domain.Aggregates.Volunteers can break VolunteerManagement.Services.Volunteers, while a change to VolunteerManagement.Services.Volunteers can't break VolunteerManagement.Domain.Aggregates.Volunteers.
- Position
- Below the diagonal: VolunteerManagement.Services.Volunteers uses a module listed above it, which is the healthy direction.
38→11 VolunteerManagement.Services.Volunteers.Adoption uses VolunteerManagement.Services.Volunteers.Dtos✕
- Connections
- 3 pairs of types, where a type in VolunteerManagement.Services.Volunteers.Adoption uses a type in VolunteerManagement.Services.Volunteers.Dtos.
- The types involved
VolunteerManagement.Services.Volunteers.Adoption.AdoptionStateMappingExtensions→VolunteerManagement.Services.Volunteers.Dtos.AdoptionStatusDtoVolunteerManagement.Services.Volunteers.Adoption.IPetAdoptionService→VolunteerManagement.Services.Volunteers.Dtos.AdoptionStatusDtoVolunteerManagement.Services.Volunteers.Adoption.PetAdoptionService→VolunteerManagement.Services.Volunteers.Dtos.AdoptionStatusDto
- Direction
- VolunteerManagement.Services.Volunteers.Adoption uses VolunteerManagement.Services.Volunteers.Dtos, so a change to VolunteerManagement.Services.Volunteers.Dtos can break VolunteerManagement.Services.Volunteers.Adoption, while a change to VolunteerManagement.Services.Volunteers.Adoption can't break VolunteerManagement.Services.Volunteers.Dtos.
- Position
- Below the diagonal: VolunteerManagement.Services.Volunteers.Adoption uses a module listed above it, which is the healthy direction.
38→35 VolunteerManagement.Services.Volunteers.Adoption uses VolunteerManagement.Infrastructure.Common.Contexts✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Services.Volunteers.Adoption uses a type in VolunteerManagement.Infrastructure.Common.Contexts.
- The types involved
VolunteerManagement.Services.Volunteers.Adoption.PetAdoptionService→VolunteerManagement.Infrastructure.Common.Contexts.VolunteerManagementDbContext
- Direction
- VolunteerManagement.Services.Volunteers.Adoption uses VolunteerManagement.Infrastructure.Common.Contexts, so a change to VolunteerManagement.Infrastructure.Common.Contexts can break VolunteerManagement.Services.Volunteers.Adoption, while a change to VolunteerManagement.Services.Volunteers.Adoption can't break VolunteerManagement.Infrastructure.Common.Contexts.
- Position
- Below the diagonal: VolunteerManagement.Services.Volunteers.Adoption uses a module listed above it, which is the healthy direction.
39→7 VolunteerManagement.Services.Volunteers.Pets uses PetFamily.SharedKernel.Infrastructure.Abstractions✕
- Connections
- 2 pairs of types, where a type in VolunteerManagement.Services.Volunteers.Pets uses a type in PetFamily.SharedKernel.Infrastructure.Abstractions.
- The types involved
VolunteerManagement.Services.Volunteers.Pets.PetSearchService→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepositoryVolunteerManagement.Services.Volunteers.Pets.PetService→PetFamily.SharedKernel.Infrastructure.Abstractions.IRepository
- Direction
- VolunteerManagement.Services.Volunteers.Pets uses PetFamily.SharedKernel.Infrastructure.Abstractions, so a change to PetFamily.SharedKernel.Infrastructure.Abstractions can break VolunteerManagement.Services.Volunteers.Pets, while a change to VolunteerManagement.Services.Volunteers.Pets can't break PetFamily.SharedKernel.Infrastructure.Abstractions.
- Position
- Below the diagonal: VolunteerManagement.Services.Volunteers.Pets uses a module listed above it, which is the healthy direction.
39→11 VolunteerManagement.Services.Volunteers.Pets uses VolunteerManagement.Services.Volunteers.Dtos✕
- Connections
- 2 pairs of types, where a type in VolunteerManagement.Services.Volunteers.Pets uses a type in VolunteerManagement.Services.Volunteers.Dtos.
- The types involved
VolunteerManagement.Services.Volunteers.Pets.IPetService→VolunteerManagement.Services.Volunteers.Dtos.RequisiteDtoVolunteerManagement.Services.Volunteers.Pets.PetService→VolunteerManagement.Services.Volunteers.Dtos.RequisiteDto
- Direction
- VolunteerManagement.Services.Volunteers.Pets uses VolunteerManagement.Services.Volunteers.Dtos, so a change to VolunteerManagement.Services.Volunteers.Dtos can break VolunteerManagement.Services.Volunteers.Pets, while a change to VolunteerManagement.Services.Volunteers.Pets can't break VolunteerManagement.Services.Volunteers.Dtos.
- Position
- Below the diagonal: VolunteerManagement.Services.Volunteers.Pets uses a module listed above it, which is the healthy direction.
39→27 VolunteerManagement.Services.Volunteers.Pets uses VolunteerManagement.Domain.Aggregates.Volunteers.Entities✕
- Connections
- 4 pairs of types, where a type in VolunteerManagement.Services.Volunteers.Pets uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.Entities.
- The types involved
VolunteerManagement.Services.Volunteers.Pets.IPetSearchService→VolunteerManagement.Domain.Aggregates.Volunteers.Entities.PetVolunteerManagement.Services.Volunteers.Pets.IPetService→VolunteerManagement.Domain.Aggregates.Volunteers.Entities.PetVolunteerManagement.Services.Volunteers.Pets.PetSearchService→VolunteerManagement.Domain.Aggregates.Volunteers.Entities.PetVolunteerManagement.Services.Volunteers.Pets.PetService→VolunteerManagement.Domain.Aggregates.Volunteers.Entities.Pet
- Direction
- VolunteerManagement.Services.Volunteers.Pets uses VolunteerManagement.Domain.Aggregates.Volunteers.Entities, so a change to VolunteerManagement.Domain.Aggregates.Volunteers.Entities can break VolunteerManagement.Services.Volunteers.Pets, while a change to VolunteerManagement.Services.Volunteers.Pets can't break VolunteerManagement.Domain.Aggregates.Volunteers.Entities.
- Position
- Below the diagonal: VolunteerManagement.Services.Volunteers.Pets uses a module listed above it, which is the healthy direction.
39→30 VolunteerManagement.Services.Volunteers.Pets uses VolunteerManagement.Domain.Aggregates.Volunteers✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Services.Volunteers.Pets uses a type in VolunteerManagement.Domain.Aggregates.Volunteers.
- The types involved
VolunteerManagement.Services.Volunteers.Pets.PetService→VolunteerManagement.Domain.Aggregates.Volunteers.Volunteer
- Direction
- VolunteerManagement.Services.Volunteers.Pets uses VolunteerManagement.Domain.Aggregates.Volunteers, so a change to VolunteerManagement.Domain.Aggregates.Volunteers can break VolunteerManagement.Services.Volunteers.Pets, while a change to VolunteerManagement.Services.Volunteers.Pets can't break VolunteerManagement.Domain.Aggregates.Volunteers.
- Position
- Below the diagonal: VolunteerManagement.Services.Volunteers.Pets uses a module listed above it, which is the healthy direction.
39→36 VolunteerManagement.Services.Volunteers.Pets uses VolunteerManagement.Services.AnimalKinds✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Services.Volunteers.Pets uses a type in VolunteerManagement.Services.AnimalKinds.
- The types involved
VolunteerManagement.Services.Volunteers.Pets.PetService→VolunteerManagement.Services.AnimalKinds.ISpeciesService
- Direction
- VolunteerManagement.Services.Volunteers.Pets uses VolunteerManagement.Services.AnimalKinds, so a change to VolunteerManagement.Services.AnimalKinds can break VolunteerManagement.Services.Volunteers.Pets, while a change to VolunteerManagement.Services.Volunteers.Pets can't break VolunteerManagement.Services.AnimalKinds.
- Position
- Below the diagonal: VolunteerManagement.Services.Volunteers.Pets uses a module listed above it, which is the healthy direction.
40→6 VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses PetFamily.SharedKernel.Domain.Primitives✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses a type in PetFamily.SharedKernel.Domain.Primitives.
- The types involved
VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add.AddPetCommand→PetFamily.SharedKernel.Domain.Primitives.Command
- Direction
- VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses PetFamily.SharedKernel.Domain.Primitives, so a change to PetFamily.SharedKernel.Domain.Primitives can break VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add, while a change to VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add can't break PetFamily.SharedKernel.Domain.Primitives.
- Position
- Below the diagonal: VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses a module listed above it, which is the healthy direction.
40→8 VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses PetFamily.SharedKernel.Infrastructure.Caching✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses a type in PetFamily.SharedKernel.Infrastructure.Caching.
- The types involved
VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add.AddPetHandler→PetFamily.SharedKernel.Infrastructure.Caching.ICacheService
- Direction
- VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses PetFamily.SharedKernel.Infrastructure.Caching, so a change to PetFamily.SharedKernel.Infrastructure.Caching can break VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add, while a change to VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add can't break PetFamily.SharedKernel.Infrastructure.Caching.
- Position
- Below the diagonal: VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses a module listed above it, which is the healthy direction.
40→11 VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses VolunteerManagement.Services.Volunteers.Dtos✕
- Connections
- 2 pairs of types, where a type in VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses a type in VolunteerManagement.Services.Volunteers.Dtos.
- The types involved
VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add.AddPetCommand→VolunteerManagement.Services.Volunteers.Dtos.AddressDtoVolunteerManagement.Handlers.Volunteers.Pets.Commands.Add.AddPetCommand→VolunteerManagement.Services.Volunteers.Dtos.RequisiteDto
- Direction
- VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses VolunteerManagement.Services.Volunteers.Dtos, so a change to VolunteerManagement.Services.Volunteers.Dtos can break VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add, while a change to VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add can't break VolunteerManagement.Services.Volunteers.Dtos.
- Position
- Below the diagonal: VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses a module listed above it, which is the healthy direction.
40→39 VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses VolunteerManagement.Services.Volunteers.Pets✕
- Connections
- 1 pair of types, where a type in VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses a type in VolunteerManagement.Services.Volunteers.Pets.
- The types involved
VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add.AddPetHandler→VolunteerManagement.Services.Volunteers.Pets.IPetService
- Direction
- VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add uses VolunteerManagement.Services.Volunteers.Pets, so a change to VolunteerManagement.Services.Volunteers.Pets can break VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add, while a change to VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add can't break VolunteerManagement.Services.Volunteers.Pets.
- Position
- Below the diagonal: VolunteerManagement.Handlers.Volunteers.Pets.Commands.Add 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 |
|---|---|---|
| A02:2025 — Security Misconfiguration | 99 | High / Critical |
| A05:2025 — Injection | 17 | High / Critical |
| A07:2025 — Authentication Failures | 12 | High / Critical |
| A01:2025 — Broken Access Control | 1 | Medium |
Roadmap
Top priorities: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.); Resolve the 68 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (31), REDACTED (22), REDACTED (15); Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.). | +8.1 pts | Medium | Data Protection |
| Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (2). | +3.7 pts | Low | REDACTED Scanning |
| Resolve the 68 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (31), REDACTED (22), REDACTED (15). | +5.2 pts | Medium | IaC & Container Security |
| Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly). | +4.9 pts | Medium | Web-Security Posture |
| Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. | +1.9 pts | Low | Secrets (history) |
| Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2). | +3.3 pts | Medium | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. | +1.5 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 95 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 95 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, 296 of 313 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes, and real coverage will be read. You can widen what we reach: optional: your test projects already reference a coverage collector, but no CI step we found runs the tests with it, so there is no report to hand us — run them with `--collect:"XPlat Code Coverage"` and commit (or publish into the working tree) the coverage.cobertura.xml it writes, and the real number is read on the next scan.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/NuGet.targets(521,5): error MSB3202: The project file "Solution/FileStorage/Hosts/FileStorage.Api/FileStorage.Api.csproj" was not found. [Solution/FileStorage/File….
- 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. Too few commits for a meaningful bus factor (36 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Solution/Account/Hosts/Account.Hosts.Consumers/Account.Hosts.Consumers.csproj' with message: Detected package version outside of dependency constraint: Microsoft.CodeAnalysis.Workspaces.MSBuild 4.14.0 requires Microsoft.CodeAnalysis.Workspaces.Common (= 4.14.0) but version Microsoft.CodeAnalysis.….
- D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
- 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) — 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. `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserCreatedEvent.cs`, `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserDeletedEvent.cs`, `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserRoleChangedEvent.cs`, `Shared/PetFamily.SharedKernel.Contracts/Events/FileStorage/FileDeleteRequestedEvent.cs`, `Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs`, … (+106 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.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (36 commit(s) sampled).
- D39 IL Efficiency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — postgres-conversation Error context canceled postgres-keycloak Error context canceled postgres-volunteer-management Error context canceled rabbitmq Error context canceled postgres-exporter-auth Error context canceled postgres-exporter-volunteer-management Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the earlier `compose pull` step reported: redis Error context canceled prometheus Error context canceled postgres-exporter-auth Error context canceled minio Error context canceled redis-exporter Error context canceled grafana Error context canceled mailpit Error context canceled seq Error context canceled jaeger Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- 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.
- 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".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GetPetsWithFilterSpecification.GetPetsWithFilterSpecification.ctor at 23.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with GetPetsWithFilterSpecification.GetPetsWithFilterSpecification.ctor (cyclomatic 23). — Refactoring it lifts Cyclomatic Complexity from 9.5 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was GetPetsWithFilterSpecification.GetPetsWithFilterSpecification.ctor at 29.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with GetPetsWithFilterSpecification.GetPetsWithFilterSpecification.ctor (cognitive 29). — Refactoring it lifts Cognitive Complexity from 9.2 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with PetAdoptionStateMachine.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
11 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with PetAdoptionStateMachine.cs, AdoptPetConsumer.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (30 lines × 2) finding(s) in Code Duplication — start with MassTransitOutboxExtensions.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (16–17 lines × 3) finding(s) in Code Duplication — start with AccountDbContextConfigurator.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
49 projects, 0 dependency cycle(s), 2 unstable depended-on project(s).
What to do
- Resolve the 2 Layer violation finding(s) in Coupling — start with Auth.Application.csproj, Notification.Application.csproj. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Off the main sequence finding(s) in Coupling — start with Auth.Core.csproj, Notification.Core.csproj. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Unstable project Notification.Infrastructure finding(s) in Coupling — start with Notification.Infrastructure.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 40 classes have LCOM4 above 3.
D9 · Test Distribution
149 test methods: 103 unit, 46 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 2 mock references across 149 tests.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).
D13 · REDACTED Scanning
6 secret(s) detected.
What to do
- Resolve the 6 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 71 direct `PackageReference`(s), and 179 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
33 deducted debt markers + unmeasured dead symbols across 18654 LoC in the .NET projects (1.6/KLoC) → score 6.8. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 33 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (33). — One of this dimension's main actionable groups (33 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
49 projects, 469 source files, 21941 hand-written lines of code (18654 production / 3287 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 4352 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 116 inter-project edges (build status unknown — did not finish). Measured across 2 solutions loaded as one workspace: `Solution/Solution.slnx`, `Solution/FileStorage/FileStorage.slnx`.
What to do
- Resolve the 1 Solution references a project that does not exist finding(s) in Solution Shape — start with FileStorage.slnx. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Shell project finding(s) in Solution Shape — start with Conversation.Contracts.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 47 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
0 naming inconsistencies among 16 declarations measured against a convention their peers follow.
D23 · Boundary Type-Coupling
No domain types are scored-flagged across 8 context boundaries; 1 contract project(s) carry advisory strong-ID notes. Contexts: Account, Auth, Conversation, FileStorage, Notification, Shared, Solution, VolunteerManagement.
D24 · Comment Value
0 of 43 judged comments only repeat the code they sit on (0.0 %). 5 comment(s) in another language or script were not judged.
D26 · Project Cohesion
0 of 49 projects flagged as possibly oversized/incoherent.
D27 · Navigability
92 % of calls cross a namespace and 4 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
D28 · Secrets (history)
5 finding(s): 0 critical, 5 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 3 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
17 finding(s): 0 critical, 3 high, 14 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 122 file(s) — `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserCreatedEvent.cs` (lines 8–14, line 14), `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserDeletedEvent.cs` (line 8), `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserRoleChangedEvent.cs` (line 8), `Shared/PetFamily.SharedKernel.Contracts/Events/FileStorage/FileDeleteRequestedEvent.cs` (line 8), `Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs` (lines 11–12, line 13), … (+117 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 121 of those file(s) — `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserCreatedEvent.cs`, `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserDeletedEvent.cs`, `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserRoleChangedEvent.cs`, `Shared/PetFamily.SharedKernel.Contracts/Events/FileStorage/FileDeleteRequestedEvent.cs`, `Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs`, … (+116 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 4 of those file(s) — `Solution/Auth/Auth.Infrastructure/Services/Keycloak/Exceptions/KeycloakAuthenticationException.cs`, `Solution/Auth/Auth.Infrastructure/Services/Keycloak/Exceptions/KeycloakException.cs`, `Solution/Auth/Auth.Infrastructure/Services/Keycloak/Exceptions/KeycloakUserNotFoundException.cs`, `Solution/Notification/Notification.Infrastructure/Services/Email/EmailService.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.
What to do
- Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D31 · IaC & Container Security
99 finding(s): 0 critical, 20 high, 68 medium, 11 low.
What to do
- Resolve the 68 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (31), REDACTED (22), REDACTED (15). — One of this dimension's main actionable groups (68 warning-level).
- Resolve the 20 High IaC finding(s) in IaC & Container Security — start with REDACTED (12), REDACTED (5), REDACTED (3). — One of this dimension's main actionable groups (20 issue-level).
- Resolve the 11 Low IaC finding(s) in IaC & Container Security — start with REDACTED (11). — One of this dimension's main actionable groups (11 recommendation-level).
D32 · Data Compliance (PII/GDPR)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 111 file(s) — `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserCreatedEvent.cs`, `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserDeletedEvent.cs`, `Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserRoleChangedEvent.cs`, `Shared/PetFamily.SharedKernel.Contracts/Events/FileStorage/FileDeleteRequestedEvent.cs`, `Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs`, … (+106 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
What to do
- Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 47 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
AX4 · Dependency direction
- `Auth.Application` is a Application project but references `Auth.Infrastructure`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — Solution/Auth/Auth.Application/Auth.Application.csproj:15
- This Application file depends on the Infrastructure project `Auth.Infrastructure`: it names `Auth.Infrastructure.Common`, `Auth.Infrastructure.Services`, `AuthDbContext`, `IKeycloakService`. The inward dependency rule is broken here. It is named again on lines 4, 17, 18. Depend on an abstraction the inner layer owns, implemented in the outer one. — Solution/Auth/Auth.Application/Services/AuthService.cs:3
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls
- Access here is not default-deny: `AccountController.GetByUserId` declares no authorization while 3 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:35
- Access here is not default-deny: `PetController.Search` declares no authorization while 4 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:51
- Access here is not default-deny: `ShelterController.GetAssignment` declares no authorization while 8 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:226
- Access here is not default-deny: `ShelterController.Get` declares no authorization while 8 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:246
- Access here is not default-deny: `ShelterController.GetWithPagination` declares no authorization while 8 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:265
- Access here is not default-deny: `VolunteerController.Get` declares no authorization while 14 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:153
- Access here is not default-deny: `VolunteerController.GetPets` declares no authorization while 14 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:171
- Access here is not default-deny: `VolunteerController.GetPetById` declares no authorization while 14 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:192
- Access here is not default-deny: `VolunteerController.GetVolunteersWithPagination` declares no authorization while 14 of its sibling actions do. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:214
What to do
- Put every endpoint behind the guard its siblings carry — [Authorize(Policy = …)] on the action or its controller, RequireAuthorization on the route or its group, or a fallback policy with explicit [AllowAnonymous] opt-outs — so the open surface is only what is public on purpose.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: 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
- `Volunteer` references the aggregate root `Pet` directly (via `_pets`) — hold its `PetId` instead. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Volunteer.cs:44
- `Volunteer` references the aggregate root `Pet` directly (via `Pets`) — hold its `PetId` instead. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Volunteer.cs:49
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
- `Pet` reads `DateTime.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:194
- `SoftDeletableEntity` reads `DateTime.UtcNow` inside `Delete`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — Shared/PetFamily.SharedKernel.Domain/Primitives/SoftDeletableEntity.cs:32
- `VolunteerAssignment` reads `DateTime.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Shelters/Entities/VolunteerAssignment.cs:72
What to do
- Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM2 · Strongly-typed ids
- `Account.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. — Solution/Account/Account.Domain/Aggregates/Account.cs:33
- `Chat.LinkedId` 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. — Solution/Conversation/Conversation.Domain/Aggregates/Chat.cs:51
- `Message.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. — Solution/Conversation/Conversation.Domain/Aggregates/Entities/Message.cs:50
- `VolunteerAssignment.VolunteerId` 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. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Shelters/Entities/VolunteerAssignment.cs:39
- `Volunteer.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. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Volunteer.cs:42
- `Pet.BreedId` 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. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:45
- `Pet.SpeciesId` 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. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:50
- `Pet.BookerId` 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. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:80
- `Pet.ShelterId` 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. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:85
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM3 · Integration-event coupling
DM4 · Rich vs anemic model
- `Account` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Solution/Account/Account.Domain/Aggregates/Account.cs:10
- `Message` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Solution/Conversation/Conversation.Domain/Aggregates/Entities/Message.cs:11
- `Breed` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/AnimalKinds/Entities/Breed.cs:10
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED3 · Event naming
- `NotificationEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — Solution/Notification/Notification.Contracts/Events/NotificationEvent.cs:8
- `ConfirmAdoption` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — Shared/PetFamily.SharedKernel.Contracts/Events/PetAdoption/ConfirmAdoption.cs:8
- `RejectAdoption` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — Shared/PetFamily.SharedKernel.Contracts/Events/PetAdoption/RejectAdoption.cs:8
- `StartPetAdoption` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — Shared/PetFamily.SharedKernel.Contracts/Events/PetAdoption/StartPetAdoption.cs:8
What to do
- Name events in the past tense — they record facts that already happened.
ED4 · Outbox / dual-write
- `NotificationEventConsumer.Consume` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — Solution/Notification/Hosts/Notification.Hosts.Consumers/Consumers/NotificationEventConsumer.cs:22
- `UserCreatedEventConsumer.Consume` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — Solution/Notification/Hosts/Notification.Hosts.Consumers/Consumers/UserCreatedEventConsumer.cs:20
- `AuthService.RegisterAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — Solution/Auth/Auth.Application/Services/AuthService.cs:24
- `DevDataSeeder.SeedAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — Solution/Auth/Auth.Infrastructure/Services/DevDataSeeder.cs:33
- `EmailService.SendAsync` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — Solution/Notification/Notification.Infrastructure/Services/Email/EmailService.cs:18
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a README to the 47 of 47 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
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
- Only 9/49 projects share a common root namespace — the code's module identity is inconsistent.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 77/78 types (99%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
What to do
- Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 670 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
P8 · Schema migrations
- This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema. (×6) — Solution/Account/Account.Infrastructure/AccountMigrator.cs:26, Solution/Conversation/Conversation.Infrastructure/ConversationMigrator.cs:26, Solution/Auth/Auth.Infrastructure/AuthMigrator.cs:26, …
What to do
- Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
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/31 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 cache.GetAsync(prefixedKey, ct)` 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) — Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:27, Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:90
- `await cache.SetAsync(prefixedKey, bytes, cacheOptions, ct)` 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)`. — Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:52
- `await cache.RemoveAsync(prefixedKey, ct)` 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)`. — Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:59
- `await GetAsync<T>(key, ct)` 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)`. (×3) — Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:69, Shared/PetFamily.SharedKernel.Infrastructure/Caching/MemoryCacheService.cs:73, Shared/PetFamily.SharedKernel.Infrastructure/Caching/MemoryCacheService.cs:109
- `await factory(ct)` 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) — Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:76, Shared/PetFamily.SharedKernel.Infrastructure/Caching/MemoryCacheService.cs:116
- `await SetAsync(key, value, ct, expiration)` 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) — Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:80, Shared/PetFamily.SharedKernel.Infrastructure/Caching/MemoryCacheService.cs:120
- `await task` 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)`. — Shared/PetFamily.SharedKernel.Infrastructure/Caching/MemoryCacheService.cs:87
- `await DbSet.AddAsync(entity, 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)`. — Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:40
- `await DbContext.SaveChangesAsync(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) — Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:41, Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:50, Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:78, …
- `await DbSet.AddRangeAsync(entities, 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)`. — Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:49
- `await DbSet.WithSpecification(specification) .FirstOrDefaultAsync(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)`. — Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:59
- `await DbSet.WithSpecification(specification) .ToListAsync(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)`. — Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:67
- `await action(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) — Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:25, Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:36
- `await strategy.ExecuteAsync(async () => { await using var transaction = await _dbCo...` 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)`. — Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:31
- `await using … = await _dbContext.Database.BeginTransactionAsync(isolationLevel, can...` 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)`. — Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:33
- `await _dbContext.Database.BeginTransactionAsync(isolationLevel, 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)`. — Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:33
- `await transaction.CommitAsync(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)`. — Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:37
- `await transaction.RollbackAsync(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)`. — Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:41
- `await httpContext.Response.WriteAsJsonAsync(problemDetails, ct)` 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)`. — Shared/PetFamily.SharedKernel.WebApi/Errors/GlobalExceptionHandler.cs:32
- `await factory.CreateConnectionAsync()` 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)`. — REDACTED:97
- `await context.Response.WriteAsync( System.Text.Json.JsonSerializer.Serialize( new {...` 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)`. — REDACTED:211
- `await base.SendAsync(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)`. — Shared/PetFamily.SharedKernel.WebApi/Handlers/AuthenticationDelegatingHandler.cs:24
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
- `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — Shared/PetFamily.SharedKernel.WebApi/Extensions/AuthenticationExtensions.cs:60
- `ValidateAudience = false` means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. — Shared/PetFamily.SharedKernel.WebApi/Extensions/AuthenticationExtensions.cs:65
- 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. (×7) — Solution/Account/Hosts/Account.Hosts.Endpoints/Program.cs:5, Solution/ApiGateway/ApiGateway/Program.cs:6, Solution/Auth/Hosts/Auth.Endpoints/Program.cs:6, …
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. (×7) — Solution/Account/Hosts/Account.Hosts.Endpoints/Program.cs:5, Solution/ApiGateway/ApiGateway/Program.cs:6, Solution/Auth/Hosts/Auth.Endpoints/Program.cs:6, …
What to do
- Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
- Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
- Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `cts` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 13). Every use of it in `CreateCancellationToken` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cts = …;`), which releases it at the end of the scope on every path including a throw. — Shared/PetFamily.SharedKernel.Tests/Abstractions/UnitTestBase.cs:13
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 217/219 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.
- Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`). — REDACTED:90
- No CancellationToken parameter — this work can't be stopped early once started. — Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Consumers/Consumers/UnreservePetConsumer.cs:60
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- ~0.4 `!` suppressions per 1k syntax nodes — 42 suppression(s) across the 95669 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 | 89% | Strong | Strongest area. |
| Architecture | 85% | Strong | Solid. |
| Maturity | 70% | Strong | Solid. |
| Readiness | 53% | Adequate — gated by D13, P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 41% | Weak — gated by D31, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 71% | Strong | Solid. |
| Event-Driven | 77% | Strong | Solid. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 34 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — postgres-conversation Error context canceled postgres-keycloak Error context canceled postgres-volunteer-management Error context canceled rabbitmq Error context canceled postgres-exporter-auth Error context canceled postgres-exporter-volunteer-management Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the earlier `compose pull` step reported: redis Error context canceled prometheus Error context canceled postgres-exporter-auth Error context canceled minio Error context canceled redis-exporter Error context canceled grafana Error context canceled mailpit Error context canceled seq Error context canceled jaeger Error context canceled Error response from daemon: Get "https://docker.elastic.co/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — too few commits for a meaningful bus factor
- D22 Internal API Consistency — N/A — too few peer members to establish a convention across 29 exposed C# types.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — analyzer environment
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
- ED5 Idempotency — not scored — 29 of 42 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 77 finding(s)
- AnalyzerSeverityNone .editorconfig:556
- AnalyzerSeverityNone .editorconfig:559
- AnalyzerSeverityNone .editorconfig:562
- AnalyzerSeverityNone .editorconfig:565
- AnalyzerSeverityNone .editorconfig:568
- AnalyzerSeverityNone .editorconfig:569
- AnalyzerSeverityNone .editorconfig:570
- AnalyzerSeverityNone .editorconfig:571
- AnalyzerSeverityNone .editorconfig:572
- AnalyzerSeverityNone .editorconfig:573
- AnalyzerSeverityNone .editorconfig:574
- AnalyzerSeverityNone .editorconfig:575
- AnalyzerSeverityNone .editorconfig:578
- AnalyzerSeverityNone .editorconfig:579
- AnalyzerSeverityNone .editorconfig:580
- AnalyzerSeverityNone .editorconfig:583
- AnalyzerSeverityNone .editorconfig:584
- AnalyzerSeverityNone .editorconfig:585
- AnalyzerSeverityNone .editorconfig:588
- AnalyzerSeverityNone .editorconfig:589
- AnalyzerSeverityNone .editorconfig:590
- AnalyzerSeverityNone .editorconfig:591
- AnalyzerSeverityNone .editorconfig:594
- AnalyzerSeverityNone .editorconfig:597
- AnalyzerSeverityNone .editorconfig:598
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dual write (no outbox): NotificationEventConsumer.Consume Solution/Notification/Hosts/Notification.Hosts.Consumers/Consumers/NotificationEventConsumer.cs:22
- Dual write (no outbox): UserCreatedEventConsumer.Consume Solution/Notification/Hosts/Notification.Hosts.Consumers/Consumers/UserCreatedEventConsumer.cs:20
- Dual write (no outbox): AuthService.RegisterAsync Solution/Auth/Auth.Application/Services/AuthService.cs:24
- Dual write (no outbox): DevDataSeeder.SeedAsync Solution/Auth/Auth.Infrastructure/Services/DevDataSeeder.cs:33
- Dual write (no outbox): EmailService.SendAsync Solution/Notification/Notification.Infrastructure/Services/Email/EmailService.cs:18
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Layer violation: Application → Infrastructure Solution/Auth/Auth.Application/Auth.Application.csproj:15
- Layer violation: Application → Infrastructure Solution/Notification/Notification.Application/Notification.Application.csproj:8
- Aggregate holds a reference to another aggregate: Volunteer._pets Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Volunteer.cs:44
- Aggregate holds a reference to another aggregate: Volunteer.Pets Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Volunteer.cs:49
- Dependency-rule violation: Auth.Application (Application) → Auth.Infrastructure (Infrastructure) Solution/Auth/Auth.Application/Auth.Application.csproj:15
- REDACTED
Serious — 153 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:27
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:52
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:59
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:69
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:76
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:80
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:90
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/MemoryCacheService.cs:73
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/MemoryCacheService.cs:87
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/MemoryCacheService.cs:109
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/MemoryCacheService.cs:116
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Caching/MemoryCacheService.cs:120
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:40
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:41
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:49
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:50
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:59
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:67
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:78
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/EntityFrameworkRepository.cs:88
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:25
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:31
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:33
- Awaits without ConfigureAwait(false) Shared/PetFamily.SharedKernel.Infrastructure/Transactions/TransactionalExecutor.cs:33
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Schema created with EnsureCreated() outside the migrations Solution/Account/Account.Infrastructure/AccountMigrator.cs:26
- Schema created with EnsureCreated() outside the migrations Solution/Conversation/Conversation.Infrastructure/ConversationMigrator.cs:26
- Schema created with EnsureCreated() outside the migrations Solution/Auth/Auth.Infrastructure/AuthMigrator.cs:26
- Schema created with EnsureCreated() outside the migrations Solution/Notification/Notification.Infrastructure/NotificationMigrator.cs:26
- Schema created with EnsureCreated() outside the migrations Shared/PetFamily.SharedKernel.Tests/Fixtures/CustomWebApplicationFactory.cs:42
- Schema created with EnsureCreated() outside the migrations Solution/VolunteerManagement/VolunteerManagement.Infrastructure/VolunteerManagementMigrator.cs:26
- REDACTED
- REDACTED
- REDACTED
- Domain type reads the wall clock: Pet Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:194
- Domain type reads the wall clock: SoftDeletableEntity Shared/PetFamily.SharedKernel.Domain/Primitives/SoftDeletableEntity.cs:32
- Domain type reads the wall clock: VolunteerAssignment Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Shelters/Entities/VolunteerAssignment.cs:72
- Anemic entity: Account Solution/Account/Account.Domain/Aggregates/Account.cs:10
- Anemic entity: Message Solution/Conversation/Conversation.Domain/Aggregates/Entities/Message.cs:11
- Anemic entity: Breed Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/AnimalKinds/Entities/Breed.cs:10
- Duplicated block (8 lines × 2) Solution/VolunteerManagement/Application/VolunteerManagement.Services/Sagas/PetAdoptionStateMachine.cs:188
- Duplicated block (8 lines × 2) Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Consumers/Consumers/AdoptPetConsumer.cs:25
- Off the main sequence: Auth.Core Solution/Auth/Auth.Core/Auth.Core.csproj:1
- Off the main sequence: Notification.Core Solution/Notification/Notification.Core/Notification.Core.csproj:1
- Dependency-rule violation: Auth.Application (Application) → Auth.Infrastructure (Infrastructure) Solution/Auth/Auth.Application/Services/AuthService.cs:3
- No data-protection/encryption
- GetPetsWithFilterSpecification.GetPetsWithFilterSpecification.ctor (cyclomatic 23) Solution/VolunteerManagement/Application/VolunteerManagement.Services/Volunteers/Pets/Specifications/GetPetsWithFilterSpecification.cs:32
- Solution references a project that does not exist Solution/FileStorage/FileStorage.slnx
- GetPetsWithFilterSpecification.GetPetsWithFilterSpecification.ctor (cognitive 29) Solution/VolunteerManagement/Application/VolunteerManagement.Services/Volunteers/Pets/Specifications/GetPetsWithFilterSpecification.cs:32
- MethodTooLong: PetAdoptionStateMachine.PetAdoptionStateMachine(…) Solution/VolunteerManagement/Application/VolunteerManagement.Services/Sagas/PetAdoptionStateMachine.cs:97
- REDACTED
- REDACTED
- Duplicated block (30 lines × 2) Shared/PetFamily.SharedKernel.WebApi/Extensions/MassTransitOutboxExtensions.cs:24
- Duplicated block (16–17 lines × 3) Solution/Account/Account.Infrastructure/Common/AccountDbContextConfigurator.cs:20
- Duplicated block (14 lines × 2) REDACTED:502
- Duplicated block (10 lines × 2) Shared/PetFamily.SharedKernel.WebApi/Extensions/LoggingExtensions.cs:29
- Duplicated block (5 lines × 2) Solution/Account/Account.Infrastructure/Common/Configurations/AccountConfiguration.cs:46
- Duplicated block (9 lines × 2) Solution/VolunteerManagement/Application/VolunteerManagement.Handlers/Shelters/Queries/GetSheltersWithPagination/GetSheltersWithPaginationHandler.cs:23
- Duplicated block (6 lines × 2) Solution/VolunteerManagement/Application/VolunteerManagement.Services/Volunteers/Pets/PetService.cs:50
- Duplicated block (43 lines × 2) Solution/Account/Hosts/Account.Hosts.Endpoints/DependencyInjection.cs:21
- Duplicated block (16 lines × 2) Shared/PetFamily.SharedKernel.Infrastructure/Caching/DistributedCacheService.cs:69
- Unstable project Notification.Infrastructure Solution/Notification/Notification.Infrastructure/Notification.Infrastructure.csproj:1
- Unstable project VolunteerManagement.Services Solution/VolunteerManagement/Application/VolunteerManagement.Services/VolunteerManagement.Services.csproj:1
- Token validation disabled Shared/PetFamily.SharedKernel.WebApi/Extensions/AuthenticationExtensions.cs:65
- Disposable created and abandoned in the method that made it Shared/PetFamily.SharedKernel.Tests/Abstractions/UnitTestBase.cs:13
- Async delegate without CancellationToken: AddRabbitMqHealthCheck REDACTED:90
- Async method without CancellationToken: PublishUnreserved Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Consumers/Consumers/UnreservePetConsumer.cs:60
Minor — 72 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Endpoints outside the guard REDACTED:35
- Endpoints outside the guard REDACTED:51
- Endpoints outside the guard REDACTED:226
- Endpoints outside the guard REDACTED:246
- Endpoints outside the guard REDACTED:265
- Endpoints outside the guard REDACTED:153
- Endpoints outside the guard REDACTED:171
- Endpoints outside the guard REDACTED:192
- Endpoints outside the guard REDACTED:214
- Primitive id on a domain type: Account.UserId Solution/Account/Account.Domain/Aggregates/Account.cs:33
- Primitive id on a domain type: Chat.LinkedId Solution/Conversation/Conversation.Domain/Aggregates/Chat.cs:51
- Primitive id on a domain type: Message.UserId Solution/Conversation/Conversation.Domain/Aggregates/Entities/Message.cs:50
- Primitive id on a domain type: VolunteerAssignment.VolunteerId Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Shelters/Entities/VolunteerAssignment.cs:39
- Primitive id on a domain type: Volunteer.UserId Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Volunteer.cs:42
- Primitive id on a domain type: Pet.BreedId Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:45
- Primitive id on a domain type: Pet.SpeciesId Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:50
- Primitive id on a domain type: Pet.BookerId Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:80
- Primitive id on a domain type: Pet.ShelterId Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:85
- No security response headers detected
- No security response headers detected Solution/Account/Hosts/Account.Hosts.Endpoints/Program.cs:5
- No security response headers detected Solution/ApiGateway/ApiGateway/Program.cs:6
- No security response headers detected Solution/Auth/Hosts/Auth.Endpoints/Program.cs:6
- No security response headers detected Solution/Conversation/Hosts/Conversation.Hosts.Endpoints/Program.cs:5
- No security response headers detected Solution/FileStorage/Hosts/FileStorage.Endpoints/Program.cs:6
- No security response headers detected Solution/Notification/Hosts/Notification.Hosts.Endpoints/Program.cs:5
- No security response headers detected Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Endpoints/Program.cs:5
- No app-layer HTTPS enforcement detected
- No app-layer HTTPS enforcement detected Solution/Account/Hosts/Account.Hosts.Endpoints/Program.cs:5
- No app-layer HTTPS enforcement detected Solution/ApiGateway/ApiGateway/Program.cs:6
- No app-layer HTTPS enforcement detected Solution/Auth/Hosts/Auth.Endpoints/Program.cs:6
- No app-layer HTTPS enforcement detected Solution/Conversation/Hosts/Conversation.Hosts.Endpoints/Program.cs:5
- No app-layer HTTPS enforcement detected Solution/FileStorage/Hosts/FileStorage.Endpoints/Program.cs:6
- No app-layer HTTPS enforcement detected Solution/Notification/Hosts/Notification.Hosts.Endpoints/Program.cs:5
- No app-layer HTTPS enforcement detected Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Endpoints/Program.cs:5
- Silent fallback default on configuration miss Solution/FileStorage/FileStorage.Contracts/Extensions/ServiceCollectionExtensions.cs:32
- Silent fallback default on configuration miss REDACTED:33
- Silent fallback default on configuration miss Shared/PetFamily.SharedKernel.WebApi/Extensions/LoggingExtensions.cs:43
- Silent fallback default on configuration miss REDACTED:92
- Silent fallback default on configuration miss Shared/PetFamily.SharedKernel.WebApi/Extensions/MassTransitOutboxExtensions.cs:42
- Silent fallback default on configuration miss Shared/PetFamily.SharedKernel.WebApi/Extensions/MassTransitOutboxExtensions.cs:72
- Silent fallback default on configuration miss Shared/PetFamily.SharedKernel.WebApi/Extensions/MassTransitOutboxExtensions.cs:110
- Silent fallback default on configuration miss Shared/PetFamily.SharedKernel.WebApi/Extensions/OpenTelemetryExtensions.cs:30
- Event not named in past tense: NotificationEvent Solution/Notification/Notification.Contracts/Events/NotificationEvent.cs:8
- Event not named in past tense: ConfirmAdoption Shared/PetFamily.SharedKernel.Contracts/Events/PetAdoption/ConfirmAdoption.cs:8
- Event not named in past tense: RejectAdoption Shared/PetFamily.SharedKernel.Contracts/Events/PetAdoption/RejectAdoption.cs:8
- Event not named in past tense: StartPetAdoption Shared/PetFamily.SharedKernel.Contracts/Events/PetAdoption/StartPetAdoption.cs:8
- Duplicated predicate Shared/PetFamily.SharedKernel.Domain/Primitives/Entity.cs:24
- Duplicated predicate Solution/Account/Account.Domain/Aggregates/ValueObjects/Properties/Description.cs:42
- Partial data-retention evidence
- Shell project: Conversation.Contracts Solution/Conversation/Conversation.Contracts/Conversation.Contracts.csproj
- No ADRs found
- REDACTED
- No ADRs
- No src/ separation
- Inconsistent root namespaces
- Large public API surface
- No SAST REDACTED:6
- No performance benchmarks
- OIDC metadata fetched over HTTP Shared/PetFamily.SharedKernel.WebApi/Extensions/AuthenticationExtensions.cs:60
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 11 finding(s)
- doc comments repeat the names Solution/Auth/Auth.Application/Services/IAuthService.cs:41
- doc comments repeat the names Solution/Auth/Auth.Infrastructure/Services/Keycloak/IKeycloakAuthorizationClient.cs:22
- doc comments repeat the names Solution/Notification/Notification.Infrastructure/BackgroundJobs/NotificationLogCleanupService.cs:46
- doc comments repeat the names Shared/PetFamily.SharedKernel.WebApi/Extensions/OpenTelemetryExtensions.cs:112
- doc comments repeat the names Solution/VolunteerManagement/VolunteerManagement.Infrastructure/Common/Contexts/VolunteerManagementDbContextFactory.cs:15
- Off the main sequence: PetFamily.SharedKernel.Application Shared/PetFamily.SharedKernel.Application/PetFamily.SharedKernel.Application.csproj:1
- Off the main sequence: PetFamily.SharedKernel.WebApi Shared/PetFamily.SharedKernel.WebApi/PetFamily.SharedKernel.WebApi.csproj:1
- Off the main sequence: PetFamily.SharedKernel.Contracts Shared/PetFamily.SharedKernel.Contracts/PetFamily.SharedKernel.Contracts.csproj:1
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- VolunteerManagement: 3 contract type(s) expose producer-owned ids/enums
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-d9960ab8e69b43dd813480b603d91404/history.json --exit-code 0 --source . | 5 | 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-d9960ab8e69b43dd813480b603d91404/tree.json --exit-code 0 --source . | 3 | 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 Solution/Account/Account.Infrastructure/Migrations --exclude Solution/Auth/Auth.Infrastructure/Migrations --exclude Solution/Conversation/Conversation.Infrastructure/Migrations --exclude Solution/Notification/Notification.Infrastructure/Migrations --exclude Solution/VolunteerManagement/VolunteerManagement.Infrastructure/Migrations . | 17 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 99 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude Solution/Account/Account.Infrastructure/Migrations --exclude Solution/Auth/Auth.Infrastructure/Migrations --exclude Solution/Conversation/Conversation.Infrastructure/Migrations --exclude Solution/Notification/Notification.Infrastructure/Migrations --exclude Solution/VolunteerManagement/VolunteerManagement.Infrastructure/Migrations . | 1 | artifacts/raw/semgrep-gdpr.json |
| 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-ecc32b9c82244454b2014492243ae4b5 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 20 field(s)
- UserCreatedEvent.FirstName Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserCreatedEvent.cs:29
- UserCreatedEvent.LastName Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserCreatedEvent.cs:34
- UserDto.FirstName Solution/Auth/Auth.Contracts/Dtos/UserDto.cs:17
- UserDto.LastName Solution/Auth/Auth.Contracts/Dtos/UserDto.cs:18
- User.FirstName Solution/Auth/Auth.Core/Models/User.cs:21
- User.LastName Solution/Auth/Auth.Core/Models/User.cs:26
- SeedUser.FirstName Solution/Auth/Auth.Infrastructure/Services/DevDataSeeder.cs:20
- SeedUser.LastName Solution/Auth/Auth.Infrastructure/Services/DevDataSeeder.cs:20
- CreateUserRequest.FirstName Solution/Auth/Auth.Infrastructure/Services/Keycloak/Models/CreateUserRequest.cs:16
- CreateUserRequest.LastName Solution/Auth/Auth.Infrastructure/Services/Keycloak/Models/CreateUserRequest.cs:17
- KeycloakUserRepresentation.FirstName Solution/Auth/Auth.Infrastructure/Services/Keycloak/Models/KeycloakUserRepresentation.cs:26
- KeycloakUserRepresentation.LastName Solution/Auth/Auth.Infrastructure/Services/Keycloak/Models/KeycloakUserRepresentation.cs:31
- UserRegisterRequest.FirstName Solution/Auth/Hosts/Auth.Endpoints/Requests/UserRegisterRequest.cs:14
- UserRegisterRequest.LastName Solution/Auth/Hosts/Auth.Endpoints/Requests/UserRegisterRequest.cs:15
- AddVolunteerCommand.Surname Solution/VolunteerManagement/Application/VolunteerManagement.Handlers/Volunteers/Commands/Add/AddVolunteerCommand.cs:18
- FullNameDto.Surname Solution/VolunteerManagement/Application/VolunteerManagement.Services/Volunteers/Dtos/FullNameDto.cs:9
- VolunteerDto.FullName Solution/VolunteerManagement/Application/VolunteerManagement.Services/Volunteers/Dtos/VolunteerDto.cs:11
- AddVolunteerRequest.FullName Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Endpoints/Requests/AddVolunteerRequest.cs:9
- FullName.Surname Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/ValueObjects/Properties/FullName.cs:20
- Volunteer.FullName Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Volunteer.cs:37
Email — 16 field(s)
- UserCreatedEvent.Email Shared/PetFamily.SharedKernel.Contracts/Events/Auth/UserCreatedEvent.cs:24
- HttpContextCurrentUser.Email Shared/PetFamily.SharedKernel.WebApi/Services/HttpContextCurrentUser.cs:39
- ICurrentUser.Email Shared/PetFamily.SharedKernel.WebApi/Services/ICurrentUser.cs:25
- UserDto.Email Solution/Auth/Auth.Contracts/Dtos/UserDto.cs:16
- User.Email Solution/Auth/Auth.Core/Models/User.cs:16
- SeedUser.Email Solution/Auth/Auth.Infrastructure/Services/DevDataSeeder.cs:20
- CreateUserRequest.Email Solution/Auth/Auth.Infrastructure/Services/Keycloak/Models/CreateUserRequest.cs:14
- KeycloakUserRepresentation.Email Solution/Auth/Auth.Infrastructure/Services/Keycloak/Models/KeycloakUserRepresentation.cs:21
- UserLoginRequest.Email Solution/Auth/Hosts/Auth.Endpoints/Requests/UserLoginRequest.cs:8
- UserRegisterRequest.Email Solution/Auth/Hosts/Auth.Endpoints/Requests/UserRegisterRequest.cs:12
- EmailSettingsDto.Email Solution/Notification/Notification.Application/Dtos/EmailSettingsDto.cs:9
- UserNotificationSettingsDto.EmailSettings Solution/Notification/Notification.Application/Dtos/UserNotificationSettingsDto.cs:18
- EmailSettings.Email Solution/Notification/Notification.Core/Models/EmailSettings.cs:21
- UserNotificationSettings.EmailSettings Solution/Notification/Notification.Core/Models/UserNotificationSettings.cs:36
- NotificationDbContext.EmailSettings Solution/Notification/Notification.Infrastructure/Common/NotificationDbContext.cs:20
- SmtpOptions.SenderEmail Solution/Notification/Notification.Infrastructure/Settings/SmtpOptions.cs:41
Phone — 12 field(s)
- Account.PhoneNumber Solution/Account/Account.Domain/Aggregates/Account.cs:43
- UpdateProfileCommand.PhoneNumber Solution/Account/Application/Account.Handlers/Commands/UpdateProfile/UpdateProfileCommand.cs:18
- AccountDto.PhoneNumber Solution/Account/Application/Account.Services/Dtos/AccountDto.cs:15
- UpdateProfileRequest.PhoneNumber Solution/Account/Hosts/Account.Hosts.Endpoints/Requests/UpdateProfileRequest.cs:10
- AddShelterCommand.PhoneNumber Solution/VolunteerManagement/Application/VolunteerManagement.Handlers/Shelters/Commands/Add/AddShelterCommand.cs:38
- UpdateShelterCommand.PhoneNumber Solution/VolunteerManagement/Application/VolunteerManagement.Handlers/Shelters/Commands/Update/UpdateShelterCommand.cs:23
- AddPetCommand.PhoneNumber Solution/VolunteerManagement/Application/VolunteerManagement.Handlers/Volunteers/Pets/Commands/Add/AddPetCommand.cs:59
- ShelterDto.PhoneNumber Solution/VolunteerManagement/Application/VolunteerManagement.Services/Shelters/Dtos/ShelterDto.cs:26
- AddPetRequest.PhoneNumber Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Endpoints/Requests/AddPetRequest.cs:31
- AddShelterRequest.PhoneNumber Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Endpoints/Requests/AddShelterRequest.cs:22
- UpdateShelterRequest.PhoneNumber Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Endpoints/Requests/UpdateShelterRequest.cs:14
- Shelter.PhoneNumber Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Shelters/Shelter.cs:58
Address — 7 field(s)
- AddShelterCommand.ZipCode Solution/VolunteerManagement/Application/VolunteerManagement.Handlers/Shelters/Commands/Add/AddShelterCommand.cs:33
- UpdateShelterAddressCommand.ZipCode Solution/VolunteerManagement/Application/VolunteerManagement.Handlers/Shelters/Commands/UpdateAddress/UpdateShelterAddressCommand.cs:33
- ShelterDto.ZipCode Solution/VolunteerManagement/Application/VolunteerManagement.Services/Shelters/Dtos/ShelterDto.cs:25
- AddressDto.ZipCode Solution/VolunteerManagement/Application/VolunteerManagement.Services/Volunteers/Dtos/AddressDto.cs:10
- AddShelterRequest.ZipCode Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Endpoints/Requests/AddShelterRequest.cs:21
- UpdateShelterAddressRequest.ZipCode Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Endpoints/Requests/UpdateShelterAddressRequest.cs:14
- Address.ZipCode Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/ValueObjects/Properties/Address.cs:29
Date of birth — 6 field(s)
- AddPetCommand.BirthDate Solution/VolunteerManagement/Application/VolunteerManagement.Handlers/Volunteers/Pets/Commands/Add/AddPetCommand.cs:64
- SearchPetsQuery.BirthDateFrom Solution/VolunteerManagement/Application/VolunteerManagement.Handlers/Volunteers/Pets/Queries/SearchPets/SearchPetsQuery.cs:31
- SearchPetsQuery.BirthDateTo Solution/VolunteerManagement/Application/VolunteerManagement.Handlers/Volunteers/Pets/Queries/SearchPets/SearchPetsQuery.cs:32
- PetDto.BirthDate Solution/VolunteerManagement/Application/VolunteerManagement.Services/Volunteers/Dtos/PetDto.cs:34
- AddPetRequest.BirthDate Solution/VolunteerManagement/Hosts/VolunteerManagement.Hosts.Endpoints/Requests/AddPetRequest.cs:32
- Pet.BirthDate Solution/VolunteerManagement/VolunteerManagement.Domain/Aggregates/Volunteers/Entities/Pet.cs:60