Executive summary
QuinntyneBrown/slackish-v2 falls short of our standard for production, in part because the project has no automated tests. It scores 26 out of 100 and is rated Weak, and ten of its 20 critical findings are security problems.
Production Readiness, at 8, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 15 points. Fixing the password or key in the code comes next, worth about 11 points. Raising Production Readiness to 70 would lift the score to about 42.
Four passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Two known security holes in the packages the code depends on can be used by attackers, and the project has no automated tests, so a change can break it without warning. Replacing each exposed password or key, adding automated tests and updating the vulnerable packages would close these risks. Hashing passwords with a password-hashing function such as Argon2, bcrypt or PBKDF2 would fix the two places where passwords are scrambled with a fast general-purpose hash, and loading the key from a secret store instead of the code would deal with the encryption key written into the code. The eight data fields that are written but never read need removing.
The product code is 3,752 lines, about €2,900 to rebuild.
If Production Readiness rose from 8 to 70, the lowest score rated Strong, the score would rise from 26 to about 42.
New since the last survey: 3 findings
- Stateful singletons · Process-global static state: UnityConfiguration UnityConfiguration.cs
- Stateful singletons · Process-global static state: MemoryCache Features/Core/MemoryCache.cs
- Outbound HTTP resilience · Outbound HTTP without resilience UnityConfiguration.cs
Rebuild cost: about €2,900 · Estimate
| Cost to rebuild | €970 to €4,700, for 16 to 50 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 26. 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: 3,752 lines of product code |
| Comment lines | The estimate prices 3,726 lines. Comment lines count towards the size of 3,752 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 ClientApp | 2 ClientApp.app.app_component | 3 ClientApp.app.app_module | 4 ClientApp.app.conversations.conversation-about_component | 5 ClientApp.app.conversations.conversation-detail-header_component | 6 ClientApp.app.conversations.conversation-detail_component | 7 ClientApp.app.conversations.conversation-header_component | 8 ClientApp.app.conversations.conversation-list_component | 9 ClientApp.app.conversations.conversation-messages_component | 10 ClientApp.app.conversations.conversation_model | 11 ClientApp.app.conversations.conversations_module | 12 ClientApp.app.landing-page_component | 13 ClientApp.app.messages.message-form_component | 14 ClientApp.app.messages.messages_module | 15 ClientApp.app.profiles.profile_model | 16 ClientApp.app.shared.components.popover_component | 17 ClientApp.app.shared.services.login-redirect_service | 18 ClientApp.app.shared.services.storage_service | 19 Slackish.Data.Model | 20 ClientApp.app.conversations.conversation-list-header_component | 21 ClientApp.app.shared.services.auth-guard_service | 22 ClientApp.app.shared.services.http_service | 23 ClientApp.app.shared.services.signalr-message-queue-factory | 24 ClientApp.app.teams.discover-team-page_component | 25 Slackish.Data | 26 ClientApp.app.conversations.conversations_service | 27 ClientApp.app.profiles.profile_service | 28 ClientApp.app.shared.services.authentication_service | 29 ClientApp.app.teams.teams_service | 30 Slackish.Data.Migrations | 31 Slackish.Features.Core | 32 Slackish.Migrations | 33 Slackish.Security | 34 ClientApp.app.conversations.conversation-page_component | 35 ClientApp.app.profiles.login-page_component | 36 ClientApp.app.teams.create-team-page_component | 37 Slackish.Features.Messages | 38 Slackish.Features.Profiles | 39 Slackish.Features.Teams | 40 Slackish.Features.Conversations |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ClientApp | ||||||||||||||||||||||||||||||||||||||||
| 2 ClientApp.app.app_component | ||||||||||||||||||||||||||||||||||||||||
| 3 ClientApp.app.app_module | ||||||||||||||||||||||||||||||||||||||||
| 4 ClientApp.app.conversations.conversation-about_component | ||||||||||||||||||||||||||||||||||||||||
| 5 ClientApp.app.conversations.conversation-detail-header_component | ||||||||||||||||||||||||||||||||||||||||
| 6 ClientApp.app.conversations.conversation-detail_component | ||||||||||||||||||||||||||||||||||||||||
| 7 ClientApp.app.conversations.conversation-header_component | ||||||||||||||||||||||||||||||||||||||||
| 8 ClientApp.app.conversations.conversation-list_component | ||||||||||||||||||||||||||||||||||||||||
| 9 ClientApp.app.conversations.conversation-messages_component | ||||||||||||||||||||||||||||||||||||||||
| 10 ClientApp.app.conversations.conversation_model | ||||||||||||||||||||||||||||||||||||||||
| 11 ClientApp.app.conversations.conversations_module | ||||||||||||||||||||||||||||||||||||||||
| 12 ClientApp.app.landing-page_component | ||||||||||||||||||||||||||||||||||||||||
| 13 ClientApp.app.messages.message-form_component | ||||||||||||||||||||||||||||||||||||||||
| 14 ClientApp.app.messages.messages_module | ||||||||||||||||||||||||||||||||||||||||
| 15 ClientApp.app.profiles.profile_model | ||||||||||||||||||||||||||||||||||||||||
| 16 ClientApp.app.shared.components.popover_component | ||||||||||||||||||||||||||||||||||||||||
| 17 ClientApp.app.shared.services.login-redirect_service | ||||||||||||||||||||||||||||||||||||||||
| 18 ClientApp.app.shared.services.storage_service | ||||||||||||||||||||||||||||||||||||||||
| 19 Slackish.Data.Model | ||||||||||||||||||||||||||||||||||||||||
| 20 ClientApp.app.conversations.conversation-list-header_component | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 ClientApp.app.shared.services.auth-guard_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 ClientApp.app.shared.services.http_service | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 ClientApp.app.shared.services.signalr-message-queue-factory | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 ClientApp.app.teams.discover-team-page_component | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Slackish.Data | 14 | |||||||||||||||||||||||||||||||||||||||
| 26 ClientApp.app.conversations.conversations_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 ClientApp.app.profiles.profile_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 ClientApp.app.shared.services.authentication_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 ClientApp.app.teams.teams_service | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 Slackish.Data.Migrations | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 Slackish.Features.Core | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 Slackish.Migrations | 4 | |||||||||||||||||||||||||||||||||||||||
| 33 Slackish.Security | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 ClientApp.app.conversations.conversation-page_component | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 ClientApp.app.profiles.login-page_component | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 ClientApp.app.teams.create-team-page_component | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Slackish.Features.Messages | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 Slackish.Features.Profiles | 2 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 Slackish.Features.Teams | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 40 Slackish.Features.Conversations | 1 | 1 | 3 | 1 | 1 |
20→16 ClientApp.app.conversations.conversation-list-header_component uses ClientApp.app.shared.components.popover_component✕
- Connections
- 1 pair of types, where a type in ClientApp.app.conversations.conversation-list-header_component uses a type in ClientApp.app.shared.components.popover_component.
- The types involved
ClientApp.app.conversations.conversation-list-header_component.ConversationListHeaderComponent→ClientApp.app.shared.components.popover_component.PopoverComponent
- Direction
- ClientApp.app.conversations.conversation-list-header_component uses ClientApp.app.shared.components.popover_component, so a change to ClientApp.app.shared.components.popover_component can break ClientApp.app.conversations.conversation-list-header_component, while a change to ClientApp.app.conversations.conversation-list-header_component can't break ClientApp.app.shared.components.popover_component.
- Position
- Below the diagonal: ClientApp.app.conversations.conversation-list-header_component uses a module listed above it, which is the healthy direction.
21→17 ClientApp.app.shared.services.auth-guard_service uses ClientApp.app.shared.services.login-redirect_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.shared.services.auth-guard_service uses a type in ClientApp.app.shared.services.login-redirect_service.
- The types involved
ClientApp.app.shared.services.auth-guard_service.AuthGuardService→ClientApp.app.shared.services.login-redirect_service.LoginRedirectService
- Direction
- ClientApp.app.shared.services.auth-guard_service uses ClientApp.app.shared.services.login-redirect_service, so a change to ClientApp.app.shared.services.login-redirect_service can break ClientApp.app.shared.services.auth-guard_service, while a change to ClientApp.app.shared.services.auth-guard_service can't break ClientApp.app.shared.services.login-redirect_service.
- Position
- Below the diagonal: ClientApp.app.shared.services.auth-guard_service uses a module listed above it, which is the healthy direction.
21→18 ClientApp.app.shared.services.auth-guard_service uses ClientApp.app.shared.services.storage_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.shared.services.auth-guard_service uses a type in ClientApp.app.shared.services.storage_service.
- The types involved
ClientApp.app.shared.services.auth-guard_service.AuthGuardService→ClientApp.app.shared.services.storage_service.Storage
- Direction
- ClientApp.app.shared.services.auth-guard_service uses ClientApp.app.shared.services.storage_service, so a change to ClientApp.app.shared.services.storage_service can break ClientApp.app.shared.services.auth-guard_service, while a change to ClientApp.app.shared.services.auth-guard_service can't break ClientApp.app.shared.services.storage_service.
- Position
- Below the diagonal: ClientApp.app.shared.services.auth-guard_service uses a module listed above it, which is the healthy direction.
22→18 ClientApp.app.shared.services.http_service uses ClientApp.app.shared.services.storage_service✕
- Connections
- 2 pairs of types, where a type in ClientApp.app.shared.services.http_service uses a type in ClientApp.app.shared.services.storage_service.
- The types involved
ClientApp.app.shared.services.http_service.HttpService→ClientApp.app.shared.services.storage_service.StorageClientApp.app.shared.services.http_service.SecuredHttpService→ClientApp.app.shared.services.storage_service.Storage
- Direction
- ClientApp.app.shared.services.http_service uses ClientApp.app.shared.services.storage_service, so a change to ClientApp.app.shared.services.storage_service can break ClientApp.app.shared.services.http_service, while a change to ClientApp.app.shared.services.http_service can't break ClientApp.app.shared.services.storage_service.
- Position
- Below the diagonal: ClientApp.app.shared.services.http_service uses a module listed above it, which is the healthy direction.
23→18 ClientApp.app.shared.services.signalr-message-queue-factory uses ClientApp.app.shared.services.storage_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.shared.services.signalr-message-queue-factory uses a type in ClientApp.app.shared.services.storage_service.
- The types involved
ClientApp.app.shared.services.signalr-message-queue-factory.SignalRMessageQueueFactory→ClientApp.app.shared.services.storage_service.Storage
- Direction
- ClientApp.app.shared.services.signalr-message-queue-factory uses ClientApp.app.shared.services.storage_service, so a change to ClientApp.app.shared.services.storage_service can break ClientApp.app.shared.services.signalr-message-queue-factory, while a change to ClientApp.app.shared.services.signalr-message-queue-factory can't break ClientApp.app.shared.services.storage_service.
- Position
- Below the diagonal: ClientApp.app.shared.services.signalr-message-queue-factory uses a module listed above it, which is the healthy direction.
24→18 ClientApp.app.teams.discover-team-page_component uses ClientApp.app.shared.services.storage_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.teams.discover-team-page_component uses a type in ClientApp.app.shared.services.storage_service.
- The types involved
ClientApp.app.teams.discover-team-page_component.DiscoverTeamPageComponent→ClientApp.app.shared.services.storage_service.Storage
- Direction
- ClientApp.app.teams.discover-team-page_component uses ClientApp.app.shared.services.storage_service, so a change to ClientApp.app.shared.services.storage_service can break ClientApp.app.teams.discover-team-page_component, while a change to ClientApp.app.teams.discover-team-page_component can't break ClientApp.app.shared.services.storage_service.
- Position
- Below the diagonal: ClientApp.app.teams.discover-team-page_component uses a module listed above it, which is the healthy direction.
25→19 Slackish.Data uses Slackish.Data.Model✕
- Connections
- 14 pairs of types, where a type in Slackish.Data uses a type in Slackish.Data.Model.
- The types involved
Slackish.Data.ISlackishContext→Slackish.Data.Model.ChannelSlackish.Data.ISlackishContext→Slackish.Data.Model.ConversationSlackish.Data.ISlackishContext→Slackish.Data.Model.MessageSlackish.Data.ISlackishContext→Slackish.Data.Model.ProfileSlackish.Data.ISlackishContext→Slackish.Data.Model.TeamSlackish.Data.ISlackishContext→Slackish.Data.Model.TenantSlackish.Data.ISlackishContext→Slackish.Data.Model.UserSlackish.Data.SlackishContext→Slackish.Data.Model.ChannelSlackish.Data.SlackishContext→Slackish.Data.Model.ConversationSlackish.Data.SlackishContext→Slackish.Data.Model.MessageSlackish.Data.SlackishContext→Slackish.Data.Model.ProfileSlackish.Data.SlackishContext→Slackish.Data.Model.TeamSlackish.Data.SlackishContext→Slackish.Data.Model.TenantSlackish.Data.SlackishContext→Slackish.Data.Model.User
- Direction
- Slackish.Data uses Slackish.Data.Model, so a change to Slackish.Data.Model can break Slackish.Data, while a change to Slackish.Data can't break Slackish.Data.Model.
- Position
- Below the diagonal: Slackish.Data uses a module listed above it, which is the healthy direction.
26→22 ClientApp.app.conversations.conversations_service uses ClientApp.app.shared.services.http_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.conversations.conversations_service uses a type in ClientApp.app.shared.services.http_service.
- The types involved
ClientApp.app.conversations.conversations_service.ConversationsService→ClientApp.app.shared.services.http_service.SecuredHttpService
- Direction
- ClientApp.app.conversations.conversations_service uses ClientApp.app.shared.services.http_service, so a change to ClientApp.app.shared.services.http_service can break ClientApp.app.conversations.conversations_service, while a change to ClientApp.app.conversations.conversations_service can't break ClientApp.app.shared.services.http_service.
- Position
- Below the diagonal: ClientApp.app.conversations.conversations_service uses a module listed above it, which is the healthy direction.
27→22 ClientApp.app.profiles.profile_service uses ClientApp.app.shared.services.http_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.profiles.profile_service uses a type in ClientApp.app.shared.services.http_service.
- The types involved
ClientApp.app.profiles.profile_service.ProfilesService→ClientApp.app.shared.services.http_service.SecuredHttpService
- Direction
- ClientApp.app.profiles.profile_service uses ClientApp.app.shared.services.http_service, so a change to ClientApp.app.shared.services.http_service can break ClientApp.app.profiles.profile_service, while a change to ClientApp.app.profiles.profile_service can't break ClientApp.app.shared.services.http_service.
- Position
- Below the diagonal: ClientApp.app.profiles.profile_service uses a module listed above it, which is the healthy direction.
28→18 ClientApp.app.shared.services.authentication_service uses ClientApp.app.shared.services.storage_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.shared.services.authentication_service uses a type in ClientApp.app.shared.services.storage_service.
- The types involved
ClientApp.app.shared.services.authentication_service.AuthenticationService→ClientApp.app.shared.services.storage_service.Storage
- Direction
- ClientApp.app.shared.services.authentication_service uses ClientApp.app.shared.services.storage_service, so a change to ClientApp.app.shared.services.storage_service can break ClientApp.app.shared.services.authentication_service, while a change to ClientApp.app.shared.services.authentication_service can't break ClientApp.app.shared.services.storage_service.
- Position
- Below the diagonal: ClientApp.app.shared.services.authentication_service uses a module listed above it, which is the healthy direction.
28→22 ClientApp.app.shared.services.authentication_service uses ClientApp.app.shared.services.http_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.shared.services.authentication_service uses a type in ClientApp.app.shared.services.http_service.
- The types involved
ClientApp.app.shared.services.authentication_service.AuthenticationService→ClientApp.app.shared.services.http_service.HttpService
- Direction
- ClientApp.app.shared.services.authentication_service uses ClientApp.app.shared.services.http_service, so a change to ClientApp.app.shared.services.http_service can break ClientApp.app.shared.services.authentication_service, while a change to ClientApp.app.shared.services.authentication_service can't break ClientApp.app.shared.services.http_service.
- Position
- Below the diagonal: ClientApp.app.shared.services.authentication_service uses a module listed above it, which is the healthy direction.
29→22 ClientApp.app.teams.teams_service uses ClientApp.app.shared.services.http_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.teams.teams_service uses a type in ClientApp.app.shared.services.http_service.
- The types involved
ClientApp.app.teams.teams_service.TeamsService→ClientApp.app.shared.services.http_service.SecuredHttpService
- Direction
- ClientApp.app.teams.teams_service uses ClientApp.app.shared.services.http_service, so a change to ClientApp.app.shared.services.http_service can break ClientApp.app.teams.teams_service, while a change to ClientApp.app.teams.teams_service can't break ClientApp.app.shared.services.http_service.
- Position
- Below the diagonal: ClientApp.app.teams.teams_service uses a module listed above it, which is the healthy direction.
30→25 Slackish.Data.Migrations uses Slackish.Data✕
- Connections
- 2 pairs of types, where a type in Slackish.Data.Migrations uses a type in Slackish.Data.
- The types involved
Slackish.Data.Migrations.ChannelConfiguration→Slackish.Data.SlackishContextSlackish.Data.Migrations.TeamConfiguration→Slackish.Data.SlackishContext
- Direction
- Slackish.Data.Migrations uses Slackish.Data, so a change to Slackish.Data can break Slackish.Data.Migrations, while a change to Slackish.Data.Migrations can't break Slackish.Data.
- Position
- Below the diagonal: Slackish.Data.Migrations uses a module listed above it, which is the healthy direction.
31→25 Slackish.Features.Core uses Slackish.Data✕
- Connections
- 1 pair of types, where a type in Slackish.Features.Core uses a type in Slackish.Data.
- The types involved
Slackish.Features.Core.RateLimitAttribute→Slackish.Data.SlackishContext
- Direction
- Slackish.Features.Core uses Slackish.Data, so a change to Slackish.Data can break Slackish.Features.Core, while a change to Slackish.Features.Core can't break Slackish.Data.
- Position
- Below the diagonal: Slackish.Features.Core uses a module listed above it, which is the healthy direction.
32→25 Slackish.Migrations uses Slackish.Data✕
- Connections
- 4 pairs of types, where a type in Slackish.Migrations uses a type in Slackish.Data.
- The types involved
Slackish.Migrations.Configuration→Slackish.Data.SlackishContextSlackish.Migrations.ProfileConfiguration→Slackish.Data.SlackishContextSlackish.Migrations.TenantConfiguration→Slackish.Data.SlackishContextSlackish.Migrations.UserConfiguration→Slackish.Data.SlackishContext
- Direction
- Slackish.Migrations uses Slackish.Data, so a change to Slackish.Data can break Slackish.Migrations, while a change to Slackish.Migrations can't break Slackish.Data.
- Position
- Below the diagonal: Slackish.Migrations uses a module listed above it, which is the healthy direction.
33→25 Slackish.Security uses Slackish.Data✕
- Connections
- 1 pair of types, where a type in Slackish.Security uses a type in Slackish.Data.
- The types involved
Slackish.Security.Handler→Slackish.Data.SlackishContext
- Direction
- Slackish.Security uses Slackish.Data, so a change to Slackish.Data can break Slackish.Security, while a change to Slackish.Security can't break Slackish.Data.
- Position
- Below the diagonal: Slackish.Security uses a module listed above it, which is the healthy direction.
34→10 ClientApp.app.conversations.conversation-page_component uses ClientApp.app.conversations.conversation_model✕
- Connections
- 1 pair of types, where a type in ClientApp.app.conversations.conversation-page_component uses a type in ClientApp.app.conversations.conversation_model.
- The types involved
ClientApp.app.conversations.conversation-page_component.ConversationPageComponent→ClientApp.app.conversations.conversation_model.Conversation
- Direction
- ClientApp.app.conversations.conversation-page_component uses ClientApp.app.conversations.conversation_model, so a change to ClientApp.app.conversations.conversation_model can break ClientApp.app.conversations.conversation-page_component, while a change to ClientApp.app.conversations.conversation-page_component can't break ClientApp.app.conversations.conversation_model.
- Position
- Below the diagonal: ClientApp.app.conversations.conversation-page_component uses a module listed above it, which is the healthy direction.
34→15 ClientApp.app.conversations.conversation-page_component uses ClientApp.app.profiles.profile_model✕
- Connections
- 1 pair of types, where a type in ClientApp.app.conversations.conversation-page_component uses a type in ClientApp.app.profiles.profile_model.
- The types involved
ClientApp.app.conversations.conversation-page_component.ConversationPageComponent→ClientApp.app.profiles.profile_model.Profile
- Direction
- ClientApp.app.conversations.conversation-page_component uses ClientApp.app.profiles.profile_model, so a change to ClientApp.app.profiles.profile_model can break ClientApp.app.conversations.conversation-page_component, while a change to ClientApp.app.conversations.conversation-page_component can't break ClientApp.app.profiles.profile_model.
- Position
- Below the diagonal: ClientApp.app.conversations.conversation-page_component uses a module listed above it, which is the healthy direction.
34→18 ClientApp.app.conversations.conversation-page_component uses ClientApp.app.shared.services.storage_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.conversations.conversation-page_component uses a type in ClientApp.app.shared.services.storage_service.
- The types involved
ClientApp.app.conversations.conversation-page_component.ConversationPageComponent→ClientApp.app.shared.services.storage_service.Storage
- Direction
- ClientApp.app.conversations.conversation-page_component uses ClientApp.app.shared.services.storage_service, so a change to ClientApp.app.shared.services.storage_service can break ClientApp.app.conversations.conversation-page_component, while a change to ClientApp.app.conversations.conversation-page_component can't break ClientApp.app.shared.services.storage_service.
- Position
- Below the diagonal: ClientApp.app.conversations.conversation-page_component uses a module listed above it, which is the healthy direction.
34→26 ClientApp.app.conversations.conversation-page_component uses ClientApp.app.conversations.conversations_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.conversations.conversation-page_component uses a type in ClientApp.app.conversations.conversations_service.
- The types involved
ClientApp.app.conversations.conversation-page_component.ConversationPageComponent→ClientApp.app.conversations.conversations_service.ConversationsService
- Direction
- ClientApp.app.conversations.conversation-page_component uses ClientApp.app.conversations.conversations_service, so a change to ClientApp.app.conversations.conversations_service can break ClientApp.app.conversations.conversation-page_component, while a change to ClientApp.app.conversations.conversation-page_component can't break ClientApp.app.conversations.conversations_service.
- Position
- Below the diagonal: ClientApp.app.conversations.conversation-page_component uses a module listed above it, which is the healthy direction.
34→27 ClientApp.app.conversations.conversation-page_component uses ClientApp.app.profiles.profile_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.conversations.conversation-page_component uses a type in ClientApp.app.profiles.profile_service.
- The types involved
ClientApp.app.conversations.conversation-page_component.ConversationPageComponent→ClientApp.app.profiles.profile_service.ProfilesService
- Direction
- ClientApp.app.conversations.conversation-page_component uses ClientApp.app.profiles.profile_service, so a change to ClientApp.app.profiles.profile_service can break ClientApp.app.conversations.conversation-page_component, while a change to ClientApp.app.conversations.conversation-page_component can't break ClientApp.app.profiles.profile_service.
- Position
- Below the diagonal: ClientApp.app.conversations.conversation-page_component uses a module listed above it, which is the healthy direction.
35→17 ClientApp.app.profiles.login-page_component uses ClientApp.app.shared.services.login-redirect_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.profiles.login-page_component uses a type in ClientApp.app.shared.services.login-redirect_service.
- The types involved
ClientApp.app.profiles.login-page_component.LoginPageComponent→ClientApp.app.shared.services.login-redirect_service.LoginRedirectService
- Direction
- ClientApp.app.profiles.login-page_component uses ClientApp.app.shared.services.login-redirect_service, so a change to ClientApp.app.shared.services.login-redirect_service can break ClientApp.app.profiles.login-page_component, while a change to ClientApp.app.profiles.login-page_component can't break ClientApp.app.shared.services.login-redirect_service.
- Position
- Below the diagonal: ClientApp.app.profiles.login-page_component uses a module listed above it, which is the healthy direction.
35→18 ClientApp.app.profiles.login-page_component uses ClientApp.app.shared.services.storage_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.profiles.login-page_component uses a type in ClientApp.app.shared.services.storage_service.
- The types involved
ClientApp.app.profiles.login-page_component.LoginPageComponent→ClientApp.app.shared.services.storage_service.Storage
- Direction
- ClientApp.app.profiles.login-page_component uses ClientApp.app.shared.services.storage_service, so a change to ClientApp.app.shared.services.storage_service can break ClientApp.app.profiles.login-page_component, while a change to ClientApp.app.profiles.login-page_component can't break ClientApp.app.shared.services.storage_service.
- Position
- Below the diagonal: ClientApp.app.profiles.login-page_component uses a module listed above it, which is the healthy direction.
35→27 ClientApp.app.profiles.login-page_component uses ClientApp.app.profiles.profile_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.profiles.login-page_component uses a type in ClientApp.app.profiles.profile_service.
- The types involved
ClientApp.app.profiles.login-page_component.LoginPageComponent→ClientApp.app.profiles.profile_service.ProfilesService
- Direction
- ClientApp.app.profiles.login-page_component uses ClientApp.app.profiles.profile_service, so a change to ClientApp.app.profiles.profile_service can break ClientApp.app.profiles.login-page_component, while a change to ClientApp.app.profiles.login-page_component can't break ClientApp.app.profiles.profile_service.
- Position
- Below the diagonal: ClientApp.app.profiles.login-page_component uses a module listed above it, which is the healthy direction.
35→28 ClientApp.app.profiles.login-page_component uses ClientApp.app.shared.services.authentication_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.profiles.login-page_component uses a type in ClientApp.app.shared.services.authentication_service.
- The types involved
ClientApp.app.profiles.login-page_component.LoginPageComponent→ClientApp.app.shared.services.authentication_service.AuthenticationService
- Direction
- ClientApp.app.profiles.login-page_component uses ClientApp.app.shared.services.authentication_service, so a change to ClientApp.app.shared.services.authentication_service can break ClientApp.app.profiles.login-page_component, while a change to ClientApp.app.profiles.login-page_component can't break ClientApp.app.shared.services.authentication_service.
- Position
- Below the diagonal: ClientApp.app.profiles.login-page_component uses a module listed above it, which is the healthy direction.
35→29 ClientApp.app.profiles.login-page_component uses ClientApp.app.teams.teams_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.profiles.login-page_component uses a type in ClientApp.app.teams.teams_service.
- The types involved
ClientApp.app.profiles.login-page_component.LoginPageComponent→ClientApp.app.teams.teams_service.TeamsService
- Direction
- ClientApp.app.profiles.login-page_component uses ClientApp.app.teams.teams_service, so a change to ClientApp.app.teams.teams_service can break ClientApp.app.profiles.login-page_component, while a change to ClientApp.app.profiles.login-page_component can't break ClientApp.app.teams.teams_service.
- Position
- Below the diagonal: ClientApp.app.profiles.login-page_component uses a module listed above it, which is the healthy direction.
36→18 ClientApp.app.teams.create-team-page_component uses ClientApp.app.shared.services.storage_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.teams.create-team-page_component uses a type in ClientApp.app.shared.services.storage_service.
- The types involved
ClientApp.app.teams.create-team-page_component.CreateTeamPageComponent→ClientApp.app.shared.services.storage_service.Storage
- Direction
- ClientApp.app.teams.create-team-page_component uses ClientApp.app.shared.services.storage_service, so a change to ClientApp.app.shared.services.storage_service can break ClientApp.app.teams.create-team-page_component, while a change to ClientApp.app.teams.create-team-page_component can't break ClientApp.app.shared.services.storage_service.
- Position
- Below the diagonal: ClientApp.app.teams.create-team-page_component uses a module listed above it, which is the healthy direction.
36→29 ClientApp.app.teams.create-team-page_component uses ClientApp.app.teams.teams_service✕
- Connections
- 1 pair of types, where a type in ClientApp.app.teams.create-team-page_component uses a type in ClientApp.app.teams.teams_service.
- The types involved
ClientApp.app.teams.create-team-page_component.CreateTeamPageComponent→ClientApp.app.teams.teams_service.TeamsService
- Direction
- ClientApp.app.teams.create-team-page_component uses ClientApp.app.teams.teams_service, so a change to ClientApp.app.teams.teams_service can break ClientApp.app.teams.create-team-page_component, while a change to ClientApp.app.teams.create-team-page_component can't break ClientApp.app.teams.teams_service.
- Position
- Below the diagonal: ClientApp.app.teams.create-team-page_component uses a module listed above it, which is the healthy direction.
37→19 Slackish.Features.Messages uses Slackish.Data.Model✕
- Connections
- 1 pair of types, where a type in Slackish.Features.Messages uses a type in Slackish.Data.Model.
- The types involved
Slackish.Features.Messages.MessageApiModel→Slackish.Data.Model.Message
- Direction
- Slackish.Features.Messages uses Slackish.Data.Model, so a change to Slackish.Data.Model can break Slackish.Features.Messages, while a change to Slackish.Features.Messages can't break Slackish.Data.Model.
- Position
- Below the diagonal: Slackish.Features.Messages uses a module listed above it, which is the healthy direction.
37→25 Slackish.Features.Messages uses Slackish.Data✕
- Connections
- 2 pairs of types, where a type in Slackish.Features.Messages uses a type in Slackish.Data.
- The types involved
Slackish.Features.Messages.Handler→Slackish.Data.SlackishContextSlackish.Features.Messages.SendMessageHandler→Slackish.Data.SlackishContext
- Direction
- Slackish.Features.Messages uses Slackish.Data, so a change to Slackish.Data can break Slackish.Features.Messages, while a change to Slackish.Features.Messages can't break Slackish.Data.
- Position
- Below the diagonal: Slackish.Features.Messages uses a module listed above it, which is the healthy direction.
37→31 Slackish.Features.Messages uses Slackish.Features.Core✕
- Connections
- 3 pairs of types, where a type in Slackish.Features.Messages uses a type in Slackish.Features.Core.
- The types involved
Slackish.Features.Messages.Handler→Slackish.Features.Core.ICacheSlackish.Features.Messages.MessageHub→Slackish.Features.Core.BaseHubSlackish.Features.Messages.MessagesController→Slackish.Features.Core.BaseApiController
- Direction
- Slackish.Features.Messages uses Slackish.Features.Core, so a change to Slackish.Features.Core can break Slackish.Features.Messages, while a change to Slackish.Features.Messages can't break Slackish.Features.Core.
- Position
- Below the diagonal: Slackish.Features.Messages uses a module listed above it, which is the healthy direction.
37→40 Slackish.Features.Messages uses Slackish.Features.Conversations part of a loop✕
- Connections
- 1 pair of types, where a type in Slackish.Features.Messages uses a type in Slackish.Features.Conversations.
- The types involved
Slackish.Features.Messages.MessageApiModel→Slackish.Features.Conversations.ConversationApiModel
- Direction
- Slackish.Features.Messages uses Slackish.Features.Conversations, so a change to Slackish.Features.Conversations can break Slackish.Features.Messages, while a change to Slackish.Features.Messages can't break Slackish.Features.Conversations.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→19 Slackish.Features.Profiles uses Slackish.Data.Model✕
- Connections
- 2 pairs of types, where a type in Slackish.Features.Profiles uses a type in Slackish.Data.Model.
- The types involved
Slackish.Features.Profiles.ProfileApiModel→Slackish.Data.Model.ProfileSlackish.Features.Profiles.UserApiModel→Slackish.Data.Model.User
- Direction
- Slackish.Features.Profiles uses Slackish.Data.Model, so a change to Slackish.Data.Model can break Slackish.Features.Profiles, while a change to Slackish.Features.Profiles can't break Slackish.Data.Model.
- Position
- Below the diagonal: Slackish.Features.Profiles uses a module listed above it, which is the healthy direction.
38→25 Slackish.Features.Profiles uses Slackish.Data✕
- Connections
- 2 pairs of types, where a type in Slackish.Features.Profiles uses a type in Slackish.Data.
- The types involved
Slackish.Features.Profiles.GetUserHandler→Slackish.Data.SlackishContextSlackish.Features.Profiles.Handler→Slackish.Data.SlackishContext
- Direction
- Slackish.Features.Profiles uses Slackish.Data, so a change to Slackish.Data can break Slackish.Features.Profiles, while a change to Slackish.Features.Profiles can't break Slackish.Data.
- Position
- Below the diagonal: Slackish.Features.Profiles uses a module listed above it, which is the healthy direction.
38→31 Slackish.Features.Profiles uses Slackish.Features.Core✕
- Connections
- 4 pairs of types, where a type in Slackish.Features.Profiles uses a type in Slackish.Features.Core.
- The types involved
Slackish.Features.Profiles.GetUserHandler→Slackish.Features.Core.ICacheSlackish.Features.Profiles.Handler→Slackish.Features.Core.ICacheSlackish.Features.Profiles.ProfileHub→Slackish.Features.Core.BaseHubSlackish.Features.Profiles.ProfilesController→Slackish.Features.Core.BaseApiController
- Direction
- Slackish.Features.Profiles uses Slackish.Features.Core, so a change to Slackish.Features.Core can break Slackish.Features.Profiles, while a change to Slackish.Features.Profiles can't break Slackish.Features.Core.
- Position
- Below the diagonal: Slackish.Features.Profiles uses a module listed above it, which is the healthy direction.
38→40 Slackish.Features.Profiles uses Slackish.Features.Conversations part of a loop✕
- Connections
- 1 pair of types, where a type in Slackish.Features.Profiles uses a type in Slackish.Features.Conversations.
- The types involved
Slackish.Features.Profiles.ProfileApiModel→Slackish.Features.Conversations.ConversationApiModel
- Direction
- Slackish.Features.Profiles uses Slackish.Features.Conversations, so a change to Slackish.Features.Conversations can break Slackish.Features.Profiles, while a change to Slackish.Features.Profiles can't break Slackish.Features.Conversations.
- 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.
39→19 Slackish.Features.Teams uses Slackish.Data.Model✕
- Connections
- 1 pair of types, where a type in Slackish.Features.Teams uses a type in Slackish.Data.Model.
- The types involved
Slackish.Features.Teams.TeamApiModel→Slackish.Data.Model.Team
- Direction
- Slackish.Features.Teams uses Slackish.Data.Model, so a change to Slackish.Data.Model can break Slackish.Features.Teams, while a change to Slackish.Features.Teams can't break Slackish.Data.Model.
- Position
- Below the diagonal: Slackish.Features.Teams uses a module listed above it, which is the healthy direction.
39→25 Slackish.Features.Teams uses Slackish.Data✕
- Connections
- 1 pair of types, where a type in Slackish.Features.Teams uses a type in Slackish.Data.
- The types involved
Slackish.Features.Teams.Handler→Slackish.Data.SlackishContext
- Direction
- Slackish.Features.Teams uses Slackish.Data, so a change to Slackish.Data can break Slackish.Features.Teams, while a change to Slackish.Features.Teams can't break Slackish.Data.
- Position
- Below the diagonal: Slackish.Features.Teams uses a module listed above it, which is the healthy direction.
39→31 Slackish.Features.Teams uses Slackish.Features.Core✕
- Connections
- 2 pairs of types, where a type in Slackish.Features.Teams uses a type in Slackish.Features.Core.
- The types involved
Slackish.Features.Teams.Handler→Slackish.Features.Core.ICacheSlackish.Features.Teams.TeamController→Slackish.Features.Core.BaseApiController
- Direction
- Slackish.Features.Teams uses Slackish.Features.Core, so a change to Slackish.Features.Core can break Slackish.Features.Teams, while a change to Slackish.Features.Teams can't break Slackish.Features.Core.
- Position
- Below the diagonal: Slackish.Features.Teams uses a module listed above it, which is the healthy direction.
40→19 Slackish.Features.Conversations uses Slackish.Data.Model✕
- Connections
- 1 pair of types, where a type in Slackish.Features.Conversations uses a type in Slackish.Data.Model.
- The types involved
Slackish.Features.Conversations.ConversationApiModel→Slackish.Data.Model.Conversation
- Direction
- Slackish.Features.Conversations uses Slackish.Data.Model, so a change to Slackish.Data.Model can break Slackish.Features.Conversations, while a change to Slackish.Features.Conversations can't break Slackish.Data.Model.
- Position
- Below the diagonal: Slackish.Features.Conversations uses a module listed above it, which is the healthy direction.
40→25 Slackish.Features.Conversations uses Slackish.Data✕
- Connections
- 1 pair of types, where a type in Slackish.Features.Conversations uses a type in Slackish.Data.
- The types involved
Slackish.Features.Conversations.Handler→Slackish.Data.SlackishContext
- Direction
- Slackish.Features.Conversations uses Slackish.Data, so a change to Slackish.Data can break Slackish.Features.Conversations, while a change to Slackish.Features.Conversations can't break Slackish.Data.
- Position
- Below the diagonal: Slackish.Features.Conversations uses a module listed above it, which is the healthy direction.
40→31 Slackish.Features.Conversations uses Slackish.Features.Core✕
- Connections
- 3 pairs of types, where a type in Slackish.Features.Conversations uses a type in Slackish.Features.Core.
- The types involved
Slackish.Features.Conversations.ConversationHub→Slackish.Features.Core.BaseHubSlackish.Features.Conversations.ConversationsController→Slackish.Features.Core.BaseApiControllerSlackish.Features.Conversations.Handler→Slackish.Features.Core.ICache
- Direction
- Slackish.Features.Conversations uses Slackish.Features.Core, so a change to Slackish.Features.Core can break Slackish.Features.Conversations, while a change to Slackish.Features.Conversations can't break Slackish.Features.Core.
- Position
- Below the diagonal: Slackish.Features.Conversations uses a module listed above it, which is the healthy direction.
40→37 Slackish.Features.Conversations uses Slackish.Features.Messages✕
- Connections
- 1 pair of types, where a type in Slackish.Features.Conversations uses a type in Slackish.Features.Messages.
- The types involved
Slackish.Features.Conversations.ConversationApiModel→Slackish.Features.Messages.MessageApiModel
- Direction
- Slackish.Features.Conversations uses Slackish.Features.Messages, so a change to Slackish.Features.Messages can break Slackish.Features.Conversations, while a change to Slackish.Features.Conversations can't break Slackish.Features.Messages.
- Position
- Below the diagonal: Slackish.Features.Conversations uses a module listed above it, which is the healthy direction.
40→38 Slackish.Features.Conversations uses Slackish.Features.Profiles✕
- Connections
- 1 pair of types, where a type in Slackish.Features.Conversations uses a type in Slackish.Features.Profiles.
- The types involved
Slackish.Features.Conversations.ConversationApiModel→Slackish.Features.Profiles.ProfileApiModel
- Direction
- Slackish.Features.Conversations uses Slackish.Features.Profiles, so a change to Slackish.Features.Profiles can break Slackish.Features.Conversations, while a change to Slackish.Features.Conversations can't break Slackish.Features.Profiles.
- Position
- Below the diagonal: Slackish.Features.Conversations 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 6 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | High / Critical |
| A05:2025 — Injection | 3 | Medium |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No tests found finding(s) in Test Distribution; Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +15.0 pts | Low | Test Distribution |
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +11.1 pts | Low | REDACTED Scanning |
| Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with UnityConfiguration.cs, QueryStringBearerAuthorizeAttribute.cs, EncryptionService.cs. | +5.7 pts | Low | Knowledge Freshness |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +15.0 pts | High | Code Coverage |
| 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. | +4.4 pts | Medium | Architecture documentation |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Slackish.csproj. | +1.8 pts | Low | Project Cohesion |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.8 pts | Low | Knowledge Freshness |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +2.9 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| Features/Core/RateLimit.cs | 4.9 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| Security/QueryStringBearerAuthorizeAttribute.cs | 6.1 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| Features/Core/Logger.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| Features/Teams/AddOrUpdateTeamCommand.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| Features/Teams/GetTeamByIdQuery.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| Features/Teams/GetTeamByNameQuery.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| Features/Teams/GetTeamsQuery.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| Features/Teams/RemoveTeamCommand.cs | 7.6 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| Slackish.csproj | 9.5 | Near-clean | Project Cohesion: Projects may be oversized for their cohesion |
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 77 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 77 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, 128 of 147 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: error: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/VisualStudio/v18.0/WebApplications/Microsoft.WebApplication.targets" was not found. Confirm that the expression in the Import declaration "$(VSToolsPath)/WebApplications/Microsoft.WebApplication.targets", which evaluated to "/usr/….
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 88 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 9 deducted marker(s) and the 1.8/KLoC density on this row were taken over this repository's .NET projects ALONE: .ts (1,130 lines, 30% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 1 error(s), and the diagnostics it printed were: MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/VisualStudio/v18.0/WebApplications/Microsoft.WebApplication.targets" was not found. Confirm that the expression in the Import declaration "$(VSToolsPath)/WebApplications/Microsoft.WebApplication.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/VisualStudio/v18.0/WebApplications/Microsoft.WebApplication.targets", is correct, and that the file exists on disk.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
- D19 Documentation Quality — 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 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.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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 solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D39 IL Efficiency — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 19 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- 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.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
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 QueryStringBearerAuthorizeAttribute.AuthorizeHubConnection at 20.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with QueryStringBearerAuthorizeAttribute.AuthorizeHubConnection (cognitive 20). — Refactoring it lifts Cognitive Complexity from 9.6 to about 10.0/10.
- Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected. Measured on part of this repository only: .ts (30% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate REDACTED Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 98 packages use a banned license. The depth of this set was not established for this repository: the graded packages are what this pass resolved, and no lockfile was read, so it is not certified to be the full transitive closure. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
9 deducted debt markers + 1 dead symbols across 2622 LoC in the .NET projects (1.8/KLoC) → score 6.3. Measured on the .NET source only: .ts (30% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 8 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Logger.cs, RateLimit.cs, AddOrUpdateTeamCommand.cs. — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with RateLimit.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Dead code finding(s) in Explicit Debt — start with RateLimit.cs. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
1 projects, 78 source files, 2622 hand-written lines of code (2622 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 0 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)
D26 · Project Cohesion
1 of 1 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Slackish.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
4 finding(s): 0 critical, 4 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 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)
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 2 high, 2 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
6 of 6 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is UnityConfiguration.cs. Counted over 6 of the 78 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 6 Orphaned file finding(s) in Knowledge Freshness — start with UnityConfiguration.cs, QueryStringBearerAuthorizeAttribute.cs, EncryptionService.cs. — One of this dimension's main actionable groups (6 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 26 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX2 · Stateful singletons
- `UnityConfiguration` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_container; e.g. `_container` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — UnityConfiguration.cs:15
- `MemoryCache` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_cache; e.g. `_cache` at line 39). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Features/Core/MemoryCache.cs:6
What to do
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces Slackish.Features.Conversations ↔ Slackish.Features.Messages ↔ Slackish.Features.Profiles depend on each other. The lightest dependency in the cycle is Slackish.Features.Conversations → Slackish.Features.Messages (Slackish.Features.Conversations.ConversationApiModel → Slackish.Features.Messages.MessageApiModel, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Features/Conversations/ConversationApiModel.cs:2
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure
AX6 · Interface segregation
AX7 · Slice cohesion
- `ConversationApiModel` (slice 'Conversations') depends on `ProfileApiModel` from slice 'Profiles'. — Features/Conversations/ConversationApiModel.cs:13
- `ConversationApiModel` (slice 'Conversations') depends on `MessageApiModel` from slice 'Messages'. — Features/Conversations/ConversationApiModel.cs:14
- `ConversationHub` (slice 'Conversations') depends on `BaseHub` from slice 'Core'. — Features/Conversations/ConversationHub.cs:12
- `ConversationsController` (slice 'Conversations') depends on `BaseApiController` from slice 'Core'. — Features/Conversations/ConversationsController.cs:11
- `GetByCurrentProfileQuery` (slice 'Conversations') depends on `ICache` from slice 'Core'. — Features/Conversations/GetByCurrentProfileQuery.cs:33
- `GetMessagesQuery` (slice 'Messages') depends on `ICache` from slice 'Core'. — Features/Messages/GetMessagesQuery.cs:26
- `MessageApiModel` (slice 'Messages') depends on `ConversationApiModel` from slice 'Conversations'. — Features/Messages/MessageApiModel.cs:12
- `MessageHub` (slice 'Messages') depends on `BaseHub` from slice 'Core'. — Features/Messages/MessageHub.cs:10
- `MessagesController` (slice 'Messages') depends on `BaseApiController` from slice 'Core'. — Features/Messages/MessagesController.cs:10
- `GetCurrentProfileQuery` (slice 'Profiles') depends on `ICache` from slice 'Core'. — Features/Profiles/GetCurrentProfileQuery.cs:25
- `GetOtherProfilesQuery` (slice 'Profiles') depends on `ICacheProvider` from slice 'Core'. — Features/Profiles/GetOtherProfiles.cs:27
- `GetOtherProfilesQuery` (slice 'Profiles') depends on `ICache` from slice 'Core'. — Features/Profiles/GetOtherProfiles.cs:50
- `GetUserQuery` (slice 'Profiles') depends on `ICache` from slice 'Core'. — Features/Profiles/GetUserQuery.cs:24
- `ProfileApiModel` (slice 'Profiles') depends on `ConversationApiModel` from slice 'Conversations'. — Features/Profiles/ProfileApiModel.cs:13
- `ProfileHub` (slice 'Profiles') depends on `BaseHub` from slice 'Core'. — Features/Profiles/ProfileHub.cs:10
- `ProfilesController` (slice 'Profiles') depends on `BaseApiController` from slice 'Core'. — REDACTED:11
- `AddOrUpdateTeamCommand` (slice 'Teams') depends on `ICache` from slice 'Core'. — Features/Teams/AddOrUpdateTeamCommand.cs:25
- `GetCurrentTeamQuery` (slice 'Teams') depends on `ICache` from slice 'Core'. — Features/Teams/GetCurrentTeamQuery.cs:26
- `GetTeamByIdQuery` (slice 'Teams') depends on `ICache` from slice 'Core'. — Features/Teams/GetTeamByIdQuery.cs:24
- `GetTeamByNameQuery` (slice 'Teams') depends on `ICache` from slice 'Core'. — Features/Teams/GetTeamByNameQuery.cs:27
- `GetTeamsQuery` (slice 'Teams') depends on `ICache` from slice 'Core'. — Features/Teams/GetTeamsQuery.cs:25
- `RemoveTeamCommand` (slice 'Teams') depends on `ICache` from slice 'Core'. — Features/Teams/RemoveTeamCommand.cs:22
- `SetCurrentTeamCommand` (slice 'Teams') depends on `ICache` from slice 'Core'. — Features/Teams/SetCurrentTeamCommand.cs:23
- `TeamController` (slice 'Teams') depends on `BaseApiController` from slice 'Core'. — Features/Teams/TeamsController.cs:11
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
AX9 · CQS / query purity
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
- Authorization IS enforced here (via [Authorize]/guards) — this is NOT a claim that endpoints are unprotected. What's missing is NAMED policies (AddAuthorization/AddPolicy, RequireRole/RequireClaim, RequireAuthorization): the access rules are implicit rather than named and testable. Recommendation, not a defect — name the rules so they're reviewable.
- This `[Authorize]` names no policy, role or scheme, so the rule it enforces (any authenticated caller) is implicit here and cannot be listed or tested apart from this attribute. Name the rule — `[Authorize(Policy = "…")]` over a policy registered with AddAuthorization — so the access rule set is reviewable. (×4) — Features/Conversations/ConversationsController.cs:9, Features/Messages/MessagesController.cs:8, REDACTED:9, …
What to do
- Add policy-based authorization — name the access rules (AddAuthorization(o => o.AddPolicy(…))) and apply them via [Authorize(Policy = …)] or RequireAuthorization.
C3 · Audit Trail
- An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
What to do
- Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
ED5 · Idempotency
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — Features/Core/RateLimit.cs:38
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `GetClientIp` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Features/Core/RateLimit.cs:38
- `Handle` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — Features/Messages/SendMessageCommand.cs:30, Features/Profiles/RegisterCommand.cs:32
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×9) — Features/Core/RateLimit.cs:23, Features/Core/RateLimit.cs:24, Features/Core/RateLimit.cs:27, …
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
- The root README is 18 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- 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.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
- Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:3
What to do
- Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P7 · Outbound HTTP resilience
- `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. — UnityConfiguration.cs:25
What to do
- Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- ClientApp/app/shared/services/http.service.ts:27 · ClientApp/app/shared/services/http.service.ts:65 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — ClientApp/app/shared/services/http.service.ts:27
- ClientApp/app/shared/services/signalr-message-queue-factory.ts:47 · ClientApp/app/shared/services/signalr-message-queue-factory.ts:59 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ClientApp/app/shared/services/signalr-message-queue-factory.ts:47
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- ClientApp/polyfills.ts:56 imports zone.js/dist/zone, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — ClientApp/polyfills.ts:56
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- 0% of 45 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 4 application, 3 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run watch` — an undetected custom entry would make these reachable.
- no import path from any entry point (4 application, 3 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — ClientApp/app/shared/layout/index.ts
- Nothing ultimately consumes this binding: its only referrer is the re-export in ClientApp/app/profiles/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in ClientApp/app/profiles/index.ts in the same commit, or the barrel will import a name that no longer exists. — ClientApp/app/profiles/register-page.component.ts:8
- Nothing ultimately consumes this binding: its only referrer is the re-export in ClientApp/app/shared/events/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in ClientApp/app/shared/events/index.ts in the same commit, or the barrel will import a name that no longer exists. — ClientApp/app/shared/events/popover.events.ts:5
- Nothing ultimately consumes this binding: its only referrer is the re-export in ClientApp/app/teams/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in ClientApp/app/teams/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — ClientApp/app/teams/set-current-team-form.component.ts:8, ClientApp/app/teams/team-selector.component.ts:9
- Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. (×2) — ClientApp/app/shared/services/login-redirect.service.ts:7, ClientApp/app/shared/services/signalr-message-queue-factory.ts:67
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Cryptographic Hygiene
- `algorithm.ComputeHash(…)` puts the password `password` through a fast general-purpose digest, so a stolen hash is guessed at billions of candidates a second whether or not it is salted — no key-derivation function (PBKDF2/scrypt/Argon2/bcrypt) stands between the password and the stored value. — Security/EncryptionService.cs:24
- `user.Password == transformedPassword` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. Store a salted KDF hash (PBKDF2/scrypt/Argon2/bcrypt) and verify by deriving again. — Security/IsAuthenticUserQuery.cs:41
- `_salt` is the key-derivation salt and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — Security/EncryptionService.cs:29
- This code fixes PBKDF2-SHA-1 at 1,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price. (×2) — Security/EncryptionService.cs:46, Security/EncryptionService.cs:88
- DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes. (×2) — Security/EncryptionService.cs:48, Security/EncryptionService.cs:90
What to do
- Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `Security/EncryptionService.cs:24`.
- Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.
- Raise the cost parameter to current guidance — PBKDF2 at 1,300,000 (HMAC-SHA1), 600,000 (SHA-256) or 210,000 (SHA-512) iterations; scrypt at N=2^17, r=8, p=1; bcrypt at a work factor of 10 or more — or move to a memory-hard KDF (Argon2id, scrypt) where the platform offers one. Read the parameter from configuration and tune it to roughly 100 ms per derivation on the slowest hardware that must run it, so the price can be raised again without shipping new code. This repository constructs a key derivation priced below the floor at 2 sites, not one: `Security/EncryptionService.cs:46` (PBKDF2-SHA-1, 1,000 iterations), `Security/EncryptionService.cs:88` (PBKDF2-SHA-1, 1,000 iterations). Each is a separate decision — fixing only the line this row cites leaves the others in place.
- Replace DES/3DES (and bare RijndaelManaged) with AES-GCM via `Aes.Create()`. This repository constructs a broken or deprecated cipher at 2 sites, not one: `Security/EncryptionService.cs:48` (RijndaelManaged), `Security/EncryptionService.cs:90` (RijndaelManaged). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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
- `algorithm` is a `HashAlgorithm`, which implements `IDisposable`, and it is created here (line 23). Every use of it in `TransformPassword` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var algorithm = …;`), which releases it at the end of the scope on every path including a throw. — Security/EncryptionService.cs:23
- `key` is a `Rfc2898DeriveBytes`, which implements `IDisposable`, and it is created here (line 46). Every use of it in `EncryptString` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var key = …;`), which releases it at the end of the scope on every path including a throw. — Security/EncryptionService.cs:46
- `key` is a `Rfc2898DeriveBytes`, which implements `IDisposable`, and it is created here (line 88). Every use of it in `DecryptString` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var key = …;`), which releases it at the end of the scope on every path including a throw. — Security/EncryptionService.cs:88
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/27 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. (×27) — Features/Conversations/ConversationsController.cs:20, Features/Conversations/GetByCurrentProfileQuery.cs:39, Features/Messages/GetMessagesQuery.cs:32, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
- The guard on line 36 rejects `plainText` and line 37 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(plainText)` is true of a value that is NOT null: it is satisfied by an EMPTY `plainText`, and on that path `plainText` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Security/EncryptionService.cs:37
- The guard on line 78 rejects `cipherText` and line 79 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(cipherText)` is true of a value that is NOT null: it is satisfied by an EMPTY `cipherText`, and on that path `cipherText` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Security/EncryptionService.cs:79
What to do
- Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 72% | Strong | Solid. |
| Architecture | 50% | Weak — gated by D26, AX2, AX7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 31% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 8% | Critical — gated by D8, D9, R4, R6, P1, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 41% | Weak — gated by C1, S1 | 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
- SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 47 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations detected
- AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D19 Documentation Quality — D19 withholds "XML-doc coverage": 1 candidate(s) (1 of them low-coverage Warnings on library projects) were measured and not published.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (902 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (2,622 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (3 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the target did not build
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a message-bus package; 1 CQRS handler(s)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- X5 Nullable reference types — no NRT-eligible projects
- 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 — 20 finding(s)
- WriteOnlyPrivateField Features/Core/Logger.cs:8
- WriteOnlyPrivateField Features/Core/RateLimit.cs:61
- WriteOnlyPrivateField Features/Teams/AddOrUpdateTeamCommand.cs:50
- WriteOnlyPrivateField Features/Teams/GetTeamByIdQuery.cs:41
- WriteOnlyPrivateField Features/Teams/GetTeamByNameQuery.cs:44
- WriteOnlyPrivateField Features/Teams/GetTeamsQuery.cs:45
- WriteOnlyPrivateField Features/Teams/RemoveTeamCommand.cs:37
- WriteOnlyPrivateField Security/QueryStringBearerAuthorizeAttribute.cs:112
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Password hashing without a KDF Security/EncryptionService.cs:24
- Password hashing without a KDF Security/IsAuthenticUserQuery.cs:41
- Namespace dependency cycle Features/Conversations/ConversationApiModel.cs:2
- REDACTED
- No automated tests
- Cryptographic key material is a compile-time constant Security/EncryptionService.cs:29
Serious — 87 finding(s)
- Async method without CancellationToken: GetByCurrentProfile Features/Conversations/ConversationsController.cs:20
- Async method without CancellationToken: Handle Features/Conversations/GetByCurrentProfileQuery.cs:39
- Async method without CancellationToken: Handle Features/Messages/GetMessagesQuery.cs:32
- Async method without CancellationToken: Handle Features/Messages/SendMessageCommand.cs:30
- Async method without CancellationToken: Handle Features/Profiles/GetCurrentProfileQuery.cs:31
- Async method without CancellationToken: Handle Features/Profiles/GetOtherProfiles.cs:33
- Async method without CancellationToken: Handle Features/Profiles/GetUserQuery.cs:30
- Async method without CancellationToken: GetOtherProfiles REDACTED:21
- Async method without CancellationToken: GetCurrentProfile REDACTED:27
- Async method without CancellationToken: Register REDACTED:33
- Async method without CancellationToken: Handle Security/GetClaimsForUserQuery.cs:29
- Async method without CancellationToken: Handle Security/IsAuthenticUserQuery.cs:44
- Async method without CancellationToken: Handle Features/Teams/AddOrUpdateTeamCommand.cs:31
- Async method without CancellationToken: Handle Features/Teams/GetTeamsQuery.cs:31
- Async method without CancellationToken: Handle Features/Teams/GetTeamByIdQuery.cs:30
- Async method without CancellationToken: Handle Features/Teams/RemoveTeamCommand.cs:28
- Async method without CancellationToken: GetCurrentTeam Features/Teams/TeamsController.cs:21
- Async method without CancellationToken: SetCurrentTeam Features/Teams/TeamsController.cs:27
- Async method without CancellationToken: Add Features/Teams/TeamsController.cs:37
- Async method without CancellationToken: Update Features/Teams/TeamsController.cs:46
- Async method without CancellationToken: Get Features/Teams/TeamsController.cs:56
- Async method without CancellationToken: GetById Features/Teams/TeamsController.cs:65
- Async method without CancellationToken: GetByName Features/Teams/TeamsController.cs:74
- Async method without CancellationToken: Remove Features/Teams/TeamsController.cs:83
- Async method without CancellationToken: Handle Features/Teams/GetCurrentTeamQuery.cs:32
- Cross-slice coupling: Conversations → Profiles Features/Conversations/ConversationApiModel.cs:13
- Cross-slice coupling: Conversations → Messages Features/Conversations/ConversationApiModel.cs:14
- Cross-slice coupling: Conversations → Core Features/Conversations/ConversationHub.cs:12
- Cross-slice coupling: Conversations → Core Features/Conversations/ConversationsController.cs:11
- Cross-slice coupling: Conversations → Core Features/Conversations/GetByCurrentProfileQuery.cs:33
- Cross-slice coupling: Messages → Core Features/Messages/GetMessagesQuery.cs:26
- Cross-slice coupling: Messages → Conversations Features/Messages/MessageApiModel.cs:12
- Cross-slice coupling: Messages → Core Features/Messages/MessageHub.cs:10
- Cross-slice coupling: Messages → Core Features/Messages/MessagesController.cs:10
- Cross-slice coupling: Profiles → Core Features/Profiles/GetCurrentProfileQuery.cs:25
- Cross-slice coupling: Profiles → Core Features/Profiles/GetOtherProfiles.cs:27
- Cross-slice coupling: Profiles → Core Features/Profiles/GetOtherProfiles.cs:50
- Cross-slice coupling: Profiles → Core Features/Profiles/GetUserQuery.cs:24
- Cross-slice coupling: Profiles → Conversations Features/Profiles/ProfileApiModel.cs:13
- Cross-slice coupling: Profiles → Core Features/Profiles/ProfileHub.cs:10
- Cross-slice coupling: Profiles → Core REDACTED:11
- Cross-slice coupling: Teams → Core Features/Teams/AddOrUpdateTeamCommand.cs:25
- Cross-slice coupling: Teams → Core Features/Teams/GetCurrentTeamQuery.cs:26
- Cross-slice coupling: Teams → Core Features/Teams/GetTeamByIdQuery.cs:24
- Cross-slice coupling: Teams → Core Features/Teams/GetTeamByNameQuery.cs:27
- Cross-slice coupling: Teams → Core Features/Teams/GetTeamsQuery.cs:25
- Cross-slice coupling: Teams → Core Features/Teams/RemoveTeamCommand.cs:22
- Cross-slice coupling: Teams → Core Features/Teams/SetCurrentTeamCommand.cs:23
- Cross-slice coupling: Teams → Core Features/Teams/TeamsController.cs:11
- Disposable created and abandoned in the method that made it Security/EncryptionService.cs:23
- Disposable created and abandoned in the method that made it Security/EncryptionService.cs:46
- Disposable created and abandoned in the method that made it Security/EncryptionService.cs:88
- Process-global static state: UnityConfiguration UnityConfiguration.cs:15
- Process-global static state: MemoryCache Features/Core/MemoryCache.cs:6
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Fake-async — async method never awaits Features/Messages/SendMessageCommand.cs:30
- Fake-async — async method never awaits Features/Profiles/RegisterCommand.cs:32
- Password key derivation is priced too cheaply Security/EncryptionService.cs:46
- Password key derivation is priced too cheaply Security/EncryptionService.cs:88
- Weak cipher Security/EncryptionService.cs:48
- Weak cipher Security/EncryptionService.cs:90
- Argument guard throws the exception its own condition disproves Security/EncryptionService.cs:37
- Argument guard throws the exception its own condition disproves Security/EncryptionService.cs:79
- CommentedOutCode Features/Core/RateLimit.cs:40
- Dead code: GetClientIp Features/Core/RateLimit.cs:38
- QueryStringBearerAuthorizeAttribute.AuthorizeHubConnection (cognitive 20) Security/QueryStringBearerAuthorizeAttribute.cs:23
- REDACTED
- Unfinished stub — throws NotImplementedException Features/Core/RateLimit.cs:38
- Unfinished stub — throws NotImplementedException Features/Core/RateLimit.cs:38
- No CI pipeline
- Outbound HTTP without resilience UnityConfiguration.cs:25
- Duplicated block (17 lines × 2 locations) ClientApp/app/shared/services/http.service.ts:27
- Duplicated block (10 lines × 2 locations) ClientApp/app/shared/services/signalr-message-queue-factory.ts:47
- Boundary violation [package:third-party-deep-import] ClientApp/polyfills.ts:56
- Test Coverage
- No test, lint or typecheck script
- Dead file (~1 LoC) ClientApp/app/shared/layout/index.ts
- Unused dependency '@angular/animations'
- Unused dependency '@angular/compiler'
- Unused dependency '@angular/compiler-cli'
- NuGet dependencies are not locked
- JavaScript dependencies are not locked package.json:9
Minor — 40 finding(s)
- Commented-out code Features/Core/RateLimit.cs:23
- Commented-out code Features/Core/RateLimit.cs:24
- Commented-out code Features/Core/RateLimit.cs:27
- Commented-out code Features/Core/RateLimit.cs:29
- Commented-out code Features/Core/RateLimit.cs:32
- Commented-out code Features/Core/RateLimit.cs:35
- Commented-out code Features/Core/RateLimit.cs:47
- Commented-out code Features/Core/RateLimit.cs:48
- Commented-out code Features/Core/RateLimit.cs:52
- Orphaned file UnityConfiguration.cs:1
- Orphaned file Security/QueryStringBearerAuthorizeAttribute.cs:1
- Orphaned file Security/EncryptionService.cs:1
- Orphaned file Features/Teams/TeamsController.cs:1
- Orphaned file REDACTED:1
- Orphaned file Data/SlackishContext.cs:1
- No named authorization policies
- No named authorization policies Features/Conversations/ConversationsController.cs:9
- No named authorization policies Features/Messages/MessagesController.cs:8
- No named authorization policies REDACTED:9
- No named authorization policies Features/Teams/TeamsController.cs:9
- Partial audit-trail evidence
- Partial data-retention evidence
- Projects may be oversized for their cohesion Slackish.csproj:1
- REDACTED
- Orphaned files with no living knowledge
- No tests found
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- No src/ separation
- No SAST
- No dependency-update automation REDACTED:3
- Unused export 'RegisterPageComponent' ClientApp/app/profiles/register-page.component.ts:8
- Unused export 'PopoverEvent' ClientApp/app/shared/events/popover.events.ts:5
- Unused export 'SetCurrentTeamFormComponent' ClientApp/app/teams/set-current-team-form.component.ts:8
- Unused export 'TeamSelectorComponent' ClientApp/app/teams/team-selector.component.ts:9
- Unused private field '_route' ClientApp/app/shared/services/login-redirect.service.ts:7
- Unused private field '_failedMessages$' ClientApp/app/shared/services/signalr-message-queue-factory.ts:67
- Duplicated predicate Features/Teams/GetTeamByIdQuery.cs:36
- Not all async methods take a CancellationToken
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-e423e00c952f4145a984eb1badb0929f/history.json --exit-code 0 --source . | 4 | 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-e423e00c952f4145a984eb1badb0929f/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 3 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 4 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
Appendix C — Personal-data map
Name — 5 field(s)
- User.Firstname Data/Model/User.cs:25
- User.Lastname Data/Model/User.cs:26
- User.Fullname Data/Model/User.cs:27
- UserApiModel.Firstname Features/Profiles/UserApiModel.cs:13
- UserApiModel.Lastname Features/Profiles/UserApiModel.cs:14
Email — 2 field(s)
- User.Email Data/Model/User.cs:18
- UserApiModel.Email Features/Profiles/UserApiModel.cs:11