Public report of anton-martyniuk/Modern, published 22 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 22 October 2026, 03:12 UTC · Survey ID cd_49396133f17049b292ab594a8a1b1193

anton-martyniuk/Modern

Measured 22 October 2026, 03:10 UTC, at code version cbb57f7

Code coverage: not measuredTest distribution: not measuredBoundary Type-Coupling: not measured

Code coverage is not measured: The suite ran but produced no coverage data.

Test distribution is not measured: Tests outside the analyzed solution.

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 42out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 3 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Code Health 89 Strong Architecture 82 Strong Performance 74 Strong Security and Compliance 45 Weak Maturity 42 Weak Production Readiness 29 Weak

A medium codebase: 23,210 lines of product code in 105 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 29

Findings by how serious they are

1 critical 334 serious 250 minor

4 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 03:10 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

68of 73 dimensions measured by tools. The other 5 are advisory notes from an AI model, which explain the code but don't count towards the score.
539of 585 findings point to an exact file and line, so you can open each one in the code. The other 46 concern the repository as a whole, such as missing documentation.
73dimensions across 6 lenses, read from 23,210 lines of product code in 105 projects.
Chapters

Executive summary

anton-martyniuk/Modern scores 42 out of 100 and is rated Weak, while four of its six lenses score higher still: Code Health at 89, Architecture at 82 and Performance at 74, all rated Strong, and Security and Compliance at 45, rated Weak.

The score is lower than those four because the weakest lens counts most, and here that is Production Readiness, which scores 29 and is rated Weak. Its CI/CD gates 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 1 Leaked secret finding(s) in Secret Scanning and to resolve the 9 Deprecated finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 42 to about 52.

One finding is critical, in Secret Scanning.

Watchdog couldn't measure Test Reliability and IL Efficiency in this code, so those dimensions are left out of the score. The product code is 23,210 lines, which would take an estimated 0.1 person-years, around €20,000, to rebuild.

Code Health 89 Strong Architecture 82 Strong Maturity 42 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 29 Weak, capped by CI/CD gates, Security & performance tooling and Schema migrations Security and Compliance 45 Weak, capped by Access Controls Performance 74 Strong

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 29 · counts for 46%Maturity 42 · counts for 25%Security and Compliance 45 · counts for 14%Performance 74 · counts for 8%Architecture 82 · counts for 4%Code Health 89 · counts for 2%

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

Code composition: what the lines of code are
Business logic 19%Supporting code 63%Tests 0%Generated by tools 11%Code analyzers 7%
New since the last survey: 90 findings

These 90 critical or serious findings weren't in the previous survey, on 7 October 2026.

  • Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs
  • Code Coverage · Coverage not measured — the suite ran but produced no coverage data
  • Dependency Hygiene · Deprecated: xunit tests/IntegrationTests/Modern.Repositories.EFCore.Tests.Integration/Modern.Repositories.EFCore.Tests.Integration.csproj
  • Dependency Hygiene · Deprecated: xunit tests/IntegrationTests/Modern.Repositories.MongoDB.Tests.Integration/Modern.Repositories.MongoDB.Tests.Integration.csproj
  • Dependency Hygiene · Deprecated: xunit tests/IntegrationTests/Modern.Repositories.Dapper.Tests.Integration/Modern.Repositories.Dapper.Tests.Integration.csproj
  • Dependency Hygiene · Deprecated: xunit tests/UnitTests/Modern.CQRS.DataStore.Cached.Tests.Unit/Modern.CQRS.DataStore.Cached.Tests.Unit.csproj
  • Dependency Hygiene · Deprecated: xunit tests/UnitTests/Modern.CQRS.DataStore.InMemory.Tests.Unit/Modern.CQRS.DataStore.InMemory.Tests.Unit.csproj
  • Dependency Hygiene · Deprecated: xunit tests/UnitTests/Modern.CQRS.DataStore.Tests.Unit/Modern.CQRS.DataStore.Tests.Unit.csproj
  • Dependency Hygiene · Deprecated: xunit tests/UnitTests/Modern.Services.DataStore.Cached.Tests.Unit/Modern.Services.DataStore.Cached.Tests.Unit.csproj
  • Dependency Hygiene · Deprecated: xunit tests/UnitTests/Modern.Services.DataStore.InMemory.Tests.Unit/Modern.Services.DataStore.InMemory.Tests.Unit.csproj
  • Dependency Hygiene · Deprecated: xunit tests/UnitTests/Modern.Services.DataStore.Tests.Unit/Modern.Services.DataStore.Tests.Unit.csproj
  • Secret Scanning · REDACTED
  • Explicit Debt · Dead code: HandlerName src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs
  • Explicit Debt · Dead code: EntityRequestAttributeName src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Access Controls · No authorization REDACTED
  • Access Controls · No authorization REDACTED
  • Access Controls · No authorization REDACTED
  • Access Controls · No authorization REDACTED
  • Access Controls · No authorization REDACTED
  • Access Controls · No authorization REDACTED
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory.OData/ModernInMemoryODataController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory.OData/ModernInMemoryODataController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Access Controls · No authorization src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs
  • Cancellation propagation · Async method without CancellationToken: SaveChangesAsync src/Repositories/Modern.Repositories.EFCore/UnitOfWork/ModernUnitOfWork.cs
  • Cancellation propagation · Async method without CancellationToken: FilterByAttributeAsync examples/Modern.MongoDb.Examples/Repositories/ProductRepository.cs
  • Cancellation propagation · Async method without CancellationToken: OrderByPriceAsync examples/Modern.MongoDb.Examples/Repositories/ProductRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetCountryCitiesAsync examples/Modern.Dapper.Examples/Repositories/CityRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetCountryCitiesAsync examples/Modern.EfCore.Examples/Repositories/CityRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetCountryCitiesAsync examples/Modern.Services.DataStore.Examples/Repositories/CityRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetCountryCitiesAsync examples/Modern.Services.DataStore.Examples/Services/CityService.cs
  • Cancellation propagation · Async method without CancellationToken: GetCountryCitiesAsync examples/Modern.Services.DataStore.Cached.Examples/Repositories/CityRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetCountryCitiesAsync examples/Modern.Services.DataStore.Cached.Examples/Services/CityService.cs
  • Cancellation propagation · Async method without CancellationToken: GetCountryCitiesAsync examples/Modern.Services.DataStore.InMemory.Examples/Repositories/CityRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetCountryCitiesAsync examples/Modern.Services.DataStore.InMemory.Examples/Services/CityService.cs
  • Cancellation propagation · Async method without CancellationToken: GetCountryCitiesAsync examples/Modern.Controllers.DataStore.Examples.Customized/Repositories/CityRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetCountryCitiesAsync examples/Modern.Controllers.DataStore.Examples.Customized/Services/CityService.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.EfCore.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Services.DataStore.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Services.DataStore.Cached.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Services.DataStore.InMemory.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.Cached.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.Examples.Customized/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.Cached.Examples.Customized/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.InMemory.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.OData.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.InMemory.OData.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.CQRS.DataStore.Examples/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/Program.cs
  • Schema migrations · Schema created with EnsureCreated() outside the migrations examples/Modern.EfCore.UnitOfWork.Examples/Program.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: 50 findings

These 50 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.

  • Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs
  • Coupling · Off the main sequence: Modern.Controllers.Attributes
  • Coupling · Off the main sequence: Modern.Repositories.EFCore.Attributes
  • Coupling · Off the main sequence: Modern.Repositories.MongoDB.Attributes
  • Coupling · Off the main sequence: Modern.Repositories.Dapper.Attributes
  • Coupling · Off the main sequence: Modern.Repositories.LiteDB.Async.Attributes
  • Coupling · Off the main sequence: Modern.Repositories.LiteDB.Attributes
  • Coupling · Off the main sequence: Modern.Services.DataStore.Attributes
  • Coupling · Off the main sequence: Modern.Services.DataStore.Cached.Attributes
  • Coupling · Off the main sequence: Modern.Services.DataStore.InMemory.Attributes
  • Coupling · Off the main sequence: Modern.Controllers.InMemory.Attributes
  • Code Coverage · No test project references Modern.CQRS.DataStore src/CQRS/Modern.CQRS.DataStore/Modern.CQRS.DataStore.csproj
  • Code Coverage · No test project references Modern.CQRS.DataStore.Cached src/CQRS/Modern.CQRS.DataStore.Cached/Modern.CQRS.DataStore.Cached.csproj
  • Code Coverage · No test project references Modern.Repositories.EFCore src/Repositories/Modern.Repositories.EFCore/Modern.Repositories.EFCore.csproj
  • Code Coverage · No test project references Modern.CQRS.DataStore.Abstractions src/CQRS/Modern.CQRS.DataStore.Abstractions/Modern.CQRS.DataStore.Abstractions.csproj
  • Code Coverage · No test project references Modern.Repositories.Dapper src/Repositories/Modern.Repositories.Dapper/Modern.Repositories.Dapper.csproj
  • Code Coverage · No test project references Modern.Repositories.LiteDB src/Repositories/Modern.Repositories.LiteDB/Modern.Repositories.LiteDB.csproj
  • Code Coverage · No test project references Modern.Repositories.LiteDB.Async src/Repositories/Modern.Repositories.LiteDB.Async/Modern.Repositories.LiteDB.Async.csproj
  • Code Coverage · No test project references Modern.Repositories.MongoDB src/Repositories/Modern.Repositories.MongoDB/Modern.Repositories.MongoDB.csproj
  • Code Coverage · No test project references Modern.Controllers.CQRS.DataStore src/WebApi/Modern.Controllers.CQRS.DataStore/Modern.Controllers.CQRS.DataStore.csproj
  • Code Coverage · No test project references Modern.Controllers.DataStore src/WebApi/Modern.Controllers.DataStore/Modern.Controllers.DataStore.csproj
  • Code Coverage · No test project references Modern.Controllers.DataStore.InMemory src/WebApi/Modern.Controllers.DataStore.InMemory/Modern.Controllers.DataStore.InMemory.csproj
  • Code Coverage · No test project references Modern.Controllers.DataStore.InMemory.OData src/WebApi/Modern.Controllers.DataStore.InMemory.OData/Modern.Controllers.DataStore.InMemory.OData.csproj
  • Code Coverage · No test project references Modern.Controllers.DataStore.OData src/WebApi/Modern.Controllers.DataStore.OData/Modern.Controllers.DataStore.OData.csproj
  • Code Coverage · No test project references Modern.Services.DataStore.InMemory src/Services/Modern.Services.DataStore.InMemory/Modern.Services.DataStore.InMemory.csproj
  • Code Coverage · No test project references Modern.Cache.Redis src/Cache/Modern.Cache.Redis/Modern.Cache.Redis.csproj
  • Code Coverage · No test project references Modern.Cache.InMemory src/Cache/Modern.Cache.InMemory/Modern.Cache.InMemory.csproj
  • Code Coverage · No test project references Modern.Controllers.Attributes src/SourceGenerators/Attributes/Modern.Controllers.Attributes/Modern.Controllers.Attributes.csproj
  • Code Coverage · No test project references Modern.Services.DataStore.InMemory.Abstractions src/Services/Modern.Services.DataStore.InMemory.Abstractions/Modern.Services.DataStore.InMemory.Abstractions.csproj
  • Code Coverage · No test project references Modern.Repositories.EFCore.Attributes src/SourceGenerators/Attributes/Modern.Repositories.EFCore.Attributes/Modern.Repositories.EFCore.Attributes.csproj
  • Code Coverage · No test project references Modern.Controllers.SourceGenerators src/SourceGenerators/Modern.Controllers.SourceGenerators/Modern.Controllers.SourceGenerators.csproj
  • Code Coverage · No test project references Modern.Repositories.EFCore.SourceGenerators src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/Modern.Repositories.EFCore.SourceGenerators.csproj
  • Code Coverage · No test project references Modern.Application.Host src/Host/Modern.Application.Host/Modern.Application.Host.csproj
  • Code Coverage · No test project references Modern.Controllers.InMemory.Attributes src/SourceGenerators/Attributes/Modern.Controllers.InMemory.Attributes/Modern.Controllers.InMemory.Attributes.csproj
  • Code Coverage · No test project references Modern.Controllers.InMemory.SourceGenerators src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/Modern.Controllers.InMemory.SourceGenerators.csproj
  • Code Coverage · No test project references Modern.Repositories.Dapper.Attributes src/SourceGenerators/Attributes/Modern.Repositories.Dapper.Attributes/Modern.Repositories.Dapper.Attributes.csproj
  • Code Coverage · No test project references Modern.Repositories.Dapper.SourceGenerators src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/Modern.Repositories.Dapper.SourceGenerators.csproj
  • Code Coverage · No test project references Modern.Repositories.LiteDB.Async.Attributes src/SourceGenerators/Attributes/Modern.Repositories.LiteDB.Async.Attributes/Modern.Repositories.LiteDB.Async.Attributes.csproj
  • Code Coverage · No test project references Modern.Repositories.LiteDB.Async.SourceGenerators src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators.csproj
  • Code Coverage · No test project references Modern.Repositories.LiteDB.Attributes src/SourceGenerators/Attributes/Modern.Repositories.LiteDB.Attributes/Modern.Repositories.LiteDB.Attributes.csproj
  • Code Coverage · No test project references Modern.Repositories.LiteDB.SourceGenerators src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators.csproj
  • Code Coverage · No test project references Modern.Repositories.MongoDB.Attributes src/SourceGenerators/Attributes/Modern.Repositories.MongoDB.Attributes/Modern.Repositories.MongoDB.Attributes.csproj
  • Code Coverage · No test project references Modern.Repositories.MongoDB.SourceGenerators src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators.csproj
  • Code Coverage · No test project references Modern.Services.DataStore.Attributes src/SourceGenerators/Attributes/Modern.Services.DataStore.Attributes/Modern.Services.DataStore.Attributes.csproj
  • Code Coverage · No test project references Modern.Services.DataStore.Cached.Attributes src/SourceGenerators/Attributes/Modern.Services.DataStore.Cached.Attributes/Modern.Services.DataStore.Cached.Attributes.csproj
  • Code Coverage · No test project references Modern.Services.DataStore.Cached.SourceGenerators src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators.csproj
  • Code Coverage · No test project references Modern.Services.DataStore.InMemory.Attributes src/SourceGenerators/Attributes/Modern.Services.DataStore.InMemory.Attributes/Modern.Services.DataStore.InMemory.Attributes.csproj
  • Code Coverage · No test project references Modern.Services.DataStore.InMemory.SourceGenerators src/SourceGenerators/Modern.Services.DataStore.InMemory.SourceGenerators/Modern.Services.DataStore.InMemory.SourceGenerators.csproj
  • Code Coverage · No test project references Modern.Services.DataStore.SourceGenerators src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/Modern.Services.DataStore.SourceGenerators.csproj
  • Dependency Hygiene · Deprecated: xunit
Rebuild cost: about €20,000 · Estimate
Cost to rebuild€6,500 to €33,000, for 109 to 343 hours of work, about 0.1 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 42. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 23,210 lines of product code, of which 42% is declarations and boilerplate, 32% straight logic and 25% logic with branches
Comment linesThe estimate prices 17,266 lines. Comment lines count towards the size of 23,210 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.

1
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 8 points · Low effort · Secret Scanning
2
Resolve the 9 Deprecated finding(s) in Dependency Hygiene — start with Modern.Repositories.EFCore.Tests.Integration.csproj, Modern.Repositories.MongoDB.Tests.Integration.csproj, Modern.Repositories.Dapper.Tests.Integration.csproj.
Raises the score by about 7 points · Low effort · Dependency Hygiene
3
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 4 points · Low effort · ADR Quality

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 €20,000 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 29 (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 1 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 1 Secret Scanning 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 — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

arch Application.Host Application.Host ctx:CQRS CQRS 5 projects ctx:Cache Cache 3 projects ctx:CQRS->ctx:Cache ctx:Common Common 3 projects ctx:CQRS->ctx:Common ctx:Repositories Repositories 6 projects ctx:CQRS->ctx:Repositories ctx:Cache->ctx:Common ctx:Repositories->ctx:Common ctx:Services Services 5 projects ctx:Services->ctx:Cache ctx:Services->ctx:Common ctx:Services->ctx:Repositories ctx:WebApi WebApi 5 projects ctx:WebApi->ctx:CQRS ctx:WebApi->ctx:Common ctx:WebApi->ctx:Repositories ctx:WebApi->ctx:Services __more__ +1 more contexts

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.

87 modules, with 101 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 47 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 Modern.CQRS.DataStore.Abstract2 Modern.CQRS.DataStore.Abstractions.Commands3 Modern.CQRS.DataStore.Abstractions.Queries4 Modern.CQRS.DataStore.Cached.Abstract5 Modern.Cache.Abstractions6 Modern.Cache.Redis.Configuration7 Modern.Controllers.DataStore.DI.Configuration8 Modern.Controllers.DataStore.OData.DI.Configuration9 Modern.Data.Paging10 Modern.Extensions.Microsoft.DependencyInjection.Models11 Modern.Repositories.Abstractions.Infrastracture12 Modern.Repositories.Abstractions.Specifications13 Modern.Repositories.Dapper.Providers14 Modern.Repositories.EFCore.Configuration15 Microsoft.Extensions.DependencyInjection16 Modern.CQRS.DataStore.Cached.CommandHandlers17 Modern.CQRS.DataStore.Cached.QueryHandlers18 Modern.CQRS.DataStore.CommandHandlers19 Modern.CQRS.DataStore.QueryHandlers20 Modern.Cache.Redis21 Modern.Repositories.Abstractions22 Modern.Repositories.EFCore.Specifications.Base23 Modern.Repositories.LiteDB.Async.Specifications24 Modern.Services.DataStore.Abstractions25 Modern.Services.DataStore.InMemory.Abstractions26 Modern.Services.DataStore.InMemory.Abstractions.Cache27 Modern.Controllers.CQRS.DataStore.DI.Features28 Modern.Controllers.DataStore.DI.Features29 Modern.Controllers.DataStore.InMemory.DI.Features30 Modern.Controllers.DataStore.InMemory.OData.DI.Features31 Modern.Controllers.DataStore.OData.DI.Features32 Modern.Repositories.Dapper33 Modern.Repositories.EFCore34 Modern.Repositories.EFCore.Specifications35 Modern.Repositories.LiteDB36 Modern.Repositories.LiteDB.Async37 Modern.Repositories.MongoDB38 Modern.Services.DataStore39 Modern.Services.DataStore.Cached40 Modern.Services.DataStore.InMemory
1 Modern.CQRS.DataStore.Abstract
2 Modern.CQRS.DataStore.Abstractions.Commands
3 Modern.CQRS.DataStore.Abstractions.Queries
4 Modern.CQRS.DataStore.Cached.Abstract
5 Modern.Cache.Abstractions
6 Modern.Cache.Redis.Configuration
7 Modern.Controllers.DataStore.DI.Configuration
8 Modern.Controllers.DataStore.OData.DI.Configuration
9 Modern.Data.Paging
10 Modern.Extensions.Microsoft.DependencyInjection.Models
11 Modern.Repositories.Abstractions.Infrastracture
12 Modern.Repositories.Abstractions.Specifications
13 Modern.Repositories.Dapper.Providers
14 Modern.Repositories.EFCore.Configuration
15 Microsoft.Extensions.DependencyInjection12211
16 Modern.CQRS.DataStore.Cached.CommandHandlers888
17 Modern.CQRS.DataStore.Cached.QueryHandlers101021
18 Modern.CQRS.DataStore.CommandHandlers88
19 Modern.CQRS.DataStore.QueryHandlers10101
20 Modern.Cache.Redis11
21 Modern.Repositories.Abstractions111
22 Modern.Repositories.EFCore.Specifications.Base1
23 Modern.Repositories.LiteDB.Async.Specifications1
24 Modern.Services.DataStore.Abstractions1
25 Modern.Services.DataStore.InMemory.Abstractions1
26 Modern.Services.DataStore.InMemory.Abstractions.Cache1
27 Modern.Controllers.CQRS.DataStore.DI.Features1
28 Modern.Controllers.DataStore.DI.Features11
29 Modern.Controllers.DataStore.InMemory.DI.Features1
30 Modern.Controllers.DataStore.InMemory.OData.DI.Features1
31 Modern.Controllers.DataStore.OData.DI.Features11
32 Modern.Repositories.Dapper11111
33 Modern.Repositories.EFCore33323
34 Modern.Repositories.EFCore.Specifications11
35 Modern.Repositories.LiteDB1111
36 Modern.Repositories.LiteDB.Async1111
37 Modern.Repositories.MongoDB1111
38 Modern.Services.DataStore111
39 Modern.Services.DataStore.Cached1111
40 Modern.Services.DataStore.InMemory1111
Uses a module listed above itPart of a loopThe module itself
1 Modern.CQRS.DataStore.Abstract2 Modern.CQRS.DataStore.Abstractions.Commands3 Modern.CQRS.DataStore.Abstractions.Queries4 Modern.CQRS.DataStore.Cached.Abstract5 Modern.Cache.Abstractions6 Modern.Cache.Redis.Configuration7 Modern.Controllers.DataStore.DI.Configuration8 Modern.Controllers.DataStore.OData.DI.Configuration9 Modern.Data.Paging10 Modern.Extensions.Microsoft.DependencyInjection.Models11 Modern.Repositories.Abstractions.Infrastracture12 Modern.Repositories.Abstractions.Specifications13 Modern.Repositories.Dapper.Providers14 Modern.Repositories.EFCore.Configuration15 Microsoft.Extensions.DependencyInjection16 Modern.CQRS.DataStore.Cached.CommandHandlers17 Modern.CQRS.DataStore.Cached.QueryHandlers18 Modern.CQRS.DataStore.CommandHandlers19 Modern.CQRS.DataStore.QueryHandlers20 Modern.Cache.Redis21 Modern.Repositories.Abstractions22 Modern.Repositories.EFCore.Specifications.Base23 Modern.Repositories.LiteDB.Async.Specifications24 Modern.Services.DataStore.Abstractions25 Modern.Services.DataStore.InMemory.Abstractions26 Modern.Services.DataStore.InMemory.Abstractions.Cache27 Modern.Controllers.CQRS.DataStore.DI.Features28 Modern.Controllers.DataStore.DI.Features29 Modern.Controllers.DataStore.InMemory.DI.Features30 Modern.Controllers.DataStore.InMemory.OData.DI.Features31 Modern.Controllers.DataStore.OData.DI.Features32 Modern.Repositories.Dapper33 Modern.Repositories.EFCore34 Modern.Repositories.EFCore.Specifications35 Modern.Repositories.LiteDB36 Modern.Repositories.LiteDB.Async37 Modern.Repositories.MongoDB38 Modern.Services.DataStore39 Modern.Services.DataStore.Cached40 Modern.Services.DataStore.InMemoryModern.CQRS.DataStore.Abstract1Modern.CQRS.DataStore.Abstractions.Commands2Modern.CQRS.DataStore.Abstractions.Queries3Modern.CQRS.DataStore.Cached.Abstract4Modern.Cache.Abstractions5Modern.Cache.Redis.Configuration6Modern.Controllers.DataStore.DI.Configuration7Modern.Controllers.DataStore.OData.DI.Configuration8Modern.Data.Paging9Modern.Extensions.Microsoft.DependencyInjection.Models10Modern.Repositories.Abstractions.Infrastracture11Modern.Repositories.Abstractions.Specifications12Modern.Repositories.Dapper.Providers13Modern.Repositories.EFCore.Configuration14Microsoft.Extensions.DependencyInjection15Modern.CQRS.DataStore.Cached.CommandHandlers16Modern.CQRS.DataStore.Cached.QueryHandlers17Modern.CQRS.DataStore.CommandHandlers18Modern.CQRS.DataStore.QueryHandlers19Modern.Cache.Redis20Modern.Repositories.Abstractions21Modern.Repositories.EFCore.Specifications.Base22Modern.Repositories.LiteDB.Async.Specifications23Modern.Services.DataStore.Abstractions24Modern.Services.DataStore.InMemory.Abstractions25Modern.Services.DataStore.InMemory.Abstractions.Cache26Modern.Controllers.CQRS.DataStore.DI.Features27Modern.Controllers.DataStore.DI.Features28Modern.Controllers.DataStore.InMemory.DI.Features29Modern.Controllers.DataStore.InMemory.OData.DI.Features30Modern.Controllers.DataStore.OData.DI.Features31Modern.Repositories.Dapper32Modern.Repositories.EFCore33Modern.Repositories.EFCore.Specifications34Modern.Repositories.LiteDB35Modern.Repositories.LiteDB.Async36Modern.Repositories.MongoDB37Modern.Services.DataStore38Modern.Services.DataStore.Cached39Modern.Services.DataStore.InMemory401221188810102188101011111111111111111111111333231111111111111111111111111+47 more modules (most-connected shown)

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

The Good
D1 · .NET / C# Cyclomatic Complexity 10.0 D2 · .NET / C# Cognitive Complexity 9.8 D3 · .NET / C# God Classes 9.4 D17 · .NET / C# Explicit Debt 9.7 D18 · .NET / C# Solution Shape 7.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 9.0 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 X3 · Repo Exception handling 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.8
The Bad
D4 · .NET / C# Code Duplication 6.6

At a glance — Architecture · 82% · Strong ·

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.0 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 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 Ugly
AX10 · Repo Code composition 4.0

At a glance — Maturity · 42% · Weak · gated by D34, M2 ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 8.0 D21 · .NET / C# Naming Consistency 9.0 D24 · .NET / C# Comment Value 7.6 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0
The Bad
M1 · Repo Documentation (README) 6.4
The Ugly
D20 · .NET / C# ADR Quality 0.0 D34 · .NET / C# Knowledge Freshness 0.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 29% · Weak · gated by P1, P3, P8 ·

The Good
D12 · .NET / C# Dependency Hygiene 8.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 9.3 P6 · Repo Release Hygiene 10.0
The Bad
D13 · .NET / C# Secret Scanning 5.0 P2 · Repo Observability 5.5
The Ugly
P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 P8 · Repo Schema migrations 3.0

At a glance — Security · 45% · Weak · gated by C2 ·

The Good
D28 · .NET / C# Secrets (history) 10.0 D29 · .NET / C# Static Analysis (SAST) 7.3 S1 · Repo Web-Security Posture 8.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 Bad
D44 · .NET / C# Platform End-of-Life 6.0
The Ugly
C2 · Repo Access Controls 0.0

At a glance — Performance · 74% · Strong ·

The Good
PF2 · Repo Allocation hygiene 7.4 PF3 · Repo Async & latency hygiene 10.0
The Bad
PF1 · Repo Benchmark discipline 6.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 categoryFindingsSeverity
A05:2025 — Injection6Medium
A07:2025 — Authentication Failures1High / Critical

Roadmap

Immediately resolve the leaked secret in REDACTED and clean up nine deprecated dependencies in the test projects to secure the codebase. Establish a CI workflow that builds and tests on every push, integrating a security analyzer to fail the build on regressions. Finally, remove ninety-seven orphaned files to improve codebase hygiene and maintainability.

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

Do thisHelpsEffortDimension
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+8.1 ptsLowSecret Scanning
Resolve the 9 Deprecated finding(s) in Dependency Hygiene — start with Modern.Repositories.EFCore.Tests.Integration.csproj, Modern.Repositories.MongoDB.Tests.Integration.csproj, Modern.Repositories.Dapper.Tests.Integration.csproj.+6.9 ptsLowDependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.+3.8 ptsLowADR Quality
Add a CI workflow that builds and runs the test suite on every push/PR.+6.5 ptsMediumCI/CD gates
Run 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 — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.+6.5 ptsMediumSecurity & performance tooling
Resolve the 97 Orphaned file finding(s) in Knowledge Freshness — start with ServicesExtensions.cs (5), Specification.cs (4), ModernServicesOptions.cs (3).+5.7 ptsMediumKnowledge Freshness
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.+4.8 ptsMediumAccess Controls
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+4.4 ptsMediumArchitecture documentation

File quality

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

FileScoreBandWorst signal
src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs6.0MixedExplicit Debt: TodoComment
src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs6.0MixedExplicit Debt: TodoComment
src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs6.0MixedExplicit Debt: Dead code: HandlerName
src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.cs6.0MixedExplicit Debt: TodoComment
src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs6.4MixedExplicit Debt: CommentedOutCode
src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs6.6MixedCognitive Complexity: ModernInMemoryControllerGenerator.Execute (cognitive 16)
src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs6.6MixedCode Duplication: Members sharing a duplicated core (5 members, 50+ identical tokens)
src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs6.7MixedExplicit Debt: TodoComment
src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs6.7MixedExplicit Debt: Dead code: EntityRequestAttributeName
src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs7.0MixedCode Duplication: Duplicated block (31 lines × 2)
src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs7.0MixedCode Duplication: Duplicated block (10 lines × 2)
src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs7.1MixedCode Duplication: Duplicated block (17 lines × 2)
src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs7.2MixedCode Duplication: Members sharing a duplicated core (10 members, 50+ identical tokens)
src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs7.2MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs7.2MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs7.2MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs7.2MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs7.2MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
REDACTED7.2MixedSecret Scanning: Leaked secret: REDACTED
src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs7.4MixedCode Duplication: Members sharing a duplicated core (10 members, 50+ identical tokens)

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 — 1

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 — 334

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 — 250

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. 68 of 73 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.8 — 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 — 73 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D17D18D19D20D21D24D26D27D28D29D34D35D44AX1AX10AX2AX3AX5AX6AX8AX9C2ED5GD1IC1M1M2M3M4P1P2P3P6P8PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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
  1. 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, 539 of 585 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.)
  2. 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.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16196-78b6-7a30-b196-455afe39ea19.

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.

  • D11 Test Reliability — 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. Test reliability not scored — the test tier(s) built and ran but no tests were discovered, so reliability couldn't be exercised.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 161 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — 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. Large codebase (23,210 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
  • C2 Access Controls — 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. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
  • 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. 12 further occurrence(s) are not listed individually; the score already reflects all 52.

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.
  • 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.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • 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.
  • 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").
  • 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.
  • 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.
  • 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.
  • 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.

D2 · Cognitive Complexity9.8 / 10Stronggated by 2 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.8 / 10 · rule-coverage 100% · ceiling Prevented

2 method(s) exceeded the cognitive complexity threshold of 15; the worst was ModernControllerGenerator.Execute at 16.

ModernControllerGenerator.Execute (cognitive 16)src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:25
ModernInMemoryControllerGenerator.Execute (cognitive 16)src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:25

What to do

  1. Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with ModernControllerGenerator.Execute (cognitive 16), ModernInMemoryControllerGenerator.Execute (cognitive 16). — 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 2 together lifts Cognitive Complexity from 9.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

D3 · God Classes9.4 / 10Stronggated by 3 serious findings✓ 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.4 / 10 · rule-coverage 100% · ceiling Prevented

3 god class(es) detected.

TooManyMethods: ModernEfCoreRepositoryWithFactory · ×3src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs

What to do

  1. Resolve the 3 TooManyMethods finding(s) in God Classes — start with ModernEfCoreRepositoryWithFactory.cs, ModernEfCoreRepository.cs, ModernEfCoreRepositoryForUnitOfWork.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

D4 · Code Duplication6.6 / 10Adequate✓ 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 6.6 / 10 · rule-coverage 100% · ceiling Verified

170 duplicated block group(s) detected. A further 18 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 12 of the 188 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 (16 lines × 2) · ×12src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:20
Duplicated block (20 lines × 2) · ×11src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:458
Duplicated block (18 lines × 2) · ×10src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs:67
Duplicated block (9 lines × 2) · ×10src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:524
Duplicated block (11 lines × 2) · ×8src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:611

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

What to do

  1. Resolve the 12 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with ModernCachedService.cs (3), CreateEntitiesCommandHandler.cs, CreateEntityCommandHandler.cs. — One of this dimension's main actionable groups (12 warning-level).
  2. Resolve the 11 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with ModernEfCoreRepository.cs (6), ModernCachedService.cs, ModernEfCoreRepositoryWithFactory.cs. — One of this dimension's main actionable groups (11 warning-level).
  3. Resolve the 10 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with GetCountAllQueryHandler.cs (2), DeleteEntitiesCommandHandler.cs, GetAllQueryHandler.cs. — One of this dimension's main actionable groups (10 warning-level).
  4. Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

D5 · Coupling9.8 / 10Stronggated by 3 serious findings✓ 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

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

Off the main sequence: Modern.Data(net8.0) · ×3src/Common/Modern.Data/Modern.Data.csproj:1

What to do

  1. Resolve the 3 Off the main sequence finding(s) in Coupling — start with Modern.Data.csproj, Modern.Exceptions.csproj, Modern.Extensions.Microsoft.DependencyInjection.csproj. — One of this dimension's main actionable groups (3 warning-level).
  2. Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

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 17 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D12 · Dependency Hygiene8.0 / 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.0 / 10 · rule-coverage 100% · ceiling Verified

32 outdated, 0 vulnerable, 1 deprecated packages.

Deprecated: xunit · ×9tests/IntegrationTests/Modern.Repositories.EFCore.Tests.Integration/Modern.Repositories.EFCore.Tests.Integration.csproj:16
Outdated: Mapster · ×2src/CQRS/Modern.CQRS.DataStore.Cached/Modern.CQRS.DataStore.Cached.csproj:26
Outdated: Microsoft.EntityFrameworkCore.Relational · ×30

What to do

  1. Resolve the 9 Deprecated finding(s) in Dependency Hygiene — start with Modern.Repositories.EFCore.Tests.Integration.csproj, Modern.Repositories.MongoDB.Tests.Integration.csproj, Modern.Repositories.Dapper.Tests.Integration.csproj. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with Modern.CQRS.DataStore.Cached.csproj, Modern.Cache.InMemory.Tests.Integration.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
  3. Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

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 5.0 / 10 · rule-coverage 100% · ceiling Prevented

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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 528 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 55 direct `PackageReference`(s), and 195 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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.

D17 · Explicit Debt9.7 / 10Stronggated by 20 serious findings✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Prevented

18 deducted debt markers + 2 dead symbols across 23210 LoC in the .NET projects (0.2/KLoC) → score 9.7.

CommentedOutCode · ×13examples/Modern.MongoDb.Examples/Repositories/ProductRepository.cs:21
TodoComment · ×5src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.cs:17
Dead code: HandlerName · ×2src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs:27

What to do

  1. Resolve the 13 CommentedOutCode finding(s) in Explicit Debt — start with ServicesExtensions.cs (12), ProductRepository.cs. — One of this dimension's main actionable groups (13 warning-level).
  2. Resolve the 5 TodoComment finding(s) in Explicit Debt — start with MySqlQueryProvider.cs, ModernEfCoreRepository.cs, ModernEfCoreRepositoryForUnitOfWork.cs. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 2 Dead code finding(s) in Explicit Debt — start with DeleteAndReturnEntityCommandHandler.cs, EntityRequestGenerator.cs. — One of this dimension's main actionable groups (2 warning-level).
  4. Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

D18 · Solution Shape7.0 / 10Strong✓ 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 7.0 / 10 · rule-coverage 100% · ceiling Documented

105 projects, 647 source files, 23231 hand-written lines of code (23210 production / 21 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 2227 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 128 inter-project edges. Measured across 2 solutions loaded as one workspace: `src/Modern.sln`, `examples/Modern.Examples.sln`.

Shell project: Modern.CQRS.DataStore.InMemory · ×2src/CQRS/Modern.CQRS.DataStore.InMemory/Modern.CQRS.DataStore.InMemory.csproj

What to do

  1. Resolve the 2 Shell project finding(s) in Solution Shape — start with Modern.CQRS.DataStore.InMemory.csproj, Modern.CQRS.DataStore.InMemory.Abstractions.csproj. — One of this dimension's main actionable groups (2 recommendation-level).

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

D19 · Documentation QualityStrong◐ 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

The repository is well documented with READMEs for each controller assembly (Modern.Controllers.DataStore/README.md, Modern.Controllers.DataStore.InMemory/README.md, Modern.Controllers.DataStore.OData/README.md) and a single architecture/design doc gap. Each README documents its own directory: the OData README shows how to register OData controllers, while the In Memory README shows how to register an In Memory controller; none of them describe what the project is or does (the repository's purpose), nor do they give installation/build/usage guidance for the root repository. (15 of 18 sampled documents could not be assessed: 1 of 2 evaluation groups failed.)

Documentation: no project overview · ×3src/WebApi/Modern.Controllers.DataStore.InMemory/README.md
XML-doc coverage: Modern.Data(net8.0) · ×68src/Common/Modern.Data/Modern.Data.csproj

What to do

  1. Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).

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

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

1 naming inconsistencies across 200 sampled symbols.

The namespace containing the `EntityIncludeQuery` type is misspelled as `Infrastracture` (missing 't') in the fully qualified names. This typo is consistent across multiple usages but represents a spelling error in the codebase's vocabulary.

✓ On the Gold path — maintain.

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

D24 · Comment ValueStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Documented

54 valuable / 2 redundant across 200 sampled comments; 2 shown with locations.

redundant comment · ×2src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:102

What to do

  1. Resolve the 2 redundant comment finding(s) in Comment Value — start with ModernInMemoryControllerGenerator.cs, ModernDapperRepositoryGenerator.cs. — One of this dimension's main actionable groups (2 recommendation-level).

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

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 80 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability8.0 / 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.0 / 10 · rule-coverage 100% · ceiling Documented

84 % of calls cross a namespace and 6 % go through an interface, but 84 % 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

  1. Improve Navigability — currently 8.0/10. — 84 % of calls cross a namespace and 6 % go through an interface, but 84 % 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.

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.

D29 · Static Analysis (SAST)7.3 / 10Strong✓ 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 7.3 / 10 · rule-coverage 100% · ceiling Documented

6 finding(s): 0 critical, 0 high, 6 medium, 0 low.

REDACTED

What to do

  1. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).

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

D34 · Knowledge Freshness0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

100 of 100 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs. Counted over 100 of the 242 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×97src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:1
Most significant orphaned file · ×3src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:1
Dormant codebase

What to do

  1. Resolve the 97 Orphaned file finding(s) in Knowledge Freshness — start with ServicesExtensions.cs (5), Specification.cs (4), ModernServicesOptions.cs (3). — One of this dimension's main actionable groups (97 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with ModernCachedService.cs, ModernInMemoryService.cs, ModernService.cs. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling10.0 / 10Exemplary✓ 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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D44 · Platform End-of-Life6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 82 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

End-of-life runtime: .NET net6.0tests/IntegrationTests/Modern.Cache.Redis.Tests.Integration/Modern.Cache.Redis.Tests.Integration.csproj:4

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Modern.Cache.Redis.Tests.Integration.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

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.

AX10 · Code composition4.0 / 10Weak✓ 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.
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.

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.

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.

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.

  • `IModernServiceCache<TEntity, TId>` declares 17 members under just 13 distinct name(s): `AddOrUpdateAsync`, `AddOrUpdateAsync`, `DeleteAsync`, `DeleteAsync`, `ClearAsync`, `GetByIdAsync`, `TryGetByIdAsync`, `TryGetManyAsync`, `GetAllAsync`, `CountAsync`, `CountAsync`, `ExistsAsync`, `FirstOrDefaultAsync`, `SingleOrDefaultAsync`, `WhereAsync`, `WhereAsync`, `AsEnumerable`. 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. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/Services/Modern.Services.DataStore.InMemory.Abstractions/Cache/IModernServiceCache.cs:11

What to do

  • Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
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.

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.

C2 · Access Controls0.0 / 10Critical✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

  • No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • `CitiesCqrsController.GetCountryCities` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — REDACTED:26, REDACTED:26
  • `CitiesController.GetCountryCities` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×4) — REDACTED:26, REDACTED:26, REDACTED:26, …
  • `ModernCqrsController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:50, src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:50
  • `ModernCqrsController.GetAll` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:75, src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:75
  • `ModernCqrsController.Create` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:93, src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:93
  • `ModernCqrsController.CreateMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:113, src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:113
  • `ModernCqrsController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:136, src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:136
  • `ModernCqrsController.UpdateMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:166, src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:166
  • `ModernCqrsController.Patch` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:197, src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:197
  • `ModernCqrsController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:223, src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:223
  • `ModernCqrsController.DeleteMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:247, src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:247
  • `ModernInMemoryODataController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.DataStore.InMemory.OData/ModernInMemoryODataController.cs:42, src/WebApi/Modern.Controllers.DataStore.InMemory.OData/ModernInMemoryODataController.cs:42
  • `ModernInMemoryController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:50, src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:50
  • `ModernInMemoryController.GetAll` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:74, src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:74
  • `ModernInMemoryController.Create` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:91, src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:91
  • `ModernInMemoryController.CreateMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:109, src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:109
  • `ModernInMemoryController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:130, src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:130
  • `ModernInMemoryController.UpdateMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:158, src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:158
  • `ModernInMemoryController.Patch` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:187

What to do

  • Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
ED5 · Idempotency9.3 / 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.

  • `CommandHandlers.UpdateEntitiesCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs:56
  • `CommandHandlers.DeleteEntitiesCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs:65

What to do

  • Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

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.

  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×11) — src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:50, src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:51, src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:53, …

What to do

  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)6.4 / 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

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 63 of 80 project(s) that lack one — worth up to 1.6 pts.
M2 · Architecture documentation0.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.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project 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.

M4 · Documentation accuracy10.0 / 10Exemplary◐ 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.

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

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.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability5.5 / 10Adequate✓ 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.

  • Only 23/47 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 47, 20 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling0.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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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

  • Run 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 — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release 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.

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.

  • This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema. (×17) — examples/Modern.EfCore.Examples/Program.cs:47, examples/Modern.Services.DataStore.Examples/Program.cs:63, examples/Modern.Services.DataStore.Cached.Examples/Program.cs:73, …

What to do

  • Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
PF1 · Benchmark discipline6.0 / 10Adequate✓ 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.

  • No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

  • Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF2 · Allocation hygiene7.4 / 10Strong✓ 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 77 use(s) across 27,757 production line(s) (~2.8/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ 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.

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×14) — examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs:14, examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Program.cs:12, examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/Program.cs:14, …

What to do

  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

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.

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.

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.

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.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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.

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.

X2 · Cancellation propagation9.0 / 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 253/304 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×39) — src/Repositories/Modern.Repositories.EFCore/UnitOfWork/ModernUnitOfWork.cs:33, src/WebApi/Modern.Controllers.DataStore/ModernController.cs:49, src/WebApi/Modern.Controllers.DataStore/ModernController.cs:90, …

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

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.

X5 · Nullable reference types7.8 / 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.

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

What to do

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

Reference — by lens

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.

LensScoreRatingImpact
Code Health89%StrongStrongest area.
Architecture82%StrongSolid.
Maturity42%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness29%Weak — gated by P1, P3, P8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security45%Weak — gated by C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance74%StrongSolid.
Unscored — 2 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.

  • 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 — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

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.

  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 44 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
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D10 Test Quality — ~15 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
  • D11 Test Reliability — No tests discovered
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
  • 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) — 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.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: this repository's test suite BUILT and its tests PASSED in this run — so neither the build nor our analyzer environment is in question — but the run produced no coverage data, and it captured no message saying why. The usual cause is that the test projects wire up no coverage collector (`--collect:"XPlat Code Coverage"` needs a `coverlet.collector` PackageReference); on a very large suite the instrumented run can also exceed its per-target budget before writing anything. Add a `coverlet.collector` PackageReference, or commit the Cobertura/OpenCover/lcov report your CI already produces, and real coverage is measured. It is excluded from the score rather than counted as a near-zero defect.
  • D9 Test Distribution — 2 test project(s) found on disk but excluded from the analyzed solution.
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a message-bus package; 74 CQRS handler(s)
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • 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
  • 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 — 1 finding(s)
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
Serious — 334 finding(s)
C2 · Access Controls · No authorization · ×40
  • No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • No authorization REDACTED:26 — `CitiesCqrsController.GetCountryCities` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:26 — `CitiesCqrsController.GetCountryCities` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:26 — `CitiesController.GetCountryCities` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:26 — `CitiesController.GetCountryCities` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:26 — `CitiesController.GetCountryCities` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:27 — `CitiesController.GetCountryCities` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:50 — `ModernCqrsController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:50 — `ModernCqrsController.GetById` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:75 — `ModernCqrsController.GetAll` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:75 — `ModernCqrsController.GetAll` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:93 — `ModernCqrsController.Create` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:93 — `ModernCqrsController.Create` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:113 — `ModernCqrsController.CreateMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:113 — `ModernCqrsController.CreateMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:136 — `ModernCqrsController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:136 — `ModernCqrsController.Update` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:166 — `ModernCqrsController.UpdateMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:166 — `ModernCqrsController.UpdateMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:197 — `ModernCqrsController.Patch` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:197 — `ModernCqrsController.Patch` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:223 — `ModernCqrsController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:223 — `ModernCqrsController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:247 — `ModernCqrsController.DeleteMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:247 — `ModernCqrsController.DeleteMany` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • + 15 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×39
  • Async method without CancellationToken: SaveChangesAsync src/Repositories/Modern.Repositories.EFCore/UnitOfWork/ModernUnitOfWork.cs:33 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetById src/WebApi/Modern.Controllers.DataStore/ModernController.cs:49 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Create src/WebApi/Modern.Controllers.DataStore/ModernController.cs:90 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateMany src/WebApi/Modern.Controllers.DataStore/ModernController.cs:108 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Update src/WebApi/Modern.Controllers.DataStore/ModernController.cs:129 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateMany src/WebApi/Modern.Controllers.DataStore/ModernController.cs:157 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Patch src/WebApi/Modern.Controllers.DataStore/ModernController.cs:186 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Delete src/WebApi/Modern.Controllers.DataStore/ModernController.cs:211 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteMany src/WebApi/Modern.Controllers.DataStore/ModernController.cs:234 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetById src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:50 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Create src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:91 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateMany src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:109 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Update src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:130 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateMany src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:158 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Patch src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:187 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Delete src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:212 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteMany src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:235 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetById src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:50 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Create src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:93 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateMany src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:113 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Update src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:136 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateMany src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:166 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Patch src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:197 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Delete src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:223 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteMany src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:247 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 14 more in this group — see findings.md.
P8 · Schema migrations · Schema created with EnsureCreated() outside the migrations · ×17
  • Schema created with EnsureCreated() outside the migrations examples/Modern.EfCore.Examples/Program.cs:47 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Services.DataStore.Examples/Program.cs:63 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Services.DataStore.Cached.Examples/Program.cs:73 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Services.DataStore.InMemory.Examples/Program.cs:63 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.Examples/Program.cs:56 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.Cached.Examples/Program.cs:65 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.Examples.Customized/Program.cs:57 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.Cached.Examples.Customized/Program.cs:79 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.InMemory.Examples/Program.cs:56 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/Program.cs:63 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.OData.Examples/Program.cs:83 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.DataStore.InMemory.OData.Examples/Program.cs:83 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Program.cs:69 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs:75 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.CQRS.DataStore.Examples/Program.cs:60 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/Program.cs:66 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
  • Schema created with EnsureCreated() outside the migrations examples/Modern.EfCore.UnitOfWork.Examples/Program.cs:59 — This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
