Executive summary
oskardudycz/GoldenEye falls short of our standard for production because 26 files are no longer known to anyone active in the project and the documentation refers to links that don't exist. It scores 43 out of 100 and is rated Weak, and 12 of its 19 critical findings are security problems.
Maturity, at 33, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the two comments that repeat the code, or contradict it, worth about 6 points. Having someone learn and document the 26 files no active contributor knows would lift Maturity itself, worth about 8 points. Raising Maturity to 70 would lift the score to about 51.
Six settings leave the servers or containers unsafe. Three passwords or keys in the code and one in the code's history are open to anyone who can read the repository, and two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Correcting the unsafe settings, replacing each exposed password or key and pinning each tool to an exact version would close these risks. Saving the change and the message together would take care of the three places where data is saved and a message sent separately.
The product code is 6,758 lines, about €12,000 to rebuild.
If Maturity rose from 33 to 70, the lowest score rated Strong, the score would rise from 43 to about 51.
New since the last survey: 30 findings
- Platform End-of-Life · End-of-life runtime: .NET net6.0 samples/DDD/Tickets/Tickets.Api.Tests/Tickets.Api.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 samples/DDD/Tickets/Tickets.Api/Tickets.Api.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 samples/DDD/Tickets/Tickets.Tests/Tickets.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 samples/DDD/Tickets/Tickets/Tickets.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 samples/GoldenEye.WebApi.Sample/GoldenEye.WebApi.Sample.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Core/Core.Tests.External/Core.Tests.External.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Core/Core.Tests/Core.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Core/Core/Core.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Dapper/Dapper.Integration.Tests/Dapper.Integration.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Dapper/Dapper.Tests/Dapper.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Dapper/Dapper/Dapper.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/ElasticSearch/ElasticSearch.Integration.Tests/ElasticSearch.Integration.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/ElasticSearch/ElasticSearch.Tests/ElasticSearch.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/ElasticSearch/ElasticSearch/ElasticSearch.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/EntityFramework/EntityFramework.Integration.Tests/EntityFramework.Integration.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/EntityFramework/EntityFramework/EntityFramework.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Kafka/Kafka.Integration.Tests/Kafka.Integration.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Kafka/Kafka.Tests/Kafka.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Kafka/Kafka/Kafka.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Marten/Marten.Integration.Tests/Marten.Integration.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Marten/Marten/Marten.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/Testing/Testing/Testing.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/WebApi/WebApi.Tests/WebApi.Tests.csproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/WebApi/WebApi/WebApi.csproj
- Outbox / dual-write · Dual write (no outbox): EntityFrameworkRepository.SaveChanges src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs
- Outbox / dual-write · Dual write (no outbox): MartenDocumentRepository.SaveChanges src/Marten/Marten/Repositories/MartenDocumentRepository.cs
- Outbox / dual-write · Dual write (no outbox): MartenEventSourcedRepository.SaveChanges src/Marten/Marten/Repositories/MartenEventSourcedRepository.cs
- Stateful singletons · Stateful shared instance: UserInfoProvider src/Core/Core/Security/UserInfoProvider.cs
- Stateful singletons · Process-global static state: DateTimeExtensions src/Core/Core/Extensions/Basic/DateTimeExtensions.cs
- Stateful singletons · Process-global static state: ReflectionExtensions src/Core/Core/Extensions/Reflection/ReflectionExtensions.cs
Fixed since the last survey: 55 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Boundary Type-Coupling · Cross-context type IEvent (Core → Marten) src/Marten/Marten/Events/Storage/MartenEventStore.cs
- Boundary Type-Coupling · Cross-context type IEvent (Core → Marten) src/Marten/Marten/Events/Storage/MartenEventStore.cs
- Boundary Type-Coupling · Cross-context type IEvent (Core → Marten) src/Marten/Marten/Events/Storage/MartenEventStore.cs
- Boundary Type-Coupling · Cross-context type IEvent (Core → samples) samples/DDD/Tickets/Tickets/Reservations/CancellingReservation/ReservationCancelled.cs
- Boundary Type-Coupling · Cross-context type IEvent (Core → samples) samples/DDD/Tickets/Tickets/Reservations/ChangingReservationSeat/ReservationSeatChanged.cs
- Boundary Type-Coupling · Cross-context type IEvent (Core → samples) samples/DDD/Tickets/Tickets/Reservations/ConfirmingReservation/ReservationConfirmed.cs
- Boundary Type-Coupling · Cross-context type IEvent (Core → samples) samples/DDD/Tickets/Tickets/Reservations/CreatingTentativeReservation/TentativeReservationCreated.cs
- Boundary Type-Coupling · Cross-context type ReservationHistory (samples → Tickets) REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 samples/GoldenEye.WebApi.Sample/GoldenEye.WebApi.Sample.csproj
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Events/Storage/MartenEventStore.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Events/Storage/MartenEventStore.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Repositories/MartenDocumentRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Repositories/MartenDocumentRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Repositories/MartenDocumentRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Repositories/MartenEventSourcedRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Repositories/MartenEventSourcedRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Repositories/MartenEventSourcedRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Repositories/MartenEventSourcedRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Repositories/MartenEventSourcedRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Marten/Marten/Repositories/MartenEventSourcedRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/WebApi/Controllers/ReadonlyControllerBase.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/WebApi/Controllers/RestControllerBase.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/WebApi/Controllers/RestControllerBase.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/WebApi/Controllers/RestControllerBase.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/WebApi/Exceptions/ExceptionHandlingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/WebApi/WebApi/Exceptions/ExceptionHandlingMiddleware.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Kafka/Kafka/Consumers/KafkaConsumer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Kafka/Kafka/Consumers/KafkaConsumer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Kafka/Kafka/Consumers/KafkaConsumer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Kafka/Kafka/Producers/KafkaProducer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/Kafka/Kafka/Producers/KafkaProducer.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
- Async & latency hygiene · Awaits without ConfigureAwait(false) src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs
Rebuild cost: about €12,000 · Estimate
| Cost to rebuild | €3,900 to €19,000, for 65 to 204 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Very 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 43. 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: 6,758 lines of product code, of which 47% is declarations and boilerplate, 33% straight logic and 20% logic with branches |
| Comment lines | The estimate prices 6,089 lines. Comment lines count towards the size of 6,758 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Core.Streaming.Kafka.Consumers | 2 Core.Streaming.Kafka.Producers | 3 GoldenEye.Commands | 4 GoldenEye.Configuration | 5 GoldenEye.Dapper.Mappings | 6 GoldenEye.EntityFramework.Migrations | 7 GoldenEye.EntityFramework.Registration | 8 GoldenEye.Exceptions | 9 GoldenEye.Extensions.Collections | 10 GoldenEye.Extensions.DependencyInjection | 11 GoldenEye.Extensions.Dynamic | 12 GoldenEye.Extensions.Enums | 13 GoldenEye.Extensions.Functions | 14 GoldenEye.Extensions.Lambda | 15 GoldenEye.Modules | 16 GoldenEye.Objects.Audit | 17 GoldenEye.Objects.Dates | 18 GoldenEye.Objects.General | 19 GoldenEye.Objects.Versioning | 20 GoldenEye.Repositories | 21 GoldenEye.Dapper.Generators | 22 GoldenEye.Entities | 23 GoldenEye.Events.External | 24 GoldenEye.Extensions.Basic | 25 GoldenEye.Queries | 26 GoldenEye.Registration | 27 GoldenEye.WebApi.Modules | 28 GoldenEye.Context.SaveChangesHandlers.Base | 29 GoldenEye.Events | 30 GoldenEye.Kafka.Consumers | 31 GoldenEye.Aggregates | 32 GoldenEye.Context.SaveChangesHandlers | 33 GoldenEye.Events.Store | 34 GoldenEye.Kafka.Producers | 35 GoldenEye.Events.Aggregate | 36 GoldenEye.Marten.Events.Storage | 37 GoldenEye.Dapper.Repositories | 38 GoldenEye.ElasticSearch.Repositories | 39 GoldenEye.EntityFramework.Repositories | 40 GoldenEye.Marten.Repositories |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Core.Streaming.Kafka.Consumers | ||||||||||||||||||||||||||||||||||||||||
| 2 Core.Streaming.Kafka.Producers | ||||||||||||||||||||||||||||||||||||||||
| 3 GoldenEye.Commands | ||||||||||||||||||||||||||||||||||||||||
| 4 GoldenEye.Configuration | ||||||||||||||||||||||||||||||||||||||||
| 5 GoldenEye.Dapper.Mappings | ||||||||||||||||||||||||||||||||||||||||
| 6 GoldenEye.EntityFramework.Migrations | ||||||||||||||||||||||||||||||||||||||||
| 7 GoldenEye.EntityFramework.Registration | ||||||||||||||||||||||||||||||||||||||||
| 8 GoldenEye.Exceptions | ||||||||||||||||||||||||||||||||||||||||
| 9 GoldenEye.Extensions.Collections | ||||||||||||||||||||||||||||||||||||||||
| 10 GoldenEye.Extensions.DependencyInjection | ||||||||||||||||||||||||||||||||||||||||
| 11 GoldenEye.Extensions.Dynamic | ||||||||||||||||||||||||||||||||||||||||
| 12 GoldenEye.Extensions.Enums | ||||||||||||||||||||||||||||||||||||||||
| 13 GoldenEye.Extensions.Functions | ||||||||||||||||||||||||||||||||||||||||
| 14 GoldenEye.Extensions.Lambda | ||||||||||||||||||||||||||||||||||||||||
| 15 GoldenEye.Modules | ||||||||||||||||||||||||||||||||||||||||
| 16 GoldenEye.Objects.Audit | ||||||||||||||||||||||||||||||||||||||||
| 17 GoldenEye.Objects.Dates | ||||||||||||||||||||||||||||||||||||||||
| 18 GoldenEye.Objects.General | ||||||||||||||||||||||||||||||||||||||||
| 19 GoldenEye.Objects.Versioning | ||||||||||||||||||||||||||||||||||||||||
| 20 GoldenEye.Repositories | ||||||||||||||||||||||||||||||||||||||||
| 21 GoldenEye.Dapper.Generators | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 GoldenEye.Entities | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 GoldenEye.Events.External | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 GoldenEye.Extensions.Basic | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 GoldenEye.Queries | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 GoldenEye.Registration | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 GoldenEye.WebApi.Modules | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 GoldenEye.Context.SaveChangesHandlers.Base | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 GoldenEye.Events | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 GoldenEye.Kafka.Consumers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 GoldenEye.Aggregates | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 32 GoldenEye.Context.SaveChangesHandlers | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 33 GoldenEye.Events.Store | 3 | |||||||||||||||||||||||||||||||||||||||
| 34 GoldenEye.Kafka.Producers | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 GoldenEye.Events.Aggregate | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 36 GoldenEye.Marten.Events.Storage | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 GoldenEye.Dapper.Repositories | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 GoldenEye.ElasticSearch.Repositories | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 GoldenEye.EntityFramework.Repositories | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 GoldenEye.Marten.Repositories | 4 | 1 | 2 | 1 |
21→5 GoldenEye.Dapper.Generators uses GoldenEye.Dapper.Mappings✕
- Connections
- 1 pair of types, where a type in GoldenEye.Dapper.Generators uses a type in GoldenEye.Dapper.Mappings.
- The types involved
GoldenEye.Dapper.Generators.MappingsSqlGenerator→GoldenEye.Dapper.Mappings.IDapperMapping
- Direction
- GoldenEye.Dapper.Generators uses GoldenEye.Dapper.Mappings, so a change to GoldenEye.Dapper.Mappings can break GoldenEye.Dapper.Generators, while a change to GoldenEye.Dapper.Generators can't break GoldenEye.Dapper.Mappings.
- Position
- Below the diagonal: GoldenEye.Dapper.Generators uses a module listed above it, which is the healthy direction.
22→16 GoldenEye.Entities uses GoldenEye.Objects.Audit✕
- Connections
- 1 pair of types, where a type in GoldenEye.Entities uses a type in GoldenEye.Objects.Audit.
- The types involved
GoldenEye.Entities.IAuditableEntity→GoldenEye.Objects.Audit.IAuditable
- Direction
- GoldenEye.Entities uses GoldenEye.Objects.Audit, so a change to GoldenEye.Objects.Audit can break GoldenEye.Entities, while a change to GoldenEye.Entities can't break GoldenEye.Objects.Audit.
- Position
- Below the diagonal: GoldenEye.Entities uses a module listed above it, which is the healthy direction.
22→18 GoldenEye.Entities uses GoldenEye.Objects.General✕
- Connections
- 1 pair of types, where a type in GoldenEye.Entities uses a type in GoldenEye.Objects.General.
- The types involved
GoldenEye.Entities.IEntity→GoldenEye.Objects.General.IHaveId
- Direction
- GoldenEye.Entities uses GoldenEye.Objects.General, so a change to GoldenEye.Objects.General can break GoldenEye.Entities, while a change to GoldenEye.Entities can't break GoldenEye.Objects.General.
- Position
- Below the diagonal: GoldenEye.Entities uses a module listed above it, which is the healthy direction.
23→29 GoldenEye.Events.External uses GoldenEye.Events part of a loop✕
- Connections
- 2 pairs of types, where a type in GoldenEye.Events.External uses a type in GoldenEye.Events.
- The types involved
GoldenEye.Events.External.IExternalEventProducer→GoldenEye.Events.IExternalEventGoldenEye.Events.External.NulloExternalEventProducer→GoldenEye.Events.IExternalEvent
- Direction
- GoldenEye.Events.External uses GoldenEye.Events, so a change to GoldenEye.Events can break GoldenEye.Events.External, while a change to GoldenEye.Events.External can't break GoldenEye.Events.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→17 GoldenEye.Extensions.Basic uses GoldenEye.Objects.Dates✕
- Connections
- 2 pairs of types, where a type in GoldenEye.Extensions.Basic uses a type in GoldenEye.Objects.Dates.
- The types involved
GoldenEye.Extensions.Basic.DateRangeExtensions→GoldenEye.Objects.Dates.DateRangeGoldenEye.Extensions.Basic.DateTimeExtensions→GoldenEye.Objects.Dates.DateRange
- Direction
- GoldenEye.Extensions.Basic uses GoldenEye.Objects.Dates, so a change to GoldenEye.Objects.Dates can break GoldenEye.Extensions.Basic, while a change to GoldenEye.Extensions.Basic can't break GoldenEye.Objects.Dates.
- Position
- Below the diagonal: GoldenEye.Extensions.Basic uses a module listed above it, which is the healthy direction.
25→18 GoldenEye.Queries uses GoldenEye.Objects.General✕
- Connections
- 1 pair of types, where a type in GoldenEye.Queries uses a type in GoldenEye.Objects.General.
- The types involved
GoldenEye.Queries.IView→GoldenEye.Objects.General.IHaveId
- Direction
- GoldenEye.Queries uses GoldenEye.Objects.General, so a change to GoldenEye.Objects.General can break GoldenEye.Queries, while a change to GoldenEye.Queries can't break GoldenEye.Objects.General.
- Position
- Below the diagonal: GoldenEye.Queries uses a module listed above it, which is the healthy direction.
26→10 GoldenEye.Registration uses GoldenEye.Extensions.DependencyInjection✕
- Connections
- 1 pair of types, where a type in GoldenEye.Registration uses a type in GoldenEye.Extensions.DependencyInjection.
- The types involved
GoldenEye.Registration.Registration→GoldenEye.Extensions.DependencyInjection.AssemblySelector
- Direction
- GoldenEye.Registration uses GoldenEye.Extensions.DependencyInjection, so a change to GoldenEye.Extensions.DependencyInjection can break GoldenEye.Registration, while a change to GoldenEye.Registration can't break GoldenEye.Extensions.DependencyInjection.
- Position
- Below the diagonal: GoldenEye.Registration uses a module listed above it, which is the healthy direction.
27→15 GoldenEye.WebApi.Modules uses GoldenEye.Modules✕
- Connections
- 2 pairs of types, where a type in GoldenEye.WebApi.Modules uses a type in GoldenEye.Modules.
- The types involved
GoldenEye.WebApi.Modules.IWebApiModule→GoldenEye.Modules.IModuleGoldenEye.WebApi.Modules.WebApiModule→GoldenEye.Modules.Module
- Direction
- GoldenEye.WebApi.Modules uses GoldenEye.Modules, so a change to GoldenEye.Modules can break GoldenEye.WebApi.Modules, while a change to GoldenEye.WebApi.Modules can't break GoldenEye.Modules.
- Position
- Below the diagonal: GoldenEye.WebApi.Modules uses a module listed above it, which is the healthy direction.
28→22 GoldenEye.Context.SaveChangesHandlers.Base uses GoldenEye.Entities✕
- Connections
- 1 pair of types, where a type in GoldenEye.Context.SaveChangesHandlers.Base uses a type in GoldenEye.Entities.
- The types involved
GoldenEye.Context.SaveChangesHandlers.Base.ISaveChangesHandler→GoldenEye.Entities.IProvidesAuditInfo
- Direction
- GoldenEye.Context.SaveChangesHandlers.Base uses GoldenEye.Entities, so a change to GoldenEye.Entities can break GoldenEye.Context.SaveChangesHandlers.Base, while a change to GoldenEye.Context.SaveChangesHandlers.Base can't break GoldenEye.Entities.
- Position
- Below the diagonal: GoldenEye.Context.SaveChangesHandlers.Base uses a module listed above it, which is the healthy direction.
29→23 GoldenEye.Events uses GoldenEye.Events.External✕
- Connections
- 1 pair of types, where a type in GoldenEye.Events uses a type in GoldenEye.Events.External.
- The types involved
GoldenEye.Events.EventBus→GoldenEye.Events.External.IExternalEventProducer
- Direction
- GoldenEye.Events uses GoldenEye.Events.External, so a change to GoldenEye.Events.External can break GoldenEye.Events, while a change to GoldenEye.Events can't break GoldenEye.Events.External.
- Position
- Below the diagonal: GoldenEye.Events uses a module listed above it, which is the healthy direction.
30→1 GoldenEye.Kafka.Consumers uses Core.Streaming.Kafka.Consumers✕
- Connections
- 1 pair of types, where a type in GoldenEye.Kafka.Consumers uses a type in Core.Streaming.Kafka.Consumers.
- The types involved
GoldenEye.Kafka.Consumers.KafkaConsumer→Core.Streaming.Kafka.Consumers.KafkaConsumerConfig
- Direction
- GoldenEye.Kafka.Consumers uses Core.Streaming.Kafka.Consumers, so a change to Core.Streaming.Kafka.Consumers can break GoldenEye.Kafka.Consumers, while a change to GoldenEye.Kafka.Consumers can't break Core.Streaming.Kafka.Consumers.
- Position
- Below the diagonal: GoldenEye.Kafka.Consumers uses a module listed above it, which is the healthy direction.
30→23 GoldenEye.Kafka.Consumers uses GoldenEye.Events.External✕
- Connections
- 1 pair of types, where a type in GoldenEye.Kafka.Consumers uses a type in GoldenEye.Events.External.
- The types involved
GoldenEye.Kafka.Consumers.KafkaConsumer→GoldenEye.Events.External.IExternalEventConsumer
- Direction
- GoldenEye.Kafka.Consumers uses GoldenEye.Events.External, so a change to GoldenEye.Events.External can break GoldenEye.Kafka.Consumers, while a change to GoldenEye.Kafka.Consumers can't break GoldenEye.Events.External.
- Position
- Below the diagonal: GoldenEye.Kafka.Consumers uses a module listed above it, which is the healthy direction.
31→19 GoldenEye.Aggregates uses GoldenEye.Objects.Versioning✕
- Connections
- 1 pair of types, where a type in GoldenEye.Aggregates uses a type in GoldenEye.Objects.Versioning.
- The types involved
GoldenEye.Aggregates.IAggregate→GoldenEye.Objects.Versioning.IHaveVersion
- Direction
- GoldenEye.Aggregates uses GoldenEye.Objects.Versioning, so a change to GoldenEye.Objects.Versioning can break GoldenEye.Aggregates, while a change to GoldenEye.Aggregates can't break GoldenEye.Objects.Versioning.
- Position
- Below the diagonal: GoldenEye.Aggregates uses a module listed above it, which is the healthy direction.
31→22 GoldenEye.Aggregates uses GoldenEye.Entities✕
- Connections
- 1 pair of types, where a type in GoldenEye.Aggregates uses a type in GoldenEye.Entities.
- The types involved
GoldenEye.Aggregates.IAggregate→GoldenEye.Entities.IEntity
- Direction
- GoldenEye.Aggregates uses GoldenEye.Entities, so a change to GoldenEye.Entities can break GoldenEye.Aggregates, while a change to GoldenEye.Aggregates can't break GoldenEye.Entities.
- Position
- Below the diagonal: GoldenEye.Aggregates uses a module listed above it, which is the healthy direction.
31→29 GoldenEye.Aggregates uses GoldenEye.Events✕
- Connections
- 2 pairs of types, where a type in GoldenEye.Aggregates uses a type in GoldenEye.Events.
- The types involved
GoldenEye.Aggregates.Aggregate→GoldenEye.Events.IEventGoldenEye.Aggregates.IAggregate→GoldenEye.Events.IEvent
- Direction
- GoldenEye.Aggregates uses GoldenEye.Events, so a change to GoldenEye.Events can break GoldenEye.Aggregates, while a change to GoldenEye.Aggregates can't break GoldenEye.Events.
- Position
- Below the diagonal: GoldenEye.Aggregates uses a module listed above it, which is the healthy direction.
32→22 GoldenEye.Context.SaveChangesHandlers uses GoldenEye.Entities✕
- Connections
- 3 pairs of types, where a type in GoldenEye.Context.SaveChangesHandlers uses a type in GoldenEye.Entities.
- The types involved
GoldenEye.Context.SaveChangesHandlers.AuditInfoSaveChangesHandler→GoldenEye.Entities.IProvidesAuditInfoGoldenEye.Context.SaveChangesHandlers.ISaveChangesProcessor→GoldenEye.Entities.IProvidesAuditInfoGoldenEye.Context.SaveChangesHandlers.SaveChangesProcessor→GoldenEye.Entities.IProvidesAuditInfo
- Direction
- GoldenEye.Context.SaveChangesHandlers uses GoldenEye.Entities, so a change to GoldenEye.Entities can break GoldenEye.Context.SaveChangesHandlers, while a change to GoldenEye.Context.SaveChangesHandlers can't break GoldenEye.Entities.
- Position
- Below the diagonal: GoldenEye.Context.SaveChangesHandlers uses a module listed above it, which is the healthy direction.
32→28 GoldenEye.Context.SaveChangesHandlers uses GoldenEye.Context.SaveChangesHandlers.Base✕
- Connections
- 3 pairs of types, where a type in GoldenEye.Context.SaveChangesHandlers uses a type in GoldenEye.Context.SaveChangesHandlers.Base.
- The types involved
GoldenEye.Context.SaveChangesHandlers.AuditInfoSaveChangesHandler→GoldenEye.Context.SaveChangesHandlers.Base.ISaveChangesHandlerGoldenEye.Context.SaveChangesHandlers.ISaveChangesProcessor→GoldenEye.Context.SaveChangesHandlers.Base.ISaveChangesHandlerGoldenEye.Context.SaveChangesHandlers.SaveChangesProcessor→GoldenEye.Context.SaveChangesHandlers.Base.ISaveChangesHandler
- Direction
- GoldenEye.Context.SaveChangesHandlers uses GoldenEye.Context.SaveChangesHandlers.Base, so a change to GoldenEye.Context.SaveChangesHandlers.Base can break GoldenEye.Context.SaveChangesHandlers, while a change to GoldenEye.Context.SaveChangesHandlers can't break GoldenEye.Context.SaveChangesHandlers.Base.
- Position
- Below the diagonal: GoldenEye.Context.SaveChangesHandlers uses a module listed above it, which is the healthy direction.
33→29 GoldenEye.Events.Store uses GoldenEye.Events✕
- Connections
- 3 pairs of types, where a type in GoldenEye.Events.Store uses a type in GoldenEye.Events.
- The types involved
GoldenEye.Events.Store.EventStorePipeline→GoldenEye.Events.IEventHandlerGoldenEye.Events.Store.IEventStore→GoldenEye.Events.IEventGoldenEye.Events.Store.IEventStoreExtensions→GoldenEye.Events.IEvent
- Direction
- GoldenEye.Events.Store uses GoldenEye.Events, so a change to GoldenEye.Events can break GoldenEye.Events.Store, while a change to GoldenEye.Events.Store can't break GoldenEye.Events.
- Position
- Below the diagonal: GoldenEye.Events.Store uses a module listed above it, which is the healthy direction.
34→2 GoldenEye.Kafka.Producers uses Core.Streaming.Kafka.Producers✕
- Connections
- 1 pair of types, where a type in GoldenEye.Kafka.Producers uses a type in Core.Streaming.Kafka.Producers.
- The types involved
GoldenEye.Kafka.Producers.KafkaProducer→Core.Streaming.Kafka.Producers.KafkaProducerConfig
- Direction
- GoldenEye.Kafka.Producers uses Core.Streaming.Kafka.Producers, so a change to Core.Streaming.Kafka.Producers can break GoldenEye.Kafka.Producers, while a change to GoldenEye.Kafka.Producers can't break Core.Streaming.Kafka.Producers.
- Position
- Below the diagonal: GoldenEye.Kafka.Producers uses a module listed above it, which is the healthy direction.
34→23 GoldenEye.Kafka.Producers uses GoldenEye.Events.External✕
- Connections
- 1 pair of types, where a type in GoldenEye.Kafka.Producers uses a type in GoldenEye.Events.External.
- The types involved
GoldenEye.Kafka.Producers.KafkaProducer→GoldenEye.Events.External.IExternalEventProducer
- Direction
- GoldenEye.Kafka.Producers uses GoldenEye.Events.External, so a change to GoldenEye.Events.External can break GoldenEye.Kafka.Producers, while a change to GoldenEye.Kafka.Producers can't break GoldenEye.Events.External.
- Position
- Below the diagonal: GoldenEye.Kafka.Producers uses a module listed above it, which is the healthy direction.
34→29 GoldenEye.Kafka.Producers uses GoldenEye.Events✕
- Connections
- 1 pair of types, where a type in GoldenEye.Kafka.Producers uses a type in GoldenEye.Events.
- The types involved
GoldenEye.Kafka.Producers.KafkaProducer→GoldenEye.Events.IExternalEvent
- Direction
- GoldenEye.Kafka.Producers uses GoldenEye.Events, so a change to GoldenEye.Events can break GoldenEye.Kafka.Producers, while a change to GoldenEye.Kafka.Producers can't break GoldenEye.Events.
- Position
- Below the diagonal: GoldenEye.Kafka.Producers uses a module listed above it, which is the healthy direction.
35→29 GoldenEye.Events.Aggregate uses GoldenEye.Events✕
- Connections
- 4 pairs of types, where a type in GoldenEye.Events.Aggregate uses a type in GoldenEye.Events.
- The types involved
GoldenEye.Events.Aggregate.AggregateEventsPublisher→GoldenEye.Events.IEventGoldenEye.Events.Aggregate.AggregateEventsPublisher→GoldenEye.Events.IEventBusGoldenEye.Events.Aggregate.IAggregateEventsPublisher→GoldenEye.Events.IEventGoldenEye.Events.Aggregate.NulloAggregateEventsPublisher→GoldenEye.Events.IEvent
- Direction
- GoldenEye.Events.Aggregate uses GoldenEye.Events, so a change to GoldenEye.Events can break GoldenEye.Events.Aggregate, while a change to GoldenEye.Events.Aggregate can't break GoldenEye.Events.
- Position
- Below the diagonal: GoldenEye.Events.Aggregate uses a module listed above it, which is the healthy direction.
35→31 GoldenEye.Events.Aggregate uses GoldenEye.Aggregates✕
- Connections
- 3 pairs of types, where a type in GoldenEye.Events.Aggregate uses a type in GoldenEye.Aggregates.
- The types involved
GoldenEye.Events.Aggregate.AggregateEventsPublisher→GoldenEye.Aggregates.IAggregateGoldenEye.Events.Aggregate.IAggregateEventsPublisher→GoldenEye.Aggregates.IAggregateGoldenEye.Events.Aggregate.NulloAggregateEventsPublisher→GoldenEye.Aggregates.IAggregate
- Direction
- GoldenEye.Events.Aggregate uses GoldenEye.Aggregates, so a change to GoldenEye.Aggregates can break GoldenEye.Events.Aggregate, while a change to GoldenEye.Events.Aggregate can't break GoldenEye.Aggregates.
- Position
- Below the diagonal: GoldenEye.Events.Aggregate uses a module listed above it, which is the healthy direction.
36→29 GoldenEye.Marten.Events.Storage uses GoldenEye.Events✕
- Connections
- 1 pair of types, where a type in GoldenEye.Marten.Events.Storage uses a type in GoldenEye.Events.
- The types involved
GoldenEye.Marten.Events.Storage.MartenEventStore→GoldenEye.Events.IEvent
- Direction
- GoldenEye.Marten.Events.Storage uses GoldenEye.Events, so a change to GoldenEye.Events can break GoldenEye.Marten.Events.Storage, while a change to GoldenEye.Marten.Events.Storage can't break GoldenEye.Events.
- Position
- Below the diagonal: GoldenEye.Marten.Events.Storage uses a module listed above it, which is the healthy direction.
36→33 GoldenEye.Marten.Events.Storage uses GoldenEye.Events.Store✕
- Connections
- 1 pair of types, where a type in GoldenEye.Marten.Events.Storage uses a type in GoldenEye.Events.Store.
- The types involved
GoldenEye.Marten.Events.Storage.MartenEventStore→GoldenEye.Events.Store.IEventStore
- Direction
- GoldenEye.Marten.Events.Storage uses GoldenEye.Events.Store, so a change to GoldenEye.Events.Store can break GoldenEye.Marten.Events.Storage, while a change to GoldenEye.Marten.Events.Storage can't break GoldenEye.Events.Store.
- Position
- Below the diagonal: GoldenEye.Marten.Events.Storage uses a module listed above it, which is the healthy direction.
37→20 GoldenEye.Dapper.Repositories uses GoldenEye.Repositories✕
- Connections
- 1 pair of types, where a type in GoldenEye.Dapper.Repositories uses a type in GoldenEye.Repositories.
- The types involved
GoldenEye.Dapper.Repositories.DapperRepository→GoldenEye.Repositories.IRepository
- Direction
- GoldenEye.Dapper.Repositories uses GoldenEye.Repositories, so a change to GoldenEye.Repositories can break GoldenEye.Dapper.Repositories, while a change to GoldenEye.Dapper.Repositories can't break GoldenEye.Repositories.
- Position
- Below the diagonal: GoldenEye.Dapper.Repositories uses a module listed above it, which is the healthy direction.
37→21 GoldenEye.Dapper.Repositories uses GoldenEye.Dapper.Generators✕
- Connections
- 1 pair of types, where a type in GoldenEye.Dapper.Repositories uses a type in GoldenEye.Dapper.Generators.
- The types involved
GoldenEye.Dapper.Repositories.DapperRepository→GoldenEye.Dapper.Generators.IDapperSqlGenerator
- Direction
- GoldenEye.Dapper.Repositories uses GoldenEye.Dapper.Generators, so a change to GoldenEye.Dapper.Generators can break GoldenEye.Dapper.Repositories, while a change to GoldenEye.Dapper.Repositories can't break GoldenEye.Dapper.Generators.
- Position
- Below the diagonal: GoldenEye.Dapper.Repositories uses a module listed above it, which is the healthy direction.
37→35 GoldenEye.Dapper.Repositories uses GoldenEye.Events.Aggregate✕
- Connections
- 1 pair of types, where a type in GoldenEye.Dapper.Repositories uses a type in GoldenEye.Events.Aggregate.
- The types involved
GoldenEye.Dapper.Repositories.DapperRepository→GoldenEye.Events.Aggregate.IAggregateEventsPublisher
- Direction
- GoldenEye.Dapper.Repositories uses GoldenEye.Events.Aggregate, so a change to GoldenEye.Events.Aggregate can break GoldenEye.Dapper.Repositories, while a change to GoldenEye.Dapper.Repositories can't break GoldenEye.Events.Aggregate.
- Position
- Below the diagonal: GoldenEye.Dapper.Repositories uses a module listed above it, which is the healthy direction.
38→20 GoldenEye.ElasticSearch.Repositories uses GoldenEye.Repositories✕
- Connections
- 1 pair of types, where a type in GoldenEye.ElasticSearch.Repositories uses a type in GoldenEye.Repositories.
- The types involved
GoldenEye.ElasticSearch.Repositories.ElasticSearchRepository→GoldenEye.Repositories.IRepository
- Direction
- GoldenEye.ElasticSearch.Repositories uses GoldenEye.Repositories, so a change to GoldenEye.Repositories can break GoldenEye.ElasticSearch.Repositories, while a change to GoldenEye.ElasticSearch.Repositories can't break GoldenEye.Repositories.
- Position
- Below the diagonal: GoldenEye.ElasticSearch.Repositories uses a module listed above it, which is the healthy direction.
38→35 GoldenEye.ElasticSearch.Repositories uses GoldenEye.Events.Aggregate✕
- Connections
- 1 pair of types, where a type in GoldenEye.ElasticSearch.Repositories uses a type in GoldenEye.Events.Aggregate.
- The types involved
GoldenEye.ElasticSearch.Repositories.ElasticSearchRepository→GoldenEye.Events.Aggregate.IAggregateEventsPublisher
- Direction
- GoldenEye.ElasticSearch.Repositories uses GoldenEye.Events.Aggregate, so a change to GoldenEye.Events.Aggregate can break GoldenEye.ElasticSearch.Repositories, while a change to GoldenEye.ElasticSearch.Repositories can't break GoldenEye.Events.Aggregate.
- Position
- Below the diagonal: GoldenEye.ElasticSearch.Repositories uses a module listed above it, which is the healthy direction.
39→20 GoldenEye.EntityFramework.Repositories uses GoldenEye.Repositories✕
- Connections
- 2 pairs of types, where a type in GoldenEye.EntityFramework.Repositories uses a type in GoldenEye.Repositories.
- The types involved
GoldenEye.EntityFramework.Repositories.EntityFrameworkRepository→GoldenEye.Repositories.IReadonlyRepositoryGoldenEye.EntityFramework.Repositories.EntityFrameworkRepository→GoldenEye.Repositories.IRepository
- Direction
- GoldenEye.EntityFramework.Repositories uses GoldenEye.Repositories, so a change to GoldenEye.Repositories can break GoldenEye.EntityFramework.Repositories, while a change to GoldenEye.EntityFramework.Repositories can't break GoldenEye.Repositories.
- Position
- Below the diagonal: GoldenEye.EntityFramework.Repositories uses a module listed above it, which is the healthy direction.
39→35 GoldenEye.EntityFramework.Repositories uses GoldenEye.Events.Aggregate✕
- Connections
- 1 pair of types, where a type in GoldenEye.EntityFramework.Repositories uses a type in GoldenEye.Events.Aggregate.
- The types involved
GoldenEye.EntityFramework.Repositories.EntityFrameworkRepository→GoldenEye.Events.Aggregate.IAggregateEventsPublisher
- Direction
- GoldenEye.EntityFramework.Repositories uses GoldenEye.Events.Aggregate, so a change to GoldenEye.Events.Aggregate can break GoldenEye.EntityFramework.Repositories, while a change to GoldenEye.EntityFramework.Repositories can't break GoldenEye.Events.Aggregate.
- Position
- Below the diagonal: GoldenEye.EntityFramework.Repositories uses a module listed above it, which is the healthy direction.
40→20 GoldenEye.Marten.Repositories uses GoldenEye.Repositories✕
- Connections
- 4 pairs of types, where a type in GoldenEye.Marten.Repositories uses a type in GoldenEye.Repositories.
- The types involved
GoldenEye.Marten.Repositories.MartenDocumentRepository→GoldenEye.Repositories.IReadonlyRepositoryGoldenEye.Marten.Repositories.MartenDocumentRepository→GoldenEye.Repositories.IRepositoryGoldenEye.Marten.Repositories.MartenEventSourcedRepository→GoldenEye.Repositories.IReadonlyRepositoryGoldenEye.Marten.Repositories.MartenEventSourcedRepository→GoldenEye.Repositories.IRepository
- Direction
- GoldenEye.Marten.Repositories uses GoldenEye.Repositories, so a change to GoldenEye.Repositories can break GoldenEye.Marten.Repositories, while a change to GoldenEye.Marten.Repositories can't break GoldenEye.Repositories.
- Position
- Below the diagonal: GoldenEye.Marten.Repositories uses a module listed above it, which is the healthy direction.
40→33 GoldenEye.Marten.Repositories uses GoldenEye.Events.Store✕
- Connections
- 1 pair of types, where a type in GoldenEye.Marten.Repositories uses a type in GoldenEye.Events.Store.
- The types involved
GoldenEye.Marten.Repositories.MartenEventSourcedRepository→GoldenEye.Events.Store.IEventStore
- Direction
- GoldenEye.Marten.Repositories uses GoldenEye.Events.Store, so a change to GoldenEye.Events.Store can break GoldenEye.Marten.Repositories, while a change to GoldenEye.Marten.Repositories can't break GoldenEye.Events.Store.
- Position
- Below the diagonal: GoldenEye.Marten.Repositories uses a module listed above it, which is the healthy direction.
40→35 GoldenEye.Marten.Repositories uses GoldenEye.Events.Aggregate✕
- Connections
- 2 pairs of types, where a type in GoldenEye.Marten.Repositories uses a type in GoldenEye.Events.Aggregate.
- The types involved
GoldenEye.Marten.Repositories.MartenDocumentRepository→GoldenEye.Events.Aggregate.IAggregateEventsPublisherGoldenEye.Marten.Repositories.MartenEventSourcedRepository→GoldenEye.Events.Aggregate.IAggregateEventsPublisher
- Direction
- GoldenEye.Marten.Repositories uses GoldenEye.Events.Aggregate, so a change to GoldenEye.Events.Aggregate can break GoldenEye.Marten.Repositories, while a change to GoldenEye.Marten.Repositories can't break GoldenEye.Events.Aggregate.
- Position
- Below the diagonal: GoldenEye.Marten.Repositories uses a module listed above it, which is the healthy direction.
40→36 GoldenEye.Marten.Repositories uses GoldenEye.Marten.Events.Storage✕
- Connections
- 1 pair of types, where a type in GoldenEye.Marten.Repositories uses a type in GoldenEye.Marten.Events.Storage.
- The types involved
GoldenEye.Marten.Repositories.MartenEventSourcedRepository→GoldenEye.Marten.Events.Storage.MartenEventStore
- Direction
- GoldenEye.Marten.Repositories uses GoldenEye.Marten.Events.Storage, so a change to GoldenEye.Marten.Events.Storage can break GoldenEye.Marten.Repositories, while a change to GoldenEye.Marten.Repositories can't break GoldenEye.Marten.Events.Storage.
- Position
- Below the diagonal: GoldenEye.Marten.Repositories 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 — Event-Driven
At a glance — Event Sourcing
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 19 | High / Critical |
| A05:2025 — Injection | 14 | High / Critical |
| A07:2025 — Authentication Failures | 5 | High / Critical |
Roadmap
Top priorities: Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with Registration.cs (4), DateTimeExtensions.cs, RegistrationExtensions.cs; Reconcile the README with reality: src/Core/Core/Readme.md links to `Validation/Readme.md`, but `src/Core/Core/Validation/Readme.md` does not exist; src/Core/Core/Readme.md links to `Extensions/Exceptions/ExceptionExtensions.cs`, but `src/Core/Core/Extensions/Exceptions/ExceptionExtensions.cs` does not exist; src/Core/Core/Readme.md links to `Extensions/Mapping/AutoMapperExtensions.cs`, but `src/Core/Core/Extensions/Mapping/AutoMapperExtensions.cs` does not exist; src/Core/Core/Readme.md links to `Utils/Cryptography/Encryption.cs`, but `src/Core/Core/Utils/Cryptography/Encryption.cs` does not exist; src/Core/Core/Readme.md links to `Utils/Lambda/PropertyName.cs`, but `src/Core/Core/Utils/Lambda/PropertyName.cs` does not exist; Resolve the 2 redundant comment finding(s) in Comment Value — start with Memoizer.cs, ExpressionExtensions.cs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 redundant comment finding(s) in Comment Value — start with Memoizer.cs, ExpressionExtensions.cs. | +5.8 pts | Low | Comment Value |
| Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED. | +5.1 pts | Low | Secret Scanning |
| Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with Registration.cs (4), DateTimeExtensions.cs, RegistrationExtensions.cs. | +8.0 pts | Medium | Knowledge Freshness |
| Reconcile the README with reality: src/Core/Core/Readme.md links to `Validation/Readme.md`, but `src/Core/Core/Validation/Readme.md` does not exist; src/Core/Core/Readme.md links to `Extensions/Exceptions/ExceptionExtensions.cs`, but `src/Core/Core/Extensions/Exceptions/ExceptionExtensions.cs` does not exist; src/Core/Core/Readme.md links to `Extensions/Mapping/AutoMapperExtensions.cs`, but `src/Core/Core/Extensions/Mapping/AutoMapperExtensions.cs` does not exist; src/Core/Core/Readme.md links to `Utils/Cryptography/Encryption.cs`, but `src/Core/Core/Utils/Cryptography/Encryption.cs` does not exist; src/Core/Core/Readme.md links to `Utils/Lambda/PropertyName.cs`, but `src/Core/Core/Utils/Lambda/PropertyName.cs` does not exist. | +6.3 pts | Medium | Documentation accuracy |
| 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. | +5.1 pts | Medium | Architecture documentation |
| 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. | +3.3 pts | Medium | Security & performance tooling |
| Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with CancelReservationTests.cs (2). | +1.7 pts | Low | Test Quality |
| Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult(). | +2.1 pts | Medium | Async & latency hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.9 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| src/Marten/Marten/Marten.csproj | 5.5 | Mixed | Explicit Debt: NoWarnInCsproj |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| samples/DDD/Tickets/Tickets.Tests/Reservations/CancellingReservation/CancelReservationTests.cs | 7.0 | Mixed | Test Quality: No assertions (empty test): ForConfirmedReservation_ShouldFailWithInvalidOperation |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| src/Core/Core/Extensions/Enums/EnumExtensions.cs | 7.3 | Mixed | Explicit Debt: CommentedOutCode |
| src/Core/Core/Core.csproj | 7.4 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| samples/DDD/Tickets/Tickets.Api.Tests/Tickets.Api.Tests.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| samples/DDD/Tickets/Tickets.Api/Tickets.Api.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| samples/DDD/Tickets/Tickets.Tests/Tickets.Tests.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| samples/DDD/Tickets/Tickets/Tickets.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| samples/GoldenEye.WebApi.Sample/GoldenEye.WebApi.Sample.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
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 81 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 — 81 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, 201 of 230 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (13 contributor(s) across 650 commit(s) sampled, automation and bot accounts excluded). One of them holds 84% of the history; the other 12 hold 1.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and 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: Found project with the same file path and output path as another project: src/Marten/Marten/Marten.csproj.
- 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.
- D39 IL Efficiency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Idempotency could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: Syntax node is not within syntax tree.
- ES3 PII in the event store — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- PF3 Async & latency hygiene — 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. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (24 lines × 2) finding(s) in Code Duplication — start with ExpressionExtensions.cs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
24 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 24 classes have LCOM4 above 3.
D9 · Test Distribution
62 test methods: 59 unit, 3 integration, 0 BDD, 0 e2e.
D10 · Test Quality
1 skipped (1 with a documented reason), 2 zero-assertion, 13 mock references across 62 tests.
What to do
- Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with CancelReservationTests.cs (2). — One of this dimension's main actionable groups (2 issue-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 3 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky); other: measured (0 flaky).
D13 · Secret Scanning
3 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 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 339 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 38 direct `PackageReference`(s), and 212 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
8 deducted debt markers + unmeasured dead symbols across 6758 LoC in the .NET projects (0.3/KLoC) → score 9.4. 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 Marten.csproj. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 5 CommentedOutCode finding(s) in Explicit Debt — start with EnumExtensions.cs (2), ObjectExtensions.cs, ListResponse.cs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with ListExtensions.cs, EntityFrameworkRepository.cs. — One of this dimension's main actionable groups (2 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
25 projects, 259 source files, 9505 hand-written lines of code (6758 production / 2747 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 105 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 33 inter-project edges.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 12 document(s) read across 8 unit(s).
D24 · Comment Value
2 of 56 judged comments only repeat the code they sit on (3.6 %). 1 comment(s) in another language or script were not judged.
What to do
- Resolve the 2 redundant comment finding(s) in Comment Value — start with Memoizer.cs, ExpressionExtensions.cs. — One of this dimension's main actionable groups (2 recommendation-level).
D26 · Project Cohesion
1 of 24 projects flagged as possibly oversized/incoherent.
D27 · Navigability
90 % of calls cross a namespace and 9 % go through an interface, but 92 % 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)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
14 finding(s): 0 critical, 2 high, 12 medium, 0 low. 2 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 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).
D31 · IaC & Container Security
19 finding(s): 0 critical, 6 high, 13 medium, 0 low.
What to do
- Resolve the 13 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (10), REDACTED (3). — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 6 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
D34 · Knowledge Freshness
26 of 26 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Core/Core/Extensions/Basic/DateTimeExtensions.cs. Counted over 26 of the 162 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with Registration.cs (4), DateTimeExtensions.cs, RegistrationExtensions.cs. — One of this dimension's main actionable groups (26 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 24 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 24 End-of-life runtime finding(s) in Platform End-of-Life — start with Tickets.Api.Tests.csproj, Tickets.Api.csproj, Tickets.Tests.csproj. — One of this dimension's main actionable groups (24 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, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `UserInfoProvider` keeps one instance of itself in the static `Instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_userInfo; e.g. `_userInfo` at line 11). — src/Core/Core/Security/UserInfoProvider.cs:3
- `DateTimeExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_allDatesInCurrentYear; e.g. `_allDatesInCurrentYear` at line 33). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Core/Core/Extensions/Basic/DateTimeExtensions.cs:9
- `ReflectionExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_assemblies; e.g. `_assemblies` at line 22). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Core/Core/Extensions/Reflection/ReflectionExtensions.cs:11
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces GoldenEye.Events ↔ GoldenEye.Events.External depend on each other. The lightest dependency in the cycle is GoldenEye.Events → GoldenEye.Events.External (GoldenEye.Events.EventBus → GoldenEye.Events.External.IExternalEventProducer, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Core/Core/Events/EventBus.cs:5
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
ED1 · Handler temporal coupling
ED2 · Event/command shape
ED3 · Event naming
ED4 · Outbox / dual-write
- `EntityFrameworkRepository.SaveChanges` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs:102
- `MartenDocumentRepository.SaveChanges` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Marten/Marten/Repositories/MartenDocumentRepository.cs:124
- `MartenEventSourcedRepository.SaveChanges` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Marten/Marten/Repositories/MartenEventSourcedRepository.cs:80
What to do
- Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
ES1 · Fold determinism
ES2 · Immutable events
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs:42
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- `Query` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs:42
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×6) — src/Core/Core/Extensions/Basic/ObjectExtensions.cs:47, src/Core/Core/Extensions/Enums/EnumExtensions.cs:29, src/Core/Core/Extensions/Enums/EnumExtensions.cs:30, …
- A test is skipped ("somehow it does not work on AppVeyor") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — src/EntityFramework/EntityFramework.Integration.Tests/Repositories/EntityFrameworkRepositoryTests.cs:17
What to do
- Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 10 project(s) that lack one — worth up to 0.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.
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.
M3 · Folder & project structure
- Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
What to do
- Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
M4 · Documentation accuracy
- src/Core/Core/Readme.md links to `Validation/Readme.md`, but `src/Core/Core/Validation/Readme.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/Core/Readme.md:19
- src/Core/Core/Readme.md links to `Extensions/Exceptions/ExceptionExtensions.cs`, but `src/Core/Core/Extensions/Exceptions/ExceptionExtensions.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/Core/Readme.md:41
- src/Core/Core/Readme.md links to `Extensions/Mapping/AutoMapperExtensions.cs`, but `src/Core/Core/Extensions/Mapping/AutoMapperExtensions.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/Core/Readme.md:45
- src/Core/Core/Readme.md links to `Utils/Cryptography/Encryption.cs`, but `src/Core/Core/Utils/Cryptography/Encryption.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/Core/Readme.md:57
- src/Core/Core/Readme.md links to `Utils/Lambda/PropertyName.cs`, but `src/Core/Core/Utils/Lambda/PropertyName.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/Core/Readme.md:61
- src/Core/Core/Readme.md links to `Utils/Localization/LocalizationUtils.cs`, but `src/Core/Core/Utils/Localization/LocalizationUtils.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/Core/Readme.md:62
- src/Core/Core/Readme.md links to `Utils/Localization/DisplayNameLocalizedAttribute.cs`, but `src/Core/Core/Utils/Localization/DisplayNameLocalizedAttribute.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Core/Core/Readme.md:63
- src/Dapper/Dapper/Readme.md links to `LICENSE.txt`, but `src/Dapper/Dapper/LICENSE.txt` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Dapper/Dapper/Readme.md:28
- src/ElasticSearch/ElasticSearch/Readme.md links to `LICENSE.txt`, but `src/ElasticSearch/ElasticSearch/LICENSE.txt` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/ElasticSearch/ElasticSearch/Readme.md:28
- src/EntityFramework/EntityFramework/Readme.md links to `LICENSE.txt`, but `src/EntityFramework/EntityFramework/LICENSE.txt` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/EntityFramework/EntityFramework/Readme.md:29
- src/Kafka/Kafka/Readme.md links to `LICENSE.txt`, but `src/Kafka/Kafka/LICENSE.txt` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Kafka/Kafka/Readme.md:28
- src/Marten/Marten/Readme.md links to `LICENSE.txt`, but `src/Marten/Marten/LICENSE.txt` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/Marten/Marten/Readme.md:30
- src/WebApi/WebApi.Tests/Readme.md links to `../Backend.Core.WebApi/Exceptions/ExceptionHandlingMiddleware.cs`, but `src/WebApi/Backend.Core.WebApi/Exceptions/ExceptionHandlingMiddleware.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/WebApi/WebApi.Tests/Readme.md:12
- src/WebApi/WebApi.Tests/Readme.md links to `LICENSE.txt`, but `src/WebApi/WebApi.Tests/LICENSE.txt` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/WebApi/WebApi.Tests/Readme.md:22
- src/WebApi/WebApi/Readme.md links to `LICENSE.txt`, but `src/WebApi/WebApi/LICENSE.txt` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/WebApi/WebApi/Readme.md:32
What to do
- Reconcile the README with reality: src/Core/Core/Readme.md links to `Validation/Readme.md`, but `src/Core/Core/Validation/Readme.md` does not exist; src/Core/Core/Readme.md links to `Extensions/Exceptions/ExceptionExtensions.cs`, but `src/Core/Core/Extensions/Exceptions/ExceptionExtensions.cs` does not exist; src/Core/Core/Readme.md links to `Extensions/Mapping/AutoMapperExtensions.cs`, but `src/Core/Core/Extensions/Mapping/AutoMapperExtensions.cs` does not exist; src/Core/Core/Readme.md links to `Utils/Cryptography/Encryption.cs`, but `src/Core/Core/Utils/Cryptography/Encryption.cs` does not exist; src/Core/Core/Readme.md links to `Utils/Lambda/PropertyName.cs`, but `src/Core/Core/Utils/Lambda/PropertyName.cs` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
- 196/199 types (98%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
What to do
- Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
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 950 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:7
- `samples/DDD/Tickets/Tickets.Api.Tests/Tickets.Api.Tests.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — samples/DDD/Tickets/Tickets.Api.Tests/Tickets.Api.Tests.csproj:12
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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
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.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- Outbound HTTP calls were found with no timeout or retry policy around them. This codebase ships libraries/tools rather than a service it operates, so the failure lands differently: an unbounded call hangs the caller's process — a build step, a CLI run, a UI thread — with no way out.
What to do
- Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
P8 · Schema migrations
PF1 · Benchmark discipline
- No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
- Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene
- 1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
- `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — src/Marten/Marten/Registration/Registration.cs:79
- Only 0/82 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
- `await mediator.Publish(@event, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Events/EventBus.cs:27
- `await externalEventProducer.Publish(externalEvent, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Events/EventBus.cs:31
- `await Publish(@event, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Events/EventBus.cs:39
- `await Task.WhenAny(executingTask, Task.Delay(-1, cancellationToken))` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Events/External/ExternalEventConsumerBackgroundWorker.cs:52
- `await eventStore.Append(@event.StreamId, cancellationToken, @event)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Events/Store/EventStorePipeline.cs:19
- `await eventStore.SaveChanges(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Events/Store/EventStorePipeline.cs:20
- `await content.ReadAsStringAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Extensions/Serialization/SerializationExtensions.cs:49
- `await repository.FindById(id, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Core/Core/Repositories/ReadonlyRepositoryExtensions.cs:20, src/Core/Core/Repositories/RepositoryExtensions.cs:72
- `await repository.Add(entity, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Repositories/RepositoryExtensions.cs:30
- `await repository.GetById(id, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Repositories/RepositoryExtensions.cs:85
- `await repository.Update(entity, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Repositories/RepositoryExtensions.cs:89
- `await ValidateAsync(dto, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Core/Core/Services/CRUDService.cs:53, src/Core/Core/Services/CRUDService.cs:68
- `await ValidateAsync(entity, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Core/Core/Services/CRUDService.cs:57, src/Core/Core/Services/CRUDService.cs:74
- `await Repository.SaveChanges(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/Core/Core/Services/CRUDService.cs:61, src/Core/Core/Services/CRUDService.cs:78
- `await Repository.GetById(id, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Services/CRUDService.cs:70
- `await Repository.Update(entity, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Services/CRUDService.cs:76
- `await (DtoValidator?.ValidateAsync(dto, null, cancellationToken) ?? Task.CompletedT...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Services/CRUDService.cs:90
- `await (EntityValidator?.ValidateAsync(entity, null, cancellationToken) ?? Task.Comp...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Services/CRUDService.cs:95
- `await ReadonlyRepository.GetById(id, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Core/Core/Services/ReadonlyService.cs:48
- `await dbConnection.QuerySingleOrDefaultAsync<TEntity>(sql, new {Id = id})` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Dapper/Dapper/Repositories/DapperRepository.cs:41
- `await dbConnection.GetAsync<TEntity>(id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Dapper/Dapper/Repositories/DapperRepository.cs:43
- `await dbConnection.QueryAsync<TEntity>(query, queryParams.First())` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Dapper/Dapper/Repositories/DapperRepository.cs:64
- `await dbConnection.ExecuteAsync(sql, entity)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×3) — src/Dapper/Dapper/Repositories/DapperRepository.cs:75, src/Dapper/Dapper/Repositories/DapperRepository.cs:95, src/Dapper/Dapper/Repositories/DapperRepository.cs:115
- `await dbConnection.InsertAsync(entity)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Dapper/Dapper/Repositories/DapperRepository.cs:77
- `await dbConnection.UpdateAsync(entity)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Dapper/Dapper/Repositories/DapperRepository.cs:97
- `await dbConnection.DeleteAsync(entity)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Dapper/Dapper/Repositories/DapperRepository.cs:117
- `await dbConnection.ExecuteAsync(sql, id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Dapper/Dapper/Repositories/DapperRepository.cs:135
- `await dbContext.FindAsync<TEntity>(id)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs:34
- `await dbContext.Set<TEntity>().FromSqlRaw(query, queryParams).ToListAsync(cancellat...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs:51
- `await dbContext.AddAsync(entity, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs:59
- `await Delete(await ReadonlyRepositoryExtensions.GetById(this, id, cancellationToken...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs:98
What to do
- Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
- In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
X1 · Async correctness
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. — src/Marten/Marten/Registration/Registration.cs:79
What to do
- Sync-over-async (deadlock risk)
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
- `cts` (line 13) holds a `CancellationTokenSource` that `ExternalEventConsumerBackgroundWorker` acquires itself — every assignment to it is a call that opens or creates a new instance for the caller to own — and nothing in `ExternalEventConsumerBackgroundWorker` ever releases it: the type is not `IDisposable`, declares no `Dispose`, and every other mention of `cts` only reads through it, so it is never disposed, closed, returned or handed on. Whatever it opened (a connection, a channel, a file) stays open until finalization if the type has a finalizer and until the process ends if it does not, once per instance of `ExternalEventConsumerBackgroundWorker`. Implement `IDisposable` and release `cts` there, or take the instance from the caller so its owner ends it. — src/Core/Core/Events/External/ExternalEventConsumerBackgroundWorker.cs:13
- `writer` is a `StreamWriter`, which implements `IDisposable`, and it is created here (line 100). Every use of it in `ToStream` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var writer = …;`), which releases it at the end of the scope on every path including a throw. — src/Core/Core/Extensions/Basic/StringExtensions.cs:100
- `memo` is a `MemoryCache`, which implements `IDisposable`, and it is created here (line 51). Every use of it in `MemoizeWithMemoryCache` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var memo = …;`), which releases it at the end of the scope on every path including a throw. — src/Core/Core/Extensions/Functions/Memoizer.cs:51
- `sw` is a `StreamWriter`, which implements `IDisposable`, and it is created here (line 34). Every use of it in `GetCsvStream` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var sw = …;`), which releases it at the end of the scope on every path including a throw. — src/Core/Core/Utils/Collections/CollectionToCSVConverter.cs:34
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 47/62 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. (×14) — src/Core/Core/Extensions/Serialization/SerializationExtensions.cs:47, src/WebApi/WebApi/Controllers/ReadonlyControllerBase.cs:27, src/WebApi/WebApi/Controllers/RestControllerBase.cs:19, …
- No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. — src/WebApi/WebApi/Exceptions/ExceptionHandlingMiddleware.cs:34
- 2 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). (×2) — src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs:29, src/Kafka/Kafka/Producers/KafkaProducer.cs:28
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
- `x.Name == typeName` picks a type by its SIMPLE name out of `AppDomain.CurrentDomain.GetAssemblies()`, and `FirstOrDefault` then takes whichever one comes first. Neither half of that is decided by this source. `Type.Name` is not unique — the namespace is what separates two types spelled the same way — and the assembly list is in LOAD order, so which `x` wins depends on which code path ran first and changes the moment another assembly contributing a same-named type is loaded. The same value of `typeName` can therefore resolve to different types in two runs of the same binary, and the run that picks the wrong one fails at the cast or the call, far from here. Compare `x.FullName` or `AssemblyQualifiedName`, which the namespace makes unique, or take the matches with `Where` and reject a set of more than one — `typeName` naming two types is a configuration error worth saying out loud, not a coin to flip. — src/Core/Core/Utils/Assemblies/TypeProvider.cs:17
What to do
- Each finding names the comparison that matches on `Type.Name` and the selector that takes the first survivor. Confirm from that span that the searched set is every loaded assembly, then decide which the lookup meant: if the name is meant to identify ONE type, compare `FullName` or `AssemblyQualifiedName`, which the namespace makes unique; if several types may legitimately answer to it, keep them all (`Where`) and reject a set of more than one, so a name that is ambiguous is reported as the configuration error it is instead of resolved by load order.
X4 · Structured logging
- Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×3) — src/WebApi/WebApi/Exceptions/ExceptionHandlingMiddleware.cs:36, src/Kafka/Kafka/Consumers/KafkaConsumer.cs:58, src/Kafka/Kafka/Consumers/KafkaConsumer.cs:92
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 2/10 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
- ~0.7 `!` suppressions per 1k syntax nodes — 3 suppression(s) across the 4582 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 | 60% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 70% | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 33% | Weak — gated by D34, M2, M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 40% | Weak — gated by D13, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 68% | Adequate | Acceptable, with room to improve. |
| Event-Driven | 80% | Strong | Solid. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 51% | Adequate | Acceptable, with room to improve. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- 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 included — 43 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.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1899 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (6,758 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Core), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- 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
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — applicable but not scored (4 signals for this style, 3 needed — the count is met but a required primary signal is absent): 7 aggregate root(s) (AggregateRoot/IAggregateRoot); 6 domain event(s); its 7 aggregate(s) are building blocks, test types or a library's examples — not the repository's own domain; a Domain/Aggregates/ValueObjects layer; 2 aggregate-constrained repository/repositories (IRepository<T> where T : IAggregateRoot); a top-level samples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- ED5 Idempotency — Idempotency could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- ES3 PII in the event store — This check finds persisted events that carry personal data no crypto-shredding strategy covers. It measured 12 of 13 valid (92.3 %) on held-out repositories, below the 95 % it must show (docs/plans/deterministic-engine/adjudication/ES3-H3H4.md), so by the pre-registered fallback (PREREGISTRATION v21) the events it finds are counted here, not reported as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- 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 — 19 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dual write (no outbox): EntityFrameworkRepository.SaveChanges src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs:102
- Dual write (no outbox): MartenDocumentRepository.SaveChanges src/Marten/Marten/Repositories/MartenDocumentRepository.cs:124
- Dual write (no outbox): MartenEventSourcedRepository.SaveChanges src/Marten/Marten/Repositories/MartenEventSourcedRepository.cs:80
- No assertions (empty test): ForConfirmedReservation_ShouldFailWithInvalidOperation samples/DDD/Tickets/Tickets.Tests/Reservations/CancellingReservation/CancelReservationTests.cs:35
- No assertions (empty test): ForCancelledReservation_ShouldFailWithInvalidOperation samples/DDD/Tickets/Tickets.Tests/Reservations/CancellingReservation/CancelReservationTests.cs:41
- REDACTED
- REDACTED
- Namespace dependency cycle src/Core/Core/Events/EventBus.cs:5
- NoWarnInCsproj src/Marten/Marten/Marten.csproj:8
- REDACTED
Serious — 128 finding(s)
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) src/Core/Core/Events/EventBus.cs:27
- Awaits without ConfigureAwait(false) src/Core/Core/Events/EventBus.cs:31
- Awaits without ConfigureAwait(false) src/Core/Core/Events/EventBus.cs:39
- Awaits without ConfigureAwait(false) src/Core/Core/Events/External/ExternalEventConsumerBackgroundWorker.cs:52
- Awaits without ConfigureAwait(false) src/Core/Core/Events/Store/EventStorePipeline.cs:19
- Awaits without ConfigureAwait(false) src/Core/Core/Events/Store/EventStorePipeline.cs:20
- Awaits without ConfigureAwait(false) src/Core/Core/Extensions/Serialization/SerializationExtensions.cs:49
- Awaits without ConfigureAwait(false) src/Core/Core/Repositories/ReadonlyRepositoryExtensions.cs:20
- Awaits without ConfigureAwait(false) src/Core/Core/Repositories/RepositoryExtensions.cs:30
- Awaits without ConfigureAwait(false) src/Core/Core/Repositories/RepositoryExtensions.cs:72
- Awaits without ConfigureAwait(false) src/Core/Core/Repositories/RepositoryExtensions.cs:85
- Awaits without ConfigureAwait(false) src/Core/Core/Repositories/RepositoryExtensions.cs:89
- Awaits without ConfigureAwait(false) src/Core/Core/Services/CRUDService.cs:53
- Awaits without ConfigureAwait(false) src/Core/Core/Services/CRUDService.cs:57
- Awaits without ConfigureAwait(false) src/Core/Core/Services/CRUDService.cs:61
- Awaits without ConfigureAwait(false) src/Core/Core/Services/CRUDService.cs:68
- Awaits without ConfigureAwait(false) src/Core/Core/Services/CRUDService.cs:70
- Awaits without ConfigureAwait(false) src/Core/Core/Services/CRUDService.cs:74
- Awaits without ConfigureAwait(false) src/Core/Core/Services/CRUDService.cs:76
- Awaits without ConfigureAwait(false) src/Core/Core/Services/CRUDService.cs:78
- Awaits without ConfigureAwait(false) src/Core/Core/Services/CRUDService.cs:90
- Awaits without ConfigureAwait(false) src/Core/Core/Services/CRUDService.cs:95
- Awaits without ConfigureAwait(false) src/Core/Core/Services/ReadonlyService.cs:48
- Awaits without ConfigureAwait(false) src/Dapper/Dapper/Repositories/DapperRepository.cs:41
- End-of-life runtime: .NET net6.0 samples/DDD/Tickets/Tickets.Api.Tests/Tickets.Api.Tests.csproj:4
- End-of-life runtime: .NET net6.0 samples/DDD/Tickets/Tickets.Api/Tickets.Api.csproj:4
- End-of-life runtime: .NET net6.0 samples/DDD/Tickets/Tickets.Tests/Tickets.Tests.csproj:4
- End-of-life runtime: .NET net6.0 samples/DDD/Tickets/Tickets/Tickets.csproj:4
- End-of-life runtime: .NET net6.0 samples/GoldenEye.WebApi.Sample/GoldenEye.WebApi.Sample.csproj:4
- End-of-life runtime: .NET net6.0 src/Core/Core.Tests.External/Core.Tests.External.csproj:4
- End-of-life runtime: .NET net6.0 src/Core/Core.Tests/Core.Tests.csproj:4
- End-of-life runtime: .NET net6.0 src/Core/Core/Core.csproj:4
- End-of-life runtime: .NET net6.0 src/Dapper/Dapper.Integration.Tests/Dapper.Integration.Tests.csproj:4
- End-of-life runtime: .NET net6.0 src/Dapper/Dapper.Tests/Dapper.Tests.csproj:4
- End-of-life runtime: .NET net6.0 src/Dapper/Dapper/Dapper.csproj:4
- End-of-life runtime: .NET net6.0 src/ElasticSearch/ElasticSearch.Integration.Tests/ElasticSearch.Integration.Tests.csproj:4
- End-of-life runtime: .NET net6.0 src/ElasticSearch/ElasticSearch.Tests/ElasticSearch.Tests.csproj:4
- End-of-life runtime: .NET net6.0 src/ElasticSearch/ElasticSearch/ElasticSearch.csproj:4
- End-of-life runtime: .NET net6.0 src/EntityFramework/EntityFramework.Integration.Tests/EntityFramework.Integration.Tests.csproj:4
- End-of-life runtime: .NET net6.0 src/EntityFramework/EntityFramework/EntityFramework.csproj:4
- End-of-life runtime: .NET net6.0 src/Kafka/Kafka.Integration.Tests/Kafka.Integration.Tests.csproj:4
- End-of-life runtime: .NET net6.0 src/Kafka/Kafka.Tests/Kafka.Tests.csproj:4
- End-of-life runtime: .NET net6.0 src/Kafka/Kafka/Kafka.csproj:4
- End-of-life runtime: .NET net6.0 src/Marten/Marten.Integration.Tests/Marten.Integration.Tests.csproj:4
- End-of-life runtime: .NET net6.0 src/Marten/Marten/Marten.csproj:4
- End-of-life runtime: .NET net6.0 src/Testing/Testing/Testing.csproj:4
- End-of-life runtime: .NET net6.0 src/WebApi/WebApi.Tests/WebApi.Tests.csproj:4
- End-of-life runtime: .NET net6.0 src/WebApi/WebApi/WebApi.csproj:4
- Async method without CancellationToken: FromJsonStringContentAsync src/Core/Core/Extensions/Serialization/SerializationExtensions.cs:47
- Async method without CancellationToken: Get src/WebApi/WebApi/Controllers/ReadonlyControllerBase.cs:27
- Async method without CancellationToken: Put src/WebApi/WebApi/Controllers/RestControllerBase.cs:19
- Async method without CancellationToken: Post src/WebApi/WebApi/Controllers/RestControllerBase.cs:29
- Async method without CancellationToken: Delete src/WebApi/WebApi/Controllers/RestControllerBase.cs:39
- Async method without CancellationToken: HandleExceptionAsync src/WebApi/WebApi/Exceptions/ExceptionHandlingMiddleware.cs:34
- Async method without CancellationToken: Rebuild REDACTED:22
- Async method without CancellationToken: Get REDACTED:40
- Async method without CancellationToken: Get REDACTED:46
- Async method without CancellationToken: GetHistory REDACTED:55
- Async method without CancellationToken: GetVersion REDACTED:63
- Async method without CancellationToken: CreateTentative REDACTED:72
- Async method without CancellationToken: ChangeSeat REDACTED:91
- Async method without CancellationToken: Confirm REDACTED:107
- Async method without CancellationToken: Cancel REDACTED:121
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- CommentedOutCode src/Core/Core/Extensions/Basic/ObjectExtensions.cs:45
- CommentedOutCode src/Core/Core/Extensions/Enums/EnumExtensions.cs:19
- CommentedOutCode src/Core/Core/Extensions/Enums/EnumExtensions.cs:32
- CommentedOutCode src/Core/Core/Objects/Responses/ListResponse.cs:44
- CommentedOutCode src/Core/Core/Objects/Responses/SingleResponse.cs:31
- Disposable created and abandoned in the method that made it src/Core/Core/Extensions/Basic/StringExtensions.cs:100
- Disposable created and abandoned in the method that made it src/Core/Core/Extensions/Functions/Memoizer.cs:51
- Disposable created and abandoned in the method that made it src/Core/Core/Utils/Collections/CollectionToCSVConverter.cs:34
- Process-global static state: DateTimeExtensions src/Core/Core/Extensions/Basic/DateTimeExtensions.cs:9
- Process-global static state: ReflectionExtensions src/Core/Core/Extensions/Reflection/ReflectionExtensions.cs:11
- TodoComment src/Core/Core/Extensions/Collections/ListExtensions.cs:62
- TodoComment src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs:110
- REDACTED
- REDACTED
- Sync-over-async blocking
- Sync-over-async blocking src/Marten/Marten/Registration/Registration.cs:79
- Async method drops its CancellationToken: FindById src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs:29
- Async method drops its CancellationToken: Publish src/Kafka/Kafka/Producers/KafkaProducer.cs:28
- Stateful shared instance: UserInfoProvider src/Core/Core/Security/UserInfoProvider.cs:3
- REDACTED
- REDACTED
- Duplicated block (24 lines × 2) src/Core/Core/Extensions/Lambda/ExpressionExtensions.cs:16
- Unfinished stub — throws NotImplementedException src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs:42
- Unfinished stub — throws NotImplementedException src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs:42
- Outbound HTTP without resilience
- NuGet dependencies are not locked
- Sync-over-async (deadlock risk) src/Marten/Marten/Registration/Registration.cs:79
- Disposable acquired into a field and never released src/Core/Core/Events/External/ExternalEventConsumerBackgroundWorker.cs:13
- Type resolved by simple name across every loaded assembly src/Core/Core/Utils/Assemblies/TypeProvider.cs:17
Minor — 68 finding(s)
- Orphaned file src/Core/Core/Extensions/Basic/DateTimeExtensions.cs:1
- Orphaned file src/Core/Core/Extensions/DependencyInjection/RegistrationExtensions.cs:1
- Orphaned file src/Core/Core/Extensions/Collections/EnumerableExtensions.cs:1
- Orphaned file src/Core/Core/Registration/Registration.cs:1
- Orphaned file src/Core/Core/Extensions/Basic/ObjectExtensions.cs:1
- Orphaned file src/Core/Core/Extensions/Lambda/ExpressionExtensions.cs:1
- Orphaned file src/Marten/Marten/Registration/Registration.cs:1
- Orphaned file src/ElasticSearch/ElasticSearch/Repositories/ElasticSearchRepository.cs:1
- Orphaned file src/Core/Core/Extensions/Basic/StringExtensions.cs:1
- Orphaned file src/Core/Core/Extensions/Reflection/ReflectionExtensions.cs:1
- Orphaned file src/Dapper/Dapper/Repositories/DapperRepository.cs:1
- Orphaned file src/Marten/Marten/Repositories/MartenDocumentRepository.cs:1
- Orphaned file src/EntityFramework/EntityFramework/Repositories/EntityFrameworkRepository.cs:1
- Orphaned file src/WebApi/WebApi/Registration/Registration.cs:1
- Orphaned file src/Marten/Marten/Repositories/MartenEventSourcedRepository.cs:1
- Orphaned file src/Core/Core/Extensions/Functions/Memoizer.cs:1
- Orphaned file src/Core/Core/Objects/Dates/DateRange.cs:1
- Orphaned file src/Kafka/Kafka/Consumers/KafkaConsumer.cs:1
- Orphaned file src/Core/Core/Extensions/Collections/DictionaryExtensions.cs:1
- Orphaned file src/Core/Core/Services/CRUDService.cs:1
- Orphaned file src/Marten/Marten/Events/Storage/MartenEventStore.cs:1
- Orphaned file src/Core/Core/Utils/Collections/CollectionToCSVConverter.cs:1
- Orphaned file src/EntityFramework/EntityFramework/Registration/Registration.cs:1
- Orphaned file src/Core/Core/Repositories/RepositoryExtensions.cs:1
- Orphaned file src/Core/Core/Extensions/Collections/ListExtensions.cs:1
- README/code drift src/Core/Core/Readme.md:19
- README/code drift src/Core/Core/Readme.md:41
- README/code drift src/Core/Core/Readme.md:45
- README/code drift src/Core/Core/Readme.md:57
- README/code drift src/Core/Core/Readme.md:61
- README/code drift src/Core/Core/Readme.md:62
- README/code drift src/Core/Core/Readme.md:63
- README/code drift src/Dapper/Dapper/Readme.md:28
- README/code drift src/ElasticSearch/ElasticSearch/Readme.md:28
- README/code drift src/EntityFramework/EntityFramework/Readme.md:29
- README/code drift src/Kafka/Kafka/Readme.md:28
- README/code drift src/Marten/Marten/Readme.md:30
- README/code drift src/WebApi/WebApi.Tests/Readme.md:12
- README/code drift src/WebApi/WebApi.Tests/Readme.md:22
- README/code drift src/WebApi/WebApi/Readme.md:32
- Commented-out code src/Core/Core/Extensions/Basic/ObjectExtensions.cs:47
- Commented-out code src/Core/Core/Extensions/Enums/EnumExtensions.cs:29
- Commented-out code src/Core/Core/Extensions/Enums/EnumExtensions.cs:30
- Commented-out code src/Core/Core/Extensions/Enums/EnumExtensions.cs:37
- Commented-out code src/Core/Core/Extensions/Enums/EnumExtensions.cs:41
- Commented-out code src/Core/Core/Extensions/Enums/EnumExtensions.cs:60
- Interpolated log message defeats structured logging src/WebApi/WebApi/Exceptions/ExceptionHandlingMiddleware.cs:36
- Interpolated log message defeats structured logging src/Kafka/Kafka/Consumers/KafkaConsumer.cs:58
- Interpolated log message defeats structured logging src/Kafka/Kafka/Consumers/KafkaConsumer.cs:92
- redundant comment src/Core/Core/Extensions/Functions/Memoizer.cs:50
- redundant comment src/Core/Core/Extensions/Lambda/ExpressionExtensions.cs:71
- Projects may be oversized for their cohesion src/Core/Core/Core.csproj:1
- REDACTED
- Dormant codebase
- REDACTED
- Disabled test src/EntityFramework/EntityFramework.Integration.Tests/Repositories/EntityFrameworkRepositoryTests.cs:17
- No ADRs
- No tests/ separation
- Large public API surface
- No SAST REDACTED:7
- No dependency-update automation samples/DDD/Tickets/Tickets.Api.Tests/Tickets.Api.Tests.csproj:12
- No rollback/health safety
- No performance benchmarks
- Not all async methods take a CancellationToken
- Some async methods drop the CancellationToken they accept
- Nullable reference types not enabled everywhere
- Null-forgiving operator (`!`) suppressions reduce the NRT score
Minor — 15 finding(s)
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Mock framework: NSubstitute
- Skipped (documented): GivenRepository_WhenFullCRUDFlowIsRun_ThenSucceed src/EntityFramework/EntityFramework.Integration.Tests/Repositories/EntityFrameworkRepositoryTests.cs:17
- doc comments repeat the names src/Core/Core/Extensions/Basic/DateTimeExtensions.cs:28
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-7b4b30f1dd964c46a9adafb5d385db5a/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-7b4b30f1dd964c46a9adafb5d385db5a/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/EntityFramework/EntityFramework.Integration.Tests/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 . | 19 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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-22f8d94b85c74895a3cca674f1064da0 | 0 | artifacts/raw/osv-scanner.json |