lucabriguglia/Memoria

Executive summary

lucabriguglia/Memoria scores 45 out of 100 and is rated Weak, while five of its seven lenses score higher still: Event-Driven at 100 and Architecture at 96, both rated Exemplary, Code Health at 74, rated Strong, and Security and Compliance at 61 and Performance at 52, both rated Adequate.

The score is lower than those five because the weakest lens counts most, and here that is Production Readiness, which scores 35 and is rated Weak. Its Observability dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 19 Deprecated finding(s) in Dependency Hygiene and to adopt ILogger (or Serilog) and log at meaningful points across the projects, and if Production Readiness rose to 70, the score would rise from 45 to about 52.

11 findings are critical: eight in Static Analysis (SAST), one in Dependency Vulnerabilities, one in Explicit Debt and one in Project dependency cycles.

Watchdog couldn't measure Internal API Consistency in this code, so that dimension is left out of the score. The product code is 21,489 lines, which would take an estimated 0.3 person-years, around €47,000, to rebuild.

Code Health 74 Strong Architecture 96 ★ Exemplary Maturity 41 Weak, capped by Architecture documentation and Documentation accuracy Production Readiness 35 Weak, capped by Observability, Security & performance tooling and Schema migrations Security and Compliance 61 Adequate, capped by Supply-chain Provenance & Signing and Data Protection Event-Driven 100 ★ Exemplary Performance 52 Adequate, capped by Async & latency hygiene

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Production Readiness 35 · counts for 46%Maturity 41 · counts for 25%Performance 52 · counts for 14%Security and Compliance 61 · counts for 8%Code Health 74 · counts for 4%Architecture 96 · counts for 2%Event-Driven 100 · counts for 1%

If Production Readiness rose from 35 to 70, the lowest score rated Strong, the score would rise from 45 to about 52.

Code composition: what the lines of code are

Business logic 13%Supporting code 26%Tests 61%

New since the last survey: 232 findings

These 232 critical or serious findings weren't in the previous survey, on 6 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

Cognitive Complexity · ContentionBenchmark.Measure (cognitive 21) benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs
Code Duplication · Members sharing a duplicated core (16 members, 50+ identical tokens) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs
Dependency Hygiene · Deprecated: xunit tests/Memoria.Caching.Memory.Tests/Memoria.Caching.Memory.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.Caching.Redis.Tests/Memoria.Caching.Redis.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Relational.Tests/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Relational.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Tests/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Dcb.Tests/Memoria.EventSourcing.Dcb.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Store.Cosmos.InMemory.Tests/Memoria.EventSourcing.Store.Cosmos.InMemory.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Store.Cosmos.Tests/Memoria.EventSourcing.Store.Cosmos.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Npgsql.Tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Npgsql.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Relational.Tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Relational.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Store.Tests/Memoria.EventSourcing.Store.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.EventSourcing.Tests/Memoria.EventSourcing.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.Messaging.RabbitMq.InMemory.Tests/Memoria.Messaging.RabbitMq.InMemory.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.Messaging.RabbitMq.Tests/Memoria.Messaging.RabbitMq.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.Messaging.ServiceBus.InMemory.Tests/Memoria.Messaging.ServiceBus.InMemory.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.Messaging.ServiceBus.Tests/Memoria.Messaging.ServiceBus.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.Tests/Memoria.Tests.csproj
Dependency Hygiene · Deprecated: xunit tests/Memoria.Validation.FluentValidation.Tests/Memoria.Validation.FluentValidation.Tests.csproj
Explicit Debt · EmptyCatchBlock src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs
Explicit Debt · Dead code: SupportsDcb benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs
Explicit Debt · Dead code: TheInstallScriptProducesTheSchemaTheModelDeclares tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs
Explicit Debt · Dead code: TheInstallScriptIsIdempotent tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs
Explicit Debt · Dead code: TheScriptedTagColumnsAreCaseSensitive tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs
Explicit Debt · Dead code: TheInstallScriptProducesTheSchemaTheModelDeclares tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs
Explicit Debt · Dead code: TheInstallScriptIsIdempotent tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs
Explicit Debt · Dead code: TheScriptedTagColumnsAreByteOrdered tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs
Explicit Debt · Dead code: GivenA150Database_ThenTheScriptDropsOnlyTheLinkTable tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DropAggregateEventsScriptTests.cs
Explicit Debt · Dead code: GivenTheTableIsAlreadyGone_ThenTheScriptIsStillSafeToRun tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DropAggregateEventsScriptTests.cs
Explicit Debt · Dead code: GivenA150Database_ThenTheScriptDropsOnlyTheLinkTable tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DropAggregateEventsScriptTests.cs
Explicit Debt · Dead code: GivenTheTableIsAlreadyGone_ThenTheScriptIsStillSafeToRun tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DropAggregateEventsScriptTests.cs
Explicit Debt · Dead code: A_postgresql_fixture_on_an_existing_server_drops_the_databases_it_handed_out tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/ExistingServerTests.cs
Explicit Debt · Dead code: A_postgresql_fixture_leaves_databases_it_did_not_hand_out tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/ExistingServerTests.cs
Explicit Debt · Dead code: A_sql_server_fixture_on_an_existing_server_drops_the_databases_it_handed_out tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/ExistingServerTests.cs
Explicit Debt · Dead code: A_sql_server_fixture_leaves_databases_it_did_not_hand_out tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/ExistingServerTests.cs
Explicit Debt · Dead code: A_migration_installs_the_routine_for_the_default_model tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlAppendRoutineInstallTests.cs
Explicit Debt · Dead code: A_migration_installs_the_routine_for_a_remapped_model tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlAppendRoutineInstallTests.cs
Explicit Debt · Dead code: Dropping_the_routine_in_a_migration_removes_only_that_mapping_s_routine tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlAppendRoutineInstallTests.cs
Explicit Debt · Dead code: The_script_a_migration_and_EnsureDcbAppendRoutineAsync_install_the_same_routine tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlAppendRoutineInstallTests.cs
Explicit Debt · Dead code: The_generated_routine_ends_its_lines_the_same_whatever_machine_built_the_store tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlAppendRoutineInstallTests.cs
Explicit Debt · Dead code: EventsAndSnapshotsRoundTripThroughJsonbColumns tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlDcbJsonbTests.cs
Explicit Debt · Dead code: TheInstallScriptProducesTheSchemaTheModelDeclares tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlInstallScriptTests.cs
Explicit Debt · Dead code: TheInstallScriptIsIdempotent tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlInstallScriptTests.cs
Explicit Debt · Dead code: TheRevertedDatabaseHasThePreMigrationIndexes tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlMigrationScriptTests.cs
Explicit Debt · Dead code: TheScriptProducesTheIndexesTheModelDeclares tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlMigrationScriptTests.cs
Explicit Debt · Dead code: TheScriptIsIdempotent tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlMigrationScriptTests.cs
Explicit Debt · Dead code: A_jsonb_model_appends_and_saves_in_one_round_trip_each tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlRemappedModelAppendTests.cs
Explicit Debt · Dead code: A_model_mapped_to_other_tables_columns_and_schema_appends_and_saves_in_one_round_trip_each tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlRemappedModelAppendTests.cs
Explicit Debt · Dead code: Two_contexts_mapping_different_tables_in_one_database_each_have_their_own_routine tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlRemappedModelAppendTests.cs
Explicit Debt · Dead code: TheStoreSchemaCanBeCreated tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSchemaTests.cs
Explicit Debt · Dead code: UnboundedStringKeysBecomeUnboundedText tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSchemaTests.cs
Explicit Debt · Dead code: A_guarded_append_over_existing_tag_heads_is_one_database_command tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_guarded_append_introducing_new_tags_is_one_database_command tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_refused_append_reports_both_positions_writes_nothing_and_records_the_conflict tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_append_waiting_on_a_tag_head_is_refused_when_the_holder_moves_its_boundary tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: Concurrent_appends_on_one_boundary_are_never_both_accepted_on_the_same_position tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_append_through_the_routine_is_stamped_as_the_entity_framework_core_path_stamps_it tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_append_without_the_routine_installed_says_how_to_install_it tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: Installing_the_routine_twice_is_harmless tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_append_conditioned_on_an_intersection_is_one_database_command tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_aggregate_save_conditioned_on_an_intersection_is_one_database_command tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_event_carrying_only_some_of_an_intersection_s_tags_does_not_move_it tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_append_on_an_intersection_waiting_on_a_tag_head_is_refused_when_the_holder_appends_into_it tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_append_on_an_intersection_waiting_on_a_tag_head_is_accepted_when_the_holder_appends_beside_it tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_unconditional_append_is_one_database_command tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_unconditional_aggregate_save_is_one_database_command tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: An_unconditional_append_refuses_a_conditioned_append_that_read_before_it tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_change_staged_on_the_context_commits_with_the_append tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_change_staged_on_the_context_commits_with_an_aggregate_save tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_refused_append_saves_no_staged_change_and_leaves_it_pending tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_staged_change_that_cannot_be_saved_fails_the_append tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_retried_append_saves_its_staged_change_again tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_guarded_aggregate_save_writing_its_first_snapshot_is_one_database_command tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_guarded_aggregate_save_replacing_its_snapshot_is_one_database_command tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_saved_aggregate_reads_back_from_its_snapshot_at_the_position_it_appended tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_snapshot_only_save_is_one_database_command_and_is_not_checked tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_refused_aggregate_save_writes_neither_events_nor_snapshot tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: A_snapshot_keeps_its_creation_stamp_and_takes_a_new_update_stamp_when_replaced tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: Saving_an_older_aggregate_does_not_replace_a_newer_snapshot tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs
Explicit Debt · Dead code: GivenA170Database_ThenTheScriptProducesTheSchemaTheModelDeclares tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/RenameEventsScriptTests.cs
Explicit Debt · Dead code: GivenStoredEvents_ThenTheStoreReadsThemBackAfterTheRename tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/RenameEventsScriptTests.cs
Explicit Debt · Dead code: GivenTheRenameAlreadyHappened_ThenTheScriptIsStillSafeToRun tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/RenameEventsScriptTests.cs
Explicit Debt · Dead code: GivenBothTablesExist_ThenTheScriptRefusesRatherThanStrandTheEvents tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/RenameEventsScriptTests.cs
Explicit Debt · Dead code: GivenA170Database_ThenTheScriptProducesTheSchemaTheModelDeclares tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/RenameEventsScriptTests.cs
Explicit Debt · Dead code: GivenStoredEvents_ThenTheStoreReadsThemBackAfterTheRename tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/RenameEventsScriptTests.cs
Explicit Debt · Dead code: GivenTheRenameAlreadyHappened_ThenTheScriptIsStillSafeToRun tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/RenameEventsScriptTests.cs
Explicit Debt · Dead code: GivenBothTablesExist_ThenTheScriptRefusesRatherThanStrandTheEvents tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/RenameEventsScriptTests.cs
Explicit Debt · Dead code: A_migration_installs_the_procedure_for_the_default_model tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerAppendRoutineInstallTests.cs
Explicit Debt · Dead code: A_migration_installs_the_procedure_for_a_remapped_model tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerAppendRoutineInstallTests.cs
Explicit Debt · Dead code: Dropping_the_procedure_in_a_migration_removes_only_that_mapping_s_procedure tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerAppendRoutineInstallTests.cs
Explicit Debt · Dead code: The_script_a_migration_and_EnsureDcbAppendRoutineAsync_install_the_same_procedure tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerAppendRoutineInstallTests.cs
Explicit Debt · Dead code: TheInstallScriptProducesTheSchemaTheModelDeclares tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerInstallScriptTests.cs
Explicit Debt · Dead code: TheInstallScriptIsIdempotent tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerInstallScriptTests.cs
Explicit Debt · Dead code: GivenIdsThatOnceExceededTheCompositeKeyLimit_ThenTheAggregateSaves tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerLongIdentifierTests.cs
Explicit Debt · Dead code: TheRevertedDatabaseHasThePreMigrationIndexes tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerMigrationScriptTests.cs
Explicit Debt · Dead code: TheScriptProducesTheIndexesTheModelDeclares tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerMigrationScriptTests.cs
Explicit Debt · Dead code: TheScriptIsIdempotent tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerMigrationScriptTests.cs
Explicit Debt · Dead code: A_model_mapped_to_other_tables_columns_and_schema_appends_and_saves_in_one_round_trip_each tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerRemappedModelAppendTests.cs

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 146 findings

These 146 critical or serious findings were in the previous survey, on 6 October 2026, and are gone from this one. The first 100 are listed here.