D17 · Explicit Debt · CommentedOutCode · ×13
  • CommentedOutCode examples/Modern.MongoDb.Examples/Repositories/ProductRepository.cs:21 — 5 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:247 — 5 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:55 — 7 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:84 — 4 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:182 — 4 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:194 — 4 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:213 — 4 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:224 — 4 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:229 — 4 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:237 — 4 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:135 — 11 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:150 — 13 consecutive commented-code lines
  • CommentedOutCode src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:199 — 13 consecutive commented-code lines
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×12
  • Duplicated block (16 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:20 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:20-35 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/CreateEntitiesCommandHandler.cs:19-34 — 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:20` 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 (16 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntityCommandHandler.cs:20 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntityCommandHandler.cs:20-35 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/CreateEntityCommandHandler.cs:19-34 — 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntityCommandHandler.cs:20` 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 (16 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs:21 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs:21-36 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs:20-35 — 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs:21` 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 (16 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs:22 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs:22-37 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntitiesCommandHandler.cs:21-36 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntitiesCommandHandler.cs` as WHOLE FILES: 87% 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 2 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. 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.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.
  • Duplicated block (16 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:20 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:20-35 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntityCommandHandler.cs:19-34 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntityCommandHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:20` 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 (16 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs:22 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs:22-37 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs:21-36 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.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.
  • Duplicated block (16 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityByActionCommandHandler.cs:21 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityByActionCommandHandler.cs:21-36 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntityByActionCommandHandler.cs:20-35 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityByActionCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntityByActionCommandHandler.cs` as WHOLE FILES: 82% 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 2 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. 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityByActionCommandHandler.cs:21` 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 (16 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityCommandHandler.cs:21 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityCommandHandler.cs:21-36 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntityCommandHandler.cs:20-35 — 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityCommandHandler.cs:21` 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 (16 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:290 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:290-305 | src/Services/Modern.Services.DataStore/ModernService.cs:241-256 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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.
  • Duplicated block (16 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:312 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:312-327 | src/Services/Modern.Services.DataStore/ModernService.cs:263-278 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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.
  • Duplicated block (16 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:334 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:334-349 | src/Services/Modern.Services.DataStore/ModernService.cs:285-300 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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.
  • Duplicated block (16 lines × 2) src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:413 — src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:413-428 | src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:435-450 — 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. 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 (20 lines × 2) · ×11
  • Duplicated block (20 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:458 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:458-477 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:464-483 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:458` 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 (20 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:236 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:236-255 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:266-285 — 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/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:236` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:265` calls `NegativeOrZero`, `nameof` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:235` does not — after which the two agree again for 4 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.
  • Duplicated block (20 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:402 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:402-421 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:311-330 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (20 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:428 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:428-447 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:337-356 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (20 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:454 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:454-473 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:363-382 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (20 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:480 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:480-499 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:389-408 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (20 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:506 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:506-525 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:415-434 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (20 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:241 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:241-260 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:272-291 — 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/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:241` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:271` calls `NegativeOrZero`, `nameof` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:240` does not — after which the two agree again for 4 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.
  • Duplicated block (20 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:56 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:56-75 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:56-75 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetFirstOrDefaultQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetFirstOrDefaultQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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.
  • Duplicated block (20 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:57 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:57-76 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:57-76 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetSingleOrDefaultQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetSingleOrDefaultQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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.
  • Duplicated block (20 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWhereQueryHandler.cs:56 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWhereQueryHandler.cs:56-75 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWhereQueryHandler.cs:56-75 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWhereQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWhereQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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 × 2) · ×10
  • Duplicated block (18 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs:67 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs:67-84 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntitiesCommandHandler.cs:58-75 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntitiesCommandHandler.cs` as WHOLE FILES: 87% 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 2 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. 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs:67` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs:86` calls `LogDebug`, `DeleteAsync`, `ConfigureAwait` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntitiesCommandHandler.cs:76` does not — after which the two agree again for 2 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.
  • Duplicated block (18 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetAllQueryHandler.cs:18 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetAllQueryHandler.cs:18-35 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetAllQueryHandler.cs:18-35 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetAllQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetAllQueryHandler.cs` as WHOLE FILES: 84% 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 2 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. 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetAllQueryHandler.cs:18` 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 (18 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountAllQueryHandler.cs:17 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountAllQueryHandler.cs:17-34 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountAllQueryHandler.cs:17-34 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountAllQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountAllQueryHandler.cs` as WHOLE FILES: 84% 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 2 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. 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountAllQueryHandler.cs:17` 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 (18 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountAllQueryHandler.cs:55 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountAllQueryHandler.cs:55-72 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountAllQueryHandler.cs:55-72 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountAllQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountAllQueryHandler.cs` as WHOLE FILES: 84% 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 2 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. 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.
  • Duplicated block (18 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:18 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:18-35 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountQueryHandler.cs:18-35 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:18` 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 (18 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetExistsQueryHandler.cs:18 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetExistsQueryHandler.cs:18-35 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetExistsQueryHandler.cs:18-35 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetExistsQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetExistsQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetExistsQueryHandler.cs:18` 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 (18 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:18 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:18-35 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:18-35 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetFirstOrDefaultQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetFirstOrDefaultQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:18` 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 (18 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:19 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:19-36 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:19-36 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetSingleOrDefaultQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetSingleOrDefaultQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetSingleOrDefaultQueryHandler.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.
  • Duplicated block (18 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWherePagedQueryHandler.cs:20 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWherePagedQueryHandler.cs:20-37 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWherePagedQueryHandler.cs:20-37 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWherePagedQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWherePagedQueryHandler.cs` as WHOLE FILES: 93% 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 2 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. 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWherePagedQueryHandler.cs:20` 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 (18 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWhereQueryHandler.cs:18 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWhereQueryHandler.cs:18-35 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWhereQueryHandler.cs:18-35 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWhereQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWhereQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWhereQueryHandler.cs:18` 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 (9 lines × 2) · ×10
  • Duplicated block (9 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:524 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:524-532 | src/Services/Modern.Services.DataStore/ModernService.cs:439-447 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:524` 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 (9 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:682 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:682-690 | src/Services/Modern.Services.DataStore/ModernService.cs:561-569 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:682` 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 (9 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:151 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:151-159 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:208-216 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:149` calls `ThrowIfNull`, `nameof` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:206` 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.
  • Duplicated block (9 lines × 2) src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:79 — src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:79-87 | src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:81-89 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs` and `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:79` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:79` calls `CreateDbContext` and `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:77` 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.
  • Duplicated block (9 lines × 2) src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:99 — src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:99-107 | src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:102-110 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs` and `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:99` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:100` calls `CreateDbContext` and `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:97` 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.
  • Duplicated block (9 lines × 2) src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:114 — src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:114-122 | src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:117-125 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs` and `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:132` calls `CreateDbContext` and `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:129` does not — after which the two agree again for 2 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.
  • Duplicated block (9 lines × 2) src/Repositories/Modern.Repositories.Dapper/Providers/OracleQueryProvider.cs:23 — src/Repositories/Modern.Repositories.Dapper/Providers/OracleQueryProvider.cs:23-31 | src/Repositories/Modern.Repositories.Dapper/Providers/PostgresQueryProvider.cs:23-31 — 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/Repositories/Modern.Repositories.Dapper/Providers/OracleQueryProvider.cs:23` 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/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:594 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:594-602 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:503-511 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (9 lines × 2) src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:214 — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:214-222 | src/WebApi/Modern.Controllers.DataStore/ModernController.cs:213-221 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs` and `src/WebApi/Modern.Controllers.DataStore/ModernController.cs` as WHOLE FILES: this scan already matched 8 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.
  • Duplicated block (9 lines × 2) src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:237 — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:237-245 | src/WebApi/Modern.Controllers.DataStore/ModernController.cs:236-244 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs` and `src/WebApi/Modern.Controllers.DataStore/ModernController.cs` as WHOLE FILES: this scan already matched 8 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.
D12 · Dependency Hygiene · Deprecated · ×9
  • Deprecated: xunit tests/IntegrationTests/Modern.Repositories.EFCore.Tests.Integration/Modern.Repositories.EFCore.Tests.Integration.csproj:16 — xunit 2.6.2 — 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/IntegrationTests/Modern.Repositories.MongoDB.Tests.Integration/Modern.Repositories.MongoDB.Tests.Integration.csproj:16 — xunit 2.6.2 — 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/IntegrationTests/Modern.Repositories.Dapper.Tests.Integration/Modern.Repositories.Dapper.Tests.Integration.csproj:16 — xunit 2.6.2 — 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/UnitTests/Modern.CQRS.DataStore.Cached.Tests.Unit/Modern.CQRS.DataStore.Cached.Tests.Unit.csproj:16 — xunit 2.6.2 — 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/UnitTests/Modern.CQRS.DataStore.InMemory.Tests.Unit/Modern.CQRS.DataStore.InMemory.Tests.Unit.csproj:16 — xunit 2.6.2 — 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/UnitTests/Modern.CQRS.DataStore.Tests.Unit/Modern.CQRS.DataStore.Tests.Unit.csproj:16 — xunit 2.6.2 — 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/UnitTests/Modern.Services.DataStore.Cached.Tests.Unit/Modern.Services.DataStore.Cached.Tests.Unit.csproj:15 — xunit 2.6.2 — 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/UnitTests/Modern.Services.DataStore.InMemory.Tests.Unit/Modern.Services.DataStore.InMemory.Tests.Unit.csproj:16 — xunit 2.6.2 — 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/UnitTests/Modern.Services.DataStore.Tests.Unit/Modern.Services.DataStore.Tests.Unit.csproj:15 — xunit 2.6.2 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×8
  • Duplicated block (11 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:611 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:611-621 | src/Services/Modern.Services.DataStore/ModernService.cs:500-510 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:611` 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/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:57 — src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:57-67 | src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:58-68 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs` and `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 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.
  • Duplicated block (11 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:407 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:407-417 | src/Services/Modern.Services.DataStore/ModernService.cs:358-368 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:407` 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/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:384 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:384-394 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:293-303 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (11 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:614 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:614-624 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:642-652 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 126 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.
  • Duplicated block (11 lines × 2) src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:189 — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:189-199 | src/WebApi/Modern.Controllers.DataStore/ModernController.cs:188-198 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs` and `src/WebApi/Modern.Controllers.DataStore/ModernController.cs` as WHOLE FILES: this scan already matched 8 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.
  • Duplicated block (11 lines × 2) examples/Modern.Controllers.DataStore.Examples/Migrations/ToolsDbContextFactory.cs:11 — examples/Modern.Controllers.DataStore.Examples/Migrations/ToolsDbContextFactory.cs:11-21 | examples/Modern.Controllers.DataStore.InMemory.Examples/Migrations/ToolsDbContextFactory.cs:11-21 — before extracting anything, compare `examples/Modern.Controllers.DataStore.Examples/Migrations/ToolsDbContextFactory.cs` and `examples/Modern.Controllers.DataStore.InMemory.Examples/Migrations/ToolsDbContextFactory.cs` as WHOLE FILES: 100% 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. 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.
  • Duplicated block (11 lines × 2) examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Migrations/ToolsDbContextFactory.cs:11 — examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Migrations/ToolsDbContextFactory.cs:11-21 | examples/Modern.Controllers.DataStore.Cached.Examples/Migrations/ToolsDbContextFactory.cs:11-21 — before extracting anything, compare `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Migrations/ToolsDbContextFactory.cs` and `examples/Modern.Controllers.DataStore.Cached.Examples/Migrations/ToolsDbContextFactory.cs` as WHOLE FILES: 100% 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. 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 · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×7
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:635 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:635-668 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:542-574 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:625-637 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:663-696 — 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:64 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:64-94 | src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs:66-96 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/CreateEntitiesCommandHandler.cs:55-77 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs:57-80 — 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs:65 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs:65-95 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/TryGetByIdQueryHandler.cs:64-98 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetByIdQueryHandler.cs:56-76 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/TryGetByIdQueryHandler.cs:55-75 — 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/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:198 — src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:198-232 | src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:291-316 | src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:322-345 | src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:351-370 — 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/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:56 — src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:56-73 | src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:79-97 | src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:132-155 | src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:220-237 — 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/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:57 — src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:57-73 | src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:79-96 | src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:130-152 | src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:215-238 — 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/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:72 — src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:72-103 | src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:116-148 | src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:151-183 | src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:186-216 — 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 (17 lines × 2) · ×7
  • Duplicated block (17 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs:20 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs:20-36 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetByIdQueryHandler.cs:19-35 — 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs:20` 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 (17 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/TryGetByIdQueryHandler.cs:19 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/TryGetByIdQueryHandler.cs:19-35 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/TryGetByIdQueryHandler.cs:18-34 — 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/TryGetByIdQueryHandler.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.
  • Duplicated block (17 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:318 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:318-334 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:227-243 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (17 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:571 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:571-587 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:480-496 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (17 lines × 2) src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:34 — src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:34-50 | src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:35-51 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs` and `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 55 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.
  • Duplicated block (17 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:225 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:225-241 | src/Services/Modern.Services.DataStore/ModernService.cs:176-192 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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.
  • Duplicated block (17 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:65 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:65-81 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntityCommandHandler.cs:56-72 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntityCommandHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:65` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:83` calls `LogDebug`, `DeleteAsync`, `ConfigureAwait` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntityCommandHandler.cs:73` does not — after which the two agree again for 2 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 (12 lines × 2) · ×7
  • Duplicated block (12 lines × 2) src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:86 — src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:86-97 | src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:83-94 — before extracting anything, compare `src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs` and `src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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 (12 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:484 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:484-495 | src/Services/Modern.Services.DataStore/ModernService.cs:411-422 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:484` 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs:78 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs:78-89 | src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:83-94 — 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs:78` 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 `request` to `DeleteAndReturnEntityCommand<TEntityDto, TId>` in one and `DeleteEntityCommand<TId>` 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.
  • Duplicated block (12 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:445 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:445-456 | src/Services/Modern.Services.DataStore/ModernService.cs:384-395 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:445` 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/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:341 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:341-352 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:250-261 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (12 lines × 2) src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:132 — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:132-143 | src/WebApi/Modern.Controllers.DataStore/ModernController.cs:131-142 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs` and `src/WebApi/Modern.Controllers.DataStore/ModernController.cs` as WHOLE FILES: this scan already matched 8 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.
  • Duplicated block (12 lines × 2) src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:160 — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:160-171 | src/WebApi/Modern.Controllers.DataStore/ModernController.cs:159-170 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs` and `src/WebApi/Modern.Controllers.DataStore/ModernController.cs` as WHOLE FILES: this scan already matched 8 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×6
  • Duplicated block (15 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:204 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:204-218 | src/Services/Modern.Services.DataStore/ModernService.cs:155-169 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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.
  • Duplicated block (15 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:248 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:248-262 | src/Services/Modern.Services.DataStore/ModernService.cs:199-213 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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.
  • Duplicated block (15 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:269 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:269-283 | src/Services/Modern.Services.DataStore/ModernService.cs:220-234 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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.
  • Duplicated block (15 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:566 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:566-580 | src/Services/Modern.Services.DataStore/ModernService.cs:467-481 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:566` 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 (15 lines × 2) src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:408 — src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:408-422 | src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:429-443 — 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. 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.
  • Duplicated block (15 lines × 2) src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:117 — src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:117-131 | src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:152-166 — 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×6
  • Duplicated block (10 lines × 2) src/Services/Modern.Services.DataStore.Cached/DI/ServicesExtensions.cs:40 — src/Services/Modern.Services.DataStore.Cached/DI/ServicesExtensions.cs:40-49 | src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:30-39 — 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/Services/Modern.Services.DataStore.Cached/DI/ServicesExtensions.cs:40` 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 (10 lines × 2) src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs:86 — src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs:86-95 | src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs:103-112 — 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/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs:86` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs:100` calls `AppendLine` and `src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs:83` does not — after which the two agree again for 2 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.
  • Duplicated block (10 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:153 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:153-162 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:212-221 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:151` calls `ThrowIfNull`, `nameof` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:210` 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.
  • Duplicated block (10 lines × 2) src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:101 — src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:101-110 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:101-110 — before extracting anything, compare `src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs` and `src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 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/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:101` 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 (10 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:742 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:742-751 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:770-779 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 126 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.
  • Duplicated block (10 lines × 2) src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:52 — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:52-61 | src/WebApi/Modern.Controllers.DataStore/ModernController.cs:51-60 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs` and `src/WebApi/Modern.Controllers.DataStore/ModernController.cs` as WHOLE FILES: this scan already matched 8 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.
D17 · Explicit Debt · TodoComment · ×5
  • TodoComment src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.cs:17 — // TODO: test it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:638 — // TODO: no reflection here if possible — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:545 — // TODO: no reflection here if possible — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:666 — // TODO: no reflection here if possible — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:63 — // // TODO: configure this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×5
  • Duplicated block (19 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:359 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:359-377 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:268-286 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (19 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityByActionCommandHandler.cs:66 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityByActionCommandHandler.cs:66-84 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntityByActionCommandHandler.cs:57-75 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityByActionCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntityByActionCommandHandler.cs` as WHOLE FILES: 82% 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 2 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. 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityByActionCommandHandler.cs:66` 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetAllQueryHandler.cs:56 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetAllQueryHandler.cs:56-74 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetAllQueryHandler.cs:56-74 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetAllQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetAllQueryHandler.cs` as WHOLE FILES: 84% 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 2 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. 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.
  • Duplicated block (19 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:56 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:56-74 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountQueryHandler.cs:56-74 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 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.
  • Duplicated block (19 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetExistsQueryHandler.cs:56 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetExistsQueryHandler.cs:56-74 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetExistsQueryHandler.cs:56-74 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetExistsQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetExistsQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 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 (14 lines × 2) · ×5
  • Duplicated block (14 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs:68 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs:68-81 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/TryGetByIdQueryHandler.cs:67-80 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/TryGetByIdQueryHandler.cs` as WHOLE FILES: 83% 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 2 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. 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 (14 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:718 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:718-731 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:746-759 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 126 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.
  • Duplicated block (14 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs:67 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs:67-80 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs:58-71 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs:67` 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 (14 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityCommandHandler.cs:66 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityCommandHandler.cs:66-79 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntityCommandHandler.cs:57-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntityCommandHandler.cs:66` 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 (14 lines × 2) src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:60 — src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:60-73 | src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:84-97 — 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/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:60` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:83` calls `NegativeOrZero`, `nameof` and `src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:59` does not — after which the two agree again for 4 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 (28 lines × 2) · ×4
  • Duplicated block (28 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:533 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:533-560 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:442-469 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (28 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWherePagedQueryHandler.cs:58 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWherePagedQueryHandler.cs:58-85 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWherePagedQueryHandler.cs:58-85 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWherePagedQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWherePagedQueryHandler.cs` as WHOLE FILES: 93% 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 2 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. 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.
  • Duplicated block (28 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:170 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:170-197 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:168-195 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:170` 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 (28 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:490 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:490-517 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:496-523 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:490` 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 (22 lines × 2) · ×4
  • Duplicated block (22 lines × 2) src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:24 — src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:24-45 | src/Repositories/Modern.Repositories.EFCore/Specifications/Base/OrSpecification.cs:24-45 — 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.
  • Duplicated block (22 lines × 2) src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/AndSpecification.cs:24 — src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/AndSpecification.cs:24-45 | src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/OrSpecification.cs:24-45 — 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.
  • Duplicated block (22 lines × 2) src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/AndSpecification.cs:24 — src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/AndSpecification.cs:24-45 | src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/OrSpecification.cs:24-45 — 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.
  • Duplicated block (22 lines × 2) src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/AndSpecification.cs:24 — src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/AndSpecification.cs:24-45 | src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/OrSpecification.cs:24-45 — 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 (24 lines × 2) · ×4
  • Duplicated block (24 lines × 2) src/Repositories/Modern.Repositories.LiteDB.Async/DI/Configuration/ModernLiteDbAsyncRepositorySpecification.cs:10 — src/Repositories/Modern.Repositories.LiteDB.Async/DI/Configuration/ModernLiteDbAsyncRepositorySpecification.cs:10-33 | src/Repositories/Modern.Repositories.LiteDB/DI/Configuration/ModernLiteDbRepositorySpecification.cs:10-33 — before extracting anything, compare `src/Repositories/Modern.Repositories.LiteDB.Async/DI/Configuration/ModernLiteDbAsyncRepositorySpecification.cs` and `src/Repositories/Modern.Repositories.LiteDB/DI/Configuration/ModernLiteDbRepositorySpecification.cs` as WHOLE FILES: 88% 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. 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 (24 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:135 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:135-158 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:133-156 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:135` 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 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:616 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:616-639 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:622-645 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:616` 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 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:652 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:652-675 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:658-681 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:652` 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 × 3) · ×4
  • Duplicated block (11 lines × 3) src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:88 — src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:88-98 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:88-98 | src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:89-99 — before extracting anything, compare `src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs` and `src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:85` calls `AppendLine` and `src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:82` 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.
  • Duplicated block (11 lines × 3) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:763 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:763-773 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:668-678 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:791-801 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
  • Duplicated block (11 lines × 3) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:572 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:572-582 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:578-588 | src/Services/Modern.Services.DataStore/ModernService.cs:473-483 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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 (11 lines × 3) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:113 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:113-123 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:111-121 | src/Services/Modern.Services.DataStore/ModernService.cs:88-98 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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 × 3) · ×4
  • Duplicated block (8 lines × 3) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:67 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:67-74 | src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs:69-76 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs:60-67 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `CreateEntitiesCommand<TEntityDto>` in one and `UpdateEntitiesCommand<TEntityDto>` 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.
  • Duplicated block (8 lines × 3) src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:80 — src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:80-87 | src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:133-140 | src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:221-228 — 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/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:80` 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 (8 lines × 3) src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:80 — src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:80-87 | src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:131-138 | src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:216-223 — 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/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:80` 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 (8 lines × 3) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:783 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:783-790 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:688-695 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:811-818 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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.
D3 · God Classes · TooManyMethods · ×3
  • TooManyMethods: ModernEfCoreRepositoryWithFactory src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs — TooManyMethods — 349 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 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.
  • TooManyMethods: ModernEfCoreRepository src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs — TooManyMethods — 330 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 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.
  • TooManyMethods: ModernEfCoreRepositoryForUnitOfWork src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs — TooManyMethods — 272 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 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.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:415 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:415-437 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:443-465 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:471-493 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:499-521 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:527-549 — 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Features/GenericControllerRouteConvention.cs:28 — src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Features/GenericControllerRouteConvention.cs:28-60 | src/WebApi/Modern.Controllers.DataStore.InMemory.OData/DI/Features/GenericControllerRouteConvention.cs:28-59 | src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericControllerRouteConvention.cs:28-60 | src/WebApi/Modern.Controllers.DataStore.OData/DI/Features/GenericControllerRouteConvention.cs:28-59 | src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.cs:28-60 — 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:22 — src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:22-68 | src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:26-90 | src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:23-77 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:23-77 | src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:23-77 — 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 (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:111 — src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:111-118 | src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:111-118 — before extracting anything, compare `src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs` and `src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 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 (8 lines × 2) src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericTypeControllerFeatureProvider.cs:35 — src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericTypeControllerFeatureProvider.cs:35-42 | src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericTypeControllerFeatureProvider.cs:35-42 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericTypeControllerFeatureProvider.cs` and `src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericTypeControllerFeatureProvider.cs` as WHOLE FILES: 92% 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. 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/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericTypeControllerFeatureProvider.cs:35` 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 (8 lines × 2) src/CQRS/Modern.CQRS.DataStore.Abstractions/Queries/GetFirstOrDefaultQuery.cs:14 — src/CQRS/Modern.CQRS.DataStore.Abstractions/Queries/GetFirstOrDefaultQuery.cs:14-21 | src/CQRS/Modern.CQRS.DataStore.Abstractions/Queries/GetSingleOrDefaultQuery.cs:15-22 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Abstractions/Queries/GetFirstOrDefaultQuery.cs` and `src/CQRS/Modern.CQRS.DataStore.Abstractions/Queries/GetSingleOrDefaultQuery.cs` as WHOLE FILES: 83% 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/CQRS/Modern.CQRS.DataStore.Abstractions/Queries/GetFirstOrDefaultQuery.cs:14` 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/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:179 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:179-185 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:268-274 — 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/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:179` 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/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:158 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:158-164 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:188-194 — 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/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:158` 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 (7 lines × 2) examples/Modern.Cache.InMemory.Examples/Program.cs:51 — examples/Modern.Cache.InMemory.Examples/Program.cs:51-57 | examples/Modern.Cache.Redis.Examples/Program.cs:63-69 — `examples/Modern.Cache.InMemory.Examples/Program.cs` and `examples/Modern.Cache.Redis.Examples/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 7 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:702 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:702-706 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:730-734 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 126 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.
  • Duplicated block (5 lines × 2) src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:92 — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:92-96 | src/WebApi/Modern.Controllers.DataStore/ModernController.cs:91-95 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs` and `src/WebApi/Modern.Controllers.DataStore/ModernController.cs` as WHOLE FILES: this scan already matched 8 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. 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 (5 lines × 2) src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:110 — src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:110-114 | src/WebApi/Modern.Controllers.DataStore/ModernController.cs:109-113 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs` and `src/WebApi/Modern.Controllers.DataStore/ModernController.cs` as WHOLE FILES: this scan already matched 8 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. 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.
D5 · Coupling · Off the main sequence · ×3
  • Off the main sequence: Modern.Data(net8.0) src/Common/Modern.Data/Modern.Data.csproj:1 — Modern.Data(net8.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
  • Off the main sequence: Modern.Exceptions(net8.0) src/Common/Modern.Exceptions/Modern.Exceptions.csproj:1 — Modern.Exceptions(net8.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
  • Off the main sequence: Modern.Extensions.Microsoft.DependencyInjection(net8.0) src/Common/Modern.Extensions.Microsoft.DependencyInjection/Modern.Extensions.Microsoft.DependencyInjection.csproj:1 — Modern.Extensions.Microsoft.DependencyInjection(net8.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
D17 · Explicit Debt · Dead code · ×2
  • Dead code: HandlerName src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs:27 — Field HandlerName — Roslyn's SymbolFinder walked every project the solution loads, including Modern.CQRS.DataStore.Cached(net8.0), 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: EntityRequestAttributeName src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs:120 — Field EntityRequestAttributeName — Roslyn's SymbolFinder walked every project the solution loads, including Modern.Controllers.SourceGenerators, 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.
D4 · Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:65 — src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:65-71 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:74-80 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:83-89 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:92-98 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:101-107 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:65-71 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:74-80 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:83-89 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:92-98 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:101-107 — These 10 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 10 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 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:55 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:55-74 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetExistsQueryHandler.cs:55-74 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:55-75 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:56-76 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWhereQueryHandler.cs:55-75 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountQueryHandler.cs:55-74 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetExistsQueryHandler.cs:55-74 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:55-75 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:56-76 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWhereQueryHandler.cs:55-75 — These 10 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 10 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 10 times.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×2
  • Duplicated block (27 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:356 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:356-382 | src/Services/Modern.Services.DataStore/ModernService.cs:307-333 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore/ModernService.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 262 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.
  • Duplicated block (27 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:412 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:412-438 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:418-444 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:412` 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 (26 lines × 2) · ×2
  • Duplicated block (26 lines × 2) src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericControllerRouteConvention.cs:30 — src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericControllerRouteConvention.cs:30-55 | src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.cs:30-55 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericControllerRouteConvention.cs` and `src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.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 2 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. 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 (26 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/DI/Configuration/ModernCqrsSpecification.cs:8 — src/CQRS/Modern.CQRS.DataStore.Cached/DI/Configuration/ModernCqrsSpecification.cs:8-33 | src/CQRS/Modern.CQRS.DataStore/DI/Configuration/ModernCqrsSpecification.cs:8-33 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/DI/Configuration/ModernCqrsSpecification.cs` and `src/CQRS/Modern.CQRS.DataStore/DI/Configuration/ModernCqrsSpecification.cs` as WHOLE FILES: 92% 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. 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/CQRS/Modern.CQRS.DataStore.Cached/DI/Configuration/ModernCqrsSpecification.cs:8` 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 (11 lines × 4) · ×2
  • Duplicated block (11 lines × 4) src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:81 — src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:81-91 | src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:126-136 | src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:161-171 | src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:194-204 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:76` calls `AppendLine` and `src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:187` does not — after which the two agree again for 2 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.
  • Duplicated block (11 lines × 4) src/Repositories/Modern.Repositories.EFCore/Specifications/Base/Specification.cs:10 — src/Repositories/Modern.Repositories.EFCore/Specifications/Base/Specification.cs:10-20 | src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/Specification.cs:10-20 | src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/Specification.cs:10-20 | src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/Specification.cs:10-20 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/Specifications/Base/Specification.cs` and `src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/Specification.cs` as WHOLE FILES: 96% 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 2 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. 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/Repositories/Modern.Repositories.EFCore/Specifications/Base/Specification.cs:10` 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 (8 lines × 4) · ×2
  • Duplicated block (8 lines × 4) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:65 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:65-72 | src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs:67-74 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/CreateEntitiesCommandHandler.cs:56-63 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs:58-65 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/UpdateEntitiesCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/CreateEntitiesCommandHandler.cs:65` 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 first that the copies are not typed on the same thing: the declarations holding them bind `request` to `CreateEntitiesCommand<TEntityDto>` in one and `UpdateEntitiesCommand<TEntityDto>` 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.
  • Duplicated block (8 lines × 4) src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:71 — src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:71-78 | src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:44-51 | src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:43-50 | src/Repositories/Modern.Repositories.MongoDB/ModernMongoDbRepository.cs:56-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×2
  • Duplicated block (6 lines × 4) src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.cs:23 — src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.cs:23-28 | src/Repositories/Modern.Repositories.Dapper/Providers/OracleQueryProvider.cs:21-26 | src/Repositories/Modern.Repositories.Dapper/Providers/PostgresQueryProvider.cs:21-26 | src/Repositories/Modern.Repositories.Dapper/Providers/SqliteQueryProvider.cs:21-26 — 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 all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.cs:23` 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 (6 lines × 4) src/Repositories/Modern.Repositories.EFCore/Specifications/Base/Specification.cs:59 — src/Repositories/Modern.Repositories.EFCore/Specifications/Base/Specification.cs:59-64 | src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/Specification.cs:59-64 | src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/Specification.cs:59-64 | src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/Specification.cs:59-64 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/Specifications/Base/Specification.cs` and `src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/Specification.cs` as WHOLE FILES: 96% 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 2 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. 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 (6 lines × 3) · ×2
  • Duplicated block (6 lines × 3) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:490 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:490-495 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:496-501 | src/Services/Modern.Services.DataStore/ModernService.cs:417-422 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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 (6 lines × 3) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:412 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:412-417 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:418-423 | src/Services/Modern.Services.DataStore/ModernService.cs:363-368 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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 · Members sharing a duplicated core (17 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (17 members, 50+ identical tokens) examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/DbContexts/CityDbContext.cs:15 — examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.CQRS.DataStore.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.DataStore.Cached.Examples.Customized/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.DataStore.Cached.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.DataStore.Examples.Customized/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.DataStore.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.DataStore.InMemory.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.DataStore.InMemory.OData.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Controllers.DataStore.OData.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.EfCore.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.EfCore.UnitOfWork.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Services.DataStore.Cached.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Services.DataStore.Examples/DbContexts/CityDbContext.cs:15-25 | examples/Modern.Services.DataStore.InMemory.Examples/DbContexts/CityDbContext.cs:15-25 — These 17 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 17 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 17 times.
  • Members sharing a duplicated core (17 members, 50+ identical tokens) examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs:95 — examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs:95-103 | examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Program.cs:89-97 | examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/Program.cs:86-94 | examples/Modern.Controllers.CQRS.DataStore.Examples/Program.cs:80-88 | examples/Modern.Controllers.DataStore.Cached.Examples.Customized/Program.cs:96-104 | examples/Modern.Controllers.DataStore.Cached.Examples/Program.cs:81-89 | examples/Modern.Controllers.DataStore.Examples.Customized/Program.cs:74-82 | examples/Modern.Controllers.DataStore.Examples/Program.cs:72-80 | examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/Program.cs:80-88 | examples/Modern.Controllers.DataStore.InMemory.Examples/Program.cs:72-80 | examples/Modern.Controllers.DataStore.InMemory.OData.Examples/Program.cs:111-119 | examples/Modern.Controllers.DataStore.OData.Examples/Program.cs:111-119 | examples/Modern.EfCore.Examples/Program.cs:100-108 | examples/Modern.EfCore.UnitOfWork.Examples/Program.cs:77-85 | examples/Modern.Services.DataStore.Cached.Examples/Program.cs:129-137 | examples/Modern.Services.DataStore.Examples/Program.cs:116-124 | examples/Modern.Services.DataStore.InMemory.Examples/Program.cs:116-124 — These 17 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 17 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 17 times.
ED5 · Idempotency · Non-idempotent mutation · ×2
  • Non-idempotent mutation: CommandHandlers.UpdateEntitiesCommandHandler.Handle src/CQRS/Modern.CQRS.DataStore/CommandHandlers/UpdateEntitiesCommandHandler.cs:56 — `CommandHandlers.UpdateEntitiesCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
  • Non-idempotent mutation: CommandHandlers.DeleteEntitiesCommandHandler.Handle src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntitiesCommandHandler.cs:65 — `CommandHandlers.DeleteEntitiesCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
D2 · Cognitive Complexity · ModernControllerGenerator.Execute (cognitive 16) · ×1
  • ModernControllerGenerator.Execute (cognitive 16) src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:25 — ModernControllerGenerator.Execute has cognitive complexity 16 (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 · ModernInMemoryControllerGenerator.Execute (cognitive 16) · ×1
  • ModernInMemoryControllerGenerator.Execute (cognitive 16) src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:25 — ModernInMemoryControllerGenerator.Execute has cognitive complexity 16 (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.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) src/Repositories/Modern.Repositories.Dapper/Providers/PostgresQueryProvider.cs:16 — src/Repositories/Modern.Repositories.Dapper/Providers/PostgresQueryProvider.cs:16-31 | src/Repositories/Modern.Repositories.Dapper/Providers/SqliteQueryProvider.cs:16-31 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:148 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:148-172 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:178-202 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:26 — src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:26-95 | src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:26-95 | src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:22-68 | src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:23-77 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:23-77 | src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:23-77 | src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:23-70 | src/SourceGenerators/Modern.Services.DataStore.InMemory.SourceGenerators/ModernInMemoryServiceGenerator.cs:23-70 | src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:23-70 — These 9 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 9 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 9 times.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:23 — src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:23-51 | src/Repositories/Modern.Repositories.EFCore/Specifications/Base/OrSpecification.cs:23-51 | src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/AndSpecification.cs:23-51 | src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/OrSpecification.cs:23-51 | src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/AndSpecification.cs:23-51 | src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/OrSpecification.cs:23-51 | src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/AndSpecification.cs:23-51 | src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/OrSpecification.cs:23-51 — These 8 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 8 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 8 times.
D4 · Code Duplication · Duplicated block (96 lines × 2) · ×1
  • Duplicated block (96 lines × 2) src/Services/Modern.Services.DataStore.Abstractions/IModernCrudService.cs:11 — src/Services/Modern.Services.DataStore.Abstractions/IModernCrudService.cs:11-106 | src/Services/Modern.Services.DataStore.InMemory.Abstractions/IModernCrudInMemoryService.cs:11-106 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Abstractions/IModernCrudService.cs` and `src/Services/Modern.Services.DataStore.InMemory.Abstractions/IModernCrudInMemoryService.cs` as WHOLE FILES: 93% 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. 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/Services/Modern.Services.DataStore.Abstractions/IModernCrudService.cs:11` 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 (52 lines × 2) · ×1
  • Duplicated block (52 lines × 2) src/Services/Modern.Services.DataStore.Abstractions/IModernQueryService.cs:14 — src/Services/Modern.Services.DataStore.Abstractions/IModernQueryService.cs:14-65 | src/Services/Modern.Services.DataStore.InMemory.Abstractions/IModernQueryInMemoryService.cs:13-64 — 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/Services/Modern.Services.DataStore.Abstractions/IModernQueryService.cs:14` 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 (48 lines × 2) · ×1
  • Duplicated block (48 lines × 2) src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:27 — src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:27-74 | src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:27-74 — before extracting anything, compare `src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs` and `src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 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/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:27` 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 (31 lines × 5) · ×1
  • Duplicated block (31 lines × 5) src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Configuration/ModernControllerSpecification.cs:6 — src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Configuration/ModernControllerSpecification.cs:6-36 | src/WebApi/Modern.Controllers.DataStore.InMemory.OData/DI/Configuration/ModernControllerSpecification.cs:6-36 | src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Configuration/ModernControllerSpecification.cs:6-36 | src/WebApi/Modern.Controllers.DataStore.OData/DI/Configuration/ModernControllerSpecification.cs:6-36 | src/WebApi/Modern.Controllers.DataStore/DI/Configuration/ModernControllerSpecification.cs:6-36 — before extracting anything, compare `src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Configuration/ModernControllerSpecification.cs` and `src/WebApi/Modern.Controllers.DataStore.InMemory.OData/DI/Configuration/ModernControllerSpecification.cs` as WHOLE FILES: 96% 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. 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/WebApi/Modern.Controllers.CQRS.DataStore/DI/Configuration/ModernControllerSpecification.cs:6` 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 (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:574 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:574-604 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:580-610 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:574` 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 (29 lines × 3) · ×1
  • Duplicated block (29 lines × 3) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:636 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:636-664 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:543-571 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:664-692 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:666` calls `SaveChangesAsync`, `ConfigureAwait` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:573` does not — after which the two agree again for 4 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 (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:530 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:530-559 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:536-565 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:530` 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 (27 lines × 3) · ×1
  • Duplicated block (27 lines × 3) src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:24 — src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:24-50 | src/SourceGenerators/Modern.Services.DataStore.InMemory.SourceGenerators/ModernInMemoryServiceGenerator.cs:24-50 | src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:24-50 — before extracting anything, compare `src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs` and `src/SourceGenerators/Modern.Services.DataStore.InMemory.SourceGenerators/ModernInMemoryServiceGenerator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:24` 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 (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/LiteDbAsyncSpecification.cs:28 — src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/LiteDbAsyncSpecification.cs:28-52 | src/Repositories/Modern.Repositories.LiteDB/Specifications/LiteDbSpecification.cs:28-52 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `queryable` to `ILiteQueryableAsync<TEntity>` in one and `ILiteQueryable<TEntity>` 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–24 lines × 5) · ×1
  • Duplicated block (23–24 lines × 5) src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Features/GenericControllerRouteConvention.cs:37 — src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Features/GenericControllerRouteConvention.cs:37-60 | src/WebApi/Modern.Controllers.DataStore.InMemory.OData/DI/Features/GenericControllerRouteConvention.cs:37-59 | src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericControllerRouteConvention.cs:38-60 | src/WebApi/Modern.Controllers.DataStore.OData/DI/Features/GenericControllerRouteConvention.cs:37-59 | src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.cs:38-60 — before extracting anything, compare `src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericControllerRouteConvention.cs` and `src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.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 2 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. 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/WebApi/Modern.Controllers.CQRS.DataStore/DI/Features/GenericControllerRouteConvention.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 (21 lines × 3) · ×1
  • Duplicated block (21 lines × 3) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:544 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:544-564 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:453-473 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:570-590 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:544` 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 (18 lines × 4) · ×1
  • Duplicated block (18 lines × 4) src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:23 — src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:23-40 | src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:24-41 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:24-41 | src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:24-41 — before extracting anything, compare `src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs` and `src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:23` 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–21 lines × 2) · ×1
  • Duplicated block (19–21 lines × 2) src/Repositories/Modern.Repositories.EFCore/Specifications/EfCoreSpecification.cs:35 — src/Repositories/Modern.Repositories.EFCore/Specifications/EfCoreSpecification.cs:35-53 | src/Repositories/Modern.Repositories.MongoDB/Specifications/MongoDbSpecification.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/Repositories/Modern.Repositories.EFCore/Specifications/EfCoreSpecification.cs:35` 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 (18–19 lines × 2) · ×1
  • Duplicated block (18–19 lines × 2) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:687 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:687-704 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:693-711 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:687` 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 (17–18 lines × 9) · ×1
  • Duplicated block (17–18 lines × 9) src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:67 — src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:67-84 | src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:67-84 | src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:42-58 | src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:50-67 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:50-67 | src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:50-67 | src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:43-60 | src/SourceGenerators/Modern.Services.DataStore.InMemory.SourceGenerators/ModernInMemoryServiceGenerator.cs:43-60 | src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:43-60 — before extracting anything, compare `src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs` and `src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 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. 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 (13–17 lines × 2) · ×1
  • Duplicated block (13–17 lines × 2) src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:329 — src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:329-345 | src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:358-370 — 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/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:329` 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 (13–16 lines × 3) · ×1
  • Duplicated block (13–16 lines × 3) src/Repositories/Modern.Repositories.EFCore/Specifications/EfCoreSpecification.cs:27 — src/Repositories/Modern.Repositories.EFCore/Specifications/EfCoreSpecification.cs:27-39 | src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/LiteDbAsyncSpecification.cs:27-42 | src/Repositories/Modern.Repositories.LiteDB/Specifications/LiteDbSpecification.cs:27-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/Specifications/EfCoreSpecification.cs:27` 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 first that the copies are not typed on the same thing: the declarations holding them bind `queryable` to `IQueryable<TEntity>` in one and `ILiteQueryableAsync<TEntity>` 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 (11–16 lines × 2) · ×1
  • Duplicated block (11–16 lines × 2) src/Cache/Modern.Cache.Redis/ModernRedisCache.cs:39 — src/Cache/Modern.Cache.Redis/ModernRedisCache.cs:39-54 | src/Cache/Modern.Cache.Redis/ModernRedisCache.cs:60-70 — 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.
D4 · Code Duplication · Duplicated block (12 lines × 8) · ×1
  • Duplicated block (12 lines × 8) src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:34 — src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:34-45 | src/Repositories/Modern.Repositories.EFCore/Specifications/Base/OrSpecification.cs:34-45 | src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/AndSpecification.cs:34-45 | src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/OrSpecification.cs:34-45 | src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/AndSpecification.cs:34-45 | src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/OrSpecification.cs:34-45 | src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/AndSpecification.cs:34-45 | src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/OrSpecification.cs:34-45 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs` and `src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/AndSpecification.cs` as WHOLE FILES: 93% 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. 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/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:34` 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 (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:61 — src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:61-73 | src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:84-96 — 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/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:61` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:83` calls `NegativeOrZero`, `nameof` and `src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:60` does not — after which the two agree again for 4 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 (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:199 — src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:199-210 | src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:292-303 | src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:323-334 | src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:352-363 — all 4 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/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:199` 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 × 5) · ×1
  • Duplicated block (10 lines × 5) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:416 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:416-425 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:444-453 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:472-481 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:500-509 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:528-537 — all 5 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/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:416` 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 (6 lines × 5) · ×1
  • Duplicated block (6 lines × 5) src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:60 — src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:60-65 | src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:60-65 | src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:43-48 | src/SourceGenerators/Modern.Services.DataStore.InMemory.SourceGenerators/ModernInMemoryServiceGenerator.cs:43-48 | src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:43-48 — before extracting anything, compare `src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs` and `src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 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 (10 lines × 10) · ×1
  • Duplicated block (10 lines × 10) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:56 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:56-65 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetExistsQueryHandler.cs:56-65 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:56-65 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:57-66 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWhereQueryHandler.cs:56-65 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountQueryHandler.cs:56-65 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetExistsQueryHandler.cs:56-65 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:56-65 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:57-66 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWhereQueryHandler.cs:56-65 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountQueryHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 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/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:56` 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 first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GetCountQuery<TEntityDbo, TId>` in one and `GetExistsQuery<TEntityDbo, TId>` 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 (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs:66 — src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs:66-75 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/TryGetByIdQueryHandler.cs:65-74 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetByIdQueryHandler.cs:57-66 | src/CQRS/Modern.CQRS.DataStore/QueryHandlers/TryGetByIdQueryHandler.cs:56-65 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs` and `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/TryGetByIdQueryHandler.cs` as WHOLE FILES: 83% 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 2 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetByIdQueryHandler.cs:66` 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 (9–10 lines × 3) · ×1
  • Duplicated block (9–10 lines × 3) src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:64 — src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:64-72 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteAndReturnEntityCommandHandler.cs:56-65 | src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntityCommandHandler.cs:55-63 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/CommandHandlers/DeleteEntityCommandHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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/CQRS/Modern.CQRS.DataStore.Cached/CommandHandlers/DeleteEntityCommandHandler.cs:64` 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 first that the copies are not typed on the same thing: the declarations holding them bind `request` to `DeleteEntityCommand<TId>` in one and `DeleteAndReturnEntityCommand<TEntityDto, TId>` 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 (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:59 — src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:59-63 | src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:71-75 | src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:68-72 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:68-72 | src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:68-72 — before extracting anything, compare `src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs` and `src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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 (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.cs:19 — src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.cs:19-25 | src/Repositories/Modern.Repositories.Dapper/Providers/PostgresQueryProvider.cs:17-23 | src/Repositories/Modern.Repositories.Dapper/Providers/SqlServerQueryProvider.cs:17-23 | src/Repositories/Modern.Repositories.Dapper/Providers/SqliteQueryProvider.cs:17-23 — 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 all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.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 (5 lines × 10) · ×1
  • Duplicated block (5 lines × 10) src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:67 — src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:67-71 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:76-80 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:85-89 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:94-98 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:103-107 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:67-71 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:76-80 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:85-89 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:94-98 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:103-107 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs` and `src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs` as WHOLE FILES: 93% 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 2 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. 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/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:67` 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 (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:644 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:644-651 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:551-558 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:629-633 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:672-679 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:644` 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.
D4 · Code Duplication · Duplicated block (39 lines × 2) · ×1
  • Duplicated block (39 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/Abstract/BaseMediatorHandler.cs:25 — src/CQRS/Modern.CQRS.DataStore.Cached/Abstract/BaseMediatorHandler.cs:25-70 | src/CQRS/Modern.CQRS.DataStore/Abstract/BaseMediatorHandler.cs:24-62 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/Abstract/BaseMediatorHandler.cs` and `src/CQRS/Modern.CQRS.DataStore/Abstract/BaseMediatorHandler.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. 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 (25 lines × 5) · ×1
  • Duplicated block (25 lines × 5) src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Configuration/ModernControllersOptions.cs:36 — src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Configuration/ModernControllersOptions.cs:36-63 | src/WebApi/Modern.Controllers.DataStore.InMemory.OData/DI/Configuration/ModernODataControllersOptions.cs:30-54 | src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Configuration/ModernControllersOptions.cs:36-63 | src/WebApi/Modern.Controllers.DataStore.OData/DI/Configuration/ModernODataControllersOptions.cs:30-54 | src/WebApi/Modern.Controllers.DataStore/DI/Configuration/ModernControllersOptions.cs:36-63 — before extracting anything, compare `src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Configuration/ModernControllersOptions.cs` and `src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Configuration/ModernControllersOptions.cs` as WHOLE FILES: 97% 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. 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 (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:69 — src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:69-77 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:62-70 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:69-77 — before extracting anything, compare `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs` and `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 299 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 (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:389 — src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:389-400 | src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:395-406 | src/Services/Modern.Services.DataStore/ModernService.cs:340-351 — before extracting anything, compare `src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs` and `src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 301 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 (35 lines × 2) · ×1
  • Duplicated block (35 lines × 2) src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:28 — src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:28-62 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:28-62 — before extracting anything, compare `src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs` and `src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs` as WHOLE FILES: 93% 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 2 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. 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 (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) examples/Modern.LiteDb.Async.Examples/Entities/CarDbo.cs:6 — examples/Modern.LiteDb.Async.Examples/Entities/CarDbo.cs:6-41 | examples/Modern.LiteDb.Examples/Entities/CarDbo.cs:6-41 — before extracting anything, compare `examples/Modern.LiteDb.Async.Examples/Entities/CarDbo.cs` and `examples/Modern.LiteDb.Examples/Entities/CarDbo.cs` as WHOLE FILES: 96% 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. 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 `examples/Modern.LiteDb.Async.Examples/Entities/CarDbo.cs:6` 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 (27 lines × 17) · ×1
  • Duplicated block (27 lines × 17) examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Entities/CityDbo.cs:8 — examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.CQRS.DataStore.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.DataStore.Cached.Examples.Customized/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.DataStore.Cached.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.DataStore.Examples.Customized/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.DataStore.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.DataStore.InMemory.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.DataStore.InMemory.OData.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.Controllers.DataStore.OData.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.EfCore.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.EfCore.UnitOfWork.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.Services.DataStore.Cached.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.Services.DataStore.Examples/Entities/CityDbo.cs:8-34 | examples/Modern.Services.DataStore.InMemory.Examples/Entities/CityDbo.cs:8-34 — before extracting anything, compare `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Entities/CityDbo.cs` and `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Entities/CityDbo.cs` as WHOLE FILES: 92% 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. 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 `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Entities/CityDbo.cs:8` 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 (26 lines × 16) · ×1
  • Duplicated block (26 lines × 16) examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Models/CityDto.cs:6 — examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Models/CityDto.cs:6-31 | examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Models/CityDto.cs:6-31 | examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/Models/CityDto.cs:6-31 | examples/Modern.Controllers.CQRS.DataStore.Examples/Models/CityDto.cs:6-31 | examples/Modern.Controllers.DataStore.Cached.Examples.Customized/Models/CityDto.cs:6-31 | examples/Modern.Controllers.DataStore.Cached.Examples/Models/CityDto.cs:6-31 | examples/Modern.Controllers.DataStore.Examples.Customized/Models/CityDto.cs:6-31 | examples/Modern.Controllers.DataStore.Examples/Models/CityDto.cs:6-31 | examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/Models/CityDto.cs:6-31 | examples/Modern.Controllers.DataStore.InMemory.Examples/Models/CityDto.cs:6-31 | examples/Modern.Controllers.DataStore.InMemory.OData.Examples/Models/CityDto.cs:6-31 | examples/Modern.Controllers.DataStore.OData.Examples/Models/CityDto.cs:6-31 | examples/Modern.EfCore.UnitOfWork.Examples/Models/CityDto.cs:6-31 | examples/Modern.Services.DataStore.Cached.Examples/Models/CityDto.cs:6-31 | examples/Modern.Services.DataStore.Examples/Models/CityDto.cs:6-31 | examples/Modern.Services.DataStore.InMemory.Examples/Models/CityDto.cs:6-31 — before extracting anything, compare `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Models/CityDto.cs` and `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Models/CityDto.cs` as WHOLE FILES: 96% 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. 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 `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Models/CityDto.cs:6` 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 (26 lines × 13) · ×1
  • Duplicated block (26 lines × 13) examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Models/UpdateCityRequest.cs:6 — examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.CQRS.DataStore.Examples/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.DataStore.Cached.Examples.Customized/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.DataStore.Cached.Examples/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.DataStore.Examples.Customized/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.DataStore.Examples/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.DataStore.InMemory.Examples/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.DataStore.InMemory.OData.Examples/Models/UpdateCityRequest.cs:6-31 | examples/Modern.Controllers.DataStore.OData.Examples/Models/UpdateCityRequest.cs:6-31 | examples/Modern.EfCore.UnitOfWork.Examples/Models/UpdateCityRequest.cs:6-31 — before extracting anything, compare `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Models/UpdateCityRequest.cs` and `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Models/UpdateCityRequest.cs` as WHOLE FILES: 96% 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. 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 `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Models/UpdateCityRequest.cs:6` 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 (8 lines × 16) · ×1
  • Duplicated block (8 lines × 16) examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs:96 — examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs:96-103 | examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Program.cs:90-97 | examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/Program.cs:87-94 | examples/Modern.Controllers.CQRS.DataStore.Examples/Program.cs:81-88 | examples/Modern.Controllers.DataStore.Cached.Examples.Customized/Program.cs:97-104 | examples/Modern.Controllers.DataStore.Cached.Examples/Program.cs:82-89 | examples/Modern.Controllers.DataStore.Examples.Customized/Program.cs:75-82 | examples/Modern.Controllers.DataStore.Examples/Program.cs:73-80 | examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/Program.cs:81-88 | examples/Modern.Controllers.DataStore.InMemory.Examples/Program.cs:73-80 | examples/Modern.Controllers.DataStore.InMemory.OData.Examples/Program.cs:112-119 | examples/Modern.Controllers.DataStore.OData.Examples/Program.cs:112-119 | examples/Modern.EfCore.UnitOfWork.Examples/Program.cs:78-85 | examples/Modern.Services.DataStore.Cached.Examples/Program.cs:130-137 | examples/Modern.Services.DataStore.Examples/Program.cs:117-124 | examples/Modern.Services.DataStore.InMemory.Examples/Program.cs:117-124 — `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs` and `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 13 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/Modern.EfCore.UnitOfWork.Examples/Program.cs:74` calls `Run` and `examples/Modern.Services.DataStore.Cached.Examples/Program.cs:126` does not — after which the two agree again for 2 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 (7 lines × 17) · ×1
  • Duplicated block (7 lines × 17) examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/DbContexts/CityDbContext.cs:16 — examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.CQRS.DataStore.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.DataStore.Cached.Examples.Customized/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.DataStore.Cached.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.DataStore.Examples.Customized/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.DataStore.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.DataStore.InMemory.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.DataStore.InMemory.OData.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Controllers.DataStore.OData.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.EfCore.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.EfCore.UnitOfWork.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Services.DataStore.Cached.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Services.DataStore.Examples/DbContexts/CityDbContext.cs:16-22 | examples/Modern.Services.DataStore.InMemory.Examples/DbContexts/CityDbContext.cs:16-22 — before extracting anything, compare `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/DbContexts/CityDbContext.cs` and `examples/Modern.Controllers.DataStore.Cached.Examples/DbContexts/CityDbContext.cs` as WHOLE FILES: 100% 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. 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 (5 lines × 17) · ×1
  • Duplicated block (5 lines × 17) examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs:99 — examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs:99-103 | examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Program.cs:93-97 | examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/Program.cs:90-94 | examples/Modern.Controllers.CQRS.DataStore.Examples/Program.cs:84-88 | examples/Modern.Controllers.DataStore.Cached.Examples.Customized/Program.cs:100-104 | examples/Modern.Controllers.DataStore.Cached.Examples/Program.cs:85-89 | examples/Modern.Controllers.DataStore.Examples.Customized/Program.cs:78-82 | examples/Modern.Controllers.DataStore.Examples/Program.cs:76-80 | examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/Program.cs:84-88 | examples/Modern.Controllers.DataStore.InMemory.Examples/Program.cs:76-80 | examples/Modern.Controllers.DataStore.InMemory.OData.Examples/Program.cs:115-119 | examples/Modern.Controllers.DataStore.OData.Examples/Program.cs:115-119 | examples/Modern.EfCore.Examples/Program.cs:104-108 | examples/Modern.EfCore.UnitOfWork.Examples/Program.cs:81-85 | examples/Modern.Services.DataStore.Cached.Examples/Program.cs:133-137 | examples/Modern.Services.DataStore.Examples/Program.cs:120-124 | examples/Modern.Services.DataStore.InMemory.Examples/Program.cs:120-124 — `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs` and `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 13 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs:99` 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.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET net6.0 tests/IntegrationTests/Modern.Cache.Redis.Tests.Integration/Modern.Cache.Redis.Tests.Integration.csproj:4 — tests/IntegrationTests/Modern.Cache.Redis.Tests.Integration/Modern.Cache.Redis.Tests.Integration.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — the suite ran but produced no coverage data — Coverage NOT MEASURED: this repository's test suite BUILT and its tests PASSED in this run — so neither the build nor our analyzer environment is in question — but the run produced no coverage data, and it captured no message saying why. The usual cause is that the test projects wire up no coverage collector (`--collect:"XPlat Code Coverage"` needs a `coverlet.collector` PackageReference); on a very large suite the instrumented run can also exceed its per-target budget before writing anything. Add a `coverlet.collector` PackageReference, or commit the Cobertura/OpenCover/lcov report your CI already produces, and real coverage is measured. It is excluded from the score rather than counted as a near-zero defect.
D9 · Test Distribution · Tests outside the analyzed solution · ×1
  • Tests outside the analyzed solution — 2 .NET test project(s) exist on disk but aren't in the .NET solution that was analyzed (e.g. Modern.Cache.Redis.Tests.Integration.csproj), so they aren't built or gated with the production code and can't be assessed here. If this .NET code is part of the product, add those projects to the solution or point Watchdog at a solution that includes them; if it is a client/compatibility harness beside a product written in another language, nothing is wrong here and this row can be ignored.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
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.
Minor — 152 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×97
  • Orphaned file src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.Dapper/ModernDapperRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.MongoDB/ModernMongoDbRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.Abstractions/IModernQueryRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/WebApi/Modern.Controllers.CQRS.DataStore/ModernCqrsController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/WebApi/Modern.Controllers.DataStore.InMemory/ModernInMemoryController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/WebApi/Modern.Controllers.DataStore/ModernController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Modern.Services.DataStore.InMemory.Abstractions/IModernQueryInMemoryService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Modern.Services.DataStore.Abstractions/IModernQueryService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Modern.Services.DataStore.InMemory/Cache/ModernInMemoryServiceCache.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Modern.Services.DataStore.InMemory.Abstractions/IModernCrudInMemoryService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Modern.Services.DataStore.Abstractions/IModernCrudService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.Abstractions/IModernCrudRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Repositories/Modern.Repositories.Dapper/Extensions/DapperAsyncExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 72 more in this group — see findings.md.
S1 · Web-Security Posture · No security response headers detected · ×15
  • No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • No security response headers detected examples/Modern.Controllers.CQRS.DataStore.Cached.Examples.Customized/Program.cs:14 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.CQRS.DataStore.Cached.Examples/Program.cs:12 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.CQRS.DataStore.Examples.Customized/Program.cs:14 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.CQRS.DataStore.Examples/Program.cs:12 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.DataStore.Cached.Examples.Customized/Program.cs:11 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.DataStore.Cached.Examples/Program.cs:9 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.DataStore.Examples.Customized/Program.cs:10 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.DataStore.Examples/Program.cs:9 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.DataStore.InMemory.Examples.Customized/Program.cs:11 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.DataStore.InMemory.Examples/Program.cs:9 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.DataStore.InMemory.OData.Examples/Program.cs:13 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.Controllers.DataStore.OData.Examples/Program.cs:13 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected examples/Modern.EfCore.UnitOfWork.Examples/Program.cs:11 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Host/Modern.Application.Host/Program.cs:1 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
IC1 · Incompleteness & stubs · Commented-out code · ×11
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:50 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:51 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:53 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:73 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:74 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:78 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:100 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:166 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:167 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:169 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:177 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
X10 · Duplicated predicate · Duplicated predicate · ×6
  • Duplicated predicate src/WebApi/Modern.Controllers.DataStore.OData/DI/Features/GenericControllerRouteConvention.cs:30 — `!controller.ControllerType.IsGenericType || genericArgs.Length != 2 || genericArgs.Length < 2` appears character-identically in 2 files — src/WebApi/Modern.Controllers.DataStore.InMemory.OData/DI/Features/GenericControllerRouteConvention.cs, src/WebApi/Modern.Controllers.DataStore.OData/DI/Features/GenericControllerRouteConvention.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.
  • Duplicated predicate src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.cs:30 — `!controller.ControllerType.IsGenericType || genericArgs.Length != 5 || genericArgs.Length < 5` appears character-identically in 2 files — src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericControllerRouteConvention.cs, src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.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.
  • Duplicated predicate src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:32 — `leftExpression is not null && rightExpression is null` appears character-identically in 8 files — src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs, src/Repositories/Modern.Repositories.EFCore/Specifications/Base/OrSpecification.cs, src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/AndSpecification.cs, src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/OrSpecification.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.
  • Duplicated predicate src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:38 — `leftExpression is null && rightExpression is not null` appears character-identically in 8 files — src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs, src/Repositories/Modern.Repositories.EFCore/Specifications/Base/OrSpecification.cs, src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/AndSpecification.cs, src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/OrSpecification.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.
  • Duplicated predicate src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:27 — `leftExpression is null && rightExpression is null` appears character-identically in 8 files — src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs, src/Repositories/Modern.Repositories.EFCore/Specifications/Base/OrSpecification.cs, src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/AndSpecification.cs, src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/OrSpecification.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.
  • Duplicated predicate src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.cs:37 — `x.CreateRequestType == genericArgs[0] && x.UpdateRequestType == genericArgs[1] && x.EntityDtoType == genericArgs[2] && x.EntityDboType == ge…` appears character-identically in 2 files — src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericControllerRouteConvention.cs, src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.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.
D19 · Documentation Quality · Documentation · ×3
  • Documentation: no project overview src/WebApi/Modern.Controllers.DataStore.InMemory/README.md — The README says nothing about what the project is or does; it only states how to install and register an In Memory controller without explaining its purpose. Add a one-line overview stating that this directory provides generic CRUD controllers for in-memory data stores.
  • Documentation: no project overview src/WebApi/Modern.Controllers.DataStore.OData/README.md — The README says nothing about what the project is or does; it only states how to install and register an OData controller without explaining its purpose. Add a one-line overview stating that this directory provides generic OData controllers for data stores.
  • Documentation: no project overview src/WebApi/Modern.Controllers.DataStore/README.md — The README says nothing about what the project is or does; it only states how to install and register a Controller without explaining its purpose. Add a one-line overview stating that this directory provides generic CRUD controllers for data stores.
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file src/Services/Modern.Services.DataStore.InMemory/ModernInMemoryService.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file src/Services/Modern.Services.DataStore/ModernService.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D12 · Dependency Hygiene · Outdated · ×2
  • Outdated: Mapster src/CQRS/Modern.CQRS.DataStore.Cached/Modern.CQRS.DataStore.Cached.csproj:26 — Mapster 7.4.0 → 10.0.13 available (referenced by Modern.Services.DataStore).
  • Outdated: coverlet.collector tests/IntegrationTests/Modern.Cache.InMemory.Tests.Integration/Modern.Cache.InMemory.Tests.Integration.csproj:21 — coverlet.collector 6.0.2 → 10.1.0 available (referenced by Modern.Repositories.EFCore.Tests.Integration).
D18 · Solution Shape · Shell project · ×2
  • Shell project: Modern.CQRS.DataStore.InMemory src/CQRS/Modern.CQRS.DataStore.InMemory/Modern.CQRS.DataStore.InMemory.csproj — `Modern.CQRS.DataStore.InMemory` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
  • Shell project: Modern.CQRS.DataStore.InMemory.Abstractions src/CQRS/Modern.CQRS.DataStore.InMemory.Abstractions/Modern.CQRS.DataStore.InMemory.Abstractions.csproj — `Modern.CQRS.DataStore.InMemory.Abstractions` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
D24 · Comment Value · redundant comment · ×2
  • redundant comment src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:102 — "Usings" — delete - generated block comment restating the usings section
  • redundant comment src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:90 — "Class" — delete - generated marker on empty sb.AppendLine()
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IModernServiceCache<TEntity, TId> (17 members) src/Services/Modern.Services.DataStore.InMemory.Abstractions/Cache/IModernServiceCache.cs:11 — `IModernServiceCache<TEntity, TId>` declares 17 members under just 13 distinct name(s): `AddOrUpdateAsync`, `AddOrUpdateAsync`, `DeleteAsync`, `DeleteAsync`, `ClearAsync`, `GetByIdAsync`, `TryGetByIdAsync`, `TryGetManyAsync`, `GetAllAsync`, `CountAsync`, `CountAsync`, `ExistsAsync`, `FirstOrDefaultAsync`, `SingleOrDefaultAsync`, `WhereAsync`, `WhereAsync`, `AsEnumerable`. 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. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D21 · Naming Consistency · The namespace containing the `EntityIncludeQuery` type is misspelled as `Infrastracture` (missing 't') in the fully qualified names. This typo is consistent across multiple usages but represents a spelling error in the codebase's vocabulary. · ×1
  • The namespace containing the `EntityIncludeQuery` type is misspelled as `Infrastracture` (missing 't') in the fully qualified names. This typo is consistent across multiple usages but represents a spelling error in the codebase's vocabulary. — Rename namespace `Modern.Repositories.Abstractions.Infrastracture` to `Modern.Repositories.Abstractions.Infrastructure` and update all references to `EntityIncludeQuery`. (symbols: Modern.Repositories.Abstractions.Infrastracture.EntityIncludeQuery<TEntity>, Modern.Repositories.EFCore.ModernEfCoreRepositoryForUnitOfWork<TDbContext, TEntity, TId>.GetAllAsync, Modern.Repositories.EFCore.ModernEfCoreRepository<TDbContext, TEntity, TId>.ExistsAsync, Modern.Repositories.LiteDB.ModernLiteDbRepository<TEntity, TId>.CountAsync, Modern.Repositories.LiteDB.Specifications.Base.Specification<TEntity>.IncludeQueries, Modern.Repositories.EFCore.Specifications.Base.Specification<TEntity>.IncludeQueries, Modern.Repositories.MongoDB.Specifications.MongoDbSpecification<TEntity>.Apply, Modern.Repositories.Abstractions.IModernQueryRepository<TEntity, TId>.WhereAsync, Modern.Repositories.Abstractions.IModernCrudRepository<TEntity, TId>.CreateAsync, Modern.Repositories.Dapper.ModernDapperRepository<TEntityMapping, TEntity, TId>.SingleOrDefaultAsync, Modern.Repositories.MongoDB.ModernMongoDbRepository<TEntity, TId>.TryGetByIdAsync)
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 100 of 100 significant files have no living knowledge — the codebase as a whole is dormant, not 100 separate risks. Counted over 100 of the 242 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 23/47 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 47, 20 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
PF1 · Benchmark discipline · No performance benchmarks · ×1
  • No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 253/304 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 — ~2.7 `!` suppressions per 1k syntax nodes — 323 suppression(s) across the 119664 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 — 98 finding(s)
D19 · Documentation Quality · XML-doc coverage · ×68
  • XML-doc coverage: Modern.Data(net8.0) src/Common/Modern.Data/Modern.Data.csproj — Modern.Data(net8.0): 100 % XML-doc coverage (5/5).
  • XML-doc coverage: Modern.Exceptions(net8.0) src/Common/Modern.Exceptions/Modern.Exceptions.csproj — Modern.Exceptions(net8.0): 100 % XML-doc coverage (24/24).
  • XML-doc coverage: Modern.Repositories.Abstractions(net8.0) src/Repositories/Modern.Repositories.Abstractions/Modern.Repositories.Abstractions.csproj — Modern.Repositories.Abstractions(net8.0): 100 % XML-doc coverage (7/7).
  • XML-doc coverage: Modern.Repositories.EFCore(net8.0) src/Repositories/Modern.Repositories.EFCore/Modern.Repositories.EFCore.csproj — Modern.Repositories.EFCore(net8.0): 99 % XML-doc coverage (138/139).
  • XML-doc coverage: Modern.Services.DataStore.Abstractions(net8.0) src/Services/Modern.Services.DataStore.Abstractions/Modern.Services.DataStore.Abstractions.csproj — Modern.Services.DataStore.Abstractions(net8.0): 100 % XML-doc coverage (3/3).
  • XML-doc coverage: Modern.Cache.Abstractions(net8.0) src/Cache/Modern.Cache.Abstractions/Modern.Cache.Abstractions.csproj — Modern.Cache.Abstractions(net8.0): 100 % XML-doc coverage (1/1).
  • XML-doc coverage: Modern.Cache.InMemory(net8.0) src/Cache/Modern.Cache.InMemory/Modern.Cache.InMemory.csproj — Modern.Cache.InMemory(net8.0): 100 % XML-doc coverage (18/18).
  • XML-doc coverage: Modern.Cache.Redis(net8.0) src/Cache/Modern.Cache.Redis/Modern.Cache.Redis.csproj — Modern.Cache.Redis(net8.0): 100 % XML-doc coverage (22/22).
  • XML-doc coverage: Modern.Services.DataStore(net8.0) src/Services/Modern.Services.DataStore/Modern.Services.DataStore.csproj — Modern.Services.DataStore(net8.0): 100 % XML-doc coverage (35/35).
  • XML-doc coverage: Modern.Services.DataStore.Cached(net8.0) src/Services/Modern.Services.DataStore.Cached/Modern.Services.DataStore.Cached.csproj — Modern.Services.DataStore.Cached(net8.0): 100 % XML-doc coverage (39/39).
  • XML-doc coverage: Modern.Services.DataStore.InMemory.Abstractions(net8.0) src/Services/Modern.Services.DataStore.InMemory.Abstractions/Modern.Services.DataStore.InMemory.Abstractions.csproj — Modern.Services.DataStore.InMemory.Abstractions(net8.0): 100 % XML-doc coverage (4/4).
  • XML-doc coverage: Modern.Services.DataStore.InMemory(net8.0) src/Services/Modern.Services.DataStore.InMemory/Modern.Services.DataStore.InMemory.csproj — Modern.Services.DataStore.InMemory(net8.0): 100 % XML-doc coverage (62/62).
  • XML-doc coverage: Modern.Controllers.DataStore(net8.0) src/WebApi/Modern.Controllers.DataStore/Modern.Controllers.DataStore.csproj — Modern.Controllers.DataStore(net8.0): 100 % XML-doc coverage (28/28).
  • XML-doc coverage: Modern.Controllers.DataStore.OData(net8.0) src/WebApi/Modern.Controllers.DataStore.OData/Modern.Controllers.DataStore.OData.csproj — Modern.Controllers.DataStore.OData(net8.0): 100 % XML-doc coverage (20/20).
  • XML-doc coverage: Modern.Controllers.DataStore.InMemory(net8.0) src/WebApi/Modern.Controllers.DataStore.InMemory/Modern.Controllers.DataStore.InMemory.csproj — Modern.Controllers.DataStore.InMemory(net8.0): 100 % XML-doc coverage (28/28).
  • XML-doc coverage: Modern.Controllers.DataStore.InMemory.OData(net8.0) src/WebApi/Modern.Controllers.DataStore.InMemory.OData/Modern.Controllers.DataStore.InMemory.OData.csproj — Modern.Controllers.DataStore.InMemory.OData(net8.0): 100 % XML-doc coverage (20/20).
  • XML-doc coverage: Modern.CQRS.DataStore.Abstractions(net8.0) src/CQRS/Modern.CQRS.DataStore.Abstractions/Modern.CQRS.DataStore.Abstractions.csproj — Modern.CQRS.DataStore.Abstractions(net8.0): 100 % XML-doc coverage (38/38).
  • XML-doc coverage: Modern.CQRS.DataStore(net8.0) src/CQRS/Modern.CQRS.DataStore/Modern.CQRS.DataStore.csproj — Modern.CQRS.DataStore(net8.0): 100 % XML-doc coverage (65/65).
  • XML-doc coverage: Modern.CQRS.DataStore.Cached(net8.0) src/CQRS/Modern.CQRS.DataStore.Cached/Modern.CQRS.DataStore.Cached.csproj — Modern.CQRS.DataStore.Cached(net8.0): 100 % XML-doc coverage (65/65).
  • XML-doc coverage: Modern.Controllers.CQRS.DataStore(net8.0) src/WebApi/Modern.Controllers.CQRS.DataStore/Modern.Controllers.CQRS.DataStore.csproj — Modern.Controllers.CQRS.DataStore(net8.0): 100 % XML-doc coverage (28/28).
  • XML-doc coverage: Modern.Repositories.Dapper(net8.0) src/Repositories/Modern.Repositories.Dapper/Modern.Repositories.Dapper.csproj — Modern.Repositories.Dapper(net8.0): 100 % XML-doc coverage (68/68).
  • XML-doc coverage: Modern.Repositories.MongoDB(net8.0) src/Repositories/Modern.Repositories.MongoDB/Modern.Repositories.MongoDB.csproj — Modern.Repositories.MongoDB(net8.0): 98 % XML-doc coverage (55/56).
  • XML-doc coverage: Modern.Repositories.LiteDB(net8.0) src/Repositories/Modern.Repositories.LiteDB/Modern.Repositories.LiteDB.csproj — Modern.Repositories.LiteDB(net8.0): 98 % XML-doc coverage (53/54).
  • XML-doc coverage: Modern.Repositories.LiteDB.Async(net8.0) src/Repositories/Modern.Repositories.LiteDB.Async/Modern.Repositories.LiteDB.Async.csproj — Modern.Repositories.LiteDB.Async(net8.0): 98 % XML-doc coverage (53/54).
  • XML-doc coverage: Modern.Controllers.SourceGenerators src/SourceGenerators/Modern.Controllers.SourceGenerators/Modern.Controllers.SourceGenerators.csproj — Modern.Controllers.SourceGenerators: 0 % XML-doc coverage (0/13).
  • + 43 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated · ×30
  • Outdated: Microsoft.EntityFrameworkCore.Relational — Microsoft.EntityFrameworkCore.Relational 10.0.2 → 10.0.13 available (referenced by Modern.Repositories.EFCore).
  • Outdated: Microsoft.Extensions.DependencyInjection.Abstractions — Microsoft.Extensions.DependencyInjection.Abstractions 10.0.2 → 10.0.13 available (referenced by Modern.Repositories.EFCore).
  • Outdated: Microsoft.Extensions.Caching.Abstractions — Microsoft.Extensions.Caching.Abstractions 10.0.2 → 10.0.13 available (referenced by Modern.Cache.InMemory).
  • Outdated: Microsoft.Extensions.Caching.Memory — Microsoft.Extensions.Caching.Memory 10.0.2 → 10.0.13 available (referenced by Modern.Cache.InMemory).
  • Outdated: Microsoft.Extensions.Options — Microsoft.Extensions.Options 10.0.2 → 10.0.13 available (referenced by Modern.Cache.InMemory).
  • Outdated: Swashbuckle.AspNetCore — Swashbuckle.AspNetCore 10.1.0 → 10.3.1 available (referenced by Modern.Application.Host).
  • Outdated: StackExchange.Redis.Extensions.AspNetCore — StackExchange.Redis.Extensions.AspNetCore 11.0.0 → 13.0.1 available (referenced by Modern.Cache.Redis).
  • Outdated: StackExchange.Redis.Extensions.Core — StackExchange.Redis.Extensions.Core 11.0.0 → 13.0.1 available (referenced by Modern.Cache.Redis).
  • Outdated: StackExchange.Redis.Extensions.Newtonsoft — StackExchange.Redis.Extensions.Newtonsoft 11.0.0 → 13.0.1 available (referenced by Modern.Cache.Redis).
  • Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 10.0.2 → 10.0.13 available (referenced by Modern.Services.DataStore).
  • Outdated: Microsoft.AspNetCore.JsonPatch — Microsoft.AspNetCore.JsonPatch 10.0.2 → 10.0.13 available (referenced by Modern.Controllers.DataStore).
  • Outdated: Microsoft.AspNetCore.OData — Microsoft.AspNetCore.OData 9.4.1 → 9.5.0 available (referenced by Modern.Controllers.DataStore.OData).
  • Outdated: MediatR — MediatR 12.5.0 → 14.2.0 available (referenced by Modern.CQRS.DataStore).
  • Outdated: Dapper — Dapper 2.1.66 → 2.1.89 available (referenced by Modern.Repositories.Dapper).
  • Outdated: MongoDB.Driver — MongoDB.Driver 3.6.0 → 3.12.0 available (referenced by Modern.Repositories.MongoDB).
  • Outdated: FluentAssertions — FluentAssertions 6.12.1 → 8.11.0 available (referenced by Modern.Repositories.EFCore.Tests.Integration).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.11.1 → 18.11.0 available (referenced by Modern.Repositories.EFCore.Tests.Integration).
  • Outdated: Testcontainers — Testcontainers 4.0.0 → 4.16.0 available (referenced by Modern.Repositories.EFCore.Tests.Integration).
  • Outdated: xunit — xunit 2.6.2 → 2.9.3 available (referenced by Modern.Repositories.EFCore.Tests.Integration).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 2.5.4 → 4.0.1 available (referenced by Modern.Repositories.EFCore.Tests.Integration).
  • Outdated: Moq — Moq 4.16.1 → 4.21.0 available (referenced by Modern.Services.DataStore.Cached.Tests.Unit).
  • Outdated: Microsoft.CodeAnalysis.Analyzers — Microsoft.CodeAnalysis.Analyzers 3.3.4 → 5.9.0 available (referenced by Modern.Controllers.SourceGenerators).
  • Outdated: Microsoft.CodeAnalysis.CSharp — Microsoft.CodeAnalysis.CSharp 4.3.0 → 5.9.0 available (referenced by Modern.Controllers.SourceGenerators).
  • Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 10.0.2 → 10.0.13 available (referenced by Modern.LiteDb.Examples).
  • Outdated: Microsoft.Extensions.Configuration — Microsoft.Extensions.Configuration 10.0.2 → 10.0.13 available (referenced by Modern.MongoDb.Examples).
  • + 5 more in this group — see findings.md.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4142f15a98d64eb4a14b8b44fe430bc8/history.json --exit-code 0 --source .0artifacts/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-4142f15a98d64eb4a14b8b44fe430bc8/tree.json --exit-code 0 --source .0artifacts/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 .6artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
D31 · IaC & Container Securitytrivy—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.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

Run 01a16196-78b6-7a30-b196-455afe39ea19 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 1 · Warnings: 334 · Recommendations: 152 · Info: 98 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 03:10 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md