Executive summary
ronnieholm/FSharp-onion-architecture-sample meets our standard for a template or a sample, though three passwords or keys sit in the current code and we found no working pipeline that builds or tests changes to the code. It scores 64 out of 100 and is rated Strong, and all seven of its critical findings are security problems.
Production Readiness, at 32, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 23 points. Replacing the two deprecated dependencies comes next, worth about 9 points. Raising Production Readiness to 52 would lift the score to about 73.
Three passwords or keys in the code and two in the code's history are open to anyone who can read the repository. Two known security holes in the packages the code depends on can be used by attackers. Replacing each exposed password or key and updating the vulnerable packages would close both risks.
The product code is 2,198 lines, about €4,000 to rebuild.
If Production Readiness rose from 32 to 52, the lowest score rated Strong, the score would rise from 64 to about 73.
Fixed since the last survey: 1 finding
- Code Coverage · Coverage not measured — no coverage collector is wired up
Rebuild cost: about €4,000 · Estimate
| Cost to rebuild | €1,300 to €6,700, for 22 to 70 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.9 at a score of 64. 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 AutoGeneratedProgram | 2 Scrum.Seedwork.Application | 3 Scrum.Seedwork.Application.EventRequest | 4 Scrum.Seedwork.Application.Models | 5 Scrum.Seedwork.Domain | 6 Scrum.Seedwork.Domain.Paging | 7 Scrum.Seedwork.Infrastructure | 8 Scrum.Seedwork.Infrastructure.Configuration | 9 Scrum.Story.Application.StoryRequest | 10 Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule | 11 Scrum.Seedwork.Application.ValidationErrorModule | 12 Scrum.Seedwork.Domain.Paging.CursorModule | 13 Scrum.Seedwork.Domain.Paging.LimitModule | 14 Scrum.Seedwork.Infrastructure.EventRepository | 15 Scrum.Seedwork.Infrastructure.ProblemDetails | 16 Scrum.Seedwork.Infrastructure.Repository | 17 Scrum.Seedwork.Infrastructure.ScrumLogger | 18 Scrum.Seedwork.Infrastructure.Service.IdentityProvider | 19 Scrum.Seedwork.Infrastructure.UserIdentity | 20 Scrum.Seedwork.RouteHandler | 21 Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule | 22 Scrum.Story.Domain.StoryAggregate.TaskEntity | 23 Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule | 24 Scrum.Story.Application.StoryRequest.TaskDtoModule | 25 Scrum.Story.Domain.StoryAggregate | 26 Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionModule | 27 Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdModule | 28 Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleModule | 29 Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule | 30 Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule | 31 Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule | 32 Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule | 33 Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule | 34 Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule | 35 Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule | 36 Scrum.Story.Application.StoryRequest.StoryDtoModule | 37 Scrum.Story.Domain.StoryAggregate.StoryDescriptionModule | 38 Scrum.Story.Domain.StoryAggregate.StoryIdModule | 39 Scrum.Story.Domain.StoryAggregate.StoryTitleModule | 40 Scrum.Story.Infrastructure.StoryRepository |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 AutoGeneratedProgram | ||||||||||||||||||||||||||||||||||||||||
| 2 Scrum.Seedwork.Application | ||||||||||||||||||||||||||||||||||||||||
| 3 Scrum.Seedwork.Application.EventRequest | ||||||||||||||||||||||||||||||||||||||||
| 4 Scrum.Seedwork.Application.Models | ||||||||||||||||||||||||||||||||||||||||
| 5 Scrum.Seedwork.Domain | ||||||||||||||||||||||||||||||||||||||||
| 6 Scrum.Seedwork.Domain.Paging | ||||||||||||||||||||||||||||||||||||||||
| 7 Scrum.Seedwork.Infrastructure | ||||||||||||||||||||||||||||||||||||||||
| 8 Scrum.Seedwork.Infrastructure.Configuration | ||||||||||||||||||||||||||||||||||||||||
| 9 Scrum.Story.Application.StoryRequest | ||||||||||||||||||||||||||||||||||||||||
| 10 Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule | 4 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 11 Scrum.Seedwork.Application.ValidationErrorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Scrum.Seedwork.Domain.Paging.CursorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Scrum.Seedwork.Domain.Paging.LimitModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Scrum.Seedwork.Infrastructure.EventRepository | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 15 Scrum.Seedwork.Infrastructure.ProblemDetails | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 Scrum.Seedwork.Infrastructure.Repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Scrum.Seedwork.Infrastructure.ScrumLogger | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Scrum.Seedwork.Infrastructure.Service.IdentityProvider | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Scrum.Seedwork.Infrastructure.UserIdentity | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Scrum.Seedwork.RouteHandler | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule | 4 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 22 Scrum.Story.Domain.StoryAggregate.TaskEntity | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Scrum.Story.Application.StoryRequest.TaskDtoModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Scrum.Story.Domain.StoryAggregate | 1 | 14 | ||||||||||||||||||||||||||||||||||||||
| 26 Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule | 4 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 30 Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule | 4 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 31 Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule | 4 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 34 Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule | 4 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 35 Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule | 4 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 36 Scrum.Story.Application.StoryRequest.StoryDtoModule | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 Scrum.Story.Domain.StoryAggregate.StoryDescriptionModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 Scrum.Story.Domain.StoryAggregate.StoryIdModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 Scrum.Story.Domain.StoryAggregate.StoryTitleModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 Scrum.Story.Infrastructure.StoryRepository | 3 | 2 | 3 |
10→2 Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses Scrum.Seedwork.Application✕
- Connections
- 4 pairs of types, where a type in Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.GetByAggregateIdError→Scrum.Seedwork.Application.ScrumRoleScrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.GetByAggregateIdError→Scrum.Seedwork.Application.ValidationErrorScrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.GetByAggregateIdQueryModule→Scrum.Seedwork.Application.ScrumIdentityScrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.GetByAggregateIdQueryModule→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule, while a change to Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses a module listed above it, which is the healthy direction.
10→3 Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses Scrum.Seedwork.Application.EventRequest✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses a type in Scrum.Seedwork.Application.EventRequest.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.GetByAggregateIdQueryModule→Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQuery
- Direction
- Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses Scrum.Seedwork.Application.EventRequest, so a change to Scrum.Seedwork.Application.EventRequest can break Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule, while a change to Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule can't break Scrum.Seedwork.Application.EventRequest.
- Position
- Below the diagonal: Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses a module listed above it, which is the healthy direction.
10→4 Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses Scrum.Seedwork.Application.Models✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses a type in Scrum.Seedwork.Application.Models.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.GetByAggregateIdQueryModule→Scrum.Seedwork.Application.Models.PagedDto`1
- Direction
- Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses Scrum.Seedwork.Application.Models, so a change to Scrum.Seedwork.Application.Models can break Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule, while a change to Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule can't break Scrum.Seedwork.Application.Models.
- Position
- Below the diagonal: Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses a module listed above it, which is the healthy direction.
10→6 Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses Scrum.Seedwork.Domain.Paging✕
- Connections
- 2 pairs of types, where a type in Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses a type in Scrum.Seedwork.Domain.Paging.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.GetByAggregateIdValidatedQuery→Scrum.Seedwork.Domain.Paging.CursorScrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.GetByAggregateIdValidatedQuery→Scrum.Seedwork.Domain.Paging.Limit
- Direction
- Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses Scrum.Seedwork.Domain.Paging, so a change to Scrum.Seedwork.Domain.Paging can break Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule, while a change to Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule can't break Scrum.Seedwork.Domain.Paging.
- Position
- Below the diagonal: Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule uses a module listed above it, which is the healthy direction.
11→2 Scrum.Seedwork.Application.ValidationErrorModule uses Scrum.Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Application.ValidationErrorModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Seedwork.Application.ValidationErrorModule.ValidationErrorModule→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Seedwork.Application.ValidationErrorModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Seedwork.Application.ValidationErrorModule, while a change to Scrum.Seedwork.Application.ValidationErrorModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Seedwork.Application.ValidationErrorModule uses a module listed above it, which is the healthy direction.
12→6 Scrum.Seedwork.Domain.Paging.CursorModule uses Scrum.Seedwork.Domain.Paging✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Domain.Paging.CursorModule uses a type in Scrum.Seedwork.Domain.Paging.
- The types involved
Scrum.Seedwork.Domain.Paging.CursorModule.CursorModule→Scrum.Seedwork.Domain.Paging.Cursor
- Direction
- Scrum.Seedwork.Domain.Paging.CursorModule uses Scrum.Seedwork.Domain.Paging, so a change to Scrum.Seedwork.Domain.Paging can break Scrum.Seedwork.Domain.Paging.CursorModule, while a change to Scrum.Seedwork.Domain.Paging.CursorModule can't break Scrum.Seedwork.Domain.Paging.
- Position
- Below the diagonal: Scrum.Seedwork.Domain.Paging.CursorModule uses a module listed above it, which is the healthy direction.
13→6 Scrum.Seedwork.Domain.Paging.LimitModule uses Scrum.Seedwork.Domain.Paging✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Domain.Paging.LimitModule uses a type in Scrum.Seedwork.Domain.Paging.
- The types involved
Scrum.Seedwork.Domain.Paging.LimitModule.LimitModule→Scrum.Seedwork.Domain.Paging.Limit
- Direction
- Scrum.Seedwork.Domain.Paging.LimitModule uses Scrum.Seedwork.Domain.Paging, so a change to Scrum.Seedwork.Domain.Paging can break Scrum.Seedwork.Domain.Paging.LimitModule, while a change to Scrum.Seedwork.Domain.Paging.LimitModule can't break Scrum.Seedwork.Domain.Paging.
- Position
- Below the diagonal: Scrum.Seedwork.Domain.Paging.LimitModule uses a module listed above it, which is the healthy direction.
14→2 Scrum.Seedwork.Infrastructure.EventRepository uses Scrum.Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Infrastructure.EventRepository uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Seedwork.Infrastructure.EventRepository.EventRepository→Scrum.Seedwork.Application.PersistedEvent
- Direction
- Scrum.Seedwork.Infrastructure.EventRepository uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Seedwork.Infrastructure.EventRepository, while a change to Scrum.Seedwork.Infrastructure.EventRepository can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Seedwork.Infrastructure.EventRepository uses a module listed above it, which is the healthy direction.
14→6 Scrum.Seedwork.Infrastructure.EventRepository uses Scrum.Seedwork.Domain.Paging✕
- Connections
- 3 pairs of types, where a type in Scrum.Seedwork.Infrastructure.EventRepository uses a type in Scrum.Seedwork.Domain.Paging.
- The types involved
Scrum.Seedwork.Infrastructure.EventRepository.EventRepository→Scrum.Seedwork.Domain.Paging.CursorScrum.Seedwork.Infrastructure.EventRepository.EventRepository→Scrum.Seedwork.Domain.Paging.LimitScrum.Seedwork.Infrastructure.EventRepository.EventRepository→Scrum.Seedwork.Domain.Paging.Paged`1
- Direction
- Scrum.Seedwork.Infrastructure.EventRepository uses Scrum.Seedwork.Domain.Paging, so a change to Scrum.Seedwork.Domain.Paging can break Scrum.Seedwork.Infrastructure.EventRepository, while a change to Scrum.Seedwork.Infrastructure.EventRepository can't break Scrum.Seedwork.Domain.Paging.
- Position
- Below the diagonal: Scrum.Seedwork.Infrastructure.EventRepository uses a module listed above it, which is the healthy direction.
15→2 Scrum.Seedwork.Infrastructure.ProblemDetails uses Scrum.Seedwork.Application✕
- Connections
- 2 pairs of types, where a type in Scrum.Seedwork.Infrastructure.ProblemDetails uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Seedwork.Infrastructure.ProblemDetails.ProblemDetails→Scrum.Seedwork.Application.ScrumRoleScrum.Seedwork.Infrastructure.ProblemDetails.ProblemDetails→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Seedwork.Infrastructure.ProblemDetails uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Seedwork.Infrastructure.ProblemDetails, while a change to Scrum.Seedwork.Infrastructure.ProblemDetails can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Seedwork.Infrastructure.ProblemDetails uses a module listed above it, which is the healthy direction.
15→7 Scrum.Seedwork.Infrastructure.ProblemDetails uses Scrum.Seedwork.Infrastructure✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Infrastructure.ProblemDetails uses a type in Scrum.Seedwork.Infrastructure.
- The types involved
Scrum.Seedwork.Infrastructure.ProblemDetails.ProblemDetails→Scrum.Seedwork.Infrastructure.ProblemDetails2
- Direction
- Scrum.Seedwork.Infrastructure.ProblemDetails uses Scrum.Seedwork.Infrastructure, so a change to Scrum.Seedwork.Infrastructure can break Scrum.Seedwork.Infrastructure.ProblemDetails, while a change to Scrum.Seedwork.Infrastructure.ProblemDetails can't break Scrum.Seedwork.Infrastructure.
- Position
- Below the diagonal: Scrum.Seedwork.Infrastructure.ProblemDetails uses a module listed above it, which is the healthy direction.
16→6 Scrum.Seedwork.Infrastructure.Repository uses Scrum.Seedwork.Domain.Paging✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Infrastructure.Repository uses a type in Scrum.Seedwork.Domain.Paging.
- The types involved
Scrum.Seedwork.Infrastructure.Repository.Repository→Scrum.Seedwork.Domain.Paging.Cursor
- Direction
- Scrum.Seedwork.Infrastructure.Repository uses Scrum.Seedwork.Domain.Paging, so a change to Scrum.Seedwork.Domain.Paging can break Scrum.Seedwork.Infrastructure.Repository, while a change to Scrum.Seedwork.Infrastructure.Repository can't break Scrum.Seedwork.Domain.Paging.
- Position
- Below the diagonal: Scrum.Seedwork.Infrastructure.Repository uses a module listed above it, which is the healthy direction.
17→2 Scrum.Seedwork.Infrastructure.ScrumLogger uses Scrum.Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Infrastructure.ScrumLogger uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Seedwork.Infrastructure.ScrumLogger.ScrumLogger→Scrum.Seedwork.Application.LogMessage
- Direction
- Scrum.Seedwork.Infrastructure.ScrumLogger uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Seedwork.Infrastructure.ScrumLogger, while a change to Scrum.Seedwork.Infrastructure.ScrumLogger can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Seedwork.Infrastructure.ScrumLogger uses a module listed above it, which is the healthy direction.
18→2 Scrum.Seedwork.Infrastructure.Service.IdentityProvider uses Scrum.Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Infrastructure.Service.IdentityProvider uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Seedwork.Infrastructure.Service.IdentityProvider.IdentityProvider→Scrum.Seedwork.Application.ScrumIdentity
- Direction
- Scrum.Seedwork.Infrastructure.Service.IdentityProvider uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Seedwork.Infrastructure.Service.IdentityProvider, while a change to Scrum.Seedwork.Infrastructure.Service.IdentityProvider can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Seedwork.Infrastructure.Service.IdentityProvider uses a module listed above it, which is the healthy direction.
18→8 Scrum.Seedwork.Infrastructure.Service.IdentityProvider uses Scrum.Seedwork.Infrastructure.Configuration✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Infrastructure.Service.IdentityProvider uses a type in Scrum.Seedwork.Infrastructure.Configuration.
- The types involved
Scrum.Seedwork.Infrastructure.Service.IdentityProvider.IdentityProvider→Scrum.Seedwork.Infrastructure.Configuration.JwtAuthenticationSettings
- Direction
- Scrum.Seedwork.Infrastructure.Service.IdentityProvider uses Scrum.Seedwork.Infrastructure.Configuration, so a change to Scrum.Seedwork.Infrastructure.Configuration can break Scrum.Seedwork.Infrastructure.Service.IdentityProvider, while a change to Scrum.Seedwork.Infrastructure.Service.IdentityProvider can't break Scrum.Seedwork.Infrastructure.Configuration.
- Position
- Below the diagonal: Scrum.Seedwork.Infrastructure.Service.IdentityProvider uses a module listed above it, which is the healthy direction.
19→2 Scrum.Seedwork.Infrastructure.UserIdentity uses Scrum.Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Infrastructure.UserIdentity uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Seedwork.Infrastructure.UserIdentity.UserIdentity→Scrum.Seedwork.Application.ScrumIdentity
- Direction
- Scrum.Seedwork.Infrastructure.UserIdentity uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Seedwork.Infrastructure.UserIdentity, while a change to Scrum.Seedwork.Infrastructure.UserIdentity can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Seedwork.Infrastructure.UserIdentity uses a module listed above it, which is the healthy direction.
20→7 Scrum.Seedwork.RouteHandler uses Scrum.Seedwork.Infrastructure✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.RouteHandler uses a type in Scrum.Seedwork.Infrastructure.
- The types involved
Scrum.Seedwork.RouteHandler.RouteHandler→Scrum.Seedwork.Infrastructure.ProblemDetails2
- Direction
- Scrum.Seedwork.RouteHandler uses Scrum.Seedwork.Infrastructure, so a change to Scrum.Seedwork.Infrastructure can break Scrum.Seedwork.RouteHandler, while a change to Scrum.Seedwork.RouteHandler can't break Scrum.Seedwork.Infrastructure.
- Position
- Below the diagonal: Scrum.Seedwork.RouteHandler uses a module listed above it, which is the healthy direction.
21→2 Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses Scrum.Seedwork.Application✕
- Connections
- 4 pairs of types, where a type in Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule.GetStoriesPagedError→Scrum.Seedwork.Application.ScrumRoleScrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule.GetStoriesPagedError→Scrum.Seedwork.Application.ValidationErrorScrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule.GetStoriesPagedQueryModule→Scrum.Seedwork.Application.ScrumIdentityScrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule.GetStoriesPagedQueryModule→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule, while a change to Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses a module listed above it, which is the healthy direction.
21→4 Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses Scrum.Seedwork.Application.Models✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses a type in Scrum.Seedwork.Application.Models.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule.GetStoriesPagedQueryModule→Scrum.Seedwork.Application.Models.PagedDto`1
- Direction
- Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses Scrum.Seedwork.Application.Models, so a change to Scrum.Seedwork.Application.Models can break Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule, while a change to Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule can't break Scrum.Seedwork.Application.Models.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses a module listed above it, which is the healthy direction.
21→6 Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses Scrum.Seedwork.Domain.Paging✕
- Connections
- 2 pairs of types, where a type in Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses a type in Scrum.Seedwork.Domain.Paging.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule.GetStoriesPagedValidatedQuery→Scrum.Seedwork.Domain.Paging.CursorScrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule.GetStoriesPagedValidatedQuery→Scrum.Seedwork.Domain.Paging.Limit
- Direction
- Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses Scrum.Seedwork.Domain.Paging, so a change to Scrum.Seedwork.Domain.Paging can break Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule, while a change to Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule can't break Scrum.Seedwork.Domain.Paging.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses a module listed above it, which is the healthy direction.
21→9 Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses Scrum.Story.Application.StoryRequest✕
- Connections
- 2 pairs of types, where a type in Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses a type in Scrum.Story.Application.StoryRequest.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule.GetStoriesPagedQueryModule→Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryScrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule.GetStoriesPagedQueryModule→Scrum.Story.Application.StoryRequest.StoryDto
- Direction
- Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses Scrum.Story.Application.StoryRequest, so a change to Scrum.Story.Application.StoryRequest can break Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule, while a change to Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule can't break Scrum.Story.Application.StoryRequest.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.GetStoriesPagedQueryModule uses a module listed above it, which is the healthy direction.
22→5 Scrum.Story.Domain.StoryAggregate.TaskEntity uses Scrum.Seedwork.Domain✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Domain.StoryAggregate.TaskEntity uses a type in Scrum.Seedwork.Domain.
- The types involved
Scrum.Story.Domain.StoryAggregate.TaskEntity.Task→Scrum.Seedwork.Domain.Entity`1
- Direction
- Scrum.Story.Domain.StoryAggregate.TaskEntity uses Scrum.Seedwork.Domain, so a change to Scrum.Seedwork.Domain can break Scrum.Story.Domain.StoryAggregate.TaskEntity, while a change to Scrum.Story.Domain.StoryAggregate.TaskEntity can't break Scrum.Seedwork.Domain.
- Position
- Below the diagonal: Scrum.Story.Domain.StoryAggregate.TaskEntity uses a module listed above it, which is the healthy direction.
23→2 Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule uses Scrum.Seedwork.Application✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule.PersistedEventDtoModule→Scrum.Seedwork.Application.PersistedEvent
- Direction
- Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule, while a change to Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule uses a module listed above it, which is the healthy direction.
23→10 Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule uses Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule✕
- Connections
- 1 pair of types, where a type in Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule uses a type in Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.
- The types involved
Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule.PersistedEventDtoModule→Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDto
- Direction
- Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule uses Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule, so a change to Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule can break Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule, while a change to Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule can't break Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.
- Position
- Below the diagonal: Scrum.Seedwork.Application.EventRequest.GetByAggregateIdQueryModule.PersistedEventDtoModule uses a module listed above it, which is the healthy direction.
24→9 Scrum.Story.Application.StoryRequest.TaskDtoModule uses Scrum.Story.Application.StoryRequest✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.TaskDtoModule uses a type in Scrum.Story.Application.StoryRequest.
- The types involved
Scrum.Story.Application.StoryRequest.TaskDtoModule.TaskDtoModule→Scrum.Story.Application.StoryRequest.TaskDto
- Direction
- Scrum.Story.Application.StoryRequest.TaskDtoModule uses Scrum.Story.Application.StoryRequest, so a change to Scrum.Story.Application.StoryRequest can break Scrum.Story.Application.StoryRequest.TaskDtoModule, while a change to Scrum.Story.Application.StoryRequest.TaskDtoModule can't break Scrum.Story.Application.StoryRequest.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.TaskDtoModule uses a module listed above it, which is the healthy direction.
24→22 Scrum.Story.Application.StoryRequest.TaskDtoModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.TaskDtoModule uses a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Application.StoryRequest.TaskDtoModule.TaskDtoModule→Scrum.Story.Domain.StoryAggregate.TaskEntity.Task
- Direction
- Scrum.Story.Application.StoryRequest.TaskDtoModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity, so a change to Scrum.Story.Domain.StoryAggregate.TaskEntity can break Scrum.Story.Application.StoryRequest.TaskDtoModule, while a change to Scrum.Story.Application.StoryRequest.TaskDtoModule can't break Scrum.Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.TaskDtoModule uses a module listed above it, which is the healthy direction.
25→5 Scrum.Story.Domain.StoryAggregate uses Scrum.Seedwork.Domain✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Domain.StoryAggregate uses a type in Scrum.Seedwork.Domain.
- The types involved
Scrum.Story.Domain.StoryAggregate.Story→Scrum.Seedwork.Domain.AggregateRoot`1
- Direction
- Scrum.Story.Domain.StoryAggregate uses Scrum.Seedwork.Domain, so a change to Scrum.Seedwork.Domain can break Scrum.Story.Domain.StoryAggregate, while a change to Scrum.Story.Domain.StoryAggregate can't break Scrum.Seedwork.Domain.
- Position
- Below the diagonal: Scrum.Story.Domain.StoryAggregate uses a module listed above it, which is the healthy direction.
25→22 Scrum.Story.Domain.StoryAggregate uses Scrum.Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 14 pairs of types, where a type in Scrum.Story.Domain.StoryAggregate uses a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Domain.StoryAggregate.AddBasicTaskDetailsToStory→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionScrum.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.TaskDescriptionScrum.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.TaskIdScrum.Story.Domain.StoryAggregate.Story→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskScrum.Story.Domain.StoryAggregate.StoryAggregate→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionScrum.Story.Domain.StoryAggregate.StoryAggregate→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdScrum.Story.Domain.StoryAggregate.StoryAggregate→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitle
- Direction
- Scrum.Story.Domain.StoryAggregate uses Scrum.Story.Domain.StoryAggregate.TaskEntity, so a change to Scrum.Story.Domain.StoryAggregate.TaskEntity can break Scrum.Story.Domain.StoryAggregate, while a change to Scrum.Story.Domain.StoryAggregate can't break Scrum.Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Scrum.Story.Domain.StoryAggregate uses a module listed above it, which is the healthy direction.
26→22 Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionModule uses a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionModule.TaskDescriptionModule→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescription
- Direction
- Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity, so a change to Scrum.Story.Domain.StoryAggregate.TaskEntity can break Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionModule, while a change to Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionModule can't break Scrum.Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionModule uses a module listed above it, which is the healthy direction.
27→22 Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdModule uses a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdModule.TaskIdModule→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskId
- Direction
- Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity, so a change to Scrum.Story.Domain.StoryAggregate.TaskEntity can break Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdModule, while a change to Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdModule can't break Scrum.Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdModule uses a module listed above it, which is the healthy direction.
28→22 Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleModule uses a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleModule.TaskTitleModule→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitle
- Direction
- Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity, so a change to Scrum.Story.Domain.StoryAggregate.TaskEntity can break Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleModule, while a change to Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleModule can't break Scrum.Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitleModule uses a module listed above it, which is the healthy direction.
29→2 Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses Scrum.Seedwork.Application✕
- Connections
- 4 pairs of types, where a type in Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule.AddBasicTaskDetailsToStoryCommandModule→Scrum.Seedwork.Application.ScrumIdentityScrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule.AddBasicTaskDetailsToStoryCommandModule→Scrum.Seedwork.Application.ValidationErrorScrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule.AddBasicTaskDetailsToStoryError→Scrum.Seedwork.Application.ScrumRoleScrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule.AddBasicTaskDetailsToStoryError→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule, while a change to Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses a module listed above it, which is the healthy direction.
29→9 Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses Scrum.Story.Application.StoryRequest✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses a type in Scrum.Story.Application.StoryRequest.
- The types involved
Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule.AddBasicTaskDetailsToStoryCommandModule→Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommand
- Direction
- Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses Scrum.Story.Application.StoryRequest, so a change to Scrum.Story.Application.StoryRequest can break Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule, while a change to Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule can't break Scrum.Story.Application.StoryRequest.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses a module listed above it, which is the healthy direction.
29→22 Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 3 pairs of types, where a type in Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule.AddBasicTaskDetailsToStoryValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionScrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule.AddBasicTaskDetailsToStoryValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdScrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule.AddBasicTaskDetailsToStoryValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitle
- Direction
- Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity, so a change to Scrum.Story.Domain.StoryAggregate.TaskEntity can break Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule, while a change to Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule can't break Scrum.Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses a module listed above it, which is the healthy direction.
29→25 Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 2 pairs of types, where a type in Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule.AddBasicTaskDetailsToStoryCommandModule→Scrum.Story.Domain.StoryAggregate.AddBasicTaskDetailsToStoryErrorScrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule.AddBasicTaskDetailsToStoryValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule, while a change to Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.AddBasicTaskDetailsToStoryCommandModule uses a module listed above it, which is the healthy direction.
30→2 Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses Scrum.Seedwork.Application✕
- Connections
- 4 pairs of types, where a type in Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule.CaptureBasicStoryDetailsCommandModule→Scrum.Seedwork.Application.ScrumIdentityScrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule.CaptureBasicStoryDetailsCommandModule→Scrum.Seedwork.Application.ValidationErrorScrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule.CaptureBasicStoryDetailsError→Scrum.Seedwork.Application.ScrumRoleScrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule.CaptureBasicStoryDetailsError→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule, while a change to Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses a module listed above it, which is the healthy direction.
30→9 Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses Scrum.Story.Application.StoryRequest✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses a type in Scrum.Story.Application.StoryRequest.
- The types involved
Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule.CaptureBasicStoryDetailsCommandModule→Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommand
- Direction
- Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses Scrum.Story.Application.StoryRequest, so a change to Scrum.Story.Application.StoryRequest can break Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule, while a change to Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule can't break Scrum.Story.Application.StoryRequest.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses a module listed above it, which is the healthy direction.
30→25 Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 3 pairs of types, where a type in Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule.CaptureBasicStoryDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryDescriptionScrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule.CaptureBasicStoryDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryIdScrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule.CaptureBasicStoryDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryTitle
- Direction
- Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule, while a change to Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.CaptureBasicStoryDetailsCommandModule uses a module listed above it, which is the healthy direction.
31→2 Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses Scrum.Seedwork.Application✕
- Connections
- 4 pairs of types, where a type in Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule.GetStoryByIdError→Scrum.Seedwork.Application.ScrumRoleScrum.Story.Application.StoryRequest.GetStoryByIdQueryModule.GetStoryByIdError→Scrum.Seedwork.Application.ValidationErrorScrum.Story.Application.StoryRequest.GetStoryByIdQueryModule.GetStoryByIdQueryModule→Scrum.Seedwork.Application.ScrumIdentityScrum.Story.Application.StoryRequest.GetStoryByIdQueryModule.GetStoryByIdQueryModule→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule, while a change to Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses a module listed above it, which is the healthy direction.
31→9 Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses Scrum.Story.Application.StoryRequest✕
- Connections
- 2 pairs of types, where a type in Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses a type in Scrum.Story.Application.StoryRequest.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule.GetStoryByIdQueryModule→Scrum.Story.Application.StoryRequest.GetStoryByIdQueryScrum.Story.Application.StoryRequest.GetStoryByIdQueryModule.GetStoryByIdQueryModule→Scrum.Story.Application.StoryRequest.StoryDto
- Direction
- Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses Scrum.Story.Application.StoryRequest, so a change to Scrum.Story.Application.StoryRequest can break Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule, while a change to Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule can't break Scrum.Story.Application.StoryRequest.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses a module listed above it, which is the healthy direction.
31→25 Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule.GetStoryByIdValidatedQuery→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule, while a change to Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.GetStoryByIdQueryModule uses a module listed above it, which is the healthy direction.
32→2 Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses Scrum.Seedwork.Application✕
- Connections
- 4 pairs of types, where a type in Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule.RemoveStoryCommandModule→Scrum.Seedwork.Application.ScrumIdentityScrum.Story.Application.StoryRequest.RemoveStoryCommandModule.RemoveStoryCommandModule→Scrum.Seedwork.Application.ValidationErrorScrum.Story.Application.StoryRequest.RemoveStoryCommandModule.RemoveStoryError→Scrum.Seedwork.Application.ScrumRoleScrum.Story.Application.StoryRequest.RemoveStoryCommandModule.RemoveStoryError→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule, while a change to Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses a module listed above it, which is the healthy direction.
32→9 Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses Scrum.Story.Application.StoryRequest✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses a type in Scrum.Story.Application.StoryRequest.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule.RemoveStoryCommandModule→Scrum.Story.Application.StoryRequest.RemoveStoryCommand
- Direction
- Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses Scrum.Story.Application.StoryRequest, so a change to Scrum.Story.Application.StoryRequest can break Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule, while a change to Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule can't break Scrum.Story.Application.StoryRequest.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses a module listed above it, which is the healthy direction.
32→25 Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule.RemoveStoryValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule, while a change to Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.RemoveStoryCommandModule uses a module listed above it, which is the healthy direction.
33→2 Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses Scrum.Seedwork.Application✕
- Connections
- 4 pairs of types, where a type in Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule.RemoveTaskCommandModule→Scrum.Seedwork.Application.ScrumIdentityScrum.Story.Application.StoryRequest.RemoveTaskCommandModule.RemoveTaskCommandModule→Scrum.Seedwork.Application.ValidationErrorScrum.Story.Application.StoryRequest.RemoveTaskCommandModule.RemoveTaskError→Scrum.Seedwork.Application.ScrumRoleScrum.Story.Application.StoryRequest.RemoveTaskCommandModule.RemoveTaskError→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule, while a change to Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses a module listed above it, which is the healthy direction.
33→9 Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses Scrum.Story.Application.StoryRequest✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses a type in Scrum.Story.Application.StoryRequest.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule.RemoveTaskCommandModule→Scrum.Story.Application.StoryRequest.RemoveTaskCommand
- Direction
- Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses Scrum.Story.Application.StoryRequest, so a change to Scrum.Story.Application.StoryRequest can break Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule, while a change to Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule can't break Scrum.Story.Application.StoryRequest.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses a module listed above it, which is the healthy direction.
33→22 Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule.RemoveTaskValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskId
- Direction
- Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity, so a change to Scrum.Story.Domain.StoryAggregate.TaskEntity can break Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule, while a change to Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule can't break Scrum.Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses a module listed above it, which is the healthy direction.
33→25 Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 2 pairs of types, where a type in Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule.RemoveTaskCommandModule→Scrum.Story.Domain.StoryAggregate.RemoveTaskErrorScrum.Story.Application.StoryRequest.RemoveTaskCommandModule.RemoveTaskValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule, while a change to Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.RemoveTaskCommandModule uses a module listed above it, which is the healthy direction.
34→2 Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses Scrum.Seedwork.Application✕
- Connections
- 4 pairs of types, where a type in Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule.ReviseBasicStoryDetailsCommandModule→Scrum.Seedwork.Application.ScrumIdentityScrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule.ReviseBasicStoryDetailsCommandModule→Scrum.Seedwork.Application.ValidationErrorScrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule.ReviseBasicStoryDetailsError→Scrum.Seedwork.Application.ScrumRoleScrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule.ReviseBasicStoryDetailsError→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule, while a change to Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses a module listed above it, which is the healthy direction.
34→9 Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses Scrum.Story.Application.StoryRequest✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses a type in Scrum.Story.Application.StoryRequest.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule.ReviseBasicStoryDetailsCommandModule→Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommand
- Direction
- Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses Scrum.Story.Application.StoryRequest, so a change to Scrum.Story.Application.StoryRequest can break Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule, while a change to Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule can't break Scrum.Story.Application.StoryRequest.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses a module listed above it, which is the healthy direction.
34→25 Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 3 pairs of types, where a type in Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule.ReviseBasicStoryDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryDescriptionScrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule.ReviseBasicStoryDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryIdScrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule.ReviseBasicStoryDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryTitle
- Direction
- Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule, while a change to Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.ReviseBasicStoryDetailsCommandModule uses a module listed above it, which is the healthy direction.
35→2 Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses Scrum.Seedwork.Application✕
- Connections
- 4 pairs of types, where a type in Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses a type in Scrum.Seedwork.Application.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule.ReviseBasicTaskDetailsCommandModule→Scrum.Seedwork.Application.ScrumIdentityScrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule.ReviseBasicTaskDetailsCommandModule→Scrum.Seedwork.Application.ValidationErrorScrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule.ReviseBasicTaskDetailsError→Scrum.Seedwork.Application.ScrumRoleScrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule.ReviseBasicTaskDetailsError→Scrum.Seedwork.Application.ValidationError
- Direction
- Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses Scrum.Seedwork.Application, so a change to Scrum.Seedwork.Application can break Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule, while a change to Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule can't break Scrum.Seedwork.Application.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses a module listed above it, which is the healthy direction.
35→9 Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses Scrum.Story.Application.StoryRequest✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses a type in Scrum.Story.Application.StoryRequest.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule.ReviseBasicTaskDetailsCommandModule→Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommand
- Direction
- Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses Scrum.Story.Application.StoryRequest, so a change to Scrum.Story.Application.StoryRequest can break Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule, while a change to Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule can't break Scrum.Story.Application.StoryRequest.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses a module listed above it, which is the healthy direction.
35→22 Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 3 pairs of types, where a type in Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule.ReviseBasicTaskDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskDescriptionScrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule.ReviseBasicTaskDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskIdScrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule.ReviseBasicTaskDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskTitle
- Direction
- Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses Scrum.Story.Domain.StoryAggregate.TaskEntity, so a change to Scrum.Story.Domain.StoryAggregate.TaskEntity can break Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule, while a change to Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule can't break Scrum.Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses a module listed above it, which is the healthy direction.
35→25 Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 2 pairs of types, where a type in Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule.ReviseBasicTaskDetailsCommandModule→Scrum.Story.Domain.StoryAggregate.ReviseBasicTaskDetailsErrorScrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule.ReviseBasicTaskDetailsValidatedCommand→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule, while a change to Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.ReviseBasicTaskDetailsCommandModule uses a module listed above it, which is the healthy direction.
36→9 Scrum.Story.Application.StoryRequest.StoryDtoModule uses Scrum.Story.Application.StoryRequest✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.StoryDtoModule uses a type in Scrum.Story.Application.StoryRequest.
- The types involved
Scrum.Story.Application.StoryRequest.StoryDtoModule.StoryDtoModule→Scrum.Story.Application.StoryRequest.StoryDto
- Direction
- Scrum.Story.Application.StoryRequest.StoryDtoModule uses Scrum.Story.Application.StoryRequest, so a change to Scrum.Story.Application.StoryRequest can break Scrum.Story.Application.StoryRequest.StoryDtoModule, while a change to Scrum.Story.Application.StoryRequest.StoryDtoModule can't break Scrum.Story.Application.StoryRequest.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.StoryDtoModule uses a module listed above it, which is the healthy direction.
36→25 Scrum.Story.Application.StoryRequest.StoryDtoModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Application.StoryRequest.StoryDtoModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Application.StoryRequest.StoryDtoModule.StoryDtoModule→Scrum.Story.Domain.StoryAggregate.Story
- Direction
- Scrum.Story.Application.StoryRequest.StoryDtoModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Application.StoryRequest.StoryDtoModule, while a change to Scrum.Story.Application.StoryRequest.StoryDtoModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Application.StoryRequest.StoryDtoModule uses a module listed above it, which is the healthy direction.
37→25 Scrum.Story.Domain.StoryAggregate.StoryDescriptionModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Domain.StoryAggregate.StoryDescriptionModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Domain.StoryAggregate.StoryDescriptionModule.StoryDescriptionModule→Scrum.Story.Domain.StoryAggregate.StoryDescription
- Direction
- Scrum.Story.Domain.StoryAggregate.StoryDescriptionModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Domain.StoryAggregate.StoryDescriptionModule, while a change to Scrum.Story.Domain.StoryAggregate.StoryDescriptionModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Domain.StoryAggregate.StoryDescriptionModule uses a module listed above it, which is the healthy direction.
38→25 Scrum.Story.Domain.StoryAggregate.StoryIdModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Domain.StoryAggregate.StoryIdModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Domain.StoryAggregate.StoryIdModule.StoryIdModule→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Scrum.Story.Domain.StoryAggregate.StoryIdModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Domain.StoryAggregate.StoryIdModule, while a change to Scrum.Story.Domain.StoryAggregate.StoryIdModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Domain.StoryAggregate.StoryIdModule uses a module listed above it, which is the healthy direction.
39→25 Scrum.Story.Domain.StoryAggregate.StoryTitleModule uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 1 pair of types, where a type in Scrum.Story.Domain.StoryAggregate.StoryTitleModule uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Domain.StoryAggregate.StoryTitleModule.StoryTitleModule→Scrum.Story.Domain.StoryAggregate.StoryTitle
- Direction
- Scrum.Story.Domain.StoryAggregate.StoryTitleModule uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Domain.StoryAggregate.StoryTitleModule, while a change to Scrum.Story.Domain.StoryAggregate.StoryTitleModule can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Domain.StoryAggregate.StoryTitleModule uses a module listed above it, which is the healthy direction.
40→6 Scrum.Story.Infrastructure.StoryRepository uses Scrum.Seedwork.Domain.Paging✕
- Connections
- 3 pairs of types, where a type in Scrum.Story.Infrastructure.StoryRepository uses a type in Scrum.Seedwork.Domain.Paging.
- The types involved
Scrum.Story.Infrastructure.StoryRepository.StoryRepository→Scrum.Seedwork.Domain.Paging.CursorScrum.Story.Infrastructure.StoryRepository.StoryRepository→Scrum.Seedwork.Domain.Paging.LimitScrum.Story.Infrastructure.StoryRepository.StoryRepository→Scrum.Seedwork.Domain.Paging.Paged`1
- Direction
- Scrum.Story.Infrastructure.StoryRepository uses Scrum.Seedwork.Domain.Paging, so a change to Scrum.Seedwork.Domain.Paging can break Scrum.Story.Infrastructure.StoryRepository, while a change to Scrum.Story.Infrastructure.StoryRepository can't break Scrum.Seedwork.Domain.Paging.
- Position
- Below the diagonal: Scrum.Story.Infrastructure.StoryRepository uses a module listed above it, which is the healthy direction.
40→22 Scrum.Story.Infrastructure.StoryRepository uses Scrum.Story.Domain.StoryAggregate.TaskEntity✕
- Connections
- 2 pairs of types, where a type in Scrum.Story.Infrastructure.StoryRepository uses a type in Scrum.Story.Domain.StoryAggregate.TaskEntity.
- The types involved
Scrum.Story.Infrastructure.StoryRepository.StoryRepository→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskScrum.Story.Infrastructure.StoryRepository.StoryRepository→Scrum.Story.Domain.StoryAggregate.TaskEntity.TaskId
- Direction
- Scrum.Story.Infrastructure.StoryRepository uses Scrum.Story.Domain.StoryAggregate.TaskEntity, so a change to Scrum.Story.Domain.StoryAggregate.TaskEntity can break Scrum.Story.Infrastructure.StoryRepository, while a change to Scrum.Story.Infrastructure.StoryRepository can't break Scrum.Story.Domain.StoryAggregate.TaskEntity.
- Position
- Below the diagonal: Scrum.Story.Infrastructure.StoryRepository uses a module listed above it, which is the healthy direction.
40→25 Scrum.Story.Infrastructure.StoryRepository uses Scrum.Story.Domain.StoryAggregate✕
- Connections
- 3 pairs of types, where a type in Scrum.Story.Infrastructure.StoryRepository uses a type in Scrum.Story.Domain.StoryAggregate.
- The types involved
Scrum.Story.Infrastructure.StoryRepository.StoryRepository→Scrum.Story.Domain.StoryAggregate.StoryScrum.Story.Infrastructure.StoryRepository.StoryRepository→Scrum.Story.Domain.StoryAggregate.StoryEventScrum.Story.Infrastructure.StoryRepository.StoryRepository→Scrum.Story.Domain.StoryAggregate.StoryId
- Direction
- Scrum.Story.Infrastructure.StoryRepository uses Scrum.Story.Domain.StoryAggregate, so a change to Scrum.Story.Domain.StoryAggregate can break Scrum.Story.Infrastructure.StoryRepository, while a change to Scrum.Story.Infrastructure.StoryRepository can't break Scrum.Story.Domain.StoryAggregate.
- Position
- Below the diagonal: Scrum.Story.Infrastructure.StoryRepository 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 | 6 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | Medium |
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED; Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2); Resolve the 2 Vulnerable finding(s) in Dependency Hygiene.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. | +22.8 pts | Low | REDACTED Scanning |
| Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). | +9.2 pts | Low | Dependency Hygiene |
| Resolve the 2 Vulnerable finding(s) in Dependency Hygiene. | +9.2 pts | Low | Dependency Hygiene |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +7.2 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. | +2.2 pts | Medium | Deployment & Rollback |
| 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.8 pts | Medium | Documentation (README) |
| Grow the ADR log (currently 11) — reach 20 to raise the maturity tier; document significant decisions as they're made. | +1.0 pts | Medium | Architecture documentation |
| 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 |
| REDACTED | 4.6 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| src/Scrum/Story.fs | 6.5 | 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 | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.9 | Near-clean | Dependency Vulnerabilities: Medium CVE: 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
Watchdog 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. 43 of 43 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 43 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, 34 of 48 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- 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 399 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.
- D21 Naming Consistency — not measured this run — Watchdog 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. 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 — Watchdog 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AX1 Captive dependencies — not measured this run — Watchdog 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.
- AX6 Interface segregation — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog measured this, but not all of it. What it 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 — Watchdog measured this, but not all of it. What it 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
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).
- Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
15 duplicated block group(s) detected.
What to do
- 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 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with Seedwork.fs, Story.fs. — 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).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
9 outdated, 2 vulnerable, 2 deprecated packages.
What to do
- Resolve the 2 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
3 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Stand up a CI pipeline, then gate REDACTED Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 150 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 13 direct `PackageReference`(s), and 137 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D26 · Project Cohesion
0 of 1 build units (MSBuild) flagged as possibly oversized/incoherent.
D27 · Navigability
97 % of calls cross a namespace and 2 % go through an interface, but 88 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
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.
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
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.
D39 · IL Efficiency
2 of 340 first-party methods have an oversized IL body.
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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
DM1 · Aggregate boundaries
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
What to do
- Grow the ADR log (currently 11) — reach 20 to raise the maturity tier; document significant decisions as they're made.
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.
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED: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
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 91% | Exemplary | Solid. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 86% | Exemplary | Solid. |
| Readiness | 32% | Weak — gated by D13, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 95% | Exemplary | Solid. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| 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 — 83 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- 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
- 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.
- 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.
- 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.
- 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 — Naming consistency is measured on C# and TypeScript only; F#, JavaScript not measured.
- 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. Aggregate roots were found in only one source directory (Scrum), which is a layered codebase, not two contexts. 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# and Visual Basic comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 8 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (5 with fewer than two methods, 3 stateless), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- D9 Test Distribution — Test source is 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- 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 only 1 of the 3 signals this lens looks for (1 aggregate(s) with Apply/When folds)
- 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 — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — 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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's F# code has 2,531 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- 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
- 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.
- 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 — 7 finding(s)
- REDACTED
- REDACTED
- REDACTED
- Vulnerable: OpenTelemetry.Exporter.Jaeger
- Vulnerable: OpenTelemetry.Exporter.OpenTelemetryProtocol
- REDACTED
- REDACTED
Serious — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- Deprecated: OpenTelemetry.Exporter.Jaeger REDACTED:11
- Deprecated: xunit REDACTED:18
- FileTooLong: Scrum/Story.fs src/Scrum/Story.fs
- FileTooLong: Scrum/Seedwork.fs src/Scrum/Seedwork.fs
- Duplicated block (11 lines × 2) src/Scrum/Story.fs:340
- Duplicated block (11 lines × 2) src/Scrum/Story.fs:987
- Duplicated block (10 lines × 2) src/Scrum/Seedwork.fs:815
- Duplicated block (10 lines × 2) src/Scrum/Story.fs:397
- 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 (12 lines × 2) src/Scrum/Story.fs:1078
- Duplicated block (11 lines × 3) src/Scrum/Story.fs:1111
- 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 — 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- IL efficiency: 2 authored method(s) exceed the IL budget src/Scrum/Story.fs:395
- No SAST
- No dependency-update automation REDACTED:7
Minor — 9 finding(s)
- Outdated: Giraffe
- Outdated: Microsoft.AspNetCore.Authentication.JwtBearer
- Outdated: OpenTelemetry.Exporter.Console
- Outdated: OpenTelemetry.Exporter.OpenTelemetryProtocol
- Outdated: OpenTelemetry.Extensions.Hosting
- Outdated: OpenTelemetry.Instrumentation.AspNetCore
- Outdated: System.Data.SQLite.Core
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: xunit.runner.visualstudio
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4b97f55b56e4422fba6c8ce455519d45/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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4b97f55b56e4422fba6c8ce455519d45/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/watchdog-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 | dotnet | — | dotnet list Scrum.sln package --vulnerable --include-transitive --format json | 3 | artifacts/raw/dotnet-vulnerable.json |
| 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 | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |