Executive summary
gayankanishka/graphql-clean-architecture falls short of our standard for production because we found no encryption of stored data, no key vault and no enforced HTTPS and no access checks on the code's endpoints or handlers. It scores 37 out of 100 and is rated Weak, and 16 of its 17 critical findings are security problems.
Security and Compliance, at 22, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 9 points. Encrypting the sensitive stored data and keeping its keys in a vault would lift Security and Compliance itself, worth about 8 points. Raising Security and Compliance to 70 would lift the score to about 48.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four passwords or keys are open to anyone who can read the repository, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the two unsafe settings in infrastructure or container files need changing to safe values. The set of compiler warnings switched off in a project needs turning back on in the build file.
The product code is 2,486 lines, about €2,200 to rebuild.
If Security and Compliance rose from 22 to 70, the lowest score rated Strong, the score would rise from 37 to about 48.
New since the last survey: 5 findings
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Application/Application.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Domain/Domain.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/GraphQL/GraphQL.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Infrastructure/Infrastructure.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 tests/GraphQL.Tests/GraphQL.Tests.csproj
Fixed since the last survey: 1 finding
- Platform End-of-Life · End-of-life runtime: .NET net6.0 tests/GraphQL.Tests/GraphQL.Tests.csproj
Rebuild cost: about €2,200 · Estimate
| Cost to rebuild | €750 to €3,600, for 12 to 38 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 37. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 2,486 lines of product code, of which 56% is declarations and boilerplate, 40% straight logic and 4% logic with branches |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Domain.Common | 2 Domain.Entities | 3 Application.Attendees | 4 Application.Common.Interfaces | 5 Application.Sessions | 6 Application.Speakers | 7 Application.Tracks | 8 Infrastructure.Persistence | 9 Application.Attendees.Commands.CheckInAttendeeById | 10 Application.Attendees.Commands.RegisterAttendee | 11 Application.Attendees.Queries.GetAttendeeById | 12 Application.Attendees.Queries.GetAttendees | 13 Application.Attendees.Queries.GetAttendeesByIds | 14 Application.Attendees.Queries.GetAttendeesBySessionId | 15 Application.Sessions.Commands.AddSession | 16 Application.Sessions.Commands.RenameSession | 17 Application.Sessions.Commands.ScheduleSession | 18 Application.Sessions.Queries.GetSessionById | 19 Application.Sessions.Queries.GetSessions | 20 Application.Sessions.Queries.GetSessionsByAttendee | 21 Application.Sessions.Queries.GetSessionsByIds | 22 Application.Sessions.Queries.GetSessionsBySpeakerId | 23 Application.Sessions.Queries.GetSessionsByTrack | 24 Application.Speakers.Commands.AddSpeaker | 25 Application.Speakers.Commands.ModifySpeaker | 26 Application.Speakers.Queries.GetSessionSpeakers | 27 Application.Speakers.Queries.GetSpeakerById | 28 Application.Speakers.Queries.GetSpeakers | 29 Application.Speakers.Queries.GetSpeakersByIds | 30 Application.Tracks.Commands.AddTrack | 31 Application.Tracks.Commands.RenameTrack | 32 Application.Tracks.Queries.GetTrackById | 33 Application.Tracks.Queries.GetTrackByName | 34 Application.Tracks.Queries.GetTracksByIds | 35 Application.Tracks.Queries.GetTracksByNames | 36 Infrastructure.Persistence.DataLoaders | 37 Infrastructure.Persistence.Repositories | 38 GraphQL.Mutations | 39 GraphQL.Nodes | 40 GraphQL.Queries |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Domain.Common | ||||||||||||||||||||||||||||||||||||||||
| 2 Domain.Entities | ||||||||||||||||||||||||||||||||||||||||
| 3 Application.Attendees | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 4 Application.Common.Interfaces | 4 | |||||||||||||||||||||||||||||||||||||||
| 5 Application.Sessions | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 6 Application.Speakers | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 Application.Tracks | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 Infrastructure.Persistence | 4 | |||||||||||||||||||||||||||||||||||||||
| 9 Application.Attendees.Commands.CheckInAttendeeById | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 10 Application.Attendees.Commands.RegisterAttendee | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 11 Application.Attendees.Queries.GetAttendeeById | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Application.Attendees.Queries.GetAttendees | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 Application.Attendees.Queries.GetAttendeesByIds | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 Application.Attendees.Queries.GetAttendeesBySessionId | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 Application.Sessions.Commands.AddSession | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 Application.Sessions.Commands.RenameSession | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 Application.Sessions.Commands.ScheduleSession | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 Application.Sessions.Queries.GetSessionById | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Application.Sessions.Queries.GetSessions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 Application.Sessions.Queries.GetSessionsByAttendee | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 Application.Sessions.Queries.GetSessionsByIds | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Application.Sessions.Queries.GetSessionsBySpeakerId | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 Application.Sessions.Queries.GetSessionsByTrack | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 Application.Speakers.Commands.AddSpeaker | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 Application.Speakers.Commands.ModifySpeaker | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 Application.Speakers.Queries.GetSessionSpeakers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Application.Speakers.Queries.GetSpeakerById | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Application.Speakers.Queries.GetSpeakers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Application.Speakers.Queries.GetSpeakersByIds | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Application.Tracks.Commands.AddTrack | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 Application.Tracks.Commands.RenameTrack | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 Application.Tracks.Queries.GetTrackById | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Application.Tracks.Queries.GetTrackByName | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 Application.Tracks.Queries.GetTracksByIds | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 Application.Tracks.Queries.GetTracksByNames | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Infrastructure.Persistence.DataLoaders | 6 | 6 | 6 | |||||||||||||||||||||||||||||||||||||
| 37 Infrastructure.Persistence.Repositories | 4 | 4 | 4 | |||||||||||||||||||||||||||||||||||||
| 38 GraphQL.Mutations | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||
| 39 GraphQL.Nodes | 10 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 GraphQL.Queries | 4 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
3→1 Application.Attendees uses Domain.Common✕
- Connections
- 2 pairs of types, where a type in Application.Attendees uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Attendees.AttendeePayloadBase→ConferencePlanner.Domain.Common.PayloadConferencePlanner.Application.Attendees.AttendeePayloadBase→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Attendees uses Domain.Common, so a change to Domain.Common can break Application.Attendees, while a change to Application.Attendees can't break Domain.Common.
- Position
- Below the diagonal: Application.Attendees uses a module listed above it, which is the healthy direction.
3→2 Application.Attendees uses Domain.Entities✕
- Connections
- 3 pairs of types, where a type in Application.Attendees uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Attendees.AttendeePayloadBase→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.Application.Attendees.SessionAttendeeCheckIn→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.Application.Attendees.SessionAttendeeCheckIn→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Attendees uses Domain.Entities, so a change to Domain.Entities can break Application.Attendees, while a change to Application.Attendees can't break Domain.Entities.
- Position
- Below the diagonal: Application.Attendees uses a module listed above it, which is the healthy direction.
4→2 Application.Common.Interfaces uses Domain.Entities✕
- Connections
- 4 pairs of types, where a type in Application.Common.Interfaces uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Common.Interfaces.IAttendeeRepository→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.Application.Common.Interfaces.ISessionRepository→ConferencePlanner.Domain.Entities.SessionConferencePlanner.Application.Common.Interfaces.ISpeakerRepository→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.Application.Common.Interfaces.ITrackRepository→ConferencePlanner.Domain.Entities.Track
- Direction
- Application.Common.Interfaces uses Domain.Entities, so a change to Domain.Entities can break Application.Common.Interfaces, while a change to Application.Common.Interfaces can't break Domain.Entities.
- Position
- Below the diagonal: Application.Common.Interfaces uses a module listed above it, which is the healthy direction.
5→1 Application.Sessions uses Domain.Common✕
- Connections
- 2 pairs of types, where a type in Application.Sessions uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Sessions.SessionPayloadBase→ConferencePlanner.Domain.Common.PayloadConferencePlanner.Application.Sessions.SessionPayloadBase→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Sessions uses Domain.Common, so a change to Domain.Common can break Application.Sessions, while a change to Application.Sessions can't break Domain.Common.
- Position
- Below the diagonal: Application.Sessions uses a module listed above it, which is the healthy direction.
5→2 Application.Sessions uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Sessions uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Sessions.SessionFilterInputType→ConferencePlanner.Domain.Entities.SessionConferencePlanner.Application.Sessions.SessionPayloadBase→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Sessions uses Domain.Entities, so a change to Domain.Entities can break Application.Sessions, while a change to Application.Sessions can't break Domain.Entities.
- Position
- Below the diagonal: Application.Sessions uses a module listed above it, which is the healthy direction.
6→1 Application.Speakers uses Domain.Common✕
- Connections
- 2 pairs of types, where a type in Application.Speakers uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Speakers.SpeakerPayloadBase→ConferencePlanner.Domain.Common.PayloadConferencePlanner.Application.Speakers.SpeakerPayloadBase→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Speakers uses Domain.Common, so a change to Domain.Common can break Application.Speakers, while a change to Application.Speakers can't break Domain.Common.
- Position
- Below the diagonal: Application.Speakers uses a module listed above it, which is the healthy direction.
6→2 Application.Speakers uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Speakers uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Speakers.SpeakerPayloadBase→ConferencePlanner.Domain.Entities.Speaker
- Direction
- Application.Speakers uses Domain.Entities, so a change to Domain.Entities can break Application.Speakers, while a change to Application.Speakers can't break Domain.Entities.
- Position
- Below the diagonal: Application.Speakers uses a module listed above it, which is the healthy direction.
7→1 Application.Tracks uses Domain.Common✕
- Connections
- 2 pairs of types, where a type in Application.Tracks uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Tracks.TrackPayloadBase→ConferencePlanner.Domain.Common.PayloadConferencePlanner.Application.Tracks.TrackPayloadBase→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Tracks uses Domain.Common, so a change to Domain.Common can break Application.Tracks, while a change to Application.Tracks can't break Domain.Common.
- Position
- Below the diagonal: Application.Tracks uses a module listed above it, which is the healthy direction.
7→2 Application.Tracks uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Tracks uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Tracks.TrackPayloadBase→ConferencePlanner.Domain.Entities.Track
- Direction
- Application.Tracks uses Domain.Entities, so a change to Domain.Entities can break Application.Tracks, while a change to Application.Tracks can't break Domain.Entities.
- Position
- Below the diagonal: Application.Tracks uses a module listed above it, which is the healthy direction.
8→2 Infrastructure.Persistence uses Domain.Entities✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Persistence uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Infrastructure.Persistence.ApplicationDbContext→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.Infrastructure.Persistence.ApplicationDbContext→ConferencePlanner.Domain.Entities.SessionConferencePlanner.Infrastructure.Persistence.ApplicationDbContext→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.Infrastructure.Persistence.ApplicationDbContext→ConferencePlanner.Domain.Entities.Track
- Direction
- Infrastructure.Persistence uses Domain.Entities, so a change to Domain.Entities can break Infrastructure.Persistence, while a change to Infrastructure.Persistence can't break Domain.Entities.
- Position
- Below the diagonal: Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
9→1 Application.Attendees.Commands.CheckInAttendeeById uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Commands.CheckInAttendeeById uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Attendees.Commands.CheckInAttendeeById.CheckInAttendeePayload→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Attendees.Commands.CheckInAttendeeById uses Domain.Common, so a change to Domain.Common can break Application.Attendees.Commands.CheckInAttendeeById, while a change to Application.Attendees.Commands.CheckInAttendeeById can't break Domain.Common.
- Position
- Below the diagonal: Application.Attendees.Commands.CheckInAttendeeById uses a module listed above it, which is the healthy direction.
9→2 Application.Attendees.Commands.CheckInAttendeeById uses Domain.Entities✕
- Connections
- 3 pairs of types, where a type in Application.Attendees.Commands.CheckInAttendeeById uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Attendees.Commands.CheckInAttendeeById.CheckInAttendeeCommandHandler→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.Application.Attendees.Commands.CheckInAttendeeById.CheckInAttendeePayload→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.Application.Attendees.Commands.CheckInAttendeeById.CheckInAttendeePayload→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Attendees.Commands.CheckInAttendeeById uses Domain.Entities, so a change to Domain.Entities can break Application.Attendees.Commands.CheckInAttendeeById, while a change to Application.Attendees.Commands.CheckInAttendeeById can't break Domain.Entities.
- Position
- Below the diagonal: Application.Attendees.Commands.CheckInAttendeeById uses a module listed above it, which is the healthy direction.
9→3 Application.Attendees.Commands.CheckInAttendeeById uses Application.Attendees✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Commands.CheckInAttendeeById uses a type in Application.Attendees.
- The types involved
ConferencePlanner.Application.Attendees.Commands.CheckInAttendeeById.CheckInAttendeePayload→ConferencePlanner.Application.Attendees.AttendeePayloadBase
- Direction
- Application.Attendees.Commands.CheckInAttendeeById uses Application.Attendees, so a change to Application.Attendees can break Application.Attendees.Commands.CheckInAttendeeById, while a change to Application.Attendees.Commands.CheckInAttendeeById can't break Application.Attendees.
- Position
- Below the diagonal: Application.Attendees.Commands.CheckInAttendeeById uses a module listed above it, which is the healthy direction.
9→4 Application.Attendees.Commands.CheckInAttendeeById uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Commands.CheckInAttendeeById uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Attendees.Commands.CheckInAttendeeById.CheckInAttendeeCommandHandler→ConferencePlanner.Application.Common.Interfaces.IAttendeeRepository
- Direction
- Application.Attendees.Commands.CheckInAttendeeById uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Attendees.Commands.CheckInAttendeeById, while a change to Application.Attendees.Commands.CheckInAttendeeById can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Attendees.Commands.CheckInAttendeeById uses a module listed above it, which is the healthy direction.
10→1 Application.Attendees.Commands.RegisterAttendee uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Commands.RegisterAttendee uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Attendees.Commands.RegisterAttendee.RegisterAttendeePayload→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Attendees.Commands.RegisterAttendee uses Domain.Common, so a change to Domain.Common can break Application.Attendees.Commands.RegisterAttendee, while a change to Application.Attendees.Commands.RegisterAttendee can't break Domain.Common.
- Position
- Below the diagonal: Application.Attendees.Commands.RegisterAttendee uses a module listed above it, which is the healthy direction.
10→2 Application.Attendees.Commands.RegisterAttendee uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Attendees.Commands.RegisterAttendee uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Attendees.Commands.RegisterAttendee.RegisterAttendeeCommandHandler→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.Application.Attendees.Commands.RegisterAttendee.RegisterAttendeePayload→ConferencePlanner.Domain.Entities.Attendee
- Direction
- Application.Attendees.Commands.RegisterAttendee uses Domain.Entities, so a change to Domain.Entities can break Application.Attendees.Commands.RegisterAttendee, while a change to Application.Attendees.Commands.RegisterAttendee can't break Domain.Entities.
- Position
- Below the diagonal: Application.Attendees.Commands.RegisterAttendee uses a module listed above it, which is the healthy direction.
10→3 Application.Attendees.Commands.RegisterAttendee uses Application.Attendees✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Commands.RegisterAttendee uses a type in Application.Attendees.
- The types involved
ConferencePlanner.Application.Attendees.Commands.RegisterAttendee.RegisterAttendeePayload→ConferencePlanner.Application.Attendees.AttendeePayloadBase
- Direction
- Application.Attendees.Commands.RegisterAttendee uses Application.Attendees, so a change to Application.Attendees can break Application.Attendees.Commands.RegisterAttendee, while a change to Application.Attendees.Commands.RegisterAttendee can't break Application.Attendees.
- Position
- Below the diagonal: Application.Attendees.Commands.RegisterAttendee uses a module listed above it, which is the healthy direction.
10→4 Application.Attendees.Commands.RegisterAttendee uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Commands.RegisterAttendee uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Attendees.Commands.RegisterAttendee.RegisterAttendeeCommandHandler→ConferencePlanner.Application.Common.Interfaces.IAttendeeRepository
- Direction
- Application.Attendees.Commands.RegisterAttendee uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Attendees.Commands.RegisterAttendee, while a change to Application.Attendees.Commands.RegisterAttendee can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Attendees.Commands.RegisterAttendee uses a module listed above it, which is the healthy direction.
11→2 Application.Attendees.Queries.GetAttendeeById uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Queries.GetAttendeeById uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Attendees.Queries.GetAttendeeById.GetAttendeeByIdQueryHandler→ConferencePlanner.Domain.Entities.Attendee
- Direction
- Application.Attendees.Queries.GetAttendeeById uses Domain.Entities, so a change to Domain.Entities can break Application.Attendees.Queries.GetAttendeeById, while a change to Application.Attendees.Queries.GetAttendeeById can't break Domain.Entities.
- Position
- Below the diagonal: Application.Attendees.Queries.GetAttendeeById uses a module listed above it, which is the healthy direction.
11→4 Application.Attendees.Queries.GetAttendeeById uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Queries.GetAttendeeById uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Attendees.Queries.GetAttendeeById.GetAttendeeByIdQueryHandler→ConferencePlanner.Application.Common.Interfaces.IAttendeeByIdDataLoader
- Direction
- Application.Attendees.Queries.GetAttendeeById uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Attendees.Queries.GetAttendeeById, while a change to Application.Attendees.Queries.GetAttendeeById can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Attendees.Queries.GetAttendeeById uses a module listed above it, which is the healthy direction.
12→2 Application.Attendees.Queries.GetAttendees uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Queries.GetAttendees uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Attendees.Queries.GetAttendees.GetAttendeesQueryHandler→ConferencePlanner.Domain.Entities.Attendee
- Direction
- Application.Attendees.Queries.GetAttendees uses Domain.Entities, so a change to Domain.Entities can break Application.Attendees.Queries.GetAttendees, while a change to Application.Attendees.Queries.GetAttendees can't break Domain.Entities.
- Position
- Below the diagonal: Application.Attendees.Queries.GetAttendees uses a module listed above it, which is the healthy direction.
12→4 Application.Attendees.Queries.GetAttendees uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Queries.GetAttendees uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Attendees.Queries.GetAttendees.GetAttendeesQueryHandler→ConferencePlanner.Application.Common.Interfaces.IAttendeeRepository
- Direction
- Application.Attendees.Queries.GetAttendees uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Attendees.Queries.GetAttendees, while a change to Application.Attendees.Queries.GetAttendees can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Attendees.Queries.GetAttendees uses a module listed above it, which is the healthy direction.
13→2 Application.Attendees.Queries.GetAttendeesByIds uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Queries.GetAttendeesByIds uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Attendees.Queries.GetAttendeesByIds.GetAttendeesByIdsQueryHandler→ConferencePlanner.Domain.Entities.Attendee
- Direction
- Application.Attendees.Queries.GetAttendeesByIds uses Domain.Entities, so a change to Domain.Entities can break Application.Attendees.Queries.GetAttendeesByIds, while a change to Application.Attendees.Queries.GetAttendeesByIds can't break Domain.Entities.
- Position
- Below the diagonal: Application.Attendees.Queries.GetAttendeesByIds uses a module listed above it, which is the healthy direction.
13→4 Application.Attendees.Queries.GetAttendeesByIds uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Queries.GetAttendeesByIds uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Attendees.Queries.GetAttendeesByIds.GetAttendeesByIdsQueryHandler→ConferencePlanner.Application.Common.Interfaces.IAttendeeByIdDataLoader
- Direction
- Application.Attendees.Queries.GetAttendeesByIds uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Attendees.Queries.GetAttendeesByIds, while a change to Application.Attendees.Queries.GetAttendeesByIds can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Attendees.Queries.GetAttendeesByIds uses a module listed above it, which is the healthy direction.
14→2 Application.Attendees.Queries.GetAttendeesBySessionId uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Queries.GetAttendeesBySessionId uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Attendees.Queries.GetAttendeesBySessionId.GetAttendeesBySessionIdQueryHandler→ConferencePlanner.Domain.Entities.Attendee
- Direction
- Application.Attendees.Queries.GetAttendeesBySessionId uses Domain.Entities, so a change to Domain.Entities can break Application.Attendees.Queries.GetAttendeesBySessionId, while a change to Application.Attendees.Queries.GetAttendeesBySessionId can't break Domain.Entities.
- Position
- Below the diagonal: Application.Attendees.Queries.GetAttendeesBySessionId uses a module listed above it, which is the healthy direction.
14→4 Application.Attendees.Queries.GetAttendeesBySessionId uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Attendees.Queries.GetAttendeesBySessionId uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Attendees.Queries.GetAttendeesBySessionId.GetAttendeesBySessionIdQueryHandler→ConferencePlanner.Application.Common.Interfaces.ISessionRepository
- Direction
- Application.Attendees.Queries.GetAttendeesBySessionId uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Attendees.Queries.GetAttendeesBySessionId, while a change to Application.Attendees.Queries.GetAttendeesBySessionId can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Attendees.Queries.GetAttendeesBySessionId uses a module listed above it, which is the healthy direction.
15→1 Application.Sessions.Commands.AddSession uses Domain.Common✕
- Connections
- 2 pairs of types, where a type in Application.Sessions.Commands.AddSession uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Sessions.Commands.AddSession.AddSessionPayload→ConferencePlanner.Domain.Common.PayloadConferencePlanner.Application.Sessions.Commands.AddSession.AddSessionPayload→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Sessions.Commands.AddSession uses Domain.Common, so a change to Domain.Common can break Application.Sessions.Commands.AddSession, while a change to Application.Sessions.Commands.AddSession can't break Domain.Common.
- Position
- Below the diagonal: Application.Sessions.Commands.AddSession uses a module listed above it, which is the healthy direction.
15→2 Application.Sessions.Commands.AddSession uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Sessions.Commands.AddSession uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Sessions.Commands.AddSession.AddSessionCommandHandler→ConferencePlanner.Domain.Entities.SessionConferencePlanner.Application.Sessions.Commands.AddSession.AddSessionPayload→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Sessions.Commands.AddSession uses Domain.Entities, so a change to Domain.Entities can break Application.Sessions.Commands.AddSession, while a change to Application.Sessions.Commands.AddSession can't break Domain.Entities.
- Position
- Below the diagonal: Application.Sessions.Commands.AddSession uses a module listed above it, which is the healthy direction.
15→4 Application.Sessions.Commands.AddSession uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Commands.AddSession uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Sessions.Commands.AddSession.AddSessionCommandHandler→ConferencePlanner.Application.Common.Interfaces.ISessionRepository
- Direction
- Application.Sessions.Commands.AddSession uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Sessions.Commands.AddSession, while a change to Application.Sessions.Commands.AddSession can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Sessions.Commands.AddSession uses a module listed above it, which is the healthy direction.
16→1 Application.Sessions.Commands.RenameSession uses Domain.Common✕
- Connections
- 2 pairs of types, where a type in Application.Sessions.Commands.RenameSession uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Sessions.Commands.RenameSession.RenameSessionPayload→ConferencePlanner.Domain.Common.PayloadConferencePlanner.Application.Sessions.Commands.RenameSession.RenameSessionPayload→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Sessions.Commands.RenameSession uses Domain.Common, so a change to Domain.Common can break Application.Sessions.Commands.RenameSession, while a change to Application.Sessions.Commands.RenameSession can't break Domain.Common.
- Position
- Below the diagonal: Application.Sessions.Commands.RenameSession uses a module listed above it, which is the healthy direction.
16→2 Application.Sessions.Commands.RenameSession uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Sessions.Commands.RenameSession uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Sessions.Commands.RenameSession.RenameSessionCommandHandler→ConferencePlanner.Domain.Entities.SessionConferencePlanner.Application.Sessions.Commands.RenameSession.RenameSessionPayload→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Sessions.Commands.RenameSession uses Domain.Entities, so a change to Domain.Entities can break Application.Sessions.Commands.RenameSession, while a change to Application.Sessions.Commands.RenameSession can't break Domain.Entities.
- Position
- Below the diagonal: Application.Sessions.Commands.RenameSession uses a module listed above it, which is the healthy direction.
16→4 Application.Sessions.Commands.RenameSession uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Commands.RenameSession uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Sessions.Commands.RenameSession.RenameSessionCommandHandler→ConferencePlanner.Application.Common.Interfaces.ISessionRepository
- Direction
- Application.Sessions.Commands.RenameSession uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Sessions.Commands.RenameSession, while a change to Application.Sessions.Commands.RenameSession can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Sessions.Commands.RenameSession uses a module listed above it, which is the healthy direction.
17→1 Application.Sessions.Commands.ScheduleSession uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Commands.ScheduleSession uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Sessions.Commands.ScheduleSession.ScheduleSessionPayload→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Sessions.Commands.ScheduleSession uses Domain.Common, so a change to Domain.Common can break Application.Sessions.Commands.ScheduleSession, while a change to Application.Sessions.Commands.ScheduleSession can't break Domain.Common.
- Position
- Below the diagonal: Application.Sessions.Commands.ScheduleSession uses a module listed above it, which is the healthy direction.
17→2 Application.Sessions.Commands.ScheduleSession uses Domain.Entities✕
- Connections
- 4 pairs of types, where a type in Application.Sessions.Commands.ScheduleSession uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Sessions.Commands.ScheduleSession.ScheduleSessionCommandHandler→ConferencePlanner.Domain.Entities.SessionConferencePlanner.Application.Sessions.Commands.ScheduleSession.ScheduleSessionPayload→ConferencePlanner.Domain.Entities.SessionConferencePlanner.Application.Sessions.Commands.ScheduleSession.ScheduleSessionPayload→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.Application.Sessions.Commands.ScheduleSession.ScheduleSessionPayload→ConferencePlanner.Domain.Entities.Track
- Direction
- Application.Sessions.Commands.ScheduleSession uses Domain.Entities, so a change to Domain.Entities can break Application.Sessions.Commands.ScheduleSession, while a change to Application.Sessions.Commands.ScheduleSession can't break Domain.Entities.
- Position
- Below the diagonal: Application.Sessions.Commands.ScheduleSession uses a module listed above it, which is the healthy direction.
17→4 Application.Sessions.Commands.ScheduleSession uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Commands.ScheduleSession uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Sessions.Commands.ScheduleSession.ScheduleSessionCommandHandler→ConferencePlanner.Application.Common.Interfaces.ISessionRepository
- Direction
- Application.Sessions.Commands.ScheduleSession uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Sessions.Commands.ScheduleSession, while a change to Application.Sessions.Commands.ScheduleSession can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Sessions.Commands.ScheduleSession uses a module listed above it, which is the healthy direction.
17→5 Application.Sessions.Commands.ScheduleSession uses Application.Sessions✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Commands.ScheduleSession uses a type in Application.Sessions.
- The types involved
ConferencePlanner.Application.Sessions.Commands.ScheduleSession.ScheduleSessionPayload→ConferencePlanner.Application.Sessions.SessionPayloadBase
- Direction
- Application.Sessions.Commands.ScheduleSession uses Application.Sessions, so a change to Application.Sessions can break Application.Sessions.Commands.ScheduleSession, while a change to Application.Sessions.Commands.ScheduleSession can't break Application.Sessions.
- Position
- Below the diagonal: Application.Sessions.Commands.ScheduleSession uses a module listed above it, which is the healthy direction.
18→2 Application.Sessions.Queries.GetSessionById uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessionById uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessionById.GetSessionByIdQueryHandler→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Sessions.Queries.GetSessionById uses Domain.Entities, so a change to Domain.Entities can break Application.Sessions.Queries.GetSessionById, while a change to Application.Sessions.Queries.GetSessionById can't break Domain.Entities.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessionById uses a module listed above it, which is the healthy direction.
18→4 Application.Sessions.Queries.GetSessionById uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessionById uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessionById.GetSessionByIdQueryHandler→ConferencePlanner.Application.Common.Interfaces.ISessionByIdDataLoader
- Direction
- Application.Sessions.Queries.GetSessionById uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Sessions.Queries.GetSessionById, while a change to Application.Sessions.Queries.GetSessionById can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessionById uses a module listed above it, which is the healthy direction.
19→2 Application.Sessions.Queries.GetSessions uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessions uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessions.GetSessionsQueryHandler→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Sessions.Queries.GetSessions uses Domain.Entities, so a change to Domain.Entities can break Application.Sessions.Queries.GetSessions, while a change to Application.Sessions.Queries.GetSessions can't break Domain.Entities.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessions uses a module listed above it, which is the healthy direction.
19→4 Application.Sessions.Queries.GetSessions uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessions uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessions.GetSessionsQueryHandler→ConferencePlanner.Application.Common.Interfaces.ISessionRepository
- Direction
- Application.Sessions.Queries.GetSessions uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Sessions.Queries.GetSessions, while a change to Application.Sessions.Queries.GetSessions can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessions uses a module listed above it, which is the healthy direction.
20→2 Application.Sessions.Queries.GetSessionsByAttendee uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessionsByAttendee uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessionsByAttendee.GetSessionsByAttendeeQueryHandler→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Sessions.Queries.GetSessionsByAttendee uses Domain.Entities, so a change to Domain.Entities can break Application.Sessions.Queries.GetSessionsByAttendee, while a change to Application.Sessions.Queries.GetSessionsByAttendee can't break Domain.Entities.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessionsByAttendee uses a module listed above it, which is the healthy direction.
20→4 Application.Sessions.Queries.GetSessionsByAttendee uses Application.Common.Interfaces✕
- Connections
- 2 pairs of types, where a type in Application.Sessions.Queries.GetSessionsByAttendee uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessionsByAttendee.GetSessionsByAttendeeQueryHandler→ConferencePlanner.Application.Common.Interfaces.IAttendeeRepositoryConferencePlanner.Application.Sessions.Queries.GetSessionsByAttendee.GetSessionsByAttendeeQueryHandler→ConferencePlanner.Application.Common.Interfaces.ISessionByIdDataLoader
- Direction
- Application.Sessions.Queries.GetSessionsByAttendee uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Sessions.Queries.GetSessionsByAttendee, while a change to Application.Sessions.Queries.GetSessionsByAttendee can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessionsByAttendee uses a module listed above it, which is the healthy direction.
21→2 Application.Sessions.Queries.GetSessionsByIds uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessionsByIds uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessionsByIds.GetSessionsByIdsQueryHandler→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Sessions.Queries.GetSessionsByIds uses Domain.Entities, so a change to Domain.Entities can break Application.Sessions.Queries.GetSessionsByIds, while a change to Application.Sessions.Queries.GetSessionsByIds can't break Domain.Entities.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessionsByIds uses a module listed above it, which is the healthy direction.
21→4 Application.Sessions.Queries.GetSessionsByIds uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessionsByIds uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessionsByIds.GetSessionsByIdsQueryHandler→ConferencePlanner.Application.Common.Interfaces.ISessionByIdDataLoader
- Direction
- Application.Sessions.Queries.GetSessionsByIds uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Sessions.Queries.GetSessionsByIds, while a change to Application.Sessions.Queries.GetSessionsByIds can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessionsByIds uses a module listed above it, which is the healthy direction.
22→2 Application.Sessions.Queries.GetSessionsBySpeakerId uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessionsBySpeakerId uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessionsBySpeakerId.GetSessionsBySpeakerIdQueryHandler→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Sessions.Queries.GetSessionsBySpeakerId uses Domain.Entities, so a change to Domain.Entities can break Application.Sessions.Queries.GetSessionsBySpeakerId, while a change to Application.Sessions.Queries.GetSessionsBySpeakerId can't break Domain.Entities.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessionsBySpeakerId uses a module listed above it, which is the healthy direction.
22→4 Application.Sessions.Queries.GetSessionsBySpeakerId uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessionsBySpeakerId uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessionsBySpeakerId.GetSessionsBySpeakerIdQueryHandler→ConferencePlanner.Application.Common.Interfaces.ISessionBySpeakerIdDataLoader
- Direction
- Application.Sessions.Queries.GetSessionsBySpeakerId uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Sessions.Queries.GetSessionsBySpeakerId, while a change to Application.Sessions.Queries.GetSessionsBySpeakerId can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessionsBySpeakerId uses a module listed above it, which is the healthy direction.
23→2 Application.Sessions.Queries.GetSessionsByTrack uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessionsByTrack uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessionsByTrack.GetSessionsByTrackQueryHandler→ConferencePlanner.Domain.Entities.Session
- Direction
- Application.Sessions.Queries.GetSessionsByTrack uses Domain.Entities, so a change to Domain.Entities can break Application.Sessions.Queries.GetSessionsByTrack, while a change to Application.Sessions.Queries.GetSessionsByTrack can't break Domain.Entities.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessionsByTrack uses a module listed above it, which is the healthy direction.
23→4 Application.Sessions.Queries.GetSessionsByTrack uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Sessions.Queries.GetSessionsByTrack uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Sessions.Queries.GetSessionsByTrack.GetSessionsByTrackQueryHandler→ConferencePlanner.Application.Common.Interfaces.ITrackRepository
- Direction
- Application.Sessions.Queries.GetSessionsByTrack uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Sessions.Queries.GetSessionsByTrack, while a change to Application.Sessions.Queries.GetSessionsByTrack can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Sessions.Queries.GetSessionsByTrack uses a module listed above it, which is the healthy direction.
24→1 Application.Speakers.Commands.AddSpeaker uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Commands.AddSpeaker uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Speakers.Commands.AddSpeaker.AddSpeakerPayload→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Speakers.Commands.AddSpeaker uses Domain.Common, so a change to Domain.Common can break Application.Speakers.Commands.AddSpeaker, while a change to Application.Speakers.Commands.AddSpeaker can't break Domain.Common.
- Position
- Below the diagonal: Application.Speakers.Commands.AddSpeaker uses a module listed above it, which is the healthy direction.
24→2 Application.Speakers.Commands.AddSpeaker uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Speakers.Commands.AddSpeaker uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Speakers.Commands.AddSpeaker.AddSpeakerCommandHandler→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.Application.Speakers.Commands.AddSpeaker.AddSpeakerPayload→ConferencePlanner.Domain.Entities.Speaker
- Direction
- Application.Speakers.Commands.AddSpeaker uses Domain.Entities, so a change to Domain.Entities can break Application.Speakers.Commands.AddSpeaker, while a change to Application.Speakers.Commands.AddSpeaker can't break Domain.Entities.
- Position
- Below the diagonal: Application.Speakers.Commands.AddSpeaker uses a module listed above it, which is the healthy direction.
24→4 Application.Speakers.Commands.AddSpeaker uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Commands.AddSpeaker uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Speakers.Commands.AddSpeaker.AddSpeakerCommandHandler→ConferencePlanner.Application.Common.Interfaces.ISpeakerRepository
- Direction
- Application.Speakers.Commands.AddSpeaker uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Speakers.Commands.AddSpeaker, while a change to Application.Speakers.Commands.AddSpeaker can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Speakers.Commands.AddSpeaker uses a module listed above it, which is the healthy direction.
24→6 Application.Speakers.Commands.AddSpeaker uses Application.Speakers✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Commands.AddSpeaker uses a type in Application.Speakers.
- The types involved
ConferencePlanner.Application.Speakers.Commands.AddSpeaker.AddSpeakerPayload→ConferencePlanner.Application.Speakers.SpeakerPayloadBase
- Direction
- Application.Speakers.Commands.AddSpeaker uses Application.Speakers, so a change to Application.Speakers can break Application.Speakers.Commands.AddSpeaker, while a change to Application.Speakers.Commands.AddSpeaker can't break Application.Speakers.
- Position
- Below the diagonal: Application.Speakers.Commands.AddSpeaker uses a module listed above it, which is the healthy direction.
25→1 Application.Speakers.Commands.ModifySpeaker uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Commands.ModifySpeaker uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Speakers.Commands.ModifySpeaker.ModifySpeakerPayload→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Speakers.Commands.ModifySpeaker uses Domain.Common, so a change to Domain.Common can break Application.Speakers.Commands.ModifySpeaker, while a change to Application.Speakers.Commands.ModifySpeaker can't break Domain.Common.
- Position
- Below the diagonal: Application.Speakers.Commands.ModifySpeaker uses a module listed above it, which is the healthy direction.
25→2 Application.Speakers.Commands.ModifySpeaker uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Speakers.Commands.ModifySpeaker uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Speakers.Commands.ModifySpeaker.ModifySpeakerCommandHandler→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.Application.Speakers.Commands.ModifySpeaker.ModifySpeakerPayload→ConferencePlanner.Domain.Entities.Speaker
- Direction
- Application.Speakers.Commands.ModifySpeaker uses Domain.Entities, so a change to Domain.Entities can break Application.Speakers.Commands.ModifySpeaker, while a change to Application.Speakers.Commands.ModifySpeaker can't break Domain.Entities.
- Position
- Below the diagonal: Application.Speakers.Commands.ModifySpeaker uses a module listed above it, which is the healthy direction.
25→4 Application.Speakers.Commands.ModifySpeaker uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Commands.ModifySpeaker uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Speakers.Commands.ModifySpeaker.ModifySpeakerCommandHandler→ConferencePlanner.Application.Common.Interfaces.ISpeakerRepository
- Direction
- Application.Speakers.Commands.ModifySpeaker uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Speakers.Commands.ModifySpeaker, while a change to Application.Speakers.Commands.ModifySpeaker can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Speakers.Commands.ModifySpeaker uses a module listed above it, which is the healthy direction.
25→6 Application.Speakers.Commands.ModifySpeaker uses Application.Speakers✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Commands.ModifySpeaker uses a type in Application.Speakers.
- The types involved
ConferencePlanner.Application.Speakers.Commands.ModifySpeaker.ModifySpeakerPayload→ConferencePlanner.Application.Speakers.SpeakerPayloadBase
- Direction
- Application.Speakers.Commands.ModifySpeaker uses Application.Speakers, so a change to Application.Speakers can break Application.Speakers.Commands.ModifySpeaker, while a change to Application.Speakers.Commands.ModifySpeaker can't break Application.Speakers.
- Position
- Below the diagonal: Application.Speakers.Commands.ModifySpeaker uses a module listed above it, which is the healthy direction.
26→2 Application.Speakers.Queries.GetSessionSpeakers uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Queries.GetSessionSpeakers uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Speakers.Queries.GetSessionSpeakers.GetSessionSpeakersQueryHandler→ConferencePlanner.Domain.Entities.SessionSpeaker
- Direction
- Application.Speakers.Queries.GetSessionSpeakers uses Domain.Entities, so a change to Domain.Entities can break Application.Speakers.Queries.GetSessionSpeakers, while a change to Application.Speakers.Queries.GetSessionSpeakers can't break Domain.Entities.
- Position
- Below the diagonal: Application.Speakers.Queries.GetSessionSpeakers uses a module listed above it, which is the healthy direction.
26→4 Application.Speakers.Queries.GetSessionSpeakers uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Queries.GetSessionSpeakers uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Speakers.Queries.GetSessionSpeakers.GetSessionSpeakersQueryHandler→ConferencePlanner.Application.Common.Interfaces.ISpeakerRepository
- Direction
- Application.Speakers.Queries.GetSessionSpeakers uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Speakers.Queries.GetSessionSpeakers, while a change to Application.Speakers.Queries.GetSessionSpeakers can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Speakers.Queries.GetSessionSpeakers uses a module listed above it, which is the healthy direction.
27→2 Application.Speakers.Queries.GetSpeakerById uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Queries.GetSpeakerById uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Speakers.Queries.GetSpeakerById.GetSpeakerByIdQueryHandler→ConferencePlanner.Domain.Entities.Speaker
- Direction
- Application.Speakers.Queries.GetSpeakerById uses Domain.Entities, so a change to Domain.Entities can break Application.Speakers.Queries.GetSpeakerById, while a change to Application.Speakers.Queries.GetSpeakerById can't break Domain.Entities.
- Position
- Below the diagonal: Application.Speakers.Queries.GetSpeakerById uses a module listed above it, which is the healthy direction.
27→4 Application.Speakers.Queries.GetSpeakerById uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Queries.GetSpeakerById uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Speakers.Queries.GetSpeakerById.GetSpeakerByIdQueryHandler→ConferencePlanner.Application.Common.Interfaces.ISpeakerByIdDataLoader
- Direction
- Application.Speakers.Queries.GetSpeakerById uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Speakers.Queries.GetSpeakerById, while a change to Application.Speakers.Queries.GetSpeakerById can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Speakers.Queries.GetSpeakerById uses a module listed above it, which is the healthy direction.
28→2 Application.Speakers.Queries.GetSpeakers uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Queries.GetSpeakers uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Speakers.Queries.GetSpeakers.GetSpeakersQueryHandler→ConferencePlanner.Domain.Entities.Speaker
- Direction
- Application.Speakers.Queries.GetSpeakers uses Domain.Entities, so a change to Domain.Entities can break Application.Speakers.Queries.GetSpeakers, while a change to Application.Speakers.Queries.GetSpeakers can't break Domain.Entities.
- Position
- Below the diagonal: Application.Speakers.Queries.GetSpeakers uses a module listed above it, which is the healthy direction.
28→4 Application.Speakers.Queries.GetSpeakers uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Queries.GetSpeakers uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Speakers.Queries.GetSpeakers.GetSpeakersQueryHandler→ConferencePlanner.Application.Common.Interfaces.ISpeakerRepository
- Direction
- Application.Speakers.Queries.GetSpeakers uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Speakers.Queries.GetSpeakers, while a change to Application.Speakers.Queries.GetSpeakers can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Speakers.Queries.GetSpeakers uses a module listed above it, which is the healthy direction.
29→2 Application.Speakers.Queries.GetSpeakersByIds uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Queries.GetSpeakersByIds uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Speakers.Queries.GetSpeakersByIds.GetSpeakersByIdsQueryHandler→ConferencePlanner.Domain.Entities.Speaker
- Direction
- Application.Speakers.Queries.GetSpeakersByIds uses Domain.Entities, so a change to Domain.Entities can break Application.Speakers.Queries.GetSpeakersByIds, while a change to Application.Speakers.Queries.GetSpeakersByIds can't break Domain.Entities.
- Position
- Below the diagonal: Application.Speakers.Queries.GetSpeakersByIds uses a module listed above it, which is the healthy direction.
29→4 Application.Speakers.Queries.GetSpeakersByIds uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Speakers.Queries.GetSpeakersByIds uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Speakers.Queries.GetSpeakersByIds.GetSpeakersByIdsQueryHandler→ConferencePlanner.Application.Common.Interfaces.ISpeakerByIdDataLoader
- Direction
- Application.Speakers.Queries.GetSpeakersByIds uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Speakers.Queries.GetSpeakersByIds, while a change to Application.Speakers.Queries.GetSpeakersByIds can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Speakers.Queries.GetSpeakersByIds uses a module listed above it, which is the healthy direction.
30→1 Application.Tracks.Commands.AddTrack uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Commands.AddTrack uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Tracks.Commands.AddTrack.AddTrackPayload→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Tracks.Commands.AddTrack uses Domain.Common, so a change to Domain.Common can break Application.Tracks.Commands.AddTrack, while a change to Application.Tracks.Commands.AddTrack can't break Domain.Common.
- Position
- Below the diagonal: Application.Tracks.Commands.AddTrack uses a module listed above it, which is the healthy direction.
30→2 Application.Tracks.Commands.AddTrack uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Tracks.Commands.AddTrack uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Tracks.Commands.AddTrack.AddTrackCommandHandler→ConferencePlanner.Domain.Entities.TrackConferencePlanner.Application.Tracks.Commands.AddTrack.AddTrackPayload→ConferencePlanner.Domain.Entities.Track
- Direction
- Application.Tracks.Commands.AddTrack uses Domain.Entities, so a change to Domain.Entities can break Application.Tracks.Commands.AddTrack, while a change to Application.Tracks.Commands.AddTrack can't break Domain.Entities.
- Position
- Below the diagonal: Application.Tracks.Commands.AddTrack uses a module listed above it, which is the healthy direction.
30→4 Application.Tracks.Commands.AddTrack uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Commands.AddTrack uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Tracks.Commands.AddTrack.AddTrackCommandHandler→ConferencePlanner.Application.Common.Interfaces.ITrackRepository
- Direction
- Application.Tracks.Commands.AddTrack uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Tracks.Commands.AddTrack, while a change to Application.Tracks.Commands.AddTrack can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Tracks.Commands.AddTrack uses a module listed above it, which is the healthy direction.
30→7 Application.Tracks.Commands.AddTrack uses Application.Tracks✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Commands.AddTrack uses a type in Application.Tracks.
- The types involved
ConferencePlanner.Application.Tracks.Commands.AddTrack.AddTrackPayload→ConferencePlanner.Application.Tracks.TrackPayloadBase
- Direction
- Application.Tracks.Commands.AddTrack uses Application.Tracks, so a change to Application.Tracks can break Application.Tracks.Commands.AddTrack, while a change to Application.Tracks.Commands.AddTrack can't break Application.Tracks.
- Position
- Below the diagonal: Application.Tracks.Commands.AddTrack uses a module listed above it, which is the healthy direction.
31→1 Application.Tracks.Commands.RenameTrack uses Domain.Common✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Commands.RenameTrack uses a type in Domain.Common.
- The types involved
ConferencePlanner.Application.Tracks.Commands.RenameTrack.RenameTrackPayload→ConferencePlanner.Domain.Common.UserError
- Direction
- Application.Tracks.Commands.RenameTrack uses Domain.Common, so a change to Domain.Common can break Application.Tracks.Commands.RenameTrack, while a change to Application.Tracks.Commands.RenameTrack can't break Domain.Common.
- Position
- Below the diagonal: Application.Tracks.Commands.RenameTrack uses a module listed above it, which is the healthy direction.
31→2 Application.Tracks.Commands.RenameTrack uses Domain.Entities✕
- Connections
- 2 pairs of types, where a type in Application.Tracks.Commands.RenameTrack uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Tracks.Commands.RenameTrack.RenameTrackCommandHandler→ConferencePlanner.Domain.Entities.TrackConferencePlanner.Application.Tracks.Commands.RenameTrack.RenameTrackPayload→ConferencePlanner.Domain.Entities.Track
- Direction
- Application.Tracks.Commands.RenameTrack uses Domain.Entities, so a change to Domain.Entities can break Application.Tracks.Commands.RenameTrack, while a change to Application.Tracks.Commands.RenameTrack can't break Domain.Entities.
- Position
- Below the diagonal: Application.Tracks.Commands.RenameTrack uses a module listed above it, which is the healthy direction.
31→4 Application.Tracks.Commands.RenameTrack uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Commands.RenameTrack uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Tracks.Commands.RenameTrack.RenameTrackCommandHandler→ConferencePlanner.Application.Common.Interfaces.ITrackRepository
- Direction
- Application.Tracks.Commands.RenameTrack uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Tracks.Commands.RenameTrack, while a change to Application.Tracks.Commands.RenameTrack can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Tracks.Commands.RenameTrack uses a module listed above it, which is the healthy direction.
31→7 Application.Tracks.Commands.RenameTrack uses Application.Tracks✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Commands.RenameTrack uses a type in Application.Tracks.
- The types involved
ConferencePlanner.Application.Tracks.Commands.RenameTrack.RenameTrackPayload→ConferencePlanner.Application.Tracks.TrackPayloadBase
- Direction
- Application.Tracks.Commands.RenameTrack uses Application.Tracks, so a change to Application.Tracks can break Application.Tracks.Commands.RenameTrack, while a change to Application.Tracks.Commands.RenameTrack can't break Application.Tracks.
- Position
- Below the diagonal: Application.Tracks.Commands.RenameTrack uses a module listed above it, which is the healthy direction.
32→2 Application.Tracks.Queries.GetTrackById uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Queries.GetTrackById uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Tracks.Queries.GetTrackById.GetTrackByIdQueryHandler→ConferencePlanner.Domain.Entities.Track
- Direction
- Application.Tracks.Queries.GetTrackById uses Domain.Entities, so a change to Domain.Entities can break Application.Tracks.Queries.GetTrackById, while a change to Application.Tracks.Queries.GetTrackById can't break Domain.Entities.
- Position
- Below the diagonal: Application.Tracks.Queries.GetTrackById uses a module listed above it, which is the healthy direction.
32→4 Application.Tracks.Queries.GetTrackById uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Queries.GetTrackById uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Tracks.Queries.GetTrackById.GetTrackByIdQueryHandler→ConferencePlanner.Application.Common.Interfaces.ITrackByIdDataLoader
- Direction
- Application.Tracks.Queries.GetTrackById uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Tracks.Queries.GetTrackById, while a change to Application.Tracks.Queries.GetTrackById can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Tracks.Queries.GetTrackById uses a module listed above it, which is the healthy direction.
33→2 Application.Tracks.Queries.GetTrackByName uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Queries.GetTrackByName uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Tracks.Queries.GetTrackByName.GetTrackByNameQueryHandler→ConferencePlanner.Domain.Entities.Track
- Direction
- Application.Tracks.Queries.GetTrackByName uses Domain.Entities, so a change to Domain.Entities can break Application.Tracks.Queries.GetTrackByName, while a change to Application.Tracks.Queries.GetTrackByName can't break Domain.Entities.
- Position
- Below the diagonal: Application.Tracks.Queries.GetTrackByName uses a module listed above it, which is the healthy direction.
33→4 Application.Tracks.Queries.GetTrackByName uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Queries.GetTrackByName uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Tracks.Queries.GetTrackByName.GetTrackByNameQueryHandler→ConferencePlanner.Application.Common.Interfaces.ITrackRepository
- Direction
- Application.Tracks.Queries.GetTrackByName uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Tracks.Queries.GetTrackByName, while a change to Application.Tracks.Queries.GetTrackByName can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Tracks.Queries.GetTrackByName uses a module listed above it, which is the healthy direction.
34→2 Application.Tracks.Queries.GetTracksByIds uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Queries.GetTracksByIds uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Tracks.Queries.GetTracksByIds.GetTracksByIdsQueryHandler→ConferencePlanner.Domain.Entities.Track
- Direction
- Application.Tracks.Queries.GetTracksByIds uses Domain.Entities, so a change to Domain.Entities can break Application.Tracks.Queries.GetTracksByIds, while a change to Application.Tracks.Queries.GetTracksByIds can't break Domain.Entities.
- Position
- Below the diagonal: Application.Tracks.Queries.GetTracksByIds uses a module listed above it, which is the healthy direction.
34→4 Application.Tracks.Queries.GetTracksByIds uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Queries.GetTracksByIds uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Tracks.Queries.GetTracksByIds.GetTracksByIdsQueryHandler→ConferencePlanner.Application.Common.Interfaces.ITrackByIdDataLoader
- Direction
- Application.Tracks.Queries.GetTracksByIds uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Tracks.Queries.GetTracksByIds, while a change to Application.Tracks.Queries.GetTracksByIds can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Tracks.Queries.GetTracksByIds uses a module listed above it, which is the healthy direction.
35→2 Application.Tracks.Queries.GetTracksByNames uses Domain.Entities✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Queries.GetTracksByNames uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Application.Tracks.Queries.GetTracksByNames.GetTracksByNamesQueryHandler→ConferencePlanner.Domain.Entities.Track
- Direction
- Application.Tracks.Queries.GetTracksByNames uses Domain.Entities, so a change to Domain.Entities can break Application.Tracks.Queries.GetTracksByNames, while a change to Application.Tracks.Queries.GetTracksByNames can't break Domain.Entities.
- Position
- Below the diagonal: Application.Tracks.Queries.GetTracksByNames uses a module listed above it, which is the healthy direction.
35→4 Application.Tracks.Queries.GetTracksByNames uses Application.Common.Interfaces✕
- Connections
- 1 pair of types, where a type in Application.Tracks.Queries.GetTracksByNames uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Application.Tracks.Queries.GetTracksByNames.GetTracksByNamesQueryHandler→ConferencePlanner.Application.Common.Interfaces.ITrackRepository
- Direction
- Application.Tracks.Queries.GetTracksByNames uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Application.Tracks.Queries.GetTracksByNames, while a change to Application.Tracks.Queries.GetTracksByNames can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Application.Tracks.Queries.GetTracksByNames uses a module listed above it, which is the healthy direction.
36→2 Infrastructure.Persistence.DataLoaders uses Domain.Entities✕
- Connections
- 6 pairs of types, where a type in Infrastructure.Persistence.DataLoaders uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Infrastructure.Persistence.DataLoaders.AttendeeByIdDataLoader→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.Infrastructure.Persistence.DataLoaders.SessionByIdDataLoader→ConferencePlanner.Domain.Entities.SessionConferencePlanner.Infrastructure.Persistence.DataLoaders.SessionBySpeakerIdDataLoader→ConferencePlanner.Domain.Entities.SessionConferencePlanner.Infrastructure.Persistence.DataLoaders.SpeakerByIdDataLoader→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.Infrastructure.Persistence.DataLoaders.SpeakerBySessionIdDataLoader→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.Infrastructure.Persistence.DataLoaders.TrackByIdDataLoader→ConferencePlanner.Domain.Entities.Track
- Direction
- Infrastructure.Persistence.DataLoaders uses Domain.Entities, so a change to Domain.Entities can break Infrastructure.Persistence.DataLoaders, while a change to Infrastructure.Persistence.DataLoaders can't break Domain.Entities.
- Position
- Below the diagonal: Infrastructure.Persistence.DataLoaders uses a module listed above it, which is the healthy direction.
36→4 Infrastructure.Persistence.DataLoaders uses Application.Common.Interfaces✕
- Connections
- 6 pairs of types, where a type in Infrastructure.Persistence.DataLoaders uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Infrastructure.Persistence.DataLoaders.AttendeeByIdDataLoader→ConferencePlanner.Application.Common.Interfaces.IAttendeeByIdDataLoaderConferencePlanner.Infrastructure.Persistence.DataLoaders.SessionByIdDataLoader→ConferencePlanner.Application.Common.Interfaces.ISessionByIdDataLoaderConferencePlanner.Infrastructure.Persistence.DataLoaders.SessionBySpeakerIdDataLoader→ConferencePlanner.Application.Common.Interfaces.ISessionBySpeakerIdDataLoaderConferencePlanner.Infrastructure.Persistence.DataLoaders.SpeakerByIdDataLoader→ConferencePlanner.Application.Common.Interfaces.ISpeakerByIdDataLoaderConferencePlanner.Infrastructure.Persistence.DataLoaders.SpeakerBySessionIdDataLoader→ConferencePlanner.Application.Common.Interfaces.ISpeakerBySessionIdDataLoaderConferencePlanner.Infrastructure.Persistence.DataLoaders.TrackByIdDataLoader→ConferencePlanner.Application.Common.Interfaces.ITrackByIdDataLoader
- Direction
- Infrastructure.Persistence.DataLoaders uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Infrastructure.Persistence.DataLoaders, while a change to Infrastructure.Persistence.DataLoaders can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Infrastructure.Persistence.DataLoaders uses a module listed above it, which is the healthy direction.
36→8 Infrastructure.Persistence.DataLoaders uses Infrastructure.Persistence✕
- Connections
- 6 pairs of types, where a type in Infrastructure.Persistence.DataLoaders uses a type in Infrastructure.Persistence.
- The types involved
ConferencePlanner.Infrastructure.Persistence.DataLoaders.AttendeeByIdDataLoader→ConferencePlanner.Infrastructure.Persistence.ApplicationDbContextConferencePlanner.Infrastructure.Persistence.DataLoaders.SessionByIdDataLoader→ConferencePlanner.Infrastructure.Persistence.ApplicationDbContextConferencePlanner.Infrastructure.Persistence.DataLoaders.SessionBySpeakerIdDataLoader→ConferencePlanner.Infrastructure.Persistence.ApplicationDbContextConferencePlanner.Infrastructure.Persistence.DataLoaders.SpeakerByIdDataLoader→ConferencePlanner.Infrastructure.Persistence.ApplicationDbContextConferencePlanner.Infrastructure.Persistence.DataLoaders.SpeakerBySessionIdDataLoader→ConferencePlanner.Infrastructure.Persistence.ApplicationDbContextConferencePlanner.Infrastructure.Persistence.DataLoaders.TrackByIdDataLoader→ConferencePlanner.Infrastructure.Persistence.ApplicationDbContext
- Direction
- Infrastructure.Persistence.DataLoaders uses Infrastructure.Persistence, so a change to Infrastructure.Persistence can break Infrastructure.Persistence.DataLoaders, while a change to Infrastructure.Persistence.DataLoaders can't break Infrastructure.Persistence.
- Position
- Below the diagonal: Infrastructure.Persistence.DataLoaders uses a module listed above it, which is the healthy direction.
37→2 Infrastructure.Persistence.Repositories uses Domain.Entities✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Persistence.Repositories uses a type in Domain.Entities.
- The types involved
ConferencePlanner.Infrastructure.Persistence.Repositories.AttendeeRepository→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.Infrastructure.Persistence.Repositories.SessionRepository→ConferencePlanner.Domain.Entities.SessionConferencePlanner.Infrastructure.Persistence.Repositories.SpeakerRepository→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.Infrastructure.Persistence.Repositories.TrackRepository→ConferencePlanner.Domain.Entities.Track
- Direction
- Infrastructure.Persistence.Repositories uses Domain.Entities, so a change to Domain.Entities can break Infrastructure.Persistence.Repositories, while a change to Infrastructure.Persistence.Repositories can't break Domain.Entities.
- Position
- Below the diagonal: Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
37→4 Infrastructure.Persistence.Repositories uses Application.Common.Interfaces✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Persistence.Repositories uses a type in Application.Common.Interfaces.
- The types involved
ConferencePlanner.Infrastructure.Persistence.Repositories.AttendeeRepository→ConferencePlanner.Application.Common.Interfaces.IAttendeeRepositoryConferencePlanner.Infrastructure.Persistence.Repositories.SessionRepository→ConferencePlanner.Application.Common.Interfaces.ISessionRepositoryConferencePlanner.Infrastructure.Persistence.Repositories.SpeakerRepository→ConferencePlanner.Application.Common.Interfaces.ISpeakerRepositoryConferencePlanner.Infrastructure.Persistence.Repositories.TrackRepository→ConferencePlanner.Application.Common.Interfaces.ITrackRepository
- Direction
- Infrastructure.Persistence.Repositories uses Application.Common.Interfaces, so a change to Application.Common.Interfaces can break Infrastructure.Persistence.Repositories, while a change to Infrastructure.Persistence.Repositories can't break Application.Common.Interfaces.
- Position
- Below the diagonal: Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
37→8 Infrastructure.Persistence.Repositories uses Infrastructure.Persistence✕
- Connections
- 4 pairs of types, where a type in Infrastructure.Persistence.Repositories uses a type in Infrastructure.Persistence.
- The types involved
ConferencePlanner.Infrastructure.Persistence.Repositories.AttendeeRepository→ConferencePlanner.Infrastructure.Persistence.ApplicationDbContextConferencePlanner.Infrastructure.Persistence.Repositories.SessionRepository→ConferencePlanner.Infrastructure.Persistence.ApplicationDbContextConferencePlanner.Infrastructure.Persistence.Repositories.SpeakerRepository→ConferencePlanner.Infrastructure.Persistence.ApplicationDbContextConferencePlanner.Infrastructure.Persistence.Repositories.TrackRepository→ConferencePlanner.Infrastructure.Persistence.ApplicationDbContext
- Direction
- Infrastructure.Persistence.Repositories uses Infrastructure.Persistence, so a change to Infrastructure.Persistence can break Infrastructure.Persistence.Repositories, while a change to Infrastructure.Persistence.Repositories can't break Infrastructure.Persistence.
- Position
- Below the diagonal: Infrastructure.Persistence.Repositories uses a module listed above it, which is the healthy direction.
38→9 GraphQL.Mutations uses Application.Attendees.Commands.CheckInAttendeeById✕
- Connections
- 2 pairs of types, where a type in GraphQL.Mutations uses a type in Application.Attendees.Commands.CheckInAttendeeById.
- The types involved
ConferencePlanner.GraphQL.Mutations.AttendeeMutations→ConferencePlanner.Application.Attendees.Commands.CheckInAttendeeById.CheckInAttendeeCommandConferencePlanner.GraphQL.Mutations.AttendeeMutations→ConferencePlanner.Application.Attendees.Commands.CheckInAttendeeById.CheckInAttendeePayload
- Direction
- GraphQL.Mutations uses Application.Attendees.Commands.CheckInAttendeeById, so a change to Application.Attendees.Commands.CheckInAttendeeById can break GraphQL.Mutations, while a change to GraphQL.Mutations can't break Application.Attendees.Commands.CheckInAttendeeById.
- Position
- Below the diagonal: GraphQL.Mutations uses a module listed above it, which is the healthy direction.
38→10 GraphQL.Mutations uses Application.Attendees.Commands.RegisterAttendee✕
- Connections
- 2 pairs of types, where a type in GraphQL.Mutations uses a type in Application.Attendees.Commands.RegisterAttendee.
- The types involved
ConferencePlanner.GraphQL.Mutations.AttendeeMutations→ConferencePlanner.Application.Attendees.Commands.RegisterAttendee.RegisterAttendeeCommandConferencePlanner.GraphQL.Mutations.AttendeeMutations→ConferencePlanner.Application.Attendees.Commands.RegisterAttendee.RegisterAttendeePayload
- Direction
- GraphQL.Mutations uses Application.Attendees.Commands.RegisterAttendee, so a change to Application.Attendees.Commands.RegisterAttendee can break GraphQL.Mutations, while a change to GraphQL.Mutations can't break Application.Attendees.Commands.RegisterAttendee.
- Position
- Below the diagonal: GraphQL.Mutations uses a module listed above it, which is the healthy direction.
38→15 GraphQL.Mutations uses Application.Sessions.Commands.AddSession✕
- Connections
- 2 pairs of types, where a type in GraphQL.Mutations uses a type in Application.Sessions.Commands.AddSession.
- The types involved
ConferencePlanner.GraphQL.Mutations.SessionMutations→ConferencePlanner.Application.Sessions.Commands.AddSession.AddSessionCommandConferencePlanner.GraphQL.Mutations.SessionMutations→ConferencePlanner.Application.Sessions.Commands.AddSession.AddSessionPayload
- Direction
- GraphQL.Mutations uses Application.Sessions.Commands.AddSession, so a change to Application.Sessions.Commands.AddSession can break GraphQL.Mutations, while a change to GraphQL.Mutations can't break Application.Sessions.Commands.AddSession.
- Position
- Below the diagonal: GraphQL.Mutations uses a module listed above it, which is the healthy direction.
38→16 GraphQL.Mutations uses Application.Sessions.Commands.RenameSession✕
- Connections
- 2 pairs of types, where a type in GraphQL.Mutations uses a type in Application.Sessions.Commands.RenameSession.
- The types involved
ConferencePlanner.GraphQL.Mutations.SessionMutations→ConferencePlanner.Application.Sessions.Commands.RenameSession.RenameSessionCommandConferencePlanner.GraphQL.Mutations.SessionMutations→ConferencePlanner.Application.Sessions.Commands.RenameSession.RenameSessionPayload
- Direction
- GraphQL.Mutations uses Application.Sessions.Commands.RenameSession, so a change to Application.Sessions.Commands.RenameSession can break GraphQL.Mutations, while a change to GraphQL.Mutations can't break Application.Sessions.Commands.RenameSession.
- Position
- Below the diagonal: GraphQL.Mutations uses a module listed above it, which is the healthy direction.
38→17 GraphQL.Mutations uses Application.Sessions.Commands.ScheduleSession✕
- Connections
- 2 pairs of types, where a type in GraphQL.Mutations uses a type in Application.Sessions.Commands.ScheduleSession.
- The types involved
ConferencePlanner.GraphQL.Mutations.SessionMutations→ConferencePlanner.Application.Sessions.Commands.ScheduleSession.ScheduleSessionCommandConferencePlanner.GraphQL.Mutations.SessionMutations→ConferencePlanner.Application.Sessions.Commands.ScheduleSession.ScheduleSessionPayload
- Direction
- GraphQL.Mutations uses Application.Sessions.Commands.ScheduleSession, so a change to Application.Sessions.Commands.ScheduleSession can break GraphQL.Mutations, while a change to GraphQL.Mutations can't break Application.Sessions.Commands.ScheduleSession.
- Position
- Below the diagonal: GraphQL.Mutations uses a module listed above it, which is the healthy direction.
38→24 GraphQL.Mutations uses Application.Speakers.Commands.AddSpeaker✕
- Connections
- 2 pairs of types, where a type in GraphQL.Mutations uses a type in Application.Speakers.Commands.AddSpeaker.
- The types involved
ConferencePlanner.GraphQL.Mutations.SpeakerMutations→ConferencePlanner.Application.Speakers.Commands.AddSpeaker.AddSpeakerCommandConferencePlanner.GraphQL.Mutations.SpeakerMutations→ConferencePlanner.Application.Speakers.Commands.AddSpeaker.AddSpeakerPayload
- Direction
- GraphQL.Mutations uses Application.Speakers.Commands.AddSpeaker, so a change to Application.Speakers.Commands.AddSpeaker can break GraphQL.Mutations, while a change to GraphQL.Mutations can't break Application.Speakers.Commands.AddSpeaker.
- Position
- Below the diagonal: GraphQL.Mutations uses a module listed above it, which is the healthy direction.
38→25 GraphQL.Mutations uses Application.Speakers.Commands.ModifySpeaker✕
- Connections
- 2 pairs of types, where a type in GraphQL.Mutations uses a type in Application.Speakers.Commands.ModifySpeaker.
- The types involved
ConferencePlanner.GraphQL.Mutations.SpeakerMutations→ConferencePlanner.Application.Speakers.Commands.ModifySpeaker.ModifySpeakerCommandConferencePlanner.GraphQL.Mutations.SpeakerMutations→ConferencePlanner.Application.Speakers.Commands.ModifySpeaker.ModifySpeakerPayload
- Direction
- GraphQL.Mutations uses Application.Speakers.Commands.ModifySpeaker, so a change to Application.Speakers.Commands.ModifySpeaker can break GraphQL.Mutations, while a change to GraphQL.Mutations can't break Application.Speakers.Commands.ModifySpeaker.
- Position
- Below the diagonal: GraphQL.Mutations uses a module listed above it, which is the healthy direction.
38→30 GraphQL.Mutations uses Application.Tracks.Commands.AddTrack✕
- Connections
- 2 pairs of types, where a type in GraphQL.Mutations uses a type in Application.Tracks.Commands.AddTrack.
- The types involved
ConferencePlanner.GraphQL.Mutations.TrackMutations→ConferencePlanner.Application.Tracks.Commands.AddTrack.AddTrackCommandConferencePlanner.GraphQL.Mutations.TrackMutations→ConferencePlanner.Application.Tracks.Commands.AddTrack.AddTrackPayload
- Direction
- GraphQL.Mutations uses Application.Tracks.Commands.AddTrack, so a change to Application.Tracks.Commands.AddTrack can break GraphQL.Mutations, while a change to GraphQL.Mutations can't break Application.Tracks.Commands.AddTrack.
- Position
- Below the diagonal: GraphQL.Mutations uses a module listed above it, which is the healthy direction.
38→31 GraphQL.Mutations uses Application.Tracks.Commands.RenameTrack✕
- Connections
- 2 pairs of types, where a type in GraphQL.Mutations uses a type in Application.Tracks.Commands.RenameTrack.
- The types involved
ConferencePlanner.GraphQL.Mutations.TrackMutations→ConferencePlanner.Application.Tracks.Commands.RenameTrack.RenameTrackCommandConferencePlanner.GraphQL.Mutations.TrackMutations→ConferencePlanner.Application.Tracks.Commands.RenameTrack.RenameTrackPayload
- Direction
- GraphQL.Mutations uses Application.Tracks.Commands.RenameTrack, so a change to Application.Tracks.Commands.RenameTrack can break GraphQL.Mutations, while a change to GraphQL.Mutations can't break Application.Tracks.Commands.RenameTrack.
- Position
- Below the diagonal: GraphQL.Mutations uses a module listed above it, which is the healthy direction.
39→2 GraphQL.Nodes uses Domain.Entities✕
- Connections
- 10 pairs of types, where a type in GraphQL.Nodes uses a type in Domain.Entities.
- The types involved
ConferencePlanner.GraphQL.Nodes.AttendeeNode→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.GraphQL.Nodes.AttendeeNode→ConferencePlanner.Domain.Entities.SessionConferencePlanner.GraphQL.Nodes.SessionNode→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.GraphQL.Nodes.SessionNode→ConferencePlanner.Domain.Entities.SessionConferencePlanner.GraphQL.Nodes.SessionNode→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.GraphQL.Nodes.SessionNode→ConferencePlanner.Domain.Entities.TrackConferencePlanner.GraphQL.Nodes.SpeakerNode→ConferencePlanner.Domain.Entities.SessionConferencePlanner.GraphQL.Nodes.SpeakerNode→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.GraphQL.Nodes.TrackNode→ConferencePlanner.Domain.Entities.SessionConferencePlanner.GraphQL.Nodes.TrackNode→ConferencePlanner.Domain.Entities.Track
- Direction
- GraphQL.Nodes uses Domain.Entities, so a change to Domain.Entities can break GraphQL.Nodes, while a change to GraphQL.Nodes can't break Domain.Entities.
- Position
- Below the diagonal: GraphQL.Nodes uses a module listed above it, which is the healthy direction.
39→11 GraphQL.Nodes uses Application.Attendees.Queries.GetAttendeeById✕
- Connections
- 1 pair of types, where a type in GraphQL.Nodes uses a type in Application.Attendees.Queries.GetAttendeeById.
- The types involved
ConferencePlanner.GraphQL.Nodes.AttendeeNode→ConferencePlanner.Application.Attendees.Queries.GetAttendeeById.GetAttendeeByIdQuery
- Direction
- GraphQL.Nodes uses Application.Attendees.Queries.GetAttendeeById, so a change to Application.Attendees.Queries.GetAttendeeById can break GraphQL.Nodes, while a change to GraphQL.Nodes can't break Application.Attendees.Queries.GetAttendeeById.
- Position
- Below the diagonal: GraphQL.Nodes uses a module listed above it, which is the healthy direction.
39→18 GraphQL.Nodes uses Application.Sessions.Queries.GetSessionById✕
- Connections
- 1 pair of types, where a type in GraphQL.Nodes uses a type in Application.Sessions.Queries.GetSessionById.
- The types involved
ConferencePlanner.GraphQL.Nodes.SessionNode→ConferencePlanner.Application.Sessions.Queries.GetSessionById.GetSessionByIdQuery
- Direction
- GraphQL.Nodes uses Application.Sessions.Queries.GetSessionById, so a change to Application.Sessions.Queries.GetSessionById can break GraphQL.Nodes, while a change to GraphQL.Nodes can't break Application.Sessions.Queries.GetSessionById.
- Position
- Below the diagonal: GraphQL.Nodes uses a module listed above it, which is the healthy direction.
39→27 GraphQL.Nodes uses Application.Speakers.Queries.GetSpeakerById✕
- Connections
- 1 pair of types, where a type in GraphQL.Nodes uses a type in Application.Speakers.Queries.GetSpeakerById.
- The types involved
ConferencePlanner.GraphQL.Nodes.SpeakerNode→ConferencePlanner.Application.Speakers.Queries.GetSpeakerById.GetSpeakerByIdQuery
- Direction
- GraphQL.Nodes uses Application.Speakers.Queries.GetSpeakerById, so a change to Application.Speakers.Queries.GetSpeakerById can break GraphQL.Nodes, while a change to GraphQL.Nodes can't break Application.Speakers.Queries.GetSpeakerById.
- Position
- Below the diagonal: GraphQL.Nodes uses a module listed above it, which is the healthy direction.
39→32 GraphQL.Nodes uses Application.Tracks.Queries.GetTrackById✕
- Connections
- 1 pair of types, where a type in GraphQL.Nodes uses a type in Application.Tracks.Queries.GetTrackById.
- The types involved
ConferencePlanner.GraphQL.Nodes.TrackNode→ConferencePlanner.Application.Tracks.Queries.GetTrackById.GetTrackByIdQuery
- Direction
- GraphQL.Nodes uses Application.Tracks.Queries.GetTrackById, so a change to Application.Tracks.Queries.GetTrackById can break GraphQL.Nodes, while a change to GraphQL.Nodes can't break Application.Tracks.Queries.GetTrackById.
- Position
- Below the diagonal: GraphQL.Nodes uses a module listed above it, which is the healthy direction.
40→2 GraphQL.Queries uses Domain.Entities✕
- Connections
- 4 pairs of types, where a type in GraphQL.Queries uses a type in Domain.Entities.
- The types involved
ConferencePlanner.GraphQL.Queries.AttendeeQueries→ConferencePlanner.Domain.Entities.AttendeeConferencePlanner.GraphQL.Queries.SessionQueries→ConferencePlanner.Domain.Entities.SessionConferencePlanner.GraphQL.Queries.SpeakerQueries→ConferencePlanner.Domain.Entities.SpeakerConferencePlanner.GraphQL.Queries.TrackQueries→ConferencePlanner.Domain.Entities.Track
- Direction
- GraphQL.Queries uses Domain.Entities, so a change to Domain.Entities can break GraphQL.Queries, while a change to GraphQL.Queries can't break Domain.Entities.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
40→11 GraphQL.Queries uses Application.Attendees.Queries.GetAttendeeById✕
- Connections
- 1 pair of types, where a type in GraphQL.Queries uses a type in Application.Attendees.Queries.GetAttendeeById.
- The types involved
ConferencePlanner.GraphQL.Queries.AttendeeQueries→ConferencePlanner.Application.Attendees.Queries.GetAttendeeById.GetAttendeeByIdQuery
- Direction
- GraphQL.Queries uses Application.Attendees.Queries.GetAttendeeById, so a change to Application.Attendees.Queries.GetAttendeeById can break GraphQL.Queries, while a change to GraphQL.Queries can't break Application.Attendees.Queries.GetAttendeeById.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
40→13 GraphQL.Queries uses Application.Attendees.Queries.GetAttendeesByIds✕
- Connections
- 1 pair of types, where a type in GraphQL.Queries uses a type in Application.Attendees.Queries.GetAttendeesByIds.
- The types involved
ConferencePlanner.GraphQL.Queries.AttendeeQueries→ConferencePlanner.Application.Attendees.Queries.GetAttendeesByIds.GetAttendeesByIdsQuery
- Direction
- GraphQL.Queries uses Application.Attendees.Queries.GetAttendeesByIds, so a change to Application.Attendees.Queries.GetAttendeesByIds can break GraphQL.Queries, while a change to GraphQL.Queries can't break Application.Attendees.Queries.GetAttendeesByIds.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
40→18 GraphQL.Queries uses Application.Sessions.Queries.GetSessionById✕
- Connections
- 1 pair of types, where a type in GraphQL.Queries uses a type in Application.Sessions.Queries.GetSessionById.
- The types involved
ConferencePlanner.GraphQL.Queries.SessionQueries→ConferencePlanner.Application.Sessions.Queries.GetSessionById.GetSessionByIdQuery
- Direction
- GraphQL.Queries uses Application.Sessions.Queries.GetSessionById, so a change to Application.Sessions.Queries.GetSessionById can break GraphQL.Queries, while a change to GraphQL.Queries can't break Application.Sessions.Queries.GetSessionById.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
40→21 GraphQL.Queries uses Application.Sessions.Queries.GetSessionsByIds✕
- Connections
- 1 pair of types, where a type in GraphQL.Queries uses a type in Application.Sessions.Queries.GetSessionsByIds.
- The types involved
ConferencePlanner.GraphQL.Queries.SessionQueries→ConferencePlanner.Application.Sessions.Queries.GetSessionsByIds.GetSessionsByIdsQuery
- Direction
- GraphQL.Queries uses Application.Sessions.Queries.GetSessionsByIds, so a change to Application.Sessions.Queries.GetSessionsByIds can break GraphQL.Queries, while a change to GraphQL.Queries can't break Application.Sessions.Queries.GetSessionsByIds.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
40→27 GraphQL.Queries uses Application.Speakers.Queries.GetSpeakerById✕
- Connections
- 1 pair of types, where a type in GraphQL.Queries uses a type in Application.Speakers.Queries.GetSpeakerById.
- The types involved
ConferencePlanner.GraphQL.Queries.SpeakerQueries→ConferencePlanner.Application.Speakers.Queries.GetSpeakerById.GetSpeakerByIdQuery
- Direction
- GraphQL.Queries uses Application.Speakers.Queries.GetSpeakerById, so a change to Application.Speakers.Queries.GetSpeakerById can break GraphQL.Queries, while a change to GraphQL.Queries can't break Application.Speakers.Queries.GetSpeakerById.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
40→29 GraphQL.Queries uses Application.Speakers.Queries.GetSpeakersByIds✕
- Connections
- 1 pair of types, where a type in GraphQL.Queries uses a type in Application.Speakers.Queries.GetSpeakersByIds.
- The types involved
ConferencePlanner.GraphQL.Queries.SpeakerQueries→ConferencePlanner.Application.Speakers.Queries.GetSpeakersByIds.GetSpeakersByIdsQuery
- Direction
- GraphQL.Queries uses Application.Speakers.Queries.GetSpeakersByIds, so a change to Application.Speakers.Queries.GetSpeakersByIds can break GraphQL.Queries, while a change to GraphQL.Queries can't break Application.Speakers.Queries.GetSpeakersByIds.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
40→32 GraphQL.Queries uses Application.Tracks.Queries.GetTrackById✕
- Connections
- 1 pair of types, where a type in GraphQL.Queries uses a type in Application.Tracks.Queries.GetTrackById.
- The types involved
ConferencePlanner.GraphQL.Queries.TrackQueries→ConferencePlanner.Application.Tracks.Queries.GetTrackById.GetTrackByIdQuery
- Direction
- GraphQL.Queries uses Application.Tracks.Queries.GetTrackById, so a change to Application.Tracks.Queries.GetTrackById can break GraphQL.Queries, while a change to GraphQL.Queries can't break Application.Tracks.Queries.GetTrackById.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
40→33 GraphQL.Queries uses Application.Tracks.Queries.GetTrackByName✕
- Connections
- 1 pair of types, where a type in GraphQL.Queries uses a type in Application.Tracks.Queries.GetTrackByName.
- The types involved
ConferencePlanner.GraphQL.Queries.TrackQueries→ConferencePlanner.Application.Tracks.Queries.GetTrackByName.GetTrackByNameQuery
- Direction
- GraphQL.Queries uses Application.Tracks.Queries.GetTrackByName, so a change to Application.Tracks.Queries.GetTrackByName can break GraphQL.Queries, while a change to GraphQL.Queries can't break Application.Tracks.Queries.GetTrackByName.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
40→34 GraphQL.Queries uses Application.Tracks.Queries.GetTracksByIds✕
- Connections
- 1 pair of types, where a type in GraphQL.Queries uses a type in Application.Tracks.Queries.GetTracksByIds.
- The types involved
ConferencePlanner.GraphQL.Queries.TrackQueries→ConferencePlanner.Application.Tracks.Queries.GetTracksByIds.GetTracksByIdsQuery
- Direction
- GraphQL.Queries uses Application.Tracks.Queries.GetTracksByIds, so a change to Application.Tracks.Queries.GetTracksByIds can break GraphQL.Queries, while a change to GraphQL.Queries can't break Application.Tracks.Queries.GetTracksByIds.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
40→35 GraphQL.Queries uses Application.Tracks.Queries.GetTracksByNames✕
- Connections
- 1 pair of types, where a type in GraphQL.Queries uses a type in Application.Tracks.Queries.GetTracksByNames.
- The types involved
ConferencePlanner.GraphQL.Queries.TrackQueries→ConferencePlanner.Application.Tracks.Queries.GetTracksByNames.GetTracksByNamesQuery
- Direction
- GraphQL.Queries uses Application.Tracks.Queries.GetTracksByNames, so a change to Application.Tracks.Queries.GetTracksByNames can break GraphQL.Queries, while a change to GraphQL.Queries can't break Application.Tracks.Queries.GetTracksByNames.
- Position
- Below the diagonal: GraphQL.Queries uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 14 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A07:2025 — Authentication Failures | 4 | High / Critical |
| A01:2025 — Broken Access Control | 2 | Medium |
Roadmap
Top priorities: Resolve the 1 No tests found finding(s) in Test Distribution; Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED, REDACTED; Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No tests found finding(s) in Test Distribution. | +9.2 pts | Low | Test Distribution |
| Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED, REDACTED. | +8.1 pts | Low | Secret Scanning |
| Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with Program.cs, DependencyInjection.cs, SessionMutations.cs. | +4.9 pts | Low | Knowledge Freshness |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.6 pts | Low | ADR Quality |
| Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.). | +7.7 pts | Medium | Data Protection |
| Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. | +7.7 pts | Medium | Access Controls |
| Resolve the 5 End-of-life runtime finding(s) in Platform End-of-Life — start with Application.csproj, Domain.csproj, GraphQL.csproj. | +2.6 pts | Low | Platform End-of-Life |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.2 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| src/GraphQL/GraphQL.csproj | 5.5 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/Domain/Domain.csproj | 6.4 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Data Compliance (PII/GDPR): REDACTED |
| REDACTED | 7.9 | Mixed | Data Compliance (PII/GDPR): REDACTED |
| src/Application/Application.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/Infrastructure/Infrastructure.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| tests/GraphQL.Tests/GraphQL.Tests.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/GraphQL/Extensions/ObjectFieldDescriptorExtensions.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
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 74 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 — 74 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, 65 of 84 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
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the test tier(s) built and ran but no tests were discovered, so reliability couldn't be exercised.
- 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 157 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'docker-compose.dcproj' because the file extension '.dcproj' is not associated with a language.
- 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.
- 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.
- D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `src/GraphQL/NDC_London_2019.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D39 IL Efficiency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
- 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 DockerCompose (REDACTED). compose up failed (exit 15 — the compose project is invalid) — service "grapghql" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
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.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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").
- 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.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
0 duplicated block group(s) detected.
D5 · Coupling
5 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 Domain.csproj. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 5 classes have LCOM4 above 3.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · Secret Scanning
3 secret(s) detected.
What to do
- Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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 256 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 26 direct `PackageReference`(s), and 224 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
2 deducted debt markers + unmeasured dead symbols across 2486 LoC in the .NET projects (0.2/KLoC) → score 9.5. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with GraphQL.csproj. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with ObjectFieldDescriptorExtensions.cs. — One of this dimension's main actionable groups (1 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
5 projects, 129 source files, 2490 hand-written lines of code (2486 production / 4 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 520 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 6 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 5 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).
D21 · Naming Consistency
0 naming inconsistencies among 18 declarations measured against a convention their peers follow.
D26 · Project Cohesion
0 of 5 projects flagged as possibly oversized/incoherent.
D27 · Navigability
99 % of calls cross a namespace and 17 % 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)
14 finding(s): 0 critical, 10 high, 4 medium, 0 low. 7 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.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 7 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 (7 issue-level, 0 of them charged here).
D31 · IaC & Container Security
5 finding(s): 0 critical, 2 high, 2 medium, 1 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D32 · Data Compliance (PII/GDPR)
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
3 of 3 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/GraphQL/Program.cs. Counted over 3 of the 129 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 3 Orphaned file finding(s) in Knowledge Freshness — start with Program.cs, DependencyInjection.cs, SessionMutations.cs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 — start with REDACTED. — 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).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 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.
What to do
- Resolve the 5 End-of-life runtime finding(s) in Platform End-of-Life — start with Application.csproj, Domain.csproj, GraphQL.csproj. — One of this dimension's main actionable groups (5 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls
- No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
- `MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/GraphQL/Program.cs:114
What to do
- Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
ED5 · Idempotency
- `CheckInAttendeeById.CheckInAttendeeCommandHandler.Handle` mutates persistent state (a database save one hop away, in AttendeeRepository.UpdateAttendeeAsync) and appends to `attendee.SessionsAttendees` (line 22) on a stored object, so a re-run appends again. A retry or at-least-once redelivery runs it again — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Application/Attendees/Commands/CheckInAttendeeById/CheckInAttendeeCommandHandler.cs:16
What to do
- Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×4) — src/Infrastructure/Persistence/DataLoaders/SessionBySpeakerIdDataLoader.cs:42, src/Infrastructure/Persistence/DataLoaders/SessionBySpeakerIdDataLoader.cs:58, src/Infrastructure/Persistence/DataLoaders/SpeakerBySessionIdDataLoader.cs:42, …
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `Handle` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×6) — src/Application/Attendees/Queries/GetAttendees/GetAttendeesQueryHandler.cs:16, src/Application/Attendees/Queries/GetAttendeesBySessionId/GetAttendeesBySessionIdQueryHandler.cs:18, src/Application/Sessions/Queries/GetSessions/GetSessionsQueryHandler.cs:16, …
- `Process` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/Application/Common/Behaviours/LoggingBehaviour.cs:15
- `SessionBySpeakerIdDataLoader` has 2 unfinished members out of 4 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented. — src/Infrastructure/Persistence/DataLoaders/SessionBySpeakerIdDataLoader.cs:8
- `LoadAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/Infrastructure/Persistence/DataLoaders/SessionBySpeakerIdDataLoader.cs:42, src/Infrastructure/Persistence/DataLoaders/SpeakerBySessionIdDataLoader.cs:42
- `Set` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/Infrastructure/Persistence/DataLoaders/SessionBySpeakerIdDataLoader.cs:58, src/Infrastructure/Persistence/DataLoaders/SpeakerBySessionIdDataLoader.cs:58
- `SpeakerBySessionIdDataLoader` has 2 unfinished members out of 4 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented. — src/Infrastructure/Persistence/DataLoaders/SpeakerBySessionIdDataLoader.cs:8
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
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 a README to the 4 of 4 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
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1817 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:7
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, and the service already exposes health probe endpoints (healthz/livez/readyz or a container healthcheck), but no compose service declares a `healthcheck:` that uses them and nothing pins a previous image to fall back to — so a release that starts but does not serve looks healthy, and reversing it is a manual step.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P8 · Schema migrations
- This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema. — src/Infrastructure/Persistence/Imports/DataImporterExtensions.cs:18
What to do
- Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
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. — src/GraphQL/Program.cs:14
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. — src/GraphQL/Program.cs:14
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.
- Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 88/91 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. (×3) — src/GraphQL/Nodes/SessionNode.cs:28, src/GraphQL/Nodes/TrackNode.cs:23, src/Infrastructure/Persistence/Imports/DataImporter.cs:9
- 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
- Accepts a CancellationToken and never uses it, while it calls something that takes one — so a caller who cancels still waits for that work. Pass the token on (or, where the work must outlive the caller, start it without awaiting it so the choice is visible). — src/Infrastructure/Persistence/Repositories/SessionRepository.cs:29
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.3 `!` suppressions per 1k syntax nodes — 20 suppression(s) across the 15498 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 77% | Adequate — gated by IC1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 44% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 32% | Weak — gated by D9, D13, P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 22% | Critical — gated by D36, C1, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 40 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX2 Stateful singletons — no singleton implementations detected
- 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 — compose up failed (exit 15 — the compose project is invalid) — service "grapghql" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No tests discovered
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (2,486 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (5 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the target did not build
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 value object(s); a Domain/Aggregates/ValueObjects layer
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a message-bus package; 30 CQRS handler(s)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (path 1, command argument 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj src/GraphQL/GraphQL.csproj:15
- REDACTED
Serious — 45 finding(s)
- Fake-async — async method never awaits src/Application/Attendees/Queries/GetAttendees/GetAttendeesQueryHandler.cs:16
- Fake-async — async method never awaits src/Application/Attendees/Queries/GetAttendeesBySessionId/GetAttendeesBySessionIdQueryHandler.cs:18
- Fake-async — async method never awaits src/Application/Common/Behaviours/LoggingBehaviour.cs:15
- Fake-async — async method never awaits src/Application/Sessions/Queries/GetSessions/GetSessionsQueryHandler.cs:16
- Fake-async — async method never awaits src/Application/Sessions/Queries/GetSessionsByTrack/GetSessionsByTrackQueryHandler.cs:16
- Fake-async — async method never awaits src/Application/Speakers/Queries/GetSessionSpeakers/GetSessionSpeakersQueryHandler.cs:17
- Fake-async — async method never awaits src/Application/Speakers/Queries/GetSpeakers/GetSpeakersQueryHandler.cs:16
- End-of-life runtime: .NET net6.0 src/Application/Application.csproj:4
- End-of-life runtime: .NET net6.0 src/Domain/Domain.csproj:4
- End-of-life runtime: .NET net6.0 src/GraphQL/GraphQL.csproj:4
- End-of-life runtime: .NET net6.0 src/Infrastructure/Infrastructure.csproj:4
- End-of-life runtime: .NET net6.0 tests/GraphQL.Tests/GraphQL.Tests.csproj:4
- Unfinished stub — throws NotImplementedException src/Infrastructure/Persistence/DataLoaders/SessionBySpeakerIdDataLoader.cs:42
- Unfinished stub — throws NotImplementedException src/Infrastructure/Persistence/DataLoaders/SessionBySpeakerIdDataLoader.cs:58
- Unfinished stub — throws NotImplementedException src/Infrastructure/Persistence/DataLoaders/SpeakerBySessionIdDataLoader.cs:42
- Unfinished stub — throws NotImplementedException src/Infrastructure/Persistence/DataLoaders/SpeakerBySessionIdDataLoader.cs:58
- Unfinished stub — throws NotImplementedException src/Infrastructure/Persistence/DataLoaders/SessionBySpeakerIdDataLoader.cs:42
- Unfinished stub — throws NotImplementedException src/Infrastructure/Persistence/DataLoaders/SessionBySpeakerIdDataLoader.cs:58
- Unfinished stub — throws NotImplementedException src/Infrastructure/Persistence/DataLoaders/SpeakerBySessionIdDataLoader.cs:42
- Unfinished stub — throws NotImplementedException src/Infrastructure/Persistence/DataLoaders/SpeakerBySessionIdDataLoader.cs:58
- REDACTED
- REDACTED
- REDACTED
- Async method without CancellationToken: GetAttendees src/GraphQL/Nodes/SessionNode.cs:28
- Async method without CancellationToken: GetSessions src/GraphQL/Nodes/TrackNode.cs:23
- Async method without CancellationToken: LoadDataAsync src/Infrastructure/Persistence/Imports/DataImporter.cs:9
- No authorization
- No authorization src/GraphQL/Program.cs:114
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Skeleton type — most members are unfinished src/Infrastructure/Persistence/DataLoaders/SessionBySpeakerIdDataLoader.cs:8
- Skeleton type — most members are unfinished src/Infrastructure/Persistence/DataLoaders/SpeakerBySessionIdDataLoader.cs:8
- No data-protection/encryption
- TodoComment src/GraphQL/Extensions/ObjectFieldDescriptorExtensions.cs:11
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: Domain src/Domain/Domain.csproj:1
- Coverage not measured — test suite did not build
- Non-idempotent mutation: CheckInAttendeeById.CheckInAttendeeCommandHandler.Handle src/Application/Attendees/Commands/CheckInAttendeeById/CheckInAttendeeCommandHandler.cs:16
- Schema created with EnsureCreated() outside the migrations src/Infrastructure/Persistence/Imports/DataImporterExtensions.cs:18
- NuGet dependencies are not locked
- Async method drops its CancellationToken: FindSessionByIdAsync src/Infrastructure/Persistence/Repositories/SessionRepository.cs:29
Minor — 22 finding(s)
- Orphaned file src/GraphQL/Program.cs:1
- Orphaned file src/Infrastructure/DependencyInjection.cs:1
- Orphaned file src/GraphQL/Mutations/SessionMutations.cs:1
- No security response headers detected
- No security response headers detected src/GraphQL/Program.cs:14
- No app-layer HTTPS enforcement detected
- No app-layer HTTPS enforcement detected src/GraphQL/Program.cs:14
- No ADRs found
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No tests found
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- Dependabot does not watch github-actions REDACTED:7
- No rollback/health safety
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
- Null-forgiving operator (`!`) suppressions reduce the NRT score
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-11d43cc5f4bc495ea84eefb011497e43/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-11d43cc5f4bc495ea84eefb011497e43/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/Persistence/Migrations . | 14 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.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/Persistence/Migrations . | 2 | artifacts/raw/semgrep-gdpr.json |
| 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-b331cd9a34414628bd8807b0209705c3 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 4 field(s)
- RegisterAttendeeCommand.FirstName src/Application/Attendees/Commands/RegisterAttendee/RegisterAttendeeCommand.cs:7
- RegisterAttendeeCommand.LastName src/Application/Attendees/Commands/RegisterAttendee/RegisterAttendeeCommand.cs:8
- Attendee.FirstName src/Domain/Entities/Attendee.cs:10
- Attendee.LastName src/Domain/Entities/Attendee.cs:12
Email — 2 field(s)
- RegisterAttendeeCommand.EmailAddress src/Application/Attendees/Commands/RegisterAttendee/RegisterAttendeeCommand.cs:10
- Attendee.EmailAddress src/Domain/Entities/Attendee.cs:16