Dependency Hygiene · Deprecated: xunit
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → benchmarks)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → examples)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → examples)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → examples)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → examples)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → examples)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → examples)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type AppendCondition (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type AppendCondition (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type TagQuery (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type AppendCondition (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type AppendCondition (Memoria.EventSourcing.Dcb → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type Failure (Memoria → Memoria.EventSourcing.Dcb)
Boundary Type-Coupling · Cross-context type Failure (Memoria → Memoria.EventSourcing.Dcb)
Boundary Type-Coupling · Cross-context type Failure (Memoria → Memoria.EventSourcing.Dcb)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type Failure (Memoria → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type Failure (Memoria → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)
Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.EntityFrameworkCore)

Rebuild cost: about €47,000 · Estimate

Cost to rebuild	€16,000 to €79,000, for 260 to 829 hours of work, about 0.3 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 45. 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	Medium: 21,489 lines of product code
Comment lines	The estimate prices 12,151 lines. Comment lines count towards the size of 21,489 lines but aren't priced as work.

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

Resolve the 19 Deprecated finding(s) in Dependency Hygiene — start with Memoria.Caching.Memory.Tests.csproj, Memoria.Caching.Redis.Tests.csproj, Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Relational.Tests.csproj.

Raises the score by about 5 points · Medium effort · Dependency Hygiene

Adopt ILogger (or Serilog) and log at meaningful points across the projects.

Raises the score by about 5 points · Medium effort · Observability

Reconcile the README with reality: README.md installs the package `Memoria` (`dotnet add package Memoria`), but no project or props file references it; README.md installs the package `Memoria.EventSourcing` (`dotnet add package Memoria.EventSourcing`), but no project or props file references it; README.md installs the package `Memoria.EventSourcing.Store.EntityFrameworkCore` (`dotnet add package Memoria.EventSourcing.Store.EntityFrameworkCore`), but no project or props file references it; benchmarks/README.md names `Store/StoreReadBenchmarks`, but no file or folder `Store/StoreReadBenchmarks` exists; benchmarks/README.md names `Store/StoreWriteBenchmarks`, but no file or folder `Store/StoreWriteBenchmarks` exists.

Raises the score by about 4 points · Medium effort · Documentation accuracy

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk

This code would cost about €47,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 35 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts

What to do: Start with the Production Readiness actions in Top priorities.

If you do one thing first · First action

Resolve the 19 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort, because it clears the 19 Dependency Hygiene findings. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

58 modules, with 101 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 18 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	1 Caching	2 Caching.Memory.Configuration	3 Caching.Redis.Configuration	4 EventSourcing.Domain	5 EventSourcing.Store.Cosmos.Configuration	6 Messaging.RabbitMq.Configuration	7 Results	12 EventSourcing	13 EventSourcing.Store.Cosmos.Documents	14 EventSourcing.Store.EntityFrameworkCore.Entities	15 Messaging	16 Notifications	17 Queries	18 Validation	19 Commands	20 EventSourcing.Dcb	21 EventSourcing.Store.Cosmos	24 EventSourcing.Store.EntityFrameworkCore.Filtering	30 EventSourcing.Dcb.Store.EntityFrameworkCore.Entities	32 EventSourcing.Store.EntityFrameworkCore	35 EventSourcing.Dcb.Store.EntityFrameworkCore
1 Caching
2 Caching.Memory.Configuration
3 Caching.Redis.Configuration
4 EventSourcing.Domain
5 EventSourcing.Store.Cosmos.Configuration
6 Messaging.RabbitMq.Configuration
7 Results
8 Benchmarks				2
9 Caching.Memory	1	1
10 Caching.Memory.Extensions		1
11 Caching.Redis	1		1
12 EventSourcing				13			3
13 EventSourcing.Store.Cosmos.Documents				3
14 EventSourcing.Store.EntityFrameworkCore.Entities				3
15 Messaging							4
16 Notifications							3
17 Queries	1						5
18 Validation							2								4
19 Commands							9				3	3		1
20 EventSourcing.Dcb				6			3	2
21 EventSourcing.Store.Cosmos				13	2		5	2	6
22 EventSourcing.Store.Cosmos.Extensions				15	1		2		7
23 EventSourcing.Store.EntityFrameworkCore.Extensions				11						3
24 EventSourcing.Store.EntityFrameworkCore.Filtering										2
25 Messaging.RabbitMq						1	1				1
26 Messaging.RabbitMq.InMemory							1				1
27 Messaging.ServiceBus							1				1
28 Messaging.ServiceBus.InMemory							1				1
29 Memoria							2					3	3		9
30 EventSourcing.Dcb.Store.EntityFrameworkCore.Entities				2												1
31 EventSourcing.Store.Cosmos.InMemory				12			2	2	6								1
32 EventSourcing.Store.EntityFrameworkCore				10			2	2		6								1
33 EventSourcing.Store.EntityFrameworkCore.Npgsql										1								1
34 Validation.FluentValidation														2	3
35 EventSourcing.Dcb.Store.EntityFrameworkCore				3			1	1								6			8
36 EventSourcing.Dcb.Store.EntityFrameworkCore.Extensions				1												3			1
37 EventSourcing.Store.EntityFrameworkCore.Extensions.DbContextExtensions				6			1	1		3								2		1
38 EventSourcing.Store.EntityFrameworkCore.Identity				3						3										1
39 Benchmarks.Store				4			1	2								4			4	1	2
40 EventSourcing.Dcb.Store.EntityFrameworkCore.Extensions.DbContextExtensions				3			2	1								6			4		2

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 74% · Strong ·

The Good

D1 · .NET / C# Cyclomatic Complexity 10.0 D2 · .NET / C# Cognitive Complexity 9.3 D3 · .NET / C# God Classes 9.8 D4 · .NET / C# Code Duplication 8.5 D18 · .NET / C# Solution Shape 10.0 D39 · .NET / C# IL Efficiency 9.9 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.9 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 8.9 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X4 · Repo Structured logging 10.0 X5 · Repo Nullable reference types 7.2

The Bad

D17 · .NET / C# Explicit Debt 6.9 X1 · Repo Async correctness 6.5 X18 · Repo Disposal-pattern correctness 5.2 X3 · Repo Exception handling 6.8

At a glance — Architecture · 96% · Exemplary ·

The Good

D5 · .NET / C# Coupling 9.8 D6 · .NET / C# Cohesion (LCOM4) 10.0 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 8.5 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 9.2 AX2 · Repo Stateful singletons 10.0 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.8 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0

The Bad

D23 · .NET / C# Boundary Type-Coupling 6.7

At a glance — Maturity · 41% · Weak · gated by M2, M4 ·

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 9.5 D21 · .NET / C# Naming Consistency 10.0 D24 · .NET / C# Comment Value 9.2 D34 · .NET / C# Knowledge Freshness 10.0 M3 · Repo Folder & project structure 10.0

The Bad

M1 · Repo Documentation (README) 6.7

The Ugly

M2 · Repo Architecture documentation 2.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 35% · Weak · gated by P2, P3, P8 ·

The Good

D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D11 · .NET / C# Test Reliability 10.0 D12 · .NET / C# Dependency Hygiene 8.6 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 10.0 P1 · Repo CI/CD gates 10.0 P6 · Repo Release Hygiene 10.0

The Bad

P10 · Repo Library API & versioning 6.0 P4 · Repo Deployment & Rollback 5.0

The Ugly

P2 · Repo Observability 0.0 P3 · Repo Security & performance tooling 1.0 P8 · Repo Schema migrations 3.0

At a glance — Security · 61% · Adequate · gated by D36, C1 ·

The Good

D28 · .NET / C# Secrets (history) 10.0 D29 · .NET / C# Static Analysis (SAST) 8.4 D30 · .NET / C# Dependency Vulnerabilities 9.4 D43 · .NET / C# Malicious Dependencies 10.0 D44 · .NET / C# Platform End-of-Life 10.0 C3 · Repo Audit Trail 9.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Ugly

D36 · .NET / C# Supply-chain Provenance & Signing 0.0 C1 · Repo Data Protection 3.0

At a glance — Event-Driven · 100% · Exemplary ·

The Good

ED1 · Repo Handler temporal coupling 10.0 ED2 · Repo Event/command shape 10.0 ED3 · Repo Event naming 10.0 ED4 · Repo Outbox / dual-write 10.0

At a glance — Performance · 52% · Adequate · gated by PF3 ·

The Good

PF1 · Repo Benchmark discipline 9.5

The Bad

PF2 · Repo Allocation hygiene 6.2

The Ugly

PF3 · Repo Async & latency hygiene 2.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP category	Findings	Severity
A05:2025 — Injection	8	High / Critical
A03:2025 — Software Supply Chain Failures	7	High / Critical

Roadmap

Begin by resolving the 19 deprecated dependencies in the test projects to ensure code hygiene. Next, implement structured logging across service-like projects and update the README to accurately reflect the current codebase structure and packages. Finally, integrate a static analysis security step into the CI pipeline to prevent regressions and document key architectural decisions in a dedicated folder.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Resolve the 19 Deprecated finding(s) in Dependency Hygiene — start with Memoria.Caching.Memory.Tests.csproj, Memoria.Caching.Redis.Tests.csproj, Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Relational.Tests.csproj.	+4.9 pts	Medium	Dependency Hygiene
Adopt ILogger (or Serilog) and log at meaningful points across the projects.	+4.7 pts	Medium	Observability
Reconcile the README with reality: README.md installs the package `Memoria` (`dotnet add package Memoria`), but no project or props file references it; README.md installs the package `Memoria.EventSourcing` (`dotnet add package Memoria.EventSourcing`), but no project or props file references it; README.md installs the package `Memoria.EventSourcing.Store.EntityFrameworkCore` (`dotnet add package Memoria.EventSourcing.Store.EntityFrameworkCore`), but no project or props file references it; benchmarks/README.md names `Store/StoreReadBenchmarks`, but no file or folder `Store/StoreReadBenchmarks` exists; benchmarks/README.md names `Store/StoreWriteBenchmarks`, but no file or folder `Store/StoreWriteBenchmarks` exists.	+4.2 pts	Medium	Documentation accuracy
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.	+4.1 pts	Medium	Security & performance tooling
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.	+3.6 pts	Medium	Architecture documentation
Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly.	+3.1 pts	Medium	Schema migrations
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().	+2.6 pts	Medium	Async & latency hygiene
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.	+1.9 pts	Medium	Deployment & Rollback

File quality

Per-file score 0–10 — a quality signature. Of 95 files carrying findings, judged against the Production bar: 1% slop · 37% mixed · 62% near-clean.

File	Score	Band	Worst signal
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs	4.0	Mixed	Cognitive Complexity: InMemoryCosmosDomainService.SaveAggregate (cognitive 18)
src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs	4.1	Mixed	Code Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens)
src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs	4.9	Mixed	Code Duplication: Duplicated block (23–28 lines × 2)
src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs	5.4	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	5.7	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
examples/Memoria.Examples.Ecommerce.Dcb/Commands/ChangeProductDetailsCommand.cs	6.0	Mixed	Explicit Debt: Dead code: ChangeProductDetailsCommandHandler
src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs	6.3	Mixed	Code Duplication: Duplicated block (8 lines × 2)
tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlSingleCallAppendTests.cs	6.4	Mixed	Explicit Debt: Dead code: A_guarded_append_over_existing_tag_heads_is_one_database_command
tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerSingleCallAppendTests.cs	6.4	Mixed	Explicit Debt: Dead code: The_database_reads_committed_data_as_the_test_says
tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/RenameEventsScriptTests.cs	6.4	Mixed	Explicit Debt: Dead code: GivenA170Database_ThenTheScriptProducesTheSchemaTheModelDeclares
tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs	6.5	Mixed	Explicit Debt: Dead code: TheInstallScriptProducesTheSchemaTheModelDeclares
tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlAppendRoutineInstallTests.cs	6.5	Mixed	Explicit Debt: Dead code: A_migration_installs_the_routine_for_the_default_model
tests/Memoria.Messaging.RabbitMq.Tests/MockRabbitMqTestHelper.cs	6.5	Mixed	Explicit Debt: Dead code: SetupCreateChannelFailure
tests/Memoria.Messaging.ServiceBus.Tests/MockServiceBusTestHelper.cs	6.5	Mixed	Explicit Debt: Dead code: SetupCreateSenderFailure
tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DropAggregateEventsScriptTests.cs	6.6	Mixed	Explicit Debt: Dead code: GivenA150Database_ThenTheScriptDropsOnlyTheLinkTable
tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/ExistingServerTests.cs	6.6	Mixed	Explicit Debt: Dead code: A_postgresql_fixture_on_an_existing_server_drops_the_databases_it_handed_out
tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/SqlServerAppendRoutineInstallTests.cs	6.6	Mixed	Explicit Debt: Dead code: A_migration_installs_the_procedure_for_the_default_model
examples/Memoria.Examples.Ecommerce.Dcb/Commands/CreateProductCommand.cs	6.7	Mixed	Explicit Debt: Dead code: CreateProductCommandHandler
tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlMigrationScriptTests.cs	6.9	Mixed	Explicit Debt: Dead code: TheRevertedDatabaseHasThePreMigrationIndexes

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 11

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.

Serious — 405

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.

Minor — 84

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 4

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 81 of 86 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 86 dimensions across the health lenses

D1D2D3D4D5D6D9D10D11D12D13D14D15D17D18D19D21D23D24D26D27D28D29D30D34D35D36D39D43D44AX1AX10AX2AX3AX5AX6AX8AX9C1C3ED1ED2ED3ED4ED5GD1IC1M1M2M3M4P1P10P2P3P4P6P8PF1PF2PF3X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions

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, 438 of 500 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16018-10eb-72c9-99e9-7ce2be1ed047.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Bundler dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 997 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 4 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D22 Internal API Consistency — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `benchmarks/Memoria.Benchmarks/Program.cs`, `benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs`, `benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs`, `benchmarks/Memoria.Benchmarks/Store/StoreModels.cs`, `src/Memoria.Caching.Memory/MemoryCacheProvider.cs`, … (+37 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
PF3 Async & latency hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 286 further occurrence(s) are not listed individually; the score already reflects all 326.
X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 5 further occurrence(s) are not listed individually; the score already reflects all 45.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.

The LLM boundary

LLM-set scores this run (5): D19, D21, D24, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cyclomatic complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

Do you agree with this assessment?

D2 · Cognitive Complexity9.3 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 100% · ceiling Prevented

4 method(s) exceeded the cognitive complexity threshold of 15; the worst was ContentionBenchmark.Measure at 21.

ContentionBenchmark.Measure (cognitive 21)benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:150

ServiceCollectionExtensions.AddMemoriaEventSourcing (cognitive 19)src/Memoria.EventSourcing/Extensions/ServiceCollectionExtensions.cs:19

InMemoryCosmosDomainService.SaveAggregate (cognitive 18)src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:515

ServiceCollectionExtensions.RegisterHandlers (cognitive 18)src/Memoria/Extensions/ServiceCollectionExtensions.cs:48

What to do

Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with ContentionBenchmark.Measure (cognitive 21), ServiceCollectionExtensions.AddMemoriaEventSourcing (cognitive 19), InMemoryCosmosDomainService.SaveAggregate (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D3 · God Classes9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Prevented

1 god class(es) detected.

ClassTooLong: CosmosDomainServicesrc/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs

What to do

Resolve the 1 ClassTooLong finding(s) in God Classes — start with CosmosDomainService.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D4 · Code Duplication8.5 / 10Strong✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.5 / 10 · rule-coverage 100% · ceiling Verified

69 duplicated block group(s) detected. A further 5 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 6 of the 74 are in trees this repository does not ship — vendored, example/demo, 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.

Duplicated block (12 lines × 2) · ×10src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:631

Duplicated block (9 lines × 2) · ×6src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:613

Duplicated block (17 lines × 2) · ×4src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:22

Duplicated block (10 lines × 2) · ×4src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:62

Duplicated block (19 lines × 2) · ×3src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:205

+ 36 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 10 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with InMemoryCosmosDomainService.cs (4), CosmosDomainService.cs (3), AggregateDocument.cs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 6 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with InMemoryCosmosDomainService.cs, IDomainDbContextExtensions.cs, CosmosDomainService.cs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with InMemoryRabbitMqMessagingProvider.cs (2), ServiceBusMessagingProvider.cs, SubscriptionDecision.cs. — One of this dimension's main actionable groups (4 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.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D5 · Coupling9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Prevented

44 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

Off the main sequence: Memoria.EventSourcing.Store.EntityFrameworkCore.Identitysrc/Memoria.EventSourcing.Store.EntityFrameworkCore.Identity/Memoria.EventSourcing.Store.EntityFrameworkCore.Identity.csproj:1

What to do

Resolve the 1 Off the main sequence finding(s) in Coupling — start with Memoria.EventSourcing.Store.EntityFrameworkCore.Identity.csproj. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 33 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

514 test methods: 505 unit, 9 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, 16 mock references across 514 tests.

Mock-dominated test: DatabaseProperty_ShouldUseOptionsValuestests/Memoria.Caching.Redis.Tests/RedisCacheProviderTests.cs:221

Mock framework: NSubstitute · ×16

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 flaky across 2 measured tier(s). unit: measured (0 flaky); integration: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene8.6 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 100% · ceiling Verified

19 outdated, 0 vulnerable, 1 deprecated packages.

Deprecated: xunit · ×19tests/Memoria.Caching.Memory.Tests/Memoria.Caching.Memory.Tests.csproj:11

Outdated: Microsoft.EntityFrameworkCore.Sqlite · ×19

What to do

Resolve the 19 Deprecated finding(s) in Dependency Hygiene — start with Memoria.Caching.Memory.Tests.csproj, Memoria.Caching.Redis.Tests.csproj, Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Relational.Tests.csproj. — One of this dimension's main actionable groups (19 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 410 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 30 direct `PackageReference`(s), and 214 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D17 · Explicit Debt6.9 / 10Adequate✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 6.9 / 10 · rule-coverage 100% · ceiling Prevented

1 deducted debt markers + 142 dead symbols across 21433 LoC in the .NET projects (1.6/KLoC) → score 6.9.

EmptyCatchBlocksrc/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:283

Dead code: SupportsDcb · ×142benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:203

What to do

Resolve the 142 Dead code finding(s) in Explicit Debt — start with SqlServerSingleCallAppendTests.cs (38), PostgreSqlSingleCallAppendTests.cs (28), RenameEventsScriptTests.cs (8). — One of this dimension's main actionable groups (142 warning-level).
Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with RabbitMqMessagingProvider.cs. — One of this dimension's main actionable groups (1 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

44 projects, 566 source files, 38714 hand-written lines of code (21433 production / 17281 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), 100 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

Do you agree with this assessment?

D19 · Documentation QualityStronggated by 10 serious findings◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Documented

Memoria's documentation is comprehensive and well-structured. The READMEs (2) plus architecture/design docs give an overview of the two libraries, mediator vs event-sourcing modes, a full Concepts guide covering aggregates, projections, providers, read modes, validation, and the result-pattern convention, plus detailed coverage for each Memoria package (e.g. DCB, EF Core, Cosmos). The concepts document is especially thorough: it explains dynamic consistency boundaries as tag-based queries over events rather than fixed streams, glosses through every term in a dedicated Glossary, and gives four concrete read-mode options with trade-offs. The repository's READMEs and XML documentation cover the project well. The root README gives an overview of Memoria with a quickstart for event sourcing and mediator models, plus installation, usage, and contribution guidance. A dedicated Getting started guide covers each store provider (in-memory, Redis, Cosmos) and provides full code examples for every documented feature set. Architecture/Docs markdown files document the project's design in depth, while XML coverage is strong across Memoria packages. (12 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)

Low XML-doc coverage: Memoria.Benchmarks · ×10REDACTED

XML-doc coverage: Memoria.Examples.Ecommerce.Dcb · ×15examples/Memoria.Examples.Ecommerce.Dcb/Memoria.Examples.Ecommerce.Dcb.csproj

What to do

Resolve the 10 Low XML-doc coverage finding(s) in Documentation Quality — start with REDACTED, Memoria.Examples.Caching.Memory.csproj, Memoria.Examples.Caching.Redis.csproj. — One of this dimension's main actionable groups (10 warning-level).

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D23 · Boundary Type-Coupling6.7 / 10Adequate✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

Maturity: Documented → Verified → Prevented · effective 6.7 / 10 · rule-coverage 100% · ceiling Verified

39 domain type(s) cross context boundaries across 18 contexts.

Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) · ×30src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:31

Cross-context type ReadMode (Memoria.EventSourcing → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore) · ×4src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:28

Cross-context type IStreamId (Memoria.EventSourcing → examples) · ×2examples/Memoria.Examples.EventSourcing.Cosmos/Streams/CustomerStreamId.cs:5

Cross-context type ReadMode (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) · ×2src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:31

Cross-context type IStreamId (Memoria.EventSourcing → benchmarks)benchmarks/Memoria.Benchmarks/Store/StoreModels.cs:71

+ 9 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 30 Cross-context type IStreamId (Memoria.EventSourcing →… finding(s) in Boundary Type-Coupling — start with InMemoryCosmosDomainService.cs (17), InMemoryCosmosDataStore.cs (11), InMemoryCosmosStorage.cs (2). — One of this dimension's main actionable groups (30 warning-level).
Resolve the 4 Cross-context type ReadMode (Memoria.EventSourcing →… finding(s) in Boundary Type-Coupling — start with EntityFrameworkCoreDcbDomainService.cs (2), Snapshots.cs (2). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Cross-context type IStreamId (Memoria.EventSourcing → examples) finding(s) in Boundary Type-Coupling — start with CustomerStreamId.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D24 · Comment ValueExemplary◐ Sampled · advisory

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Documented

120 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 44 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D27 · Navigability8.5 / 10Strong✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 8.5 / 10 · rule-coverage 100% · ceiling Documented

80 % of calls cross a namespace and 11 % go through an interface, but 96 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

What to do

Improve Navigability — currently 8.5/10. — 80 % of calls cross a namespace and 11 % go through an interface, but 96 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)8.4 / 10Adequategated by 8 critical findings✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Documented

8 finding(s): 0 critical, 8 high, 0 medium, 0 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 71 file(s) — `benchmarks/Memoria.Benchmarks/Program.cs` (line 28), `benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs` (line 287, line 307, line 414, …), `benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs` (line 234, line 235, lines 235–237, …), `benchmarks/Memoria.Benchmarks/Store/StoreModels.cs` (line 71, line 84, line 94), `examples/Memoria.Examples.Caching.Memory/Queries/GetSomethingQuery.cs` (line 5), … (+66 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 58 of those file(s) — `benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs`, `benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs`, `benchmarks/Memoria.Benchmarks/Store/StoreModels.cs`, `examples/Memoria.Examples.Ecommerce.Dcb/Commands/ChangeProductDetailsCommand.cs`, `examples/Memoria.Examples.Ecommerce.Dcb/Commands/CreateProductCommand.cs`, … (+53 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 2 of those file(s) — `examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Data/SchoolDbContext.cs`, `examples/Memoria.Examples.EventSourcing.EntityFrameworkCore/Data/MyStoreDbContext.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities9.4 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. No known-vulnerable gem among the 5 declared gem(s) osv.dev was asked about. This repository commits no Gemfile.lock — which a published gem correctly does not — so osv-scanner had no resolved graph to read, and the question was put to osv.dev instead over the releases `bundle install` resolves this repository's 5 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over.

REDACTED

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).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 99 of the 231 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: CosmosDataStore.cs↔CosmosDomainService.cs 82%

Change coupling: CosmosDataStore.cs ↔ CosmosDomainService.cssrc/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs:1

What to do

Resolve the 1 Change coupling finding(s) in Change Coupling — start with CosmosDataStore.cs. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D39 · IL Efficiency9.9 / 10Exemplary✓ Tool-verified

Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

5 of 933 first-party methods have an oversized IL body.

IL efficiency: 5 authored method(s) exceed the IL budgetsrc/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/AppendRoutine/DcbAppendRoutine.cs:315

✓ On the Gold path — maintain.

Detailed fixes: d39_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious. No known-vulnerable gem among the 5 declared gem(s) osv.dev was asked about. This repository commits no Gemfile.lock — which a published gem correctly does not — so osv-scanner had no resolved graph to read, and the question was put to osv.dev instead over the releases `bundle install` resolves this repository's 5 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 44 platform declaration(s) and 5 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

Do you agree with this assessment?

AX10 · Code composition9.2 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

The namespaces Memoria.Commands ↔ Memoria.Validation depend on each other. The lightest dependency in the cycle is Memoria.Commands → Memoria.Validation (Memoria.Commands.CommandSender → Memoria.Validation.IValidationService, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Memoria/Commands/CommandSender.cs:6

What to do

Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.

Do you agree with this assessment?

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

AX6 · Interface segregation9.8 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

`IDcbDomainService` declares 21 members: `GetAggregate`, `GetEvents`, `GetEventsFromPosition`, `GetEventsUpToPosition`, `GetEventsBetweenPositions`, `GetEventsFromDate`, `GetEventsUpToDate`, `GetEventsBetweenDates`, `GetLatestPosition`, `GetInMemoryAggregate`, `GetInMemoryAggregate`, `GetInMemoryAggregate`, `GetInMemoryProjection`, `GetInMemoryProjection`, `GetInMemoryProjection`, `GetProjection`, `SaveProjection`, `SaveAggregate`, `SaveEvents`, `UpdateAggregate`, `UpdateProjection`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 21 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Memoria.EventSourcing.Dcb/IDcbDomainService.cs:21
`IDomainService` declares 21 members: `GetAggregate`, `GetEvents`, `GetEventsBetweenSequences`, `GetEventsFromSequence`, `GetEventsUpToSequence`, `GetEventsUpToDate`, `GetEventsFromDate`, `GetEventsBetweenDates`, `GetInMemoryAggregate`, `GetInMemoryAggregate`, `GetInMemoryAggregate`, `GetInMemoryProjection`, `GetInMemoryProjection`, `GetInMemoryProjection`, `GetProjection`, `SaveProjection`, `GetLatestEventSequence`, `SaveAggregate`, `SaveEvents`, `UpdateAggregate`, `UpdateProjection`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 21 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Memoria.EventSourcing/IDomainService.cs:6

What to do

Split fat interfaces into focused role-interfaces so clients depend only on what they use.

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

Do you agree with this assessment?

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

Do you agree with this assessment?

C1 · Data Protection3.0 / 10Weak✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

What to do

Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).

Do you agree with this assessment?

C3 · Audit Trail9.0 / 10Exemplary✓ Tool-verified

Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.

Method: Roslyn scan: audit-trail mechanism graded (SaveChanges interceptor/immutable AuditLog/[Audited] strong; bare IAuditable/AddAuditing weak). Deterministic.

An audit mechanism is present, but the trail is not yet complete — missing: a dedicated audit read-model (an audit-log/-trail/-entry projection) over the sensitive event streams.

What to do

Surface the who-changed-what trail: project the sensitive event streams into a dedicated audit read-model (an audit-log/-trail/-entry type) and make sure appended events carry the acting user.

Do you agree with this assessment?

ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).

Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.

Do you agree with this assessment?

ED2 · Event/command shape10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether commands have a single handler (one owner of the decision) and fan-out is modelled with events.

Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.

Do you agree with this assessment?

ED3 · Event naming10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).

Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.

Do you agree with this assessment?

ED4 · Outbox / dual-write10.0 / 10Exemplary○ Nothing flagged

Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.

Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.

Do you agree with this assessment?

ED5 · Idempotency10.0 / 10Exemplary◐ Sampled · advisory

Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.

Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.

Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:702

What to do

Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.

Do you agree with this assessment?

IC1 · Incompleteness & stubs8.9 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

`Dispose` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:702

What to do

Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.

Do you agree with this assessment?

M1 · Documentation (README)6.7 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

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 44 of 44 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

Do you agree with this assessment?

M4 · Documentation accuracy0.0 / 10Critical◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

README.md installs the package `Memoria` (`dotnet add package Memoria`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:46
README.md installs the package `Memoria.EventSourcing` (`dotnet add package Memoria.EventSourcing`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:52
README.md installs the package `Memoria.EventSourcing.Store.EntityFrameworkCore` (`dotnet add package Memoria.EventSourcing.Store.EntityFrameworkCore`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:53
benchmarks/README.md names `Store/StoreReadBenchmarks`, but no file or folder `Store/StoreReadBenchmarks` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — benchmarks/README.md:48
benchmarks/README.md names `Store/StoreWriteBenchmarks`, but no file or folder `Store/StoreWriteBenchmarks` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — benchmarks/README.md:48
benchmarks/README.md names `Store/ContentionBenchmark`, but no file or folder `Store/ContentionBenchmark` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — benchmarks/README.md:172
benchmarks/README.md names `Store/StreamedProviderBenchmarks`, but no file or folder `Store/StreamedProviderBenchmarks` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — benchmarks/README.md:295
docs/index.md installs the package `Memoria` (`dotnet add package Memoria`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/index.md:14
docs/getting-started/install.md installs the package `Memoria` (`dotnet add package Memoria`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/getting-started/install.md:20

What to do

Reconcile the README with reality: README.md installs the package `Memoria` (`dotnet add package Memoria`), but no project or props file references it; README.md installs the package `Memoria.EventSourcing` (`dotnet add package Memoria.EventSourcing`), but no project or props file references it; README.md installs the package `Memoria.EventSourcing.Store.EntityFrameworkCore` (`dotnet add package Memoria.EventSourcing.Store.EntityFrameworkCore`), but no project or props file references it; benchmarks/README.md names `Store/StoreReadBenchmarks`, but no file or folder `Store/StoreReadBenchmarks` exists; benchmarks/README.md names `Store/StoreWriteBenchmarks`, but no file or folder `Store/StoreWriteBenchmarks` exists.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

Do you agree with this assessment?

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

202/224 types (90%) 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.

Do you agree with this assessment?

P2 · Observability0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

No logging call was found in the 378 `.cs` file(s) this check read. Each was searched for the framework names `ILogger`, `Serilog`, `NLog` and `log4net`; for a call on a receiver whose name ends in `Logger`; for a `System.Diagnostics` write; for a level-gated log facade; and for the builder spellings that CONFIGURE logging for everyone else (`AddLogging(`, `ConfigureLogging(`, `UseSerilog(`, `UseNLog(`, `.Logging.Add…(`); and for emission through an `EventSource`, `ActivitySource` or `DiagnosticSource` (`WriteEvent(`, `StartActivity(`, `.Write("event", …)`). That walk sees only `.cs` documents from projects the workspace loaded, so it cannot see logging in source that did not load, in another language, or through a repo-local wrapper whose name does not end in `Logger` — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

Adopt ILogger (or Serilog) and log at meaningful points across the projects.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.

Do you agree with this assessment?

P3 · Security & performance tooling1.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

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 3078 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.

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.

Do you agree with this assessment?

P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

What to do

Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

Do you agree with this assessment?

P8 · Schema migrations3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

`EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely. (×6) — benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:133, benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:77, benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:78, …

What to do

Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly.

Do you agree with this assessment?

PF1 · Benchmark discipline9.5 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

Do you agree with this assessment?

PF2 · Allocation hygiene6.2 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

Raise allocation-aware density on the hot paths — currently 10 use(s) across 22,125 production line(s) (~0.5/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.

Do you agree with this assessment?

PF3 · Async & latency hygiene2.0 / 10Critical✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

14 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).
`.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). (×14) — benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:81, benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:79, benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:132, …
Only 0/310 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 IsSet(key)` 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/Memoria.Caching.Memory/MemoryCacheProvider.cs:39
`await Database.StringGetAsync(key)` 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/Memoria.Caching.Redis/RedisCacheProvider.cs:28
`await Database.StringSetAsync(key, json, TimeSpan.FromSeconds(cacheTimeInSeconds.Va...` 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/Memoria.Caching.Redis/RedisCacheProvider.cs:46
`await Database.KeyExistsAsync(key)` 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/Memoria.Caching.Redis/RedisCacheProvider.cs:56
`await Database.KeyDeleteAsync(key)` 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/Memoria.Caching.Redis/RedisCacheProvider.cs:67
`await database.ExecuteSqlRawAsync(routine.Definition, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/DcbAppendRoutineDatabaseExtensions.cs:40
`await Guarded("Get Events", query, () => dcbDbContext.GetEvents(query, eventTypeFil...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:35
`await Guarded("Get Events From Position", query, () => dcbDbContext.GetEventsFromPo...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:40
`await Guarded("Get Events Up To Position", query, () => dcbDbContext.GetEventsUpToP...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:46
`await Guarded("Get Events Between Positions", query, () => dcbDbContext.GetEventsBe...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:52
`await Guarded("Get Events From Date", query, () => dcbDbContext.GetEventsFromDate(q...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:59
`await Guarded("Get Events Up To Date", query, () => dcbDbContext.GetEventsUpToDate(...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:65
`await Guarded("Get Events Between Dates", query, () => dcbDbContext.GetEventsBetwee...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:71
`await Guarded("Get Latest Position", query, () => dcbDbContext.GetLatestPosition(qu...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:77
`await read()` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:156
`await context.Database.CreateExecutionStrategy().ExecuteAsync(async token => { if (...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:66
`await dcbDbContext.CallAppendRoutine(events, condition, affectedTags, snapshot, token)` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:70, src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:76
`await using … = await context.Database.BeginTransactionAsync(token)` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:73
`await context.Database.BeginTransactionAsync(token)` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:73
`await context.SaveChangesAsync(acceptAllChangesOnSuccess: false, token)` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:74
`await transaction.CommitAsync(token)` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:79
`await dcbDbContext.AppendFailure(exception, operation, condition, affectedTags, can...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:120
`await context.Database .SqlQueryRaw<AppendRoutineOutcome>( $"EXEC {DcbAppendRoutine...` 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/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:173

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.

Do you agree with this assessment?

X1 · Async correctness6.5 / 10Adequate✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

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. (×14) — benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:81, benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:79, benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:132, …

What to do

Sync-over-async (deadlock risk)

Do you agree with this assessment?

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X18 · Disposal-pattern correctness5.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

`StoreBenchmarkHarness` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_dcb` itself (line 44), which makes that instance its own. But `_dcb` is named in none of the methods the disposal search covered: `DisposeAsync` (line 149) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_dcb?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:44
`InMemoryCosmosDomainService` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_dataStore` itself (line 28), which makes that instance its own. But `_dataStore` is named in none of the methods the disposal search covered: `Dispose` (line 702) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_dataStore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:28
`domainDbContext` is never created by `EntityFrameworkCoreDomainService` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 346). Its declared type `IDomainDbContext` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Memoria.EventSourcing.Store.EntityFrameworkCore/EntityFrameworkCoreDomainService.cs:346
`_connection` is never created by `RabbitMqMessagingProvider` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 410). Its declared type `IConnection` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:410

What to do

Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.

Do you agree with this assessment?

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X2 · Cancellation propagation8.9 / 10Strong✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

Only 205/249 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. (×26) — benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:71, benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:124, benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:150, …
This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on. — examples/Memoria.Examples.Ecommerce.Dcb/Program.cs:72
Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. (×12) — examples/Memoria.Examples.EventSourcing.Cosmos/Program.cs:49, examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:85, examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:95, …

What to do

Thread a CancellationToken through async methods so work stops promptly on cancellation.

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X3 · Exception handling6.8 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

`catch (CosmosException) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:651
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:283

What to do

Swallowed exception (caught, then discarded)

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

Do you agree with this assessment?

X5 · Nullable reference types7.2 / 10Strong✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

~3.5 `!` suppressions per 1k syntax nodes — 270 suppression(s) across the 76836 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Do you agree with this assessment?

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

Lens	Score	Rating	Impact
Code Health	74%	Strong	Solid.
Architecture	96%	Exemplary	Solid.
Maturity	41%	Weak — gated by M2, M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	35%	Weak — gated by P2, P3, P8	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	61%	Adequate — gated by D36, C1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven	100%	Exemplary	Strongest area.
Performance	52%	Adequate — gated by PF3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.

Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 3 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data (event-sourced storage — lifecycle is stream archival / event TTL, not row CASCADE) — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 32 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — LLM evaluation failed
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) — 42 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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: `--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.
DM1 Domain Modelling — applicable but not scored (5 signals for this style, 3 needed — the count is met but a required primary signal is absent): 4 aggregate root(s) (entities that raise its domain events); 5 aggregate root(s) (AggregateRoot/IAggregateRoot); 4 value object(s); 15 domain event(s); a Domain/Aggregates/ValueObjects layer; 1 aggregate-constrained repository/repositories (IRepository<T> where T : IAggregateRoot); a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
ES1 Event Sourcing — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 4 aggregate(s) with Apply/When folds; 1 projection(s)
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
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.
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)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 11 finding(s)

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

AX3 · Project dependency cycles · Namespace dependency cycle · ×1

Namespace dependency cycle src/Memoria/Commands/CommandSender.cs:6 — The namespaces Memoria.Commands ↔ Memoria.Validation depend on each other. The lightest dependency in the cycle is Memoria.Commands → Memoria.Validation (Memoria.Commands.CommandSender → Memoria.Validation.IValidationService, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.

D17 · Explicit Debt · EmptyCatchBlock · ×1

EmptyCatchBlock src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:283 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · High CVE · ×1

REDACTED

Serious — 405 finding(s)

D17 · Explicit Debt · Dead code · ×142

Dead code: SupportsDcb benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:203 — Method SupportsDcb — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.Benchmarks, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ChangeProductDetailsCommandHandler examples/Memoria.Examples.Ecommerce.Dcb/Commands/ChangeProductDetailsCommand.cs:34 — NamedType ChangeProductDetailsCommandHandler — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.Examples.Ecommerce.Dcb, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CreateProductCommandHandler examples/Memoria.Examples.Ecommerce.Dcb/Commands/CreateProductCommand.cs:38 — NamedType CreateProductCommandHandler — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.Examples.Ecommerce.Dcb, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: DeleteProductCommandHandler examples/Memoria.Examples.Ecommerce.Dcb/Commands/DeleteProductCommand.cs:29 — NamedType DeleteProductCommandHandler — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.Examples.Ecommerce.Dcb, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetProductQueryHandler examples/Memoria.Examples.Ecommerce.Dcb/Queries/GetProductQuery.cs:17 — NamedType GetProductQueryHandler — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.Examples.Ecommerce.Dcb, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetProductsQueryHandler examples/Memoria.Examples.Ecommerce.Dcb/Queries/GetProductsQuery.cs:39 — NamedType GetProductsQueryHandler — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.Examples.Ecommerce.Dcb, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetOrderAggregateQueryHandler examples/Memoria.Examples.EventSourcing.Cosmos/Queries/Handlers/GetOrderAggregateQueryHandler.cs:9 — NamedType GetOrderAggregateQueryHandler — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.Examples.EventSourcing.Cosmos, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ChangeCourseCapacityCommandHandler examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Commands/ChangeCourseCapacityCommand.cs:29 — NamedType ChangeCourseCapacityCommandHandler — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetStudentTranscriptQueryHandler examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Queries/GetStudentTranscriptQuery.cs:35 — NamedType GetStudentTranscriptQueryHandler — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetOrderAggregateQueryHandler examples/Memoria.Examples.EventSourcing.EntityFrameworkCore/Queries/Handlers/GetOrderAggregateQueryHandler.cs:9 — NamedType GetOrderAggregateQueryHandler — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.Examples.EventSourcing.EntityFrameworkCore, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: TheInstallScriptProducesTheSchemaTheModelDeclares tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs:49 — Method TheInstallScriptProducesTheSchemaTheModelDeclares — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: TheInstallScriptIsIdempotent tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs:75 — Method TheInstallScriptIsIdempotent — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: TheScriptedTagColumnsAreCaseSensitive tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs:100 — Method TheScriptedTagColumnsAreCaseSensitive — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: TheInstallScriptProducesTheSchemaTheModelDeclares tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs:164 — Method TheInstallScriptProducesTheSchemaTheModelDeclares — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: TheInstallScriptIsIdempotent tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs:190 — Method TheInstallScriptIsIdempotent — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: TheScriptedTagColumnsAreByteOrdered tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DcbInstallScriptTests.cs:215 — Method TheScriptedTagColumnsAreByteOrdered — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GivenA150Database_ThenTheScriptDropsOnlyTheLinkTable tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DropAggregateEventsScriptTests.cs:27 — Method GivenA150Database_ThenTheScriptDropsOnlyTheLinkTable — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GivenTheTableIsAlreadyGone_ThenTheScriptIsStillSafeToRun tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DropAggregateEventsScriptTests.cs:57 — Method GivenTheTableIsAlreadyGone_ThenTheScriptIsStillSafeToRun — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GivenA150Database_ThenTheScriptDropsOnlyTheLinkTable tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DropAggregateEventsScriptTests.cs:85 — Method GivenA150Database_ThenTheScriptDropsOnlyTheLinkTable — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GivenTheTableIsAlreadyGone_ThenTheScriptIsStillSafeToRun tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/DropAggregateEventsScriptTests.cs:115 — Method GivenTheTableIsAlreadyGone_ThenTheScriptIsStillSafeToRun — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: A_postgresql_fixture_on_an_existing_server_drops_the_databases_it_handed_out tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/ExistingServerTests.cs:129 — Method A_postgresql_fixture_on_an_existing_server_drops_the_databases_it_handed_out — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: A_postgresql_fixture_leaves_databases_it_did_not_hand_out tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/ExistingServerTests.cs:150 — Method A_postgresql_fixture_leaves_databases_it_did_not_hand_out — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: A_sql_server_fixture_on_an_existing_server_drops_the_databases_it_handed_out tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/ExistingServerTests.cs:172 — Method A_sql_server_fixture_on_an_existing_server_drops_the_databases_it_handed_out — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: A_sql_server_fixture_leaves_databases_it_did_not_hand_out tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/ExistingServerTests.cs:193 — Method A_sql_server_fixture_leaves_databases_it_did_not_hand_out — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: A_migration_installs_the_routine_for_the_default_model tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/PostgreSqlAppendRoutineInstallTests.cs:98 — Method A_migration_installs_the_routine_for_the_default_model — Roslyn's SymbolFinder walked every project the solution loads, including Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
+ 117 more in this group — see findings.md.

D23 · Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) · ×30

Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:31 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.GetAggregateDocument — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:43 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.GetEventDocuments — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:59 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.GetEventDocumentsBetweenSequences — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:78 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.GetEventDocumentsFromSequence — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:96 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.GetEventDocumentsUpToSequence — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:114 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.GetEventDocumentsUpToDate — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:132 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.GetEventDocumentsFromDate — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:150 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.GetEventDocumentsBetweenDates — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:198 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.UpdateAggregateDocument — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:248 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.GetProjectionDocument — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:259 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDataStore.UpdateProjectionDocument — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:30 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetAggregate — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:117 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetEvents — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:129 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetEventsBetweenSequences — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:143 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetEventsFromSequence — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:157 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetEventsUpToSequence — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:171 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetEventsUpToDate — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:185 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetEventsFromDate — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:199 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetEventsBetweenDates — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:214 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetInMemoryAggregate — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:293 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetInMemoryProjection — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:386 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetProjection — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:463 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.SaveProjection — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:494 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetLatestEventSequence — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:515 — IStreamId (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.SaveAggregate — couples the contexts.
+ 5 more in this group — see findings.md.

X2 · Cancellation propagation · Async method without CancellationToken · ×26

Async method without CancellationToken: Run benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:71 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RunCase benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:124 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Measure benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:150 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Seed benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:278 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DescribeServer benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:328 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Run benchmarks/Memoria.Benchmarks/Store/RoundTripReport.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveStreamed benchmarks/Memoria.Benchmarks/Store/RoundTripReport.cs:72 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveDcb benchmarks/Memoria.Benchmarks/Store/RoundTripReport.cs:81 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PrintCommands benchmarks/Memoria.Benchmarks/Store/RoundTripReport.cs:122 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Seed benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:111 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: WriteSnapshots benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:140 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateStatistics benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:194 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetEventsStreamed benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:57 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetEventsDcb benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:61 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAggregateSnapshotStreamed benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:69 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAggregateSnapshotDcb benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:74 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAggregateFoldedStreamed benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:83 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAggregateFoldedDcb benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:88 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveAggregateStreamed benchmarks/Memoria.Benchmarks/Store/StoreWriteBenchmarks.cs:69 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveAggregateDcb benchmarks/Memoria.Benchmarks/Store/StoreWriteBenchmarks.cs:84 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetEvents benchmarks/Memoria.Benchmarks/Store/StreamedProviderBenchmarks.cs:68 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAggregateSnapshot benchmarks/Memoria.Benchmarks/Store/StreamedProviderBenchmarks.cs:72 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAggregateFolded benchmarks/Memoria.Benchmarks/Store/StreamedProviderBenchmarks.cs:77 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveAggregate benchmarks/Memoria.Benchmarks/Store/StreamedProviderBenchmarks.cs:82 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Set src/Memoria.Caching.Memory/MemoryCacheProvider.cs:32 — No CancellationToken parameter — this work can't be stopped early once started.
+ 1 more in this group — see findings.md.

PF3 · Async & latency hygiene · Awaits without ConfigureAwait(false) · ×25

Awaits without ConfigureAwait(false) — Only 0/310 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.
Awaits without ConfigureAwait(false) src/Memoria.Caching.Memory/MemoryCacheProvider.cs:39 — `await IsSet(key)` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.Caching.Redis/RedisCacheProvider.cs:28 — `await Database.StringGetAsync(key)` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.Caching.Redis/RedisCacheProvider.cs:46 — `await Database.StringSetAsync(key, json, TimeSpan.FromSeconds(cacheTimeInSeconds.Va...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.Caching.Redis/RedisCacheProvider.cs:56 — `await Database.KeyExistsAsync(key)` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.Caching.Redis/RedisCacheProvider.cs:67 — `await Database.KeyDeleteAsync(key)` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/DcbAppendRoutineDatabaseExtensions.cs:40 — `await database.ExecuteSqlRawAsync(routine.Definition, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:35 — `await Guarded("Get Events", query, () => dcbDbContext.GetEvents(query, eventTypeFil...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:40 — `await Guarded("Get Events From Position", query, () => dcbDbContext.GetEventsFromPo...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:46 — `await Guarded("Get Events Up To Position", query, () => dcbDbContext.GetEventsUpToP...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:52 — `await Guarded("Get Events Between Positions", query, () => dcbDbContext.GetEventsBe...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:59 — `await Guarded("Get Events From Date", query, () => dcbDbContext.GetEventsFromDate(q...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:65 — `await Guarded("Get Events Up To Date", query, () => dcbDbContext.GetEventsUpToDate(...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:71 — `await Guarded("Get Events Between Dates", query, () => dcbDbContext.GetEventsBetwee...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:77 — `await Guarded("Get Latest Position", query, () => dcbDbContext.GetLatestPosition(qu...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:156 — `await read()` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:66 — `await context.Database.CreateExecutionStrategy().ExecuteAsync(async token => { if (...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:70 — `await dcbDbContext.CallAppendRoutine(events, condition, affectedTags, snapshot, token)` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:73 — `await using … = await context.Database.BeginTransactionAsync(token)` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:73 — `await context.Database.BeginTransactionAsync(token)` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:74 — `await context.SaveChangesAsync(acceptAllChangesOnSuccess: false, token)` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:76 — `await dcbDbContext.CallAppendRoutine(events, condition, affectedTags, snapshot, token)` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:79 — `await transaction.CommitAsync(token)` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:120 — `await dcbDbContext.AppendFailure(exception, operation, condition, affectedTags, can...` 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)`.
Awaits without ConfigureAwait(false) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/AppendThroughRoutine.cs:173 — `await context.Database .SqlQueryRaw<AppendRoutineOutcome>( $"EXEC {DcbAppendRoutine...` 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)`.

D12 · Dependency Hygiene · Deprecated · ×19

Deprecated: xunit tests/Memoria.Caching.Memory.Tests/Memoria.Caching.Memory.Tests.csproj:11 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.Caching.Redis.Tests/Memoria.Caching.Redis.Tests.csproj:11 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Relational.Tests/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Relational.Tests.csproj:21 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Tests/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Tests.csproj:20 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Dcb.Tests/Memoria.EventSourcing.Dcb.Tests.csproj:13 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Store.Cosmos.InMemory.Tests/Memoria.EventSourcing.Store.Cosmos.InMemory.Tests.csproj:15 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Store.Cosmos.Tests/Memoria.EventSourcing.Store.Cosmos.Tests.csproj:15 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Containers.Tests.csproj:18 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Npgsql.Tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Npgsql.Tests.csproj:13 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Relational.Tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Relational.Tests.csproj:19 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Tests/Memoria.EventSourcing.Store.EntityFrameworkCore.Tests.csproj:20 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Store.Tests/Memoria.EventSourcing.Store.Tests.csproj:19 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.EventSourcing.Tests/Memoria.EventSourcing.Tests.csproj:13 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.Messaging.RabbitMq.InMemory.Tests/Memoria.Messaging.RabbitMq.InMemory.Tests.csproj:15 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.Messaging.RabbitMq.Tests/Memoria.Messaging.RabbitMq.Tests.csproj:15 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.Messaging.ServiceBus.InMemory.Tests/Memoria.Messaging.ServiceBus.InMemory.Tests.csproj:15 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.Messaging.ServiceBus.Tests/Memoria.Messaging.ServiceBus.Tests.csproj:17 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.Tests/Memoria.Tests.csproj:13 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit tests/Memoria.Validation.FluentValidation.Tests/Memoria.Validation.FluentValidation.Tests.csproj:13 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×15

Sync-over-async blocking — 14 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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:81 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:79 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:132 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:183 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:49 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:50 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:54 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreWriteBenchmarks.cs:56 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreWriteBenchmarks.cs:57 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreWriteBenchmarks.cs:61 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StoreWriteBenchmarks.cs:66 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StreamedProviderBenchmarks.cs:57 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StreamedProviderBenchmarks.cs:58 — `.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).
Sync-over-async blocking benchmarks/Memoria.Benchmarks/Store/StreamedProviderBenchmarks.cs:65 — `.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).

X1 · Async correctness · Sync-over-async (deadlock risk) · ×14

Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:81 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:79 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:132 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreEngine.cs:182 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:49 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:50 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreReadBenchmarks.cs:54 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreWriteBenchmarks.cs:56 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreWriteBenchmarks.cs:57 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreWriteBenchmarks.cs:60 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StoreWriteBenchmarks.cs:66 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StreamedProviderBenchmarks.cs:57 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StreamedProviderBenchmarks.cs:58 — 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.
Sync-over-async (deadlock risk) benchmarks/Memoria.Benchmarks/Store/StreamedProviderBenchmarks.cs:65 — 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.

X2 · Cancellation propagation · Async local function without CancellationToken · ×12

Async local function without CancellationToken: CreateDatabase examples/Memoria.Examples.EventSourcing.Cosmos/Program.cs:49 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: Subscribe examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:85 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: ShowStaleDecisionRefused examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:95 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: ChangeCapacity examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:116 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: ShowSnapshot examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:127 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: ShowCapacityChangeRefusedBySubscription examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:139 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: ShowIntersectionBoundary examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:163 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: ShowTranscript examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:189 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: ShowStaleSnapshot examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:205 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: Seed examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:225 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: CreateDatabase examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:265 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: CreateDatabase examples/Memoria.Examples.EventSourcing.EntityFrameworkCore/Program.cs:62 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.

D19 · Documentation Quality · Low XML-doc coverage · ×10

Low XML-doc coverage: Memoria.Benchmarks REDACTED — Memoria.Benchmarks: 36 % XML-doc coverage (38/107).
Low XML-doc coverage: Memoria.Examples.Caching.Memory examples/Memoria.Examples.Caching.Memory/Memoria.Examples.Caching.Memory.csproj — Memoria.Examples.Caching.Memory: 0 % XML-doc coverage (0/3).
Low XML-doc coverage: Memoria.Examples.Caching.Redis examples/Memoria.Examples.Caching.Redis/Memoria.Examples.Caching.Redis.csproj — Memoria.Examples.Caching.Redis: 0 % XML-doc coverage (0/3).
Low XML-doc coverage: Memoria.Examples.EventSourcing.Cosmos examples/Memoria.Examples.EventSourcing.Cosmos/Memoria.Examples.EventSourcing.Cosmos.csproj — Memoria.Examples.EventSourcing.Cosmos: 0 % XML-doc coverage (0/18).
Low XML-doc coverage: Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore.csproj — Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore: 34 % XML-doc coverage (24/71).
Low XML-doc coverage: Memoria.Examples.EventSourcing.EntityFrameworkCore examples/Memoria.Examples.EventSourcing.EntityFrameworkCore/Memoria.Examples.EventSourcing.EntityFrameworkCore.csproj — Memoria.Examples.EventSourcing.EntityFrameworkCore: 0 % XML-doc coverage (0/19).
Low XML-doc coverage: Memoria.Examples.Messaging.RabbitMq examples/Memoria.Examples.Messaging.RabbitMq/Memoria.Examples.Messaging.RabbitMq.csproj — Memoria.Examples.Messaging.RabbitMq: 0 % XML-doc coverage (0/7).
Low XML-doc coverage: Memoria.Examples.Messaging.ServiceBus examples/Memoria.Examples.Messaging.ServiceBus/Memoria.Examples.Messaging.ServiceBus.csproj — Memoria.Examples.Messaging.ServiceBus: 0 % XML-doc coverage (0/7).
Low XML-doc coverage: Memoria.EventSourcing.Store.Cosmos.InMemory src/Memoria.EventSourcing.Store.Cosmos.InMemory/Memoria.EventSourcing.Store.Cosmos.InMemory.csproj — Memoria.EventSourcing.Store.Cosmos.InMemory: 13 % XML-doc coverage (6/47).
Low XML-doc coverage: Memoria.EventSourcing.Store.EntityFrameworkCore.Identity src/Memoria.EventSourcing.Store.EntityFrameworkCore.Identity/Memoria.EventSourcing.Store.EntityFrameworkCore.Identity.csproj — Memoria.EventSourcing.Store.EntityFrameworkCore.Identity: 14 % XML-doc coverage (1/7).

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×10

Duplicated block (12 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:631 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:631-642 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:851-862 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) src/Memoria.EventSourcing.Store.Cosmos/Documents/AggregateDocument.cs:131 — src/Memoria.EventSourcing.Store.Cosmos/Documents/AggregateDocument.cs:131-142 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Entities/AggregateEntity.cs:96-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos/Documents/AggregateDocument.cs:131` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (12 lines × 2) src/Memoria.EventSourcing.Store.Cosmos/Extensions/ProjectionExtensions.cs:65 — src/Memoria.EventSourcing.Store.Cosmos/Extensions/ProjectionExtensions.cs:65-76 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/ProjectionExtensions.cs:65-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos/Extensions/ProjectionExtensions.cs:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (12 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:62 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:62-73 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:419-430 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:58 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:58-69 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:217-228 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:296 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:296-307 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:415-426 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:296` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:82 — src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:82-93 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:561-572 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:409 — src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:409-420 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:557-568 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:409` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:206 — src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:206-217 | src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:336-348 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:206` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:78 — src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:78-90 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:303-314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×6

Duplicated block (9 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:613 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:613-621 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:666-674 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:613` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/IDomainDbContextExtensions.cs:16 — src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/IDomainDbContextExtensions.cs:16-24 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/IDomainDbContextExtensions.cs:63-71 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:573 — src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:573-581 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetProjection.cs:65-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs:407 — src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs:407-416 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/IDomainDbContextExtensions.cs:71-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetAggregate.cs:60 — src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetAggregate.cs:60-68 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/IDomainDbContextExtensions.cs:21-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetAggregate.cs:60` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) src/Memoria.EventSourcing.Dcb/DcbStoreFailures.cs:89 — src/Memoria.EventSourcing.Dcb/DcbStoreFailures.cs:89-97 | src/Memoria.EventSourcing/StoreFailures.cs:105-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

P8 · Schema migrations · Schema created with EnsureCreated() (no migration path) · ×6

Schema created with EnsureCreated() (no migration path) benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:133 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:77 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:78 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) examples/Memoria.Examples.Ecommerce.Dcb/Program.cs:45 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Program.cs:271 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) examples/Memoria.Examples.EventSourcing.EntityFrameworkCore/Program.cs:92 — `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.

D23 · Boundary Type-Coupling · Cross-context type ReadMode (Memoria.EventSourcing → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore) · ×4

Cross-context type ReadMode (Memoria.EventSourcing → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:28 — ReadMode (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore's public surface via EntityFrameworkCoreDcbDomainService.GetAggregate — couples the contexts.
Cross-context type ReadMode (Memoria.EventSourcing → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/EntityFrameworkCoreDcbDomainService.cs:114 — ReadMode (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore's public surface via EntityFrameworkCoreDcbDomainService.GetProjection — couples the contexts.
Cross-context type ReadMode (Memoria.EventSourcing → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:99 — ReadMode (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore's public surface via DcbDbContextExtensions.GetAggregate — couples the contexts.
Cross-context type ReadMode (Memoria.EventSourcing → Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:235 — ReadMode (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore's public surface via DcbDbContextExtensions.GetProjection — couples the contexts.

D4 · Code Duplication · Duplicated block (17 lines × 2) · ×4

Duplicated block (17 lines × 2) src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:22 — src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:22-38 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs:22-38 — before extracting anything, compare `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs` and `src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:55 — src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:55-71 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs:55-71 — before extracting anything, compare `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs` and `src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) src/Memoria.Messaging.ServiceBus/ServiceBusMessagingProvider.cs:34 — src/Memoria.Messaging.ServiceBus/ServiceBusMessagingProvider.cs:34-50 | src/Memoria.Messaging.ServiceBus/ServiceBusMessagingProvider.cs:69-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.Messaging.ServiceBus/ServiceBusMessagingProvider.cs:34` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision.cs:77 — examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision.cs:77-93 | examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision2.cs:77-93 — before extracting anything, compare `examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision.cs` and `examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision2.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×4

Duplicated block (10 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:62 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:62-71 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:82-91 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:419 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:419-428 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:561-570 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:281 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:281-290 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:431-440 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:119 — src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:119-128 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs:119-128 — before extracting anything, compare `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs` and `src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:119` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (19 lines × 2) · ×3

Duplicated block (19 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:205 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:205-223 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs:292-310 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:205` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetAggregate.cs:45 — src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetAggregate.cs:45-63 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetProjection.cs:46-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetAggregate.cs:45` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:113 — src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:113-131 | src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:199-217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:113` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×3

Duplicated block (11 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:523 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:523-533 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:631-641 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:523` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:35 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:35-45 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:55-65 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:392 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:392-402 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:534-544 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:392` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3

Duplicated block (7 lines × 2) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:193 — src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:193-199 | src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:323-329 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:81 — src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:81-87 | src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:165-171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:94 — src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:94-100 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetAggregate.cs:64-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D23 · Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → examples) · ×2

Cross-context type IStreamId (Memoria.EventSourcing → examples) examples/Memoria.Examples.EventSourcing.Cosmos/Streams/CustomerStreamId.cs:5 — IStreamId (context Memoria.EventSourcing) is exposed in examples's public surface via CustomerStreamId.IStreamId — couples the contexts.
Cross-context type IStreamId (Memoria.EventSourcing → examples) examples/Memoria.Examples.EventSourcing.EntityFrameworkCore/Streams/CustomerStreamId.cs:5 — IStreamId (context Memoria.EventSourcing) is exposed in examples's public surface via CustomerStreamId.IStreamId — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type ReadMode (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) · ×2

Cross-context type ReadMode (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:31 — ReadMode (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetAggregate — couples the contexts.
Cross-context type ReadMode (Memoria.EventSourcing → Memoria.EventSourcing.Store.Cosmos.InMemory) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:387 — ReadMode (context Memoria.EventSourcing) is exposed in Memoria.EventSourcing.Store.Cosmos.InMemory's public surface via InMemoryCosmosDomainService.GetProjection — couples the contexts.

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2

Members sharing a duplicated core (4 members, 50+ identical tokens) src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:21 — src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:21-44 | src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:54-77 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs:21-44 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs:54-77 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:34 — src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:34-54 | src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:60-81 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs:34-54 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs:60-81 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Duplicated block (34 lines × 2) · ×2

Duplicated block (34 lines × 2) src/Memoria.EventSourcing.Store.EntityFrameworkCore/Entities/AggregateEntity.cs:28 — src/Memoria.EventSourcing.Store.EntityFrameworkCore/Entities/AggregateEntity.cs:28-61 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Entities/ProjectionEntity.cs:25-58 — before extracting anything, compare `src/Memoria.EventSourcing.Store.EntityFrameworkCore/Entities/AggregateEntity.cs` and `src/Memoria.EventSourcing.Store.EntityFrameworkCore/Entities/ProjectionEntity.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (34 lines × 2) examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision.cs:97 — examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision.cs:97-130 | examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision2.cs:97-130 — before extracting anything, compare `examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision.cs` and `examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision2.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (24–25 lines × 3) · ×2

Duplicated block (24–25 lines × 3) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:298 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:298-322 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:330-353 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:361-384 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:298` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24–25 lines × 3) src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:411 — src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:411-435 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:453-476 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:494-517 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:411` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (20 lines × 2) · ×2

Duplicated block (20 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:263 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:263-282 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs:389-408 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (20 lines × 2) src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:35 — src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:35-54 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs:35-54 — before extracting anything, compare `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs` and `src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (18 lines × 3) · ×2

Duplicated block (18 lines × 3) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:221 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:221-238 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:247-264 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:274-291 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:221` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 3) src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:306 — src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:306-323 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:341-358 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:378-395 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:306` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2

Duplicated block (15 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:523 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:523-537 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:749-763 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision.cs:30 — examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision.cs:30-44 | examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision2.cs:30-44 — before extracting anything, compare `examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision.cs` and `examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Domain/SubscriptionDecision2.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2

Duplicated block (14 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:246 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:246-259 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:340-353 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:246` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:273 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:273-286 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:377-390 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:273` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

X18 · Disposal-pattern correctness · Owned disposable field is never released · ×2

Owned disposable field is never released benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs:44 — `StoreBenchmarkHarness` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_dcb` itself (line 44), which makes that instance its own. But `_dcb` is named in none of the methods the disposal search covered: `DisposeAsync` (line 149) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_dcb?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:28 — `InMemoryCosmosDomainService` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_dataStore` itself (line 28), which makes that instance its own. But `_dataStore` is named in none of the methods the disposal search covered: `Dispose` (line 702) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_dataStore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.

X18 · Disposal-pattern correctness · Disposes a dependency it does not own · ×2

Disposes a dependency it does not own src/Memoria.EventSourcing.Store.EntityFrameworkCore/EntityFrameworkCoreDomainService.cs:346 — `domainDbContext` is never created by `EntityFrameworkCoreDomainService` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 346). Its declared type `IDomainDbContext` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:410 — `_connection` is never created by `RabbitMqMessagingProvider` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 410). Its declared type `IConnection` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.

C1 · Data Protection · No data-protection/encryption · ×1

No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

D2 · Cognitive Complexity · ContentionBenchmark.Measure (cognitive 21) · ×1

ContentionBenchmark.Measure (cognitive 21) benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs:150 — ContentionBenchmark.Measure has cognitive complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 170, 155). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · ServiceCollectionExtensions.AddMemoriaEventSourcing (cognitive 19) · ×1

ServiceCollectionExtensions.AddMemoriaEventSourcing (cognitive 19) src/Memoria.EventSourcing/Extensions/ServiceCollectionExtensions.cs:19 — ServiceCollectionExtensions.AddMemoriaEventSourcing has cognitive complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InMemoryCosmosDomainService.SaveAggregate (cognitive 18) · ×1

InMemoryCosmosDomainService.SaveAggregate (cognitive 18) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:515 — InMemoryCosmosDomainService.SaveAggregate has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ServiceCollectionExtensions.RegisterHandlers (cognitive 18) · ×1

ServiceCollectionExtensions.RegisterHandlers (cognitive 18) src/Memoria/Extensions/ServiceCollectionExtensions.cs:48 — ServiceCollectionExtensions.RegisterHandlers has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D23 · Boundary Type-Coupling · Cross-context type IStreamId (Memoria.EventSourcing → benchmarks) · ×1

Cross-context type IStreamId (Memoria.EventSourcing → benchmarks) benchmarks/Memoria.Benchmarks/Store/StoreModels.cs:71 — IStreamId (context Memoria.EventSourcing) is exposed in benchmarks's public surface via ShowStreamId.IStreamId — couples the contexts.

D3 · God Classes · ClassTooLong · ×1

ClassTooLong: CosmosDomainService src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs — ClassTooLong — 427 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 27 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D35 · Change Coupling · Change coupling · ×1

Change coupling: CosmosDataStore.cs ↔ CosmosDomainService.cs src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs:1 — `src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `748f42cb` Use ReadMode and add in memory Projections (#191); `12b4307b` Refactor query logic in CosmosDomainService by introducing reusable `…; `bba742bb` Get aggregate with apply new events false returns now null if the agg… (at that commit the files were still `src/OpenCqrs.EventSourcing.Store.Cosmos/CosmosDataStore.cs` and `src/OpenCqrs.EventSourcing.Store.Cosmos/CosmosDomainService.cs`) — run `git show` on any of them.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Members sharing a duplicated core (16 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (16 members, 50+ identical tokens) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:33 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:33-115 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:216-238 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:242-264 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:268-291 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:295-322 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:326-353 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:357-384 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:389-461 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:52-120 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:302-323 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:336-358 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:372-395 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:408-435 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:449-476 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:490-517 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:531-613 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.

D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (6 members, 50+ identical tokens) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:65 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:65-75 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:83-93 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:101-111 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:119-129 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:137-147 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:156-166 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.

D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (5 members, 50+ identical tokens) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:517 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:517-621 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:625-674 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:733-825 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:837-890 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/TrackAggregate.cs:31-61 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.

D4 · Code Duplication · Duplicated block (72–74 lines × 2) · ×1

Duplicated block (72–74 lines × 2) src/Memoria/Commands/ICommandSender.cs:19 — src/Memoria/Commands/ICommandSender.cs:19-92 | src/Memoria/IDispatcher.cs:18-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria/Commands/ICommandSender.cs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (49–62 lines × 2) · ×1

Duplicated block (49–62 lines × 2) src/Memoria.EventSourcing.Store.Cosmos/Documents/AggregateDocument.cs:41 — src/Memoria.EventSourcing.Store.Cosmos/Documents/AggregateDocument.cs:41-102 | src/Memoria.EventSourcing.Store.Cosmos/Documents/ProjectionDocument.cs:36-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1

Duplicated block (26 lines × 2) src/Memoria.EventSourcing.Store.EntityFrameworkCore/Configurations/AggregateEntityConfiguration.cs:15 — src/Memoria.EventSourcing.Store.EntityFrameworkCore/Configurations/AggregateEntityConfiguration.cs:15-40 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Configurations/ProjectionEntityConfiguration.cs:15-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.EntityFrameworkCore/Configurations/AggregateEntityConfiguration.cs:15` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<AggregateEntity>` in one and `EntityTypeBuilder<ProjectionEntity>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (23–28 lines × 2) · ×1

Duplicated block (23–28 lines × 2) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:122 — src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:122-149 | src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:258-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:122` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (25–26 lines × 2) · ×1

Duplicated block (25–26 lines × 2) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:150 — src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:150-175 | src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:281-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Extensions/DbContextExtensions/Snapshots.cs:150` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (21–25 lines × 2) · ×1

Duplicated block (21–25 lines × 2) src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Interceptors/AuditInterceptor.cs:41 — src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Interceptors/AuditInterceptor.cs:41-65 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Interceptors/AuditInterceptor.cs:30-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Interceptors/AuditInterceptor.cs:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1

Duplicated block (24 lines × 2) src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:81 — src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:81-104 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs:81-104 — before extracting anything, compare `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs` and `src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1

Duplicated block (21 lines × 2) src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:61 — src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:61-81 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs:61-81 — before extracting anything, compare `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs` and `src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1

Duplicated block (17 lines × 3) src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetInMemoryProjection.cs:37 — src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetInMemoryProjection.cs:37-53 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetInMemoryProjection.cs:84-100 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetInMemoryProjection.cs:131-147 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetInMemoryProjection.cs:37` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1

Duplicated block (15 lines × 4) src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:30 — src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:30-44 | src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:63-77 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs:30-44 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs:63-77 — before extracting anything, compare `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs` and `src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusMessagingProvider.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqMessagingProvider.cs:30` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1

Duplicated block (16 lines × 4) src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:39 — src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:39-54 | src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:66-81 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs:39-54 | src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs:66-81 — before extracting anything, compare `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs` and `src/Memoria.Messaging.ServiceBus.InMemory/InMemoryServiceBusStorage.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:39` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:64` calls `Where`, `Equals` and `src/Memoria.Messaging.RabbitMq.InMemory/InMemoryRabbitMqStorage.cs:37` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (13 lines × 6) · ×1

Duplicated block (13 lines × 6) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:221 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:221-233 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:247-259 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:274-286 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:306-318 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:341-353 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:378-390 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13–15 lines × 4) · ×1

Duplicated block (13–15 lines × 4) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:209 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:209-221 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:268-282 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs:296-308 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs:394-408 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:268` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1

Duplicated block (12 lines × 4) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:523 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:523-534 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:631-642 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:749-760 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:851-862 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1

Duplicated block (13 lines × 2) src/Memoria.Validation.FluentValidation/Extensions/ServiceCollectionExtensions.cs:30 — src/Memoria.Validation.FluentValidation/Extensions/ServiceCollectionExtensions.cs:30-42 | src/Memoria/Extensions/ServiceCollectionExtensions.cs:50-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.Validation.FluentValidation/Extensions/ServiceCollectionExtensions.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1

Duplicated block (10 lines × 6) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:300 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:300-309 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:331-340 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:362-371 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:413-422 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:454-463 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:495-504 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1

Duplicated block (12 lines × 3) src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetInMemoryAggregate.cs:39 — src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetInMemoryAggregate.cs:39-50 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetInMemoryAggregate.cs:80-91 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetInMemoryAggregate.cs:122-133 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/GetInMemoryAggregate.cs:39` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1

Duplicated block (8 lines × 3) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:530 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:530-537 | src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:756-763 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/TrackAggregate.cs:42-49 — before extracting anything, compare `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs` and `src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1

Duplicated block (8 lines × 2) src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs:308 — src/Memoria.EventSourcing.Store.Cosmos/CosmosDataStore.cs:308-315 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/Extensions/DbContextExtensions/IDomainDbContextExtensions.cs:25-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.

D4 · Code Duplication · Duplicated block (7 lines × 6) · ×1

Duplicated block (7 lines × 6) src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:69 — src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:69-75 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:87-93 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:105-111 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:123-129 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:141-147 | src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:160-166 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDataStore.cs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1

Duplicated block (6 lines × 2) src/Memoria.EventSourcing.Store.EntityFrameworkCore.Identity/IdentityDomainDbContext.cs:27 — src/Memoria.EventSourcing.Store.EntityFrameworkCore.Identity/IdentityDomainDbContext.cs:27-32 | src/Memoria.EventSourcing.Store.EntityFrameworkCore/DomainDbContext.cs:196-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×1

Duplicated block (18–20 lines × 2) examples/Memoria.Examples.Ecommerce.Dcb/Commands/ChangeProductDetailsCommand.cs:42 — examples/Memoria.Examples.Ecommerce.Dcb/Commands/ChangeProductDetailsCommand.cs:42-59 | examples/Memoria.Examples.Ecommerce.Dcb/Commands/DeleteProductCommand.cs:34-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/Memoria.Examples.Ecommerce.Dcb/Commands/ChangeProductDetailsCommand.cs:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `ChangeProductDetailsCommand` in one and `DeleteProductCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (15–20 lines × 2) · ×1

Duplicated block (15–20 lines × 2) examples/Memoria.Examples.Ecommerce.Dcb/Commands/ChangeProductDetailsCommand.cs:50 — examples/Memoria.Examples.Ecommerce.Dcb/Commands/ChangeProductDetailsCommand.cs:50-64 | examples/Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore/Commands/ChangeCourseCapacityCommand.cs:35-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `ChangeProductDetailsCommand` in one and `ChangeCourseCapacityCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1

Duplicated block (18–19 lines × 2) examples/Memoria.Examples.Ecommerce.Dcb/Commands/CreateProductCommand.cs:60 — examples/Memoria.Examples.Ecommerce.Dcb/Commands/CreateProductCommand.cs:60-78 | examples/Memoria.Examples.Ecommerce.Dcb/Commands/DeleteProductCommand.cs:44-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `CreateProductCommand` in one and `DeleteProductCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: Memoria.EventSourcing.Store.EntityFrameworkCore.Identity src/Memoria.EventSourcing.Store.EntityFrameworkCore.Identity/Memoria.EventSourcing.Store.EntityFrameworkCore.Identity.csproj:1 — Memoria.EventSourcing.Store.EntityFrameworkCore.Identity: abstractness 1.00, instability 1.00, distance 1.00 — zone of uselessness — abstract and unstable, so it's likely unused.

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — no coverage collector is wired up — 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.

GD1 · Unfinished & placeholder code · Unfinished stub · ×1

Unfinished stub — throws NotImplementedException src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:702 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.

IC1 · Incompleteness & stubs · Unfinished stub · ×1

Unfinished stub — throws NotImplementedException src/Memoria.EventSourcing.Store.Cosmos.InMemory/InMemoryCosmosDomainService.cs:702 — `Dispose` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.

P12 · CI test-gate honesty · CI test gate excludes suites by filter · ×1

CI test gate excludes suites by filter REDACTED:30 — `dotnet test --configuration Release --no-build --verbosity normal --filter "Category!=Container&Category!=Emulator"` filters with `Category!=Container&Category!=Emulator` — 27 test(s) it drops — run by no other gate before merge (categories Emulator; e.g. BatchLimitTests.GivenExactlyTheMaximumEvents_WhenSaved_ThenTheySucceed, BatchLimitTests.GivenMoreThanTheMaximumEvents_WhenSaved_ThenTheLimitIsReportedAndNothingIsWritten). Run what it drops in another job before merge (a complementary filter), or remove the filter.

P2 · Observability · No structured logging · ×1

No structured logging — No logging call was found in the 378 `.cs` file(s) this check read. Each was searched for the framework names `ILogger`, `Serilog`, `NLog` and `log4net`; for a call on a receiver whose name ends in `Logger`; for a `System.Diagnostics` write; for a level-gated log facade; and for the builder spellings that CONFIGURE logging for everyone else (`AddLogging(`, `ConfigureLogging(`, `UseSerilog(`, `UseNLog(`, `.Logging.Add…(`); and for emission through an `EventSource`, `ActivitySource` or `DiagnosticSource` (`WriteEvent(`, `StartActivity(`, `.Write("event", …)`). That walk sees only `.cs` documents from projects the workspace loaded, so it cannot see logging in source that did not load, in another language, or through a repo-local wrapper whose name does not end in `Logger` — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1

NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.

X2 · Cancellation propagation · Async endpoint handler without CancellationToken · ×1

Async endpoint handler without CancellationToken: /admin/products/delete examples/Memoria.Examples.Ecommerce.Dcb/Program.cs:72 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1

Swallowed exception (caught, then discarded) src/Memoria.EventSourcing.Store.Cosmos/CosmosDomainService.cs:651 — `catch (CosmosException) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.

X3 · Exception handling · Swallowed exception (empty catch) · ×1

Swallowed exception (empty catch) src/Memoria.Messaging.RabbitMq/RabbitMqMessagingProvider.cs:283 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.

Minor — 25 finding(s)

M4 · Documentation accuracy · README/code drift · ×9

README/code drift README.md:46 — README.md installs the package `Memoria` (`dotnet add package Memoria`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:52 — README.md installs the package `Memoria.EventSourcing` (`dotnet add package Memoria.EventSourcing`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:53 — README.md installs the package `Memoria.EventSourcing.Store.EntityFrameworkCore` (`dotnet add package Memoria.EventSourcing.Store.EntityFrameworkCore`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift benchmarks/README.md:48 — benchmarks/README.md names `Store/StoreReadBenchmarks`, but no file or folder `Store/StoreReadBenchmarks` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift benchmarks/README.md:48 — benchmarks/README.md names `Store/StoreWriteBenchmarks`, but no file or folder `Store/StoreWriteBenchmarks` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift benchmarks/README.md:172 — benchmarks/README.md names `Store/ContentionBenchmark`, but no file or folder `Store/ContentionBenchmark` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift benchmarks/README.md:295 — benchmarks/README.md names `Store/StreamedProviderBenchmarks`, but no file or folder `Store/StreamedProviderBenchmarks` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/index.md:14 — docs/index.md installs the package `Memoria` (`dotnet add package Memoria`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/getting-started/install.md:20 — docs/getting-started/install.md installs the package `Memoria` (`dotnet add package Memoria`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.

AX6 · Interface segregation · Fat interface · ×2

Fat interface: IDcbDomainService (21 members) src/Memoria.EventSourcing.Dcb/IDcbDomainService.cs:21 — `IDcbDomainService` declares 21 members: `GetAggregate`, `GetEvents`, `GetEventsFromPosition`, `GetEventsUpToPosition`, `GetEventsBetweenPositions`, `GetEventsFromDate`, `GetEventsUpToDate`, `GetEventsBetweenDates`, `GetLatestPosition`, `GetInMemoryAggregate`, `GetInMemoryAggregate`, `GetInMemoryAggregate`, `GetInMemoryProjection`, `GetInMemoryProjection`, `GetInMemoryProjection`, `GetProjection`, `SaveProjection`, `SaveAggregate`, `SaveEvents`, `UpdateAggregate`, `UpdateProjection`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 21 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IDomainService (21 members) src/Memoria.EventSourcing/IDomainService.cs:6 — `IDomainService` declares 21 members: `GetAggregate`, `GetEvents`, `GetEventsBetweenSequences`, `GetEventsFromSequence`, `GetEventsUpToSequence`, `GetEventsUpToDate`, `GetEventsFromDate`, `GetEventsBetweenDates`, `GetInMemoryAggregate`, `GetInMemoryAggregate`, `GetInMemoryAggregate`, `GetInMemoryProjection`, `GetInMemoryProjection`, `GetInMemoryProjection`, `GetProjection`, `SaveProjection`, `GetLatestEventSequence`, `SaveAggregate`, `SaveEvents`, `UpdateAggregate`, `UpdateProjection`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 21 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.

C3 · Audit Trail · Partial audit-trail evidence · ×1

Partial audit-trail evidence — An audit mechanism is present, but the trail is not yet complete — missing: a dedicated audit read-model (an audit-log/-trail/-entry projection) over the sensitive event streams.

D10 · Test Quality · Mock-dominated test · ×1

Mock-dominated test: DatabaseProperty_ShouldUseOptionsValues tests/Memoria.Caching.Redis.Tests/RedisCacheProviderTests.cs:221 — This test sets up 3 test doubles (for example `Substitute.For<IConnectionMultiplexer>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D39 · IL Efficiency · IL efficiency · ×1

IL efficiency: 5 authored method(s) exceed the IL budget src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/AppendRoutine/DcbAppendRoutine.cs:315 — 5 of 933 first-party methods compile to oversized IL bodies (> 250 instructions); worst: Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.AppendRoutine.DcbAppendRoutine.SqlServerDefinition @ src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/AppendRoutine/DcbAppendRoutine.cs:315, 720 IL instructions; that pulled this dimension to 9.9/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.

M2 · Architecture documentation · No ADRs · ×1

No ADRs — 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.

P10 · Library API & versioning · Large public API surface · ×1

Large public API surface — 202/224 types (90%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.

P3 · Security & performance tooling · No SAST · ×1

No SAST — 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 3078 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.

P4 · Deployment & Rollback · No release approval gate · ×1

No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

X10 · Duplicated predicate · Duplicated predicate · ×1

Duplicated predicate src/Memoria.Validation.FluentValidation/Extensions/ServiceCollectionExtensions.cs:36 — `!type.IsClass || type.IsAbstract || type.IsGenericTypeDefinition` appears character-identically in 2 files — src/Memoria.Validation.FluentValidation/Extensions/ServiceCollectionExtensions.cs, src/Memoria/Extensions/ServiceCollectionExtensions.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.

X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1

Not all async methods take a CancellationToken — Only 205/249 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.

X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1

Null-forgiving operator (`!`) suppressions reduce the NRT score — ~3.5 `!` suppressions per 1k syntax nodes — 270 suppression(s) across the 76836 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

Minor — 59 finding(s)

D12 · Dependency Hygiene · Outdated · ×19

Outdated: Microsoft.EntityFrameworkCore.Sqlite — Microsoft.EntityFrameworkCore.Sqlite 10.0.12 → 10.0.13 available (referenced by Memoria.Benchmarks).
Outdated: Microsoft.EntityFrameworkCore.SqlServer — Microsoft.EntityFrameworkCore.SqlServer 10.0.12 → 10.0.13 available (referenced by Memoria.Benchmarks).
Outdated: Testcontainers.MsSql — Testcontainers.MsSql 4.15.0 → 4.16.0 available (referenced by Memoria.Benchmarks).
Outdated: Testcontainers.PostgreSql — Testcontainers.PostgreSql 4.15.0 → 4.16.0 available (referenced by Memoria.Benchmarks).
Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 10.0.12 → 10.0.13 available (referenced by Memoria.Examples.EventSourcing.Dcb.EntityFrameworkCore).
Outdated: Microsoft.Extensions.Caching.Abstractions — Microsoft.Extensions.Caching.Abstractions 10.0.12 → 10.0.13 available (referenced by Memoria.Caching.Memory).
Outdated: Microsoft.Extensions.Caching.Memory — Microsoft.Extensions.Caching.Memory 10.0.12 → 10.0.13 available (referenced by Memoria.Caching.Memory).
Outdated: Microsoft.Extensions.Options — Microsoft.Extensions.Options 10.0.12 → 10.0.13 available (referenced by Memoria.Caching.Memory).
Outdated: StackExchange.Redis — StackExchange.Redis 3.2.1 → 3.4.5 available (referenced by Memoria.Caching.Redis).
Outdated: Microsoft.EntityFrameworkCore — Microsoft.EntityFrameworkCore 10.0.12 → 10.0.13 available (referenced by Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore).
Outdated: Microsoft.EntityFrameworkCore.Relational — Microsoft.EntityFrameworkCore.Relational 10.0.12 → 10.0.13 available (referenced by Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore).
Outdated: Microsoft.Azure.Cosmos — Microsoft.Azure.Cosmos 3.63.0 → 3.63.2 available (referenced by Memoria.EventSourcing.Store.Cosmos).
Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore — Microsoft.AspNetCore.Identity.EntityFrameworkCore 10.0.12 → 10.0.13 available (referenced by Memoria.EventSourcing.Store.EntityFrameworkCore.Identity).
Outdated: Azure.Messaging.ServiceBus — Azure.Messaging.ServiceBus 7.20.2 → 7.21.0 available (referenced by Memoria.Messaging.ServiceBus).
Outdated: FluentValidation — FluentValidation 12.1.1 → 12.2.0 available (referenced by Memoria.Validation.FluentValidation).
Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 18.10.1 → 18.11.0 available (referenced by Memoria.Caching.Memory.Tests).
Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 4.0.0 → 4.0.1 available (referenced by Memoria.Caching.Memory.Tests).
Outdated: Microsoft.Extensions.TimeProvider.Testing — Microsoft.Extensions.TimeProvider.Testing 10.10.0 → 10.11.0 available (referenced by Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Relational.Tests).
Outdated: Microsoft.EntityFrameworkCore.InMemory — Microsoft.EntityFrameworkCore.InMemory 10.0.12 → 10.0.13 available (referenced by Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Tests).

D10 · Test Quality · Mock framework · ×16

Mock framework: NSubstitute — Memoria.Caching.Memory.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.Caching.Redis.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Relational.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.EventSourcing.Dcb.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.EventSourcing.Store.Cosmos.InMemory.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.EventSourcing.Store.Cosmos.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.EventSourcing.Store.EntityFrameworkCore.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.EventSourcing.Store.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.EventSourcing.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.Messaging.RabbitMq.InMemory.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.Messaging.RabbitMq.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.Messaging.ServiceBus.InMemory.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.Messaging.ServiceBus.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.Tests references NSubstitute.
Mock framework: NSubstitute — Memoria.Validation.FluentValidation.Tests references NSubstitute.

D19 · Documentation Quality · XML-doc coverage · ×15

XML-doc coverage: Memoria.Examples.Ecommerce.Dcb examples/Memoria.Examples.Ecommerce.Dcb/Memoria.Examples.Ecommerce.Dcb.csproj — Memoria.Examples.Ecommerce.Dcb: 51 % XML-doc coverage (30/59).
XML-doc coverage: Memoria.Caching.Memory src/Memoria.Caching.Memory/Memoria.Caching.Memory.csproj — Memoria.Caching.Memory: 100 % XML-doc coverage (10/10).
XML-doc coverage: Memoria.Caching.Redis src/Memoria.Caching.Redis/Memoria.Caching.Redis.csproj — Memoria.Caching.Redis: 100 % XML-doc coverage (12/12).
XML-doc coverage: Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore src/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore/Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore.csproj — Memoria.EventSourcing.Dcb.Store.EntityFrameworkCore: 87 % XML-doc coverage (141/162).
XML-doc coverage: Memoria.EventSourcing.Dcb src/Memoria.EventSourcing.Dcb/Memoria.EventSourcing.Dcb.csproj — Memoria.EventSourcing.Dcb: 100 % XML-doc coverage (85/85).
XML-doc coverage: Memoria.EventSourcing.Store.Cosmos src/Memoria.EventSourcing.Store.Cosmos/Memoria.EventSourcing.Store.Cosmos.csproj — Memoria.EventSourcing.Store.Cosmos: 96 % XML-doc coverage (129/134).
XML-doc coverage: Memoria.EventSourcing.Store.EntityFrameworkCore.Npgsql src/Memoria.EventSourcing.Store.EntityFrameworkCore.Npgsql/Memoria.EventSourcing.Store.EntityFrameworkCore.Npgsql.csproj — Memoria.EventSourcing.Store.EntityFrameworkCore.Npgsql: 100 % XML-doc coverage (4/4).
XML-doc coverage: Memoria.EventSourcing.Store.EntityFrameworkCore src/Memoria.EventSourcing.Store.EntityFrameworkCore/Memoria.EventSourcing.Store.EntityFrameworkCore.csproj — Memoria.EventSourcing.Store.EntityFrameworkCore: 81 % XML-doc coverage (130/160).
XML-doc coverage: Memoria.EventSourcing src/Memoria.EventSourcing/Memoria.EventSourcing.csproj — Memoria.EventSourcing: 73 % XML-doc coverage (78/107).
XML-doc coverage: Memoria.Messaging.RabbitMq.InMemory src/Memoria.Messaging.RabbitMq.InMemory/Memoria.Messaging.RabbitMq.InMemory.csproj — Memoria.Messaging.RabbitMq.InMemory: 65 % XML-doc coverage (15/23).
XML-doc coverage: Memoria.Messaging.RabbitMq src/Memoria.Messaging.RabbitMq/Memoria.Messaging.RabbitMq.csproj — Memoria.Messaging.RabbitMq: 90 % XML-doc coverage (18/20).
XML-doc coverage: Memoria.Messaging.ServiceBus.InMemory src/Memoria.Messaging.ServiceBus.InMemory/Memoria.Messaging.ServiceBus.InMemory.csproj — Memoria.Messaging.ServiceBus.InMemory: 65 % XML-doc coverage (15/23).
XML-doc coverage: Memoria.Messaging.ServiceBus src/Memoria.Messaging.ServiceBus/Memoria.Messaging.ServiceBus.csproj — Memoria.Messaging.ServiceBus: 100 % XML-doc coverage (8/8).
XML-doc coverage: Memoria.Validation.FluentValidation src/Memoria.Validation.FluentValidation/Memoria.Validation.FluentValidation.csproj — Memoria.Validation.FluentValidation: 71 % XML-doc coverage (5/7).
XML-doc coverage: Memoria src/Memoria/Memoria.csproj — Memoria: 89 % XML-doc coverage (141/158).

D23 · Boundary Type-Coupling · Memoria.EventSourcing · ×1

Memoria.EventSourcing: 6 contract type(s) expose producer-owned ids/enums — In Memoria.EventSourcing, 6 contract type(s) (AggregateDiagnostics, DefaultDomainService, IDomainService, ProjectionDiagnostics, StoreFailures, TestStreamId) expose strong-typed ids/value objects (IStreamId); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · Memoria.EventSourcing.Store.Cosmos · ×1

Memoria.EventSourcing.Store.Cosmos: 8 contract type(s) expose producer-owned ids/enums — In Memoria.EventSourcing.Store.Cosmos, 8 contract type(s) (AggregateExtensions, CosmosDataStore, CosmosDomainService, CosmosStoreFailures, DiagnosticsExtensions, EventExtensions, ICosmosDataStore, ProjectionExtensions) expose strong-typed ids/value objects (IStreamId); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · Memoria.EventSourcing.Store.EntityFrameworkCore · ×1

Memoria.EventSourcing.Store.EntityFrameworkCore: 6 contract type(s) expose producer-owned ids/enums — In Memoria.EventSourcing.Store.EntityFrameworkCore, 6 contract type(s) (AggregateExtensions, DiagnosticsExtensions, EntityFrameworkCoreDomainService, EventExtensions, IDomainDbContextExtensions, ProjectionExtensions) expose strong-typed ids/value objects (IStreamId); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · SeatReleasedEvent · ×1

SeatReleasedEvent: 3 contract type(s) expose producer-owned ids/enums — In SeatReleasedEvent, 3 contract type(s) (SeatReleasedEvent, SeatReleasedEvent, SeatReleasedEvent) expose strong-typed ids/value objects (SeatReleasedEvent); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · SomethingHappenedEvent · ×1

SomethingHappenedEvent: 1 contract type(s) expose producer-owned ids/enums — In SomethingHappenedEvent, 1 contract type(s) (SomethingHappenedEvent) expose strong-typed ids/value objects (SomethingHappenedEvent); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · SomethingHappenedEvent2 · ×1

SomethingHappenedEvent2: 1 contract type(s) expose producer-owned ids/enums — In SomethingHappenedEvent2, 1 contract type(s) (SomethingHappenedEvent2) expose strong-typed ids/value objects (SomethingHappenedEvent2); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · TwinReleasedEvent · ×1

TwinReleasedEvent: 1 contract type(s) expose producer-owned ids/enums — In TwinReleasedEvent, 1 contract type(s) (TwinReleasedEvent) expose strong-typed ids/value objects (TwinReleasedEvent); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · UnrelatedEvent · ×1

UnrelatedEvent: 1 contract type(s) expose producer-owned ids/enums — In UnrelatedEvent, 1 contract type(s) (UnrelatedEvent) expose strong-typed ids/value objects (UnrelatedEvent); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

D23 · Boundary Type-Coupling · examples · ×1

examples: 2 contract type(s) expose producer-owned ids/enums — In examples, 2 contract type(s) (GetStudentTranscriptQuery, GetStudentTranscriptQueryHandler) expose strong-typed ids/value objects (GetStudentTranscriptQuery); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3c34e83b150a48a3b1da3fa68b379f27/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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3c34e83b150a48a3b1da3fa68b379f27/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	8	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list Memoria.slnx package --vulnerable --include-transitive --format json	1	artifacts/raw/dotnet-vulnerable.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 42 file(s) — `benchmarks/Memoria.Benchmarks/Program.cs`, `benchmarks/Memoria.Benchmarks/Store/ContentionBenchmark.cs`, `benchmarks/Memoria.Benchmarks/Store/StoreBenchmarkHarness.cs`, `benchmarks/Memoria.Benchmarks/Store/StoreModels.cs`, `src/Memoria.Caching.Memory/MemoryCacheProvider.cs`, … (+37 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—

Run 01a16018-10eb-72c9-99e9-7ce2be1ed047 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 74% · Strong ·

At a glance — Architecture · 96% · Exemplary ·

At a glance — Maturity · 41% · Weak · gated by M2, M4 ·

At a glance — Readiness · 35% · Weak · gated by P2, P3, P8 ·

At a glance — Security · 61% · Adequate · gated by D36, C1 ·

At a glance — Event-Driven · 100% · Exemplary ·

At a glance — Performance · 52% · Adequate · gated by PF3 ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts