Executive summary
onebeyond/onebeyond-studio-obelisk is rated At risk because critical security findings are open. Its score is held back because 33 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 62 out of 100, which the At risk rating leaves unchanged.
Maturity, at 57, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4 points. Replacing the four exposed passwords or keys and switching the old ones off comes next, worth about 2 points. Raising Maturity to 70 would lift the score to about 64.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven settings leave the servers or containers unsafe, and five known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, correcting the unsafe settings and updating the vulnerable packages would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the four passwords or keys in the code and the three passwords or keys in the code's history need replacing, with the old ones switched off. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 6,960 lines, about €13,000 to rebuild.
If Maturity rose from 57 to 70, the lowest score rated Strong, the score would rise from 62 to about 64.
New since the last survey: 5 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
Fixed since the last survey: 16 findings
- Dependency Hygiene · Vulnerable: OpenTelemetry.Exporter.OpenTelemetryProtocol
- Boundary Type-Coupling · Cross-context type AmbientContext (OneBeyond.Studio.Obelisk → OneBeyond.Studio.Obelisk.WebApi) REDACTED
- Boundary Type-Coupling · Cross-context type WhoAmIDto (OneBeyond.Studio.Obelisk → OneBeyond.Studio.Obelisk.WebApi) REDACTED
- Boundary Type-Coupling · Cross-context type SignInResult (OneBeyond.Studio.Obelisk.Authentication → OneBeyond.Studio.Obelisk.WebApi) REDACTED
- Boundary Type-Coupling · Cross-context type SignInViaPassword (OneBeyond.Studio.Obelisk.Authentication → OneBeyond.Studio.Obelisk.WebApi) REDACTED
- Boundary Type-Coupling · Cross-context type SignInResult (OneBeyond.Studio.Obelisk.Authentication → OneBeyond.Studio.Obelisk.WebApi) REDACTED
- Boundary Type-Coupling · Cross-context type SignInWithRecoveryCodeResult (OneBeyond.Studio.Obelisk.Authentication → OneBeyond.Studio.Obelisk.WebApi) REDACTED
- Boundary Type-Coupling · Cross-context type SignInTfaWithRecoveryCode (OneBeyond.Studio.Obelisk.Authentication → OneBeyond.Studio.Obelisk.WebApi) REDACTED
- Boundary Type-Coupling · Cross-context type ResetPasswordStatus (OneBeyond.Studio.Obelisk.Authentication → OneBeyond.Studio.Obelisk.WebApi) REDACTED
- Boundary Type-Coupling · Cross-context type ChangePasswordResult (OneBeyond.Studio.Obelisk.Authentication → OneBeyond.Studio.Obelisk.WebApi) REDACTED
- Boundary Type-Coupling · Cross-context type AmbientContext (OneBeyond.Studio.Obelisk → OneBeyond.Studio.Obelisk.WebApi) REDACTED
- Boundary Type-Coupling · Cross-context type AmbientContext (OneBeyond.Studio.Obelisk → OneBeyond.Studio.Obelisk.WebApi) src/OneBeyond.Studio.Obelisk.WebApi/Controllers/TFAController.cs
- Boundary Type-Coupling · Cross-context type LoginTfaSettings (OneBeyond.Studio.Obelisk.Authentication → OneBeyond.Studio.Obelisk.WebApi) src/OneBeyond.Studio.Obelisk.WebApi/Controllers/TFAController.cs
- Boundary Type-Coupling · Cross-context type TfaAuthenticatorSettings (OneBeyond.Studio.Obelisk.Authentication → OneBeyond.Studio.Obelisk.WebApi) src/OneBeyond.Studio.Obelisk.WebApi/Controllers/TFAController.cs
- Boundary Type-Coupling · Cross-context type CreateUserDto (OneBeyond.Studio.Obelisk → OneBeyond.Studio.Obelisk.WebApi) src/OneBeyond.Studio.Obelisk.WebApi/Controllers/UsersController.cs
- Boundary Type-Coupling · Cross-context type UpdateUser (OneBeyond.Studio.Obelisk → OneBeyond.Studio.Obelisk.WebApi) src/OneBeyond.Studio.Obelisk.WebApi/Controllers/UsersController.cs
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,200 to €21,000, for 70 to 222 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 62. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,960 lines of product code, of which 49% is declarations and boilerplate, 35% straight logic and 16% logic with branches |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Application.Features.Users.Dto | 2 Application.Features.Users.Queries | 3 Application.Repositories | 4 Application.Services.AmbientContexts | 5 Authentication.Application.Entities | 6 Authentication.Application.Repositories.AuthUsers | 7 Authentication.Application.Services.ApplicationClaims | 8 Authentication.Domain | 9 Authentication.Domain.Exceptions | 10 Authentication.Domain.JwtAuthentication | 11 Domain.Features.EmailTemplates.Entities | 12 Domain.Features.Users.Commands | 13 WebApi.Requests | 14 Application.Services.EmailTemplateService | 15 Authentication.Application.JwtAuthentication | 16 Authentication.Application.Services.JwtAuthentication | 17 Authentication.Domain.AuthenticationFlows | 18 Authentication.Domain.Commands | 19 Authentication.Domain.Queries | 20 Authentication.Domain.TfaAuthentication | 21 Domain.Features.Users.Entities | 22 Infrastructure.Data.BulkUpdate | 23 Application.Features.Users.CommandHandlers | 24 Application.Features.Users.DomainEventHandlers | 25 Application.Features.Users.Predicates | 26 Application.Features.Users.QueryHandlers | 27 Application.Services.AuthenticationFlows | 28 Authentication.Application.CommandHandlers | 29 Authentication.Application.JwtAuthentication.CommandHandlers | 30 Authentication.Application.QueryHandlers | 31 Authentication.Application.TfaAuthentication.QueryHandlers | 32 Authentication.Domain.TfaAuthentication.Commands | 33 Infrastructure.Data | 34 Infrastructure.Data.EmailTemplates.Projections | 35 Infrastructure.Data.Users.Projections | 36 WebApi.AmbientContexts | 37 Authentication.Application.TfaAuthentication.CommandHandlers | 38 Infrastructure.Data.AuthUsers.Repositories | 39 Infrastructure.Data.Seeding | 40 WebApi.Controllers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Application.Features.Users.Dto | ||||||||||||||||||||||||||||||||||||||||
| 2 Application.Features.Users.Queries | ||||||||||||||||||||||||||||||||||||||||
| 3 Application.Repositories | ||||||||||||||||||||||||||||||||||||||||
| 4 Application.Services.AmbientContexts | ||||||||||||||||||||||||||||||||||||||||
| 5 Authentication.Application.Entities | ||||||||||||||||||||||||||||||||||||||||
| 6 Authentication.Application.Repositories.AuthUsers | ||||||||||||||||||||||||||||||||||||||||
| 7 Authentication.Application.Services.ApplicationClaims | ||||||||||||||||||||||||||||||||||||||||
| 8 Authentication.Domain | ||||||||||||||||||||||||||||||||||||||||
| 9 Authentication.Domain.Exceptions | ||||||||||||||||||||||||||||||||||||||||
| 10 Authentication.Domain.JwtAuthentication | ||||||||||||||||||||||||||||||||||||||||
| 11 Domain.Features.EmailTemplates.Entities | ||||||||||||||||||||||||||||||||||||||||
| 12 Domain.Features.Users.Commands | ||||||||||||||||||||||||||||||||||||||||
| 13 WebApi.Requests | ||||||||||||||||||||||||||||||||||||||||
| 14 Application.Services.EmailTemplateService | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 Authentication.Application.JwtAuthentication | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 Authentication.Application.Services.JwtAuthentication | 2 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 17 Authentication.Domain.AuthenticationFlows | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Authentication.Domain.Commands | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 Authentication.Domain.Queries | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Authentication.Domain.TfaAuthentication | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Domain.Features.Users.Entities | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 Infrastructure.Data.BulkUpdate | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Application.Features.Users.CommandHandlers | 4 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 24 Application.Features.Users.DomainEventHandlers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Application.Features.Users.Predicates | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Application.Features.Users.QueryHandlers | 2 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 27 Application.Services.AuthenticationFlows | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 28 Authentication.Application.CommandHandlers | 12 | 8 | 3 | 11 | ||||||||||||||||||||||||||||||||||||
| 29 Authentication.Application.JwtAuthentication.CommandHandlers | 4 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 Authentication.Application.QueryHandlers | 3 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 31 Authentication.Application.TfaAuthentication.QueryHandlers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 Authentication.Domain.TfaAuthentication.Commands | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Infrastructure.Data | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 34 Infrastructure.Data.EmailTemplates.Projections | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 Infrastructure.Data.Users.Projections | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 WebApi.AmbientContexts | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 Authentication.Application.TfaAuthentication.CommandHandlers | 7 | 1 | 2 | 7 | ||||||||||||||||||||||||||||||||||||
| 38 Infrastructure.Data.AuthUsers.Repositories | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 Infrastructure.Data.Seeding | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 WebApi.Controllers | 2 | 4 | 3 | 1 | 1 | 1 | 1 | 3 | 2 |
14→11 Application.Services.EmailTemplateService uses Domain.Features.EmailTemplates.Entities✕
- Connections
- 1 pair of types, where a type in Application.Services.EmailTemplateService uses a type in Domain.Features.EmailTemplates.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Application.Services.EmailTemplateService.EmailTemplateService→OneBeyond.Studio.Obelisk.Domain.Features.EmailTemplates.Entities.EmailTemplate
- Direction
- Application.Services.EmailTemplateService uses Domain.Features.EmailTemplates.Entities, so a change to Domain.Features.EmailTemplates.Entities can break Application.Services.EmailTemplateService, while a change to Application.Services.EmailTemplateService can't break Domain.Features.EmailTemplates.Entities.
- Position
- Below the diagonal: Application.Services.EmailTemplateService uses a module listed above it, which is the healthy direction.
15→5 Authentication.Application.JwtAuthentication uses Authentication.Application.Entities✕
- Connections
- 1 pair of types, where a type in Authentication.Application.JwtAuthentication uses a type in Authentication.Application.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.TokenGenerator→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUser
- Direction
- Authentication.Application.JwtAuthentication uses Authentication.Application.Entities, so a change to Authentication.Application.Entities can break Authentication.Application.JwtAuthentication, while a change to Authentication.Application.JwtAuthentication can't break Authentication.Application.Entities.
- Position
- Below the diagonal: Authentication.Application.JwtAuthentication uses a module listed above it, which is the healthy direction.
15→10 Authentication.Application.JwtAuthentication uses Authentication.Domain.JwtAuthentication✕
- Connections
- 1 pair of types, where a type in Authentication.Application.JwtAuthentication uses a type in Authentication.Domain.JwtAuthentication.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.TokenGenerator→OneBeyond.Studio.Obelisk.Authentication.Domain.JwtAuthentication.JwtAuthenticationOptions
- Direction
- Authentication.Application.JwtAuthentication uses Authentication.Domain.JwtAuthentication, so a change to Authentication.Domain.JwtAuthentication can break Authentication.Application.JwtAuthentication, while a change to Authentication.Application.JwtAuthentication can't break Authentication.Domain.JwtAuthentication.
- Position
- Below the diagonal: Authentication.Application.JwtAuthentication uses a module listed above it, which is the healthy direction.
16→5 Authentication.Application.Services.JwtAuthentication uses Authentication.Application.Entities✕
- Connections
- 2 pairs of types, where a type in Authentication.Application.Services.JwtAuthentication uses a type in Authentication.Application.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.Services.JwtAuthentication.IJwtTokenService→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.Services.JwtAuthentication.JwtTokenService→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUser
- Direction
- Authentication.Application.Services.JwtAuthentication uses Authentication.Application.Entities, so a change to Authentication.Application.Entities can break Authentication.Application.Services.JwtAuthentication, while a change to Authentication.Application.Services.JwtAuthentication can't break Authentication.Application.Entities.
- Position
- Below the diagonal: Authentication.Application.Services.JwtAuthentication uses a module listed above it, which is the healthy direction.
16→6 Authentication.Application.Services.JwtAuthentication uses Authentication.Application.Repositories.AuthUsers✕
- Connections
- 1 pair of types, where a type in Authentication.Application.Services.JwtAuthentication uses a type in Authentication.Application.Repositories.AuthUsers.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.Services.JwtAuthentication.JwtCleardownServce→OneBeyond.Studio.Obelisk.Authentication.Application.Repositories.AuthUsers.IAuthTokenRepository
- Direction
- Authentication.Application.Services.JwtAuthentication uses Authentication.Application.Repositories.AuthUsers, so a change to Authentication.Application.Repositories.AuthUsers can break Authentication.Application.Services.JwtAuthentication, while a change to Authentication.Application.Services.JwtAuthentication can't break Authentication.Application.Repositories.AuthUsers.
- Position
- Below the diagonal: Authentication.Application.Services.JwtAuthentication uses a module listed above it, which is the healthy direction.
16→7 Authentication.Application.Services.JwtAuthentication uses Authentication.Application.Services.ApplicationClaims✕
- Connections
- 1 pair of types, where a type in Authentication.Application.Services.JwtAuthentication uses a type in Authentication.Application.Services.ApplicationClaims.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.Services.JwtAuthentication.JwtTokenService→OneBeyond.Studio.Obelisk.Authentication.Application.Services.ApplicationClaims.IApplicationClaimsService
- Direction
- Authentication.Application.Services.JwtAuthentication uses Authentication.Application.Services.ApplicationClaims, so a change to Authentication.Application.Services.ApplicationClaims can break Authentication.Application.Services.JwtAuthentication, while a change to Authentication.Application.Services.JwtAuthentication can't break Authentication.Application.Services.ApplicationClaims.
- Position
- Below the diagonal: Authentication.Application.Services.JwtAuthentication uses a module listed above it, which is the healthy direction.
16→10 Authentication.Application.Services.JwtAuthentication uses Authentication.Domain.JwtAuthentication✕
- Connections
- 3 pairs of types, where a type in Authentication.Application.Services.JwtAuthentication uses a type in Authentication.Domain.JwtAuthentication.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.Services.JwtAuthentication.IJwtTokenService→OneBeyond.Studio.Obelisk.Authentication.Domain.JwtAuthentication.JwtTokenOneBeyond.Studio.Obelisk.Authentication.Application.Services.JwtAuthentication.JwtTokenService→OneBeyond.Studio.Obelisk.Authentication.Domain.JwtAuthentication.JwtAuthenticationOptionsOneBeyond.Studio.Obelisk.Authentication.Application.Services.JwtAuthentication.JwtTokenService→OneBeyond.Studio.Obelisk.Authentication.Domain.JwtAuthentication.JwtToken
- Direction
- Authentication.Application.Services.JwtAuthentication uses Authentication.Domain.JwtAuthentication, so a change to Authentication.Domain.JwtAuthentication can break Authentication.Application.Services.JwtAuthentication, while a change to Authentication.Application.Services.JwtAuthentication can't break Authentication.Domain.JwtAuthentication.
- Position
- Below the diagonal: Authentication.Application.Services.JwtAuthentication uses a module listed above it, which is the healthy direction.
17→8 Authentication.Domain.AuthenticationFlows uses Authentication.Domain✕
- Connections
- 1 pair of types, where a type in Authentication.Domain.AuthenticationFlows uses a type in Authentication.Domain.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Domain.AuthenticationFlows.IAuthenticationFlowHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInStatus
- Direction
- Authentication.Domain.AuthenticationFlows uses Authentication.Domain, so a change to Authentication.Domain can break Authentication.Domain.AuthenticationFlows, while a change to Authentication.Domain.AuthenticationFlows can't break Authentication.Domain.
- Position
- Below the diagonal: Authentication.Domain.AuthenticationFlows uses a module listed above it, which is the healthy direction.
18→8 Authentication.Domain.Commands uses Authentication.Domain✕
- Connections
- 2 pairs of types, where a type in Authentication.Domain.Commands uses a type in Authentication.Domain.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.CreateLogin→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInProviderLoginOneBeyond.Studio.Obelisk.Authentication.Domain.Commands.SignInViaProvider→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInProviderLogin
- Direction
- Authentication.Domain.Commands uses Authentication.Domain, so a change to Authentication.Domain can break Authentication.Domain.Commands, while a change to Authentication.Domain.Commands can't break Authentication.Domain.
- Position
- Below the diagonal: Authentication.Domain.Commands uses a module listed above it, which is the healthy direction.
19→8 Authentication.Domain.Queries uses Authentication.Domain✕
- Connections
- 1 pair of types, where a type in Authentication.Domain.Queries uses a type in Authentication.Domain.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Domain.Queries.GetLoginForProviderLogin→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInProviderLogin
- Direction
- Authentication.Domain.Queries uses Authentication.Domain, so a change to Authentication.Domain can break Authentication.Domain.Queries, while a change to Authentication.Domain.Queries can't break Authentication.Domain.
- Position
- Below the diagonal: Authentication.Domain.Queries uses a module listed above it, which is the healthy direction.
20→8 Authentication.Domain.TfaAuthentication uses Authentication.Domain✕
- Connections
- 1 pair of types, where a type in Authentication.Domain.TfaAuthentication uses a type in Authentication.Domain.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.SignInWithRecoveryCodeResult→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInStatus
- Direction
- Authentication.Domain.TfaAuthentication uses Authentication.Domain, so a change to Authentication.Domain can break Authentication.Domain.TfaAuthentication, while a change to Authentication.Domain.TfaAuthentication can't break Authentication.Domain.
- Position
- Below the diagonal: Authentication.Domain.TfaAuthentication uses a module listed above it, which is the healthy direction.
21→12 Domain.Features.Users.Entities uses Domain.Features.Users.Commands✕
- Connections
- 2 pairs of types, where a type in Domain.Features.Users.Entities uses a type in Domain.Features.Users.Commands.
- The types involved
OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.User→OneBeyond.Studio.Obelisk.Domain.Features.Users.Commands.CreateUserOneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBase→OneBeyond.Studio.Obelisk.Domain.Features.Users.Commands.UpdateUser
- Direction
- Domain.Features.Users.Entities uses Domain.Features.Users.Commands, so a change to Domain.Features.Users.Commands can break Domain.Features.Users.Entities, while a change to Domain.Features.Users.Entities can't break Domain.Features.Users.Commands.
- Position
- Below the diagonal: Domain.Features.Users.Entities uses a module listed above it, which is the healthy direction.
22→33 Infrastructure.Data.BulkUpdate uses Infrastructure.Data part of a loop✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Data.BulkUpdate uses a type in Infrastructure.Data.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.BulkUpdate.BulkUpdateConfiguration→OneBeyond.Studio.Obelisk.Infrastructure.Data.DomainContextOneBeyond.Studio.Obelisk.Infrastructure.Data.BulkUpdate.IBulkUpdateConfiguration→OneBeyond.Studio.Obelisk.Infrastructure.Data.DomainContext
- Direction
- Infrastructure.Data.BulkUpdate uses Infrastructure.Data, so a change to Infrastructure.Data can break Infrastructure.Data.BulkUpdate, while a change to Infrastructure.Data.BulkUpdate can't break Infrastructure.Data.
- 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→12 Application.Features.Users.CommandHandlers uses Domain.Features.Users.Commands✕
- Connections
- 4 pairs of types, where a type in Application.Features.Users.CommandHandlers uses a type in Domain.Features.Users.Commands.
- The types involved
OneBeyond.Studio.Obelisk.Application.Features.Users.CommandHandlers.CreateUserHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Commands.CreateUserOneBeyond.Studio.Obelisk.Application.Features.Users.CommandHandlers.SendResetPasswordEmailHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Commands.SendResetPasswordEmailOneBeyond.Studio.Obelisk.Application.Features.Users.CommandHandlers.UnlockUserHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Commands.UnlockUserOneBeyond.Studio.Obelisk.Application.Features.Users.CommandHandlers.UpdateUserHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Commands.UpdateUser
- Direction
- Application.Features.Users.CommandHandlers uses Domain.Features.Users.Commands, so a change to Domain.Features.Users.Commands can break Application.Features.Users.CommandHandlers, while a change to Application.Features.Users.CommandHandlers can't break Domain.Features.Users.Commands.
- Position
- Below the diagonal: Application.Features.Users.CommandHandlers uses a module listed above it, which is the healthy direction.
23→14 Application.Features.Users.CommandHandlers uses Application.Services.EmailTemplateService✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.CommandHandlers uses a type in Application.Services.EmailTemplateService.
- The types involved
OneBeyond.Studio.Obelisk.Application.Features.Users.CommandHandlers.SendResetPasswordEmailHandler→OneBeyond.Studio.Obelisk.Application.Services.EmailTemplateService.IEmailTemplateService
- Direction
- Application.Features.Users.CommandHandlers uses Application.Services.EmailTemplateService, so a change to Application.Services.EmailTemplateService can break Application.Features.Users.CommandHandlers, while a change to Application.Features.Users.CommandHandlers can't break Application.Services.EmailTemplateService.
- Position
- Below the diagonal: Application.Features.Users.CommandHandlers uses a module listed above it, which is the healthy direction.
23→21 Application.Features.Users.CommandHandlers uses Domain.Features.Users.Entities✕
- Connections
- 4 pairs of types, where a type in Application.Features.Users.CommandHandlers uses a type in Domain.Features.Users.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Application.Features.Users.CommandHandlers.CreateUserHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBaseOneBeyond.Studio.Obelisk.Application.Features.Users.CommandHandlers.SendResetPasswordEmailHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBaseOneBeyond.Studio.Obelisk.Application.Features.Users.CommandHandlers.UnlockUserHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBaseOneBeyond.Studio.Obelisk.Application.Features.Users.CommandHandlers.UpdateUserHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBase
- Direction
- Application.Features.Users.CommandHandlers uses Domain.Features.Users.Entities, so a change to Domain.Features.Users.Entities can break Application.Features.Users.CommandHandlers, while a change to Application.Features.Users.CommandHandlers can't break Domain.Features.Users.Entities.
- Position
- Below the diagonal: Application.Features.Users.CommandHandlers uses a module listed above it, which is the healthy direction.
24→14 Application.Features.Users.DomainEventHandlers uses Application.Services.EmailTemplateService✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.DomainEventHandlers uses a type in Application.Services.EmailTemplateService.
- The types involved
OneBeyond.Studio.Obelisk.Application.Features.Users.DomainEventHandlers.NewUserPasswordEmailSender→OneBeyond.Studio.Obelisk.Application.Services.EmailTemplateService.IEmailTemplateService
- Direction
- Application.Features.Users.DomainEventHandlers uses Application.Services.EmailTemplateService, so a change to Application.Services.EmailTemplateService can break Application.Features.Users.DomainEventHandlers, while a change to Application.Features.Users.DomainEventHandlers can't break Application.Services.EmailTemplateService.
- Position
- Below the diagonal: Application.Features.Users.DomainEventHandlers uses a module listed above it, which is the healthy direction.
24→21 Application.Features.Users.DomainEventHandlers uses Domain.Features.Users.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.DomainEventHandlers uses a type in Domain.Features.Users.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Application.Features.Users.DomainEventHandlers.NewUserPasswordEmailSender→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBase
- Direction
- Application.Features.Users.DomainEventHandlers uses Domain.Features.Users.Entities, so a change to Domain.Features.Users.Entities can break Application.Features.Users.DomainEventHandlers, while a change to Application.Features.Users.DomainEventHandlers can't break Domain.Features.Users.Entities.
- Position
- Below the diagonal: Application.Features.Users.DomainEventHandlers uses a module listed above it, which is the healthy direction.
25→21 Application.Features.Users.Predicates uses Domain.Features.Users.Entities✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.Predicates uses a type in Domain.Features.Users.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Application.Features.Users.Predicates.UserPredicates→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBase
- Direction
- Application.Features.Users.Predicates uses Domain.Features.Users.Entities, so a change to Domain.Features.Users.Entities can break Application.Features.Users.Predicates, while a change to Application.Features.Users.Predicates can't break Domain.Features.Users.Entities.
- Position
- Below the diagonal: Application.Features.Users.Predicates uses a module listed above it, which is the healthy direction.
26→1 Application.Features.Users.QueryHandlers uses Application.Features.Users.Dto✕
- Connections
- 2 pairs of types, where a type in Application.Features.Users.QueryHandlers uses a type in Application.Features.Users.Dto.
- The types involved
OneBeyond.Studio.Obelisk.Application.Features.Users.QueryHandlers.ListUserHandler→OneBeyond.Studio.Obelisk.Application.Features.Users.Dto.ListUsersDtoOneBeyond.Studio.Obelisk.Application.Features.Users.QueryHandlers.WhoAmIHandler→OneBeyond.Studio.Obelisk.Application.Features.Users.Dto.WhoAmIDto
- Direction
- Application.Features.Users.QueryHandlers uses Application.Features.Users.Dto, so a change to Application.Features.Users.Dto can break Application.Features.Users.QueryHandlers, while a change to Application.Features.Users.QueryHandlers can't break Application.Features.Users.Dto.
- Position
- Below the diagonal: Application.Features.Users.QueryHandlers uses a module listed above it, which is the healthy direction.
26→2 Application.Features.Users.QueryHandlers uses Application.Features.Users.Queries✕
- Connections
- 1 pair of types, where a type in Application.Features.Users.QueryHandlers uses a type in Application.Features.Users.Queries.
- The types involved
OneBeyond.Studio.Obelisk.Application.Features.Users.QueryHandlers.WhoAmIHandler→OneBeyond.Studio.Obelisk.Application.Features.Users.Queries.WhoAmI
- Direction
- Application.Features.Users.QueryHandlers uses Application.Features.Users.Queries, so a change to Application.Features.Users.Queries can break Application.Features.Users.QueryHandlers, while a change to Application.Features.Users.QueryHandlers can't break Application.Features.Users.Queries.
- Position
- Below the diagonal: Application.Features.Users.QueryHandlers uses a module listed above it, which is the healthy direction.
26→4 Application.Features.Users.QueryHandlers uses Application.Services.AmbientContexts✕
- Connections
- 2 pairs of types, where a type in Application.Features.Users.QueryHandlers uses a type in Application.Services.AmbientContexts.
- The types involved
OneBeyond.Studio.Obelisk.Application.Features.Users.QueryHandlers.WhoAmIHandler→OneBeyond.Studio.Obelisk.Application.Services.AmbientContexts.AmbientContextOneBeyond.Studio.Obelisk.Application.Features.Users.QueryHandlers.WhoAmIHandler→OneBeyond.Studio.Obelisk.Application.Services.AmbientContexts.UserContext
- Direction
- Application.Features.Users.QueryHandlers uses Application.Services.AmbientContexts, so a change to Application.Services.AmbientContexts can break Application.Features.Users.QueryHandlers, while a change to Application.Features.Users.QueryHandlers can't break Application.Services.AmbientContexts.
- Position
- Below the diagonal: Application.Features.Users.QueryHandlers uses a module listed above it, which is the healthy direction.
26→21 Application.Features.Users.QueryHandlers uses Domain.Features.Users.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Features.Users.QueryHandlers uses a type in Domain.Features.Users.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Application.Features.Users.QueryHandlers.ListUserHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBaseOneBeyond.Studio.Obelisk.Application.Features.Users.QueryHandlers.WhoAmIHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBase
- Direction
- Application.Features.Users.QueryHandlers uses Domain.Features.Users.Entities, so a change to Domain.Features.Users.Entities can break Application.Features.Users.QueryHandlers, while a change to Application.Features.Users.QueryHandlers can't break Domain.Features.Users.Entities.
- Position
- Below the diagonal: Application.Features.Users.QueryHandlers uses a module listed above it, which is the healthy direction.
27→8 Application.Services.AuthenticationFlows uses Authentication.Domain✕
- Connections
- 1 pair of types, where a type in Application.Services.AuthenticationFlows uses a type in Authentication.Domain.
- The types involved
OneBeyond.Studio.Obelisk.Application.Services.AuthenticationFlows.AuthenticationFlowHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInStatus
- Direction
- Application.Services.AuthenticationFlows uses Authentication.Domain, so a change to Authentication.Domain can break Application.Services.AuthenticationFlows, while a change to Application.Services.AuthenticationFlows can't break Authentication.Domain.
- Position
- Below the diagonal: Application.Services.AuthenticationFlows uses a module listed above it, which is the healthy direction.
27→17 Application.Services.AuthenticationFlows uses Authentication.Domain.AuthenticationFlows✕
- Connections
- 1 pair of types, where a type in Application.Services.AuthenticationFlows uses a type in Authentication.Domain.AuthenticationFlows.
- The types involved
OneBeyond.Studio.Obelisk.Application.Services.AuthenticationFlows.AuthenticationFlowHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.AuthenticationFlows.IAuthenticationFlowHandler
- Direction
- Application.Services.AuthenticationFlows uses Authentication.Domain.AuthenticationFlows, so a change to Authentication.Domain.AuthenticationFlows can break Application.Services.AuthenticationFlows, while a change to Application.Services.AuthenticationFlows can't break Authentication.Domain.AuthenticationFlows.
- Position
- Below the diagonal: Application.Services.AuthenticationFlows uses a module listed above it, which is the healthy direction.
27→21 Application.Services.AuthenticationFlows uses Domain.Features.Users.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Services.AuthenticationFlows uses a type in Domain.Features.Users.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Application.Services.AuthenticationFlows.AuthenticationFlowHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBaseOneBeyond.Studio.Obelisk.Application.Services.AuthenticationFlows.AuthenticationFlowHandler→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserLoginLog
- Direction
- Application.Services.AuthenticationFlows uses Domain.Features.Users.Entities, so a change to Domain.Features.Users.Entities can break Application.Services.AuthenticationFlows, while a change to Application.Services.AuthenticationFlows can't break Domain.Features.Users.Entities.
- Position
- Below the diagonal: Application.Services.AuthenticationFlows uses a module listed above it, which is the healthy direction.
28→5 Authentication.Application.CommandHandlers uses Authentication.Application.Entities✕
- Connections
- 12 pairs of types, where a type in Authentication.Application.CommandHandlers uses a type in Authentication.Application.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.ChangePasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.CreateLoginHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.GenerateResetPasswordTokenByEmailHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.GenerateResetPasswordTokenByLoginIdHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.ResetPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SetPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInViaPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInViaProviderHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignOutHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.UnlockLoginHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.UpdateLoginHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUser
- Direction
- Authentication.Application.CommandHandlers uses Authentication.Application.Entities, so a change to Authentication.Application.Entities can break Authentication.Application.CommandHandlers, while a change to Authentication.Application.CommandHandlers can't break Authentication.Application.Entities.
- Position
- Below the diagonal: Authentication.Application.CommandHandlers uses a module listed above it, which is the healthy direction.
28→8 Authentication.Application.CommandHandlers uses Authentication.Domain✕
- Connections
- 8 pairs of types, where a type in Authentication.Application.CommandHandlers uses a type in Authentication.Domain.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.ChangePasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.ChangePasswordResultOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.CreateLoginHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.ResetPasswordTokenOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.GenerateResetPasswordTokenByEmailHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.ResetPasswordTokenOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.ResetPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.ResetPasswordStatusOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInResultOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInViaPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInResultOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInViaProviderHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInResultOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.UpdateLoginHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.UpdateLoginResult
- Direction
- Authentication.Application.CommandHandlers uses Authentication.Domain, so a change to Authentication.Domain can break Authentication.Application.CommandHandlers, while a change to Authentication.Application.CommandHandlers can't break Authentication.Domain.
- Position
- Below the diagonal: Authentication.Application.CommandHandlers uses a module listed above it, which is the healthy direction.
28→17 Authentication.Application.CommandHandlers uses Authentication.Domain.AuthenticationFlows✕
- Connections
- 3 pairs of types, where a type in Authentication.Application.CommandHandlers uses a type in Authentication.Domain.AuthenticationFlows.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.AuthenticationFlows.IAuthenticationFlowHandlerOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInViaPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.AuthenticationFlows.IAuthenticationFlowHandlerOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInViaProviderHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.AuthenticationFlows.IAuthenticationFlowHandler
- Direction
- Authentication.Application.CommandHandlers uses Authentication.Domain.AuthenticationFlows, so a change to Authentication.Domain.AuthenticationFlows can break Authentication.Application.CommandHandlers, while a change to Authentication.Application.CommandHandlers can't break Authentication.Domain.AuthenticationFlows.
- Position
- Below the diagonal: Authentication.Application.CommandHandlers uses a module listed above it, which is the healthy direction.
28→18 Authentication.Application.CommandHandlers uses Authentication.Domain.Commands✕
- Connections
- 11 pairs of types, where a type in Authentication.Application.CommandHandlers uses a type in Authentication.Domain.Commands.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.ChangePasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.ChangePasswordOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.CreateLoginHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.CreateLoginOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.GenerateResetPasswordTokenByEmailHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.GenerateResetPasswordTokenByEmailOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.GenerateResetPasswordTokenByLoginIdHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.GenerateResetPasswordTokenByLoginIdOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.ResetPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.ResetPasswordOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SetPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.SetPasswordOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInViaPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.SignInViaPasswordOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignInViaProviderHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.SignInViaProviderOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.SignOutHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.SignOutOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.UnlockLoginHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.UnlockLoginOneBeyond.Studio.Obelisk.Authentication.Application.CommandHandlers.UpdateLoginHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.UpdateLogin
- Direction
- Authentication.Application.CommandHandlers uses Authentication.Domain.Commands, so a change to Authentication.Domain.Commands can break Authentication.Application.CommandHandlers, while a change to Authentication.Application.CommandHandlers can't break Authentication.Domain.Commands.
- Position
- Below the diagonal: Authentication.Application.CommandHandlers uses a module listed above it, which is the healthy direction.
29→5 Authentication.Application.JwtAuthentication.CommandHandlers uses Authentication.Application.Entities✕
- Connections
- 4 pairs of types, where a type in Authentication.Application.JwtAuthentication.CommandHandlers uses a type in Authentication.Application.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.CommandHandlers.RefreshJwtTokenHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthTokenOneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.CommandHandlers.RefreshJwtTokenHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.CommandHandlers.SignInJwtTokenHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.CommandHandlers.SignoutJwtHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUser
- Direction
- Authentication.Application.JwtAuthentication.CommandHandlers uses Authentication.Application.Entities, so a change to Authentication.Application.Entities can break Authentication.Application.JwtAuthentication.CommandHandlers, while a change to Authentication.Application.JwtAuthentication.CommandHandlers can't break Authentication.Application.Entities.
- Position
- Below the diagonal: Authentication.Application.JwtAuthentication.CommandHandlers uses a module listed above it, which is the healthy direction.
29→10 Authentication.Application.JwtAuthentication.CommandHandlers uses Authentication.Domain.JwtAuthentication✕
- Connections
- 2 pairs of types, where a type in Authentication.Application.JwtAuthentication.CommandHandlers uses a type in Authentication.Domain.JwtAuthentication.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.CommandHandlers.RefreshJwtTokenHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.JwtAuthentication.JwtTokenOneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.CommandHandlers.SignInJwtTokenHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.JwtAuthentication.JwtToken
- Direction
- Authentication.Application.JwtAuthentication.CommandHandlers uses Authentication.Domain.JwtAuthentication, so a change to Authentication.Domain.JwtAuthentication can break Authentication.Application.JwtAuthentication.CommandHandlers, while a change to Authentication.Application.JwtAuthentication.CommandHandlers can't break Authentication.Domain.JwtAuthentication.
- Position
- Below the diagonal: Authentication.Application.JwtAuthentication.CommandHandlers uses a module listed above it, which is the healthy direction.
29→16 Authentication.Application.JwtAuthentication.CommandHandlers uses Authentication.Application.Services.JwtAuthentication✕
- Connections
- 3 pairs of types, where a type in Authentication.Application.JwtAuthentication.CommandHandlers uses a type in Authentication.Application.Services.JwtAuthentication.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.CommandHandlers.RefreshJwtTokenHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Services.JwtAuthentication.IJwtTokenServiceOneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.CommandHandlers.SignInJwtTokenHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Services.JwtAuthentication.IJwtTokenServiceOneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.CommandHandlers.SignoutJwtHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Services.JwtAuthentication.IJwtTokenService
- Direction
- Authentication.Application.JwtAuthentication.CommandHandlers uses Authentication.Application.Services.JwtAuthentication, so a change to Authentication.Application.Services.JwtAuthentication can break Authentication.Application.JwtAuthentication.CommandHandlers, while a change to Authentication.Application.JwtAuthentication.CommandHandlers can't break Authentication.Application.Services.JwtAuthentication.
- Position
- Below the diagonal: Authentication.Application.JwtAuthentication.CommandHandlers uses a module listed above it, which is the healthy direction.
29→17 Authentication.Application.JwtAuthentication.CommandHandlers uses Authentication.Domain.AuthenticationFlows✕
- Connections
- 1 pair of types, where a type in Authentication.Application.JwtAuthentication.CommandHandlers uses a type in Authentication.Domain.AuthenticationFlows.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.JwtAuthentication.CommandHandlers.SignInJwtTokenHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.AuthenticationFlows.IAuthenticationFlowHandler
- Direction
- Authentication.Application.JwtAuthentication.CommandHandlers uses Authentication.Domain.AuthenticationFlows, so a change to Authentication.Domain.AuthenticationFlows can break Authentication.Application.JwtAuthentication.CommandHandlers, while a change to Authentication.Application.JwtAuthentication.CommandHandlers can't break Authentication.Domain.AuthenticationFlows.
- Position
- Below the diagonal: Authentication.Application.JwtAuthentication.CommandHandlers uses a module listed above it, which is the healthy direction.
30→5 Authentication.Application.QueryHandlers uses Authentication.Application.Entities✕
- Connections
- 3 pairs of types, where a type in Authentication.Application.QueryHandlers uses a type in Authentication.Application.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.QueryHandlers.CheckLoginHasPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.QueryHandlers.GetExternalLoginInformationHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.QueryHandlers.GetLoginForProviderLoginHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUser
- Direction
- Authentication.Application.QueryHandlers uses Authentication.Application.Entities, so a change to Authentication.Application.Entities can break Authentication.Application.QueryHandlers, while a change to Authentication.Application.QueryHandlers can't break Authentication.Application.Entities.
- Position
- Below the diagonal: Authentication.Application.QueryHandlers uses a module listed above it, which is the healthy direction.
30→8 Authentication.Application.QueryHandlers uses Authentication.Domain✕
- Connections
- 1 pair of types, where a type in Authentication.Application.QueryHandlers uses a type in Authentication.Domain.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.QueryHandlers.GetExternalLoginInformationHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.ExternalLoginInfo
- Direction
- Authentication.Application.QueryHandlers uses Authentication.Domain, so a change to Authentication.Domain can break Authentication.Application.QueryHandlers, while a change to Authentication.Application.QueryHandlers can't break Authentication.Domain.
- Position
- Below the diagonal: Authentication.Application.QueryHandlers uses a module listed above it, which is the healthy direction.
30→19 Authentication.Application.QueryHandlers uses Authentication.Domain.Queries✕
- Connections
- 3 pairs of types, where a type in Authentication.Application.QueryHandlers uses a type in Authentication.Domain.Queries.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.QueryHandlers.CheckLoginHasPasswordHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Queries.CheckLoginHasPasswordOneBeyond.Studio.Obelisk.Authentication.Application.QueryHandlers.GetExternalLoginInformationHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Queries.GetExternalLoginInformationOneBeyond.Studio.Obelisk.Authentication.Application.QueryHandlers.GetLoginForProviderLoginHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.Queries.GetLoginForProviderLogin
- Direction
- Authentication.Application.QueryHandlers uses Authentication.Domain.Queries, so a change to Authentication.Domain.Queries can break Authentication.Application.QueryHandlers, while a change to Authentication.Application.QueryHandlers can't break Authentication.Domain.Queries.
- Position
- Below the diagonal: Authentication.Application.QueryHandlers uses a module listed above it, which is the healthy direction.
31→5 Authentication.Application.TfaAuthentication.QueryHandlers uses Authentication.Application.Entities✕
- Connections
- 1 pair of types, where a type in Authentication.Application.TfaAuthentication.QueryHandlers uses a type in Authentication.Application.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.QueryHandlers.GetTfaSettingsHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUser
- Direction
- Authentication.Application.TfaAuthentication.QueryHandlers uses Authentication.Application.Entities, so a change to Authentication.Application.Entities can break Authentication.Application.TfaAuthentication.QueryHandlers, while a change to Authentication.Application.TfaAuthentication.QueryHandlers can't break Authentication.Application.Entities.
- Position
- Below the diagonal: Authentication.Application.TfaAuthentication.QueryHandlers uses a module listed above it, which is the healthy direction.
31→20 Authentication.Application.TfaAuthentication.QueryHandlers uses Authentication.Domain.TfaAuthentication✕
- Connections
- 1 pair of types, where a type in Authentication.Application.TfaAuthentication.QueryHandlers uses a type in Authentication.Domain.TfaAuthentication.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.QueryHandlers.GetTfaSettingsHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.LoginTfaSettings
- Direction
- Authentication.Application.TfaAuthentication.QueryHandlers uses Authentication.Domain.TfaAuthentication, so a change to Authentication.Domain.TfaAuthentication can break Authentication.Application.TfaAuthentication.QueryHandlers, while a change to Authentication.Application.TfaAuthentication.QueryHandlers can't break Authentication.Domain.TfaAuthentication.
- Position
- Below the diagonal: Authentication.Application.TfaAuthentication.QueryHandlers uses a module listed above it, which is the healthy direction.
32→8 Authentication.Domain.TfaAuthentication.Commands uses Authentication.Domain✕
- Connections
- 4 pairs of types, where a type in Authentication.Domain.TfaAuthentication.Commands uses a type in Authentication.Domain.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.DisableTfa→OneBeyond.Studio.Obelisk.Authentication.Domain.LoginCommandOneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.EnableTfa→OneBeyond.Studio.Obelisk.Authentication.Domain.LoginCommandOneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.GenerateTfaKey→OneBeyond.Studio.Obelisk.Authentication.Domain.LoginCommandOneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.GenerateTfaRecoveryCodes→OneBeyond.Studio.Obelisk.Authentication.Domain.LoginCommand
- Direction
- Authentication.Domain.TfaAuthentication.Commands uses Authentication.Domain, so a change to Authentication.Domain can break Authentication.Domain.TfaAuthentication.Commands, while a change to Authentication.Domain.TfaAuthentication.Commands can't break Authentication.Domain.
- Position
- Below the diagonal: Authentication.Domain.TfaAuthentication.Commands uses a module listed above it, which is the healthy direction.
32→20 Authentication.Domain.TfaAuthentication.Commands uses Authentication.Domain.TfaAuthentication✕
- Connections
- 1 pair of types, where a type in Authentication.Domain.TfaAuthentication.Commands uses a type in Authentication.Domain.TfaAuthentication.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.GenerateTfaKey→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.TfaKey
- Direction
- Authentication.Domain.TfaAuthentication.Commands uses Authentication.Domain.TfaAuthentication, so a change to Authentication.Domain.TfaAuthentication can break Authentication.Domain.TfaAuthentication.Commands, while a change to Authentication.Domain.TfaAuthentication.Commands can't break Authentication.Domain.TfaAuthentication.
- Position
- Below the diagonal: Authentication.Domain.TfaAuthentication.Commands uses a module listed above it, which is the healthy direction.
33→3 Infrastructure.Data uses Application.Repositories✕
- Connections
- 1 pair of types, where a type in Infrastructure.Data uses a type in Application.Repositories.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.RWBulkRepository→OneBeyond.Studio.Obelisk.Application.Repositories.IRWBulkRepository
- Direction
- Infrastructure.Data uses Application.Repositories, so a change to Application.Repositories can break Infrastructure.Data, while a change to Infrastructure.Data can't break Application.Repositories.
- Position
- Below the diagonal: Infrastructure.Data uses a module listed above it, which is the healthy direction.
33→5 Infrastructure.Data uses Authentication.Application.Entities✕
- Connections
- 3 pairs of types, where a type in Infrastructure.Data uses a type in Authentication.Application.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.AuthContextExtensions→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthRoleOneBeyond.Studio.Obelisk.Infrastructure.Data.AuthContextExtensions→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Infrastructure.Data.AuthUserStore→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUser
- Direction
- Infrastructure.Data uses Authentication.Application.Entities, so a change to Authentication.Application.Entities can break Infrastructure.Data, while a change to Infrastructure.Data can't break Authentication.Application.Entities.
- Position
- Below the diagonal: Infrastructure.Data uses a module listed above it, which is the healthy direction.
33→22 Infrastructure.Data uses Infrastructure.Data.BulkUpdate✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Data uses a type in Infrastructure.Data.BulkUpdate.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.RWBulkRepository→OneBeyond.Studio.Obelisk.Infrastructure.Data.BulkUpdate.EntityTypeMappingOneBeyond.Studio.Obelisk.Infrastructure.Data.RWBulkRepository→OneBeyond.Studio.Obelisk.Infrastructure.Data.BulkUpdate.IBulkUpdateConfiguration
- Direction
- Infrastructure.Data uses Infrastructure.Data.BulkUpdate, so a change to Infrastructure.Data.BulkUpdate can break Infrastructure.Data, while a change to Infrastructure.Data can't break Infrastructure.Data.BulkUpdate.
- Position
- Below the diagonal: Infrastructure.Data uses a module listed above it, which is the healthy direction.
34→11 Infrastructure.Data.EmailTemplates.Projections uses Domain.Features.EmailTemplates.Entities✕
- Connections
- 1 pair of types, where a type in Infrastructure.Data.EmailTemplates.Projections uses a type in Domain.Features.EmailTemplates.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.EmailTemplates.Projections.EmailTemplateProjection→OneBeyond.Studio.Obelisk.Domain.Features.EmailTemplates.Entities.EmailTemplate
- Direction
- Infrastructure.Data.EmailTemplates.Projections uses Domain.Features.EmailTemplates.Entities, so a change to Domain.Features.EmailTemplates.Entities can break Infrastructure.Data.EmailTemplates.Projections, while a change to Infrastructure.Data.EmailTemplates.Projections can't break Domain.Features.EmailTemplates.Entities.
- Position
- Below the diagonal: Infrastructure.Data.EmailTemplates.Projections uses a module listed above it, which is the healthy direction.
34→14 Infrastructure.Data.EmailTemplates.Projections uses Application.Services.EmailTemplateService✕
- Connections
- 1 pair of types, where a type in Infrastructure.Data.EmailTemplates.Projections uses a type in Application.Services.EmailTemplateService.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.EmailTemplates.Projections.EmailTemplateProjection→OneBeyond.Studio.Obelisk.Application.Services.EmailTemplateService.EmailTemplateDto
- Direction
- Infrastructure.Data.EmailTemplates.Projections uses Application.Services.EmailTemplateService, so a change to Application.Services.EmailTemplateService can break Infrastructure.Data.EmailTemplates.Projections, while a change to Infrastructure.Data.EmailTemplates.Projections can't break Application.Services.EmailTemplateService.
- Position
- Below the diagonal: Infrastructure.Data.EmailTemplates.Projections uses a module listed above it, which is the healthy direction.
35→1 Infrastructure.Data.Users.Projections uses Application.Features.Users.Dto✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Data.Users.Projections uses a type in Application.Features.Users.Dto.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.Users.Projections.UserProjection→OneBeyond.Studio.Obelisk.Application.Features.Users.Dto.GetUserDtoOneBeyond.Studio.Obelisk.Infrastructure.Data.Users.Projections.UserProjection→OneBeyond.Studio.Obelisk.Application.Features.Users.Dto.ListUsersDtoOneBeyond.Studio.Obelisk.Infrastructure.Data.Users.Projections.UserProjection→OneBeyond.Studio.Obelisk.Application.Features.Users.Dto.UserIsActiveDtoOneBeyond.Studio.Obelisk.Infrastructure.Data.Users.Projections.UserProjection→OneBeyond.Studio.Obelisk.Application.Features.Users.Dto.UserNameDto
- Direction
- Infrastructure.Data.Users.Projections uses Application.Features.Users.Dto, so a change to Application.Features.Users.Dto can break Infrastructure.Data.Users.Projections, while a change to Infrastructure.Data.Users.Projections can't break Application.Features.Users.Dto.
- Position
- Below the diagonal: Infrastructure.Data.Users.Projections uses a module listed above it, which is the healthy direction.
35→21 Infrastructure.Data.Users.Projections uses Domain.Features.Users.Entities✕
- Connections
- 1 pair of types, where a type in Infrastructure.Data.Users.Projections uses a type in Domain.Features.Users.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.Users.Projections.UserProjection→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBase
- Direction
- Infrastructure.Data.Users.Projections uses Domain.Features.Users.Entities, so a change to Domain.Features.Users.Entities can break Infrastructure.Data.Users.Projections, while a change to Infrastructure.Data.Users.Projections can't break Domain.Features.Users.Entities.
- Position
- Below the diagonal: Infrastructure.Data.Users.Projections uses a module listed above it, which is the healthy direction.
36→4 WebApi.AmbientContexts uses Application.Services.AmbientContexts✕
- Connections
- 1 pair of types, where a type in WebApi.AmbientContexts uses a type in Application.Services.AmbientContexts.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.AmbientContexts.AmbientContextAccessor→OneBeyond.Studio.Obelisk.Application.Services.AmbientContexts.AmbientContext
- Direction
- WebApi.AmbientContexts uses Application.Services.AmbientContexts, so a change to Application.Services.AmbientContexts can break WebApi.AmbientContexts, while a change to WebApi.AmbientContexts can't break Application.Services.AmbientContexts.
- Position
- Below the diagonal: WebApi.AmbientContexts uses a module listed above it, which is the healthy direction.
36→5 WebApi.AmbientContexts uses Authentication.Application.Entities✕
- Connections
- 1 pair of types, where a type in WebApi.AmbientContexts uses a type in Authentication.Application.Entities.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.AmbientContexts.ApplicationClaimsIdentityFactory→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUser
- Direction
- WebApi.AmbientContexts uses Authentication.Application.Entities, so a change to Authentication.Application.Entities can break WebApi.AmbientContexts, while a change to WebApi.AmbientContexts can't break Authentication.Application.Entities.
- Position
- Below the diagonal: WebApi.AmbientContexts uses a module listed above it, which is the healthy direction.
36→7 WebApi.AmbientContexts uses Authentication.Application.Services.ApplicationClaims✕
- Connections
- 1 pair of types, where a type in WebApi.AmbientContexts uses a type in Authentication.Application.Services.ApplicationClaims.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.AmbientContexts.ApplicationClaimsIdentityFactory→OneBeyond.Studio.Obelisk.Authentication.Application.Services.ApplicationClaims.IApplicationClaimsService
- Direction
- WebApi.AmbientContexts uses Authentication.Application.Services.ApplicationClaims, so a change to Authentication.Application.Services.ApplicationClaims can break WebApi.AmbientContexts, while a change to WebApi.AmbientContexts can't break Authentication.Application.Services.ApplicationClaims.
- Position
- Below the diagonal: WebApi.AmbientContexts uses a module listed above it, which is the healthy direction.
36→21 WebApi.AmbientContexts uses Domain.Features.Users.Entities✕
- Connections
- 1 pair of types, where a type in WebApi.AmbientContexts uses a type in Domain.Features.Users.Entities.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.AmbientContexts.ApplicationClaimsIdentityFactory→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.UserBase
- Direction
- WebApi.AmbientContexts uses Domain.Features.Users.Entities, so a change to Domain.Features.Users.Entities can break WebApi.AmbientContexts, while a change to WebApi.AmbientContexts can't break Domain.Features.Users.Entities.
- Position
- Below the diagonal: WebApi.AmbientContexts uses a module listed above it, which is the healthy direction.
37→5 Authentication.Application.TfaAuthentication.CommandHandlers uses Authentication.Application.Entities✕
- Connections
- 7 pairs of types, where a type in Authentication.Application.TfaAuthentication.CommandHandlers uses a type in Authentication.Application.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.DisableTfaHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.EnableTfaHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.ForgetTfaClientHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.GenerateTfaKeyHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.GenerateTfaRecoveryCodesHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.SignInTfaHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUserOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.SignInTfaWithRecoveryCodeHandler→OneBeyond.Studio.Obelisk.Authentication.Application.Entities.AuthUser
- Direction
- Authentication.Application.TfaAuthentication.CommandHandlers uses Authentication.Application.Entities, so a change to Authentication.Application.Entities can break Authentication.Application.TfaAuthentication.CommandHandlers, while a change to Authentication.Application.TfaAuthentication.CommandHandlers can't break Authentication.Application.Entities.
- Position
- Below the diagonal: Authentication.Application.TfaAuthentication.CommandHandlers uses a module listed above it, which is the healthy direction.
37→8 Authentication.Application.TfaAuthentication.CommandHandlers uses Authentication.Domain✕
- Connections
- 1 pair of types, where a type in Authentication.Application.TfaAuthentication.CommandHandlers uses a type in Authentication.Domain.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.SignInTfaHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInResult
- Direction
- Authentication.Application.TfaAuthentication.CommandHandlers uses Authentication.Domain, so a change to Authentication.Domain can break Authentication.Application.TfaAuthentication.CommandHandlers, while a change to Authentication.Application.TfaAuthentication.CommandHandlers can't break Authentication.Domain.
- Position
- Below the diagonal: Authentication.Application.TfaAuthentication.CommandHandlers uses a module listed above it, which is the healthy direction.
37→20 Authentication.Application.TfaAuthentication.CommandHandlers uses Authentication.Domain.TfaAuthentication✕
- Connections
- 2 pairs of types, where a type in Authentication.Application.TfaAuthentication.CommandHandlers uses a type in Authentication.Domain.TfaAuthentication.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.GenerateTfaKeyHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.TfaKeyOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.SignInTfaWithRecoveryCodeHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.SignInWithRecoveryCodeResult
- Direction
- Authentication.Application.TfaAuthentication.CommandHandlers uses Authentication.Domain.TfaAuthentication, so a change to Authentication.Domain.TfaAuthentication can break Authentication.Application.TfaAuthentication.CommandHandlers, while a change to Authentication.Application.TfaAuthentication.CommandHandlers can't break Authentication.Domain.TfaAuthentication.
- Position
- Below the diagonal: Authentication.Application.TfaAuthentication.CommandHandlers uses a module listed above it, which is the healthy direction.
37→32 Authentication.Application.TfaAuthentication.CommandHandlers uses Authentication.Domain.TfaAuthentication.Commands✕
- Connections
- 7 pairs of types, where a type in Authentication.Application.TfaAuthentication.CommandHandlers uses a type in Authentication.Domain.TfaAuthentication.Commands.
- The types involved
OneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.DisableTfaHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.DisableTfaOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.EnableTfaHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.EnableTfaOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.ForgetTfaClientHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.ForgetTfaClientOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.GenerateTfaKeyHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.GenerateTfaKeyOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.GenerateTfaRecoveryCodesHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.GenerateTfaRecoveryCodesOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.SignInTfaHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.SignInTfaOneBeyond.Studio.Obelisk.Authentication.Application.TfaAuthentication.CommandHandlers.SignInTfaWithRecoveryCodeHandler→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.SignInTfaWithRecoveryCode
- Direction
- Authentication.Application.TfaAuthentication.CommandHandlers uses Authentication.Domain.TfaAuthentication.Commands, so a change to Authentication.Domain.TfaAuthentication.Commands can break Authentication.Application.TfaAuthentication.CommandHandlers, while a change to Authentication.Application.TfaAuthentication.CommandHandlers can't break Authentication.Domain.TfaAuthentication.Commands.
- Position
- Below the diagonal: Authentication.Application.TfaAuthentication.CommandHandlers uses a module listed above it, which is the healthy direction.
38→6 Infrastructure.Data.AuthUsers.Repositories uses Authentication.Application.Repositories.AuthUsers✕
- Connections
- 1 pair of types, where a type in Infrastructure.Data.AuthUsers.Repositories uses a type in Authentication.Application.Repositories.AuthUsers.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.AuthUsers.Repositories.AuthTokenRepository→OneBeyond.Studio.Obelisk.Authentication.Application.Repositories.AuthUsers.IAuthTokenRepository
- Direction
- Infrastructure.Data.AuthUsers.Repositories uses Authentication.Application.Repositories.AuthUsers, so a change to Authentication.Application.Repositories.AuthUsers can break Infrastructure.Data.AuthUsers.Repositories, while a change to Infrastructure.Data.AuthUsers.Repositories can't break Authentication.Application.Repositories.AuthUsers.
- Position
- Below the diagonal: Infrastructure.Data.AuthUsers.Repositories uses a module listed above it, which is the healthy direction.
38→33 Infrastructure.Data.AuthUsers.Repositories uses Infrastructure.Data✕
- Connections
- 1 pair of types, where a type in Infrastructure.Data.AuthUsers.Repositories uses a type in Infrastructure.Data.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.AuthUsers.Repositories.AuthTokenRepository→OneBeyond.Studio.Obelisk.Infrastructure.Data.DomainContext
- Direction
- Infrastructure.Data.AuthUsers.Repositories uses Infrastructure.Data, so a change to Infrastructure.Data can break Infrastructure.Data.AuthUsers.Repositories, while a change to Infrastructure.Data.AuthUsers.Repositories can't break Infrastructure.Data.
- Position
- Below the diagonal: Infrastructure.Data.AuthUsers.Repositories uses a module listed above it, which is the healthy direction.
39→21 Infrastructure.Data.Seeding uses Domain.Features.Users.Entities✕
- Connections
- 1 pair of types, where a type in Infrastructure.Data.Seeding uses a type in Domain.Features.Users.Entities.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.Seeding.IdentitiesSeeder→OneBeyond.Studio.Obelisk.Domain.Features.Users.Entities.User
- Direction
- Infrastructure.Data.Seeding uses Domain.Features.Users.Entities, so a change to Domain.Features.Users.Entities can break Infrastructure.Data.Seeding, while a change to Infrastructure.Data.Seeding can't break Domain.Features.Users.Entities.
- Position
- Below the diagonal: Infrastructure.Data.Seeding uses a module listed above it, which is the healthy direction.
39→33 Infrastructure.Data.Seeding uses Infrastructure.Data✕
- Connections
- 2 pairs of types, where a type in Infrastructure.Data.Seeding uses a type in Infrastructure.Data.
- The types involved
OneBeyond.Studio.Obelisk.Infrastructure.Data.Seeding.EmailTemplatesSeeder→OneBeyond.Studio.Obelisk.Infrastructure.Data.DomainContextOneBeyond.Studio.Obelisk.Infrastructure.Data.Seeding.IdentitiesSeeder→OneBeyond.Studio.Obelisk.Infrastructure.Data.DomainContext
- Direction
- Infrastructure.Data.Seeding uses Infrastructure.Data, so a change to Infrastructure.Data can break Infrastructure.Data.Seeding, while a change to Infrastructure.Data.Seeding can't break Infrastructure.Data.
- Position
- Below the diagonal: Infrastructure.Data.Seeding uses a module listed above it, which is the healthy direction.
40→1 WebApi.Controllers uses Application.Features.Users.Dto✕
- Connections
- 2 pairs of types, where a type in WebApi.Controllers uses a type in Application.Features.Users.Dto.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.Controllers.AuthController→OneBeyond.Studio.Obelisk.Application.Features.Users.Dto.WhoAmIDtoOneBeyond.Studio.Obelisk.WebApi.Controllers.UsersController→OneBeyond.Studio.Obelisk.Application.Features.Users.Dto.CreateUserDto
- Direction
- WebApi.Controllers uses Application.Features.Users.Dto, so a change to Application.Features.Users.Dto can break WebApi.Controllers, while a change to WebApi.Controllers can't break Application.Features.Users.Dto.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
40→4 WebApi.Controllers uses Application.Services.AmbientContexts✕
- Connections
- 4 pairs of types, where a type in WebApi.Controllers uses a type in Application.Services.AmbientContexts.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.Controllers.AuthController→OneBeyond.Studio.Obelisk.Application.Services.AmbientContexts.AmbientContextOneBeyond.Studio.Obelisk.WebApi.Controllers.JWTAuthenticationController→OneBeyond.Studio.Obelisk.Application.Services.AmbientContexts.AmbientContextOneBeyond.Studio.Obelisk.WebApi.Controllers.TFAController→OneBeyond.Studio.Obelisk.Application.Services.AmbientContexts.AmbientContextOneBeyond.Studio.Obelisk.WebApi.Controllers.TFAController→OneBeyond.Studio.Obelisk.Application.Services.AmbientContexts.UserContext
- Direction
- WebApi.Controllers uses Application.Services.AmbientContexts, so a change to Application.Services.AmbientContexts can break WebApi.Controllers, while a change to WebApi.Controllers can't break Application.Services.AmbientContexts.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
40→8 WebApi.Controllers uses Authentication.Domain✕
- Connections
- 3 pairs of types, where a type in WebApi.Controllers uses a type in Authentication.Domain.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.Controllers.AuthController→OneBeyond.Studio.Obelisk.Authentication.Domain.ChangePasswordResultOneBeyond.Studio.Obelisk.WebApi.Controllers.AuthController→OneBeyond.Studio.Obelisk.Authentication.Domain.ResetPasswordStatusOneBeyond.Studio.Obelisk.WebApi.Controllers.AuthController→OneBeyond.Studio.Obelisk.Authentication.Domain.SignInResult
- Direction
- WebApi.Controllers uses Authentication.Domain, so a change to Authentication.Domain can break WebApi.Controllers, while a change to WebApi.Controllers can't break Authentication.Domain.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
40→10 WebApi.Controllers uses Authentication.Domain.JwtAuthentication✕
- Connections
- 1 pair of types, where a type in WebApi.Controllers uses a type in Authentication.Domain.JwtAuthentication.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.Controllers.JWTAuthenticationController→OneBeyond.Studio.Obelisk.Authentication.Domain.JwtAuthentication.JwtToken
- Direction
- WebApi.Controllers uses Authentication.Domain.JwtAuthentication, so a change to Authentication.Domain.JwtAuthentication can break WebApi.Controllers, while a change to WebApi.Controllers can't break Authentication.Domain.JwtAuthentication.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
40→12 WebApi.Controllers uses Domain.Features.Users.Commands✕
- Connections
- 1 pair of types, where a type in WebApi.Controllers uses a type in Domain.Features.Users.Commands.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.Controllers.UsersController→OneBeyond.Studio.Obelisk.Domain.Features.Users.Commands.UpdateUser
- Direction
- WebApi.Controllers uses Domain.Features.Users.Commands, so a change to Domain.Features.Users.Commands can break WebApi.Controllers, while a change to WebApi.Controllers can't break Domain.Features.Users.Commands.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
40→13 WebApi.Controllers uses WebApi.Requests✕
- Connections
- 1 pair of types, where a type in WebApi.Controllers uses a type in WebApi.Requests.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.Controllers.QBasedController→OneBeyond.Studio.Obelisk.WebApi.Requests.ListRequest
- Direction
- WebApi.Controllers uses WebApi.Requests, so a change to WebApi.Requests can break WebApi.Controllers, while a change to WebApi.Controllers can't break WebApi.Requests.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
40→18 WebApi.Controllers uses Authentication.Domain.Commands✕
- Connections
- 1 pair of types, where a type in WebApi.Controllers uses a type in Authentication.Domain.Commands.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.Controllers.AuthController→OneBeyond.Studio.Obelisk.Authentication.Domain.Commands.SignInViaPassword
- Direction
- WebApi.Controllers uses Authentication.Domain.Commands, so a change to Authentication.Domain.Commands can break WebApi.Controllers, while a change to WebApi.Controllers can't break Authentication.Domain.Commands.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
40→20 WebApi.Controllers uses Authentication.Domain.TfaAuthentication✕
- Connections
- 3 pairs of types, where a type in WebApi.Controllers uses a type in Authentication.Domain.TfaAuthentication.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.Controllers.AuthController→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.SignInWithRecoveryCodeResultOneBeyond.Studio.Obelisk.WebApi.Controllers.TFAController→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.LoginTfaSettingsOneBeyond.Studio.Obelisk.WebApi.Controllers.TFAController→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.TfaAuthenticatorSettings
- Direction
- WebApi.Controllers uses Authentication.Domain.TfaAuthentication, so a change to Authentication.Domain.TfaAuthentication can break WebApi.Controllers, while a change to WebApi.Controllers can't break Authentication.Domain.TfaAuthentication.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
40→32 WebApi.Controllers uses Authentication.Domain.TfaAuthentication.Commands✕
- Connections
- 2 pairs of types, where a type in WebApi.Controllers uses a type in Authentication.Domain.TfaAuthentication.Commands.
- The types involved
OneBeyond.Studio.Obelisk.WebApi.Controllers.AuthController→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.SignInTfaOneBeyond.Studio.Obelisk.WebApi.Controllers.AuthController→OneBeyond.Studio.Obelisk.Authentication.Domain.TfaAuthentication.Commands.SignInTfaWithRecoveryCode
- Direction
- WebApi.Controllers uses Authentication.Domain.TfaAuthentication.Commands, so a change to Authentication.Domain.TfaAuthentication.Commands can break WebApi.Controllers, while a change to WebApi.Controllers can't break Authentication.Domain.TfaAuthentication.Commands.
- Position
- Below the diagonal: WebApi.Controllers uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 47 | High / Critical |
| A05:2025 — Injection | 26 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | High / Critical |
| A07:2025 — Authentication Failures | 8 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 33 Orphaned file finding(s) in Knowledge Freshness — start with ServiceCollectionExtensions.cs (2), UsersController.cs, FromMixedSourceOperationTransformer.cs; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.1 pts | Low | ADR Quality |
| Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED. | +2.1 pts | Low | REDACTED Scanning |
| Resolve the 1 redundant comment finding(s) in Comment Value — start with Program.cs. | +2.0 pts | Low | Comment Value |
| Resolve the 33 Orphaned file finding(s) in Knowledge Freshness — start with ServiceCollectionExtensions.cs (2), UsersController.cs, FromMixedSourceOperationTransformer.cs. | +3.8 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.2 pts | Medium | Architecture documentation |
| Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). | +1.5 pts | Low | Dependency Hygiene |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.4 pts | Medium | Documentation (README) |
| Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. | +0.8 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.8 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 4.2 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.6 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.1 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.2 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 5.7 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/FromMixedSourceOperationTransformer.cs | 6.3 | Mixed | Cognitive Complexity: FromMixedSourceOperationTransformer.TransformAsync (cognitive 19) |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 91 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 — 91 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, 206 of 264 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
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/VersionInfoDocumentTransformer.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via AspireAppHost (REDACTED). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
- 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was FromMixedSourceOperationTransformer.TransformAsync at 19.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with FromMixedSourceOperationTransformer.TransformAsync (cognitive 19). — Refactoring it lifts Cognitive Complexity from 9.7 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
4 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with SendResetPasswordEmailHandler.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with GetUserDto.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with UnlockUserHandler.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
11 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling — start with OneBeyond.Studio.Obelisk.Authentication.Domain.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 15 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 6.6% — 28 file(s) below 50% · 4 method(s) over the CRAP-30 risk line.
What to do
- Resolve the 28 Low coverage finding(s) in Code Coverage — start with AzureADSignInProvider.cs, SignInProviderFactory.cs, AuthorizeSummaryOperationTransformer.cs. — One of this dimension's main actionable groups (28 warning-level).
- Resolve the 1 No test project references OneBeyond.Studio.Obelisk.Workers finding(s) in Code Coverage — start with OneBeyond.Studio.Obelisk.Workers.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references OneBeyond.Studio.Obelisk.AppHost finding(s) in Code Coverage — start with REDACTED. — 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
3 test methods: 3 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, 1 mock references across 3 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
44 outdated, 1 vulnerable, 2 deprecated packages.
What to do
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 250 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 47 direct `PackageReference`(s), and 203 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.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/OneBeyond.Studio.Obelisk.ServiceDefaults/Extensions.cs. Counted over 35 of the 220 production source files in this repository: 181 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
D17 · Explicit Debt
2 deducted debt markers + 11 dead symbols across 6960 LoC in the .NET projects (0.4/KLoC) → score 9.1.
What to do
- Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 11 Dead code finding(s) in Explicit Debt — start with AssemblyMark.cs (3), ISignInProvider.cs (2), StringHelpers.cs. — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 1 ObsoleteWithoutCallers finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-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
11 projects, 224 source files, 7136 hand-written lines of code (6960 production / 176 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 1462 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 12 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 10 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (2 contexts). Contexts: OneBeyond.Studio.Obelisk, OneBeyond.Studio.Obelisk.Authentication.
D24 · Comment Value
1 of 58 judged comments only repeat the code they sit on (1.7 %). 2 comment(s) in another language or script were not judged.
What to do
- Resolve the 1 redundant comment finding(s) in Comment Value — start with Program.cs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 11 projects flagged as possibly oversized/incoherent.
D27 · Navigability
95 % of calls cross a namespace and 4 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
26 finding(s): 0 critical, 12 high, 14 medium, 0 low. 11 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `REDACTED` (line 1, line 6), `REDACTED` (line 1, line 6), `src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/VersionInfoDocumentTransformer.cs` (line 14, line 15) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 1 of those file(s) — `src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/VersionInfoDocumentTransformer.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- No action in Static Analysis (SAST) — all 11 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 (11 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
9 finding(s): 1 critical, 4 high, 2 medium, 2 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
47 finding(s): 3 critical, 4 high, 24 medium, 16 low.
What to do
- Resolve the 24 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (8), REDACTED (6), REDACTED (3). — One of this dimension's main actionable groups (24 warning-level).
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 Critical IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D34 · Knowledge Freshness
33 of 39 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/DependencyInjection/ServiceCollectionExtensions.cs. Counted over 39 of the 220 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 33 Orphaned file finding(s) in Knowledge Freshness — start with ServiceCollectionExtensions.cs (2), UsersController.cs, FromMixedSourceOperationTransformer.cs. — One of this dimension's main actionable groups (33 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
0 of 430 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
- The namespaces OneBeyond.Studio.Obelisk.Infrastructure.Data ↔ OneBeyond.Studio.Obelisk.Infrastructure.Data.BulkUpdate depend on each other. The lightest dependency in the cycle is OneBeyond.Studio.Obelisk.Infrastructure.Data → OneBeyond.Studio.Obelisk.Infrastructure.Data.BulkUpdate (OneBeyond.Studio.Obelisk.Infrastructure.Data.RWBulkRepository → OneBeyond.Studio.Obelisk.Infrastructure.Data.BulkUpdate.EntityTypeMapping, 2 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/OneBeyond.Studio.Obelisk.Infrastructure/Data/RWBulkRepository.cs:17
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
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.
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
- `EmailTemplate`'s public constructor takes `id`, `subject`, `body`, `description` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `EmailTemplate` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/OneBeyond.Studio.Obelisk.Domain/Features/EmailTemplates/Entities/EmailTemplate.cs:9
- `User`'s public constructor takes `loginId`, `userName`, `email`, `roleId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `User` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/User.cs:9
- `UserLoginLog`'s public constructor takes `username`, `status` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `UserLoginLog` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserLoginLog.cs:9
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `UserCreated.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/OneBeyond.Studio.Obelisk.Domain/Features/Users/DomainEvents/UserCreated.cs:21
- `UserBase.LoginId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserBase.cs:45
- `UserBase.TypeId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserBase.cs:52
- `UserBase.RoleId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserBase.cs:53
- `AuthToken.LoginId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/Entities/AuthToken.cs:32
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `EmailTemplate` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/OneBeyond.Studio.Obelisk.Domain/Features/EmailTemplates/Entities/EmailTemplate.cs:6
- `UserLoginLog` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserLoginLog.cs:7
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — src/OneBeyond.Studio.Obelisk.WebApi/Program.cs:242
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- 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 an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 9 of 9 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- Only 5/7 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 7, 3 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.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:7
What to do
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `ValidateAudience = false` means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. — src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/JwtAuthentication/DependencyInjection/ServiceCollectionExtensions.cs:31
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. — src/OneBeyond.Studio.Obelisk.WebApi/Program.cs:53
What to do
- Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
- Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 63/67 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. — src/OneBeyond.Studio.Obelisk.Application/Services/EmailTemplateService/EmailTemplateService.cs:21
- No CancellationToken parameter, and the token `httpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `httpContext.RequestAborted` on, or take a CancellationToken. (×2) — src/OneBeyond.Studio.Obelisk.WebApi/Extensions/UnhandledExceptionExtension.cs:18, REDACTED:19
- 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
- Its signature is fixed by the framework, and the token it carries (`httpContext.RequestAborted`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `httpContext.RequestAborted` to them. — src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/UnitOfWork/ApplicationBuilderExtensions.cs:42
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. — src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/CommandHandlers/ResetPasswordHandler.cs:41
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- ~1.6 `!` suppressions per 1k syntax nodes — 75 suppression(s) across the 46964 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 | 87% | Strong | Solid. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 57% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 65% | Adequate — gated by D8, D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 60% | Adequate — gated by D31 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 62% | Adequate — gated by DM2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 3 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.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 3 control(s) we could not find positive evidence for
- 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.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 35 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1178 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 4 event handler(s); 35 CQRS handler(s)
- ED5 Idempotency — not scored — 6 of 9 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 aggregate(s) with Apply/When folds)
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P9 Domain vs controller coverage — coverage data present for 45 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 33 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle src/OneBeyond.Studio.Obelisk.Infrastructure/Data/RWBulkRepository.cs:17
- NoWarnInCsproj REDACTED:7
- REDACTED
- REDACTED
- REDACTED
Serious — 107 finding(s)
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/SignInProviders/AzureADSignInProvider.cs src/OneBeyond.Studio.Obelisk.WebApi/SignInProviders/AzureADSignInProvider.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/SignInProviders/SignInProviderFactory.cs src/OneBeyond.Studio.Obelisk.WebApi/SignInProviders/SignInProviderFactory.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/AuthorizeSummaryOperationTransformer.cs src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/AuthorizeSummaryOperationTransformer.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/BearerSecuritySchemeTransformer.cs src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/BearerSecuritySchemeTransformer.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/FromMixedSourceOperationTransformer.cs src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/FromMixedSourceOperationTransformer.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/SmartEnumSchemaTransformer.cs src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/SmartEnumSchemaTransformer.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/VersionInfoDocumentTransformer.cs src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/VersionInfoDocumentTransformer.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/UnitOfWork/ApplicationBuilderExtensions.cs src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/UnitOfWork/ApplicationBuilderExtensions.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/Security/SecurityHeadersBuilder.cs src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/Security/SecurityHeadersBuilder.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/Security/SecurityHeadersMiddleware.cs src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/Security/SecurityHeadersMiddleware.cs:1
- Low coverage: REDACTED REDACTED:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/HostedServices/DomainEventRelayJob.cs src/OneBeyond.Studio.Obelisk.WebApi/HostedServices/DomainEventRelayJob.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Helpers/ClientApplicationLinkGenerator.cs src/OneBeyond.Studio.Obelisk.WebApi/Helpers/ClientApplicationLinkGenerator.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Helpers/ControllerHelpers.cs src/OneBeyond.Studio.Obelisk.WebApi/Helpers/ControllerHelpers.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Helpers/UIBuildFileHelpers.cs src/OneBeyond.Studio.Obelisk.WebApi/Helpers/UIBuildFileHelpers.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Extensions/HealthCheckExtensions.cs src/OneBeyond.Studio.Obelisk.WebApi/Extensions/HealthCheckExtensions.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Extensions/HostExtensions.cs src/OneBeyond.Studio.Obelisk.WebApi/Extensions/HostExtensions.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Extensions/QueryParametersExtension.cs src/OneBeyond.Studio.Obelisk.WebApi/Extensions/QueryParametersExtension.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Extensions/UnhandledExceptionExtension.cs src/OneBeyond.Studio.Obelisk.WebApi/Extensions/UnhandledExceptionExtension.cs:1
- Low coverage: REDACTED REDACTED:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Controllers/ControllerBase.cs src/OneBeyond.Studio.Obelisk.WebApi/Controllers/ControllerBase.cs:1
- Low coverage: REDACTED REDACTED:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Controllers/TFAController.cs src/OneBeyond.Studio.Obelisk.WebApi/Controllers/TFAController.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Controllers/UsersController.cs src/OneBeyond.Studio.Obelisk.WebApi/Controllers/UsersController.cs:1
- Low coverage: src/OneBeyond.Studio.Obelisk.WebApi/Dto/SignInJwtDto.cs src/OneBeyond.Studio.Obelisk.WebApi/Dto/SignInJwtDto.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dead code: AssemblyMark src/OneBeyond.Studio.Obelisk.Application/AssemblyMark.cs:3
- Dead code: StringHelpers src/OneBeyond.Studio.Obelisk.Domain.Tests/Helpers/StringHelpers.cs:6
- Dead code: AssemblyMark src/OneBeyond.Studio.Obelisk.Domain/AssemblyMark.cs:3
- Dead code: GetPropertyMapping src/OneBeyond.Studio.Obelisk.Infrastructure/Data/BulkUpdate/EntityTypeMapping.cs:31
- Dead code: Exclude src/OneBeyond.Studio.Obelisk.Infrastructure/Data/BulkUpdate/PropertyMapping.cs:64
- Dead code: UIBuildFileHelpers src/OneBeyond.Studio.Obelisk.WebApi/Helpers/UIBuildFileHelpers.cs:7
- Dead code: Error src/OneBeyond.Studio.Obelisk.WebApi/Requests/Result.cs:5
- Dead code: GetProviderLoginId src/OneBeyond.Studio.Obelisk.WebApi/SignInProviders/ISignInProvider.cs:8
- Dead code: GetEmail src/OneBeyond.Studio.Obelisk.WebApi/SignInProviders/ISignInProvider.cs:10
- Dead code: SignInProviderFactory src/OneBeyond.Studio.Obelisk.WebApi/SignInProviders/SignInProviderFactory.cs:6
- Dead code: AssemblyMark src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/AssemblyMark.cs:3
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Constructible in an invalid state: EmailTemplate src/OneBeyond.Studio.Obelisk.Domain/Features/EmailTemplates/Entities/EmailTemplate.cs:9
- Constructible in an invalid state: User src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/User.cs:9
- Constructible in an invalid state: UserLoginLog src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserLoginLog.cs:9
- Async method without CancellationToken: GetTemplateByKeyAsync src/OneBeyond.Studio.Obelisk.Application/Services/EmailTemplateService/EmailTemplateService.cs:21
- Async method without CancellationToken: LogUnhandledException src/OneBeyond.Studio.Obelisk.WebApi/Extensions/UnhandledExceptionExtension.cs:18
- Async method without CancellationToken: HandleDomainException REDACTED:19
- Deprecated: xunit REDACTED:60
- Deprecated: AspNetCore.HealthChecks.AzureStorage REDACTED:12
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Anemic entity: EmailTemplate src/OneBeyond.Studio.Obelisk.Domain/Features/EmailTemplates/Entities/EmailTemplate.cs:6
- Anemic entity: UserLoginLog src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserLoginLog.cs:7
- FromMixedSourceOperationTransformer.TransformAsync (cognitive 19) src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/FromMixedSourceOperationTransformer.cs:25
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) src/OneBeyond.Studio.Obelisk.Application/Features/Users/CommandHandlers/SendResetPasswordEmailHandler.cs:66
- Duplicated block (8 lines × 2) src/OneBeyond.Studio.Obelisk.Application/Features/Users/Dto/GetUserDto.cs:7
- Duplicated block (6 lines × 2) src/OneBeyond.Studio.Obelisk.Application/Features/Users/CommandHandlers/UnlockUserHandler.cs:22
- Duplicated block (7 lines × 6) src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/CommandHandlers/ChangePasswordHandler.cs:22
- Off the main sequence: OneBeyond.Studio.Obelisk.Authentication.Domain src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Domain/OneBeyond.Studio.Obelisk.Authentication.Domain.csproj:1
- No test project references OneBeyond.Studio.Obelisk.Workers src/OneBeyond.Studio.Obelisk.Workers/OneBeyond.Studio.Obelisk.Workers.csproj
- No test project references OneBeyond.Studio.Obelisk.AppHost REDACTED
- CRAP 210: FromMixedSourceOperationTransformer.TransformAsync src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/FromMixedSourceOperationTransformer.cs:25
- CRAP 72: AuthorizeSummaryOperationTransformer.TransformAsync src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/AuthorizeSummaryOperationTransformer.cs:28
- CRAP 56: ExceptionHandlingExtension.HandleDomainException REDACTED:19
- CRAP 42: SecurityHeadersBuilder.AddSecurityPolicyFromConfiguration src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/Security/SecurityHeadersBuilder.cs:16
- Coverage collected but not gated
- Token validation disabled src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/JwtAuthentication/DependencyInjection/ServiceCollectionExtensions.cs:31
- Async method drops its ambient CancellationToken: Invoke src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/UnitOfWork/ApplicationBuilderExtensions.cs:42
Minor — 76 finding(s)
- Orphaned file src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/DependencyInjection/ServiceCollectionExtensions.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.WebApi/Controllers/UsersController.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/FromMixedSourceOperationTransformer.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Infrastructure/Data/RWBulkRepository.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Infrastructure/Data/BulkUpdate/BulkUpdateConfiguration.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/Security/Constants/SecurityMiddlewareConstants.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Application/Services/AuthenticationFlows/AuthenticationFlowHandler.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/Security/SecurityHeadersBuilder.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.WebApi/Controllers/TFAController.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/Services/JwtAuthentication/JwtTokenService.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/CommandHandlers/SignInViaPasswordHandler.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Domain/Features/EmailTemplates/Entities/PredefinedEmailTemplates.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Application/Features/Users/DomainEventHandlers/NewUserPasswordEmailSender.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/Services/AuthenticationFlows/CookieAuthenticationFlow.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/AuthorizeSummaryOperationTransformer.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.WebApi/Controllers/QBasedController.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/JwtAuthentication/CommandHandlers/RefreshJwtTokenHandler.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Application/Features/Users/CommandHandlers/SendResetPasswordEmailHandler.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.WebApi/Middlewares/ErrorResultGeneratorMiddleware.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.WebApi/AmbientContexts/ApplicationClaimsIdentityFactory.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/CommandHandlers/SignInHandler.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Infrastructure/DependencyInjection/ServiceCollectionExtensions.cs:1
- Orphaned file src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/CommandHandlers/ResetPasswordHandler.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/BearerSecuritySchemeTransformer.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Primitive id on a domain type: UserCreated.UserId src/OneBeyond.Studio.Obelisk.Domain/Features/Users/DomainEvents/UserCreated.cs:21
- Primitive id on a domain type: UserBase.LoginId src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserBase.cs:45
- Primitive id on a domain type: UserBase.TypeId src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserBase.cs:52
- Primitive id on a domain type: UserBase.RoleId src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserBase.cs:53
- Primitive id on a domain type: AuthToken.LoginId src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/Entities/AuthToken.cs:32
- REDACTED
- REDACTED
- No app-layer HTTPS enforcement detected
- No app-layer HTTPS enforcement detected src/OneBeyond.Studio.Obelisk.WebApi/Program.cs:53
- Partial data-retention evidence
- Outdated: coverlet.collector REDACTED:56
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- ObsoleteWithoutCallers REDACTED:63
- No ADRs found
- redundant comment src/OneBeyond.Studio.Obelisk.WebApi/Program.cs:55
- REDACTED
- Dormant codebase
- Commented-out code src/OneBeyond.Studio.Obelisk.WebApi/Program.cs:242
- No ADRs
- Logging is not universal
- Dependabot does not watch github-actions REDACTED:7
- No rollback/health safety
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
- Interpolated log message defeats structured logging src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/CommandHandlers/ResetPasswordHandler.cs:41
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 48 finding(s)
- Outdated: Aspire.Hosting.Azure.Functions
- Outdated: OneBeyond.Studio.Application.SharedKernel
- Outdated: OneBeyond.Studio.EmailProviders.Domain
- Outdated: OneBeyond.Studio.TemplateRendering
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: xunit.runner.visualstudio
- Outdated: OneBeyond.Studio.Domain.SharedKernel
- Outdated: OneBeyond.Studio.FileStorage.Domain
- Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore
- Outdated: Microsoft.EntityFrameworkCore.Tools
- Outdated: OneBeyond.Studio.DataAccess.EFCore
- Outdated: Azure.Monitor.OpenTelemetry.AspNetCore
- Outdated: Microsoft.Extensions.Http.Resilience
- Outdated: Microsoft.Extensions.ServiceDiscovery
- Outdated: OpenTelemetry.Exporter.OpenTelemetryProtocol
- Outdated: OpenTelemetry.Extensions.Hosting
- Outdated: OpenTelemetry.Instrumentation.AspNetCore
- Outdated: OpenTelemetry.Instrumentation.Http
- Outdated: OpenTelemetry.Instrumentation.Runtime
- Outdated: AwesomeAssertions
- Outdated: Microsoft.AspNetCore.Mvc.Testing
- Outdated: Moq
- Outdated: Asp.Versioning.Mvc.ApiExplorer
- Outdated: Autofac.Extensions.DependencyInjection
- Outdated: Microsoft.AspNetCore.OpenApi
- doc comments repeat the names src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Application/Repositories/AuthUsers/IAuthTokenRepository.cs:10
- doc comments repeat the names src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Domain/AuthenticationFlows/IAuthenticationFlowHandler.cs:12
- doc comments repeat the names src/OneBeyond.Studio.Obelisk.Infrastructure/DependencyInjection/IDataAccessBuilder.cs:11
- doc comments repeat the names REDACTED:52
- Mock framework: Moq
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-b411e9f166a94c7da22f88e33d1e7ba5/history.json --exit-code 0 --source . | 2 | 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-b411e9f166a94c7da22f88e33d1e7ba5/tree.json --exit-code 0 --source . | 2 | 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/OneBeyond.Studio.Obelisk.Infrastructure/Migrations . | 26 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list OneBeyond.Studio.Obelisk.slnx package --vulnerable --include-transitive --format json | 9 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 47 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/OneBeyond.Studio.Obelisk.WebApi/OpenApi/VersionInfoDocumentTransformer.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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-f4fcd16d039544d0912848dd863cbd9d | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Email — 11 field(s)
- CreateUserDto.Email src/OneBeyond.Studio.Obelisk.Application/Features/Users/Dto/CreateUserDto.cs:5
- GetUserDto.Email src/OneBeyond.Studio.Obelisk.Application/Features/Users/Dto/GetUserDto.cs:9
- ListUsersDto.Email src/OneBeyond.Studio.Obelisk.Application/Features/Users/Dto/ListUsersDto.cs:9
- CreateLogin.Email src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Domain/Commands/CreateLogin.cs:24
- GenerateResetPasswordTokenByEmail.Email src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Domain/Commands/GenerateResetPasswordTokenByEmail.cs:15
- UpdateLogin.Email src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Domain/Commands/UpdateLogin.cs:26
- TfaKey.Email src/OneBeyond.Studio.Obelisk.Authentication/OneBeyond.Studio.Obelisk.Authentication.Domain/TfaAuthentication/TfaKey.cs:25
- CreateUser.Email src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Commands/CreateUser.cs:28
- UpdateUser.Email src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Commands/UpdateUser.cs:28
- UserBase.Email src/OneBeyond.Studio.Obelisk.Domain/Features/Users/Entities/UserBase.cs:48
- ForgotPasswordRequest.Email src/OneBeyond.Studio.Obelisk.WebApi/Requests/Auth/ForgotPasswordRequest.cs:5