Executive summary
goodtocode/semantickernel-microservice is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 50 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 46, is the weakest lens, level with Maturity, and counts most in the score. The best first step is recording design decisions, worth about 4 points. Documenting the recovery plan would lift Production Readiness itself, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 53.
Twenty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen secrets can leak from the build pipeline, and four known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. The two passwords or keys in the code need replacing, with the old ones switched off. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The analysis rule switched off in the settings needs switching back on in the settings file.
The product code is 5,641 lines, about €21,000 to rebuild.
If Production Readiness rose from 46 to 70, the lowest score rated Strong, the score would rise from 50 to about 53.
Fixed since the last survey: 2 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Cancellation propagation · Async method without CancellationToken: SyncUserAsync src/Presentation.Blazor/Services/UserSyncService.cs
Rebuild cost: about €21,000 · Estimate
| Cost to rebuild | €6,800 to €34,000, for 114 to 360 hours of work, about 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.7 at a score of 50. 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: 5,641 lines of product code, of which 44% is declarations and boilerplate, 40% straight logic and 15% logic with branches |
| Comment lines | The estimate prices 5,282 lines. Comment lines count towards the size of 5,641 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 Goodtocode.SemanticKernel.Core.Application | 3 Goodtocode.SemanticKernel.Core.Application.Common | 4 Goodtocode.SemanticKernel.Core.Application.Common.Behaviors | 5 Goodtocode.SemanticKernel.Core.Application.Common.Exceptions | 6 Goodtocode.SemanticKernel.Core.Application.Common.Models | 7 Goodtocode.SemanticKernel.Core.Domain.Auth | 8 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel | 9 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.AiModels | 10 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Options | 11 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Services | 12 Goodtocode.SemanticKernel.Infrastructure.SqlServer | 13 Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth | 14 Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.Services | 15 Goodtocode.SemanticKernel.Presentation.Blazor.Options | 16 Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models | 17 Goodtocode.SemanticKernel.Core.Application.Common.Mappings | 18 Goodtocode.SemanticKernel.Core.Domain.Actor | 19 Goodtocode.SemanticKernel.Presentation.Blazor | 20 Goodtocode.SemanticKernel.Presentation.Blazor.Services | 21 Goodtocode.SemanticKernel.Presentation.WebApi.Common | 22 Goodtocode.SemanticKernel.Core.Domain.Audio | 23 Goodtocode.SemanticKernel.Core.Domain.ChatCompletion | 24 Goodtocode.SemanticKernel.Core.Domain.Image | 25 Goodtocode.SemanticKernel.Core.Domain.TextGeneration | 26 Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services | 27 Goodtocode.SemanticKernel.Core.Application.Abstractions | 28 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations | 29 Goodtocode.SemanticKernel.Core.Application.Audio | 30 Goodtocode.SemanticKernel.Core.Application.ChatCompletion | 31 Goodtocode.SemanticKernel.Core.Application.Image | 32 Goodtocode.SemanticKernel.Core.Application.TextGeneration | 33 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins | 34 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence | 35 Goodtocode.SemanticKernel.Core.Application.Actor | 36 Goodtocode.SemanticKernel.Presentation.WebApi.Audio | 37 Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion | 38 Goodtocode.SemanticKernel.Presentation.WebApi.Image | 39 Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration | 40 Goodtocode.SemanticKernel.Presentation.WebApi.Actor |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 Goodtocode.SemanticKernel.Core.Application | ||||||||||||||||||||||||||||||||||||||||
| 3 Goodtocode.SemanticKernel.Core.Application.Common | ||||||||||||||||||||||||||||||||||||||||
| 4 Goodtocode.SemanticKernel.Core.Application.Common.Behaviors | ||||||||||||||||||||||||||||||||||||||||
| 5 Goodtocode.SemanticKernel.Core.Application.Common.Exceptions | ||||||||||||||||||||||||||||||||||||||||
| 6 Goodtocode.SemanticKernel.Core.Application.Common.Models | ||||||||||||||||||||||||||||||||||||||||
| 7 Goodtocode.SemanticKernel.Core.Domain.Auth | ||||||||||||||||||||||||||||||||||||||||
| 8 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel | ||||||||||||||||||||||||||||||||||||||||
| 9 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.AiModels | ||||||||||||||||||||||||||||||||||||||||
| 10 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Options | ||||||||||||||||||||||||||||||||||||||||
| 11 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Services | ||||||||||||||||||||||||||||||||||||||||
| 12 Goodtocode.SemanticKernel.Infrastructure.SqlServer | ||||||||||||||||||||||||||||||||||||||||
| 13 Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth | ||||||||||||||||||||||||||||||||||||||||
| 14 Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.Services | ||||||||||||||||||||||||||||||||||||||||
| 15 Goodtocode.SemanticKernel.Presentation.Blazor.Options | ||||||||||||||||||||||||||||||||||||||||
| 16 Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models | ||||||||||||||||||||||||||||||||||||||||
| 17 Goodtocode.SemanticKernel.Core.Application.Common.Mappings | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Goodtocode.SemanticKernel.Core.Domain.Actor | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Goodtocode.SemanticKernel.Presentation.Blazor | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 Goodtocode.SemanticKernel.Presentation.Blazor.Services | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 Goodtocode.SemanticKernel.Presentation.WebApi.Common | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Goodtocode.SemanticKernel.Core.Domain.Audio | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Goodtocode.SemanticKernel.Core.Domain.ChatCompletion | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Goodtocode.SemanticKernel.Core.Domain.Image | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 Goodtocode.SemanticKernel.Core.Domain.TextGeneration | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 Goodtocode.SemanticKernel.Core.Application.Abstractions | 1 | 1 | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 28 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations | 1 | 1 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 29 Goodtocode.SemanticKernel.Core.Application.Audio | 1 | 4 | 5 | |||||||||||||||||||||||||||||||||||||
| 30 Goodtocode.SemanticKernel.Core.Application.ChatCompletion | 3 | 5 | 1 | 11 | 1 | 19 | ||||||||||||||||||||||||||||||||||
| 31 Goodtocode.SemanticKernel.Core.Application.Image | 1 | 3 | 4 | |||||||||||||||||||||||||||||||||||||
| 32 Goodtocode.SemanticKernel.Core.Application.TextGeneration | 1 | 5 | 5 | |||||||||||||||||||||||||||||||||||||
| 33 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins | 5 | |||||||||||||||||||||||||||||||||||||||
| 34 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence | 1 | 1 | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 35 Goodtocode.SemanticKernel.Core.Application.Actor | 1 | 2 | 7 | 1 | 12 | 3 | ||||||||||||||||||||||||||||||||||
| 36 Goodtocode.SemanticKernel.Presentation.WebApi.Audio | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 37 Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion | 3 | 3 | 9 | |||||||||||||||||||||||||||||||||||||
| 38 Goodtocode.SemanticKernel.Presentation.WebApi.Image | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 39 Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 40 Goodtocode.SemanticKernel.Presentation.WebApi.Actor | 1 | 2 |
17→6 Goodtocode.SemanticKernel.Core.Application.Common.Mappings uses Goodtocode.SemanticKernel.Core.Application.Common.Models✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.Common.Mappings uses a type in Goodtocode.SemanticKernel.Core.Application.Common.Models.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Common.Mappings.MappingExtensions→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedList
- Direction
- Goodtocode.SemanticKernel.Core.Application.Common.Mappings uses Goodtocode.SemanticKernel.Core.Application.Common.Models, so a change to Goodtocode.SemanticKernel.Core.Application.Common.Models can break Goodtocode.SemanticKernel.Core.Application.Common.Mappings, while a change to Goodtocode.SemanticKernel.Core.Application.Common.Mappings can't break Goodtocode.SemanticKernel.Core.Application.Common.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Common.Mappings uses a module listed above it, which is the healthy direction.
18→7 Goodtocode.SemanticKernel.Core.Domain.Actor uses Goodtocode.SemanticKernel.Core.Domain.Auth✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Domain.Actor uses a type in Goodtocode.SemanticKernel.Core.Domain.Auth.
- The types involved
Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntity→Goodtocode.SemanticKernel.Core.Domain.Auth.IUserEntity
- Direction
- Goodtocode.SemanticKernel.Core.Domain.Actor uses Goodtocode.SemanticKernel.Core.Domain.Auth, so a change to Goodtocode.SemanticKernel.Core.Domain.Auth can break Goodtocode.SemanticKernel.Core.Domain.Actor, while a change to Goodtocode.SemanticKernel.Core.Domain.Actor can't break Goodtocode.SemanticKernel.Core.Domain.Auth.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Domain.Actor uses a module listed above it, which is the healthy direction.
19→15 Goodtocode.SemanticKernel.Presentation.Blazor uses Goodtocode.SemanticKernel.Presentation.Blazor.Options✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.Blazor uses a type in Goodtocode.SemanticKernel.Presentation.Blazor.Options.
- The types involved
Goodtocode.SemanticKernel.Presentation.Blazor.ConfigureServicesAuth→Goodtocode.SemanticKernel.Presentation.Blazor.Options.ResilientHttpClientOptions
- Direction
- Goodtocode.SemanticKernel.Presentation.Blazor uses Goodtocode.SemanticKernel.Presentation.Blazor.Options, so a change to Goodtocode.SemanticKernel.Presentation.Blazor.Options can break Goodtocode.SemanticKernel.Presentation.Blazor, while a change to Goodtocode.SemanticKernel.Presentation.Blazor can't break Goodtocode.SemanticKernel.Presentation.Blazor.Options.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.Blazor uses a module listed above it, which is the healthy direction.
20→13 Goodtocode.SemanticKernel.Presentation.Blazor.Services uses Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.Blazor.Services uses a type in Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.
- The types involved
Goodtocode.SemanticKernel.Presentation.Blazor.Services.UserSyncService→Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.IUserClaimsInfo
- Direction
- Goodtocode.SemanticKernel.Presentation.Blazor.Services uses Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth, so a change to Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth can break Goodtocode.SemanticKernel.Presentation.Blazor.Services, while a change to Goodtocode.SemanticKernel.Presentation.Blazor.Services can't break Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.Blazor.Services uses a module listed above it, which is the healthy direction.
20→14 Goodtocode.SemanticKernel.Presentation.Blazor.Services uses Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.Services✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.Blazor.Services uses a type in Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.Services.
- The types involved
Goodtocode.SemanticKernel.Presentation.Blazor.Services.UserSyncService→Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.Services.IUserSyncService
- Direction
- Goodtocode.SemanticKernel.Presentation.Blazor.Services uses Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.Services, so a change to Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.Services can break Goodtocode.SemanticKernel.Presentation.Blazor.Services, while a change to Goodtocode.SemanticKernel.Presentation.Blazor.Services can't break Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.Services.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.Blazor.Services uses a module listed above it, which is the healthy direction.
21→7 Goodtocode.SemanticKernel.Presentation.WebApi.Common uses Goodtocode.SemanticKernel.Core.Domain.Auth✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.Common uses a type in Goodtocode.SemanticKernel.Core.Domain.Auth.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.Common.ApiControllerBase→Goodtocode.SemanticKernel.Core.Domain.Auth.IUserEntity
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.Common uses Goodtocode.SemanticKernel.Core.Domain.Auth, so a change to Goodtocode.SemanticKernel.Core.Domain.Auth can break Goodtocode.SemanticKernel.Presentation.WebApi.Common, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.Common can't break Goodtocode.SemanticKernel.Core.Domain.Auth.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.Common uses a module listed above it, which is the healthy direction.
22→18 Goodtocode.SemanticKernel.Core.Domain.Audio uses Goodtocode.SemanticKernel.Core.Domain.Actor✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Domain.Audio uses a type in Goodtocode.SemanticKernel.Core.Domain.Actor.
- The types involved
Goodtocode.SemanticKernel.Core.Domain.Audio.TextAudioEntity→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntity
- Direction
- Goodtocode.SemanticKernel.Core.Domain.Audio uses Goodtocode.SemanticKernel.Core.Domain.Actor, so a change to Goodtocode.SemanticKernel.Core.Domain.Actor can break Goodtocode.SemanticKernel.Core.Domain.Audio, while a change to Goodtocode.SemanticKernel.Core.Domain.Audio can't break Goodtocode.SemanticKernel.Core.Domain.Actor.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Domain.Audio uses a module listed above it, which is the healthy direction.
23→18 Goodtocode.SemanticKernel.Core.Domain.ChatCompletion uses Goodtocode.SemanticKernel.Core.Domain.Actor✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Domain.ChatCompletion uses a type in Goodtocode.SemanticKernel.Core.Domain.Actor.
- The types involved
Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntity→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntity
- Direction
- Goodtocode.SemanticKernel.Core.Domain.ChatCompletion uses Goodtocode.SemanticKernel.Core.Domain.Actor, so a change to Goodtocode.SemanticKernel.Core.Domain.Actor can break Goodtocode.SemanticKernel.Core.Domain.ChatCompletion, while a change to Goodtocode.SemanticKernel.Core.Domain.ChatCompletion can't break Goodtocode.SemanticKernel.Core.Domain.Actor.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Domain.ChatCompletion uses a module listed above it, which is the healthy direction.
24→18 Goodtocode.SemanticKernel.Core.Domain.Image uses Goodtocode.SemanticKernel.Core.Domain.Actor✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Domain.Image uses a type in Goodtocode.SemanticKernel.Core.Domain.Actor.
- The types involved
Goodtocode.SemanticKernel.Core.Domain.Image.TextImageEntity→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntity
- Direction
- Goodtocode.SemanticKernel.Core.Domain.Image uses Goodtocode.SemanticKernel.Core.Domain.Actor, so a change to Goodtocode.SemanticKernel.Core.Domain.Actor can break Goodtocode.SemanticKernel.Core.Domain.Image, while a change to Goodtocode.SemanticKernel.Core.Domain.Image can't break Goodtocode.SemanticKernel.Core.Domain.Actor.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Domain.Image uses a module listed above it, which is the healthy direction.
25→18 Goodtocode.SemanticKernel.Core.Domain.TextGeneration uses Goodtocode.SemanticKernel.Core.Domain.Actor✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Domain.TextGeneration uses a type in Goodtocode.SemanticKernel.Core.Domain.Actor.
- The types involved
Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextPromptEntity→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntity
- Direction
- Goodtocode.SemanticKernel.Core.Domain.TextGeneration uses Goodtocode.SemanticKernel.Core.Domain.Actor, so a change to Goodtocode.SemanticKernel.Core.Domain.Actor can break Goodtocode.SemanticKernel.Core.Domain.TextGeneration, while a change to Goodtocode.SemanticKernel.Core.Domain.TextGeneration can't break Goodtocode.SemanticKernel.Core.Domain.Actor.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Domain.TextGeneration uses a module listed above it, which is the healthy direction.
26→13 Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses a type in Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.
- The types involved
Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services.ChatService→Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.IUserClaimsInfo
- Direction
- Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth, so a change to Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth can break Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services, while a change to Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services can't break Goodtocode.SemanticKernel.Presentation.Blazor.Components.Auth.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses a module listed above it, which is the healthy direction.
26→16 Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models✕
- Connections
- 4 pairs of types, where a type in Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses a type in Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models.
- The types involved
Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services.ChatService→Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models.ChatMessageModelGoodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services.ChatService→Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models.ChatSessionModelGoodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services.IChatService→Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models.ChatMessageModelGoodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services.IChatService→Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models.ChatSessionModel
- Direction
- Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models, so a change to Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models can break Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services, while a change to Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services can't break Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses a module listed above it, which is the healthy direction.
26→20 Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses Goodtocode.SemanticKernel.Presentation.Blazor.Services✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses a type in Goodtocode.SemanticKernel.Presentation.Blazor.Services.
- The types involved
Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services.ChatService→Goodtocode.SemanticKernel.Presentation.Blazor.Services.ApiService
- Direction
- Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses Goodtocode.SemanticKernel.Presentation.Blazor.Services, so a change to Goodtocode.SemanticKernel.Presentation.Blazor.Services can break Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services, while a change to Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services can't break Goodtocode.SemanticKernel.Presentation.Blazor.Services.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.Blazor.Pages.Chat.Services uses a module listed above it, which is the healthy direction.
27→7 Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.Auth✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.Abstractions uses a type in Goodtocode.SemanticKernel.Core.Domain.Auth.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Abstractions.IUserInfoRequest→Goodtocode.SemanticKernel.Core.Domain.Auth.IUserEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.Auth, so a change to Goodtocode.SemanticKernel.Core.Domain.Auth can break Goodtocode.SemanticKernel.Core.Application.Abstractions, while a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can't break Goodtocode.SemanticKernel.Core.Domain.Auth.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Abstractions uses a module listed above it, which is the healthy direction.
27→18 Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.Actor✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.Abstractions uses a type in Goodtocode.SemanticKernel.Core.Domain.Actor.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.Actor, so a change to Goodtocode.SemanticKernel.Core.Domain.Actor can break Goodtocode.SemanticKernel.Core.Application.Abstractions, while a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can't break Goodtocode.SemanticKernel.Core.Domain.Actor.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Abstractions uses a module listed above it, which is the healthy direction.
27→22 Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.Audio✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.Abstractions uses a type in Goodtocode.SemanticKernel.Core.Domain.Audio.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.Audio.TextAudioEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.Audio, so a change to Goodtocode.SemanticKernel.Core.Domain.Audio can break Goodtocode.SemanticKernel.Core.Application.Abstractions, while a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can't break Goodtocode.SemanticKernel.Core.Domain.Audio.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Abstractions uses a module listed above it, which is the healthy direction.
27→23 Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.ChatCompletion✕
- Connections
- 2 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.Abstractions uses a type in Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatMessageEntityGoodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.ChatCompletion, so a change to Goodtocode.SemanticKernel.Core.Domain.ChatCompletion can break Goodtocode.SemanticKernel.Core.Application.Abstractions, while a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can't break Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Abstractions uses a module listed above it, which is the healthy direction.
27→24 Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.Image✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.Abstractions uses a type in Goodtocode.SemanticKernel.Core.Domain.Image.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.Image.TextImageEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.Image, so a change to Goodtocode.SemanticKernel.Core.Domain.Image can break Goodtocode.SemanticKernel.Core.Application.Abstractions, while a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can't break Goodtocode.SemanticKernel.Core.Domain.Image.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Abstractions uses a module listed above it, which is the healthy direction.
27→25 Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.TextGeneration✕
- Connections
- 2 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.Abstractions uses a type in Goodtocode.SemanticKernel.Core.Domain.TextGeneration.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextPromptEntityGoodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextResponseEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Abstractions uses Goodtocode.SemanticKernel.Core.Domain.TextGeneration, so a change to Goodtocode.SemanticKernel.Core.Domain.TextGeneration can break Goodtocode.SemanticKernel.Core.Application.Abstractions, while a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can't break Goodtocode.SemanticKernel.Core.Domain.TextGeneration.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Abstractions uses a module listed above it, which is the healthy direction.
28→18 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses Goodtocode.SemanticKernel.Core.Domain.Actor✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses a type in Goodtocode.SemanticKernel.Core.Domain.Actor.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations.ActorsConfig→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntity
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses Goodtocode.SemanticKernel.Core.Domain.Actor, so a change to Goodtocode.SemanticKernel.Core.Domain.Actor can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations can't break Goodtocode.SemanticKernel.Core.Domain.Actor.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses a module listed above it, which is the healthy direction.
28→22 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses Goodtocode.SemanticKernel.Core.Domain.Audio✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses a type in Goodtocode.SemanticKernel.Core.Domain.Audio.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations.TextAudioConfig→Goodtocode.SemanticKernel.Core.Domain.Audio.TextAudioEntity
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses Goodtocode.SemanticKernel.Core.Domain.Audio, so a change to Goodtocode.SemanticKernel.Core.Domain.Audio can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations can't break Goodtocode.SemanticKernel.Core.Domain.Audio.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses a module listed above it, which is the healthy direction.
28→23 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses Goodtocode.SemanticKernel.Core.Domain.ChatCompletion✕
- Connections
- 2 pairs of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses a type in Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations.ChatMessagesConfig→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatMessageEntityGoodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations.ChatSessionsConfig→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntity
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses Goodtocode.SemanticKernel.Core.Domain.ChatCompletion, so a change to Goodtocode.SemanticKernel.Core.Domain.ChatCompletion can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations can't break Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses a module listed above it, which is the healthy direction.
28→24 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses Goodtocode.SemanticKernel.Core.Domain.Image✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses a type in Goodtocode.SemanticKernel.Core.Domain.Image.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations.TextImagesConfig→Goodtocode.SemanticKernel.Core.Domain.Image.TextImageEntity
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses Goodtocode.SemanticKernel.Core.Domain.Image, so a change to Goodtocode.SemanticKernel.Core.Domain.Image can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations can't break Goodtocode.SemanticKernel.Core.Domain.Image.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses a module listed above it, which is the healthy direction.
28→25 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses Goodtocode.SemanticKernel.Core.Domain.TextGeneration✕
- Connections
- 2 pairs of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses a type in Goodtocode.SemanticKernel.Core.Domain.TextGeneration.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations.TextPromptsConfig→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextPromptEntityGoodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations.TextResponsesConfig→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextResponseEntity
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses Goodtocode.SemanticKernel.Core.Domain.TextGeneration, so a change to Goodtocode.SemanticKernel.Core.Domain.TextGeneration can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations can't break Goodtocode.SemanticKernel.Core.Domain.TextGeneration.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.Configurations uses a module listed above it, which is the healthy direction.
29→6 Goodtocode.SemanticKernel.Core.Application.Audio uses Goodtocode.SemanticKernel.Core.Application.Common.Models✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.Audio uses a type in Goodtocode.SemanticKernel.Core.Application.Common.Models.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Audio.GetTextAudioPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedList
- Direction
- Goodtocode.SemanticKernel.Core.Application.Audio uses Goodtocode.SemanticKernel.Core.Application.Common.Models, so a change to Goodtocode.SemanticKernel.Core.Application.Common.Models can break Goodtocode.SemanticKernel.Core.Application.Audio, while a change to Goodtocode.SemanticKernel.Core.Application.Audio can't break Goodtocode.SemanticKernel.Core.Application.Common.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Audio uses a module listed above it, which is the healthy direction.
29→22 Goodtocode.SemanticKernel.Core.Application.Audio uses Goodtocode.SemanticKernel.Core.Domain.Audio✕
- Connections
- 4 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.Audio uses a type in Goodtocode.SemanticKernel.Core.Domain.Audio.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Audio.CreateTextToAudioCommandHandler→Goodtocode.SemanticKernel.Core.Domain.Audio.TextAudioEntityGoodtocode.SemanticKernel.Core.Application.Audio.DeleteTextAudioCommandHandler→Goodtocode.SemanticKernel.Core.Domain.Audio.TextAudioEntityGoodtocode.SemanticKernel.Core.Application.Audio.GetTextAudioQueryHandler→Goodtocode.SemanticKernel.Core.Domain.Audio.TextAudioEntityGoodtocode.SemanticKernel.Core.Application.Audio.TextAudioDto→Goodtocode.SemanticKernel.Core.Domain.Audio.TextAudioEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Audio uses Goodtocode.SemanticKernel.Core.Domain.Audio, so a change to Goodtocode.SemanticKernel.Core.Domain.Audio can break Goodtocode.SemanticKernel.Core.Application.Audio, while a change to Goodtocode.SemanticKernel.Core.Application.Audio can't break Goodtocode.SemanticKernel.Core.Domain.Audio.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Audio uses a module listed above it, which is the healthy direction.
29→27 Goodtocode.SemanticKernel.Core.Application.Audio uses Goodtocode.SemanticKernel.Core.Application.Abstractions✕
- Connections
- 5 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.Audio uses a type in Goodtocode.SemanticKernel.Core.Application.Abstractions.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Audio.CreateTextToAudioCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Audio.DeleteTextAudioCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Audio.GetTextAudioPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Audio.GetTextAudioQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Audio.GetTextAudiosQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext
- Direction
- Goodtocode.SemanticKernel.Core.Application.Audio uses Goodtocode.SemanticKernel.Core.Application.Abstractions, so a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can break Goodtocode.SemanticKernel.Core.Application.Audio, while a change to Goodtocode.SemanticKernel.Core.Application.Audio can't break Goodtocode.SemanticKernel.Core.Application.Abstractions.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Audio uses a module listed above it, which is the healthy direction.
30→6 Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Application.Common.Models✕
- Connections
- 3 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a type in Goodtocode.SemanticKernel.Core.Application.Common.Models.
- The types involved
Goodtocode.SemanticKernel.Core.Application.ChatCompletion.GetAuthorChatSessionsByExternalIdPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedListGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatMessagesPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedListGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatSessionsPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedList
- Direction
- Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Application.Common.Models, so a change to Goodtocode.SemanticKernel.Core.Application.Common.Models can break Goodtocode.SemanticKernel.Core.Application.ChatCompletion, while a change to Goodtocode.SemanticKernel.Core.Application.ChatCompletion can't break Goodtocode.SemanticKernel.Core.Application.Common.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a module listed above it, which is the healthy direction.
30→7 Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Domain.Auth✕
- Connections
- 5 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a type in Goodtocode.SemanticKernel.Core.Domain.Auth.
- The types involved
Goodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatMessageCommand→Goodtocode.SemanticKernel.Core.Domain.Auth.IUserEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatMessageCommandHandler→Goodtocode.SemanticKernel.Core.Domain.Auth.IUserEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetMyChatSessionQuery→Goodtocode.SemanticKernel.Core.Domain.Auth.IUserEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetMyChatSessionsPaginatedQuery→Goodtocode.SemanticKernel.Core.Domain.Auth.IUserEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetMyChatSessionsQuery→Goodtocode.SemanticKernel.Core.Domain.Auth.IUserEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Domain.Auth, so a change to Goodtocode.SemanticKernel.Core.Domain.Auth can break Goodtocode.SemanticKernel.Core.Application.ChatCompletion, while a change to Goodtocode.SemanticKernel.Core.Application.ChatCompletion can't break Goodtocode.SemanticKernel.Core.Domain.Auth.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a module listed above it, which is the healthy direction.
30→18 Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Domain.Actor✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a type in Goodtocode.SemanticKernel.Core.Domain.Actor.
- The types involved
Goodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatSessionCommandHandler→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Domain.Actor, so a change to Goodtocode.SemanticKernel.Core.Domain.Actor can break Goodtocode.SemanticKernel.Core.Application.ChatCompletion, while a change to Goodtocode.SemanticKernel.Core.Application.ChatCompletion can't break Goodtocode.SemanticKernel.Core.Domain.Actor.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a module listed above it, which is the healthy direction.
30→23 Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Domain.ChatCompletion✕
- Connections
- 11 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a type in Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.
- The types involved
Goodtocode.SemanticKernel.Core.Application.ChatCompletion.ChatMessageDto→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatMessageEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.ChatSessionDto→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatMessageCommandHandler→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatMessageEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatMessageCommandHandler→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatSessionCommandHandler→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.DeleteChatSessionCommandHandler→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetAuthorChatSessionByOwnerIdQueryHandler→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatMessageQueryHandler→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatMessageEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatSessionQueryHandler→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.PatchChatSessionCommandHandler→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntityGoodtocode.SemanticKernel.Core.Application.ChatCompletion.UpdateChatSessionCommandHandler→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Domain.ChatCompletion, so a change to Goodtocode.SemanticKernel.Core.Domain.ChatCompletion can break Goodtocode.SemanticKernel.Core.Application.ChatCompletion, while a change to Goodtocode.SemanticKernel.Core.Application.ChatCompletion can't break Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a module listed above it, which is the healthy direction.
30→24 Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Domain.Image✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a type in Goodtocode.SemanticKernel.Core.Domain.Image.
- The types involved
Goodtocode.SemanticKernel.Core.Application.ChatCompletion.DeleteTextImageCommandHandler→Goodtocode.SemanticKernel.Core.Domain.Image.TextImageEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Domain.Image, so a change to Goodtocode.SemanticKernel.Core.Domain.Image can break Goodtocode.SemanticKernel.Core.Application.ChatCompletion, while a change to Goodtocode.SemanticKernel.Core.Application.ChatCompletion can't break Goodtocode.SemanticKernel.Core.Domain.Image.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a module listed above it, which is the healthy direction.
30→27 Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Application.Abstractions✕
- Connections
- 19 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a type in Goodtocode.SemanticKernel.Core.Application.Abstractions.
- The types involved
Goodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatMessageCommand→Goodtocode.SemanticKernel.Core.Application.Abstractions.IUserInfoRequestGoodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatMessageCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatSessionCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.DeleteChatSessionCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.DeleteTextImageCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetAuthorChatSessionByOwnerIdQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetAuthorChatSessionsByExternalIdPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetAuthorChatSessionsByOwnerIdQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatMessageQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatMessagesPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatMessagesQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatSessionQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatSessionsPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatSessionsQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetMyChatSessionQuery→Goodtocode.SemanticKernel.Core.Application.Abstractions.IUserInfoRequestGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetMyChatSessionsPaginatedQuery→Goodtocode.SemanticKernel.Core.Application.Abstractions.IUserInfoRequestGoodtocode.SemanticKernel.Core.Application.ChatCompletion.GetMyChatSessionsQuery→Goodtocode.SemanticKernel.Core.Application.Abstractions.IUserInfoRequestGoodtocode.SemanticKernel.Core.Application.ChatCompletion.PatchChatSessionCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.ChatCompletion.UpdateChatSessionCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext
- Direction
- Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses Goodtocode.SemanticKernel.Core.Application.Abstractions, so a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can break Goodtocode.SemanticKernel.Core.Application.ChatCompletion, while a change to Goodtocode.SemanticKernel.Core.Application.ChatCompletion can't break Goodtocode.SemanticKernel.Core.Application.Abstractions.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.ChatCompletion uses a module listed above it, which is the healthy direction.
31→6 Goodtocode.SemanticKernel.Core.Application.Image uses Goodtocode.SemanticKernel.Core.Application.Common.Models✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.Image uses a type in Goodtocode.SemanticKernel.Core.Application.Common.Models.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Image.GetTextImagesPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedList
- Direction
- Goodtocode.SemanticKernel.Core.Application.Image uses Goodtocode.SemanticKernel.Core.Application.Common.Models, so a change to Goodtocode.SemanticKernel.Core.Application.Common.Models can break Goodtocode.SemanticKernel.Core.Application.Image, while a change to Goodtocode.SemanticKernel.Core.Application.Image can't break Goodtocode.SemanticKernel.Core.Application.Common.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Image uses a module listed above it, which is the healthy direction.
31→24 Goodtocode.SemanticKernel.Core.Application.Image uses Goodtocode.SemanticKernel.Core.Domain.Image✕
- Connections
- 3 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.Image uses a type in Goodtocode.SemanticKernel.Core.Domain.Image.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Image.CreateTextToImageCommandHandler→Goodtocode.SemanticKernel.Core.Domain.Image.TextImageEntityGoodtocode.SemanticKernel.Core.Application.Image.GetTextImageQueryHandler→Goodtocode.SemanticKernel.Core.Domain.Image.TextImageEntityGoodtocode.SemanticKernel.Core.Application.Image.TextImageDto→Goodtocode.SemanticKernel.Core.Domain.Image.TextImageEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Image uses Goodtocode.SemanticKernel.Core.Domain.Image, so a change to Goodtocode.SemanticKernel.Core.Domain.Image can break Goodtocode.SemanticKernel.Core.Application.Image, while a change to Goodtocode.SemanticKernel.Core.Application.Image can't break Goodtocode.SemanticKernel.Core.Domain.Image.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Image uses a module listed above it, which is the healthy direction.
31→27 Goodtocode.SemanticKernel.Core.Application.Image uses Goodtocode.SemanticKernel.Core.Application.Abstractions✕
- Connections
- 4 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.Image uses a type in Goodtocode.SemanticKernel.Core.Application.Abstractions.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Image.CreateTextToImageCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Image.GetTextImageQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Image.GetTextImagesPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Image.GetTextImagesQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext
- Direction
- Goodtocode.SemanticKernel.Core.Application.Image uses Goodtocode.SemanticKernel.Core.Application.Abstractions, so a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can break Goodtocode.SemanticKernel.Core.Application.Image, while a change to Goodtocode.SemanticKernel.Core.Application.Image can't break Goodtocode.SemanticKernel.Core.Application.Abstractions.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Image uses a module listed above it, which is the healthy direction.
32→6 Goodtocode.SemanticKernel.Core.Application.TextGeneration uses Goodtocode.SemanticKernel.Core.Application.Common.Models✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.TextGeneration uses a type in Goodtocode.SemanticKernel.Core.Application.Common.Models.
- The types involved
Goodtocode.SemanticKernel.Core.Application.TextGeneration.GetTextPromptsPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedList
- Direction
- Goodtocode.SemanticKernel.Core.Application.TextGeneration uses Goodtocode.SemanticKernel.Core.Application.Common.Models, so a change to Goodtocode.SemanticKernel.Core.Application.Common.Models can break Goodtocode.SemanticKernel.Core.Application.TextGeneration, while a change to Goodtocode.SemanticKernel.Core.Application.TextGeneration can't break Goodtocode.SemanticKernel.Core.Application.Common.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.TextGeneration uses a module listed above it, which is the healthy direction.
32→25 Goodtocode.SemanticKernel.Core.Application.TextGeneration uses Goodtocode.SemanticKernel.Core.Domain.TextGeneration✕
- Connections
- 5 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.TextGeneration uses a type in Goodtocode.SemanticKernel.Core.Domain.TextGeneration.
- The types involved
Goodtocode.SemanticKernel.Core.Application.TextGeneration.CreateTextPromptCommandHandler→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextPromptEntityGoodtocode.SemanticKernel.Core.Application.TextGeneration.DeleteTextPromptCommandHandler→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextPromptEntityGoodtocode.SemanticKernel.Core.Application.TextGeneration.GetTextPromptQueryHandler→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextPromptEntityGoodtocode.SemanticKernel.Core.Application.TextGeneration.TextPromptDto→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextPromptEntityGoodtocode.SemanticKernel.Core.Application.TextGeneration.TextResponseDto→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextResponseEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.TextGeneration uses Goodtocode.SemanticKernel.Core.Domain.TextGeneration, so a change to Goodtocode.SemanticKernel.Core.Domain.TextGeneration can break Goodtocode.SemanticKernel.Core.Application.TextGeneration, while a change to Goodtocode.SemanticKernel.Core.Application.TextGeneration can't break Goodtocode.SemanticKernel.Core.Domain.TextGeneration.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.TextGeneration uses a module listed above it, which is the healthy direction.
32→27 Goodtocode.SemanticKernel.Core.Application.TextGeneration uses Goodtocode.SemanticKernel.Core.Application.Abstractions✕
- Connections
- 5 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.TextGeneration uses a type in Goodtocode.SemanticKernel.Core.Application.Abstractions.
- The types involved
Goodtocode.SemanticKernel.Core.Application.TextGeneration.CreateTextPromptCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.TextGeneration.DeleteTextPromptCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.TextGeneration.GetTextPromptQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.TextGeneration.GetTextPromptsPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.TextGeneration.GetTextPromptsQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext
- Direction
- Goodtocode.SemanticKernel.Core.Application.TextGeneration uses Goodtocode.SemanticKernel.Core.Application.Abstractions, so a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can break Goodtocode.SemanticKernel.Core.Application.TextGeneration, while a change to Goodtocode.SemanticKernel.Core.Application.TextGeneration can't break Goodtocode.SemanticKernel.Core.Application.Abstractions.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.TextGeneration uses a module listed above it, which is the healthy direction.
33→27 Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins uses Goodtocode.SemanticKernel.Core.Application.Abstractions✕
- Connections
- 5 pairs of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins uses a type in Goodtocode.SemanticKernel.Core.Application.Abstractions.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins.ActorResponse→Goodtocode.SemanticKernel.Core.Application.Abstractions.IActorResponseGoodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins.ActorsPlugin→Goodtocode.SemanticKernel.Core.Application.Abstractions.IActorResponseGoodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins.ActorsPlugin→Goodtocode.SemanticKernel.Core.Application.Abstractions.IActorsPluginGoodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins.ChatMessagesPlugin→Goodtocode.SemanticKernel.Core.Application.Abstractions.IChatMessagesPluginGoodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins.ChatSessionsPlugin→Goodtocode.SemanticKernel.Core.Application.Abstractions.IChatSessionsPlugin
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins uses Goodtocode.SemanticKernel.Core.Application.Abstractions, so a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can break Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins, while a change to Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins can't break Goodtocode.SemanticKernel.Core.Application.Abstractions.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SemanticKernel.Plugins uses a module listed above it, which is the healthy direction.
34→18 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Domain.Actor✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a type in Goodtocode.SemanticKernel.Core.Domain.Actor.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.SemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntity
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Domain.Actor, so a change to Goodtocode.SemanticKernel.Core.Domain.Actor can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence can't break Goodtocode.SemanticKernel.Core.Domain.Actor.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a module listed above it, which is the healthy direction.
34→22 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Domain.Audio✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a type in Goodtocode.SemanticKernel.Core.Domain.Audio.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.SemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.Audio.TextAudioEntity
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Domain.Audio, so a change to Goodtocode.SemanticKernel.Core.Domain.Audio can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence can't break Goodtocode.SemanticKernel.Core.Domain.Audio.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a module listed above it, which is the healthy direction.
34→23 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Domain.ChatCompletion✕
- Connections
- 2 pairs of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a type in Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.SemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatMessageEntityGoodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.SemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntity
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Domain.ChatCompletion, so a change to Goodtocode.SemanticKernel.Core.Domain.ChatCompletion can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence can't break Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a module listed above it, which is the healthy direction.
34→24 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Domain.Image✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a type in Goodtocode.SemanticKernel.Core.Domain.Image.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.SemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.Image.TextImageEntity
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Domain.Image, so a change to Goodtocode.SemanticKernel.Core.Domain.Image can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence can't break Goodtocode.SemanticKernel.Core.Domain.Image.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a module listed above it, which is the healthy direction.
34→25 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Domain.TextGeneration✕
- Connections
- 2 pairs of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a type in Goodtocode.SemanticKernel.Core.Domain.TextGeneration.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.SemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextPromptEntityGoodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.SemanticKernelContext→Goodtocode.SemanticKernel.Core.Domain.TextGeneration.TextResponseEntity
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Domain.TextGeneration, so a change to Goodtocode.SemanticKernel.Core.Domain.TextGeneration can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence can't break Goodtocode.SemanticKernel.Core.Domain.TextGeneration.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a module listed above it, which is the healthy direction.
34→27 Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Application.Abstractions✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a type in Goodtocode.SemanticKernel.Core.Application.Abstractions.
- The types involved
Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence.SemanticKernelContext→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext
- Direction
- Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses Goodtocode.SemanticKernel.Core.Application.Abstractions, so a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can break Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence, while a change to Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence can't break Goodtocode.SemanticKernel.Core.Application.Abstractions.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Infrastructure.SqlServer.Persistence uses a module listed above it, which is the healthy direction.
35→6 Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Application.Common.Models✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.Actor uses a type in Goodtocode.SemanticKernel.Core.Application.Common.Models.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Actor.GetAuthorChatSessionsPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedList
- Direction
- Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Application.Common.Models, so a change to Goodtocode.SemanticKernel.Core.Application.Common.Models can break Goodtocode.SemanticKernel.Core.Application.Actor, while a change to Goodtocode.SemanticKernel.Core.Application.Actor can't break Goodtocode.SemanticKernel.Core.Application.Common.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Actor uses a module listed above it, which is the healthy direction.
35→7 Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Domain.Auth✕
- Connections
- 2 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.Actor uses a type in Goodtocode.SemanticKernel.Core.Domain.Auth.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Actor.GetMyActorQuery→Goodtocode.SemanticKernel.Core.Domain.Auth.IUserEntityGoodtocode.SemanticKernel.Core.Application.Actor.SaveMyActorCommand→Goodtocode.SemanticKernel.Core.Domain.Auth.IUserEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Domain.Auth, so a change to Goodtocode.SemanticKernel.Core.Domain.Auth can break Goodtocode.SemanticKernel.Core.Application.Actor, while a change to Goodtocode.SemanticKernel.Core.Application.Actor can't break Goodtocode.SemanticKernel.Core.Domain.Auth.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Actor uses a module listed above it, which is the healthy direction.
35→18 Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Domain.Actor✕
- Connections
- 7 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.Actor uses a type in Goodtocode.SemanticKernel.Core.Domain.Actor.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Actor.ActorDto→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntityGoodtocode.SemanticKernel.Core.Application.Actor.CreateAuthorCommandHandler→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntityGoodtocode.SemanticKernel.Core.Application.Actor.DeleteAuthorByOwnerIdCommandHandler→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntityGoodtocode.SemanticKernel.Core.Application.Actor.DeleteAuthorCommandHandler→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntityGoodtocode.SemanticKernel.Core.Application.Actor.GetAuthorByOwnerIdQueryHandler→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntityGoodtocode.SemanticKernel.Core.Application.Actor.GetAuthorQueryHandler→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntityGoodtocode.SemanticKernel.Core.Application.Actor.UpdateAuthorCommandHandler→Goodtocode.SemanticKernel.Core.Domain.Actor.ActorEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Domain.Actor, so a change to Goodtocode.SemanticKernel.Core.Domain.Actor can break Goodtocode.SemanticKernel.Core.Application.Actor, while a change to Goodtocode.SemanticKernel.Core.Application.Actor can't break Goodtocode.SemanticKernel.Core.Domain.Actor.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Actor uses a module listed above it, which is the healthy direction.
35→23 Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Domain.ChatCompletion✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Core.Application.Actor uses a type in Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Actor.GetAuthorChatSessionQueryHandler→Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.ChatSessionEntity
- Direction
- Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Domain.ChatCompletion, so a change to Goodtocode.SemanticKernel.Core.Domain.ChatCompletion can break Goodtocode.SemanticKernel.Core.Application.Actor, while a change to Goodtocode.SemanticKernel.Core.Application.Actor can't break Goodtocode.SemanticKernel.Core.Domain.ChatCompletion.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Actor uses a module listed above it, which is the healthy direction.
35→27 Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Application.Abstractions✕
- Connections
- 12 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.Actor uses a type in Goodtocode.SemanticKernel.Core.Application.Abstractions.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Actor.CreateAuthorCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Actor.DeleteAuthorByOwnerIdCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Actor.DeleteAuthorCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Actor.GetAuthorByOwnerIdQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Actor.GetAuthorChatSessionQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Actor.GetAuthorChatSessionsPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Actor.GetAuthorChatSessionsQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Actor.GetAuthorQueryHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Actor.GetMyActorQuery→Goodtocode.SemanticKernel.Core.Application.Abstractions.IUserInfoRequestGoodtocode.SemanticKernel.Core.Application.Actor.SaveAuthorCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContextGoodtocode.SemanticKernel.Core.Application.Actor.SaveMyActorCommand→Goodtocode.SemanticKernel.Core.Application.Abstractions.IUserInfoRequestGoodtocode.SemanticKernel.Core.Application.Actor.UpdateAuthorCommandHandler→Goodtocode.SemanticKernel.Core.Application.Abstractions.ISemanticKernelContext
- Direction
- Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Application.Abstractions, so a change to Goodtocode.SemanticKernel.Core.Application.Abstractions can break Goodtocode.SemanticKernel.Core.Application.Actor, while a change to Goodtocode.SemanticKernel.Core.Application.Actor can't break Goodtocode.SemanticKernel.Core.Application.Abstractions.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Actor uses a module listed above it, which is the healthy direction.
35→30 Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Application.ChatCompletion✕
- Connections
- 3 pairs of types, where a type in Goodtocode.SemanticKernel.Core.Application.Actor uses a type in Goodtocode.SemanticKernel.Core.Application.ChatCompletion.
- The types involved
Goodtocode.SemanticKernel.Core.Application.Actor.GetAuthorChatSessionQueryHandler→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.ChatSessionDtoGoodtocode.SemanticKernel.Core.Application.Actor.GetAuthorChatSessionsPaginatedQueryHandler→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.ChatSessionDtoGoodtocode.SemanticKernel.Core.Application.Actor.GetAuthorChatSessionsQueryHandler→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.ChatSessionDto
- Direction
- Goodtocode.SemanticKernel.Core.Application.Actor uses Goodtocode.SemanticKernel.Core.Application.ChatCompletion, so a change to Goodtocode.SemanticKernel.Core.Application.ChatCompletion can break Goodtocode.SemanticKernel.Core.Application.Actor, while a change to Goodtocode.SemanticKernel.Core.Application.Actor can't break Goodtocode.SemanticKernel.Core.Application.ChatCompletion.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Core.Application.Actor uses a module listed above it, which is the healthy direction.
36→6 Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses Goodtocode.SemanticKernel.Core.Application.Common.Models✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses a type in Goodtocode.SemanticKernel.Core.Application.Common.Models.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.Audio.AdminAudioController→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedList
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses Goodtocode.SemanticKernel.Core.Application.Common.Models, so a change to Goodtocode.SemanticKernel.Core.Application.Common.Models can break Goodtocode.SemanticKernel.Presentation.WebApi.Audio, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.Audio can't break Goodtocode.SemanticKernel.Core.Application.Common.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses a module listed above it, which is the healthy direction.
36→21 Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses Goodtocode.SemanticKernel.Presentation.WebApi.Common✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses a type in Goodtocode.SemanticKernel.Presentation.WebApi.Common.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.Audio.AdminAudioController→Goodtocode.SemanticKernel.Presentation.WebApi.Common.ApiControllerBase
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses Goodtocode.SemanticKernel.Presentation.WebApi.Common, so a change to Goodtocode.SemanticKernel.Presentation.WebApi.Common can break Goodtocode.SemanticKernel.Presentation.WebApi.Audio, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.Audio can't break Goodtocode.SemanticKernel.Presentation.WebApi.Common.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses a module listed above it, which is the healthy direction.
36→29 Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses Goodtocode.SemanticKernel.Core.Application.Audio✕
- Connections
- 3 pairs of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses a type in Goodtocode.SemanticKernel.Core.Application.Audio.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.Audio.AdminAudioController→Goodtocode.SemanticKernel.Core.Application.Audio.CreateTextToAudioCommandGoodtocode.SemanticKernel.Presentation.WebApi.Audio.AdminAudioController→Goodtocode.SemanticKernel.Core.Application.Audio.GetTextAudioPaginatedQueryGoodtocode.SemanticKernel.Presentation.WebApi.Audio.AdminAudioController→Goodtocode.SemanticKernel.Core.Application.Audio.TextAudioDto
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses Goodtocode.SemanticKernel.Core.Application.Audio, so a change to Goodtocode.SemanticKernel.Core.Application.Audio can break Goodtocode.SemanticKernel.Presentation.WebApi.Audio, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.Audio can't break Goodtocode.SemanticKernel.Core.Application.Audio.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.Audio uses a module listed above it, which is the healthy direction.
37→6 Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses Goodtocode.SemanticKernel.Core.Application.Common.Models✕
- Connections
- 3 pairs of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses a type in Goodtocode.SemanticKernel.Core.Application.Common.Models.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatMessageController→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedListGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatSessionController→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedListGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.MyChatSessionController→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedList
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses Goodtocode.SemanticKernel.Core.Application.Common.Models, so a change to Goodtocode.SemanticKernel.Core.Application.Common.Models can break Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion can't break Goodtocode.SemanticKernel.Core.Application.Common.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses a module listed above it, which is the healthy direction.
37→21 Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses Goodtocode.SemanticKernel.Presentation.WebApi.Common✕
- Connections
- 3 pairs of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses a type in Goodtocode.SemanticKernel.Presentation.WebApi.Common.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatMessageController→Goodtocode.SemanticKernel.Presentation.WebApi.Common.ApiControllerBaseGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatSessionController→Goodtocode.SemanticKernel.Presentation.WebApi.Common.ApiControllerBaseGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.MyChatSessionController→Goodtocode.SemanticKernel.Presentation.WebApi.Common.ApiControllerBase
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses Goodtocode.SemanticKernel.Presentation.WebApi.Common, so a change to Goodtocode.SemanticKernel.Presentation.WebApi.Common can break Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion can't break Goodtocode.SemanticKernel.Presentation.WebApi.Common.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses a module listed above it, which is the healthy direction.
37→30 Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses Goodtocode.SemanticKernel.Core.Application.ChatCompletion✕
- Connections
- 9 pairs of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses a type in Goodtocode.SemanticKernel.Core.Application.ChatCompletion.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatMessageController→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.ChatMessageDtoGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatMessageController→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatMessageCommandGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatMessageController→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatMessagesPaginatedQueryGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatSessionController→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.ChatSessionDtoGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatSessionController→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.CreateChatSessionCommandGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatSessionController→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.GetChatSessionsPaginatedQueryGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatSessionController→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.PatchChatSessionCommandGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.AdminChatSessionController→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.UpdateChatSessionCommandGoodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion.MyChatSessionController→Goodtocode.SemanticKernel.Core.Application.ChatCompletion.ChatSessionDto
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses Goodtocode.SemanticKernel.Core.Application.ChatCompletion, so a change to Goodtocode.SemanticKernel.Core.Application.ChatCompletion can break Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion can't break Goodtocode.SemanticKernel.Core.Application.ChatCompletion.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.ChatCompletion uses a module listed above it, which is the healthy direction.
38→6 Goodtocode.SemanticKernel.Presentation.WebApi.Image uses Goodtocode.SemanticKernel.Core.Application.Common.Models✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.Image uses a type in Goodtocode.SemanticKernel.Core.Application.Common.Models.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.Image.AdminImageController→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedList
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.Image uses Goodtocode.SemanticKernel.Core.Application.Common.Models, so a change to Goodtocode.SemanticKernel.Core.Application.Common.Models can break Goodtocode.SemanticKernel.Presentation.WebApi.Image, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.Image can't break Goodtocode.SemanticKernel.Core.Application.Common.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.Image uses a module listed above it, which is the healthy direction.
38→21 Goodtocode.SemanticKernel.Presentation.WebApi.Image uses Goodtocode.SemanticKernel.Presentation.WebApi.Common✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.Image uses a type in Goodtocode.SemanticKernel.Presentation.WebApi.Common.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.Image.AdminImageController→Goodtocode.SemanticKernel.Presentation.WebApi.Common.ApiControllerBase
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.Image uses Goodtocode.SemanticKernel.Presentation.WebApi.Common, so a change to Goodtocode.SemanticKernel.Presentation.WebApi.Common can break Goodtocode.SemanticKernel.Presentation.WebApi.Image, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.Image can't break Goodtocode.SemanticKernel.Presentation.WebApi.Common.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.Image uses a module listed above it, which is the healthy direction.
38→31 Goodtocode.SemanticKernel.Presentation.WebApi.Image uses Goodtocode.SemanticKernel.Core.Application.Image✕
- Connections
- 3 pairs of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.Image uses a type in Goodtocode.SemanticKernel.Core.Application.Image.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.Image.AdminImageController→Goodtocode.SemanticKernel.Core.Application.Image.CreateTextToImageCommandGoodtocode.SemanticKernel.Presentation.WebApi.Image.AdminImageController→Goodtocode.SemanticKernel.Core.Application.Image.GetTextImagesPaginatedQueryGoodtocode.SemanticKernel.Presentation.WebApi.Image.AdminImageController→Goodtocode.SemanticKernel.Core.Application.Image.TextImageDto
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.Image uses Goodtocode.SemanticKernel.Core.Application.Image, so a change to Goodtocode.SemanticKernel.Core.Application.Image can break Goodtocode.SemanticKernel.Presentation.WebApi.Image, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.Image can't break Goodtocode.SemanticKernel.Core.Application.Image.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.Image uses a module listed above it, which is the healthy direction.
39→6 Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses Goodtocode.SemanticKernel.Core.Application.Common.Models✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses a type in Goodtocode.SemanticKernel.Core.Application.Common.Models.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration.AdminTextGenerationController→Goodtocode.SemanticKernel.Core.Application.Common.Models.PaginatedList
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses Goodtocode.SemanticKernel.Core.Application.Common.Models, so a change to Goodtocode.SemanticKernel.Core.Application.Common.Models can break Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration can't break Goodtocode.SemanticKernel.Core.Application.Common.Models.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses a module listed above it, which is the healthy direction.
39→21 Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses Goodtocode.SemanticKernel.Presentation.WebApi.Common✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses a type in Goodtocode.SemanticKernel.Presentation.WebApi.Common.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration.AdminTextGenerationController→Goodtocode.SemanticKernel.Presentation.WebApi.Common.ApiControllerBase
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses Goodtocode.SemanticKernel.Presentation.WebApi.Common, so a change to Goodtocode.SemanticKernel.Presentation.WebApi.Common can break Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration can't break Goodtocode.SemanticKernel.Presentation.WebApi.Common.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses a module listed above it, which is the healthy direction.
39→32 Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses Goodtocode.SemanticKernel.Core.Application.TextGeneration✕
- Connections
- 3 pairs of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses a type in Goodtocode.SemanticKernel.Core.Application.TextGeneration.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration.AdminTextGenerationController→Goodtocode.SemanticKernel.Core.Application.TextGeneration.CreateTextPromptCommandGoodtocode.SemanticKernel.Presentation.WebApi.TextGeneration.AdminTextGenerationController→Goodtocode.SemanticKernel.Core.Application.TextGeneration.GetTextPromptsPaginatedQueryGoodtocode.SemanticKernel.Presentation.WebApi.TextGeneration.AdminTextGenerationController→Goodtocode.SemanticKernel.Core.Application.TextGeneration.TextPromptDto
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses Goodtocode.SemanticKernel.Core.Application.TextGeneration, so a change to Goodtocode.SemanticKernel.Core.Application.TextGeneration can break Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration can't break Goodtocode.SemanticKernel.Core.Application.TextGeneration.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.TextGeneration uses a module listed above it, which is the healthy direction.
40→21 Goodtocode.SemanticKernel.Presentation.WebApi.Actor uses Goodtocode.SemanticKernel.Presentation.WebApi.Common✕
- Connections
- 1 pair of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.Actor uses a type in Goodtocode.SemanticKernel.Presentation.WebApi.Common.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.Actor.MyActorController→Goodtocode.SemanticKernel.Presentation.WebApi.Common.ApiControllerBase
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.Actor uses Goodtocode.SemanticKernel.Presentation.WebApi.Common, so a change to Goodtocode.SemanticKernel.Presentation.WebApi.Common can break Goodtocode.SemanticKernel.Presentation.WebApi.Actor, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.Actor can't break Goodtocode.SemanticKernel.Presentation.WebApi.Common.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.Actor uses a module listed above it, which is the healthy direction.
40→35 Goodtocode.SemanticKernel.Presentation.WebApi.Actor uses Goodtocode.SemanticKernel.Core.Application.Actor✕
- Connections
- 2 pairs of types, where a type in Goodtocode.SemanticKernel.Presentation.WebApi.Actor uses a type in Goodtocode.SemanticKernel.Core.Application.Actor.
- The types involved
Goodtocode.SemanticKernel.Presentation.WebApi.Actor.MyActorController→Goodtocode.SemanticKernel.Core.Application.Actor.ActorDtoGoodtocode.SemanticKernel.Presentation.WebApi.Actor.MyActorController→Goodtocode.SemanticKernel.Core.Application.Actor.SaveMyActorCommand
- Direction
- Goodtocode.SemanticKernel.Presentation.WebApi.Actor uses Goodtocode.SemanticKernel.Core.Application.Actor, so a change to Goodtocode.SemanticKernel.Core.Application.Actor can break Goodtocode.SemanticKernel.Presentation.WebApi.Actor, while a change to Goodtocode.SemanticKernel.Presentation.WebApi.Actor can't break Goodtocode.SemanticKernel.Core.Application.Actor.
- Position
- Below the diagonal: Goodtocode.SemanticKernel.Presentation.WebApi.Actor 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 123 | Medium |
| A05:2025 — Injection | 41 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with ConfigureServices.cs (3), AdminChatSessionController.cs, AdminTextGenerationController.cs; Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.7 pts | Low | ADR Quality |
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). | +3.4 pts | Low | Secret Scanning |
| Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with ConfigureServices.cs (3), AdminChatSessionController.cs, AdminTextGenerationController.cs. | +3.7 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.3 pts | Medium | Architecture documentation |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +2.9 pts | Medium | DR & Backup |
| Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. | +1.3 pts | Low | Test Distribution |
| Enable Dependabot/Renovate or a dependency-review gate. | +1.6 pts | Medium | Security & performance tooling |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +1.6 pts | Medium | Keyboard semantics |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/Infrastructure.SemanticKernel/AiModels/OpenAiModels.cs | 6.5 | Mixed | Explicit Debt: Dead code: OpenAiModels |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 98 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 98 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, 323 of 346 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- 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).
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- 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 62 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Core.Application/Actor/CreateActorCommand.cs`, `src/Core.Application/Actor/DeleteActorByExternalIdCommand.cs`, `src/Core.Application/Actor/DeleteActorCommand.cs`, `src/Core.Application/Actor/GetActorChatSessionQuery.cs`, `src/Core.Application/Actor/GetActorChatSessionsPaginatedQuery.cs`, … (+53 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D39 IL Efficiency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (src/Presentation.Blazor). the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'REDACTED'`: igureServicesAuth.AddAccessTokenHttpClient(IServiceCollection services, Action`1 configureOptions) in src/Presentation.Blazor/ConfigureServicesAuth…; runtime evidence skipped (launch chosen because REDACTED is a Microsoft.NET.Sdk.Web project).
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
19 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 9 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with GetActorChatSessionsPaginatedQuery.cs, NewChatMessageCard.razor, GetTextAudiosPaginatedQuery.cs. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 Members sharing a duplicated core (14 members, 50+ identical tokens) finding(s) in Code Duplication — start with GetActorChatSessionsPaginatedQueryValidator.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Members sharing a duplicated core (7 members, 50+ identical tokens) finding(s) in Code Duplication — start with ActorsConfig.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
7 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling — start with Core.Application.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 37 classes have LCOM4 above 3.
D9 · Test Distribution
35 test methods: 0 unit, 35 integration, 0 BDD, 0 e2e.
What to do
- Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, 1 mock references across 35 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). integration: measured (0 flaky).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 259 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 49 direct `PackageReference`(s), and 201 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
6 deducted debt markers + 18 dead symbols across 5641 LoC in the .NET projects (0.9/KLoC) → score 8.1.
What to do
- Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with GetChatSessionQueryStepDefinitions.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 18 Dead code finding(s) in Explicit Debt — start with OpenAiModels.cs (5), IActorsPlugin.cs (2), IChatMessagesPlugin.cs (2). — One of this dimension's main actionable groups (18 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D18 · Solution Shape
7 projects, 246 source files, 15262 hand-written lines of code (5641 production / 9621 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 927 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 9 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 7 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 7 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Core.Application.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Split Core.Application finding(s) in Project Cohesion — start with Core.Application.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
93 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
41 finding(s): 0 critical, 39 high, 1 medium, 1 low. 24 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 59 file(s) — `src/Core.Application/Actor/CreateActorCommand.cs` (line 17), `src/Core.Application/Actor/DeleteActorByExternalIdCommand.cs` (line 12), `src/Core.Application/Actor/DeleteActorCommand.cs` (line 12), `src/Core.Application/Actor/GetActorChatSessionQuery.cs` (line 14), `src/Core.Application/Actor/GetActorChatSessionsPaginatedQuery.cs` (line 17), … (+54 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 59 of those file(s) — `src/Core.Application/Actor/CreateActorCommand.cs`, `src/Core.Application/Actor/DeleteActorByExternalIdCommand.cs`, `src/Core.Application/Actor/DeleteActorCommand.cs`, `src/Core.Application/Actor/GetActorChatSessionQuery.cs`, `src/Core.Application/Actor/GetActorChatSessionsPaginatedQuery.cs`, … (+54 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (4). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 24 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (24 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 1 critical, 3 high, 1 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
123 finding(s): 0 critical, 0 high, 123 medium, 0 low.
What to do
- Resolve the 123 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (28), REDACTED (11), REDACTED (11). — One of this dimension's main actionable groups (123 warning-level).
D34 · Knowledge Freshness
26 of 26 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Presentation.WebApi/ChatCompletion/AdminChatSessionController.cs. Counted over 26 of the 173 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with ConfigureServices.cs (3), AdminChatSessionController.cs, AdminTextGenerationController.cs. — One of this dimension's main actionable groups (26 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 7 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
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This layout renders the routed page body, so it is where the landmark belongs: wrap @Body in <main>. — src/Presentation.Blazor/Components/Layout/MainLayout.razor:12
- A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet). — src/Presentation.Blazor/Components/Layout/NotFound.razor:3
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — src/Presentation.Blazor/Components/Wizard/WizardLayout.razor:11
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 31 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies
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
- `ActorsPlugin` is a singleton (one shared instance) but mutates instance state outside any lock (_currentFunctionName, _currentParameters; e.g. `_currentFunctionName` at line 33). — src/Infrastructure.SemanticKernel/Plugins/ActorsPlugin.cs:18
- `ChatSessionsPlugin` is a singleton (one shared instance) but mutates instance state outside any lock (_currentFunctionName, _currentParameters; e.g. `_currentFunctionName` at line 24). — src/Infrastructure.SemanticKernel/Plugins/ChatSessionsPlugin.cs:9
- `ChatMessagesPlugin` is a singleton (one shared instance) but mutates instance state outside any lock (_currentFunctionName, _currentParameters; e.g. `_currentFunctionName` at line 25). — src/Infrastructure.SemanticKernel/Plugins/ChatMessagesPlugin.cs:9
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls
C3 · Audit Trail
- An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
What to do
- Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
DM1 · Aggregate boundaries
- `ChatSessionEntity` references the aggregate root `ActorEntity` directly (via `Actor`) — hold its `ActorEntityId` instead. — src/Core.Domain/ChatCompletion/ChatSessionEntity.cs:13
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
- `CreateTextPromptCommandHandler.Handle` saves `TextResponseEntity`, `TextPromptEntity` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/Core.Application/TextGeneration/CreateTextPromptCommand.cs:20
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
- `ChatMessageEntity` reads `DateTime.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/Core.Domain/ChatCompletion/ChatMessageEntity.cs:20
- `ChatSessionEntity` reads `DateTime.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/Core.Domain/ChatCompletion/ChatSessionEntity.cs:22
- `TextAudioEntity` reads `DateTime.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/Core.Domain/Audio/TextAudioEntity.cs:44
- `TextImageEntity` reads `DateTime.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/Core.Domain/Image/TextImageEntity.cs:73
- `TextPromptEntity` reads `DateTime.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/Core.Domain/TextGeneration/TextPromptEntity.cs:21
What to do
- Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM2 · Strongly-typed ids
- `ChatSessionEntity.ActorId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Core.Domain/ChatCompletion/ChatSessionEntity.cs:10
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
DM5 · Encapsulated state
- `ChatSessionEntity` exposes its own state through a mutable collection (Messages) — a caller can add to or remove from it directly, without passing through the methods that enforce the invariants. — src/Core.Domain/ChatCompletion/ChatSessionEntity.cs:6
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/Infrastructure.SemanticKernel/Services/TextGenerationService.cs:12
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `Attributes` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Infrastructure.SemanticKernel/Services/TextGenerationService.cs:12
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×11) — src/Presentation.Blazor/ConfigureServicesAuth.cs:52, src/Presentation.Blazor/ConfigureServicesAuth.cs:57, src/Presentation.Blazor/ConfigureServicesAuth.cs:60, …
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 6 of 6 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
- Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
What to do
- Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
M4 · Documentation accuracy
P1 · CI/CD gates
P11 · BDD / executable specs
P2 · Observability
- Only 2/5 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 5, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
- Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
P3 · Security & performance tooling
- `src/Core.Application/Core.Application.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/Core.Application/Core.Application.csproj:13
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×2) — REDACTED:8, src/Presentation.WebApi/Program.cs:10
- No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.) — src/Presentation.Blazor/Components/Auth/Routing/LoginLogoutEndpointRouteBuilderExtensions.cs:20
What to do
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
- Set secure cookie flags — CookieSecurePolicy.Always, HttpOnly, and SameSite (Strict/Lax) on auth/session cookies. Skip only if the app sets no cookies.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 87/127 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×39) — src/Core.Application/Common/Models/PaginatedList.cs:14, src/Presentation.WebApi/Actor/MyActorController.cs:39, src/Presentation.WebApi/Actor/MyActorController.cs:68, …
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X32 · Type resolved by simple name across every loaded assembly
X4 · Structured logging
X5 · Nullable reference types
- ~1.6 `!` suppressions per 1k syntax nodes — 56 suppression(s) across the 34339 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 87% | Strong | Strongest area. |
| Architecture | 75% | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 46% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 46% | Weak — gated by P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 66% | Adequate — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 59% | Adequate — gated by DM1, DM2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 53% | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 77% | Strong | Solid. |
Unscored — 4 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 29 check(s) not relevant to this codebase
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'REDACTED'`: igureServicesAuth.AddAccessTokenHttpClient(IServiceCollection services, Action`1 configureOptions) in src/Presentation.Blazor/ConfigureServicesAuth…; runtime evidence skipped (launch chosen because REDACTED is a Microsoft.NET.Sdk.Web project) 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.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1305 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (5,641 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Core.Domain), 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 — Too few judgeable comments (20 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 58 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (39 CQRS handler(s))
- ED5 Idempotency — not scored — 14 of 16 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X8 JS interop contract — 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 — 50 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Routed page without a <PageTitle> src/Presentation.Blazor/Components/Layout/NotFound.razor:3
- Click handler on a non-interactive <span> src/Presentation.Blazor/Components/Wizard/WizardLayout.razor:11
- WriteOnlyPrivateField src/Tests.Specs.Integration/ChatCompletion/GetChatSessionQueryStepDefinitions.cs:13
- AnalyzerSeverityNone src/Presentation.Blazor/Clients/.editorconfig:6
- REDACTED
- REDACTED
- REDACTED
- Aggregate holds a reference to another aggregate: ChatSessionEntity.Actor src/Core.Domain/ChatCompletion/ChatSessionEntity.cs:13
Serious — 225 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Async method without CancellationToken: CreateAsync src/Core.Application/Common/Models/PaginatedList.cs:14
- Async method without CancellationToken: GetMyActorProfile src/Presentation.WebApi/Actor/MyActorController.cs:39
- Async method without CancellationToken: SaveMyActor src/Presentation.WebApi/Actor/MyActorController.cs:68
- Async method without CancellationToken: Get src/Presentation.WebApi/Audio/AdminAudioController.cs:42
- Async method without CancellationToken: GetAll src/Presentation.WebApi/Audio/AdminAudioController.cs:76
- Async method without CancellationToken: GetTextAudioPaginatedQuery src/Presentation.WebApi/Audio/AdminAudioController.cs:107
- Async method without CancellationToken: Post src/Presentation.WebApi/Audio/AdminAudioController.cs:143
- Async method without CancellationToken: Delete src/Presentation.WebApi/Audio/AdminAudioController.cs:164
- Async method without CancellationToken: Get src/Presentation.WebApi/ChatCompletion/AdminChatMessageController.cs:38
- Async method without CancellationToken: GetAll src/Presentation.WebApi/ChatCompletion/AdminChatMessageController.cs:67
- Async method without CancellationToken: GetPaginated src/Presentation.WebApi/ChatCompletion/AdminChatMessageController.cs:98
- Async method without CancellationToken: Post src/Presentation.WebApi/ChatCompletion/AdminChatMessageController.cs:141
- Async method without CancellationToken: Get src/Presentation.WebApi/ChatCompletion/AdminChatSessionController.cs:42
- Async method without CancellationToken: GetAll src/Presentation.WebApi/ChatCompletion/AdminChatSessionController.cs:76
- Async method without CancellationToken: GetChatSessionsPaginatedQuery src/Presentation.WebApi/ChatCompletion/AdminChatSessionController.cs:107
- Async method without CancellationToken: Post src/Presentation.WebApi/ChatCompletion/AdminChatSessionController.cs:150
- Async method without CancellationToken: Put src/Presentation.WebApi/ChatCompletion/AdminChatSessionController.cs:183
- Async method without CancellationToken: Patch src/Presentation.WebApi/ChatCompletion/AdminChatSessionController.cs:212
- Async method without CancellationToken: Delete src/Presentation.WebApi/ChatCompletion/AdminChatSessionController.cs:235
- Async method without CancellationToken: GetMyChatSessions src/Presentation.WebApi/ChatCompletion/MyChatSessionController.cs:37
- Async method without CancellationToken: GetMyChatSessionsPaginated src/Presentation.WebApi/ChatCompletion/MyChatSessionController.cs:66
- Async method without CancellationToken: GetMyChatSession src/Presentation.WebApi/ChatCompletion/MyChatSessionController.cs:97
- Async method without CancellationToken: Get src/Presentation.WebApi/Image/AdminImageController.cs:42
- Async method without CancellationToken: GetAll src/Presentation.WebApi/Image/AdminImageController.cs:76
- Async method without CancellationToken: GetTextImagesPaginatedQuery src/Presentation.WebApi/Image/AdminImageController.cs:107
- Dead code: GetActorByIdAsync src/Core.Application/Abstractions/IActorsPlugin.cs:5
- Dead code: GetActorsByNameAsync src/Core.Application/Abstractions/IActorsPlugin.cs:6
- Dead code: ListRecentMessagesAsync src/Core.Application/Abstractions/IChatMessagesPlugin.cs:5
- Dead code: GetChatMessagesAsync src/Core.Application/Abstractions/IChatMessagesPlugin.cs:6
- Dead code: ListRecentSessionsAsync src/Core.Application/Abstractions/IChatSessionsPlugin.cs:5
- Dead code: UpdateChatSessionTitleAsync src/Core.Application/Abstractions/IChatSessionsPlugin.cs:6
- Dead code: TokenRoleClaimTypes src/Presentation.WebApi/Auth/ConfigureServices.cs:12
- Dead code: TokenRoleClaimTypes src/Presentation.Blazor/ConfigureServicesAuth.cs:13
- Dead code: SetItemAsync src/Presentation.Blazor/Services/LocalStorageService.cs:15
- Dead code: GetItemAsync src/Presentation.Blazor/Services/LocalStorageService.cs:16
- Dead code: JsonSerializerOptionsProvider src/Infrastructure.SqlServer/JsonSerializerOptionsProvider.cs:5
- Dead code: HuggingfaceModels src/Infrastructure.SemanticKernel/AiModels/HuggingfaceModels.cs:3
- Dead code: OpenAiModels src/Infrastructure.SemanticKernel/AiModels/OpenAiModels.cs:3
- Dead code: TextEmbedding src/Infrastructure.SemanticKernel/AiModels/OpenAiModels.cs:15
- Dead code: TextModeration src/Infrastructure.SemanticKernel/AiModels/OpenAiModels.cs:20
- Dead code: Image src/Infrastructure.SemanticKernel/AiModels/OpenAiModels.cs:24
- Dead code: Audio src/Infrastructure.SemanticKernel/AiModels/OpenAiModels.cs:29
- Dead code: AzureOpenAIOptions src/Infrastructure.SemanticKernel/Options/AzureOpenAIOptions.cs:8
- Duplicated block (5 lines × 2) src/Core.Application/Actor/GetActorChatSessionsPaginatedQuery.cs:23
- Duplicated block (5 lines × 2) src/Presentation.Blazor/Pages/Chat/Components/NewChatMessageCard.razor:31
- Duplicated block (5 lines × 2) src/Core.Application/Audio/GetTextAudiosPaginatedQuery.cs:21
- Duplicated block (5 lines × 2) src/Core.Application/ChatCompletion/ChatMessageDto.cs:7
- Duplicated block (5 lines × 2) src/Core.Application/ChatCompletion/GetChatMessagesPaginatedQuery.cs:21
- Duplicated block (5 lines × 2) src/Core.Application/ChatCompletion/GetChatSessionsPaginatedQuery.cs:21
- Duplicated block (5 lines × 2) src/Core.Application/Image/GetTextImagesPaginatedQuery.cs:21
- Duplicated block (5 lines × 2) src/Core.Application/TextGeneration/GetTextPromptsPaginatedQuery.cs:21
- Duplicated block (5 lines × 2) src/Presentation.Blazor/Pages/Chat/Components/ChatSessionList.razor:82
- Domain type reads the wall clock: ChatMessageEntity src/Core.Domain/ChatCompletion/ChatMessageEntity.cs:20
- Domain type reads the wall clock: ChatSessionEntity src/Core.Domain/ChatCompletion/ChatSessionEntity.cs:22
- Domain type reads the wall clock: TextAudioEntity src/Core.Domain/Audio/TextAudioEntity.cs:44
- Domain type reads the wall clock: TextImageEntity src/Core.Domain/Image/TextImageEntity.cs:73
- Domain type reads the wall clock: TextPromptEntity src/Core.Domain/TextGeneration/TextPromptEntity.cs:21
- Stateful singleton: ActorsPlugin src/Infrastructure.SemanticKernel/Plugins/ActorsPlugin.cs:18
- Stateful singleton: ChatSessionsPlugin src/Infrastructure.SemanticKernel/Plugins/ChatSessionsPlugin.cs:9
- Stateful singleton: ChatMessagesPlugin src/Infrastructure.SemanticKernel/Plugins/ChatMessagesPlugin.cs:9
- CommentedOutCode src/Infrastructure.SemanticKernel/ConfigureServices.cs:22
- CommentedOutCode src/Presentation.Blazor/ConfigureServicesAuth.cs:88
- TodoComment REDACTED:44
- TodoComment src/Presentation.WebApi/ConfigureServices.cs:50
- Page without a main landmark src/Presentation.Blazor/Components/Layout/MainLayout.razor:12
- Accessibility enforcement below the top rung
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (14 members, 50+ identical tokens) src/Core.Application/Actor/GetActorChatSessionsPaginatedQueryValidator.cs:6
- Members sharing a duplicated core (7 members, 50+ identical tokens) src/Infrastructure.SqlServer/Persistence/Configurations/ActorsConfig.cs:8
- Duplicated block (33 lines × 2) src/Presentation.Blazor/Pages/Chat/Components/NewChatMessageCard.razor:54
- Duplicated block (20 lines × 2) src/Presentation.Blazor/Components/Skeleton/SkeletonList.razor:24
- Duplicated block (12–17 lines × 7) src/Infrastructure.SqlServer/Persistence/Configurations/ActorsConfig.cs:11
- Duplicated block (13 lines × 7) src/Core.Application/Actor/GetActorChatSessionsPaginatedQueryValidator.cs:9
- Duplicated block (8 lines × 4) src/Core.Application/Actor/GetActorChatSessionsPaginatedQueryValidator.cs:9
- Duplicated block (9 lines × 2) src/Presentation.Blazor/Components/Skeleton/SkeletonList.razor:12
- Duplicated block (8 lines × 10) src/Core.Application/Audio/GetTextAudiosPaginatedQueryValidator.cs:7
- Duplicated block (9 lines × 7) src/Core.Application/Actor/GetActorChatSessionsQueryValidator.cs:9
- Duplicated block (8 lines × 14) src/Core.Application/Actor/GetActorChatSessionsPaginatedQueryValidator.cs:9
- Duplicated block (7 lines × 2) src/Core.Application/Actor/GetActorChatSessionsPaginatedQuery.cs:26
- Off the main sequence: Core.Application src/Core.Application/Core.Application.csproj:1
- One operation mutates 2 aggregates: CreateTextPromptCommandHandler.Handle src/Core.Application/TextGeneration/CreateTextPromptCommand.cs:20
- Unfinished stub — throws NotImplementedException src/Infrastructure.SemanticKernel/Services/TextGenerationService.cs:12
- Unfinished stub — throws NotImplementedException src/Infrastructure.SemanticKernel/Services/TextGenerationService.cs:12
- Coverage collected but not gated
- No DR/backup evidence
- NuGet dependencies are not locked
Minor — 70 finding(s)
- Orphaned file src/Presentation.WebApi/ChatCompletion/AdminChatSessionController.cs:1
- Orphaned file src/Presentation.WebApi/TextGeneration/AdminTextGenerationController.cs:1
- Orphaned file src/Presentation.Blazor/ConfigureServicesAuth.cs:1
- Orphaned file src/Presentation.WebApi/Image/AdminImageController.cs:1
- Orphaned file src/Presentation.WebApi/Audio/AdminAudioController.cs:1
- Orphaned file src/Presentation.WebApi/ChatCompletion/AdminChatMessageController.cs:1
- Orphaned file src/Presentation.WebApi/ConfigureServices.cs:1
- Orphaned file src/Presentation.WebApi/Common/ApiExceptionFilterAttribute.cs:1
- Orphaned file src/Infrastructure.SemanticKernel/ConfigureServices.cs:1
- Orphaned file src/Infrastructure.SemanticKernel/Plugins/ActorsPlugin.cs:1
- Orphaned file src/Core.Application/ChatCompletion/CreateChatMessageCommand.cs:1
- Orphaned file src/Presentation.WebApi/ChatCompletion/MyChatSessionController.cs:1
- Orphaned file src/Presentation.WebApi/Auth/UserInfoBehavior.cs:1
- Orphaned file src/Presentation.Blazor/Components/Auth/UserClaimsInfo.cs:1
- Orphaned file src/Presentation.Blazor/Pages/Chat/Models/ChatSessionsModel.cs:1
- Orphaned file src/Core.Application/ChatCompletion/CreateChatSessionCommand.cs:1
- Orphaned file src/Presentation.WebApi/Auth/ClaimsUserInfo.cs:1
- Orphaned file src/Infrastructure.SemanticKernel/Plugins/ChatSessionsPlugin.cs:1
- Orphaned file src/Infrastructure.SqlServer/Persistence/SemanticKernelContext.cs:1
- Orphaned file src/Core.Application/Audio/CreateTextToAudioCommand.cs:1
- Orphaned file src/Presentation.Blazor/ConfigureServices.cs:1
- Orphaned file src/Infrastructure.SemanticKernel/Plugins/ChatMessagesPlugin.cs:1
- Orphaned file src/Presentation.Blazor/Pages/Chat/Services/ChatService.cs:1
- Orphaned file src/Core.Application/Image/CreateTextToImageCommand.cs:1
- Orphaned file src/Presentation.WebApi/Actor/MyActorController.cs:1
- Commented-out code src/Presentation.Blazor/ConfigureServicesAuth.cs:52
- Commented-out code src/Presentation.Blazor/ConfigureServicesAuth.cs:57
- Commented-out code src/Presentation.Blazor/ConfigureServicesAuth.cs:60
- Commented-out code src/Presentation.Blazor/ConfigureServicesAuth.cs:63
- Commented-out code src/Presentation.Blazor/ConfigureServicesAuth.cs:66
- Commented-out code src/Presentation.Blazor/ConfigureServicesAuth.cs:84
- Commented-out code src/Presentation.Blazor/ConfigureServicesAuth.cs:90
- Commented-out code src/Presentation.Blazor/ConfigureServicesAuth.cs:103
- Commented-out code src/Presentation.Blazor/ConfigureServicesAuth.cs:112
- Commented-out code src/Presentation.Blazor/ConfigureServicesAuth.cs:114
- Commented-out code src/Presentation.WebApi/Auth/ConfigureServices.cs:31
- Silent fallback default on parse failure src/Core.Application/ChatCompletion/CreateChatSessionCommand.cs:47
- Silent fallback default on parse failure src/Presentation.WebApi/Auth/ClaimsUserInfo.cs:16
- Silent fallback default on parse failure src/Presentation.WebApi/Auth/ClaimsUserInfo.cs:26
- Silent fallback default on parse failure src/Presentation.Blazor/Components/Auth/UserClaimsInfo.cs:18
- Silent fallback default on parse failure src/Presentation.Blazor/Components/Auth/UserClaimsInfo.cs:28
- No security response headers detected
- No security response headers detected REDACTED:8
- No security response headers detected src/Presentation.WebApi/Program.cs:10
- Duplicated predicate src/Core.Application/Actor/GetActorChatSessionsPaginatedQuery.cs:26
- Duplicated predicate src/Presentation.WebApi/Program.cs:30
- Partial audit-trail evidence
- No ADRs found
- Projects may be oversized for their cohesion src/Core.Application/Core.Application.csproj:1
- Split Core.Application src/Core.Application/Core.Application.csproj:1
- REDACTED
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Inverted test pyramid
- Primitive id on a domain type: ChatSessionEntity.ActorId src/Core.Domain/ChatCompletion/ChatSessionEntity.cs:10
- Mutable entity: ChatSessionEntity src/Core.Domain/ChatCompletion/ChatSessionEntity.cs:6
- No ADRs
- No architecture diagram/doc
- No tests/ separation
- Logging is not universal
- No dependency-update automation src/Core.Application/Core.Application.csproj:13
- No changelog
- No performance benchmarks
- Secure cookie flags not detected src/Presentation.Blazor/Components/Auth/Routing/LoginLogoutEndpointRouteBuilderExtensions.cs:20
- Not all async methods take a CancellationToken
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 1 finding(s)
- Mock framework: Moq
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-53d219896d6d489a86a6b9e50b1cf47b/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-53d219896d6d489a86a6b9e50b1cf47b/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/Infrastructure.SqlServer/Migrations . | 41 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/SemanticKernelBlazor.sln package --vulnerable --include-transitive --format json | 5 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 123 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 58 file(s) — `src/Core.Application/Actor/CreateActorCommand.cs`, `src/Core.Application/Actor/DeleteActorByExternalIdCommand.cs`, `src/Core.Application/Actor/DeleteActorCommand.cs`, `src/Core.Application/Actor/GetActorChatSessionQuery.cs`, `src/Core.Application/Actor/GetActorChatSessionsPaginatedQuery.cs`, … (+53 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-92b13c87f6424dd5a8128d291c596c70 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 20 field(s)
- ActorDto.FirstName src/Core.Application/Actor/ActorDto.cs:9
- ActorDto.LastName src/Core.Application/Actor/ActorDto.cs:10
- CreateActorCommand.FirstName src/Core.Application/Actor/CreateActorCommand.cs:10
- CreateActorCommand.LastName src/Core.Application/Actor/CreateActorCommand.cs:11
- SaveMyActorCommand.FirstName src/Core.Application/Actor/SaveMyActorCommand.cs:9
- SaveMyActorCommand.LastName src/Core.Application/Actor/SaveMyActorCommand.cs:10
- ActorEntity.FirstName src/Core.Domain/Actor/ActorEntity.cs:10
- ActorEntity.LastName src/Core.Domain/Actor/ActorEntity.cs:11
- IUserEntity.FirstName src/Core.Domain/Auth/IUserEntity.cs:7
- IUserEntity.LastName src/Core.Domain/Auth/IUserEntity.cs:8
- UserEntity.FirstName src/Core.Domain/Auth/UserEntity.cs:14
- UserEntity.LastName src/Core.Domain/Auth/UserEntity.cs:15
- IUserClaimsInfo.Givenname src/Presentation.Blazor/Components/Auth/IUserClaimsInfo.cs:24
- IUserClaimsInfo.Surname src/Presentation.Blazor/Components/Auth/IUserClaimsInfo.cs:29
- UserClaimsInfo.Givenname src/Presentation.Blazor/Components/Auth/UserClaimsInfo.cs:35
- UserClaimsInfo.Surname src/Presentation.Blazor/Components/Auth/UserClaimsInfo.cs:40
- ClaimsUserInfo.Givenname src/Presentation.WebApi/Auth/ClaimsUserInfo.cs:33
- ClaimsUserInfo.Surname src/Presentation.WebApi/Auth/ClaimsUserInfo.cs:38
- IClaimsUserInfo.Givenname src/Presentation.WebApi/Auth/IClaimsUserInfo.cs:24
- IClaimsUserInfo.Surname src/Presentation.WebApi/Auth/IClaimsUserInfo.cs:29
Email — 10 field(s)
- ActorDto.Email src/Core.Application/Actor/ActorDto.cs:11
- CreateActorCommand.Email src/Core.Application/Actor/CreateActorCommand.cs:12
- SaveMyActorCommand.Email src/Core.Application/Actor/SaveMyActorCommand.cs:11
- ActorEntity.Email src/Core.Domain/Actor/ActorEntity.cs:12
- IUserEntity.Email src/Core.Domain/Auth/IUserEntity.cs:9
- UserEntity.Email src/Core.Domain/Auth/UserEntity.cs:16
- IUserClaimsInfo.Email src/Presentation.Blazor/Components/Auth/IUserClaimsInfo.cs:34
- UserClaimsInfo.Email src/Presentation.Blazor/Components/Auth/UserClaimsInfo.cs:45
- ClaimsUserInfo.Email src/Presentation.WebApi/Auth/ClaimsUserInfo.cs:43
- IClaimsUserInfo.Email src/Presentation.WebApi/Auth/IClaimsUserInfo.cs:34