Executive summary
kamilbaczek/Modular-monolith-by-example is rated At risk because critical security findings are open. Its score is held back in part because two passwords or keys sit in the current code. It scores 45 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 34, is the weakest lens and counts most in the score. The best first steps are replacing the two exposed passwords or keys and switching the old ones off and updating the outdated dependencies, each worth about 9 points. Raising Production Readiness to 62 would lift the score to about 53.
Thirty-five passwords or keys in the code's history and two in the code are open to anyone who can read the repository. Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Replacing each exposed password or key and pinning each tool to an exact version would close both risks. Updating the vulnerable packages would fix the 18 packages with a known security hole, and limiting each secret to its own step would deal with the 12 secrets exposed to more of the pipeline than needed. The 40 pieces of business logic tied to the database or web code need separating from the database and web code.
The product code is 13,653 lines, about €22,000 to rebuild.
If Production Readiness rose from 34 to 62, the lowest score rated Strong, the score would rise from 45 to about 53.
New since the last survey: 93 findings
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/SharedInfrastructureModule.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/SharedInfrastructureModule.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/HealthChecks/HealthChecksSharedModule.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/HealthChecks/HealthChecksSharedModule.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/EventBus/EventBusModule.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/EventBus/EventBusModule.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Data/SqlConnectionFactory.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Data/SqlConnectionFactory.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/BackgroundJobScheduler.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/BackgroundJobScheduler.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Extensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Extensions.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Storage/BackgroundJobsStorageExtensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Storage/BackgroundJobsStorageExtensions.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Dashboard/DashboardAuthorizationFilter.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Dashboard/DashboardAuthorizationFilter.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Configuration/BackgroundProcessingConfiguration.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Configuration/BackgroundProcessingConfiguration.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/WebSockets/WebSocketsExtensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/WebSockets/WebSocketsExtensions.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/WebSockets/Configurations/WebSocketsConfiguration.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/WebSockets/Configurations/WebSocketsConfiguration.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Swagger/SwaggerAuthorizationExtensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Swagger/SwaggerAuthorizationExtensions.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Swagger/SwaggerModule.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Swagger/SwaggerModule.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Errors/ErrorTypes.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Errors/ErrorTypes.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Errors/Middleware/ErrorHandling.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Errors/Middleware/ErrorHandling.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Environments/EnvironmentExtensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Environments/EnvironmentExtensions.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Cors/CorsExtensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Cors/CorsExtensions.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Cors/Configurations/CorsConfiguration.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Cors/Configurations/CorsConfiguration.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Controllers/InternalControllersFeatureProvider.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Controllers/InternalControllersFeatureProvider.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/BusinessRuleValidationException.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/BusinessRuleValidationException.cs
- Code Coverage · Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/ValueObject.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/ValueObject.cs
- Code Coverage · Low coverage: Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/UserAccess/CurrentUserService.cs Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/UserAccess/CurrentUserService.cs
- Code Coverage · Low coverage: Src/Modules/Push/Divstack.Company.Estimation.Tool.Push/PushModule.cs Src/Modules/Push/Divstack.Company.Estimation.Tool.Push/PushModule.cs
- Code Coverage · Low coverage: Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Events/PriorityArchivedDomainEvent.cs Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Events/PriorityArchivedDomainEvent.cs
- Code Coverage · Low coverage: Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Events/PriorityForcedDomainEvent.cs Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Events/PriorityForcedDomainEvent.cs
- Code Coverage · Low coverage: Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Events/Publish/IntegrationEventPublisher.cs Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Events/Publish/IntegrationEventPublisher.cs
- Code Coverage · Low coverage: Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Events/Publish/Mapper/EventMapper.cs Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Events/Publish/Mapper/EventMapper.cs
- Code Coverage · Low coverage: Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/Priorities/Commands/Archive/ArchivePriorityCommandCommandHandler.cs Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/Priorities/Commands/Archive/ArchivePriorityCommandCommandHandler.cs
- Code Coverage · Low coverage: Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetClient/GetInquiryClientQueryHandler.cs Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetClient/GetInquiryClientQueryHandler.cs
- Code Coverage · Low coverage: Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetAll/GetAllInquiriesQueryHandler.cs Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetAll/GetAllInquiriesQueryHandler.cs
- Code Coverage · Low coverage: Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetAll/InquiryListItemDto.cs Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetAll/InquiryListItemDto.cs
- Code Coverage · Low coverage: Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/Get/GetInquiriesQueryHandler.cs Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/Get/GetInquiriesQueryHandler.cs
- Code Coverage · Low coverage: Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/Get/Dtos/InquiryInformationDto.cs Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/Get/Dtos/InquiryInformationDto.cs
- Code Coverage · Low coverage: Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommandHandler.cs Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommandHandler.cs
- Code Coverage · Low coverage: Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommandValidator.cs Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommandValidator.cs
- Code Coverage · Low coverage: Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/Mappers/ServiceDtoToServiceMapper.cs Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/Mappers/ServiceDtoToServiceMapper.cs
- Code Coverage · Low coverage: Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Common/Extensions/QueriesExtensions.cs Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Common/Extensions/QueriesExtensions.cs
- Code Coverage · Low coverage: REDACTED REDACTED
- Code Coverage · Low coverage: Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails/EmailsModule.cs Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails/EmailsModule.cs
- Code Coverage · Low coverage: Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Common/Configurations/ConfigurationLoader.cs Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Common/Configurations/ConfigurationLoader.cs
- Code Coverage · CRAP 56: InternalControllersFeatureProvider.IsController Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Controllers/InternalControllersFeatureProvider.cs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Deployment/Infrastructure/Divstack.Estimation.Tool.Deployment.Infrastructure.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Core/Divstack.Company.Estimation.Tool.Emails.Core.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/Divstack.Company.Estimation.Tool.Emails.Payments.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Priorities/Divstack.Company.Estimation.Tool.Emails.Priorities.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Users/Divstack.Company.Estimation.Tool.Emails.Users.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Divstack.Company.Estimation.Tool.Emails.Valuations.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails/Divstack.Company.Estimation.Tool.Emails.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Divstack.Company.Estimation.Tool.Inquiries.Domain.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.IntegrationsEvents/Divstack.Company.Estimation.Tool.Inquiries.IntegrationsEvents.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Inquiries/Tests/Divstack.Company.Estimation.Tool.Inquiries.IntegrationTests/Divstack.Company.Estimation.Tool.Inquiries.IntegrationTests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Api/Divstack.Company.Estimation.Tool.Payments.Api.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Application/Divstack.Company.Estimation.Tool.Payments.Application.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Domain/Divstack.Company.Estimation.Tool.Payments.Domain.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Infrastructure/Divstack.Company.Estimation.Tool.Payments.Infrastructure.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.IntegrationsEvents/Divstack.Company.Estimation.Tool.Payments.IntegrationsEvents.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Divstack.Company.Estimation.Tool.Payments.Persistance.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Api/Divstack.Company.Estimation.Tool.Priorities.Api.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Divstack.Company.Estimation.Tool.Priorities.Domain.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Divstack.Company.Estimation.Tool.Priorities.Infrastructure.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.IntegrationsEvents/Divstack.Company.Estimation.Tool.Priorities.IntegrationsEvents.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Divstack.Company.Estimation.Tool.Priorities.Persistance.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.DataAccess/Divstack.Company.Estimation.Tool.Push.DataAccess.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Payments/Divstack.Company.Estimation.Tool.Push.Payments.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Valuations/Divstack.Company.Estimation.Tool.Push.Valuations.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Push/Divstack.Company.Estimation.Tool.Push/Divstack.Company.Estimation.Tool.Push.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Reminders/Divstack.Company.Estimation.Tool.Reminders.Priorities/Divstack.Company.Estimation.Tool.Reminders.Priorities.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Reminders/Divstack.Company.Estimation.Tool.Reminders/Divstack.Company.Estimation.Tool.Reminders.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Divstack.Company.Estimation.Tool.Services.Api.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/Divstack.Company.Estimation.Tool.Services.Core.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.DataAccess/Divstack.Company.Estimation.Tool.Services.DataAccess.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Core/Divstack.Company.Estimation.Tool.Sms.Core.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Payments/Divstack.Company.Estimation.Tool.Sms.Payments.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Valuations/Divstack.Company.Estimation.Tool.Sms.Valuations.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms/Divstack.Company.Estimation.Tool.Sms.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Divstack.Company.Estimation.Tool.Users.Domain.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Divstack.Company.Estimation.Tool.Valuations.Application.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure.Signalr/Divstack.Company.Estimation.Tool.Shared.Infrastructure.Signalr.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Shared/Divstack.Company.Estimation.Tool.Shared.IntegrationTesting/Divstack.Company.Estimation.Tool.Shared.IntegrationTesting.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Shared/Testing/Divstack.Comapany.Estimation.Tool.Shared.Testing.Application.IntegrationsTests/Divstack.Comapany.Estimation.Tool.Shared.Testing.Application.IntegrationsTests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Shared/Testing/Divstack.Company.Estimation.Tool.Shared.IntegrationsTest.Persistance/Divstack.Company.Estimation.Tool.Shared.IntegrationsTest.Persistance.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Shared/Testing/Divstack.Company.Estimation.Tool.Shared.Testing.Application.IntegrationTests/Divstack.Company.Estimation.Tool.Shared.Testing.Application.IntegrationTests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Src/Shared/Testing/Divstack.Company.Estimation.Tool.Shared.Testing.IntegrationTests/Divstack.Company.Estimation.Tool.Shared.Testing.IntegrationTests.csproj
- Stateful singletons · Process-global static state: SystemTime Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/SystemTime.cs
- Test isolation · Production project references a test package: Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks → FluentAssertions REDACTED
Fixed since the last survey: 91 findings
- Dependency Hygiene · Vulnerable: IdentityServer4
- Dependency Hygiene · Vulnerable: MailKit
- Dependency Hygiene · Vulnerable: MimeKit
- Dependency Hygiene · Vulnerable: Marten
- Dependency Hygiene · Vulnerable: Microsoft.Data.SqlClient
- Dependency Hygiene · Vulnerable: Azure.Identity
- Boundary Type-Coupling · Cross-context type InquiryMadeEvent (Inquiries → Valuations) Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Valuations/Commands/Request/RequestValuationEventHandler.cs
- Boundary Type-Coupling · Cross-context type InquiryMadeEvent (Inquiries → Valuations) Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Valuations/Commands/Request/RequestValuationEventHandler.cs
- Static Analysis (SAST) · Medium: watchdog-eol-dotnet-runtime-in-workflow REDACTED
- Static Analysis (SAST) · Medium: watchdog-eol-dotnet-runtime-in-workflow REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net7.0 Deployment/Infrastructure/Divstack.Estimation.Tool.Deployment.Infrastructure.csproj
- Cancellation propagation · Async method without CancellationToken: SignOutAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/SignInManagementService.cs
- Cancellation propagation · Async method without CancellationToken: SendResetPasswordMail Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/SignInManagementService.cs
- Cancellation propagation · Async method without CancellationToken: UpdateAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: UserExists Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: AssignUserToRoleAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: AssignUserToRolesAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: UpdateAssignedRolesAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: GetUserDetailsAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: GetUserDetailsByPublicIdAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: GetUserDetailsByUsernameAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: GetAllUsersAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: GetUserRolesAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: GetUserRolesAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: GetAllCustomerUsersAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: GetAllUserDetails Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteCommandAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/UserModule.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteCommandAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/UserModule.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteQueryAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/UserModule.cs
- Cancellation propagation · Async method without CancellationToken: AddAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/UserRepository.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteCommandAsync Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Infrastructure/ValuationsModule.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteCommandAsync Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Infrastructure/ValuationsModule.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteQueryAsync Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Infrastructure/ValuationsModule.cs
- Cancellation propagation · Async method without CancellationToken: SendResponse Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Errors/Middleware/ErrorHandling.cs
- Cancellation propagation · Async method without CancellationToken: FindCompany Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ClientCompanyFinder.cs
- Cancellation propagation · Async method without CancellationToken: Make REDACTED
- Cancellation propagation · Async method without CancellationToken: Get REDACTED
- Cancellation propagation · Async method without CancellationToken: GetAll REDACTED
- Cancellation propagation · Async method without CancellationToken: MakeAsync Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Inquiry.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteCommandAsync Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure/InquiriesModule.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteQueryAsync Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure/InquiriesModule.cs
- Cancellation propagation · Async method without CancellationToken: InitializeAsync Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Domain/Payments/Payment.cs
- Cancellation propagation · Async method without CancellationToken: PayCard Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Domain/Payments/Payment.cs
- Cancellation propagation · Async method without CancellationToken: Pay REDACTED
- Cancellation propagation · Async method without CancellationToken: ExecuteCommandAsync Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Infrastructure/PaymentsModule.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteQueryAsync Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Infrastructure/PaymentsModule.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteCommandAsync Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Infrastructure/PaymentsModule.cs
- Cancellation propagation · Async method without CancellationToken: GetClientInfo Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/PaymentCompletedEventHandler.cs
- Cancellation propagation · Async method without CancellationToken: GetClientInfo Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/PaymentInitializedEventHandler.cs
- Cancellation propagation · Async method without CancellationToken: GetCompanySizeAsync Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/Priorities/Commands/Define/DefinePrioritiesEventHandler.cs
- Cancellation propagation · Async method without CancellationToken: GetCompanySizeAsync Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/Priorities/Commands/Redefine/RedefinePriorityCommandCommandHandler.cs
- Cancellation propagation · Async method without CancellationToken: RedefineAllAsync Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Domain/Services/PrioritiesRedefiner.cs
- Cancellation propagation · Async method without CancellationToken: RedefinePriorityAsync Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Domain/Services/PrioritiesRedefiner.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteCommandAsync Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/PrioritiesModule.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteCommandAsync Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/PrioritiesModule.cs
- Cancellation propagation · Async method without CancellationToken: ExecuteQueryAsync Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/PrioritiesModule.cs
- Cancellation propagation · Async method drops its CancellationToken: PublishAsync Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure/Events/Publish/IntegrationEventPublisher.cs
- Cancellation propagation · Async method drops its CancellationToken: PublishAsync Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Infrastructure/Events/Publish/IntegrationEventPublisher.cs
- Cancellation propagation · Async method drops its CancellationToken: PublishAsync Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Events/Publish/IntegrationEventPublisher.cs
- Slice cohesion · Cross-slice coupling: Divstack.Company.Estimation.Tool.Sms → Divstack.Company.Estimation.Tool.Valuations Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Valuations/Notifications/Proposals/ProposalSuggested/ProposalSuggestedSmsNotificationHandler.cs
- Slice cohesion · Cross-slice coupling: Divstack.Company.Estimation.Tool.Sms → Divstack.Company.Estimation.Tool.Inquiries Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Valuations/Notifications/Proposals/ProposalSuggested/ProposalSuggestedSmsNotificationHandler.cs
- Slice cohesion · Cross-slice coupling: Divstack.Company.Estimation.Tool.Valuations → Divstack.Company.Estimation.Tool.Inquiries Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Valuations/Commands/Request/RequestValuationEventHandler.cs
- Rich vs anemic model · Anemic entity: Inquiry Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Inquiry.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: GetAllValuationsQueryHandler Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/GetAll/GetAllValuationsQueryHandler.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: GetAllValuationsQueryHandler Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/GetAll/GetAllValuationsQueryHandler.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ValuationListItemAggregation Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/GetAll/ValuationListItemAggregation.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: GetValuationHistoryByIdQueryHandler Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/GetHistory/GetValuationHistoryByIdQueryHandler.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: GetValuationHistoryByIdQueryHandler Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/GetHistory/GetValuationHistoryByIdQueryHandler.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: HistoryAggregation Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/GetHistory/HistoryAggregation.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: GetValuationProposalsByIdQueryHandler Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/GetProposals/GetValuationProposalsByIdQueryHandler.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: GetValuationProposalsByIdQueryHandler Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/GetProposals/GetValuationProposalsByIdQueryHandler.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ProposalsAggregation Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/GetProposals/ProposalsAggregation.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ProjectionsModule Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Projections/ProjectionsModule.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ProjectionsModule Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Projections/ProjectionsModule.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ProjectionsModule Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Projections/ProjectionsModule.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ProjectionsModule Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Projections/ProjectionsModule.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ProjectionsModule Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Projections/ProjectionsModule.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ProjectionsModule Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Projections/ProjectionsModule.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ValuationsRepository Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Repositories/ValuationsRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: ValuationsRepository Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Repositories/ValuationsRepository.cs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: Divstack.Company.Estimation.Tool.Users.Domain Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Divstack.Company.Estimation.Tool.Users.Domain.csproj
- Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: PaymentsRepository Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Repositories/PaymentsRepository.cs
- Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: PrioritiesRepository Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Repositories/PrioritiesRepository.cs
- Immutable events · Mutable event: ProposalApproved Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.IntegrationsEvents/ExternalEvents/ProposalApproved.cs
- Immutable events · Mutable event: ProposalCancelled Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.IntegrationsEvents/ExternalEvents/ProposalCancelled.cs
- Immutable events · Mutable event: ProposalRejected Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.IntegrationsEvents/ExternalEvents/ProposalRejected.cs
- Immutable events · Mutable event: ProposalSuggested Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.IntegrationsEvents/ExternalEvents/ProposalSuggested.cs
- Immutable events · Mutable event: ValuationCompleted Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.IntegrationsEvents/ExternalEvents/ValuationCompleted.cs
- Immutable events · Mutable event: ValuationRequested Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.IntegrationsEvents/ExternalEvents/ValuationRequested.cs
- Immutable events · Mutable event: PriorityDefined Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.IntegrationsEvents/ExternalEvents/PriorityDefined.cs
- PII in the event store · PII in event: UserCreatedEvent Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/CreateUser/UserCreatedEvent.cs
Rebuild cost: about €22,000 · Estimate
| Cost to rebuild | €7,400 to €37,000, for 124 to 385 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 45. 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: 13,653 lines of product code, of which 54% is declarations and boilerplate, 42% straight logic and 5% logic with branches |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Emails.Core | 2 Emails.Core.Sender.TemplateReader | 3 Inquiries.Application.Common.Contracts | 4 Priorities.Application.Common.Contracts | 5 Push.DataAccess.DataAccess.Repositories.Write | 6 Services.Core.Services.Categories | 7 Shared.Abstractions.Configuration | 8 Shared.DDD.BuildingBlocks | 9 Shared.Infrastructure.FeatureFlags | 10 Users.Application.Contracts | 11 Users.Domain.Users | 12 Valuations.Application.Common.Contracts | 13 Inquiries.Application.Common.Interfaces | 14 Inquiries.Domain.Inquiries.Clients | 15 Inquiries.Domain.Inquiries.Items.Services | 16 Payments.IntegrationsEvents.External | 17 Priorities.Domain.Deadlines | 18 Services.Core.Services | 19 Services.Core.Services.Categories.Dtos | 20 Shared.DDD.ValueObjects | 21 Users.Api.Controllers | 22 Users.Application.Users.Queries.GetAllUsers | 23 Valuations.Application.Common.Interfaces | 24 Valuations.IntegrationsEvents.ExternalEvents | 25 Inquiries.Domain.Inquiries | 26 Payments.Domain.Payments | 27 Priorities.Domain | 28 Reminders.Priorities.DeadlineClose.Scheduler | 29 Services.Core.Services.Services | 30 Users.Application.Authentication | 31 Valuations.Domain.Valuations.Events | 32 Valuations.Domain.Valuations.Proposals | 33 Inquiries.Application.Inquiries.Commands.Make | 34 Payments.Application.Payments.Commands.Pay | 35 Services.Api.Controllers | 36 Users.Infrastructure.Identity.Jwt.RefreshTokens | 37 Valuations.Domain.Valuations.Proposals.Events | 38 Users.Infrastructure.Identity.Users.Services | 39 Valuations.Domain.Valuations.States | 40 Valuations.Domain.Valuations |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Emails.Core | ||||||||||||||||||||||||||||||||||||||||
| 2 Emails.Core.Sender.TemplateReader | ||||||||||||||||||||||||||||||||||||||||
| 3 Inquiries.Application.Common.Contracts | ||||||||||||||||||||||||||||||||||||||||
| 4 Priorities.Application.Common.Contracts | ||||||||||||||||||||||||||||||||||||||||
| 5 Push.DataAccess.DataAccess.Repositories.Write | ||||||||||||||||||||||||||||||||||||||||
| 6 Services.Core.Services.Categories | ||||||||||||||||||||||||||||||||||||||||
| 7 Shared.Abstractions.Configuration | ||||||||||||||||||||||||||||||||||||||||
| 8 Shared.DDD.BuildingBlocks | ||||||||||||||||||||||||||||||||||||||||
| 9 Shared.Infrastructure.FeatureFlags | ||||||||||||||||||||||||||||||||||||||||
| 10 Users.Application.Contracts | ||||||||||||||||||||||||||||||||||||||||
| 11 Users.Domain.Users | ||||||||||||||||||||||||||||||||||||||||
| 12 Valuations.Application.Common.Contracts | ||||||||||||||||||||||||||||||||||||||||
| 13 Inquiries.Application.Common.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Inquiries.Domain.Inquiries.Clients | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 Inquiries.Domain.Inquiries.Items.Services | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Payments.IntegrationsEvents.External | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 Priorities.Domain.Deadlines | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Services.Core.Services | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Services.Core.Services.Categories.Dtos | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Shared.DDD.ValueObjects | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Users.Api.Controllers | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 Users.Application.Users.Queries.GetAllUsers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 Valuations.Application.Common.Interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Valuations.IntegrationsEvents.ExternalEvents | 6 | |||||||||||||||||||||||||||||||||||||||
| 25 Inquiries.Domain.Inquiries | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 Payments.Domain.Payments | 5 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 Priorities.Domain | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Reminders.Priorities.DeadlineClose.Scheduler | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 Services.Core.Services.Services | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 Users.Application.Authentication | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 Valuations.Domain.Valuations.Events | 2 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 32 Valuations.Domain.Valuations.Proposals | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 Inquiries.Application.Inquiries.Commands.Make | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 Payments.Application.Payments.Commands.Pay | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 Services.Api.Controllers | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 36 Users.Infrastructure.Identity.Jwt.RefreshTokens | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 Valuations.Domain.Valuations.Proposals.Events | 4 | 3 | 5 | 9 | ||||||||||||||||||||||||||||||||||||
| 38 Users.Infrastructure.Identity.Users.Services | 8 | 1 | 8 | 2 | ||||||||||||||||||||||||||||||||||||
| 39 Valuations.Domain.Valuations.States | 9 | 4 | 5 | 5 | 3 | 13 | ||||||||||||||||||||||||||||||||||
| 40 Valuations.Domain.Valuations | 1 |
13→8 Inquiries.Application.Common.Interfaces uses Shared.DDD.BuildingBlocks✕
- Connections
- 1 pair of types, where a type in Inquiries.Application.Common.Interfaces uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Application.Common.Interfaces.IIntegrationEventPublisher→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IDomainEvent
- Direction
- Inquiries.Application.Common.Interfaces uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Inquiries.Application.Common.Interfaces, while a change to Inquiries.Application.Common.Interfaces can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Inquiries.Application.Common.Interfaces uses a module listed above it, which is the healthy direction.
14→8 Inquiries.Domain.Inquiries.Clients uses Shared.DDD.BuildingBlocks✕
- Connections
- 2 pairs of types, where a type in Inquiries.Domain.Inquiries.Clients uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Clients.Client→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.ValueObjectDivstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Clients.ClientCompany→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.ValueObject
- Direction
- Inquiries.Domain.Inquiries.Clients uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Inquiries.Domain.Inquiries.Clients, while a change to Inquiries.Domain.Inquiries.Clients can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Inquiries.Domain.Inquiries.Clients uses a module listed above it, which is the healthy direction.
15→8 Inquiries.Domain.Inquiries.Items.Services uses Shared.DDD.BuildingBlocks✕
- Connections
- 1 pair of types, where a type in Inquiries.Domain.Inquiries.Items.Services uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items.Services.Service→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.Entity
- Direction
- Inquiries.Domain.Inquiries.Items.Services uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Inquiries.Domain.Inquiries.Items.Services, while a change to Inquiries.Domain.Inquiries.Items.Services can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Inquiries.Domain.Inquiries.Items.Services uses a module listed above it, which is the healthy direction.
16→8 Payments.IntegrationsEvents.External uses Shared.DDD.BuildingBlocks✕
- Connections
- 2 pairs of types, where a type in Payments.IntegrationsEvents.External uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Payments.IntegrationsEvents.External.PaymentCompleted→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IIntegrationEventDivstack.Company.Estimation.Tool.Payments.IntegrationsEvents.External.PaymentInitialized→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IIntegrationEvent
- Direction
- Payments.IntegrationsEvents.External uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Payments.IntegrationsEvents.External, while a change to Payments.IntegrationsEvents.External can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Payments.IntegrationsEvents.External uses a module listed above it, which is the healthy direction.
17→8 Priorities.Domain.Deadlines uses Shared.DDD.BuildingBlocks✕
- Connections
- 1 pair of types, where a type in Priorities.Domain.Deadlines uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Priorities.Domain.Deadlines.Deadline→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.ValueObject
- Direction
- Priorities.Domain.Deadlines uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Priorities.Domain.Deadlines, while a change to Priorities.Domain.Deadlines can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Priorities.Domain.Deadlines uses a module listed above it, which is the healthy direction.
18→6 Services.Core.Services uses Services.Core.Services.Categories✕
- Connections
- 1 pair of types, where a type in Services.Core.Services uses a type in Services.Core.Services.Categories.
- The types involved
Divstack.Company.Estimation.Tool.Services.Core.Services.Service→Divstack.Company.Estimation.Tool.Services.Core.Services.Categories.Category
- Direction
- Services.Core.Services uses Services.Core.Services.Categories, so a change to Services.Core.Services.Categories can break Services.Core.Services, while a change to Services.Core.Services can't break Services.Core.Services.Categories.
- Position
- Below the diagonal: Services.Core.Services uses a module listed above it, which is the healthy direction.
19→6 Services.Core.Services.Categories.Dtos uses Services.Core.Services.Categories✕
- Connections
- 1 pair of types, where a type in Services.Core.Services.Categories.Dtos uses a type in Services.Core.Services.Categories.
- The types involved
Divstack.Company.Estimation.Tool.Services.Core.Services.Categories.Dtos.CategoryDto→Divstack.Company.Estimation.Tool.Services.Core.Services.Categories.Category
- Direction
- Services.Core.Services.Categories.Dtos uses Services.Core.Services.Categories, so a change to Services.Core.Services.Categories can break Services.Core.Services.Categories.Dtos, while a change to Services.Core.Services.Categories.Dtos can't break Services.Core.Services.Categories.
- Position
- Below the diagonal: Services.Core.Services.Categories.Dtos uses a module listed above it, which is the healthy direction.
20→8 Shared.DDD.ValueObjects uses Shared.DDD.BuildingBlocks✕
- Connections
- 1 pair of types, where a type in Shared.DDD.ValueObjects uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.Money→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.ValueObject
- Direction
- Shared.DDD.ValueObjects uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Shared.DDD.ValueObjects, while a change to Shared.DDD.ValueObjects can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Shared.DDD.ValueObjects uses a module listed above it, which is the healthy direction.
21→10 Users.Api.Controllers uses Users.Application.Contracts✕
- Connections
- 2 pairs of types, where a type in Users.Api.Controllers uses a type in Users.Application.Contracts.
- The types involved
Divstack.Company.Estimation.Tool.Users.Api.Controllers.AuthenticationController→Divstack.Company.Estimation.Tool.Users.Application.Contracts.IUserModuleDivstack.Company.Estimation.Tool.Users.Api.Controllers.UsersController→Divstack.Company.Estimation.Tool.Users.Application.Contracts.IUserModule
- Direction
- Users.Api.Controllers uses Users.Application.Contracts, so a change to Users.Application.Contracts can break Users.Api.Controllers, while a change to Users.Api.Controllers can't break Users.Application.Contracts.
- Position
- Below the diagonal: Users.Api.Controllers uses a module listed above it, which is the healthy direction.
22→10 Users.Application.Users.Queries.GetAllUsers uses Users.Application.Contracts✕
- Connections
- 1 pair of types, where a type in Users.Application.Users.Queries.GetAllUsers uses a type in Users.Application.Contracts.
- The types involved
Divstack.Company.Estimation.Tool.Users.Application.Users.Queries.GetAllUsers.GetAllUsersQuery→Divstack.Company.Estimation.Tool.Users.Application.Contracts.IQuery
- Direction
- Users.Application.Users.Queries.GetAllUsers uses Users.Application.Contracts, so a change to Users.Application.Contracts can break Users.Application.Users.Queries.GetAllUsers, while a change to Users.Application.Users.Queries.GetAllUsers can't break Users.Application.Contracts.
- Position
- Below the diagonal: Users.Application.Users.Queries.GetAllUsers uses a module listed above it, which is the healthy direction.
22→30 Users.Application.Users.Queries.GetAllUsers uses Users.Application.Authentication part of a loop✕
- Connections
- 1 pair of types, where a type in Users.Application.Users.Queries.GetAllUsers uses a type in Users.Application.Authentication.
- The types involved
Divstack.Company.Estimation.Tool.Users.Application.Users.Queries.GetAllUsers.Handler→Divstack.Company.Estimation.Tool.Users.Application.Authentication.IUserManagementService
- Direction
- Users.Application.Users.Queries.GetAllUsers uses Users.Application.Authentication, so a change to Users.Application.Authentication can break Users.Application.Users.Queries.GetAllUsers, while a change to Users.Application.Users.Queries.GetAllUsers can't break Users.Application.Authentication.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→8 Valuations.Application.Common.Interfaces uses Shared.DDD.BuildingBlocks✕
- Connections
- 1 pair of types, where a type in Valuations.Application.Common.Interfaces uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Application.Common.Interfaces.IIntegrationEventPublisher→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IDomainEvent
- Direction
- Valuations.Application.Common.Interfaces uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Valuations.Application.Common.Interfaces, while a change to Valuations.Application.Common.Interfaces can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Valuations.Application.Common.Interfaces uses a module listed above it, which is the healthy direction.
24→8 Valuations.IntegrationsEvents.ExternalEvents uses Shared.DDD.BuildingBlocks✕
- Connections
- 6 pairs of types, where a type in Valuations.IntegrationsEvents.ExternalEvents uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.IntegrationsEvents.ExternalEvents.ProposalApproved→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IIntegrationEventDivstack.Company.Estimation.Tool.Valuations.IntegrationsEvents.ExternalEvents.ProposalCancelled→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IIntegrationEventDivstack.Company.Estimation.Tool.Valuations.IntegrationsEvents.ExternalEvents.ProposalRejected→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IIntegrationEventDivstack.Company.Estimation.Tool.Valuations.IntegrationsEvents.ExternalEvents.ProposalSuggested→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IIntegrationEventDivstack.Company.Estimation.Tool.Valuations.IntegrationsEvents.ExternalEvents.ValuationCompleted→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IIntegrationEventDivstack.Company.Estimation.Tool.Valuations.IntegrationsEvents.ExternalEvents.ValuationRequested→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IIntegrationEvent
- Direction
- Valuations.IntegrationsEvents.ExternalEvents uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Valuations.IntegrationsEvents.ExternalEvents, while a change to Valuations.IntegrationsEvents.ExternalEvents can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Valuations.IntegrationsEvents.ExternalEvents uses a module listed above it, which is the healthy direction.
25→8 Inquiries.Domain.Inquiries uses Shared.DDD.BuildingBlocks✕
- Connections
- 2 pairs of types, where a type in Inquiries.Domain.Inquiries uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Inquiry→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.EntityDivstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Inquiry→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IAggregateRoot
- Direction
- Inquiries.Domain.Inquiries uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Inquiries.Domain.Inquiries, while a change to Inquiries.Domain.Inquiries can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Inquiries.Domain.Inquiries uses a module listed above it, which is the healthy direction.
25→14 Inquiries.Domain.Inquiries uses Inquiries.Domain.Inquiries.Clients✕
- Connections
- 1 pair of types, where a type in Inquiries.Domain.Inquiries uses a type in Inquiries.Domain.Inquiries.Clients.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Inquiry→Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Clients.Client
- Direction
- Inquiries.Domain.Inquiries uses Inquiries.Domain.Inquiries.Clients, so a change to Inquiries.Domain.Inquiries.Clients can break Inquiries.Domain.Inquiries, while a change to Inquiries.Domain.Inquiries can't break Inquiries.Domain.Inquiries.Clients.
- Position
- Below the diagonal: Inquiries.Domain.Inquiries uses a module listed above it, which is the healthy direction.
25→15 Inquiries.Domain.Inquiries uses Inquiries.Domain.Inquiries.Items.Services✕
- Connections
- 1 pair of types, where a type in Inquiries.Domain.Inquiries uses a type in Inquiries.Domain.Inquiries.Items.Services.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Inquiry→Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items.Services.Service
- Direction
- Inquiries.Domain.Inquiries uses Inquiries.Domain.Inquiries.Items.Services, so a change to Inquiries.Domain.Inquiries.Items.Services can break Inquiries.Domain.Inquiries, while a change to Inquiries.Domain.Inquiries can't break Inquiries.Domain.Inquiries.Items.Services.
- Position
- Below the diagonal: Inquiries.Domain.Inquiries uses a module listed above it, which is the healthy direction.
26→8 Payments.Domain.Payments uses Shared.DDD.BuildingBlocks✕
- Connections
- 5 pairs of types, where a type in Payments.Domain.Payments uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Payments.Domain.Payments.Card→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.ValueObjectDivstack.Company.Estimation.Tool.Payments.Domain.Payments.Payment→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.EntityDivstack.Company.Estimation.Tool.Payments.Domain.Payments.Payment→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IAggregateRootDivstack.Company.Estimation.Tool.Payments.Domain.Payments.PaymentSecret→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.ValueObjectDivstack.Company.Estimation.Tool.Payments.Domain.Payments.PaymentStatus→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.ValueObject
- Direction
- Payments.Domain.Payments uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Payments.Domain.Payments, while a change to Payments.Domain.Payments can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Payments.Domain.Payments uses a module listed above it, which is the healthy direction.
26→20 Payments.Domain.Payments uses Shared.DDD.ValueObjects✕
- Connections
- 2 pairs of types, where a type in Payments.Domain.Payments uses a type in Shared.DDD.ValueObjects.
- The types involved
Divstack.Company.Estimation.Tool.Payments.Domain.Payments.IPaymentProcessor→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.MoneyDivstack.Company.Estimation.Tool.Payments.Domain.Payments.Payment→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.Money
- Direction
- Payments.Domain.Payments uses Shared.DDD.ValueObjects, so a change to Shared.DDD.ValueObjects can break Payments.Domain.Payments, while a change to Payments.Domain.Payments can't break Shared.DDD.ValueObjects.
- Position
- Below the diagonal: Payments.Domain.Payments uses a module listed above it, which is the healthy direction.
27→8 Priorities.Domain uses Shared.DDD.BuildingBlocks✕
- Connections
- 1 pair of types, where a type in Priorities.Domain uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Priorities.Domain.Priority→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.Entity
- Direction
- Priorities.Domain uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Priorities.Domain, while a change to Priorities.Domain can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Priorities.Domain uses a module listed above it, which is the healthy direction.
27→17 Priorities.Domain uses Priorities.Domain.Deadlines✕
- Connections
- 1 pair of types, where a type in Priorities.Domain uses a type in Priorities.Domain.Deadlines.
- The types involved
Divstack.Company.Estimation.Tool.Priorities.Domain.Priority→Divstack.Company.Estimation.Tool.Priorities.Domain.Deadlines.Deadline
- Direction
- Priorities.Domain uses Priorities.Domain.Deadlines, so a change to Priorities.Domain.Deadlines can break Priorities.Domain, while a change to Priorities.Domain can't break Priorities.Domain.Deadlines.
- Position
- Below the diagonal: Priorities.Domain uses a module listed above it, which is the healthy direction.
28→24 Reminders.Priorities.DeadlineClose.Scheduler uses Valuations.IntegrationsEvents.ExternalEvents✕
- Connections
- 2 pairs of types, where a type in Reminders.Priorities.DeadlineClose.Scheduler uses a type in Valuations.IntegrationsEvents.ExternalEvents.
- The types involved
Divstack.Company.Estimation.Tool.Reminders.Priorities.DeadlineClose.Scheduler.PriorityCloseToDeadlineUnScheduler→Divstack.Company.Estimation.Tool.Valuations.IntegrationsEvents.ExternalEvents.ProposalCancelledDivstack.Company.Estimation.Tool.Reminders.Priorities.DeadlineClose.Scheduler.PriorityCloseToDeadlineUnScheduler→Divstack.Company.Estimation.Tool.Valuations.IntegrationsEvents.ExternalEvents.ProposalSuggested
- Direction
- Reminders.Priorities.DeadlineClose.Scheduler uses Valuations.IntegrationsEvents.ExternalEvents, so a change to Valuations.IntegrationsEvents.ExternalEvents can break Reminders.Priorities.DeadlineClose.Scheduler, while a change to Reminders.Priorities.DeadlineClose.Scheduler can't break Valuations.IntegrationsEvents.ExternalEvents.
- Position
- Below the diagonal: Reminders.Priorities.DeadlineClose.Scheduler uses a module listed above it, which is the healthy direction.
29→6 Services.Core.Services.Services uses Services.Core.Services.Categories✕
- Connections
- 2 pairs of types, where a type in Services.Core.Services.Services uses a type in Services.Core.Services.Categories.
- The types involved
Divstack.Company.Estimation.Tool.Services.Core.Services.Services.ServicesService→Divstack.Company.Estimation.Tool.Services.Core.Services.Categories.CategoryDivstack.Company.Estimation.Tool.Services.Core.Services.Services.ServicesService→Divstack.Company.Estimation.Tool.Services.Core.Services.Categories.ICategoriesRepository
- Direction
- Services.Core.Services.Services uses Services.Core.Services.Categories, so a change to Services.Core.Services.Categories can break Services.Core.Services.Services, while a change to Services.Core.Services.Services can't break Services.Core.Services.Categories.
- Position
- Below the diagonal: Services.Core.Services.Services uses a module listed above it, which is the healthy direction.
29→18 Services.Core.Services.Services uses Services.Core.Services✕
- Connections
- 2 pairs of types, where a type in Services.Core.Services.Services uses a type in Services.Core.Services.
- The types involved
Divstack.Company.Estimation.Tool.Services.Core.Services.Services.ServicesService→Divstack.Company.Estimation.Tool.Services.Core.Services.IServicesRepositoryDivstack.Company.Estimation.Tool.Services.Core.Services.Services.ServicesService→Divstack.Company.Estimation.Tool.Services.Core.Services.Service
- Direction
- Services.Core.Services.Services uses Services.Core.Services, so a change to Services.Core.Services can break Services.Core.Services.Services, while a change to Services.Core.Services.Services can't break Services.Core.Services.
- Position
- Below the diagonal: Services.Core.Services.Services uses a module listed above it, which is the healthy direction.
30→22 Users.Application.Authentication uses Users.Application.Users.Queries.GetAllUsers✕
- Connections
- 1 pair of types, where a type in Users.Application.Authentication uses a type in Users.Application.Users.Queries.GetAllUsers.
- The types involved
Divstack.Company.Estimation.Tool.Users.Application.Authentication.IUserManagementService→Divstack.Company.Estimation.Tool.Users.Application.Users.Queries.GetAllUsers.UserDto
- Direction
- Users.Application.Authentication uses Users.Application.Users.Queries.GetAllUsers, so a change to Users.Application.Users.Queries.GetAllUsers can break Users.Application.Authentication, while a change to Users.Application.Authentication can't break Users.Application.Users.Queries.GetAllUsers.
- Position
- Below the diagonal: Users.Application.Authentication uses a module listed above it, which is the healthy direction.
31→8 Valuations.Domain.Valuations.Events uses Shared.DDD.BuildingBlocks✕
- Connections
- 2 pairs of types, where a type in Valuations.Domain.Valuations.Events uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationCompletedDomainEvent→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.DomainEventBaseDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationRequestedDomainEvent→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.DomainEventBase
- Direction
- Valuations.Domain.Valuations.Events uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Valuations.Domain.Valuations.Events, while a change to Valuations.Domain.Valuations.Events can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Valuations.Domain.Valuations.Events uses a module listed above it, which is the healthy direction.
31→20 Valuations.Domain.Valuations.Events uses Shared.DDD.ValueObjects✕
- Connections
- 1 pair of types, where a type in Valuations.Domain.Valuations.Events uses a type in Shared.DDD.ValueObjects.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationCompletedDomainEvent→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.Money
- Direction
- Valuations.Domain.Valuations.Events uses Shared.DDD.ValueObjects, so a change to Shared.DDD.ValueObjects can break Valuations.Domain.Valuations.Events, while a change to Valuations.Domain.Valuations.Events can't break Shared.DDD.ValueObjects.
- Position
- Below the diagonal: Valuations.Domain.Valuations.Events uses a module listed above it, which is the healthy direction.
31→40 Valuations.Domain.Valuations.Events uses Valuations.Domain.Valuations part of a loop✕
- Connections
- 5 pairs of types, where a type in Valuations.Domain.Valuations.Events uses a type in Valuations.Domain.Valuations.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationCompletedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.EmployeeIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationCompletedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.InquiryIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationCompletedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationRequestedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.InquiryIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationRequestedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationId
- Direction
- Valuations.Domain.Valuations.Events uses Valuations.Domain.Valuations, so a change to Valuations.Domain.Valuations can break Valuations.Domain.Valuations.Events, while a change to Valuations.Domain.Valuations.Events can't break Valuations.Domain.Valuations.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→8 Valuations.Domain.Valuations.Proposals uses Shared.DDD.BuildingBlocks✕
- Connections
- 3 pairs of types, where a type in Valuations.Domain.Valuations.Proposals uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Proposal→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.EntityDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalDecision→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.ValueObjectDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalDescription→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.ValueObject
- Direction
- Valuations.Domain.Valuations.Proposals uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Valuations.Domain.Valuations.Proposals, while a change to Valuations.Domain.Valuations.Proposals can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Valuations.Domain.Valuations.Proposals uses a module listed above it, which is the healthy direction.
32→20 Valuations.Domain.Valuations.Proposals uses Shared.DDD.ValueObjects✕
- Connections
- 1 pair of types, where a type in Valuations.Domain.Valuations.Proposals uses a type in Shared.DDD.ValueObjects.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Proposal→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.Money
- Direction
- Valuations.Domain.Valuations.Proposals uses Shared.DDD.ValueObjects, so a change to Shared.DDD.ValueObjects can break Valuations.Domain.Valuations.Proposals, while a change to Valuations.Domain.Valuations.Proposals can't break Shared.DDD.ValueObjects.
- Position
- Below the diagonal: Valuations.Domain.Valuations.Proposals uses a module listed above it, which is the healthy direction.
32→40 Valuations.Domain.Valuations.Proposals uses Valuations.Domain.Valuations part of a loop✕
- Connections
- 1 pair of types, where a type in Valuations.Domain.Valuations.Proposals uses a type in Valuations.Domain.Valuations.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Proposal→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.EmployeeId
- Direction
- Valuations.Domain.Valuations.Proposals uses Valuations.Domain.Valuations, so a change to Valuations.Domain.Valuations can break Valuations.Domain.Valuations.Proposals, while a change to Valuations.Domain.Valuations.Proposals can't break Valuations.Domain.Valuations.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→3 Inquiries.Application.Inquiries.Commands.Make uses Inquiries.Application.Common.Contracts✕
- Connections
- 1 pair of types, where a type in Inquiries.Application.Inquiries.Commands.Make uses a type in Inquiries.Application.Common.Contracts.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Application.Inquiries.Commands.Make.MakeInquiryCommand→Divstack.Company.Estimation.Tool.Inquiries.Application.Common.Contracts.ICommand
- Direction
- Inquiries.Application.Inquiries.Commands.Make uses Inquiries.Application.Common.Contracts, so a change to Inquiries.Application.Common.Contracts can break Inquiries.Application.Inquiries.Commands.Make, while a change to Inquiries.Application.Inquiries.Commands.Make can't break Inquiries.Application.Common.Contracts.
- Position
- Below the diagonal: Inquiries.Application.Inquiries.Commands.Make uses a module listed above it, which is the healthy direction.
33→13 Inquiries.Application.Inquiries.Commands.Make uses Inquiries.Application.Common.Interfaces✕
- Connections
- 2 pairs of types, where a type in Inquiries.Application.Inquiries.Commands.Make uses a type in Inquiries.Application.Common.Interfaces.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Application.Inquiries.Commands.Make.MakeInquiryCommandHandler→Divstack.Company.Estimation.Tool.Inquiries.Application.Common.Interfaces.IIntegrationEventPublisherDivstack.Company.Estimation.Tool.Inquiries.Application.Inquiries.Commands.Make.MakeInquiryCommandHandler→Divstack.Company.Estimation.Tool.Inquiries.Application.Common.Interfaces.IMapper
- Direction
- Inquiries.Application.Inquiries.Commands.Make uses Inquiries.Application.Common.Interfaces, so a change to Inquiries.Application.Common.Interfaces can break Inquiries.Application.Inquiries.Commands.Make, while a change to Inquiries.Application.Inquiries.Commands.Make can't break Inquiries.Application.Common.Interfaces.
- Position
- Below the diagonal: Inquiries.Application.Inquiries.Commands.Make uses a module listed above it, which is the healthy direction.
33→14 Inquiries.Application.Inquiries.Commands.Make uses Inquiries.Domain.Inquiries.Clients✕
- Connections
- 1 pair of types, where a type in Inquiries.Application.Inquiries.Commands.Make uses a type in Inquiries.Domain.Inquiries.Clients.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Application.Inquiries.Commands.Make.MakeInquiryCommandHandler→Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Clients.IClientCompanyFinder
- Direction
- Inquiries.Application.Inquiries.Commands.Make uses Inquiries.Domain.Inquiries.Clients, so a change to Inquiries.Domain.Inquiries.Clients can break Inquiries.Application.Inquiries.Commands.Make, while a change to Inquiries.Application.Inquiries.Commands.Make can't break Inquiries.Domain.Inquiries.Clients.
- Position
- Below the diagonal: Inquiries.Application.Inquiries.Commands.Make uses a module listed above it, which is the healthy direction.
33→15 Inquiries.Application.Inquiries.Commands.Make uses Inquiries.Domain.Inquiries.Items.Services✕
- Connections
- 1 pair of types, where a type in Inquiries.Application.Inquiries.Commands.Make uses a type in Inquiries.Domain.Inquiries.Items.Services.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Application.Inquiries.Commands.Make.MakeInquiryCommandHandler→Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items.Services.Service
- Direction
- Inquiries.Application.Inquiries.Commands.Make uses Inquiries.Domain.Inquiries.Items.Services, so a change to Inquiries.Domain.Inquiries.Items.Services can break Inquiries.Application.Inquiries.Commands.Make, while a change to Inquiries.Application.Inquiries.Commands.Make can't break Inquiries.Domain.Inquiries.Items.Services.
- Position
- Below the diagonal: Inquiries.Application.Inquiries.Commands.Make uses a module listed above it, which is the healthy direction.
33→25 Inquiries.Application.Inquiries.Commands.Make uses Inquiries.Domain.Inquiries✕
- Connections
- 1 pair of types, where a type in Inquiries.Application.Inquiries.Commands.Make uses a type in Inquiries.Domain.Inquiries.
- The types involved
Divstack.Company.Estimation.Tool.Inquiries.Application.Inquiries.Commands.Make.MakeInquiryCommandHandler→Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.IInquiriesRepository
- Direction
- Inquiries.Application.Inquiries.Commands.Make uses Inquiries.Domain.Inquiries, so a change to Inquiries.Domain.Inquiries can break Inquiries.Application.Inquiries.Commands.Make, while a change to Inquiries.Application.Inquiries.Commands.Make can't break Inquiries.Domain.Inquiries.
- Position
- Below the diagonal: Inquiries.Application.Inquiries.Commands.Make uses a module listed above it, which is the healthy direction.
34→26 Payments.Application.Payments.Commands.Pay uses Payments.Domain.Payments✕
- Connections
- 2 pairs of types, where a type in Payments.Application.Payments.Commands.Pay uses a type in Payments.Domain.Payments.
- The types involved
Divstack.Company.Estimation.Tool.Payments.Application.Payments.Commands.Pay.PayCommandHandler→Divstack.Company.Estimation.Tool.Payments.Domain.Payments.IPaymentProcessorDivstack.Company.Estimation.Tool.Payments.Application.Payments.Commands.Pay.PayCommandHandler→Divstack.Company.Estimation.Tool.Payments.Domain.Payments.IPaymentsRepository
- Direction
- Payments.Application.Payments.Commands.Pay uses Payments.Domain.Payments, so a change to Payments.Domain.Payments can break Payments.Application.Payments.Commands.Pay, while a change to Payments.Application.Payments.Commands.Pay can't break Payments.Domain.Payments.
- Position
- Below the diagonal: Payments.Application.Payments.Commands.Pay uses a module listed above it, which is the healthy direction.
35→19 Services.Api.Controllers uses Services.Core.Services.Categories.Dtos✕
- Connections
- 1 pair of types, where a type in Services.Api.Controllers uses a type in Services.Core.Services.Categories.Dtos.
- The types involved
Divstack.Company.Estimation.Tool.Services.Api.Controllers.CategoriesController→Divstack.Company.Estimation.Tool.Services.Core.Services.Categories.Dtos.CreateCategoryRequest
- Direction
- Services.Api.Controllers uses Services.Core.Services.Categories.Dtos, so a change to Services.Core.Services.Categories.Dtos can break Services.Api.Controllers, while a change to Services.Api.Controllers can't break Services.Core.Services.Categories.Dtos.
- Position
- Below the diagonal: Services.Api.Controllers uses a module listed above it, which is the healthy direction.
35→29 Services.Api.Controllers uses Services.Core.Services.Services✕
- Connections
- 3 pairs of types, where a type in Services.Api.Controllers uses a type in Services.Core.Services.Services.
- The types involved
Divstack.Company.Estimation.Tool.Services.Api.Controllers.AttributesController→Divstack.Company.Estimation.Tool.Services.Core.Services.Services.IServicesServiceDivstack.Company.Estimation.Tool.Services.Api.Controllers.PossibleValuesController→Divstack.Company.Estimation.Tool.Services.Core.Services.Services.IServicesServiceDivstack.Company.Estimation.Tool.Services.Api.Controllers.ServicesController→Divstack.Company.Estimation.Tool.Services.Core.Services.Services.IServicesService
- Direction
- Services.Api.Controllers uses Services.Core.Services.Services, so a change to Services.Core.Services.Services can break Services.Api.Controllers, while a change to Services.Api.Controllers can't break Services.Core.Services.Services.
- Position
- Below the diagonal: Services.Api.Controllers uses a module listed above it, which is the healthy direction.
36→11 Users.Infrastructure.Identity.Jwt.RefreshTokens uses Users.Domain.Users✕
- Connections
- 2 pairs of types, where a type in Users.Infrastructure.Identity.Jwt.RefreshTokens uses a type in Users.Domain.Users.
- The types involved
Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Jwt.RefreshTokens.IRefreshTokenRepository→Divstack.Company.Estimation.Tool.Users.Domain.Users.RefreshTokenDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Jwt.RefreshTokens.RefreshTokenRepository→Divstack.Company.Estimation.Tool.Users.Domain.Users.RefreshToken
- Direction
- Users.Infrastructure.Identity.Jwt.RefreshTokens uses Users.Domain.Users, so a change to Users.Domain.Users can break Users.Infrastructure.Identity.Jwt.RefreshTokens, while a change to Users.Infrastructure.Identity.Jwt.RefreshTokens can't break Users.Domain.Users.
- Position
- Below the diagonal: Users.Infrastructure.Identity.Jwt.RefreshTokens uses a module listed above it, which is the healthy direction.
36→30 Users.Infrastructure.Identity.Jwt.RefreshTokens uses Users.Application.Authentication✕
- Connections
- 2 pairs of types, where a type in Users.Infrastructure.Identity.Jwt.RefreshTokens uses a type in Users.Application.Authentication.
- The types involved
Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Jwt.RefreshTokens.JwtTokenManagementService→Divstack.Company.Estimation.Tool.Users.Application.Authentication.IJwtTokenManagementServiceDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Jwt.RefreshTokens.RefreshTokenGenerationService→Divstack.Company.Estimation.Tool.Users.Application.Authentication.IRefreshTokenGenerationService
- Direction
- Users.Infrastructure.Identity.Jwt.RefreshTokens uses Users.Application.Authentication, so a change to Users.Application.Authentication can break Users.Infrastructure.Identity.Jwt.RefreshTokens, while a change to Users.Infrastructure.Identity.Jwt.RefreshTokens can't break Users.Application.Authentication.
- Position
- Below the diagonal: Users.Infrastructure.Identity.Jwt.RefreshTokens uses a module listed above it, which is the healthy direction.
37→8 Valuations.Domain.Valuations.Proposals.Events uses Shared.DDD.BuildingBlocks✕
- Connections
- 4 pairs of types, where a type in Valuations.Domain.Valuations.Proposals.Events uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalApprovedDomainEvent→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.DomainEventBaseDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalCancelledDomainEvent→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.DomainEventBaseDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalRejectedDomainEvent→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.DomainEventBaseDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalSuggestedDomainEvent→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.DomainEventBase
- Direction
- Valuations.Domain.Valuations.Proposals.Events uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Valuations.Domain.Valuations.Proposals.Events, while a change to Valuations.Domain.Valuations.Proposals.Events can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Valuations.Domain.Valuations.Proposals.Events uses a module listed above it, which is the healthy direction.
37→20 Valuations.Domain.Valuations.Proposals.Events uses Shared.DDD.ValueObjects✕
- Connections
- 3 pairs of types, where a type in Valuations.Domain.Valuations.Proposals.Events uses a type in Shared.DDD.ValueObjects.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalApprovedDomainEvent→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.MoneyDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalRejectedDomainEvent→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.MoneyDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalSuggestedDomainEvent→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.Money
- Direction
- Valuations.Domain.Valuations.Proposals.Events uses Shared.DDD.ValueObjects, so a change to Shared.DDD.ValueObjects can break Valuations.Domain.Valuations.Proposals.Events, while a change to Valuations.Domain.Valuations.Proposals.Events can't break Shared.DDD.ValueObjects.
- Position
- Below the diagonal: Valuations.Domain.Valuations.Proposals.Events uses a module listed above it, which is the healthy direction.
37→32 Valuations.Domain.Valuations.Proposals.Events uses Valuations.Domain.Valuations.Proposals✕
- Connections
- 5 pairs of types, where a type in Valuations.Domain.Valuations.Proposals.Events uses a type in Valuations.Domain.Valuations.Proposals.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalApprovedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalCancelledDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalRejectedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalSuggestedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalDescriptionDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalSuggestedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalId
- Direction
- Valuations.Domain.Valuations.Proposals.Events uses Valuations.Domain.Valuations.Proposals, so a change to Valuations.Domain.Valuations.Proposals can break Valuations.Domain.Valuations.Proposals.Events, while a change to Valuations.Domain.Valuations.Proposals.Events can't break Valuations.Domain.Valuations.Proposals.
- Position
- Below the diagonal: Valuations.Domain.Valuations.Proposals.Events uses a module listed above it, which is the healthy direction.
37→40 Valuations.Domain.Valuations.Proposals.Events uses Valuations.Domain.Valuations part of a loop✕
- Connections
- 9 pairs of types, where a type in Valuations.Domain.Valuations.Proposals.Events uses a type in Valuations.Domain.Valuations.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalApprovedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.EmployeeIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalApprovedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalCancelledDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.EmployeeIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalCancelledDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.InquiryIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalCancelledDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalRejectedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalSuggestedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.EmployeeIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalSuggestedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.InquiryIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalSuggestedDomainEvent→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationId
- Direction
- Valuations.Domain.Valuations.Proposals.Events uses Valuations.Domain.Valuations, so a change to Valuations.Domain.Valuations can break Valuations.Domain.Valuations.Proposals.Events, while a change to Valuations.Domain.Valuations.Proposals.Events can't break Valuations.Domain.Valuations.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→11 Users.Infrastructure.Identity.Users.Services uses Users.Domain.Users✕
- Connections
- 8 pairs of types, where a type in Users.Infrastructure.Identity.Users.Services uses a type in Users.Domain.Users.
- The types involved
Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.ApplicationUserManager→Divstack.Company.Estimation.Tool.Users.Domain.Users.UserAccountDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.ISignInManager→Divstack.Company.Estimation.Tool.Users.Domain.Users.UserAccountDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.IUsersRepository→Divstack.Company.Estimation.Tool.Users.Domain.Users.UserAccountDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.RoleManagementService→Divstack.Company.Estimation.Tool.Users.Domain.Users.ApplicationRoleDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.SignInManagementService→Divstack.Company.Estimation.Tool.Users.Domain.Users.UserAccountDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.UserAccountSignInManager→Divstack.Company.Estimation.Tool.Users.Domain.Users.UserAccountDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.UserManagementService→Divstack.Company.Estimation.Tool.Users.Domain.Users.UserAccountDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.UsersRepository→Divstack.Company.Estimation.Tool.Users.Domain.Users.UserAccount
- Direction
- Users.Infrastructure.Identity.Users.Services uses Users.Domain.Users, so a change to Users.Domain.Users can break Users.Infrastructure.Identity.Users.Services, while a change to Users.Infrastructure.Identity.Users.Services can't break Users.Domain.Users.
- Position
- Below the diagonal: Users.Infrastructure.Identity.Users.Services uses a module listed above it, which is the healthy direction.
38→22 Users.Infrastructure.Identity.Users.Services uses Users.Application.Users.Queries.GetAllUsers✕
- Connections
- 1 pair of types, where a type in Users.Infrastructure.Identity.Users.Services uses a type in Users.Application.Users.Queries.GetAllUsers.
- The types involved
Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.UserManagementService→Divstack.Company.Estimation.Tool.Users.Application.Users.Queries.GetAllUsers.UserDto
- Direction
- Users.Infrastructure.Identity.Users.Services uses Users.Application.Users.Queries.GetAllUsers, so a change to Users.Application.Users.Queries.GetAllUsers can break Users.Infrastructure.Identity.Users.Services, while a change to Users.Infrastructure.Identity.Users.Services can't break Users.Application.Users.Queries.GetAllUsers.
- Position
- Below the diagonal: Users.Infrastructure.Identity.Users.Services uses a module listed above it, which is the healthy direction.
38→30 Users.Infrastructure.Identity.Users.Services uses Users.Application.Authentication✕
- Connections
- 8 pairs of types, where a type in Users.Infrastructure.Identity.Users.Services uses a type in Users.Application.Authentication.
- The types involved
Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.ApplicationUserManager→Divstack.Company.Estimation.Tool.Users.Application.Authentication.ICurrentUserServiceDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.RoleManagementService→Divstack.Company.Estimation.Tool.Users.Application.Authentication.IRoleManagementServiceDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.SignInManagementService→Divstack.Company.Estimation.Tool.Users.Application.Authentication.ICurrentUserServiceDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.SignInManagementService→Divstack.Company.Estimation.Tool.Users.Application.Authentication.ISignInManagementServiceDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.SignInManagementService→Divstack.Company.Estimation.Tool.Users.Application.Authentication.SignInRequestDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.SignInManagementService→Divstack.Company.Estimation.Tool.Users.Application.Authentication.SignInResultStatusDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.UserManagementService→Divstack.Company.Estimation.Tool.Users.Application.Authentication.ICurrentUserServiceDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.UserManagementService→Divstack.Company.Estimation.Tool.Users.Application.Authentication.IUserManagementService
- Direction
- Users.Infrastructure.Identity.Users.Services uses Users.Application.Authentication, so a change to Users.Application.Authentication can break Users.Infrastructure.Identity.Users.Services, while a change to Users.Infrastructure.Identity.Users.Services can't break Users.Application.Authentication.
- Position
- Below the diagonal: Users.Infrastructure.Identity.Users.Services uses a module listed above it, which is the healthy direction.
38→36 Users.Infrastructure.Identity.Users.Services uses Users.Infrastructure.Identity.Jwt.RefreshTokens✕
- Connections
- 2 pairs of types, where a type in Users.Infrastructure.Identity.Users.Services uses a type in Users.Infrastructure.Identity.Jwt.RefreshTokens.
- The types involved
Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.SignInManagementService→Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Jwt.RefreshTokens.IRefreshTokenRepositoryDivstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.SignInManagementService→Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Jwt.RefreshTokens.ITokenStoreManager
- Direction
- Users.Infrastructure.Identity.Users.Services uses Users.Infrastructure.Identity.Jwt.RefreshTokens, so a change to Users.Infrastructure.Identity.Jwt.RefreshTokens can break Users.Infrastructure.Identity.Users.Services, while a change to Users.Infrastructure.Identity.Users.Services can't break Users.Infrastructure.Identity.Jwt.RefreshTokens.
- Position
- Below the diagonal: Users.Infrastructure.Identity.Users.Services uses a module listed above it, which is the healthy direction.
39→8 Valuations.Domain.Valuations.States uses Shared.DDD.BuildingBlocks✕
- Connections
- 9 pairs of types, where a type in Valuations.Domain.Valuations.States uses a type in Shared.DDD.BuildingBlocks.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.IValuationState→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IDomainEventDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationApproved→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.EntityDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationApproved→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IAggregateRootDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationCompleted→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.EntityDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationCompleted→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IAggregateRootDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.EntityDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IAggregateRootDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationRequested→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.EntityDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationRequested→Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks.IAggregateRoot
- Direction
- Valuations.Domain.Valuations.States uses Shared.DDD.BuildingBlocks, so a change to Shared.DDD.BuildingBlocks can break Valuations.Domain.Valuations.States, while a change to Valuations.Domain.Valuations.States can't break Shared.DDD.BuildingBlocks.
- Position
- Below the diagonal: Valuations.Domain.Valuations.States uses a module listed above it, which is the healthy direction.
39→20 Valuations.Domain.Valuations.States uses Shared.DDD.ValueObjects✕
- Connections
- 4 pairs of types, where a type in Valuations.Domain.Valuations.States uses a type in Shared.DDD.ValueObjects.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationApproved→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.MoneyDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationCompleted→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.MoneyDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.MoneyDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationRequested→Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.Money
- Direction
- Valuations.Domain.Valuations.States uses Shared.DDD.ValueObjects, so a change to Shared.DDD.ValueObjects can break Valuations.Domain.Valuations.States, while a change to Valuations.Domain.Valuations.States can't break Shared.DDD.ValueObjects.
- Position
- Below the diagonal: Valuations.Domain.Valuations.States uses a module listed above it, which is the healthy direction.
39→31 Valuations.Domain.Valuations.States uses Valuations.Domain.Valuations.Events✕
- Connections
- 5 pairs of types, where a type in Valuations.Domain.Valuations.States uses a type in Valuations.Domain.Valuations.Events.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationApproved→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationRequestedDomainEventDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationCompleted→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationCompletedDomainEventDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationCompleted→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationRequestedDomainEventDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationRequestedDomainEventDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationRequested→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events.ValuationRequestedDomainEvent
- Direction
- Valuations.Domain.Valuations.States uses Valuations.Domain.Valuations.Events, so a change to Valuations.Domain.Valuations.Events can break Valuations.Domain.Valuations.States, while a change to Valuations.Domain.Valuations.States can't break Valuations.Domain.Valuations.Events.
- Position
- Below the diagonal: Valuations.Domain.Valuations.States uses a module listed above it, which is the healthy direction.
39→32 Valuations.Domain.Valuations.States uses Valuations.Domain.Valuations.Proposals✕
- Connections
- 5 pairs of types, where a type in Valuations.Domain.Valuations.States uses a type in Valuations.Domain.Valuations.Proposals.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationApproved→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationApproved→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalDescriptionDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.ProposalId
- Direction
- Valuations.Domain.Valuations.States uses Valuations.Domain.Valuations.Proposals, so a change to Valuations.Domain.Valuations.Proposals can break Valuations.Domain.Valuations.States, while a change to Valuations.Domain.Valuations.States can't break Valuations.Domain.Valuations.Proposals.
- Position
- Below the diagonal: Valuations.Domain.Valuations.States uses a module listed above it, which is the healthy direction.
39→37 Valuations.Domain.Valuations.States uses Valuations.Domain.Valuations.Proposals.Events✕
- Connections
- 3 pairs of types, where a type in Valuations.Domain.Valuations.States uses a type in Valuations.Domain.Valuations.Proposals.Events.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationApproved→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalApprovedDomainEventDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalRejectedDomainEventDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events.ProposalSuggestedDomainEvent
- Direction
- Valuations.Domain.Valuations.States uses Valuations.Domain.Valuations.Proposals.Events, so a change to Valuations.Domain.Valuations.Proposals.Events can break Valuations.Domain.Valuations.States, while a change to Valuations.Domain.Valuations.States can't break Valuations.Domain.Valuations.Proposals.Events.
- Position
- Below the diagonal: Valuations.Domain.Valuations.States uses a module listed above it, which is the healthy direction.
39→40 Valuations.Domain.Valuations.States uses Valuations.Domain.Valuations part of a loop✕
- Connections
- 13 pairs of types, where a type in Valuations.Domain.Valuations.States uses a type in Valuations.Domain.Valuations.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.IValuationState→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationApproved→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.EmployeeIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationApproved→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.InquiryIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationApproved→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationCompleted→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.EmployeeIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationCompleted→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.InquiryIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationCompleted→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.EmployeeIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.InquiryIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationNegotiation→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationRequested→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.EmployeeIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationRequested→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.InquiryIdDivstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationRequested→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.ValuationId
- Direction
- Valuations.Domain.Valuations.States uses Valuations.Domain.Valuations, so a change to Valuations.Domain.Valuations can break Valuations.Domain.Valuations.States, while a change to Valuations.Domain.Valuations.States can't break Valuations.Domain.Valuations.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
40→39 Valuations.Domain.Valuations uses Valuations.Domain.Valuations.States✕
- Connections
- 1 pair of types, where a type in Valuations.Domain.Valuations uses a type in Valuations.Domain.Valuations.States.
- The types involved
Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.IValuationsRepository→Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationRequested
- Direction
- Valuations.Domain.Valuations uses Valuations.Domain.Valuations.States, so a change to Valuations.Domain.Valuations.States can break Valuations.Domain.Valuations, while a change to Valuations.Domain.Valuations can't break Valuations.Domain.Valuations.States.
- Position
- Below the diagonal: Valuations.Domain.Valuations 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 — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 43 | High / Critical |
| A07:2025 — Authentication Failures | 38 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 28 | High / Critical |
| A02:2025 — Security Misconfiguration | 8 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2); Resolve the 41 Outdated finding(s) in Dependency Hygiene — start with REDACTED (9), REDACTED (8), REDACTED (3); Resolve the 38 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5), REDACTED (3), REDACTED (3).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). | +9.0 pts | Low | REDACTED Scanning |
| Resolve the 41 Outdated finding(s) in Dependency Hygiene — start with REDACTED (9), REDACTED (8), REDACTED (3). | +8.6 pts | Medium | Dependency Hygiene |
| Resolve the 38 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5), REDACTED (3), REDACTED (3). | +8.4 pts | Medium | Dependency Hygiene |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +4.9 pts | Medium | DR & Backup |
| Resolve the 13 Prerelease dependency finding(s) in Dependency Hygiene. | +4.1 pts | Medium | Dependency Hygiene |
| Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse. | +4.1 pts | Medium | Test isolation |
| Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices. | +3.4 pts | Medium | Slice cohesion |
| Resolve the 40 Low coverage finding(s) in Code Coverage — start with SharedInfrastructureModule.cs, HealthChecksSharedModule.cs, EventBusModule.cs. | +2.8 pts | Medium | Code Coverage |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 0.2 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.7 | Slop | Secrets (history): High secret: REDACTED |
| REDACTED | 0.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 1.7 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 3.1 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.4 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Divstack.Company.Estimation.Tool.Valuations.Application.csproj | 4.0 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Core/Divstack.Company.Estimation.Tool.Sms.Core.csproj | 4.4 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| REDACTED | 4.4 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 4.5 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Infrastructure/Divstack.Company.Estimation.Tool.Payments.Infrastructure.csproj | 4.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Valuations/Divstack.Company.Estimation.Tool.Push.Valuations.csproj | 5.7 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Payments/Divstack.Company.Estimation.Tool.Push.Payments.csproj | 5.7 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Divstack.Company.Estimation.Tool.Priorities.Infrastructure.csproj | 5.7 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| REDACTED | 5.7 | Mixed | Dependency Vulnerabilities: High CVE: 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 103 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 103 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, 633 of 724 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (6 contributor(s) across 727 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 5 hold 2.8% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/infrastructure-appsettings.json`, `Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure.Azure/azure-appsettings.json`, `Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails/emails-appsettings.json`, `Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/emails-payments-appsettings.json`, `Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Priorities/emails-priority-appsettings.json` and 13 more did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- AX7 Slice cohesion — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
- DM6 Domain ↔ infrastructure boundary — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
- 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.
- ES3 PII in the event store — 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 persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 47 further occurrence(s) are not listed individually; the score already reflects all 87.
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.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
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 Init_users_module.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
9 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Init_users_module.cs, DataAccessModule.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with AsyncUtil.cs, DesignTimeDbContextFactoryBase.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with UserManagementService.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
72 projects, 0 dependency cycle(s), 4 unstable depended-on project(s).
What to do
- Resolve the 4 Layer violation finding(s) in Coupling — start with Divstack.Company.Estimation.Tool.Priorities.Application.csproj, Divstack.Company.Estimation.Tool.Sms.Core.csproj, Divstack.Company.Estimation.Tool.Users.Application.csproj. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 4 Off the main sequence finding(s) in Coupling — start with Divstack.Company.Estimation.Tool.Services.Core.csproj, Divstack.Company.Estimation.Tool.Payments.IntegrationsEvents.csproj, Divstack.Company.Estimation.Tool.Inquiries.IntegrationsEvents.csproj. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Unstable project Divstack.Company.Estimation.Tool.Emails.Valuations finding(s) in Coupling — start with Divstack.Company.Estimation.Tool.Emails.Valuations.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
1 of 56 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with UserAccount.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D7 · Architectural Integrity
All 4 mechanizable ADR(s) are enforced: 4 by analyzers, 0 by tests. Cycles found: 0.
D8 · Code Coverage
Line coverage 37.2% — 40 file(s) below 50% · 1 method(s) over the CRAP-30 risk line.
What to do
- Resolve the 40 Low coverage finding(s) in Code Coverage — start with SharedInfrastructureModule.cs, HealthChecksSharedModule.cs, EventBusModule.cs. — One of this dimension's main actionable groups (40 warning-level).
- Resolve the 1 No test project references Divstack.Estimation.Tool.Deployment.Infrastru… finding(s) in Code Coverage — start with Divstack.Estimation.Tool.Deployment.Infrastructure.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references Divstack.Company.Estimation.Tool.Shared.Infra… finding(s) in Code Coverage — start with Divstack.Company.Estimation.Tool.Shared.Infrastructure.Signalr.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
36 test methods: 29 unit, 4 integration, 3 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 6 mock references across 37 tests.
D11 · Test Reliability
0 flaky across 4 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky); BDD: measured (0 flaky); other: measured (0 flaky).
D12 · Dependency Hygiene
96 outdated, 6 vulnerable, 16 deprecated, 13 prerelease packages.
What to do
- Resolve the 41 Outdated finding(s) in Dependency Hygiene — start with REDACTED (9), REDACTED (8), REDACTED (3). — One of this dimension's main actionable groups (41 recommendation-level).
- Resolve the 38 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (38 warning-level).
- Resolve the 13 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (13 warning-level).
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 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 501 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 116 direct `PackageReference`(s), and 134 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
76 deducted debt markers + 54 dead symbols across 13653 LoC in the .NET projects (3.7/KLoC) → score 2.6.
What to do
- Resolve the 5 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (3), Divstack.Company.Estimation.Tool.Valuations.Domain.csproj (2). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 FileScopedPragmaDisable repeated across 21 files finding(s) in Explicit Debt — start with MakeInquiryCommand.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ChangeUserPasswordCommand.cs. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
69 projects, 845 source files, 15712 hand-written lines of code (13624 production / 2088 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 935 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 192 inter-project edges.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 1 document(s) read across 62 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
0 of 4 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D23 · Boundary Type-Coupling
2 domain type(s) cross context boundaries across 14 contexts; they are measured and withheld (not published, not scored). Contexts: Bootstrapper, Deployment, Divstack.Company.Estimation.Tool.Push, Emails, Inquiries, Payments, Priorities, Push, Reminders, Services, Shared, Sms and 2 more.
D26 · Project Cohesion
0 of 72 projects flagged as possibly oversized/incoherent.
D27 · Navigability
90 % of calls cross a namespace and 24 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.
What to do
- Resolve the 4 Pass-through layer finding(s) in Navigability — start with UserModule.cs, ValuationsModule.cs, PaymentsModule.cs. — One of this dimension's main actionable groups (4 recommendation-level).
D28 · Secrets (history)
35 finding(s): 0 critical, 35 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 27 High secret finding(s) in Secrets (history) — start with REDACTED (6), REDACTED (6), REDACTED (6). — One of this dimension's main actionable groups (27 issue-level).
- Resolve the 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 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)
43 finding(s): 0 critical, 33 high, 10 medium, 0 low. 19 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (12). — One of this dimension's main actionable groups (12 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 19 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 (19 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
28 finding(s): 4 critical, 14 high, 10 medium, 0 low.
What to do
- Resolve the 14 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 10 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
D31 · IaC & Container Security
8 finding(s): 0 critical, 1 high, 6 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
27 of 27 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Migrations/Init_users_module.cs. Counted over 27 of the 757 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with Init_users_module.cs, UserManagementService.cs, ContainerAppCreator.cs. — One of this dimension's main actionable groups (27 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
2 of 1258 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.
What to do
- Resolve the 47 End-of-life runtime finding(s) in Platform End-of-Life — start with Divstack.Estimation.Tool.Deployment.Infrastructure.csproj, Divstack.Company.Estimation.Tool.Bootstrapper.csproj, REDACTED. — One of this dimension's main actionable groups (47 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
- `SystemTime` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Now; e.g. `Now` at line 19). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/SystemTime.cs:8
What to do
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces Divstack.Company.Estimation.Tool.Users.Application.Authentication ↔ Divstack.Company.Estimation.Tool.Users.Application.Users.Queries.GetAllUsers depend on each other. The lightest dependency in the cycle is Divstack.Company.Estimation.Tool.Users.Application.Authentication → Divstack.Company.Estimation.Tool.Users.Application.Users.Queries.GetAllUsers (Divstack.Company.Estimation.Tool.Users.Application.Authentication.IUserManagementService → Divstack.Company.Estimation.Tool.Users.Application.Users.Queries.GetAllUsers.UserDto, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/IUserManagementService.cs:11
- The namespaces Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items.Services ↔ Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items.Services.Attributes depend on each other. The lightest dependency in the cycle is Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items.Services.Attributes → Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items.Services (Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items.Services.Attributes.Attribute → Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items.Services.Service, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Items/Services/Attributes/Attribute.cs:4
- The namespaces Divstack.Company.Estimation.Tool.Services.Core.Services ↔ Divstack.Company.Estimation.Tool.Services.Core.Services.Attributes ↔ Divstack.Company.Estimation.Tool.Services.Core.Services.Attributes.PossibleValues depend on each other. The lightest dependency in the cycle is Divstack.Company.Estimation.Tool.Services.Core.Services → Divstack.Company.Estimation.Tool.Services.Core.Services.Attributes (Divstack.Company.Estimation.Tool.Services.Core.Services.Service → Divstack.Company.Estimation.Tool.Services.Core.Services.Attributes.Attribute, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/Services/Service.cs:12
- The namespaces Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries ↔ Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items depend on each other. The lightest dependency in the cycle is Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries → Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items (Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Inquiry → Divstack.Company.Estimation.Tool.Inquiries.Domain.Inquiries.Items.InquiryItem, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Inquiry.cs:12
- The namespaces Divstack.Company.Estimation.Tool.Users.Domain.Users ↔ Divstack.Company.Estimation.Tool.Users.Domain.Users.Interfaces depend on each other. The lightest dependency in the cycle is Divstack.Company.Estimation.Tool.Users.Domain.Users.Interfaces → Divstack.Company.Estimation.Tool.Users.Domain.Users (Divstack.Company.Estimation.Tool.Users.Domain.Users.Interfaces.IPasswordComparer → Divstack.Company.Estimation.Tool.Users.Domain.Users.UserAccount, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/Interfaces/IPasswordComparer.cs:3
- The namespaces Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Passwords ↔ Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services depend on each other. The lightest dependency in the cycle is Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Passwords → Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services (Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Passwords.PasswordsManagementService → Divstack.Company.Estimation.Tool.Users.Infrastructure.Identity.Users.Services.ApplicationUserManager, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Passwords/PasswordsManagementService.cs:12
- The namespaces Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations ↔ Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Events ↔ Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals ↔ Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.Proposals.Events ↔ Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States depend on each other. The lightest dependency in the cycle is Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations → Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States (Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.IValuationsRepository → Divstack.Company.Estimation.Tool.Valuations.Domain.Valuations.States.ValuationRequested, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/IValuationsRepository.cs:5
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX7 · Slice cohesion
- `Startup` (slice 'Divstack.Company.Estimation.Tool.Bootstrapper') depends on `UsersModule` from slice 'Divstack.Company.Estimation.Tool.Users'. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:36
- `Startup` (slice 'Divstack.Company.Estimation.Tool.Bootstrapper') depends on `ServicesModule` from slice 'Divstack.Company.Estimation.Tool.Services'. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:37
- `Startup` (slice 'Divstack.Company.Estimation.Tool.Bootstrapper') depends on `InquiriesModule` from slice 'Divstack.Company.Estimation.Tool.Inquiries'. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:38
- `Startup` (slice 'Divstack.Company.Estimation.Tool.Bootstrapper') depends on `PaymentsModule` from slice 'Divstack.Company.Estimation.Tool.Payments'. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:39
- `Startup` (slice 'Divstack.Company.Estimation.Tool.Bootstrapper') depends on `ValuationModule` from slice 'Divstack.Company.Estimation.Tool.Valuations'. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:40
- `Startup` (slice 'Divstack.Company.Estimation.Tool.Bootstrapper') depends on `PrioritiesModule` from slice 'Divstack.Company.Estimation.Tool.Priorities'. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:41
- `Startup` (slice 'Divstack.Company.Estimation.Tool.Bootstrapper') depends on `RemindersModule` from slice 'Divstack.Company.Estimation.Tool.Reminders'. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:42
- `Startup` (slice 'Divstack.Company.Estimation.Tool.Bootstrapper') depends on `PushModule` from slice 'Divstack.Company.Estimation.Tool.Push'. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:44
- `Startup` (slice 'Divstack.Company.Estimation.Tool.Bootstrapper') depends on `EmailsModule` from slice 'Divstack.Company.Estimation.Tool.Emails'. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:45
- `Startup` (slice 'Divstack.Company.Estimation.Tool.Bootstrapper') depends on `SmsModule` from slice 'Divstack.Company.Estimation.Tool.Sms'. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:46
- `PaymentCompletedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `PaymentCompleted` from slice 'Divstack.Company.Estimation.Tool.Payments'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/PaymentCompletedEventHandler.cs:11
- `PaymentCompletedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `InquiryClientDto` from slice 'Divstack.Company.Estimation.Tool.Inquiries'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/PaymentCompletedEventHandler.cs:35
- `PaymentCompletedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `GetInquiryClientQuery` from slice 'Divstack.Company.Estimation.Tool.Inquiries'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/PaymentCompletedEventHandler.cs:37
- `PaymentInitializedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `PaymentInitialized` from slice 'Divstack.Company.Estimation.Tool.Payments'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/PaymentInitializedEventHandler.cs:11
- `PaymentInitializedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `InquiryClientDto` from slice 'Divstack.Company.Estimation.Tool.Inquiries'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/PaymentInitializedEventHandler.cs:36
- `PaymentInitializedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `GetInquiryClientQuery` from slice 'Divstack.Company.Estimation.Tool.Inquiries'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/PaymentInitializedEventHandler.cs:38
- `PriorityCloseToDeadlineRemindEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `PriorityCloseToDeadlineRemind` from slice 'Divstack.Company.Estimation.Tool.Reminders'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Priorities/DeadlineClose/PriorityCloseToDeadlineRemindEventHandler.cs:10
- `PriorityCloseToDeadlineRemindEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `GetUsersEmailsQuery` from slice 'Divstack.Company.Estimation.Tool.Users'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Priorities/DeadlineClose/PriorityCloseToDeadlineRemindEventHandler.cs:25
- `UserCreatedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `UserCreatedEvent` from slice 'Divstack.Company.Estimation.Tool.Users'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Users/ConfirmAccount/UserCreatedEventHandler.cs:9
- `ProposalApprovedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `ProposalApproved` from slice 'Divstack.Company.Estimation.Tool.Valuations'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Approved/ProposalApprovedEventHandler.cs:9
- `ProposalApprovedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `GetUserEmailQuery` from slice 'Divstack.Company.Estimation.Tool.Users'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Approved/ProposalApprovedEventHandler.cs:24
- `ProposalSuggestedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `ProposalSuggested` from slice 'Divstack.Company.Estimation.Tool.Valuations'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/ProposalSuggestedEventHandler.cs:10
- `ProposalSuggestedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `InquiryClientDto` from slice 'Divstack.Company.Estimation.Tool.Inquiries'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/ProposalSuggestedEventHandler.cs:37
- `ProposalSuggestedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Emails') depends on `GetInquiryClientQuery` from slice 'Divstack.Company.Estimation.Tool.Inquiries'. — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/ProposalSuggestedEventHandler.cs:39
- `InitializePaymentEventHandler` (slice 'Divstack.Company.Estimation.Tool.Payments') depends on `ValuationCompleted` from slice 'Divstack.Company.Estimation.Tool.Valuations'. — Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Application/Payments/Commands/Initalize/InitializePaymentEventHandler.cs:8
- `ArchivePriorityCommandCommandHandler` (slice 'Divstack.Company.Estimation.Tool.Priorities') depends on `ProposalSuggested` from slice 'Divstack.Company.Estimation.Tool.Valuations'. — Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/Priorities/Commands/Archive/ArchivePriorityCommandCommandHandler.cs:6
- `DefinePrioritiesEventHandler` (slice 'Divstack.Company.Estimation.Tool.Priorities') depends on `ValuationRequested` from slice 'Divstack.Company.Estimation.Tool.Valuations'. — Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/Priorities/Commands/Define/DefinePrioritiesEventHandler.cs:8
- `DefinePrioritiesEventHandler` (slice 'Divstack.Company.Estimation.Tool.Priorities') depends on `GetInquiryClientQuery` from slice 'Divstack.Company.Estimation.Tool.Inquiries'. — Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/Priorities/Commands/Define/DefinePrioritiesEventHandler.cs:37
- `RedefinePriorityCommandCommandHandler` (slice 'Divstack.Company.Estimation.Tool.Priorities') depends on `GetInquiryClientQuery` from slice 'Divstack.Company.Estimation.Tool.Inquiries'. — Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/Priorities/Commands/Redefine/RedefinePriorityCommandCommandHandler.cs:39
- `PaymentCompletedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Push') depends on `PaymentCompleted` from slice 'Divstack.Company.Estimation.Tool.Payments'. — Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Payments/Notifications/PaymentCompletedEventHandler.cs:12
- `PaymentCompletedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Push') depends on `GetAllUsersQuery` from slice 'Divstack.Company.Estimation.Tool.Users'. — Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Payments/Notifications/PaymentCompletedEventHandler.cs:29
- `ProposalApprovedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Push') depends on `ProposalApproved` from slice 'Divstack.Company.Estimation.Tool.Valuations'. — Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Valuations/Notifications/ProposalApprovedEventHandler.cs:10
- `ValuationRequestEventHandler` (slice 'Divstack.Company.Estimation.Tool.Push') depends on `ValuationRequested` from slice 'Divstack.Company.Estimation.Tool.Valuations'. — Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Valuations/Notifications/ValuationRequestEventHandler.cs:12
- `ValuationRequestEventHandler` (slice 'Divstack.Company.Estimation.Tool.Push') depends on `GetAllUsersQuery` from slice 'Divstack.Company.Estimation.Tool.Users'. — Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Valuations/Notifications/ValuationRequestEventHandler.cs:30
- `DeadlinesCloseReminderConfiguration` (slice 'Divstack.Company.Estimation.Tool.Reminders') depends on `Priority` from slice 'Divstack.Company.Estimation.Tool.Priorities'. — Src/Modules/Reminders/Divstack.Company.Estimation.Tool.Reminders.Priorities/DeadlineClose/Configuration/DeadlinesCloseReminderConfiguration.cs:12
- `PriorityCloseToDeadlineScheduler` (slice 'Divstack.Company.Estimation.Tool.Reminders') depends on `PriorityDefined` from slice 'Divstack.Company.Estimation.Tool.Priorities'. — Src/Modules/Reminders/Divstack.Company.Estimation.Tool.Reminders.Priorities/DeadlineClose/Scheduler/PriorityCloseToDeadlineScheduler.cs:9
- `PriorityCloseToDeadlineUnScheduler` (slice 'Divstack.Company.Estimation.Tool.Reminders') depends on `ProposalSuggested` from slice 'Divstack.Company.Estimation.Tool.Valuations'. — Src/Modules/Reminders/Divstack.Company.Estimation.Tool.Reminders.Priorities/DeadlineClose/Scheduler/PriorityCloseToDeadlineUnScheduler.cs:10
- `PriorityCloseToDeadlineUnScheduler` (slice 'Divstack.Company.Estimation.Tool.Reminders') depends on `ProposalCancelled` from slice 'Divstack.Company.Estimation.Tool.Valuations'. — Src/Modules/Reminders/Divstack.Company.Estimation.Tool.Reminders.Priorities/DeadlineClose/Scheduler/PriorityCloseToDeadlineUnScheduler.cs:11
- `PaymentCompletedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Sms') depends on `PaymentCompleted` from slice 'Divstack.Company.Estimation.Tool.Payments'. — Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Payments/Notifications/PaymentCompletedEventHandler.cs:9
- `PaymentCompletedEventHandler` (slice 'Divstack.Company.Estimation.Tool.Sms') depends on `GetInquiryClientQuery` from slice 'Divstack.Company.Estimation.Tool.Inquiries'. — Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Payments/Notifications/PaymentCompletedEventHandler.cs:23
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
AX8 · Test isolation
- `Divstack.Company.Estimation.Tool.Inquiries.Domain.Tests` (production) references the test project `Divstack.Company.Estimation.Tool.Shared.Testing`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — Src/Modules/Inquiries/Tests/Divstack.Company.Estimation.Tool.Inquiries.Domain.Tests/Divstack.Company.Estimation.Tool.Inquiries.Domain.Tests.csproj:13
- `Divstack.Company.Estimation.Tool.Priorities.Domain.Tests` (production) references the test project `Divstack.Company.Estimation.Tool.Shared.Testing`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — Src/Modules/Priorities/Tests/Divstack.Company.Estimation.Tool.Priorities.Domain.Tests/Divstack.Company.Estimation.Tool.Priorities.Domain.Tests.csproj:12
- `Divstack.Company.Estimation.Tool.Priorities.IntegrationTests` (production) references the test project `Divstack.Company.Estimation.Tool.Shared.Testing`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — Src/Modules/Priorities/Tests/Divstack.Company.Estimation.Tool.Priorities.IntegrationTests/Divstack.Company.Estimation.Tool.Priorities.IntegrationTests.csproj:9
- `Divstack.Company.Estimation.Tool.Services.IntegrationsTests` (production) references the test project `Divstack.Company.Estimation.Tool.Shared.Testing`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — Src/Modules/Services/Tests/Divstack.Company.Estimation.Tool.Services.IntegrationsTests/Divstack.Company.Estimation.Tool.Services.IntegrationsTests.csproj:14
- `Divstack.Company.Estimation.Tool.Users.Infrastructure.Tests` (production) references the test project `Divstack.Company.Estimation.Tool.Shared.Testing`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — Src/Modules/Users/Tests/Divstack.Company.Estimation.Tool.Users.Infrastructure.Tests/Divstack.Company.Estimation.Tool.Users.Infrastructure.Tests.csproj:7
- `Divstack.Company.Estimation.Tool.Valuations.Domain.Tests` (production) references the test project `Divstack.Company.Estimation.Tool.Shared.Testing`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain.Tests/Divstack.Company.Estimation.Tool.Valuations.Domain.Tests.csproj:13
- `Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks` ships in a production host and references `FluentAssertions`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. — REDACTED:4
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `UserCreatedEvent.UserPublicId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/CreateUser/UserCreatedEvent.cs:20
- `UserAccount.PublicId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/UserAccount.cs:34
- `Notification.ActionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.DataAccess/Entities/Notification.cs:8
- `Notification.ReceiverId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.DataAccess/Entities/Notification.cs:9
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
- `ValuationApproved` 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. — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationApproved.cs:7
- `ValuationCompleted` 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. — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationCompleted.cs:5
- `ValuationRequested` 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. — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationRequested.cs:6
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
- `Proposal` exposes publicly writable state (CancelledBy). — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/Proposals/Proposal.cs:5
- `ValuationApproved` exposes publicly writable state (Id). — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationApproved.cs:7
- `ValuationCompleted` exposes publicly writable state (Id). — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationCompleted.cs:5
- `ValuationNegotiation` exposes publicly writable state (Id). — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationNegotiation.cs:9
- `ValuationRequested` exposes publicly writable state (Id). — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationRequested.cs:6
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
- `InquiriesRepository` (domain layer) names `InquiriesContext` from `Divstack.Company.Estimation.Tool.Inquiries.Persistance.DataAccess` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/Domain/Inquiries/InquiriesRepository.cs:8, Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/Domain/Inquiries/InquiriesRepository.cs:10
- `InquiryEntityTypeConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/Domain/Inquiries/InquiryEntityTypeConfiguration.cs:13
- `InquiryEntityTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/Domain/Inquiries/InquiryEntityTypeConfiguration.cs:15
- `MongoMappingsExtensions` (domain layer) names `BsonMemberMap` from `MongoDB.Bson.Serialization` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/Extensions/MongoMappingsExtensions.cs:9, Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/Extensions/MongoMappingsExtensions.cs:9
- `MongoMappingsExtensions` (domain layer) names `GuidSerializer` from `MongoDB.Bson.Serialization.Serializers` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×2) — Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/Extensions/MongoMappingsExtensions.cs:11, Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/Extensions/MongoMappingsExtensions.cs:11
- `PaymentPersistanceConfiguration` (domain layer) names `BsonClassMap` from `MongoDB.Bson.Serialization` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×6) — Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/PaymentPersistanceConfiguration.cs:11, Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/PaymentPersistanceConfiguration.cs:20, Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/PaymentPersistanceConfiguration.cs:26, …
- `PrioritiesPersistanceConfiguration` (domain layer) names `BsonClassMap` from `MongoDB.Bson.Serialization` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×5) — Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/PrioritiesPersistanceConfiguration.cs:12, Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/PrioritiesPersistanceConfiguration.cs:25, Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/PrioritiesPersistanceConfiguration.cs:32, …
- `GetPrioritiesQueryHandler` (domain layer) names `Builders` from `MongoDB.Driver` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×2) — Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Queries/Handlers/GetPrioritiesQueryHandler.cs:25, Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Queries/Handlers/GetPrioritiesQueryHandler.cs:26
- `ApplicationRole` (domain layer) names `IdentityRole` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/ApplicationRole.cs:5
- `IPasswordComparer` (domain layer) names `UserAccount` from `Divstack.Company.Estimation.Tool.Users.Domain.Users` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/Interfaces/IPasswordComparer.cs:5
- `UserAccount` (domain layer) names `IdentityUser` from `Microsoft.AspNetCore.Identity` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/UserAccount.cs:10
- `ApplicationRoleEntityConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/ApplicationRoleEntityConfiguration.cs:7
- `ApplicationRoleEntityConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/ApplicationRoleEntityConfiguration.cs:9
- `IdentityRoleClaimsEntityConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/IdentityRoleClaimsEntityConfiguration.cs:7
- `IdentityRoleClaimsEntityConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/IdentityRoleClaimsEntityConfiguration.cs:9
- `IdentityTokenEntityTypeConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/IdentityTokenEntityTypeConfiguration.cs:7
- `IdentityTokenEntityTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/IdentityTokenEntityTypeConfiguration.cs:9
- `RefreshTokenConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/RefreshTokenConfiguration.cs:7
- `RefreshTokenConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/RefreshTokenConfiguration.cs:9
- `UserAccountEntityTypeConfiguration` (domain layer) names `IEntityTypeConfiguration` from `Microsoft.EntityFrameworkCore` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/UserAccountEntityTypeConfiguration.cs:7
- `UserAccountEntityTypeConfiguration` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/UserAccountEntityTypeConfiguration.cs:9
- `UserRepository` (domain layer) names `UsersContext` from `Divstack.Company.Estimation.Tool.Users.Persistance.DataAccess` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/UserRepository.cs:9, Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/UserRepository.cs:11
- `UserRepository` (domain layer) names `UserAccount` from `Divstack.Company.Estimation.Tool.Users.Domain.Users` — a persistence/infrastructure type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/UserRepository.cs:16
- `GetValuationsQueryHandler` (domain layer) names `IDocumentStore` from `Marten` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/Get/GetValuationsQueryHandler.cs:9, Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/Get/GetValuationsQueryHandler.cs:11
- `ValuationInformationAggregation` (domain layer) names `SingleStreamAggregation` from `Marten.Events.Aggregation` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/Domain/Valuations/Queries/Handlers/Get/ValuationInformationAggregation.cs:10
What to do
- Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM7 · Repository granularity
DM9 · Scattered domain decisions
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED3 · Event naming
- `PriorityCloseToDeadlineRemind` 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. — Src/Modules/Reminders/Divstack.Company.Estimation.Tool.Reminders.Priorities/DeadlineClose/Reminder/Events/PriorityCloseToDeadlineRemind.cs:5
What to do
- Name events in the past tense — they record facts that already happened.
ED4 · Outbox / dual-write
- `RequestValuationEventHandler.Handle` 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). — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Valuations/Commands/Request/RequestValuationEventHandler.cs:19
- `MakeInquiryCommandHandler.Handle` 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). — Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommandHandler.cs:33
- `InitializePaymentEventHandler.Handle` 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). — Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Application/Payments/Commands/Initalize/InitializePaymentEventHandler.cs:22
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
ES1 · Fold determinism
ES2 · Immutable events
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `AddApplicationModule` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×4) — Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Application/ApplicationModule.cs:7, Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/ApplicationModule.cs:7, Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/ApplicationModule.cs:11, …
- `UsePersistanceModule` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/PersistanceModule.cs:27
- `AddPayments` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Payments/PaymentsSmsModule.cs:11
- `UseDataAccess` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/DataAccess/DataAccessModule.cs:21
- `UseSignalr` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure.Signalr/SignalrModule.cs:11
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×2) — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ApiConsumer/CompanyFinderHttpClient.cs:23, Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ApiConsumer/CompanyFinderHttpClient.cs:28
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 63 of 63 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 4) — reach 8 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
- Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
What to do
- Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
P1 · CI/CD gates
P11 · BDD / executable specs
P2 · Observability
- Only 2/48 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 48, 1 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
- Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- `Deployment/Infrastructure/Divstack.Estimation.Tool.Deployment.Infrastructure.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Deployment/Infrastructure/Divstack.Estimation.Tool.Deployment.Infrastructure.csproj:11
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
- Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/SharedInfrastructureModule.cs:27
What to do
- Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
P8 · Schema migrations
P9 · Domain vs controller coverage
What to do
- Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
PF3 · Async & latency hygiene
- 5 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Seeder/UsersSeeder.cs:41
- `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×4) — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Utils/AsyncUtil.cs:24, Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Utils/AsyncUtil.cs:42, Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Utils/AsyncUtil.cs:15, …
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Web-Security Posture
- `ValidateLifetime = false` means expired tokens keep working indefinitely, so a leaked or revoked token never stops being valid. — REDACTED:50
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Program.cs:27
What to do
- Re-enable token validation — `ValidateLifetime` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×5) — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Seeder/UsersSeeder.cs:41, Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Utils/AsyncUtil.cs:21, Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Utils/AsyncUtil.cs:39, …
What to do
- Sync-over-async (deadlock risk)
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `_serviceScopeFactory.CreateScope()` (line 19) creates an `IServiceScope`, and it is bound to the local `serviceScope`, which this method only reads through and never disposes. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`. — Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Seeder/UsersSeederInitializer.cs:19
- `connection` is a `IDbConnection`, which implements `IDisposable`, and it is created here (line 15). Every use of it in `Handle` 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 connection = …;`), which releases it at the end of the scope on every path including a throw. (×2) — Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetAll/GetAllInquiriesQueryHandler.cs:15, Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetClient/GetInquiryClientQueryHandler.cs:15
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 106/188 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×39) — Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Core/Sender/EmailSender.cs:29, Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/ProposalSuggestedEventHandler.cs:37, Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/AttributesController.cs:22, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
- The guard on line 13 rejects `message` and line 14 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(message)` is true of a value that is NOT null: it is satisfied by an EMPTY `message`, and on that path `message` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/Proposals/ProposalDescription.cs:14
What to do
- Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
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.6 `!` suppressions per 1k syntax nodes — 44 suppression(s) across the 72251 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 | 66% | Adequate — gated by D17 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 43% | Weak — gated by AX7, AX8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 63% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 34% | Weak — gated by D12, D13, P5, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 61% | Adequate — gated by D28, D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 74% | Adequate — gated by DM6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event-Driven | 86% | Exemplary | Solid. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| 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.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.
Not included — 30 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.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D24 Comment Value — Too few judgeable comments (0 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — None of 4 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED5 Idempotency — not scored — 16 of 16 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES3 PII in the event store — This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- 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'.
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 157 finding(s)
- Domain depends on infrastructure: InquiriesRepository Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/Domain/Inquiries/InquiriesRepository.cs:8
- Domain depends on infrastructure: InquiriesRepository Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/Domain/Inquiries/InquiriesRepository.cs:10
- Domain depends on infrastructure: InquiryEntityTypeConfiguration Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/Domain/Inquiries/InquiryEntityTypeConfiguration.cs:13
- Domain depends on infrastructure: InquiryEntityTypeConfiguration Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/Domain/Inquiries/InquiryEntityTypeConfiguration.cs:15
- Domain depends on infrastructure: MongoMappingsExtensions Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/Extensions/MongoMappingsExtensions.cs:9
- Domain depends on infrastructure: MongoMappingsExtensions Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/Extensions/MongoMappingsExtensions.cs:11
- Domain depends on infrastructure: PaymentPersistanceConfiguration Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/PaymentPersistanceConfiguration.cs:11
- Domain depends on infrastructure: PaymentPersistanceConfiguration Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/PaymentPersistanceConfiguration.cs:20
- Domain depends on infrastructure: PaymentPersistanceConfiguration Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/PaymentPersistanceConfiguration.cs:26
- Domain depends on infrastructure: PaymentPersistanceConfiguration Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/PaymentPersistanceConfiguration.cs:32
- Domain depends on infrastructure: PaymentPersistanceConfiguration Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/PaymentPersistanceConfiguration.cs:38
- Domain depends on infrastructure: PaymentPersistanceConfiguration Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Domain/Payments/Configurations/PaymentPersistanceConfiguration.cs:42
- Domain depends on infrastructure: MongoMappingsExtensions Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/Extensions/MongoMappingsExtensions.cs:9
- Domain depends on infrastructure: MongoMappingsExtensions Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/Extensions/MongoMappingsExtensions.cs:11
- Domain depends on infrastructure: PrioritiesPersistanceConfiguration Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/PrioritiesPersistanceConfiguration.cs:12
- Domain depends on infrastructure: PrioritiesPersistanceConfiguration Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/PrioritiesPersistanceConfiguration.cs:25
- Domain depends on infrastructure: PrioritiesPersistanceConfiguration Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/PrioritiesPersistanceConfiguration.cs:32
- Domain depends on infrastructure: PrioritiesPersistanceConfiguration Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/PrioritiesPersistanceConfiguration.cs:37
- Domain depends on infrastructure: PrioritiesPersistanceConfiguration Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Configurations/PrioritiesPersistanceConfiguration.cs:43
- Domain depends on infrastructure: GetPrioritiesQueryHandler Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Queries/Handlers/GetPrioritiesQueryHandler.cs:25
- Domain depends on infrastructure: GetPrioritiesQueryHandler Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Domain/Priorities/Queries/Handlers/GetPrioritiesQueryHandler.cs:26
- Domain depends on infrastructure: ApplicationRole Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/ApplicationRole.cs:5
- Domain depends on infrastructure: IPasswordComparer Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/Interfaces/IPasswordComparer.cs:5
- Domain depends on infrastructure: UserAccount Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/UserAccount.cs:10
- Domain depends on infrastructure: ApplicationRoleEntityConfiguration Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Domain/Users/ApplicationRoleEntityConfiguration.cs:7
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/IUserManagementService.cs:11
- Namespace dependency cycle Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Items/Services/Attributes/Attribute.cs:4
- Namespace dependency cycle Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/Services/Service.cs:12
- Namespace dependency cycle Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Inquiry.cs:12
- Namespace dependency cycle Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/Interfaces/IPasswordComparer.cs:3
- Namespace dependency cycle Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Passwords/PasswordsManagementService.cs:12
- Namespace dependency cycle Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/IValuationsRepository.cs:5
- Production project references a test project: Divstack.Company.Estimation.Tool.Inquiries.Domain.Tests → Divstack.Company.Estimation.Tool.Shared.Testing Src/Modules/Inquiries/Tests/Divstack.Company.Estimation.Tool.Inquiries.Domain.Tests/Divstack.Company.Estimation.Tool.Inquiries.Domain.Tests.csproj:13
- Production project references a test project: Divstack.Company.Estimation.Tool.Priorities.Domain.Tests → Divstack.Company.Estimation.Tool.Shared.Testing Src/Modules/Priorities/Tests/Divstack.Company.Estimation.Tool.Priorities.Domain.Tests/Divstack.Company.Estimation.Tool.Priorities.Domain.Tests.csproj:12
- Production project references a test project: Divstack.Company.Estimation.Tool.Priorities.IntegrationTests → Divstack.Company.Estimation.Tool.Shared.Testing Src/Modules/Priorities/Tests/Divstack.Company.Estimation.Tool.Priorities.IntegrationTests/Divstack.Company.Estimation.Tool.Priorities.IntegrationTests.csproj:9
- Production project references a test project: Divstack.Company.Estimation.Tool.Services.IntegrationsTests → Divstack.Company.Estimation.Tool.Shared.Testing Src/Modules/Services/Tests/Divstack.Company.Estimation.Tool.Services.IntegrationsTests/Divstack.Company.Estimation.Tool.Services.IntegrationsTests.csproj:14
- Production project references a test project: Divstack.Company.Estimation.Tool.Users.Infrastructure.Tests → Divstack.Company.Estimation.Tool.Shared.Testing Src/Modules/Users/Tests/Divstack.Company.Estimation.Tool.Users.Infrastructure.Tests/Divstack.Company.Estimation.Tool.Users.Infrastructure.Tests.csproj:7
- Production project references a test project: Divstack.Company.Estimation.Tool.Valuations.Domain.Tests → Divstack.Company.Estimation.Tool.Shared.Testing Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain.Tests/Divstack.Company.Estimation.Tool.Valuations.Domain.Tests.csproj:13
- NoWarnInCsproj Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Divstack.Company.Estimation.Tool.Valuations.Domain.csproj:4
- NoWarnInCsproj Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Divstack.Company.Estimation.Tool.Valuations.Domain.csproj:12
- NoWarnInCsproj Directory.Build.props:10
- NoWarnInCsproj Directory.Build.props:10
- NoWarnInCsproj Directory.Build.props:10
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Layer violation: Application → Infrastructure Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/Divstack.Company.Estimation.Tool.Priorities.Application.csproj:11
- Layer violation: Domain → Infrastructure Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Core/Divstack.Company.Estimation.Tool.Sms.Core.csproj:27
- Layer violation: Application → Infrastructure Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Divstack.Company.Estimation.Tool.Users.Application.csproj:15
- Layer violation: Application → Infrastructure Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Divstack.Company.Estimation.Tool.Valuations.Application.csproj:26
- Dual write (no outbox): RequestValuationEventHandler.Handle Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Valuations/Commands/Request/RequestValuationEventHandler.cs:19
- Dual write (no outbox): MakeInquiryCommandHandler.Handle Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommandHandler.cs:33
- Dual write (no outbox): InitializePaymentEventHandler.Handle Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Application/Payments/Commands/Initalize/InitializePaymentEventHandler.cs:22
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Production project references a test package: Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks → FluentAssertions REDACTED:4
- FileScopedPragmaDisable repeated across 21 files Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommand.cs:1
- WriteOnlyPrivateField Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/ChangeUserPassword/ChangeUserPasswordCommand.cs:23
- REDACTED
Serious — 400 finding(s)
- Dead code: ProposalApprovedEventHandler Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Approved/ProposalApprovedEventHandler.cs:9
- Dead code: Attribute Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/Services/Attributes/PossibleValues/PossibleValue.cs:20
- Dead code: CategoryPersistanceConfiguration Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/Services/Categories/Configurations/PaymentPersistanceConfiguration.cs:6
- Dead code: UpdateCategoryRequest Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/Services/Categories/Dtos/UpdateCategoryRequest.cs:5
- Dead code: GetCurrentUserRoles Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/UserAccess/ICurrentUserService.cs:6
- Dead code: ResetPasswordRequest Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/Common/DTO/Authentication/ResetPasswordRequest.cs:5
- Dead code: ResetPasswordResponse Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/Common/DTO/Authentication/ResetPasswordResponse.cs:3
- Dead code: SignOutRequest Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/Common/DTO/Authentication/SignOutRequest.cs:3
- Dead code: SignOutResponse Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/Common/DTO/Authentication/SignOutResponse.cs:3
- Dead code: GetCurrentUserRoles Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/ICurrentUserService.cs:8
- Dead code: GenerateResetUserPasswordTokenAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/IPasswordsManagementService.cs:9
- Dead code: UpdateAssignedRolesAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/IUserManagementService.cs:15
- Dead code: AssignUserToRoleAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/IUserManagementService.cs:18
- Dead code: Customer Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Customers/Customer.cs:5
- Dead code: Employee Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Employees/Employee.cs:5
- Dead code: Id Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/FailedLoginAttempt.cs:19
- Dead code: Id Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/PasswordHistory.cs:22
- Dead code: GetChangedBy Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/ApplicationUserManager.cs:97
- Dead code: UsersContextFactory Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/DataAccess/UsersContextFactory.cs:5
- Dead code: Deconstruct Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Valuations/Queries/GetProposalsById/Dtos/ValuationProposalEntryDto.cs:36
- Dead code: Cancel Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/Proposals/Proposal.cs:64
- Dead code: When Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationApproved.cs:52
- Dead code: When Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationCompleted.cs:40
- Dead code: When Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationNegotiation.cs:128
- Dead code: When Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationRequested.cs:48
- End-of-life runtime: .NET net7.0 Deployment/Infrastructure/Divstack.Estimation.Tool.Deployment.Infrastructure.csproj:5
- End-of-life runtime: .NET net7.0 Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper.csproj:4
- End-of-life runtime: .NET net7.0 REDACTED:4
- End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Core/Divstack.Company.Estimation.Tool.Emails.Core.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/Divstack.Company.Estimation.Tool.Emails.Payments.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Priorities/Divstack.Company.Estimation.Tool.Emails.Priorities.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Users/Divstack.Company.Estimation.Tool.Emails.Users.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Divstack.Company.Estimation.Tool.Emails.Valuations.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails/Divstack.Company.Estimation.Tool.Emails.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Divstack.Company.Estimation.Tool.Inquiries.Domain.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.IntegrationsEvents/Divstack.Company.Estimation.Tool.Inquiries.IntegrationsEvents.csproj:4
- End-of-life runtime: .NET net7.0 REDACTED:4
- End-of-life runtime: .NET net7.0 Src/Modules/Inquiries/Tests/Divstack.Company.Estimation.Tool.Inquiries.IntegrationTests/Divstack.Company.Estimation.Tool.Inquiries.IntegrationTests.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Api/Divstack.Company.Estimation.Tool.Payments.Api.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Application/Divstack.Company.Estimation.Tool.Payments.Application.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Domain/Divstack.Company.Estimation.Tool.Payments.Domain.csproj:4
- End-of-life runtime: .NET net7.0 REDACTED:4
- End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Infrastructure/Divstack.Company.Estimation.Tool.Payments.Infrastructure.csproj:3
- End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.IntegrationsEvents/Divstack.Company.Estimation.Tool.Payments.IntegrationsEvents.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Divstack.Company.Estimation.Tool.Payments.Persistance.csproj:3
- End-of-life runtime: .NET net7.0 Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Api/Divstack.Company.Estimation.Tool.Priorities.Api.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Divstack.Company.Estimation.Tool.Priorities.Domain.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Divstack.Company.Estimation.Tool.Priorities.Infrastructure.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.IntegrationsEvents/Divstack.Company.Estimation.Tool.Priorities.IntegrationsEvents.csproj:4
- End-of-life runtime: .NET net7.0 Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Divstack.Company.Estimation.Tool.Priorities.Persistance.csproj:4
- CoverageExclusion Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Program.cs:11
- CoverageExclusion Src/Modules/Divstack.Company.Estimation.Tool.Push.Api/Notifications/Commands/MarkAllAsReadEndpoint.cs:7
- CoverageExclusion Src/Modules/Divstack.Company.Estimation.Tool.Push.Api/Notifications/Commands/MarkAsReadEndpoint.cs:7
- CoverageExclusion Src/Modules/Divstack.Company.Estimation.Tool.Push.Api/Notifications/NotificationsRouting.cs:5
- CoverageExclusion Src/Modules/Divstack.Company.Estimation.Tool.Push.Api/Notifications/Queries/GetNotReadEndpoint.cs:7
- CoverageExclusion Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Api/Common/UserAccess/CurrentUserService.cs:7
- CoverageExclusion Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Api/UserAccess/CurrentUserService.cs:7
- CoverageExclusion Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/CurrentUserService.cs:9
- CoverageExclusion Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Api/UserAccess/CurrentUserService.cs:7
- CoverageExclusion Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Api/Controllers/BaseController.cs:10
- CoverageExclusion Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/BaseController.cs:10
- CoverageExclusion Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/Common/Controllers/BaseController.cs:8
- CoverageExclusion REDACTED:9
- CoverageExclusion Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Api/FeatureFlags.cs:5
- CoverageExclusion Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Api/FeatureFlags.cs:5
- CoverageExclusion Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/FeatureFlags.cs:5
- CoverageExclusion Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Api/FeatureFlags.cs:5
- CoverageExclusion Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Api/PaymentsModule.cs:12
- CoverageExclusion Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Api/Common/Endpoints/Routing.cs:3
- CoverageExclusion Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Api/Priorities/Get.cs:7
- CoverageExclusion Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Api/Priorities/PrioritiesRouting.cs:5
- CoverageExclusion Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Api/PrioritiesModule.cs:13
- CoverageExclusion Src/Modules/Reminders/Divstack.Company.Estimation.Tool.Reminders.Priorities/PrioritiesModule.cs:10
- CoverageExclusion Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Domain/BackgroundProcesses/RedefinePrioritiesScheduler.cs:8
- CoverageExclusion Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/AttributesController.cs:8
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Bootstrapper → Divstack.Company.Estimation.Tool.Users Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:36
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Bootstrapper → Divstack.Company.Estimation.Tool.Services Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:37
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Bootstrapper → Divstack.Company.Estimation.Tool.Inquiries Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:38
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Bootstrapper → Divstack.Company.Estimation.Tool.Payments Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:39
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Bootstrapper → Divstack.Company.Estimation.Tool.Valuations Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:40
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Bootstrapper → Divstack.Company.Estimation.Tool.Priorities Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:41
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Bootstrapper → Divstack.Company.Estimation.Tool.Reminders Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:42
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Bootstrapper → Divstack.Company.Estimation.Tool.Push Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:44
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Bootstrapper → Divstack.Company.Estimation.Tool.Emails Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:45
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Bootstrapper → Divstack.Company.Estimation.Tool.Sms Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Startup.cs:46
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Payments Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/PaymentCompletedEventHandler.cs:11
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Inquiries Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/PaymentCompletedEventHandler.cs:35
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Inquiries Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/PaymentCompletedEventHandler.cs:37
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Payments Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/PaymentInitializedEventHandler.cs:11
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Inquiries Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/PaymentInitializedEventHandler.cs:36
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Inquiries Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/PaymentInitializedEventHandler.cs:38
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Reminders Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Priorities/DeadlineClose/PriorityCloseToDeadlineRemindEventHandler.cs:10
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Users Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Priorities/DeadlineClose/PriorityCloseToDeadlineRemindEventHandler.cs:25
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Users Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Users/ConfirmAccount/UserCreatedEventHandler.cs:9
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Valuations Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Approved/ProposalApprovedEventHandler.cs:9
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Users Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Approved/ProposalApprovedEventHandler.cs:24
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Valuations Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/ProposalSuggestedEventHandler.cs:10
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Inquiries Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/ProposalSuggestedEventHandler.cs:37
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Emails → Divstack.Company.Estimation.Tool.Inquiries Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/ProposalSuggestedEventHandler.cs:39
- Cross-slice coupling: Divstack.Company.Estimation.Tool.Payments → Divstack.Company.Estimation.Tool.Valuations Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Application/Payments/Commands/Initalize/InitializePaymentEventHandler.cs:8
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/SharedInfrastructureModule.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/SharedInfrastructureModule.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/HealthChecks/HealthChecksSharedModule.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/HealthChecks/HealthChecksSharedModule.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/EventBus/EventBusModule.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/EventBus/EventBusModule.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Data/SqlConnectionFactory.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Data/SqlConnectionFactory.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/BackgroundJobScheduler.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/BackgroundJobScheduler.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Extensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Extensions.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Storage/BackgroundJobsStorageExtensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Storage/BackgroundJobsStorageExtensions.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Dashboard/DashboardAuthorizationFilter.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Dashboard/DashboardAuthorizationFilter.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Configuration/BackgroundProcessingConfiguration.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/BackgroundProcessing/Configuration/BackgroundProcessingConfiguration.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/WebSockets/WebSocketsExtensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/WebSockets/WebSocketsExtensions.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/WebSockets/Configurations/WebSocketsConfiguration.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/WebSockets/Configurations/WebSocketsConfiguration.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Swagger/SwaggerAuthorizationExtensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Swagger/SwaggerAuthorizationExtensions.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Swagger/SwaggerModule.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Swagger/SwaggerModule.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Errors/ErrorTypes.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Errors/ErrorTypes.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Errors/Middleware/ErrorHandling.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Errors/Middleware/ErrorHandling.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Environments/EnvironmentExtensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Environments/EnvironmentExtensions.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Cors/CorsExtensions.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Cors/CorsExtensions.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Cors/Configurations/CorsConfiguration.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Cors/Configurations/CorsConfiguration.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Controllers/InternalControllersFeatureProvider.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Controllers/InternalControllersFeatureProvider.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/BusinessRuleValidationException.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/BusinessRuleValidationException.cs:1
- Low coverage: Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/ValueObject.cs Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/ValueObject.cs:1
- Low coverage: Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/UserAccess/CurrentUserService.cs Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/UserAccess/CurrentUserService.cs:1
- Low coverage: Src/Modules/Push/Divstack.Company.Estimation.Tool.Push/PushModule.cs Src/Modules/Push/Divstack.Company.Estimation.Tool.Push/PushModule.cs:1
- Low coverage: Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Events/PriorityArchivedDomainEvent.cs Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Events/PriorityArchivedDomainEvent.cs:1
- Low coverage: Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Events/PriorityForcedDomainEvent.cs Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Events/PriorityForcedDomainEvent.cs:1
- Async method without CancellationToken: SendMessageAsync Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Core/Sender/EmailSender.cs:29
- Async method without CancellationToken: GetClientInfo Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/ProposalSuggestedEventHandler.cs:37
- Async method without CancellationToken: CreateAttributeAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/AttributesController.cs:22
- Async method without CancellationToken: RemoveAttributeAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/AttributesController.cs:31
- Async method without CancellationToken: GetAllAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/CategoriesController.cs:20
- Async method without CancellationToken: CreateAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/CategoriesController.cs:30
- Async method without CancellationToken: DeleteAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/CategoriesController.cs:39
- Async method without CancellationToken: CreatePossibleValuesAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/PossibleValuesController.cs:20
- Async method without CancellationToken: RemovePossibleValuesAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/PossibleValuesController.cs:30
- Async method without CancellationToken: GetBatchAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/ServicesController.cs:27
- Async method without CancellationToken: GetAllAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/ServicesController.cs:35
- Async method without CancellationToken: Create Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/ServicesController.cs:45
- Async method without CancellationToken: DeleteAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Controllers/ServicesController.cs:54
- Async method without CancellationToken: ExistAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/Services/Contracts/ServiceExistingChecker.cs:16
- Async method without CancellationToken: ExistAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/Services/Contracts/ServiceExistingChecker.cs:23
- Async method without CancellationToken: CreateServiceAsync Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.DataAccess/Seeder/Services/ServicesSeeder.cs:48
- Async method without CancellationToken: SignIn Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/AuthenticationController.cs:22
- Async method without CancellationToken: GetAll Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/UsersController.cs:24
- Async method without CancellationToken: Get Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/UsersController.cs:37
- Async method without CancellationToken: Create Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/UsersController.cs:50
- Async method without CancellationToken: Delete Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/UsersController.cs:60
- Async method without CancellationToken: ChangeUserPassword Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/UsersController.cs:73
- Async method without CancellationToken: GenerateRefreshTokenAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Jwt/RefreshTokens/RefreshTokenGenerationService.cs:25
- Async method without CancellationToken: HasValidRefreshTokenAsync Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Jwt/RefreshTokens/RefreshTokenGenerationService.cs:35
- Async method without CancellationToken: SaveTokenInDb Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Jwt/RefreshTokens/RefreshTokenGenerationService.cs:54
- Deprecated: Microsoft.AspNetCore.Mvc Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Api/Divstack.Company.Estimation.Tool.Services.Api.csproj:9
- Deprecated: Microsoft.AspNetCore.Mvc Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Divstack.Company.Estimation.Tool.Users.Application.csproj:9
- Deprecated: Microsoft.AspNetCore.Mvc Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Api/Divstack.Company.Estimation.Tool.Valuations.Api.csproj:14
- Deprecated: Microsoft.AspNetCore.Mvc REDACTED:18
- Deprecated: Microsoft.AspNetCore.Mvc REDACTED:5
- Deprecated: IdentityServer4 REDACTED:4
- Deprecated: IdentityServer4.AccessTokenValidation REDACTED:5
- Deprecated: Microsoft.AspNetCore.Http.Abstractions REDACTED:7
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Infrastructure/Divstack.Company.Estimation.Tool.Valuations.Infrastructure.csproj:14
- Deprecated: Microsoft.AspNetCore.Http.Abstractions REDACTED:11
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Infrastructure.Trello/Divstack.Company.Estimation.Tool.Valuations.Infrastructure.Trello.csproj:5
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.csproj:9
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Infrastructure/Divstack.Company.Estimation.Tool.Payments.Infrastructure.csproj:16
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Divstack.Company.Estimation.Tool.Payments.Persistance.csproj:9
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Shared/Divstack.Company.Estimation.Tool.Shared.Persistance/Divstack.Company.Estimation.Tool.Shared.Persistance.csproj:4
- Deprecated: Microsoft.AspNetCore.Http.Abstractions REDACTED:9
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Push/Divstack.Company.Estimation.Tool.Push/Divstack.Company.Estimation.Tool.Push.csproj:10
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Valuations/Divstack.Company.Estimation.Tool.Push.Valuations.csproj:13
- Deprecated: Microsoft.AspNetCore.Http.Abstractions REDACTED:14
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.DataAccess/Divstack.Company.Estimation.Tool.Push.DataAccess.csproj:10
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.Payments/Divstack.Company.Estimation.Tool.Push.Payments.csproj:12
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Divstack.Company.Estimation.Tool.Priorities.Infrastructure.csproj:13
- Deprecated: Microsoft.AspNetCore.Http.Abstractions Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/Divstack.Company.Estimation.Tool.Priorities.Persistance.csproj:11
- Deprecated: Microsoft.AspNetCore.Http.Abstractions REDACTED:8
- Deprecated: Microsoft.AspNetCore.Mvc.Core Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Divstack.Company.Estimation.Tool.Valuations.Application.csproj:20
- Prerelease dependency: Pomelo.EntityFrameworkCore.MySql
- Prerelease dependency: Hangfire
- Prerelease dependency: MassTransit
- Prerelease dependency: MassTransit.Azure.ServiceBus.Core
- Prerelease dependency: Microsoft.Data.SqlClient
- Prerelease dependency: Hangfire.Core
- Prerelease dependency: Stripe.net
- Prerelease dependency: Azure.Identity
- Prerelease dependency: Microsoft.ApplicationInsights
- Prerelease dependency: Microsoft.ApplicationInsights.AspNetCore
- Prerelease dependency: Microsoft.FeatureManagement
- Prerelease dependency: SpecFlow.NUnit
- Prerelease dependency: Azure.Security.KeyVault.Secrets
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Sync-over-async blocking
- Sync-over-async blocking Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Seeder/UsersSeeder.cs:41
- Sync-over-async blocking Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Utils/AsyncUtil.cs:24
- Sync-over-async blocking Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Utils/AsyncUtil.cs:42
- Sync-over-async blocking Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Utils/AsyncUtil.cs:15
- Sync-over-async blocking Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Utils/AsyncUtil.cs:24
- Hollow method — returns a constant without doing the work Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Application/ApplicationModule.cs:7
- Hollow method — returns a constant without doing the work Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Application/ApplicationModule.cs:7
- Hollow method — returns a constant without doing the work Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Payments/PaymentsSmsModule.cs:11
- Hollow method — returns a constant without doing the work Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/ApplicationModule.cs:11
- Hollow method — returns a constant without doing the work Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/ApplicationModule.cs:9
- Sync-over-async (deadlock risk) Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Seeder/UsersSeeder.cs:41
- Sync-over-async (deadlock risk) Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Utils/AsyncUtil.cs:21
- Sync-over-async (deadlock risk) Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Utils/AsyncUtil.cs:39
- Sync-over-async (deadlock risk) Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Utils/AsyncUtil.cs:12
- Sync-over-async (deadlock risk) Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Utils/AsyncUtil.cs:21
- CommentedOutCode Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/AuthenticationController.cs:44
- CommentedOutCode Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ApiConsumer/CompanyFinderHttpClient.cs:10
- CommentedOutCode Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ApiConsumer/CompanyFinderHttpClient.cs:23
- CommentedOutCode Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ApiConsumer/CompanyFinderHttpClient.cs:40
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: Divstack.Company.Estimation.Tool.Services.Core Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/Divstack.Company.Estimation.Tool.Services.Core.csproj:1
- Off the main sequence: Divstack.Company.Estimation.Tool.Payments.IntegrationsEvents Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.IntegrationsEvents/Divstack.Company.Estimation.Tool.Payments.IntegrationsEvents.csproj:1
- Off the main sequence: Divstack.Company.Estimation.Tool.Inquiries.IntegrationsEvents Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.IntegrationsEvents/Divstack.Company.Estimation.Tool.Inquiries.IntegrationsEvents.csproj:1
- Off the main sequence: Divstack.Company.Estimation.Tool.Users.Domain Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Divstack.Company.Estimation.Tool.Users.Domain.csproj:1
- TodoComment Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/RoleManagementService.cs:28
- TodoComment Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ApiConsumer/CompanyFinderHttpClient.cs:22
- TodoComment Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ApiConsumer/CompanyFinderHttpClient.cs:39
- Anemic entity: ValuationApproved Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationApproved.cs:7
- Anemic entity: ValuationCompleted Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationCompleted.cs:5
- Anemic entity: ValuationRequested Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationRequested.cs:6
- Empty method body — does nothing with its inputs Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Persistance/PersistanceModule.cs:27
- Empty method body — does nothing with its inputs Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Persistance/DataAccess/DataAccessModule.cs:21
- Empty method body — does nothing with its inputs Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure.Signalr/SignalrModule.cs:11
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Migrations/Init_users_module.cs:104
- Duplicated block (8 lines × 2) Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/DataAccess/DataAccessModule.cs:20
- Duplicated block (16 lines × 2) Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Utils/AsyncUtil.cs:20
- Duplicated block (16 lines × 2) Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/DataAccess/DesignTimeDbContextFactoryBase.cs:31
- Disposable created and abandoned in the method that made it Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetAll/GetAllInquiriesQueryHandler.cs:15
- Disposable created and abandoned in the method that made it Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetClient/GetInquiryClientQueryHandler.cs:15
- Process-global static state: SystemTime Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/SystemTime.cs:8
- MethodTooLong: Init_users_module.Up Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Migrations/Init_users_module.cs:11
- REDACTED
- Duplicated block (15 lines × 2) Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs:133
- Duplicated block (5 lines × 2) Src/Modules/Divstack.Company.Estimation.Tool.Push.Api/Common/CurrentUser/CurrentUserService.cs:14
- Duplicated block (10 lines × 2) Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Api/PaymentsModule.cs:17
- Duplicated block (12 lines × 2) Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/Mediation/MediationModule.cs:13
- Duplicated block (7 lines × 2) Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/PersistanceModule.cs:15
- Unstable project Divstack.Company.Estimation.Tool.Emails.Valuations Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Divstack.Company.Estimation.Tool.Emails.Valuations.csproj:1
- Unstable project Divstack.Company.Estimation.Tool.Valuations.Infrastructure Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Infrastructure/Divstack.Company.Estimation.Tool.Valuations.Infrastructure.csproj:1
- Unstable project Divstack.Company.Estimation.Tool.Payments.Infrastructure Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Infrastructure/Divstack.Company.Estimation.Tool.Payments.Infrastructure.csproj:1
- Unstable project Divstack.Company.Estimation.Tool.Emails.Payments Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/Divstack.Company.Estimation.Tool.Emails.Payments.csproj:1
- Low cohesion: UserAccount (LCOM4 6) Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/UserAccount.cs:10
- No test project references Divstack.Estimation.Tool.Deployment.Infrastructure Deployment/Infrastructure/Divstack.Estimation.Tool.Deployment.Infrastructure.csproj
- No test project references Divstack.Company.Estimation.Tool.Shared.Infrastructure.Signalr Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure.Signalr/Divstack.Company.Estimation.Tool.Shared.Infrastructure.Signalr.csproj
- CRAP 56: InternalControllersFeatureProvider.IsController Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/Api/Controllers/InternalControllersFeatureProvider.cs:11
- No DR/backup evidence
- Outbound HTTP without resilience Src/Shared/Divstack.Company.Estimation.Tool.Shared.Infrastructure/SharedInfrastructureModule.cs:27
- Token validation disabled REDACTED:50
- NuGet dependencies are not locked
- DI scope created and never disposed Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Seeder/UsersSeederInitializer.cs:19
- Argument guard throws the exception its own condition disproves Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/Proposals/ProposalDescription.cs:14
Minor — 100 finding(s)
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Core/Divstack.Company.Estimation.Tool.Emails.Core.csproj:11
- Outdated: Microsoft.Extensions.Configuration.Abstractions Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Core/Divstack.Company.Estimation.Tool.Emails.Core.csproj:10
- Outdated: MediatR REDACTED:11
- Outdated: Microsoft.Extensions.Configuration.Binder Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/Divstack.Company.Estimation.Tool.Emails.Payments.csproj:25
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer REDACTED:17
- Outdated: Scrutor Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Priorities/Divstack.Company.Estimation.Tool.Emails.Priorities.csproj:20
- Outdated: AspNetCore.HealthChecks.MongoDb Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Persistance/Divstack.Company.Estimation.Tool.Payments.Persistance.csproj:15
- Outdated: Microsoft.Extensions.Configuration Src/Modules/Inquiries/Tests/Divstack.Company.Estimation.Tool.Inquiries.IntegrationTests/Divstack.Company.Estimation.Tool.Inquiries.IntegrationTests.csproj:18
- Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables REDACTED:21
- Outdated: Microsoft.Extensions.Configuration.FileExtensions Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.DataAccess/Divstack.Company.Estimation.Tool.Services.DataAccess.csproj:11
- Outdated: Microsoft.Extensions.Configuration.Json REDACTED:22
- Outdated: Microsoft.Extensions.Diagnostics.HealthChecks REDACTED:24
- Outdated: Microsoft.Extensions.Hosting.Abstractions REDACTED:17
- Outdated: Swashbuckle.AspNetCore Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Divstack.Company.Estimation.Tool.Users.Api.csproj:7
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Divstack.Company.Estimation.Tool.Users.Domain.csproj:9
- Outdated: Microsoft.Extensions.DependencyInjection Src/Modules/Inquiries/Tests/Divstack.Company.Estimation.Tool.Inquiries.IntegrationTests/Divstack.Company.Estimation.Tool.Inquiries.IntegrationTests.csproj:19
- Outdated: AspNetCore.HealthChecks.MySql REDACTED:25
- Outdated: Microsoft.EntityFrameworkCore Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Divstack.Company.Estimation.Tool.Users.Persistance.csproj:8
- Outdated: Microsoft.EntityFrameworkCore.Design REDACTED:11
- Outdated: Microsoft.EntityFrameworkCore.Relational REDACTED:15
- Outdated: Swashbuckle.AspNetCore.Annotations REDACTED:21
- Outdated: DotNetCore.CAP Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Application/Divstack.Company.Estimation.Tool.Valuations.Application.csproj:15
- Outdated: AspNetCore.HealthChecks.NpgSql REDACTED:8
- Outdated: Marten REDACTED:10
- Outdated: Microsoft.Extensions.Configuration.UserSecrets REDACTED:16
- Orphaned file Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Persistance/Migrations/Init_users_module.cs:1
- Orphaned file Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/UserManagementService.cs:1
- Orphaned file Deployment/Infrastructure/Resources/ContainerApp/ContainerAppCreator.cs:1
- Orphaned file Src/Modules/Services/Divstack.Company.Estimation.Tool.Services.Core/Services/Services/ServicesService.cs:1
- Orphaned file Deployment/Infrastructure/Resources/AppConfiguration/AppConfigurationKeys.cs:1
- Orphaned file Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Passwords/PasswordsManagementService.cs:1
- Orphaned file Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationNegotiation.cs:1
- Orphaned file Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/UserAccount.cs:1
- Orphaned file Deployment/Infrastructure/Resources/AppConfiguration/AppConfigurationCreator.cs:1
- Orphaned file Deployment/Infrastructure/Resources/KeyVault/SecuredKeyValueCreator.cs:1
- Orphaned file Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/ApplicationUserManager.cs:1
- Orphaned file REDACTED:1
- Orphaned file Src/Shared/Testing/Divstack.Comapany.Estimation.Tool.Shared.Testing.Application.IntegrationsTests/Testing.cs:1
- Orphaned file Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/Domain/Inquiries/InquiryEntityTypeConfiguration.cs:1
- Orphaned file Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Services/SignInManagementService.cs:1
- Orphaned file Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/Sender/ValuationProposalSuggestedMailSender.cs:1
- Orphaned file Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/AuthenticationController.cs:1
- Orphaned file Src/Modules/Sms/Divstack.Company.Estimation.Tool.Sms.Valuations/Notifications/Proposals/ProposalSuggested/ProposalSuggestedSmsNotificationHandler.cs:1
- Orphaned file Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.BuildingBlocks/ValueObject.cs:1
- Orphaned file REDACTED:1
- Orphaned file Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/Commands/SignIn/SignInCommand.cs:1
- Orphaned file Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Domain/Priority.cs:1
- Orphaned file Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Jwt/RefreshTokens/RefreshTokenGenerationService.cs:1
- Orphaned file Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/Get/GetInquiriesQueryHandler.cs:1
- Orphaned file Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/UsersController.cs:1
- Mutable entity: Proposal Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/Proposals/Proposal.cs:5
- Mutable entity: ValuationApproved Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationApproved.cs:7
- Mutable entity: ValuationCompleted Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationCompleted.cs:5
- Mutable entity: ValuationNegotiation Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationNegotiation.cs:9
- Mutable entity: ValuationRequested Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Domain/Valuations/States/ValuationRequested.cs:6
- Pass-through layer Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/UserModule.cs:7
- Pass-through layer Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Valuations.Infrastructure/ValuationsModule.cs:6
- Pass-through layer Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Infrastructure/PaymentsModule.cs:6
- Pass-through layer Src/Modules/Priorities/Divstack.Company.Estimation.Tool.Priorities.Infrastructure/PrioritiesModule.cs:6
- Primitive id on a domain type: UserCreatedEvent.UserPublicId Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/CreateUser/UserCreatedEvent.cs:20
- Primitive id on a domain type: UserAccount.PublicId Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/UserAccount.cs:34
- Primitive id on a domain type: Notification.ActionId Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.DataAccess/Entities/Notification.cs:8
- Primitive id on a domain type: Notification.ReceiverId Src/Modules/Push/Divstack.Company.Estimation.Tool.Push.DataAccess/Entities/Notification.cs:9
- Commented-out code Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ApiConsumer/CompanyFinderHttpClient.cs:23
- Commented-out code Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ApiConsumer/CompanyFinderHttpClient.cs:28
- No security response headers detected
- No security response headers detected Src/Bootstrapper/Divstack.Company.Estimation.Tool.Bootstrapper/Program.cs:27
- Partial data-retention evidence
- Documentation: no build, run or usage example README.md:1
- REDACTED
- REDACTED
- Dormant codebase
- IL efficiency: 2 authored method(s) exceed the IL budget Deployment/Infrastructure/Resources/ContainerApp/ContainerAppCreator.cs:22
- Event not named in past tense: PriorityCloseToDeadlineRemind Src/Modules/Reminders/Divstack.Company.Estimation.Tool.Reminders.Priorities/DeadlineClose/Reminder/Events/PriorityCloseToDeadlineRemind.cs:5
- No tests/ separation
- Logging is not universal
- No dependency-update automation Deployment/Infrastructure/Divstack.Estimation.Tool.Deployment.Infrastructure.csproj:11
- No rollback/health safety
- No changelog
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
- Silent fallback default in catch Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects/Emails/Email.cs:40
Minor — 67 finding(s)
- Outdated: SendGrid
- Outdated: Ardalis.GuardClauses
- Outdated: MediatR.Extensions.Microsoft.DependencyInjection
- Outdated: Microsoft.AspNetCore.Mvc
- Outdated: Newtonsoft.Json
- Outdated: MongoDB.Bson
- Outdated: MongoDB.Driver
- Outdated: Dapper
- Outdated: FluentValidation
- Outdated: FluentValidation.DependencyInjectionExtensions
- Outdated: MailKit
- Outdated: Microsoft.AspNetCore.Http.Abstractions
- Outdated: MimeKit
- Outdated: Pomelo.EntityFrameworkCore.MySql
- Outdated: Ardalis.ApiEndpoints
- Outdated: Azure.Messaging.ServiceBus
- Outdated: Microsoft.AspNetCore.Mvc.Core
- Outdated: MediatR.Extensions.FluentValidation.AspNetCore
- Outdated: JetBrains.Annotations
- Outdated: FluentAssertions
- Outdated: NServiceBus
- Outdated: Hangfire
- Outdated: Hangfire.InMemory
- Outdated: Hangfire.Mongo
- Outdated: MassTransit
- Mock framework: Moq
- Mock framework: Moq
- Mock framework: Moq
- Mock framework: NSubstitute
- Mock framework: Moq
- Mock framework: Moq
- Off the main sequence: Divstack.Company.Estimation.Tool.Shared.Infrastructure.Azure REDACTED:1
- Off the main sequence: Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects Src/Shared/Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects/Divstack.Company.Estimation.Tool.Shared.DDD.ValueObjects.csproj:1
- Inquiries: 2 contract type(s) expose producer-owned ids/enums
- Payments: 2 contract type(s) expose producer-owned ids/enums
- Priorities: 4 contract type(s) expose producer-owned ids/enums
- Valuations: 6 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-a680fa2eb2e5483ebab824887ff08363/history.json --exit-code 0 --source . | 9 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a680fa2eb2e5483ebab824887ff08363/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Persistance/Migrations . | 43 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Divstack.Company.Estimation.Tool.sln package --vulnerable --include-transitive --format json | 28 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 8 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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-357c27ab06ab4ad7aadf15a40cbe2a6e | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 39 field(s)
- PaymentCompletedEmailRequest.FirstName Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/Sender/PaymentCompletedEmailRequest.cs:4
- PaymentCompletedEmailRequest.LastName Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/Sender/PaymentCompletedEmailRequest.cs:5
- PaymentCompletedEmailRequest.ClientFullName Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/Sender/PaymentCompletedEmailRequest.cs:9
- PaymentInitializedEmailRequest.FirstName Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/Sender/PaymentInitializedEmailRequest.cs:4
- PaymentInitializedEmailRequest.LastName Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/Sender/PaymentInitializedEmailRequest.cs:5
- PaymentInitializedEmailRequest.ClientFullName Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/Sender/PaymentInitializedEmailRequest.cs:12
- ValuationProposalSuggestedEmailRequest.FullName Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/Sender/ValuationProposalSuggestedEmailRequest.cs:7
- MakeInquiryCommand.FirstName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommand.cs:9
- MakeInquiryCommand.LastName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommand.cs:10
- InquiryInformationDto.FirstName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/Get/Dtos/InquiryInformationDto.cs:17
- InquiryInformationDto.LastName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/Get/Dtos/InquiryInformationDto.cs:18
- InquiryInformationDto.FullName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/Get/Dtos/InquiryInformationDto.cs:21
- InquiryListItemDto.FirstName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetAll/InquiryListItemDto.cs:15
- InquiryListItemDto.LastName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetAll/InquiryListItemDto.cs:16
- InquiryListItemDto.FullName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetAll/InquiryListItemDto.cs:17
- InquiryClientDto.FirstName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetClient/Dtos/InquiryClientDto.cs:3
- InquiryClientDto.LastName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetClient/Dtos/InquiryClientDto.cs:3
- InquiryClientDto.FullName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetClient/Dtos/InquiryClientDto.cs:14
- Client.FullName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Clients/Client.cs:24
- Client.FirstName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Clients/Client.cs:25
- Client.LastName Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Clients/Client.cs:26
- UpdateUserDto.FirstName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/DTOs/UpdateUserDto.cs:9
- UpdateUserDto.LastName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/DTOs/UpdateUserDto.cs:10
- UserDetailsDto.FirstName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/DTOs/UserDetailsDto.cs:8
- UserDetailsDto.LastName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/DTOs/UserDetailsDto.cs:9
- CreateUserCommand.FirstName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/CreateUser/CreateUserCommand.cs:6
- CreateUserCommand.LastName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/CreateUser/CreateUserCommand.cs:6
- CreateUserRequest.FirstName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/CreateUser/Requests/CreateUserRequest.cs:14
- CreateUserRequest.LastName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/CreateUser/Requests/CreateUserRequest.cs:15
- UserDto.FirstName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Queries/GetAllUsers/UserDto.cs:6
- UserDto.LastName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Queries/GetAllUsers/UserDto.cs:7
- UserDetailVm.FirstName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Queries/GetUser/UserDetailVm.cs:5
- UserDetailVm.LastName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Queries/GetUser/UserDetailVm.cs:5
- Customer.FirstName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Customers/Customer.cs:15
- Customer.LastName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Customers/Customer.cs:16
- Employee.FirstName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Employees/Employee.cs:15
- Employee.LastName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Employees/Employee.cs:16
- UserAccount.FirstName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/UserAccount.cs:35
- UserAccount.LastName Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Domain/Users/UserAccount.cs:36
Email — 21 field(s)
- PaymentCompletedEmailRequest.ClientEmail Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentCompleted/Sender/PaymentCompletedEmailRequest.cs:6
- PaymentInitializedEmailRequest.ClientEmail Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Payments/PaymentInitialized/Sender/PaymentInitializedEmailRequest.cs:8
- PriorityCloseToDeadlineEmailRequest.EmployeeEmail Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Priorities/DeadlineClose/Sender/PriorityCloseToDeadlineEmailRequest.cs:5
- ValuationProposalApprovedEmailRequest.SuggestedByEmployeeEmail Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Approved/Sender/ValuationProposalApprovedEmailRequest.cs:4
- ValuationProposalSuggestedEmailRequest.Email Src/Modules/Emails/Divstack.Company.Estimation.Tool.Emails.Valuations/Proposals/Suggested/Sender/ValuationProposalSuggestedEmailRequest.cs:8
- MakeInquiryCommand.Email Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommand.cs:11
- InquiryInformationDto.Email Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/Get/Dtos/InquiryInformationDto.cs:19
- InquiryClientDto.Email Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetClient/Dtos/InquiryClientDto.cs:3
- Client.Email Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Clients/Client.cs:22
- SignInRequest.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Api/Controllers/Common/DTO/Authentication/SignInRequest.cs:17
- UpdateUserDto.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/DTOs/UpdateUserDto.cs:8
- UserDetailsDto.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Authentication/DTOs/UserDetailsDto.cs:7
- CreateUserCommand.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/CreateUser/CreateUserCommand.cs:6
- CreateUserRequest.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/CreateUser/Requests/CreateUserRequest.cs:17
- UserCreatedEvent.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Commands/CreateUser/UserCreatedEvent.cs:21
- UserDto.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Queries/GetAllUsers/UserDto.cs:9
- UserDetailVm.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Queries/GetUser/UserDetailVm.cs:5
- UserAccountDto.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Application/Users/Queries/GetUserByUsername/UserAccountDto.cs:16
- AdminAccountConfiguration.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Configuration/AdminAccountConfiguration.cs:20
- IAdminAccountConfiguration.Email Src/Modules/Users/Divstack.Company.Estimation.Tool.Users.Infrastructure/Identity/Users/Configuration/IAdminAccountConfiguration.cs:7
- FindProfileRequest.Email Src/Modules/Valuations/Divstack.Company.Estimation.Tool.Inquiries.Infrastructure.Snov/FindClientCompany/ApiConsumer/Requests/FindProfileRequest.cs:3
Phone — 3 field(s)
- MakeInquiryCommand.PhoneNumber Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Commands/Make/MakeInquiryCommand.cs:12
- InquiryClientDto.PhoneNumber Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Application/Inquiries/Queries/GetClient/Dtos/InquiryClientDto.cs:3
- Client.PhoneNumber Src/Modules/Inquiries/Divstack.Company.Estimation.Tool.Inquiries.Domain/Inquiries/Clients/Client.cs:23
Financial (card / IBAN) — 1 field(s)
- CreditCardDto.CardNumber Src/Modules/Payments/Divstack.Company.Estimation.Tool.Payments.Application/Payments/Commands/Pay/Dtos/CreditCard/CreditCardDto.cs:3