Executive summary
dasiths/NEventLite has a provisional result, because the code didn't build. It scores 42 out of 100, and the ratings may change once the code builds. All nine of its critical findings are security problems in its code and in the packages it uses.
Performance, at 38, is the weakest lens and counts most in the score. The best first step is removing the blocking calls, worth about 4 points. Making the naming consistent comes next, worth about 2 points. Raising Performance to 70 would lift the score to about 45.
Eight weaknesses in the code could be used by an attacker. One known security hole in a package the code depends on can be used by attackers. Fixing the weaknesses the scanner points to and updating the vulnerable packages would close both risks.
The product code is 4,906 lines, about β¬5,200 to rebuild.
If Performance rose from 38 to 70, the lowest score rated Strong, the score would rise from 42 to about 45.
New since the last survey: 6 findings
- Platform End-of-Life Β· End-of-life runtime: .NET netcoreapp2.1 src/NEventLite.Tests.Integration/NEventLite.Tests.Integration.csproj
- Platform End-of-Life Β· End-of-life runtime: .NET netcoreapp2.1 src/Samples/NEventLite.Samples.ConsoleApp/NEventLite.Samples.ConsoleApp.csproj
- Stateful singletons Β· Process-global static state: EventstoreConnection legacy/v1.0/src/Examples/NEventLite Example/Util/EventstoreConnection.cs
- Stateful singletons Β· Process-global static state: RedisConnection legacy/v1.0/src/Examples/NEventLite Example/Util/RedisConnection.cs
- Stateful singletons Β· Process-global static state: EventstoreStorageProviderBase legacy/v1.0/src/Storage Providers/EventStore/EventstoreStorageProviderBase.cs
- Stateful singletons Β· Process-global static state: LogManager legacy/v1.0/src/Framework/Logger/LogManager.cs
Fixed since the last survey: 45 findings
- Code Coverage Β· Coverage not measured β no coverage collector is wired up
- Boundary Type-Coupling Β· Cross-context type LogSeverity (NEventLite β v1.0) legacy/v1.0/src/Examples/NEventLite Example/Logging/ConsoleLogger.cs
- Boundary Type-Coupling Β· Cross-context type ISnapshotStorageProvider (NEventLite β v1.0) legacy/v1.0/src/Storage Providers/InMemory/InMemorySnapshotStorageProvider.cs
- Boundary Type-Coupling Β· Cross-context type ISnapshotStorageProvider (NEventLite β v1.0) REDACTED
- Boundary Type-Coupling Β· Cross-context type AggregateRoot (NEventLite β Storage) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Boundary Type-Coupling Β· Cross-context type AggregateRoot (NEventLite β Storage) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Boundary Type-Coupling Β· Cross-context type AggregateRoot (NEventLite β Storage) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Boundary Type-Coupling Β· Cross-context type ISnapshotStorageProvider (NEventLite β Storage) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreSnapshotStorageProvider.cs
- Boundary Type-Coupling Β· Cross-context type AggregateRoot (NEventLite β Storage) src/Storage/NEventLite.StorageProviders.EventStore/Core/EventstoreStorageCore.cs
- Boundary Type-Coupling Β· Cross-context type AggregateRoot (NEventLite β Storage) src/Storage/NEventLite.StorageProviders.EventStore/Core/IEventStoreStorageCore.cs
- Boundary Type-Coupling Β· Cross-context type AggregateRoot (NEventLite β Storage) src/Storage/NEventLite.StorageProviders.InMemory/InMemoryEventStorageProvider.cs
- Boundary Type-Coupling Β· Cross-context type AggregateRoot (NEventLite β Storage) src/Storage/NEventLite.StorageProviders.InMemory/InMemoryEventStorageProvider.cs
- Boundary Type-Coupling Β· Cross-context type AggregateRoot (NEventLite β Storage) src/Storage/NEventLite.StorageProviders.InMemory/InMemoryEventStorageProvider.cs
- Boundary Type-Coupling Β· Cross-context type ISnapshotStorageProvider (NEventLite β Storage) src/Storage/NEventLite.StorageProviders.InMemory/InMemorySnapshotStorageProvider.cs
- Platform End-of-Life Β· End-of-life runtime: .NET netcoreapp2.1 src/NEventLite.Tests.Integration/NEventLite.Tests.Integration.csproj
- Cancellation propagation Β· Async method without CancellationToken: DoApplyAsync src/NEventLite/Core/Domain/AggregateRoot.cs
- Cancellation propagation Β· Async method without CancellationToken: GetLatestSnapshotAsync src/NEventLite/Repository/Repository.cs
- Cancellation propagation Β· Async method without CancellationToken: SaveSnapshotAsync src/NEventLite/Repository/Repository.cs
- Cancellation propagation Β· Async method without CancellationToken: PublishEventsAsync src/NEventLite/Repository/Repository.cs
- Cancellation propagation Β· Async method without CancellationToken: HandleAsync src/Samples/NEventLite.Samples.Common/Handlers/UpdateTodoNameHandler.cs
- Cancellation propagation Β· Async method without CancellationToken: GetEventsAsync src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Cancellation propagation Β· Async method without CancellationToken: GetLastEventAsync src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Cancellation propagation Β· Async method without CancellationToken: SaveAsync src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Cancellation propagation Β· Async method without CancellationToken: GetSnapshotAsync src/Storage/NEventLite.StorageProviders.EventStore/EventStoreSnapshotStorageProvider.cs
- Cancellation propagation Β· Async method without CancellationToken: SaveSnapshotAsync src/Storage/NEventLite.StorageProviders.EventStore/EventStoreSnapshotStorageProvider.cs
- Cancellation propagation Β· Async method without CancellationToken: RunSample src/Samples/NEventLite.Samples.Autofac/Program.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/NEventLite/Repository/Repository.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/NEventLite/Repository/Session.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/NEventLite/Repository/Session.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/NEventLite/Repository/Session.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/NEventLite/Repository/Session.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/NEventLite/Util/EventExtensions.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/Core/EventStoreStorageConnectionProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/Core/EventStoreStorageConnectionProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreSnapshotStorageProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreSnapshotStorageProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreSnapshotStorageProvider.cs
- Async & latency hygiene Β· Awaits without ConfigureAwait(false) src/Storage/NEventLite.StorageProviders.EventStore/EventStoreSnapshotStorageProvider.cs
Rebuild cost: about β¬5,200 Β· Estimate
| Cost to rebuild | β¬1,700 to β¬8,600, for 29 to 91 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 42. 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: 4,906 lines of product code, of which 47% is declarations and boilerplate, 35% straight logic and 19% logic with branches |
| Comment lines | The estimate prices 4,612 lines. Comment lines count towards the size of 4,906 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 β bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses β | 1 NEventLite | 2 NEventLite.Command_Handler | 3 NEventLite.Core.Domain | 4 NEventLite.Custom_Attribute | 5 NEventLite.Event_Handler | 6 NEventLite.Exception | 7 NEventLite.Exceptions | 8 NEventLite.Logger | 9 NEventLite.Message | 10 NEventLite.Scope | 11 NEventLite.Snapshot | 12 NEventLite.StorageProviders.InMemory | 13 NEventLite_Storage_Providers.Util | 14 NEventLite.Command | 15 NEventLite.Core | 16 NEventLite.Event | 17 NEventLite.StorageProviders.EventStore.Core | 18 NEventLite.Util | 19 NEventLite.Command_Bus | 20 NEventLite.Domain | 21 NEventLite.Event_Bus | 22 NEventLite.Extensions.Autofac | 23 NEventLite.Extensions.Microsoft.DependencyInjection | 24 NEventLite.Extension | 25 NEventLite.Storage | 26 NEventLite.Repository | 27 NEventLite.StorageProviders.EventStore | 28 NEventLite_Storage_Providers.EventStore | 29 NEventLite_Storage_Providers.InMemory | 30 NEventLite_Storage_Providers.Redis | 31 NEventLite.Unit_Of_Work |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 NEventLite | |||||||||||||||||||||||||||||||
| 2 NEventLite.Command_Handler | |||||||||||||||||||||||||||||||
| 3 NEventLite.Core.Domain | |||||||||||||||||||||||||||||||
| 4 NEventLite.Custom_Attribute | |||||||||||||||||||||||||||||||
| 5 NEventLite.Event_Handler | |||||||||||||||||||||||||||||||
| 6 NEventLite.Exception | |||||||||||||||||||||||||||||||
| 7 NEventLite.Exceptions | |||||||||||||||||||||||||||||||
| 8 NEventLite.Logger | |||||||||||||||||||||||||||||||
| 9 NEventLite.Message | |||||||||||||||||||||||||||||||
| 10 NEventLite.Scope | |||||||||||||||||||||||||||||||
| 11 NEventLite.Snapshot | |||||||||||||||||||||||||||||||
| 12 NEventLite.StorageProviders.InMemory | |||||||||||||||||||||||||||||||
| 13 NEventLite_Storage_Providers.Util | |||||||||||||||||||||||||||||||
| 14 NEventLite.Command | 1 | ||||||||||||||||||||||||||||||
| 15 NEventLite.Core | 2 | ||||||||||||||||||||||||||||||
| 16 NEventLite.Event | 1 | ||||||||||||||||||||||||||||||
| 17 NEventLite.StorageProviders.EventStore.Core | 4 | ||||||||||||||||||||||||||||||
| 18 NEventLite.Util | 2 | ||||||||||||||||||||||||||||||
| 19 NEventLite.Command_Bus | 1 | ||||||||||||||||||||||||||||||
| 20 NEventLite.Domain | 1 | ||||||||||||||||||||||||||||||
| 21 NEventLite.Event_Bus | 1 | ||||||||||||||||||||||||||||||
| 22 NEventLite.Extensions.Autofac | 1 | ||||||||||||||||||||||||||||||
| 23 NEventLite.Extensions.Microsoft.DependencyInjection | 1 | ||||||||||||||||||||||||||||||
| 24 NEventLite.Extension | 1 | 1 | |||||||||||||||||||||||||||||
| 25 NEventLite.Storage | 2 | 1 | 1 | ||||||||||||||||||||||||||||
| 26 NEventLite.Repository | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||
| 27 NEventLite.StorageProviders.EventStore | 2 | 6 | 2 | ||||||||||||||||||||||||||||
| 28 NEventLite_Storage_Providers.EventStore | 2 | 2 | 1 | 2 | |||||||||||||||||||||||||||
| 29 NEventLite_Storage_Providers.InMemory | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||
| 30 NEventLite_Storage_Providers.Redis | 1 | 1 | |||||||||||||||||||||||||||||
| 31 NEventLite.Unit_Of_Work | 1 | 1 |
14β9 NEventLite.Command uses NEventLite.Message✕
- Connections
- 1 pair of types, where a type in NEventLite.Command uses a type in NEventLite.Message.
- The types involved
NEventLite.Command.ICommandβNEventLite.Message.IMessage
- Direction
- NEventLite.Command uses NEventLite.Message, so a change to NEventLite.Message can break NEventLite.Command, while a change to NEventLite.Command can't break NEventLite.Message.
- Position
- Below the diagonal: NEventLite.Command uses a module listed above it, which is the healthy direction.
15β3 NEventLite.Core uses NEventLite.Core.Domain✕
- Connections
- 2 pairs of types, where a type in NEventLite.Core uses a type in NEventLite.Core.Domain.
- The types involved
NEventLite.Core.DefaultNoOpEventPublisherβNEventLite.Core.Domain.IEventNEventLite.Core.IEventPublisherβNEventLite.Core.Domain.IEvent
- Direction
- NEventLite.Core uses NEventLite.Core.Domain, so a change to NEventLite.Core.Domain can break NEventLite.Core, while a change to NEventLite.Core can't break NEventLite.Core.Domain.
- Position
- Below the diagonal: NEventLite.Core uses a module listed above it, which is the healthy direction.
16β9 NEventLite.Event uses NEventLite.Message✕
- Connections
- 1 pair of types, where a type in NEventLite.Event uses a type in NEventLite.Message.
- The types involved
NEventLite.Event.IEventβNEventLite.Message.IMessage
- Direction
- NEventLite.Event uses NEventLite.Message, so a change to NEventLite.Message can break NEventLite.Event, while a change to NEventLite.Event can't break NEventLite.Message.
- Position
- Below the diagonal: NEventLite.Event uses a module listed above it, which is the healthy direction.
17β3 NEventLite.StorageProviders.EventStore.Core uses NEventLite.Core.Domain✕
- Connections
- 4 pairs of types, where a type in NEventLite.StorageProviders.EventStore.Core uses a type in NEventLite.Core.Domain.
- The types involved
NEventLite.StorageProviders.EventStore.Core.EventStoreStorageCoreβNEventLite.Core.Domain.AggregateRootNEventLite.StorageProviders.EventStore.Core.EventStoreStorageCoreβNEventLite.Core.Domain.IEventNEventLite.StorageProviders.EventStore.Core.IEventStoreStorageCoreβNEventLite.Core.Domain.AggregateRootNEventLite.StorageProviders.EventStore.Core.IEventStoreStorageCoreβNEventLite.Core.Domain.IEvent
- Direction
- NEventLite.StorageProviders.EventStore.Core uses NEventLite.Core.Domain, so a change to NEventLite.Core.Domain can break NEventLite.StorageProviders.EventStore.Core, while a change to NEventLite.StorageProviders.EventStore.Core can't break NEventLite.Core.Domain.
- Position
- Below the diagonal: NEventLite.StorageProviders.EventStore.Core uses a module listed above it, which is the healthy direction.
18β3 NEventLite.Util uses NEventLite.Core.Domain✕
- Connections
- 2 pairs of types, where a type in NEventLite.Util uses a type in NEventLite.Core.Domain.
- The types involved
NEventLite.Util.EventExtensionsβNEventLite.Core.Domain.AggregateRootNEventLite.Util.EventExtensionsβNEventLite.Core.Domain.IEvent
- Direction
- NEventLite.Util uses NEventLite.Core.Domain, so a change to NEventLite.Core.Domain can break NEventLite.Util, while a change to NEventLite.Util can't break NEventLite.Core.Domain.
- Position
- Below the diagonal: NEventLite.Util uses a module listed above it, which is the healthy direction.
19β14 NEventLite.Command_Bus uses NEventLite.Command✕
- Connections
- 1 pair of types, where a type in NEventLite.Command_Bus uses a type in NEventLite.Command.
- The types involved
NEventLite.Command_Bus.ICommandBusβNEventLite.Command.ICommandPublishResult
- Direction
- NEventLite.Command_Bus uses NEventLite.Command, so a change to NEventLite.Command can break NEventLite.Command_Bus, while a change to NEventLite.Command_Bus can't break NEventLite.Command.
- Position
- Below the diagonal: NEventLite.Command_Bus uses a module listed above it, which is the healthy direction.
20β16 NEventLite.Domain uses NEventLite.Event✕
- Connections
- 1 pair of types, where a type in NEventLite.Domain uses a type in NEventLite.Event.
- The types involved
NEventLite.Domain.AggregateRootβNEventLite.Event.IEvent
- Direction
- NEventLite.Domain uses NEventLite.Event, so a change to NEventLite.Event can break NEventLite.Domain, while a change to NEventLite.Domain can't break NEventLite.Event.
- Position
- Below the diagonal: NEventLite.Domain uses a module listed above it, which is the healthy direction.
21β16 NEventLite.Event_Bus uses NEventLite.Event✕
- Connections
- 1 pair of types, where a type in NEventLite.Event_Bus uses a type in NEventLite.Event.
- The types involved
NEventLite.Event_Bus.IEventPublisherβNEventLite.Event.IEvent
- Direction
- NEventLite.Event_Bus uses NEventLite.Event, so a change to NEventLite.Event can break NEventLite.Event_Bus, while a change to NEventLite.Event_Bus can't break NEventLite.Event.
- Position
- Below the diagonal: NEventLite.Event_Bus uses a module listed above it, which is the healthy direction.
22β18 NEventLite.Extensions.Autofac uses NEventLite.Util✕
- Connections
- 1 pair of types, where a type in NEventLite.Extensions.Autofac uses a type in NEventLite.Util.
- The types involved
NEventLite.Extensions.Autofac.ExtensionsβNEventLite.Util.AggregateInformation
- Direction
- NEventLite.Extensions.Autofac uses NEventLite.Util, so a change to NEventLite.Util can break NEventLite.Extensions.Autofac, while a change to NEventLite.Extensions.Autofac can't break NEventLite.Util.
- Position
- Below the diagonal: NEventLite.Extensions.Autofac uses a module listed above it, which is the healthy direction.
23β18 NEventLite.Extensions.Microsoft.DependencyInjection uses NEventLite.Util✕
- Connections
- 1 pair of types, where a type in NEventLite.Extensions.Microsoft.DependencyInjection uses a type in NEventLite.Util.
- The types involved
NEventLite.Extensions.Microsoft.DependencyInjection.ExtensionsβNEventLite.Util.AggregateInformation
- Direction
- NEventLite.Extensions.Microsoft.DependencyInjection uses NEventLite.Util, so a change to NEventLite.Util can break NEventLite.Extensions.Microsoft.DependencyInjection, while a change to NEventLite.Extensions.Microsoft.DependencyInjection can't break NEventLite.Util.
- Position
- Below the diagonal: NEventLite.Extensions.Microsoft.DependencyInjection uses a module listed above it, which is the healthy direction.
24β16 NEventLite.Extension uses NEventLite.Event✕
- Connections
- 1 pair of types, where a type in NEventLite.Extension uses a type in NEventLite.Event.
- The types involved
NEventLite.Extension.EventExtensionβNEventLite.Event.IEvent
- Direction
- NEventLite.Extension uses NEventLite.Event, so a change to NEventLite.Event can break NEventLite.Extension, while a change to NEventLite.Extension can't break NEventLite.Event.
- Position
- Below the diagonal: NEventLite.Extension uses a module listed above it, which is the healthy direction.
24β20 NEventLite.Extension uses NEventLite.Domain✕
- Connections
- 1 pair of types, where a type in NEventLite.Extension uses a type in NEventLite.Domain.
- The types involved
NEventLite.Extension.EventExtensionβNEventLite.Domain.AggregateRoot
- Direction
- NEventLite.Extension uses NEventLite.Domain, so a change to NEventLite.Domain can break NEventLite.Extension, while a change to NEventLite.Extension can't break NEventLite.Domain.
- Position
- Below the diagonal: NEventLite.Extension uses a module listed above it, which is the healthy direction.
25β11 NEventLite.Storage uses NEventLite.Snapshot✕
- Connections
- 2 pairs of types, where a type in NEventLite.Storage uses a type in NEventLite.Snapshot.
- The types involved
NEventLite.Storage.IEventSnapshotStorageProviderβNEventLite.Snapshot.SnapshotNEventLite.Storage.ISnapshotStorageProviderβNEventLite.Snapshot.Snapshot
- Direction
- NEventLite.Storage uses NEventLite.Snapshot, so a change to NEventLite.Snapshot can break NEventLite.Storage, while a change to NEventLite.Storage can't break NEventLite.Snapshot.
- Position
- Below the diagonal: NEventLite.Storage uses a module listed above it, which is the healthy direction.
25β16 NEventLite.Storage uses NEventLite.Event✕
- Connections
- 1 pair of types, where a type in NEventLite.Storage uses a type in NEventLite.Event.
- The types involved
NEventLite.Storage.IEventStorageProviderβNEventLite.Event.IEvent
- Direction
- NEventLite.Storage uses NEventLite.Event, so a change to NEventLite.Event can break NEventLite.Storage, while a change to NEventLite.Storage can't break NEventLite.Event.
- Position
- Below the diagonal: NEventLite.Storage uses a module listed above it, which is the healthy direction.
25β20 NEventLite.Storage uses NEventLite.Domain✕
- Connections
- 1 pair of types, where a type in NEventLite.Storage uses a type in NEventLite.Domain.
- The types involved
NEventLite.Storage.IEventStorageProviderβNEventLite.Domain.AggregateRoot
- Direction
- NEventLite.Storage uses NEventLite.Domain, so a change to NEventLite.Domain can break NEventLite.Storage, while a change to NEventLite.Storage can't break NEventLite.Domain.
- Position
- Below the diagonal: NEventLite.Storage uses a module listed above it, which is the healthy direction.
26β1 NEventLite.Repository uses NEventLite✕
- Connections
- 1 pair of types, where a type in NEventLite.Repository uses a type in NEventLite.
- The types involved
NEventLite.Repository.EventOnlyRepositoryβNEventLite.IClock
- Direction
- NEventLite.Repository uses NEventLite, so a change to NEventLite can break NEventLite.Repository, while a change to NEventLite.Repository can't break NEventLite.
- Position
- Below the diagonal: NEventLite.Repository uses a module listed above it, which is the healthy direction.
26β3 NEventLite.Repository uses NEventLite.Core.Domain✕
- Connections
- 1 pair of types, where a type in NEventLite.Repository uses a type in NEventLite.Core.Domain.
- The types involved
NEventLite.Repository.MockAggregateβNEventLite.Core.Domain.AggregateRoot
- Direction
- NEventLite.Repository uses NEventLite.Core.Domain, so a change to NEventLite.Core.Domain can break NEventLite.Repository, while a change to NEventLite.Repository can't break NEventLite.Core.Domain.
- Position
- Below the diagonal: NEventLite.Repository uses a module listed above it, which is the healthy direction.
26β15 NEventLite.Repository uses NEventLite.Core✕
- Connections
- 2 pairs of types, where a type in NEventLite.Repository uses a type in NEventLite.Core.
- The types involved
NEventLite.Repository.EventOnlyRepositoryβNEventLite.Core.IEventPublisherNEventLite.Repository.IMockSnapShotβNEventLite.Core.ISnapshot
- Direction
- NEventLite.Repository uses NEventLite.Core, so a change to NEventLite.Core can break NEventLite.Repository, while a change to NEventLite.Repository can't break NEventLite.Core.
- Position
- Below the diagonal: NEventLite.Repository uses a module listed above it, which is the healthy direction.
26β16 NEventLite.Repository uses NEventLite.Event✕
- Connections
- 1 pair of types, where a type in NEventLite.Repository uses a type in NEventLite.Event.
- The types involved
NEventLite.Repository.RepositoryβNEventLite.Event.IEvent
- Direction
- NEventLite.Repository uses NEventLite.Event, so a change to NEventLite.Event can break NEventLite.Repository, while a change to NEventLite.Repository can't break NEventLite.Event.
- Position
- Below the diagonal: NEventLite.Repository uses a module listed above it, which is the healthy direction.
26β18 NEventLite.Repository uses NEventLite.Util✕
- Connections
- 1 pair of types, where a type in NEventLite.Repository uses a type in NEventLite.Util.
- The types involved
NEventLite.Repository.AggregateTypeContainerβNEventLite.Util.AggregateInformation
- Direction
- NEventLite.Repository uses NEventLite.Util, so a change to NEventLite.Util can break NEventLite.Repository, while a change to NEventLite.Repository can't break NEventLite.Util.
- Position
- Below the diagonal: NEventLite.Repository uses a module listed above it, which is the healthy direction.
26β20 NEventLite.Repository uses NEventLite.Domain✕
- Connections
- 1 pair of types, where a type in NEventLite.Repository uses a type in NEventLite.Domain.
- The types involved
NEventLite.Repository.RepositoryβNEventLite.Domain.AggregateRoot
- Direction
- NEventLite.Repository uses NEventLite.Domain, so a change to NEventLite.Domain can break NEventLite.Repository, while a change to NEventLite.Repository can't break NEventLite.Domain.
- Position
- Below the diagonal: NEventLite.Repository uses a module listed above it, which is the healthy direction.
26β21 NEventLite.Repository uses NEventLite.Event_Bus✕
- Connections
- 1 pair of types, where a type in NEventLite.Repository uses a type in NEventLite.Event_Bus.
- The types involved
NEventLite.Repository.RepositoryβNEventLite.Event_Bus.IEventPublisher
- Direction
- NEventLite.Repository uses NEventLite.Event_Bus, so a change to NEventLite.Event_Bus can break NEventLite.Repository, while a change to NEventLite.Repository can't break NEventLite.Event_Bus.
- Position
- Below the diagonal: NEventLite.Repository uses a module listed above it, which is the healthy direction.
26β25 NEventLite.Repository uses NEventLite.Storage✕
- Connections
- 4 pairs of types, where a type in NEventLite.Repository uses a type in NEventLite.Storage.
- The types involved
NEventLite.Repository.EventOnlyRepositoryβNEventLite.Storage.IEventStorageProviderNEventLite.Repository.MockSnapshotStorageProviderβNEventLite.Storage.ISnapshotStorageProviderNEventLite.Repository.RepositoryβNEventLite.Storage.IEventStorageProviderNEventLite.Repository.RepositoryβNEventLite.Storage.ISnapshotStorageProvider
- Direction
- NEventLite.Repository uses NEventLite.Storage, so a change to NEventLite.Storage can break NEventLite.Repository, while a change to NEventLite.Repository can't break NEventLite.Storage.
- Position
- Below the diagonal: NEventLite.Repository uses a module listed above it, which is the healthy direction.
27β3 NEventLite.StorageProviders.EventStore uses NEventLite.Core.Domain✕
- Connections
- 2 pairs of types, where a type in NEventLite.StorageProviders.EventStore uses a type in NEventLite.Core.Domain.
- The types involved
NEventLite.StorageProviders.EventStore.EventStoreEventStorageProviderβNEventLite.Core.Domain.AggregateRootNEventLite.StorageProviders.EventStore.EventStoreEventStorageProviderβNEventLite.Core.Domain.IEvent
- Direction
- NEventLite.StorageProviders.EventStore uses NEventLite.Core.Domain, so a change to NEventLite.Core.Domain can break NEventLite.StorageProviders.EventStore, while a change to NEventLite.StorageProviders.EventStore can't break NEventLite.Core.Domain.
- Position
- Below the diagonal: NEventLite.StorageProviders.EventStore uses a module listed above it, which is the healthy direction.
27β17 NEventLite.StorageProviders.EventStore uses NEventLite.StorageProviders.EventStore.Core✕
- Connections
- 6 pairs of types, where a type in NEventLite.StorageProviders.EventStore uses a type in NEventLite.StorageProviders.EventStore.Core.
- The types involved
NEventLite.StorageProviders.EventStore.EventStoreEventStorageProviderβNEventLite.StorageProviders.EventStore.Core.IEventStoreSettingsNEventLite.StorageProviders.EventStore.EventStoreEventStorageProviderβNEventLite.StorageProviders.EventStore.Core.IEventStoreStorageConnectionProviderNEventLite.StorageProviders.EventStore.EventStoreEventStorageProviderβNEventLite.StorageProviders.EventStore.Core.IEventStoreStorageCoreNEventLite.StorageProviders.EventStore.EventStoreSnapshotStorageProviderβNEventLite.StorageProviders.EventStore.Core.IEventStoreSettingsNEventLite.StorageProviders.EventStore.EventStoreSnapshotStorageProviderβNEventLite.StorageProviders.EventStore.Core.IEventStoreStorageConnectionProviderNEventLite.StorageProviders.EventStore.EventStoreSnapshotStorageProviderβNEventLite.StorageProviders.EventStore.Core.IEventStoreStorageCore
- Direction
- NEventLite.StorageProviders.EventStore uses NEventLite.StorageProviders.EventStore.Core, so a change to NEventLite.StorageProviders.EventStore.Core can break NEventLite.StorageProviders.EventStore, while a change to NEventLite.StorageProviders.EventStore can't break NEventLite.StorageProviders.EventStore.Core.
- Position
- Below the diagonal: NEventLite.StorageProviders.EventStore uses a module listed above it, which is the healthy direction.
27β25 NEventLite.StorageProviders.EventStore uses NEventLite.Storage✕
- Connections
- 2 pairs of types, where a type in NEventLite.StorageProviders.EventStore uses a type in NEventLite.Storage.
- The types involved
NEventLite.StorageProviders.EventStore.EventStoreEventStorageProviderβNEventLite.Storage.IEventStorageProviderNEventLite.StorageProviders.EventStore.EventStoreSnapshotStorageProviderβNEventLite.Storage.ISnapshotStorageProvider
- Direction
- NEventLite.StorageProviders.EventStore uses NEventLite.Storage, so a change to NEventLite.Storage can break NEventLite.StorageProviders.EventStore, while a change to NEventLite.StorageProviders.EventStore can't break NEventLite.Storage.
- Position
- Below the diagonal: NEventLite.StorageProviders.EventStore uses a module listed above it, which is the healthy direction.
28β11 NEventLite_Storage_Providers.EventStore uses NEventLite.Snapshot✕
- Connections
- 2 pairs of types, where a type in NEventLite_Storage_Providers.EventStore uses a type in NEventLite.Snapshot.
- The types involved
NEventLite_Storage_Providers.EventStore.EventstoreSnapshotStorageProviderβNEventLite.Snapshot.SnapshotNEventLite_Storage_Providers.EventStore.EventstoreStorageProviderBaseβNEventLite.Snapshot.Snapshot
- Direction
- NEventLite_Storage_Providers.EventStore uses NEventLite.Snapshot, so a change to NEventLite.Snapshot can break NEventLite_Storage_Providers.EventStore, while a change to NEventLite_Storage_Providers.EventStore can't break NEventLite.Snapshot.
- Position
- Below the diagonal: NEventLite_Storage_Providers.EventStore uses a module listed above it, which is the healthy direction.
28β16 NEventLite_Storage_Providers.EventStore uses NEventLite.Event✕
- Connections
- 2 pairs of types, where a type in NEventLite_Storage_Providers.EventStore uses a type in NEventLite.Event.
- The types involved
NEventLite_Storage_Providers.EventStore.EventstoreEventStorageProviderβNEventLite.Event.IEventNEventLite_Storage_Providers.EventStore.EventstoreStorageProviderBaseβNEventLite.Event.IEvent
- Direction
- NEventLite_Storage_Providers.EventStore uses NEventLite.Event, so a change to NEventLite.Event can break NEventLite_Storage_Providers.EventStore, while a change to NEventLite_Storage_Providers.EventStore can't break NEventLite.Event.
- Position
- Below the diagonal: NEventLite_Storage_Providers.EventStore uses a module listed above it, which is the healthy direction.
28β20 NEventLite_Storage_Providers.EventStore uses NEventLite.Domain✕
- Connections
- 1 pair of types, where a type in NEventLite_Storage_Providers.EventStore uses a type in NEventLite.Domain.
- The types involved
NEventLite_Storage_Providers.EventStore.EventstoreEventStorageProviderβNEventLite.Domain.AggregateRoot
- Direction
- NEventLite_Storage_Providers.EventStore uses NEventLite.Domain, so a change to NEventLite.Domain can break NEventLite_Storage_Providers.EventStore, while a change to NEventLite_Storage_Providers.EventStore can't break NEventLite.Domain.
- Position
- Below the diagonal: NEventLite_Storage_Providers.EventStore uses a module listed above it, which is the healthy direction.
28β25 NEventLite_Storage_Providers.EventStore uses NEventLite.Storage✕
- Connections
- 2 pairs of types, where a type in NEventLite_Storage_Providers.EventStore uses a type in NEventLite.Storage.
- The types involved
NEventLite_Storage_Providers.EventStore.EventstoreEventStorageProviderβNEventLite.Storage.IEventStorageProviderNEventLite_Storage_Providers.EventStore.EventstoreSnapshotStorageProviderβNEventLite.Storage.IEventSnapshotStorageProvider
- Direction
- NEventLite_Storage_Providers.EventStore uses NEventLite.Storage, so a change to NEventLite.Storage can break NEventLite_Storage_Providers.EventStore, while a change to NEventLite_Storage_Providers.EventStore can't break NEventLite.Storage.
- Position
- Below the diagonal: NEventLite_Storage_Providers.EventStore uses a module listed above it, which is the healthy direction.
29β11 NEventLite_Storage_Providers.InMemory uses NEventLite.Snapshot✕
- Connections
- 1 pair of types, where a type in NEventLite_Storage_Providers.InMemory uses a type in NEventLite.Snapshot.
- The types involved
NEventLite_Storage_Providers.InMemory.InMemorySnapshotStorageProviderβNEventLite.Snapshot.Snapshot
- Direction
- NEventLite_Storage_Providers.InMemory uses NEventLite.Snapshot, so a change to NEventLite.Snapshot can break NEventLite_Storage_Providers.InMemory, while a change to NEventLite_Storage_Providers.InMemory can't break NEventLite.Snapshot.
- Position
- Below the diagonal: NEventLite_Storage_Providers.InMemory uses a module listed above it, which is the healthy direction.
29β16 NEventLite_Storage_Providers.InMemory uses NEventLite.Event✕
- Connections
- 1 pair of types, where a type in NEventLite_Storage_Providers.InMemory uses a type in NEventLite.Event.
- The types involved
NEventLite_Storage_Providers.InMemory.InMemoryEventStorageProviderβNEventLite.Event.IEvent
- Direction
- NEventLite_Storage_Providers.InMemory uses NEventLite.Event, so a change to NEventLite.Event can break NEventLite_Storage_Providers.InMemory, while a change to NEventLite_Storage_Providers.InMemory can't break NEventLite.Event.
- Position
- Below the diagonal: NEventLite_Storage_Providers.InMemory uses a module listed above it, which is the healthy direction.
29β20 NEventLite_Storage_Providers.InMemory uses NEventLite.Domain✕
- Connections
- 1 pair of types, where a type in NEventLite_Storage_Providers.InMemory uses a type in NEventLite.Domain.
- The types involved
NEventLite_Storage_Providers.InMemory.InMemoryEventStorageProviderβNEventLite.Domain.AggregateRoot
- Direction
- NEventLite_Storage_Providers.InMemory uses NEventLite.Domain, so a change to NEventLite.Domain can break NEventLite_Storage_Providers.InMemory, while a change to NEventLite_Storage_Providers.InMemory can't break NEventLite.Domain.
- Position
- Below the diagonal: NEventLite_Storage_Providers.InMemory uses a module listed above it, which is the healthy direction.
29β25 NEventLite_Storage_Providers.InMemory uses NEventLite.Storage✕
- Connections
- 2 pairs of types, where a type in NEventLite_Storage_Providers.InMemory uses a type in NEventLite.Storage.
- The types involved
NEventLite_Storage_Providers.InMemory.InMemoryEventStorageProviderβNEventLite.Storage.IEventStorageProviderNEventLite_Storage_Providers.InMemory.InMemorySnapshotStorageProviderβNEventLite.Storage.ISnapshotStorageProvider
- Direction
- NEventLite_Storage_Providers.InMemory uses NEventLite.Storage, so a change to NEventLite.Storage can break NEventLite_Storage_Providers.InMemory, while a change to NEventLite_Storage_Providers.InMemory can't break NEventLite.Storage.
- Position
- Below the diagonal: NEventLite_Storage_Providers.InMemory uses a module listed above it, which is the healthy direction.
30β11 NEventLite_Storage_Providers.Redis uses NEventLite.Snapshot✕
- Connections
- 1 pair of types, where a type in NEventLite_Storage_Providers.Redis uses a type in NEventLite.Snapshot.
- The types involved
NEventLite_Storage_Providers.Redis.RedisSnapshotStorageProviderβNEventLite.Snapshot.Snapshot
- Direction
- NEventLite_Storage_Providers.Redis uses NEventLite.Snapshot, so a change to NEventLite.Snapshot can break NEventLite_Storage_Providers.Redis, while a change to NEventLite_Storage_Providers.Redis can't break NEventLite.Snapshot.
- Position
- Below the diagonal: NEventLite_Storage_Providers.Redis uses a module listed above it, which is the healthy direction.
30β25 NEventLite_Storage_Providers.Redis uses NEventLite.Storage✕
- Connections
- 1 pair of types, where a type in NEventLite_Storage_Providers.Redis uses a type in NEventLite.Storage.
- The types involved
NEventLite_Storage_Providers.Redis.RedisSnapshotStorageProviderβNEventLite.Storage.ISnapshotStorageProvider
- Direction
- NEventLite_Storage_Providers.Redis uses NEventLite.Storage, so a change to NEventLite.Storage can break NEventLite_Storage_Providers.Redis, while a change to NEventLite_Storage_Providers.Redis can't break NEventLite.Storage.
- Position
- Below the diagonal: NEventLite_Storage_Providers.Redis uses a module listed above it, which is the healthy direction.
31β20 NEventLite.Unit_Of_Work uses NEventLite.Domain✕
- Connections
- 1 pair of types, where a type in NEventLite.Unit_Of_Work uses a type in NEventLite.Domain.
- The types involved
NEventLite.Unit_Of_Work.UnitOfWorkβNEventLite.Domain.AggregateRoot
- Direction
- NEventLite.Unit_Of_Work uses NEventLite.Domain, so a change to NEventLite.Domain can break NEventLite.Unit_Of_Work, while a change to NEventLite.Unit_Of_Work can't break NEventLite.Domain.
- Position
- Below the diagonal: NEventLite.Unit_Of_Work uses a module listed above it, which is the healthy direction.
31β26 NEventLite.Unit_Of_Work uses NEventLite.Repository✕
- Connections
- 1 pair of types, where a type in NEventLite.Unit_Of_Work uses a type in NEventLite.Repository.
- The types involved
NEventLite.Unit_Of_Work.UnitOfWorkβNEventLite.Repository.IRepository
- Direction
- NEventLite.Unit_Of_Work uses NEventLite.Repository, so a change to NEventLite.Repository can break NEventLite.Unit_Of_Work, while a change to NEventLite.Unit_Of_Work can't break NEventLite.Repository.
- Position
- Below the diagonal: NEventLite.Unit_Of_Work uses a module listed above it, which is the healthy direction.
At a glance β Code Health
At a glance β Architecture
At a glance β Maturity
At a glance β Readiness
At a glance β Security
At a glance β Domain Modelling
At a glance β Performance
Security & Compliance β OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 β Injection | 29 | High / Critical |
| A03:2025 β Software Supply Chain Failures | 1 | High / Critical |
Roadmap
Top priorities: Make the call chain async end-to-end and await it β never block on a Task with .Wait()/.GetAwaiter().GetResult(); 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); Resolve the 19 Orphaned file finding(s) in Knowledge Freshness β start with AggregateRoot.cs (2), Repository.cs (2), ReflectionHelper.cs (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make the call chain async end-to-end and await it β never block on a Task with .Wait()/.GetAwaiter().GetResult(). | +3.7 pts | Medium | Async & latency hygiene |
| Resolve the 1 `CommitChanges` returns an awaitable but lacks the `Async` suffix its 13β¦ finding(s) in Naming Consistency β start with Repository.cs. | +1.7 pts | Low | Naming Consistency |
| Resolve the 1 `CommitChanges` returns an awaitable but lacks the `Async` suffix its 20β¦ finding(s) in Naming Consistency β start with Repository.cs. | +1.7 pts | Low | Naming Consistency |
| 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). | +2.9 pts | Medium | Benchmark discipline |
| Resolve the 19 Orphaned file finding(s) in Knowledge Freshness β start with AggregateRoot.cs (2), Repository.cs (2), ReflectionHelper.cs (2). | +2.9 pts | Medium | Knowledge Freshness |
| Resolve the 10 redundant comment finding(s) in Comment Value β start with AssemblyInfo.cs (8), Repository.cs (2). | +2.7 pts | Medium | Comment Value |
| 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. | +2.5 pts | Medium | Architecture documentation |
| Resolve the 3 End-of-life runtime finding(s) in Platform End-of-Life β start with NEventLite.Tests.Integration.csproj, NEventLite.Samples.ConsoleApp.csproj, NEventLite.Samples.Autofac.csproj. | +0.9 pts | Low | Platform End-of-Life |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/NEventLite.Tests.Integration/NEventLite.Tests.Integration.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp2.1 |
| src/Samples/NEventLite.Samples.ConsoleApp/NEventLite.Samples.ConsoleApp.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp2.1 |
| src/Samples/NEventLite.Samples.Autofac/NEventLite.Samples.Autofac.csproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET netcoreapp3.1 |
| legacy/v1.0/src/Framework/Extension/EventExtension.cs | 8.2 | Near-clean | Explicit Debt: CommentedOutCode |
| legacy/v1.0/src/Framework/Domain/AggregateRoot.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (17 lines × 2) |
| legacy/v1.0/src/Framework/Extension/ReflectionHelper.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| src/Storage/NEventLite.StorageProviders.EventStore/Core/EventstoreStorageCore.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| src/Samples/NEventLite.Samples.Autofac/Program.cs | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 3) |
| REDACTED | 8.6 | Near-clean | Static Analysis (SAST): Low: REDACTED |
| legacy/v1.0/src/Storage Providers/Properties/AssemblyInfo.cs | 9.1 | Near-clean | Comment Value: redundant comment |
| legacy/v1.0/src/Unit Tests/Properties/AssemblyInfo.cs | 9.1 | Near-clean | Comment Value: redundant comment |
| legacy/v1.0/src/Framework/Repository/Repository.cs | 9.3 | Near-clean | Naming Consistency: `CommitChanges` returns an awaitable but lacks the `Async` suffix its 13 peers carry |
| src/NEventLite/Repository/Repository.cs | 9.3 | Near-clean | Naming Consistency: `CommitChanges` returns an awaitable but lacks the `Async` suffix its 20 peers carry |
| legacy/v1.0/src/Examples/NEventLite Example/Read Model/MyReadRepository.cs | 9.5 | Near-clean | Navigability: Pass-through layer |
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 76 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked β 76 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, 175 of 192 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 Β· 0.69.3 | β 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).
- D11 Test Reliability β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored β the test tier(s) ran but surfaced none of this repository's 10 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
- 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: error: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/VisualStudio/v18.0/WebApplications/Microsoft.WebApplication.targets" was not found. Confirm that the expression in the Import declaration "$(VSToolsPath)/WebApplications/Microsoft.WebApplication.targets", which evaluated to "/usr/β¦.
- 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. All 19 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains β nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 1 of the 88 production source files in this repository: 69 are under the ~2,400-byte size floor this dimension measures over, and the remaining 18 have no attributable history left to measure.
- 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: Msbuild failed when processing the file 'legacy/v1.0/src/Examples/NEventLite Example MVC/NEventLite Example MVC.csproj' with message: This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missinβ¦.
- 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.
- D21 Naming Consistency β 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run β this says nothing about whether its names are consistent.
- D22 Internal API Consistency β not measured this run β This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. 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.
- D30 Dependency Vulnerabilities β measured, with a gap in what it reached β 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 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. 1 of 2 declared ecosystem(s) (nuget REDACTED) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. `legacy/v1.0/src/Examples/NEventLite Example MVC/Scripts/_references.js` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D39 IL Efficiency β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) β MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- DM8 Value-object opportunities β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- ED5 Idempotency β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check classifies a mutation as idempotent when a guard is visible (an exists check, an upsert, an idempotency key or inbox, a versioned or fixed-value write) and as at risk only on positive evidence that a re-run double-applies it (a fresh-identity insert, an accumulation, a growing collection, an unkeyed outbound send or charge). The rest show neither, and they are the majority here, so a score over the classified minority would not describe this repository. That is a limit of the analyzer, not a finding about your code.
- P5 DR & Backup β 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found β and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
- X2 Cancellation propagation β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 2 further occurrence(s) are not listed individually; the score already reflects all 42.
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.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases β a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body β a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain β infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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
4 duplicated block group(s) detected. 1 of the 4 are in trees this repository does not ship β vendored, example/demo, project-template, fixture and benchmark code β and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 1 Duplicated block (17 lines × 2) finding(s) in Code Duplication β start with AggregateRoot.cs. β One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (14 lines × 2) finding(s) in Code Duplication β start with ReflectionHelper.cs. β One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication β start with EventstoreStorageCore.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
14 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 Β· Cohesion (LCOM4)
0 of 23 classes have LCOM4 above 3.
D9 Β· Test Distribution
10 test methods: 2 unit, 8 integration, 0 BDD, 0 e2e.
D10 Β· Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 10 tests.
D13 Β· Secret Scanning
Secret scan ran and found no leaked secrets.
D14 Β· License Compliance
0 of 204 packages use a banned license. β DEPTH: this repository's MSBuild projects declare 7 direct `PackageReference`(s), and 187 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
1 deducted debt markers + unmeasured dead symbols across 4906 LoC in the .NET projects (0.0/KLoC) β score 9.9. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
What to do
- Resolve the 1 CommentedOutCode finding(s) in Explicit Debt β start with EventExtension.cs. β One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). β Hardens enforcement from Documented toward Prevented β provenance only; does not change the score.
D18 Β· Solution Shape
14 projects, 142 source files, 5294 hand-written lines of code (4906 production / 388 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), 26 inter-project edges (build failed). Measured across 2 solutions loaded as one workspace: `legacy/v1.0/src/NEventLite.v1.sln`, `src/NEventLite.sln`.
What to do
- Resolve the 1 Build failed finding(s) in Solution Shape. β One of this dimension's main actionable groups (1 warning-level).
D19 Β· Documentation Quality
2 of 2 documentation facets pass in full. 2 document(s) read across 8 unit(s).
D21 Β· Naming Consistency
2 naming inconsistencies among 35 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `CommitChanges` returns an awaitable but lacks the `Async` suffix its 13β¦ finding(s) in Naming Consistency β start with Repository.cs. β One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `CommitChanges` returns an awaitable but lacks the `Async` suffix its 20β¦ finding(s) in Naming Consistency β start with Repository.cs. β One of this dimension's main actionable groups (1 recommendation-level).
D24 Β· Comment Value
10 of 58 judged comments only repeat the code they sit on (17.2 %).
What to do
- Resolve the 10 redundant comment finding(s) in Comment Value β start with AssemblyInfo.cs (8), Repository.cs (2). β One of this dimension's main actionable groups (10 recommendation-level).
D26 Β· Project Cohesion
0 of 14 projects flagged as possibly oversized/incoherent.
D27 Β· Navigability
86 % of calls cross a namespace and 11 % go through an interface, but 53 % of collaborators are co-located β so following a call takes several hops. Baseline: small β navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. β One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Pass-through layer finding(s) in Navigability β start with MyReadRepository.cs. β One of this dimension's main actionable groups (1 recommendation-level).
D28 Β· Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 Β· Static Analysis (SAST)
29 finding(s): 0 critical, 8 high, 1 medium, 20 low. semgrep hit a parse error in 1 file(s) β `legacy/v1.0/src/Examples/NEventLite Example MVC/Scripts/_references.js` (line 1) β so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 20 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED (20). β One of this dimension's main actionable groups (20 recommendation-level).
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED (4), REDACTED (2), REDACTED (2). β One of this dimension's main actionable groups (8 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED. β One of this dimension's main actionable groups (1 warning-level).
D30 Β· Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget REDACTED), and the findings above are real and complete for them. nuget was not scanned (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), so this is not the whole dependency surface and the result is reported at reduced confidence.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities β start with REDACTED. β One of this dimension's main actionable groups (1 issue-level).
D34 Β· Knowledge Freshness
19 of 19 significant source file(s) are orphaned β their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/NEventLite/Repository/MasterSession.cs. Counted over 19 of the 88 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 19 Orphaned file finding(s) in Knowledge Freshness β start with AggregateRoot.cs (2), Repository.cs (2), ReflectionHelper.cs (2). β One of this dimension's main actionable groups (19 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. β One of this dimension's main actionable groups (1 recommendation-level).
D35 Β· Change Coupling
No strong hidden change-coupling between production files.
D43 Β· Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 Β· Platform End-of-Life
2 end-of-life runtime(s) and 0 end-of-life framework(s), read from 10 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 3 End-of-life runtime finding(s) in Platform End-of-Life β start with NEventLite.Tests.Integration.csproj, NEventLite.Samples.ConsoleApp.csproj, NEventLite.Samples.Autofac.csproj. β One of this dimension's main actionable groups (3 warning-level).
Frontend & cross-cutting dimensions
AX1 Β· Captive dependencies
AX10 Β· Code composition
AX2 Β· Stateful singletons
- `EventstoreConnection` 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 (_connection; e.g. `_connection` at line 18). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. β legacy/v1.0/src/Examples/NEventLite Example/Util/EventstoreConnection.cs:7
- `RedisConnection` 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 (_manager; e.g. `_manager` at line 17). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. β legacy/v1.0/src/Examples/NEventLite Example/Util/RedisConnection.cs:6
- `EventstoreStorageProviderBase` 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 (_serializerSetting; e.g. `_serializerSetting` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. β legacy/v1.0/src/Storage Providers/EventStore/EventstoreStorageProviderBase.cs:10
- `LogManager` 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 (_loggers; e.g. `_loggers` at line 18). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. β legacy/v1.0/src/Framework/Logger/LogManager.cs:9
What to do
- 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
AX5 Β· Architecture & structure
AX6 Β· Interface segregation
AX8 Β· Test isolation
DM1 Β· Aggregate boundaries
DM10 Β· One transaction, one aggregate
DM11 Β· Constructible invalid state
- `Note`'s public constructor takes `title`, `desc`, `cat` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `β¦Exception.ThrowIfβ¦(` helper, and so was any method of this type it calls β a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Note` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. β legacy/v1.0/src/Examples/NEventLite Example/Domain/Note.cs:48
- `Schedule`'s public constructor takes `scheduleName` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `β¦Exception.ThrowIfβ¦(` helper, and so was any method of this type it calls β a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Schedule` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. β src/Samples/NEventLite.Samples.Common/Domain/Schedule/Schedule.cs:21
What to do
- Give each aggregate one way in that can refuse β a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 Β· Ambient inputs in the domain
DM4 Β· Rich vs anemic model
DM5 Β· Encapsulated state
- `Schedule` exposes its own state through a mutable collection (Todos) β a caller can add to or remove from it directly, without passing through the methods that enforce the invariants. β src/Samples/NEventLite.Samples.Common/Domain/Schedule/Schedule.cs:12
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 Β· Domain β infrastructure boundary
DM9 Β· Scattered domain decisions
GD1 Β· Unfinished & placeholder code
IC1 Β· Incompleteness & stubs
- `GetEventsAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. β legacy/v1.0/src/Storage Providers/InMemory/InMemoryEventStorageProvider.cs:29
- `GetLastEventAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. β legacy/v1.0/src/Storage Providers/InMemory/InMemoryEventStorageProvider.cs:62
- `CommitChangesAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. β legacy/v1.0/src/Storage Providers/InMemory/InMemoryEventStorageProvider.cs:74
- `GetSnapshotAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×3) β legacy/v1.0/src/Storage Providers/InMemory/InMemorySnapshotStorageProvider.cs:28, REDACTED:23, src/NEventLite/Repository/EventOnlyRepository.cs:22
- `SaveSnapshotAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×3) β legacy/v1.0/src/Storage Providers/InMemory/InMemorySnapshotStorageProvider.cs:39, REDACTED:48, src/NEventLite/Repository/EventOnlyRepository.cs:27
- A line of code has been commented out rather than removed β dead weight that rots and confuses. Delete it (version control remembers). (×3) β legacy/v1.0/src/Framework/Extension/EventExtension.cs:19, legacy/v1.0/src/Framework/Extension/EventExtension.cs:20, legacy/v1.0/src/Framework/Extension/EventExtension.cs:21
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 Β· Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README β the high-level shape.
- Add a README to the 12 of 12 project(s) that lack one β worth up to 2 pts.
M2 Β· Architecture documentation
- No Architecture Decision Records found β no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape β no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is β¦" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document β not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 Β· Folder & project structure
- Tests aren't grouped in a dedicated test folder β the test surface isn't separable from production code at a glance.
What to do
- Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
P1 Β· CI/CD gates
- A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found β changes may merge without the suite running.
What to do
- Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P10 Β· Library API & versioning
- 95/98 types (97%) 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 490 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.
- `src/Extensions/NEventLite.Extensions.Autofac/NEventLite.Extensions.Autofac.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices β including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. β src/Extensions/NEventLite.Extensions.Autofac/NEventLite.Extensions.Autofac.csproj:18
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.
P6 Β· Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file β what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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
- 3 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). β legacy/v1.0/src/Examples/NEventLite Example/Util/EventstoreConnection.cs:19
- `.GetAwaiter().GetResult()` 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). (×2) β src/NEventLite/Core/Domain/AggregateRoot.cs:83, src/Storage/NEventLite.StorageProviders.EventStore/Core/EventStoreStorageConnectionProvider.cs:36
- Only 2/54 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 SnapshotStorageProvider.GetSnapshotAsync(typeof(T), 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)`. β legacy/v1.0/src/Framework/Repository/Repository.cs:42
- `await EventStorageProvider.GetEventsAsync(typeof(T), id, snapshot.Version + 1, int....` 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)`. β legacy/v1.0/src/Framework/Repository/Repository.cs:49
- `await EventStorageProvider.GetEventsAsync(typeof(T), id, 0, int.MaxValue)` 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)`. β legacy/v1.0/src/Framework/Repository/Repository.cs:54
- `await CommitChanges(aggregate)` 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) β legacy/v1.0/src/Framework/Repository/Repository.cs:70, src/NEventLite/Repository/Repository.cs:84
- `await EventStorageProvider.GetLastEventAsync(aggregate.GetType(), aggregate.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)`. β legacy/v1.0/src/Framework/Repository/Repository.cs:78
- `await EventStorageProvider.CommitChangesAsync(aggregate)` 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)`. β legacy/v1.0/src/Framework/Repository/Repository.cs:98
- `await EventPublisher.PublishAsync(e)` 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)`. β legacy/v1.0/src/Framework/Repository/Repository.cs:103
- `await SnapshotStorageProvider.SaveSnapshotAsync(aggregate.GetType(), snapshottable....` 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)`. β legacy/v1.0/src/Framework/Repository/Repository.cs:120
- `await Repository.GetByIdAsync<TAggregate>(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)`. β legacy/v1.0/src/Framework/Repository/RepositoryDecorator.cs:21
- `await Repository.SaveAsync(aggregate)` 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)`. β legacy/v1.0/src/Framework/Repository/RepositoryDecorator.cs:26
- `await _repository.GetByIdAsync<T>(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)`. β legacy/v1.0/src/Framework/Unit Of Work/UnitOfWork.cs:43
- `await _repository.SaveAsync(aggregate)` 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)`. β legacy/v1.0/src/Framework/Unit Of Work/UnitOfWork.cs:66
- `await _loadLock.WaitAsync()` 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/NEventLite/Core/Domain/AggregateRoot.cs:63, src/NEventLite/Core/Domain/AggregateRoot.cs:89
- `await ApplyEventAsync(e, false)` 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/NEventLite/Core/Domain/AggregateRoot.cs:70
- `await ApplyEventAsync(@event, true)` 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/NEventLite/Core/Domain/AggregateRoot.cs:93
- `await _applyLock.WaitAsync()` 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/NEventLite/Core/Domain/AggregateRoot.cs:107
- `await DoApplyAsync(@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/NEventLite/Core/Domain/AggregateRoot.cs:113
- `await @event.InvokeOnAggregateAsync(this, _eventHandlerCache[@event.GetType()])` 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/NEventLite/Core/Domain/AggregateRoot.cs:152
- `await _syncLock.WaitAsync()` 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/NEventLite/Repository/MasterSession.cs:49, src/NEventLite/Repository/MasterSession.cs:135
- `await (Task<TAggregate>)typeContainer.GetByIdMethod(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/NEventLite/Repository/MasterSession.cs:68
- `await saveMethod(keyValuePair.Value)` 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/NEventLite/Repository/MasterSession.cs:145
- `await GetLatestSnapshotAsync(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/NEventLite/Repository/Repository.cs:44
- `await _eventStorageProvider.GetEventsAsync<TAggregate, TAggregateKey>(id, snapshot....` 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/NEventLite/Repository/Repository.cs:59
- `await item.LoadsFromHistoryAsync(events)` 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/NEventLite/Repository/Repository.cs:60, src/NEventLite/Repository/Repository.cs:69
- `await _eventStorageProvider.GetEventsAsync<TAggregate, TAggregateKey>(id, 0, long.M...` 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/NEventLite/Repository/Repository.cs:64
- `await _eventStorageProvider.GetLastEventAsync<TAggregate, TAggregateKey>(aggregate.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/NEventLite/Repository/Repository.cs:92
- `await _eventStorageProvider.SaveAsync<TAggregate, TAggregateKey>(aggregate.Id, chan...` 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/NEventLite/Repository/Repository.cs:116
- `await PublishEventsAsync(changesToCommit)` 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/NEventLite/Repository/Repository.cs:119
- `await SaveSnapshotAsync(aggregate, changesToCommit)` 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/NEventLite/Repository/Repository.cs:122
- `await _snapshotStorageProvider.GetSnapshotAsync<TSnapshot, TAggregateKey>(aggregateId)` 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/NEventLite/Repository/Repository.cs:130
- `await _snapshotStorageProvider.SaveSnapshotAsync<TSnapshot, TAggregateKey>(snapshot)` 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/NEventLite/Repository/Repository.cs:148
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. (×2) β legacy/v1.0/src/Examples/NEventLite Example/Util/EventstoreConnection.cs:19, src/NEventLite/Core/Domain/AggregateRoot.cs:83
- Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and β where callers can use it β add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. β src/Storage/NEventLite.StorageProviders.EventStore/Core/EventStoreStorageConnectionProvider.cs:36
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
X19 Β· Unrestored process-global state
X2 Β· Cancellation propagation
- Only 0/41 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up β whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice β judge against your hosting model.
- No CancellationToken parameter β this work can't be stopped early once started. (×39) β legacy/v1.0/src/Examples/NEventLite Example/Command Bus/MyCommandBus.cs:23, legacy/v1.0/src/Examples/NEventLite Example/Command Handler/NoteCommandHandler.cs:19, legacy/v1.0/src/Examples/NEventLite Example/Command Handler/NoteCommandHandler.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
X5 Β· Nullable reference types
- 0/1 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.
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 | 50% | Adequate β gated by D18, 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 | 40% | Weak β gated by D34, M2 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Readiness | 45% | Weak β gated by P3 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Security | 46% | Weak β gated by D29, D44 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Domain Modelling | 75% | Strong | Strongest area. |
| Performance | 38% | Weak β gated by PF3 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
Unscored β 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene β 1 observation(s) recorded Β· Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate β 4 observation(s) recorded Β· Advisory β this card reports evidence and never carries a score.
Not evidenced β 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback β not evidenced β no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup β not evidenced β repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included β 52 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
- AX9 CQS / query purity β no CQRS query handlers detected β query purity is not applicable to this codebase
- 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.
- D11 Test Reliability β Test runner surfaced no tests
- D12 Dependency Hygiene β Dependency hygiene not measured
- D16 Bus Factor β dormant codebase β no living knowledge left to concentrate
- 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.
- D22 Internal API Consistency β No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling β small single-context codebase (4,906 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 (NEventLite), 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
- D31 IaC & Container Security β No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) β 1 file(s) were not parsed by semgrep β the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing β 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.
- 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
- DM2 Strongly-typed ids β no id-bearing domain types detected β strongly-typed-id adoption not assessable
- DM3 Integration-event coupling β no integration events detected β coupling check not applicable
- DM7 Repository granularity β no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities β not scored β the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven β applicable but not scored (2 of 3 signals for this style β below the bar we score at): 1 event handler(s); 5 CQRS handler(s)
- ED5 Idempotency β not scored β 6 of 6 retry-prone mutations could not be classified (no visible guard and no positive evidence of a double-applied effect)
- ES1 Event Sourcing β not scored β this repository shows only 1 of the 3 signals this lens looks for (an event-store package (Marten/EventStore))
- M4 Documentation accuracy β Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty β Reported, not scored β and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience β no outbound HTTP usage detected β no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P8 Schema migrations β no EF Core usage detected
- 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.
- X4 Structured logging β This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message β its own wrapper, log4net, Console or Debug β so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
- 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 β 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious β 109 finding(s)
- Async method without CancellationToken: ExecuteAsync legacy/v1.0/src/Examples/NEventLite Example/Command Bus/MyCommandBus.cs:23
- Async method without CancellationToken: HandleCommandAsync legacy/v1.0/src/Examples/NEventLite Example/Command Handler/NoteCommandHandler.cs:19
- Async method without CancellationToken: HandleCommandAsync legacy/v1.0/src/Examples/NEventLite Example/Command Handler/NoteCommandHandler.cs:28
- Async method without CancellationToken: PublishAsync legacy/v1.0/src/Examples/NEventLite Example/Event Bus/MyEventPublisher.cs:24
- Async method without CancellationToken: DoMockRunAsync legacy/v1.0/src/Examples/NEventLite Example/Program.cs:42
- Async method without CancellationToken: GetByIdAsync legacy/v1.0/src/Examples/NEventLite Example/Repository/MyRepositoryDecorator.cs:21
- Async method without CancellationToken: SaveAsync legacy/v1.0/src/Examples/NEventLite Example/Repository/MyRepositoryDecorator.cs:29
- Async method without CancellationToken: SaveAsync legacy/v1.0/src/Examples/NEventLite Example/Repository/NoteRepository.cs:19
- Async method without CancellationToken: GetEventsAsync legacy/v1.0/src/Storage Providers/EventStore/EventstoreEventStorageProvider.cs:17
- Async method without CancellationToken: ReadEvents legacy/v1.0/src/Storage Providers/EventStore/EventstoreEventStorageProvider.cs:26
- Async method without CancellationToken: GetLastEventAsync legacy/v1.0/src/Storage Providers/EventStore/EventstoreEventStorageProvider.cs:64
- Async method without CancellationToken: CommitChangesAsync legacy/v1.0/src/Storage Providers/EventStore/EventstoreEventStorageProvider.cs:81
- Async method without CancellationToken: GetSnapshotAsync REDACTED:18
- Async method without CancellationToken: SaveSnapshotAsync REDACTED:37
- Async method without CancellationToken: GetSnapshotAsync REDACTED:51
- Async method without CancellationToken: Create legacy/v1.0/src/Examples/NEventLite Example MVC/Controllers/NoteDtoController.cs:32
- Async method without CancellationToken: Edit legacy/v1.0/src/Examples/NEventLite Example MVC/Controllers/NoteDtoController.cs:61
- Async method without CancellationToken: GetByIdAsync legacy/v1.0/src/Framework/Repository/Repository.cs:33
- Async method without CancellationToken: SaveAsync legacy/v1.0/src/Framework/Repository/Repository.cs:66
- Async method without CancellationToken: CommitChanges legacy/v1.0/src/Framework/Repository/Repository.cs:74
- Async method without CancellationToken: GetByIdAsync legacy/v1.0/src/Framework/Repository/RepositoryDecorator.cs:19
- Async method without CancellationToken: SaveAsync legacy/v1.0/src/Framework/Repository/RepositoryDecorator.cs:24
- Async method without CancellationToken: GetAsync legacy/v1.0/src/Framework/Unit Of Work/UnitOfWork.cs:31
- Async method without CancellationToken: CommitAsync legacy/v1.0/src/Framework/Unit Of Work/UnitOfWork.cs:62
- Async method without CancellationToken: LoadsFromHistoryAsync src/NEventLite/Core/Domain/AggregateRoot.cs:61
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Repository/Repository.cs:42
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Repository/Repository.cs:49
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Repository/Repository.cs:54
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Repository/Repository.cs:70
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Repository/Repository.cs:78
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Repository/Repository.cs:98
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Repository/Repository.cs:103
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Repository/Repository.cs:120
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Repository/RepositoryDecorator.cs:21
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Repository/RepositoryDecorator.cs:26
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Unit Of Work/UnitOfWork.cs:43
- Awaits without ConfigureAwait(false) legacy/v1.0/src/Framework/Unit Of Work/UnitOfWork.cs:66
- Awaits without ConfigureAwait(false) src/NEventLite/Core/Domain/AggregateRoot.cs:63
- Awaits without ConfigureAwait(false) src/NEventLite/Core/Domain/AggregateRoot.cs:70
- Awaits without ConfigureAwait(false) src/NEventLite/Core/Domain/AggregateRoot.cs:89
- Awaits without ConfigureAwait(false) src/NEventLite/Core/Domain/AggregateRoot.cs:93
- Awaits without ConfigureAwait(false) src/NEventLite/Core/Domain/AggregateRoot.cs:107
- Awaits without ConfigureAwait(false) src/NEventLite/Core/Domain/AggregateRoot.cs:113
- Awaits without ConfigureAwait(false) src/NEventLite/Core/Domain/AggregateRoot.cs:152
- Awaits without ConfigureAwait(false) src/NEventLite/Repository/MasterSession.cs:49
- Awaits without ConfigureAwait(false) src/NEventLite/Repository/MasterSession.cs:68
- Awaits without ConfigureAwait(false) src/NEventLite/Repository/MasterSession.cs:135
- Awaits without ConfigureAwait(false) src/NEventLite/Repository/MasterSession.cs:145
- Awaits without ConfigureAwait(false) src/NEventLite/Repository/Repository.cs:44
- Fake-async β async method never awaits legacy/v1.0/src/Storage Providers/InMemory/InMemoryEventStorageProvider.cs:29
- Fake-async β async method never awaits legacy/v1.0/src/Storage Providers/InMemory/InMemoryEventStorageProvider.cs:62
- Fake-async β async method never awaits legacy/v1.0/src/Storage Providers/InMemory/InMemoryEventStorageProvider.cs:74
- Fake-async β async method never awaits legacy/v1.0/src/Storage Providers/InMemory/InMemorySnapshotStorageProvider.cs:28
- Fake-async β async method never awaits legacy/v1.0/src/Storage Providers/InMemory/InMemorySnapshotStorageProvider.cs:39
- Fake-async β async method never awaits REDACTED:23
- Fake-async β async method never awaits REDACTED:48
- Fake-async β async method never awaits src/NEventLite/Repository/EventOnlyRepository.cs:22
- Fake-async β async method never awaits src/NEventLite/Repository/EventOnlyRepository.cs:27
- Process-global static state: EventstoreConnection legacy/v1.0/src/Examples/NEventLite Example/Util/EventstoreConnection.cs:7
- Process-global static state: RedisConnection legacy/v1.0/src/Examples/NEventLite Example/Util/RedisConnection.cs:6
- Process-global static state: EventstoreStorageProviderBase legacy/v1.0/src/Storage Providers/EventStore/EventstoreStorageProviderBase.cs:10
- Process-global static state: LogManager legacy/v1.0/src/Framework/Logger/LogManager.cs:9
- Sync-over-async blocking
- Sync-over-async blocking legacy/v1.0/src/Examples/NEventLite Example/Util/EventstoreConnection.cs:19
- Sync-over-async blocking src/NEventLite/Core/Domain/AggregateRoot.cs:83
- Sync-over-async blocking src/Storage/NEventLite.StorageProviders.EventStore/Core/EventStoreStorageConnectionProvider.cs:36
- End-of-life runtime: .NET netcoreapp2.1 src/NEventLite.Tests.Integration/NEventLite.Tests.Integration.csproj:4
- End-of-life runtime: .NET netcoreapp2.1 src/Samples/NEventLite.Samples.ConsoleApp/NEventLite.Samples.ConsoleApp.csproj:5
- End-of-life runtime: .NET netcoreapp3.1 src/Samples/NEventLite.Samples.Autofac/NEventLite.Samples.Autofac.csproj:5
- Sync-over-async (deadlock risk) legacy/v1.0/src/Examples/NEventLite Example/Util/EventstoreConnection.cs:19
- Sync-over-async (deadlock risk) src/NEventLite/Core/Domain/AggregateRoot.cs:83
- Sync-over-async (deadlock risk) src/Storage/NEventLite.StorageProviders.EventStore/Core/EventStoreStorageConnectionProvider.cs:36
- Constructible in an invalid state: Note legacy/v1.0/src/Examples/NEventLite Example/Domain/Note.cs:48
- Constructible in an invalid state: Schedule src/Samples/NEventLite.Samples.Common/Domain/Schedule/Schedule.cs:21
- CommentedOutCode legacy/v1.0/src/Framework/Extension/EventExtension.cs:19
- Build failed
- REDACTED
- Duplicated block (17 lines × 2) legacy/v1.0/src/Framework/Domain/AggregateRoot.cs:149
- Duplicated block (14 lines × 2) legacy/v1.0/src/Framework/Extension/ReflectionHelper.cs:53
- Duplicated block (10 lines × 2) src/Storage/NEventLite.StorageProviders.EventStore/Core/EventstoreStorageCore.cs:49
- Duplicated block (5 lines × 3) src/Samples/NEventLite.Samples.Autofac/Program.cs:74
- Mutable entity: Schedule src/Samples/NEventLite.Samples.Common/Domain/Schedule/Schedule.cs:12
- NuGet dependencies are not locked
Minor β 73 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file src/NEventLite/Repository/MasterSession.cs:1
- Orphaned file legacy/v1.0/src/Framework/Domain/AggregateRoot.cs:1
- Orphaned file src/NEventLite/Repository/Repository.cs:1
- Orphaned file src/NEventLite/Core/Domain/AggregateRoot.cs:1
- Orphaned file src/Storage/NEventLite.StorageProviders.EventStore/EventStoreEventStorageProvider.cs:1
- Orphaned file legacy/v1.0/src/Framework/Repository/Repository.cs:1
- Orphaned file src/NEventLite/Util/ReflectionHelper.cs:1
- Orphaned file src/Storage/NEventLite.StorageProviders.InMemory/InMemoryEventStorageProvider.cs:1
- Orphaned file legacy/v1.0/src/Framework/Extension/ReflectionHelper.cs:1
- Orphaned file legacy/v1.0/src/Storage Providers/EventStore/EventstoreEventStorageProvider.cs:1
- Orphaned file src/NEventLite/Repository/Session.cs:1
- Orphaned file src/Storage/NEventLite.StorageProviders.EventStore/Core/EventstoreStorageCore.cs:1
- Orphaned file legacy/v1.0/src/Storage Providers/EventStore/EventstoreStorageProviderBase.cs:1
- Orphaned file src/NEventLite/Util/AssemblyExtensions.cs:1
- Orphaned file legacy/v1.0/src/Storage Providers/InMemory/InMemoryEventStorageProvider.cs:1
- Orphaned file src/Storage/NEventLite.StorageProviders.EventStore/EventStoreSnapshotStorageProvider.cs:1
- Orphaned file REDACTED:1
- Orphaned file src/Extensions/NEventLite.Extensions.Autofac/Extensions.cs:1
- Orphaned file src/Storage/NEventLite.StorageProviders.InMemory/InMemorySnapshotStorageProvider.cs:1
- redundant comment legacy/v1.0/src/Framework/Repository/Repository.cs:97
- redundant comment legacy/v1.0/src/Storage Providers/Properties/AssemblyInfo.cs:4
- redundant comment legacy/v1.0/src/Storage Providers/Properties/AssemblyInfo.cs:16
- redundant comment legacy/v1.0/src/Storage Providers/Properties/AssemblyInfo.cs:21
- redundant comment legacy/v1.0/src/Storage Providers/Properties/AssemblyInfo.cs:24
- redundant comment legacy/v1.0/src/Unit Tests/Properties/AssemblyInfo.cs:5
- redundant comment legacy/v1.0/src/Unit Tests/Properties/AssemblyInfo.cs:17
- redundant comment legacy/v1.0/src/Unit Tests/Properties/AssemblyInfo.cs:22
- redundant comment legacy/v1.0/src/Unit Tests/Properties/AssemblyInfo.cs:25
- redundant comment src/NEventLite/Repository/Repository.cs:115
- Duplicated predicate src/Storage/NEventLite.StorageProviders.InMemory/InMemoryEventStorageProvider.cs:38
- Duplicated predicate legacy/v1.0/src/Framework/Extension/ReflectionHelper.cs:57
- Duplicated predicate src/Extensions/NEventLite.Extensions.Microsoft.DependencyInjection/Extensions.cs:48
- Duplicated predicate legacy/v1.0/src/Framework/Extension/ReflectionHelper.cs:62
- Commented-out code legacy/v1.0/src/Framework/Extension/EventExtension.cs:19
- Commented-out code legacy/v1.0/src/Framework/Extension/EventExtension.cs:20
- Commented-out code legacy/v1.0/src/Framework/Extension/EventExtension.cs:21
- `CommitChanges` returns an awaitable but lacks the `Async` suffix its 13 peers carry legacy/v1.0/src/Framework/Repository/Repository.cs:74
- `CommitChanges` returns an awaitable but lacks the `Async` suffix its 20 peers carry src/NEventLite/Repository/Repository.cs:88
- Scattered collaborators
- Pass-through layer legacy/v1.0/src/Examples/NEventLite Example/Read Model/MyReadRepository.cs:9
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- No tests/ separation
- CI test execution not evidenced
- Large public API surface
- No SAST
- No dependency-update automation src/Extensions/NEventLite.Extensions.Autofac/NEventLite.Extensions.Autofac.csproj:18
- No changelog
- No performance benchmarks
- Not all async methods take a CancellationToken
- Nullable reference types not enabled everywhere
Minor β 1 finding(s)
- doc comments repeat the names legacy/v1.0/src/Framework/Event/Event.cs:34
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-2f62ff361ccf43c4a1f54c1bb86e9e01/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-2f62ff361ccf43c4a1f54c1bb86e9e01/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 . | 29 | 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 | β |
| D30 Β· Dependency Vulnerabilities | 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-5fae6cb438a14fe391f57b5a3a1e0b8d | 1 | artifacts/raw/osv-scanner.json |
| D31 Β· IaC & Container Security | trivy | β | trivy: not applicable β No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | β |
| D32 Β· Data Compliance (PII/GDPR) | semgrep | β | semgrep: not applicable β No personal data was found crossing a boundary the PII/GDPR ruleset checks β nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) β `legacy/v1.0/src/Examples/NEventLite Example MVC/Scripts/_references.js` β so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | β |
| D37 Β· Vulnerability-disclosure Policy | disclosure | β | disclosure: not applicable β No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | β |
| D40 Β· Network Egress Confinement | runtime-hardening | β | runtime-hardening: not applicable β No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | β |
| D41 Β· Kernel & Syscall Confinement | runtime-hardening | β | runtime-hardening: not applicable β No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | β |
| D42 Β· Runtime Threat Enforcement | runtime-hardening | β | runtime-hardening: not applicable β No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | β |
| D43 Β· Malicious Dependencies | osv-scanner | β | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-5fae6cb438a14fe391f57b5a3a1e0b8d | 0 | artifacts/raw/osv-scanner.json |