Executive summary
ronnieholm/FSharp-onion-architecture-sample falls short of our standard for a template or a sample because two passwords or keys sit in the current code and we found no working pipeline that builds or tests changes to the code. It scores 54 out of 100 and is rated Adequate, and all four of its critical findings are leaked passwords or keys.
Production Readiness, at 27, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 19 points. Adding an automated build and test pipeline comes next, worth about 9 points. Raising Production Readiness to 52 would lift the score to about 66.
Two passwords or keys in the code and two in the code's history are open to anyone who can read the repository. Replacing each exposed password or key would close this risk.
The product code is 2,198 lines, about €3,400 to rebuild.
If Production Readiness rose from 27 to 52, the lowest score rated Strong, the score would rise from 54 to about 66.
Fixed since the last survey: 8 findings
- Dependency Hygiene · Vulnerable: OpenTelemetry.Exporter.Jaeger
- Dependency Hygiene · Vulnerable: OpenTelemetry.Exporter.OpenTelemetryProtocol
- Dependency Hygiene · Deprecated: OpenTelemetry.Exporter.Jaeger Directory.Packages.props
- Dependency Hygiene · Deprecated: xunit Directory.Packages.props
- REDACTED Scanning · Leaked secret: signing-key src/Scrum/appsettings.json
- Dependency Vulnerabilities · Medium CVE: OpenTelemetry.Exporter.Jaeger 1.5.1 Directory.Packages.props
- Dependency Vulnerabilities · Medium CVE: OpenTelemetry.Exporter.OpenTelemetryProtocol 1.14.0 Directory.Packages.props
- Dependency Vulnerabilities · Medium CVE: OpenTelemetry.Api 1.14.0 src/Scrum/Scrum.fsproj
Rebuild cost: about €3,400 · Estimate
| Cost to rebuild | €1,100 to €5,700, for 19 to 60 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 54. 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: 2,198 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Seedwork.Application.Models | 2 Seedwork.Application.ValidationError | 3 Seedwork.Domain | 4 Seedwork.Domain.Paging | 5 Seedwork.Domain.Paging.Cursor | 6 Seedwork.Domain.Paging.Limit | 7 Seedwork.Domain.Validation.Guid | 8 Seedwork.Domain.Validation.Int | 9 Seedwork.Domain.Validation.String | 10 Seedwork.Infrastructure | 11 Seedwork.Infrastructure.Configuration | 12 Seedwork.Infrastructure.DatabaseMigration | 13 Seedwork.Infrastructure.Json | 14 Seedwork.Infrastructure.Option | 15 Seedwork.Infrastructure.ScrumClaims | 16 Seedwork.Infrastructure.ScrumLogger | 17 Seedwork.Infrastructure.UserIdentity | 18 Seedwork.RouteHandler | 19 Seedwork.Application | 20 Seedwork.Application.EventRequest | 21 Seedwork.Infrastructure.EventRepository | 22 Seedwork.Infrastructure.Repository | 23 Seedwork.Infrastructure.Service.IdentityProvider | 24 Story.Application.StoryRequest | 25 Story.Domain.StoryAggregate.TaskEntity | 26 Seedwork.Application.EventRequest.GetByAggregateIdQuery | 27 Seedwork.Application.EventRequest.GetByAggregateIdQuery.PersistedEventDto | 28 Seedwork.Infrastructure.ProblemDetails | 29 Story.Application.StoryRequest.GetStoriesPagedQuery | 30 Story.Application.StoryRequest.TaskDto | 31 Story.Domain.StoryAggregate | 32 WebHost.HealthCheck | 33 Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand | 34 Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand | 35 Story.Application.StoryRequest.GetStoryByIdQuery | 36 Story.Application.StoryRequest.RemoveStoryCommand | 37 Story.Application.StoryRequest.RemoveTaskCommand | 38 Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand | 39 Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand | 40 Story.Application.StoryRequest.StoryDto |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Seedwork.Application.Models | ||||||||||||||||||||||||||||||||||||||||
| 2 Seedwork.Application.ValidationError | ||||||||||||||||||||||||||||||||||||||||
| 3 Seedwork.Domain | ||||||||||||||||||||||||||||||||||||||||
| 4 Seedwork.Domain.Paging | ||||||||||||||||||||||||||||||||||||||||
| 5 Seedwork.Domain.Paging.Cursor | ||||||||||||||||||||||||||||||||||||||||
| 6 Seedwork.Domain.Paging.Limit | ||||||||||||||||||||||||||||||||||||||||
| 7 Seedwork.Domain.Validation.Guid | ||||||||||||||||||||||||||||||||||||||||
| 8 Seedwork.Domain.Validation.Int | ||||||||||||||||||||||||||||||||||||||||
| 9 Seedwork.Domain.Validation.String | ||||||||||||||||||||||||||||||||||||||||
| 10 Seedwork.Infrastructure | ||||||||||||||||||||||||||||||||||||||||
| 11 Seedwork.Infrastructure.Configuration | ||||||||||||||||||||||||||||||||||||||||
| 12 Seedwork.Infrastructure.DatabaseMigration | ||||||||||||||||||||||||||||||||||||||||
| 13 Seedwork.Infrastructure.Json | ||||||||||||||||||||||||||||||||||||||||
| 14 Seedwork.Infrastructure.Option | ||||||||||||||||||||||||||||||||||||||||
| 15 Seedwork.Infrastructure.ScrumClaims | ||||||||||||||||||||||||||||||||||||||||
| 16 Seedwork.Infrastructure.ScrumLogger | ||||||||||||||||||||||||||||||||||||||||
| 17 Seedwork.Infrastructure.UserIdentity | ||||||||||||||||||||||||||||||||||||||||
| 18 Seedwork.RouteHandler | ||||||||||||||||||||||||||||||||||||||||
| 19 Seedwork.Application | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Seedwork.Application.EventRequest | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Seedwork.Infrastructure.EventRepository | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Seedwork.Infrastructure.Repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Seedwork.Infrastructure.Service.IdentityProvider | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Story.Application.StoryRequest | 9 | |||||||||||||||||||||||||||||||||||||||
| 25 Story.Domain.StoryAggregate.TaskEntity | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Seedwork.Application.EventRequest.GetByAggregateIdQuery | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 Seedwork.Application.EventRequest.GetByAggregateIdQuery.PersistedEventDto | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Seedwork.Infrastructure.ProblemDetails | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Story.Application.StoryRequest.GetStoriesPagedQuery | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Story.Application.StoryRequest.TaskDto | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 Story.Domain.StoryAggregate | 1 | 1 | 8 | |||||||||||||||||||||||||||||||||||||
| 32 WebHost.HealthCheck | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 Story.Application.StoryRequest.GetStoryByIdQuery | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 Story.Application.StoryRequest.RemoveStoryCommand | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 Story.Application.StoryRequest.RemoveTaskCommand | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 39 Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 Story.Application.StoryRequest.StoryDto | 1 |
19→7 Seedwork.Application uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Seedwork.Application uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Seedwork.Application.PersistedEvent→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Seedwork.Application uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Seedwork.Application, while a change to Seedwork.Application can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Seedwork.Application uses a module listed above it, which is the healthy direction.
20→7 Seedwork.Application.EventRequest uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Seedwork.Application.EventRequest uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQuery→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Seedwork.Application.EventRequest uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Seedwork.Application.EventRequest, while a change to Seedwork.Application.EventRequest can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Seedwork.Application.EventRequest uses a module listed above it, which is the healthy direction.
21→7 Seedwork.Infrastructure.EventRepository uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Seedwork.Infrastructure.EventRepository uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Seedwork.Infrastructure.EventRepository.EventRepository→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Seedwork.Infrastructure.EventRepository uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Seedwork.Infrastructure.EventRepository, while a change to Seedwork.Infrastructure.EventRepository can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Seedwork.Infrastructure.EventRepository uses a module listed above it, which is the healthy direction.
22→7 Seedwork.Infrastructure.Repository uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Seedwork.Infrastructure.Repository uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Seedwork.Infrastructure.Repository.Repository→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Seedwork.Infrastructure.Repository uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Seedwork.Infrastructure.Repository, while a change to Seedwork.Infrastructure.Repository can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Seedwork.Infrastructure.Repository uses a module listed above it, which is the healthy direction.
23→11 Seedwork.Infrastructure.Service.IdentityProvider uses Seedwork.Infrastructure.Configuration✕
- Connections
- 1 pair of types, where a type in Seedwork.Infrastructure.Service.IdentityProvider uses a type in Seedwork.Infrastructure.Configuration.
- The types involved
Scrum.Seedwork.Infrastructure.Service.IdentityProvider.IdentityProvider→Scrum.Seedwork.Infrastructure.Configuration.JwtAuthenticationSettings
- Direction
- Seedwork.Infrastructure.Service.IdentityProvider uses Seedwork.Infrastructure.Configuration, so a change to Seedwork.Infrastructure.Configuration can break Seedwork.Infrastructure.Service.IdentityProvider, while a change to Seedwork.Infrastructure.Service.IdentityProvider can't break Seedwork.Infrastructure.Configuration.
- Position
- Below the diagonal: Seedwork.Infrastructure.Service.IdentityProvider uses a module listed above it, which is the healthy direction.
24→7 Story.Application.StoryRequest uses Seedwork.Domain.Validation.Guid✕
- Connections
- 9 pairs of types, where a type in Story.Application.StoryRequest uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand→Scrum.Seedwork.Domain.Validation.Guid.GuidScrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand→Scrum.Seedwork.Domain.Validation.Guid.GuidScrum.Story.Application.StoryRequest.GetStoryByIdQuery→Scrum.Seedwork.Domain.Validation.Guid.GuidScrum.Story.Application.StoryRequest.RemoveStoryCommand→Scrum.Seedwork.Domain.Validation.Guid.GuidScrum.Story.Application.StoryRequest.RemoveTaskCommand→Scrum.Seedwork.Domain.Validation.Guid.GuidScrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand→Scrum.Seedwork.Domain.Validation.Guid.GuidScrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand→Scrum.Seedwork.Domain.Validation.Guid.GuidScrum.Story.Application.StoryRequest.StoryDto→Scrum.Seedwork.Domain.Validation.Guid.GuidScrum.Story.Application.StoryRequest.TaskDto→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Story.Application.StoryRequest uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Story.Application.StoryRequest, while a change to Story.Application.StoryRequest can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Story.Application.StoryRequest uses a module listed above it, which is the healthy direction.
25→3 Story.Domain.StoryAggregate.TaskEntity uses Seedwork.Domain✕
- Connections
- 1 pair of types, where a type in Story.Domain.StoryAggregate.TaskEntity uses a type in Seedwork.Domain.
- The types involved
Scrum.Story.Domain.StoryAggregate.TaskEntity.Task→Scrum.Seedwork.Domain.Entity
- Direction
- Story.Domain.StoryAggregate.TaskEntity uses Seedwork.Domain, so a change to Seedwork.Domain can break Story.Domain.StoryAggregate.TaskEntity, while a change to Story.Domain.StoryAggregate.TaskEntity can't break Seedwork.Domain.
- Position
- Below the diagonal: Story.Domain.StoryAggregate.TaskEntity uses a module listed above it, which is the healthy direction.
25→7 Story.Domain.StoryAggregate.TaskEntity uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Story.Domain.StoryAggregate.TaskEntity uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskId→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Story.Domain.StoryAggregate.TaskEntity uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Story.Domain.StoryAggregate.TaskEntity, while a change to Story.Domain.StoryAggregate.TaskEntity can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Story.Domain.StoryAggregate.TaskEntity uses a module listed above it, which is the healthy direction.
26→4 Seedwork.Application.EventRequest.GetByAggregateIdQuery uses Seedwork.Domain.Paging✕
- Connections
- 1 pair of types, where a type in Seedwork.Application.EventRequest.GetByAggregateIdQuery uses a type in Seedwork.Domain.Paging.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQuery.GetByAggregateIdValidatedQuery→Scrum.Seedwork.Domain.Paging.Limit
- Direction
- Seedwork.Application.EventRequest.GetByAggregateIdQuery uses Seedwork.Domain.Paging, so a change to Seedwork.Domain.Paging can break Seedwork.Application.EventRequest.GetByAggregateIdQuery, while a change to Seedwork.Application.EventRequest.GetByAggregateIdQuery can't break Seedwork.Domain.Paging.
- Position
- Below the diagonal: Seedwork.Application.EventRequest.GetByAggregateIdQuery uses a module listed above it, which is the healthy direction.
26→7 Seedwork.Application.EventRequest.GetByAggregateIdQuery uses Seedwork.Domain.Validation.Guid✕
- Connections
- 2 pairs of types, where a type in Seedwork.Application.EventRequest.GetByAggregateIdQuery uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQuery.GetByAggregateIdValidatedQuery→Scrum.Seedwork.Domain.Validation.Guid.GuidScrum.Seedwork.Application.EventRequest.GetByAggregateIdQuery.PersistedEventDto→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Seedwork.Application.EventRequest.GetByAggregateIdQuery uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Seedwork.Application.EventRequest.GetByAggregateIdQuery, while a change to Seedwork.Application.EventRequest.GetByAggregateIdQuery can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Seedwork.Application.EventRequest.GetByAggregateIdQuery uses a module listed above it, which is the healthy direction.
26→19 Seedwork.Application.EventRequest.GetByAggregateIdQuery uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Seedwork.Application.EventRequest.GetByAggregateIdQuery uses a type in Seedwork.Application.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQuery.GetByAggregateIdError→Scrum.Seedwork.Application.ScrumRole
- Direction
- Seedwork.Application.EventRequest.GetByAggregateIdQuery uses Seedwork.Application, so a change to Seedwork.Application can break Seedwork.Application.EventRequest.GetByAggregateIdQuery, while a change to Seedwork.Application.EventRequest.GetByAggregateIdQuery can't break Seedwork.Application.
- Position
- Below the diagonal: Seedwork.Application.EventRequest.GetByAggregateIdQuery uses a module listed above it, which is the healthy direction.
27→19 Seedwork.Application.EventRequest.GetByAggregateIdQuery.PersistedEventDto uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Seedwork.Application.EventRequest.GetByAggregateIdQuery.PersistedEventDto uses a type in Seedwork.Application.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQuery.PersistedEventDto.PersistedEventDto→Scrum.Seedwork.Application.PersistedEvent
- Direction
- Seedwork.Application.EventRequest.GetByAggregateIdQuery.PersistedEventDto uses Seedwork.Application, so a change to Seedwork.Application can break Seedwork.Application.EventRequest.GetByAggregateIdQuery.PersistedEventDto, while a change to Seedwork.Application.EventRequest.GetByAggregateIdQuery.PersistedEventDto can't break Seedwork.Application.
- Position
- Below the diagonal: Seedwork.Application.EventRequest.GetByAggregateIdQuery.PersistedEventDto uses a module listed above it, which is the healthy direction.
28→10 Seedwork.Infrastructure.ProblemDetails uses Seedwork.Infrastructure✕
- Connections
- 1 pair of types, where a type in Seedwork.Infrastructure.ProblemDetails uses a type in Seedwork.Infrastructure.
- The types involved
Scrum.Seedwork.Infrastructure.ProblemDetails.ProblemDetails→Scrum.Seedwork.Infrastructure.ProblemDetails2
- Direction
- Seedwork.Infrastructure.ProblemDetails uses Seedwork.Infrastructure, so a change to Seedwork.Infrastructure can break Seedwork.Infrastructure.ProblemDetails, while a change to Seedwork.Infrastructure.ProblemDetails can't break Seedwork.Infrastructure.
- Position
- Below the diagonal: Seedwork.Infrastructure.ProblemDetails uses a module listed above it, which is the healthy direction.
28→19 Seedwork.Infrastructure.ProblemDetails uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Seedwork.Infrastructure.ProblemDetails uses a type in Seedwork.Application.
- The types involved
Scrum.Seedwork.Infrastructure.ProblemDetails.ProblemDetails→Scrum.Seedwork.Application.ScrumRole
- Direction
- Seedwork.Infrastructure.ProblemDetails uses Seedwork.Application, so a change to Seedwork.Application can break Seedwork.Infrastructure.ProblemDetails, while a change to Seedwork.Infrastructure.ProblemDetails can't break Seedwork.Application.
- Position
- Below the diagonal: Seedwork.Infrastructure.ProblemDetails uses a module listed above it, which is the healthy direction.
29→4 Story.Application.StoryRequest.GetStoriesPagedQuery uses Seedwork.Domain.Paging✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.GetStoriesPagedQuery uses a type in Seedwork.Domain.Paging.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoriesPagedQuery.GetStoriesPagedValidatedQuery→Scrum.Seedwork.Domain.Paging.Limit
- Direction
- Story.Application.StoryRequest.GetStoriesPagedQuery uses Seedwork.Domain.Paging, so a change to Seedwork.Domain.Paging can break Story.Application.StoryRequest.GetStoriesPagedQuery, while a change to Story.Application.StoryRequest.GetStoriesPagedQuery can't break Seedwork.Domain.Paging.
- Position
- Below the diagonal: Story.Application.StoryRequest.GetStoriesPagedQuery uses a module listed above it, which is the healthy direction.
29→19 Story.Application.StoryRequest.GetStoriesPagedQuery uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.GetStoriesPagedQuery uses a type in Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoriesPagedQuery.GetStoriesPagedError→Scrum.Seedwork.Application.ScrumRole
- Direction
- Story.Application.StoryRequest.GetStoriesPagedQuery uses Seedwork.Application, so a change to Seedwork.Application can break Story.Application.StoryRequest.GetStoriesPagedQuery, while a change to Story.Application.StoryRequest.GetStoriesPagedQuery can't break Seedwork.Application.
- Position
- Below the diagonal: Story.Application.StoryRequest.GetStoriesPagedQuery uses a module listed above it, which is the healthy direction.
30→25 Story.Application.StoryRequest.TaskDto uses Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.TaskDto uses a type in Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Application.StoryRequest.TaskDto.TaskDto→Scrum.Story.Domain.StoryAggregate.TaskEntity.Task
- Direction
- Story.Application.StoryRequest.TaskDto uses Story.Domain.StoryAggregate.TaskEntity, so a change to Story.Domain.StoryAggregate.TaskEntity can break Story.Application.StoryRequest.TaskDto, while a change to Story.Application.StoryRequest.TaskDto can't break Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Story.Application.StoryRequest.TaskDto uses a module listed above it, which is the healthy direction.
31→3 Story.Domain.StoryAggregate uses Seedwork.Domain✕
- Connections
- 1 pair of types, where a type in Story.Domain.StoryAggregate uses a type in Seedwork.Domain.
- The types involved
Scrum.Story.Domain.StoryAggregate.Story→Scrum.Seedwork.Domain.AggregateRoot
- Direction
- Story.Domain.StoryAggregate uses Seedwork.Domain, so a change to Seedwork.Domain can break Story.Domain.StoryAggregate, while a change to Story.Domain.StoryAggregate can't break Seedwork.Domain.
- Position
- Below the diagonal: Story.Domain.StoryAggregate uses a module listed above it, which is the healthy direction.
31→7 Story.Domain.StoryAggregate uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Story.Domain.StoryAggregate uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Story.Domain.StoryAggregate.StoryId→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Story.Domain.StoryAggregate uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Story.Domain.StoryAggregate, while a change to Story.Domain.StoryAggregate can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Story.Domain.StoryAggregate uses a module listed above it, which is the healthy direction.
31→25 Story.Domain.StoryAggregate uses Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 8 pairs of types, where a type in Story.Domain.StoryAggregate uses a type in Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Domain.StoryAggregate.AddBasicTaskDetailsToStory→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdScrum.Story.Domain.StoryAggregate.AddBasicTaskDetailsToStory→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleScrum.Story.Domain.StoryAggregate.AddBasicTaskDetailsToStoryError→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdScrum.Story.Domain.StoryAggregate.RemoveTask→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdScrum.Story.Domain.StoryAggregate.RemoveTaskError→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdScrum.Story.Domain.StoryAggregate.ReviseBasicTaskDetails→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdScrum.Story.Domain.StoryAggregate.ReviseBasicTaskDetails→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleScrum.Story.Domain.StoryAggregate.ReviseBasicTaskDetailsError→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskId
- Direction
- Story.Domain.StoryAggregate uses Story.Domain.StoryAggregate.TaskEntity, so a change to Story.Domain.StoryAggregate.TaskEntity can break Story.Domain.StoryAggregate, while a change to Story.Domain.StoryAggregate can't break Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Story.Domain.StoryAggregate uses a module listed above it, which is the healthy direction.
32→25 WebHost.HealthCheck uses Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 1 pair of types, where a type in WebHost.HealthCheck uses a type in Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.WebHost.HealthCheck.SQLiteHealthCheck→Scrum.Story.Domain.StoryAggregate.TaskEntity.Task
- Direction
- WebHost.HealthCheck uses Story.Domain.StoryAggregate.TaskEntity, so a change to Story.Domain.StoryAggregate.TaskEntity can break WebHost.HealthCheck, while a change to WebHost.HealthCheck can't break Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: WebHost.HealthCheck uses a module listed above it, which is the healthy direction.
33→7 Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand.AddBasicTaskDetailsToStoryError→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand, while a change to Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses a module listed above it, which is the healthy direction.
33→19 Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses a type in Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand.AddBasicTaskDetailsToStoryError→Scrum.Seedwork.Application.ScrumRole
- Direction
- Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses Seedwork.Application, so a change to Seedwork.Application can break Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand, while a change to Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand can't break Seedwork.Application.
- Position
- Below the diagonal: Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses a module listed above it, which is the healthy direction.
33→25 Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 2 pairs of types, where a type in Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses a type in Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand.AddBasicTaskDetailsToStoryValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdScrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand.AddBasicTaskDetailsToStoryValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitle
- Direction
- Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses Story.Domain.StoryAggregate.TaskEntity, so a change to Story.Domain.StoryAggregate.TaskEntity can break Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand, while a change to Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand can't break Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses a module listed above it, which is the healthy direction.
33→31 Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses a type in Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand.AddBasicTaskDetailsToStoryValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses Story.Domain.StoryAggregate, so a change to Story.Domain.StoryAggregate can break Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand, while a change to Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand can't break Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand uses a module listed above it, which is the healthy direction.
34→7 Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand.CaptureBasicStoryDetailsError→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand, while a change to Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses a module listed above it, which is the healthy direction.
34→19 Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses a type in Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand.CaptureBasicStoryDetailsError→Scrum.Seedwork.Application.ScrumRole
- Direction
- Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses Seedwork.Application, so a change to Seedwork.Application can break Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand, while a change to Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand can't break Seedwork.Application.
- Position
- Below the diagonal: Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses a module listed above it, which is the healthy direction.
34→31 Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses Story.Domain.StoryAggregate✕
- Connections
- 2 pairs of types, where a type in Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses a type in Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand.CaptureBasicStoryDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryIdScrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand.CaptureBasicStoryDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryTitle
- Direction
- Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses Story.Domain.StoryAggregate, so a change to Story.Domain.StoryAggregate can break Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand, while a change to Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand can't break Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand uses a module listed above it, which is the healthy direction.
35→7 Story.Application.StoryRequest.GetStoryByIdQuery uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.GetStoryByIdQuery uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoryByIdQuery.GetStoryByIdError→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Story.Application.StoryRequest.GetStoryByIdQuery uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Story.Application.StoryRequest.GetStoryByIdQuery, while a change to Story.Application.StoryRequest.GetStoryByIdQuery can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Story.Application.StoryRequest.GetStoryByIdQuery uses a module listed above it, which is the healthy direction.
35→19 Story.Application.StoryRequest.GetStoryByIdQuery uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.GetStoryByIdQuery uses a type in Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoryByIdQuery.GetStoryByIdError→Scrum.Seedwork.Application.ScrumRole
- Direction
- Story.Application.StoryRequest.GetStoryByIdQuery uses Seedwork.Application, so a change to Seedwork.Application can break Story.Application.StoryRequest.GetStoryByIdQuery, while a change to Story.Application.StoryRequest.GetStoryByIdQuery can't break Seedwork.Application.
- Position
- Below the diagonal: Story.Application.StoryRequest.GetStoryByIdQuery uses a module listed above it, which is the healthy direction.
35→31 Story.Application.StoryRequest.GetStoryByIdQuery uses Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.GetStoryByIdQuery uses a type in Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoryByIdQuery.GetStoryByIdValidatedQuery→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Story.Application.StoryRequest.GetStoryByIdQuery uses Story.Domain.StoryAggregate, so a change to Story.Domain.StoryAggregate can break Story.Application.StoryRequest.GetStoryByIdQuery, while a change to Story.Application.StoryRequest.GetStoryByIdQuery can't break Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Story.Application.StoryRequest.GetStoryByIdQuery uses a module listed above it, which is the healthy direction.
36→7 Story.Application.StoryRequest.RemoveStoryCommand uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.RemoveStoryCommand uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveStoryCommand.RemoveStoryError→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Story.Application.StoryRequest.RemoveStoryCommand uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Story.Application.StoryRequest.RemoveStoryCommand, while a change to Story.Application.StoryRequest.RemoveStoryCommand can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Story.Application.StoryRequest.RemoveStoryCommand uses a module listed above it, which is the healthy direction.
36→19 Story.Application.StoryRequest.RemoveStoryCommand uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.RemoveStoryCommand uses a type in Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveStoryCommand.RemoveStoryError→Scrum.Seedwork.Application.ScrumRole
- Direction
- Story.Application.StoryRequest.RemoveStoryCommand uses Seedwork.Application, so a change to Seedwork.Application can break Story.Application.StoryRequest.RemoveStoryCommand, while a change to Story.Application.StoryRequest.RemoveStoryCommand can't break Seedwork.Application.
- Position
- Below the diagonal: Story.Application.StoryRequest.RemoveStoryCommand uses a module listed above it, which is the healthy direction.
36→31 Story.Application.StoryRequest.RemoveStoryCommand uses Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.RemoveStoryCommand uses a type in Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveStoryCommand.RemoveStoryValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Story.Application.StoryRequest.RemoveStoryCommand uses Story.Domain.StoryAggregate, so a change to Story.Domain.StoryAggregate can break Story.Application.StoryRequest.RemoveStoryCommand, while a change to Story.Application.StoryRequest.RemoveStoryCommand can't break Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Story.Application.StoryRequest.RemoveStoryCommand uses a module listed above it, which is the healthy direction.
37→7 Story.Application.StoryRequest.RemoveTaskCommand uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.RemoveTaskCommand uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveTaskCommand.RemoveTaskError→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Story.Application.StoryRequest.RemoveTaskCommand uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Story.Application.StoryRequest.RemoveTaskCommand, while a change to Story.Application.StoryRequest.RemoveTaskCommand can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Story.Application.StoryRequest.RemoveTaskCommand uses a module listed above it, which is the healthy direction.
37→19 Story.Application.StoryRequest.RemoveTaskCommand uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.RemoveTaskCommand uses a type in Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveTaskCommand.RemoveTaskError→Scrum.Seedwork.Application.ScrumRole
- Direction
- Story.Application.StoryRequest.RemoveTaskCommand uses Seedwork.Application, so a change to Seedwork.Application can break Story.Application.StoryRequest.RemoveTaskCommand, while a change to Story.Application.StoryRequest.RemoveTaskCommand can't break Seedwork.Application.
- Position
- Below the diagonal: Story.Application.StoryRequest.RemoveTaskCommand uses a module listed above it, which is the healthy direction.
37→25 Story.Application.StoryRequest.RemoveTaskCommand uses Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.RemoveTaskCommand uses a type in Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveTaskCommand.RemoveTaskValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskId
- Direction
- Story.Application.StoryRequest.RemoveTaskCommand uses Story.Domain.StoryAggregate.TaskEntity, so a change to Story.Domain.StoryAggregate.TaskEntity can break Story.Application.StoryRequest.RemoveTaskCommand, while a change to Story.Application.StoryRequest.RemoveTaskCommand can't break Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Story.Application.StoryRequest.RemoveTaskCommand uses a module listed above it, which is the healthy direction.
37→31 Story.Application.StoryRequest.RemoveTaskCommand uses Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.RemoveTaskCommand uses a type in Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveTaskCommand.RemoveTaskValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Story.Application.StoryRequest.RemoveTaskCommand uses Story.Domain.StoryAggregate, so a change to Story.Domain.StoryAggregate can break Story.Application.StoryRequest.RemoveTaskCommand, while a change to Story.Application.StoryRequest.RemoveTaskCommand can't break Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Story.Application.StoryRequest.RemoveTaskCommand uses a module listed above it, which is the healthy direction.
38→7 Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand.ReviseBasicStoryDetailsError→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand, while a change to Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses a module listed above it, which is the healthy direction.
38→19 Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses a type in Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand.ReviseBasicStoryDetailsError→Scrum.Seedwork.Application.ScrumRole
- Direction
- Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses Seedwork.Application, so a change to Seedwork.Application can break Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand, while a change to Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand can't break Seedwork.Application.
- Position
- Below the diagonal: Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses a module listed above it, which is the healthy direction.
38→31 Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses Story.Domain.StoryAggregate✕
- Connections
- 2 pairs of types, where a type in Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses a type in Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand.ReviseBasicStoryDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryIdScrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand.ReviseBasicStoryDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryTitle
- Direction
- Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses Story.Domain.StoryAggregate, so a change to Story.Domain.StoryAggregate can break Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand, while a change to Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand can't break Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand uses a module listed above it, which is the healthy direction.
39→7 Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses Seedwork.Domain.Validation.Guid✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses a type in Seedwork.Domain.Validation.Guid.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand.ReviseBasicTaskDetailsError→Scrum.Seedwork.Domain.Validation.Guid.Guid
- Direction
- Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses Seedwork.Domain.Validation.Guid, so a change to Seedwork.Domain.Validation.Guid can break Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand, while a change to Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand can't break Seedwork.Domain.Validation.Guid.
- Position
- Below the diagonal: Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses a module listed above it, which is the healthy direction.
39→19 Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses a type in Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand.ReviseBasicTaskDetailsError→Scrum.Seedwork.Application.ScrumRole
- Direction
- Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses Seedwork.Application, so a change to Seedwork.Application can break Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand, while a change to Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand can't break Seedwork.Application.
- Position
- Below the diagonal: Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses a module listed above it, which is the healthy direction.
39→25 Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 2 pairs of types, where a type in Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses a type in Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand.ReviseBasicTaskDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdScrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand.ReviseBasicTaskDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitle
- Direction
- Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses Story.Domain.StoryAggregate.TaskEntity, so a change to Story.Domain.StoryAggregate.TaskEntity can break Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand, while a change to Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand can't break Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses a module listed above it, which is the healthy direction.
39→31 Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses a type in Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand.ReviseBasicTaskDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses Story.Domain.StoryAggregate, so a change to Story.Domain.StoryAggregate can break Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand, while a change to Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand can't break Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand uses a module listed above it, which is the healthy direction.
40→31 Story.Application.StoryRequest.StoryDto uses Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Story.Application.StoryRequest.StoryDto uses a type in Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.StoryDto.StoryDto→Scrum.Story.Domain.StoryAggregate.Story
- Direction
- Story.Application.StoryRequest.StoryDto uses Story.Domain.StoryAggregate, so a change to Story.Domain.StoryAggregate can break Story.Application.StoryRequest.StoryDto, while a change to Story.Application.StoryRequest.StoryDto can't break Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Story.Application.StoryRequest.StoryDto uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 5 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | Medium |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2); Add a CI workflow that builds and runs the test suite on every push/PR; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). | +19.2 pts | Low | REDACTED Scanning |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +8.8 pts | Medium | CI/CD gates |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +3.2 pts | Medium | Deployment & Rollback |
| Resolve the 2 FileTooLong finding(s) in God Classes — start with Story.fs, Seedwork.fs. | +3.0 pts | Medium | God Classes |
| 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. | +1.0 pts | Medium | Documentation (README) |
| Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with Story.fs (2). | +1.0 pts | Medium | Code Duplication |
| Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with Story.fs (2). | +1.0 pts | Medium | Code Duplication |
| Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. | +0.3 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| src/Scrum/Story.fs | 7.0 | Near-clean | God Classes: FileTooLong: Scrum/Story.fs |
| src/Scrum/Seedwork.fs | 7.2 | Near-clean | God Classes: FileTooLong: Scrum/Seedwork.fs |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 8.6 | Near-clean | IaC & Container Security: Low IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 30 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 30 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, 27 of 30 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.fs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.fs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D6 Cohesion (LCOM4) — 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. 4 of 4 class(es) with two or more methods were found, but the language model this pass loaded exposed none of their method bodies, so which method touches which field could not be seen.
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the analyzer environment could not build/run this repository's test suite, whose production source is .fs. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed.
- D11 Test Reliability — 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. Test reliability NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry), so no test ever ran. This is OUR limitation, not a defect in the repo — it is excluded from the score. We track the analyzer-image gap so it can be closed.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.TargetFrameworkInference.targets(184,5): error NETSDK1045: The current .NET SDK does not support targeting .NET 11.0. Either target .NET 10.0 or lower, or use a version of the .NET SDK that supports .NET 11.0. Download the ….
- D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (22 line(s) across the 90-day window), but no complexity could be computed for .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- 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 400 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.
- 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. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Microsoft.Extensions.DependencyInjection registered from F#, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX2 Stateful singletons — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection singletons in C#, Spring/JSR-330/CDI singletons in Java and Kotlin, module state in Python request handlers, handler state in Go and Swift, Play controllers, Cask routes, Scalatra servlets, Finatra controllers, Akka/Pekko HTTP routes and JSR-330 singletons in Scala, Rails, Sinatra, Grape, Roda and Hanami handlers and Rack apps in Ruby, and module state in F# request handlers (Giraffe, Saturn, Falco, Oxpecker and Suave handlers and ASP.NET Core controllers) only, and this repository's product is written in F#, which was left unread, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 22 | RUN apt-get update -------------------- ERROR: failed to solve: process "/bin/sh -c gpg --no-default-keyring --keyring /usr/share/keyrings/k6-archive-keyring.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys C5AD17C747E3415A3642D57D77C6C491D6AC1D69" did not complete successfully: exit code: 2; runtime evidence skipped.
- C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/Scrum/Scrum.fsproj, tests/Scrum.Tests/Scrum.Tests.fsproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
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
- 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.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Story.fs, Seedwork.fs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
15 duplicated block group(s) detected. 14.6 % of the production lines (322 of 2,198) are in a reported copy.
What to do
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with Story.fs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with Story.fs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (19–20 lines × 2) finding(s) in Code Duplication — start with Seedwork.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D13 · REDACTED Scanning
2 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
What to do
- Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D14 · License Compliance
0 of 146 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 13 direct `PackageReference`(s), and 133 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
semgrep found no security issues.
D31 · IaC & Container Security
5 finding(s): 0 critical, 0 high, 0 medium, 5 low.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked.
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 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- 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.
M2 · Architecture documentation
M3 · Folder & project structure
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.
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — 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.
- `Directory.Packages.props` 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`. — Directory.Packages.props:7
What to do
- Run what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — 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.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
PF3 · Async & latency hygiene
X23 · Unguarded diagnostic materialisation
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 59% | Checked 2 of 11 | Acceptable, with room to improve. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 90% | Exemplary | Solid. |
| Readiness | 27% | Weak — gated by D13, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 95% | Checked 4 of 10 | Solid. |
| Domain Modelling | 100% | Exemplary | Solid. |
| Performance | 100% | Exemplary | Solid. |
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 — 93 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 22 | RUN apt-get update -------------------- ERROR: failed to solve: process "/bin/sh -c gpg --no-default-keyring --keyring /usr/share/keyrings/k6-archive-keyring.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys C5AD17C747E3415A3642D57D77C6C491D6AC1D69" did not complete successfully: exit code: 2; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .fs exposed no member bodies
- D10 Test Quality — ~384 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — analyzer environment
- D12 Dependency Hygiene — Dependency hygiene not measured
- D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D2 Cognitive Complexity — cognitive complexity not measured — .fs exposed no member bodies
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (605 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — 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 — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `src/Scrum` (2198 LoC, 123 module-visible types across 1 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- 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.
- 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.
- D6 Cohesion (LCOM4) — cohesion (LCOM4) not measured — the code model exposed no member bodies
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — analyzer environment
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 13 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- 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.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — 4 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 18 finding(s)
- FileTooLong: Scrum/Story.fs src/Scrum/Story.fs
- FileTooLong: Scrum/Seedwork.fs src/Scrum/Seedwork.fs
- Duplicated block (12 lines × 2) src/Scrum/Story.fs:1078
- Duplicated block (12 lines × 2) src/Scrum/Story.fs:395
- Duplicated block (11 lines × 2) src/Scrum/Story.fs:340
- Duplicated block (11 lines × 2) src/Scrum/Story.fs:987
- Duplicated block (19–20 lines × 2) src/Scrum/Seedwork.fs:791
- Duplicated block (11–15 lines × 2) src/Scrum/Story.fs:278
- Duplicated block (15 lines × 2) src/Scrum/Story.fs:1024
- Duplicated block (14 lines × 2) src/Scrum/Story.fs:935
- Duplicated block (11 lines × 3) src/Scrum/Story.fs:1111
- Duplicated block (10 lines × 2) src/Scrum/Seedwork.fs:815
- Duplicated block (8–9 lines × 7) src/Scrum/Story.fs:918
- Duplicated block (7–8 lines × 9) src/Scrum/Seedwork.fs:790
- Duplicated block (8 lines × 4) src/Scrum/Story.fs:933
- Duplicated block (7–8 lines × 3) src/Scrum/Story.fs:419
- Duplicated block (5 lines × 2) src/Scrum/Story.fs:823
- No CI pipeline
Minor — 8 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No SAST
- No dependency-update automation Directory.Packages.props:7
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-89a74da8e7174579bbb2dd24399f4151/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-89a74da8e7174579bbb2dd24399f4151/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-c5bba353d54246fb9314923b98857402 | 0 | artifacts/raw/osv-scanner.json |