Public report — Modern, published 3 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
139findings with an exact file:lineof 163 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
51/97dimensions across the health lenses17966 LoC · 82 projects — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
anton-martyniuk/Modern carries serious risk (50%). Several issues below can materially affect reliability, security, or the cost of change and warrant near-term attention.
It is strongest in Code Health (91%) — the code is clean and low-risk to change. Security (89%) is solid too.
The area that most needs attention is Readiness (31%) — operating, monitoring and recovering the system safely is harder. Maturity (49%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); Extend structured logging across the projects you operate (Observability); Record significant decisions one document per decision (Architecture documentation).
For scale: Small (~17,966 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.
Encouragingly, the gaps are in documentation and release process — not in the code's correctness, structure or security, which are strong. They're low-risk to close, and doing so would lift the grade without re-engineering anything that already works.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
This codebase represents roughly ~0.1 person-years of build effort (about ~€20,000 to rebuild). Its weakest lens is Readiness at 31% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — service/app, CQRS × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Add a CI workflow that builds and runs the test suite on every push/PR.
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with ModernEfCoreRepositoryWithFactory.cs, ModernEfCoreRepository.cs, ModernCachedService.cs.
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.
Value concentrated against a weak lens · High · Value at risk
This is a Small asset (~0.1 person-years to rebuild), and its weakest lens is Readiness at 31%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a CI workflow that builds and runs the test suite on every push/PR.
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.
Architecture — module dependency matrix
87 modules, 101 dependencies — every dependency points down the layering, so there are no cycles. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
At a glance — Code Health · 91% · Adequate · gated by D18
First, establish a CI/CD pipeline to automatically build and test every change. Next, improve observability by implementing structured logging and diagnostics seams across all services. Then, document key architectural decisions in a dedicated folder to preserve design context. After that, remove the three largest orphaned files to improve code freshness. Finally, add a quick-start section to the root README to help new contributors get started.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a CI workflow that builds and runs the test suite on every push/PR.
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with ModernEfCoreRepositoryWithFactory.cs, ModernEfCoreRepository.cs, ModernCachedService.cs.
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.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
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. 49 of 51 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — 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 — 51 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 139 of 163 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D24 Comment Value — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
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 (jscpd) — 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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
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.
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.
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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: 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 (4): D19, D20, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These 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.
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.
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.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.2 / 10Exemplary✓ 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.
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.
+ 17 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with ModernService.cs (4), GetCountAllQueryHandler.cs, GetCountQueryHandler.cs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 6 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with EfCoreQueryProvider.cs (2), EfCoreSpecification.cs, GetFirstOrDefaultQueryHandler.cs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with EfCoreQueryProvider.cs, GenericTypeControllerFeatureProvider.cs, ModernLiteDbRepository.cs. — One of this dimension's main actionable groups (6 warning-level).
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.
Do you agree with this assessment?
D5 · Coupling8.7 / 10Strong✓ 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.
Resolve the 13 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (13 warning-level).
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.
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.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Stand up a CI pipeline, then gate Code Coverage 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.
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.
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.
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.
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.
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.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape3.5 / 10Weak✓ 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.
Resolve the 11 Shell project finding(s) in Solution Shape — start with Modern.CQRS.DataStore.InMemory.csproj, Modern.CQRS.DataStore.InMemory.Abstractions.csproj, Modern.Repositories.EFCore.Tests.Integration.csproj. — One of this dimension's main actionable groups (11 recommendation-level).
Resolve the 1 Monorepo finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Thin analysable surface across projects finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
The 'What is Modern?' section gives a strong description of what the project is and its components, plus an outline table of contents. The README files are mostly well written with concrete installation commands (e.g. Nuget package URLs) for each component type, but there is no dedicated Roadmap or Usage document and only one README file covers the CQRS data-store source generators (Modern.CQRS.DataStore.SourceGenerators).
The single controller README explains how to register controllers but does not cover usage of OData controllers or the OData-specific repository types.WebApi/Modern.Controllers.DataStore/README.md
The CQRS data-store in-memory abstraction is referenced but the README does not show how to register or use it.WebApi/Modern.CQRS.DataStore.InMemory.Abstractions/README.md
Resolve the 1 The single controller README explains how to register controllers but… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 The CQRS data-store in-memory abstraction is referenced but the README… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
1 naming inconsistencies across 200 sampled symbols.
Typo in namespace 'Infrastracture' (missing 't') in the 'EntityIncludeQuery' definition, while other query-related types use 'Query' or 'Infrastructure' correctly spelled.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
0 of 57 projects flagged as possibly oversized/incoherent.
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md.
Do you agree with this assessment?
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.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
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
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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
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.
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.
Largest orphaned file · ×3src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs
Dormant codebase
What to do
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with ModernEfCoreRepositoryWithFactory.cs, ModernEfCoreRepository.cs, ModernCachedService.cs. — One of this dimension's main actionable groups (3 recommendation-level).
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.
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; coupling through a build step, config, or non-source file isn't seen.
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.
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.
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 — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
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.
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.
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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
`IModernServiceCache<TEntity, TId>` declares 17 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IModernServiceCache.cs:11
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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.
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.
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.
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×11) — ServicesExtensions.cs:50, ServicesExtensions.cs:51, 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.
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.
Add a 'Testing' section to the root README — 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 40 of 57 project(s) that lack one — worth up to 1.4 pts.
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 `NNNN-title.md` documents 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/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
P2 · Observability4.8 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 8/31 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 31, 1 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.
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 (it analyses VB.NET too), or a 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 to do
Run what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a 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.
Readiness · Performance — Whether the library 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 — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
No benchmark suite was found. 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).
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.
Raise allocation-aware density on the hot paths — currently 77 use(s) across 19,780 production line(s) (~3.9/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code keeps its host responsive — a library awaits with ConfigureAwait(false) (so it never captures and stalls the host's context) and avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a library with ≥5 awaits — the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
What to do
Add security response headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) — defense in depth, even when a reverse proxy could set them.
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.
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.
Only 249/273 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. (×24) — ModernController.cs:45, ModernController.cs:86, ModernController.cs:104, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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.
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. Deterministic.
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.
~1.5 `!` suppressions per 1k syntax nodes — 123 suppression(s) across the 79947 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Not included — 46 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 vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — Partial workspace load — the web/host project 'Modern.EfCore.UnitOfWork.Examples' present on disk did not load into the C# workspace (it failed to build/restore and was silently dropped), so its authorization signals were never scanned. The surviving documents carry no evidence for this control, but absence of evidence in an INCOMPLETE document set is not evidence the control is missing — the relevant middleware/attributes most plausibly live in the dropped project. This dimension is therefore Not-evidenced (excluded from the score) rather than asserting a confident negative. Restore/build that project (see diagnostics.md) so it loads and the dimension can be scored.
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-maintainer — knowledge-concentration (bus factor) risk
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D24 Comment Value — LLM evaluation failed
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — 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 for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); 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.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D9 Test Distribution — Tests outside the analyzed solution
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this check 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; 72 CQRS handler(s)
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
P12 CI test-gate honesty — no CI workflow found
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
P7 Outbound HTTP resilience — no outbound HTTP usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
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.
Off the main sequence: Modern.Data(net8.0) — Modern.Data(net8.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 19 project(s), so it's rigid to change.
Off the main sequence: Modern.Exceptions(net8.0) — Modern.Exceptions(net8.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 22 project(s), so it's rigid to change.
Off the main sequence: Modern.Controllers.Attributes — Modern.Controllers.Attributes: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Modern.Repositories.EFCore.Attributes — Modern.Repositories.EFCore.Attributes: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Modern.Repositories.MongoDB.Attributes — Modern.Repositories.MongoDB.Attributes: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Modern.Repositories.Dapper.Attributes — Modern.Repositories.Dapper.Attributes: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Modern.Repositories.LiteDB.Async.Attributes — Modern.Repositories.LiteDB.Async.Attributes: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Modern.Repositories.LiteDB.Attributes — Modern.Repositories.LiteDB.Attributes: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Modern.Services.DataStore.Attributes — Modern.Services.DataStore.Attributes: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Modern.Services.DataStore.Cached.Attributes — Modern.Services.DataStore.Cached.Attributes: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Modern.Services.DataStore.InMemory.Attributes — Modern.Services.DataStore.InMemory.Attributes: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Modern.Controllers.InMemory.Attributes — Modern.Controllers.InMemory.Attributes: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Modern.Extensions.Microsoft.DependencyInjection(net8.0) — 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.
Duplicated block (13 lines × 2) src/Services/Modern.Services.DataStore/ModernService.cs:154— src/Services/Modern.Services.DataStore/ModernService.cs:154-166 | src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:203-215 — 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/ModernService.cs:154` 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 (13 lines × 2) src/Services/Modern.Services.DataStore/ModernService.cs:241— src/Services/Modern.Services.DataStore/ModernService.cs:241-253 | src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:290-302 — 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/ModernService.cs:241` 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 (13 lines × 2) src/Services/Modern.Services.DataStore/ModernService.cs:263— src/Services/Modern.Services.DataStore/ModernService.cs:263-275 | src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:312-324 — 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/ModernService.cs:263` 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 (13 lines × 2) src/Services/Modern.Services.DataStore/ModernService.cs:285— src/Services/Modern.Services.DataStore/ModernService.cs:285-297 | src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:334-346 — 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/ModernService.cs:285` 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 (13 lines × 2) src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountAllQueryHandler.cs:54— src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountAllQueryHandler.cs:54-66 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountAllQueryHandler.cs:54-66 — 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/QueryHandlers/GetCountAllQueryHandler.cs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountQueryHandler.cs:59— src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetCountQueryHandler.cs:59-71 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetCountQueryHandler.cs:59-71 — 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/QueryHandlers/GetCountQueryHandler.cs:59` 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.
Duplicated block (13 lines × 2) src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetExistsQueryHandler.cs:59— src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetExistsQueryHandler.cs:59-71 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetExistsQueryHandler.cs:59-71 — 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/QueryHandlers/GetExistsQueryHandler.cs:59` 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.
Duplicated block (13 lines × 2) src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:407— src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:407-419 | src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:428-440 — 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: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 (13 lines × 2) src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:116— src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:116-128 | src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:151-163 — 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.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:116` 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 (13 lines × 2) src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:38— src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:38-50 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:38-50 — 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 54 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 × 2) src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:33— src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:33-43 | src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:34-44 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) src/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 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:57` 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.
Duplicated block (11 lines × 2) src/Repositories/Modern.Repositories.EFCore/Specifications/EfCoreSpecification.cs:35— src/Repositories/Modern.Repositories.EFCore/Specifications/EfCoreSpecification.cs:35-45 | src/Repositories/Modern.Repositories.MongoDB/Specifications/MongoDbSpecification.cs:30-42 — 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 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.
Duplicated block (11 lines × 2) src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:57— src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:57-67 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:57-67 — 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/QueryHandlers/GetFirstOrDefaultQueryHandler.cs:57` 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/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:58— src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:58-68 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:58-68 — 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/QueryHandlers/GetSingleOrDefaultQueryHandler.cs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWhereQueryHandler.cs:57— src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWhereQueryHandler.cs:57-67 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWhereQueryHandler.cs:57-67 — 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/QueryHandlers/GetWhereQueryHandler.cs:57` 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/Query/EfCoreQueryProvider.cs:114— src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:114-122 | src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:117-125 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:114` 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. 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 (9 lines × 2) src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericTypeControllerFeatureProvider.cs:34— src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericTypeControllerFeatureProvider.cs:34-42 | src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericTypeControllerFeatureProvider.cs:34-42 — 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/WebApi/Modern.Controllers.DataStore/DI/Features/GenericTypeControllerFeatureProvider.cs:34` 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.
Duplicated block (9 lines × 2) src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:79— src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:79-87 | src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:132-140 — 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:79` 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.LiteDB.Async/ModernLiteDbAsyncRepository.cs:79— src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:79-87 | src/Repositories/Modern.Repositories.LiteDB.Async/ModernLiteDbAsyncRepository.cs:130-138 — 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:79` 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/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:101— src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:101-109 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:101-109 — 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 54 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 (9 lines × 2) src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:85— src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:85-93 | src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:88-96 — 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.
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.
Duplicated block (20 lines × 2) src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:25— src/Repositories/Modern.Repositories.EFCore/Specifications/Base/AndSpecification.cs:25-44 | src/Repositories/Modern.Repositories.EFCore/Specifications/Base/OrSpecification.cs:25-44 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (20 lines × 2) src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/AndSpecification.cs:25— src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/AndSpecification.cs:25-44 | src/Repositories/Modern.Repositories.MongoDB/Specifications/Base/OrSpecification.cs:25-44 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (20 lines × 2) src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/AndSpecification.cs:25— src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/AndSpecification.cs:25-44 | src/Repositories/Modern.Repositories.LiteDB/Specifications/Base/OrSpecification.cs:25-44 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (20 lines × 2) src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/AndSpecification.cs:25— src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/AndSpecification.cs:25-44 | src/Repositories/Modern.Repositories.LiteDB.Async/Specifications/Base/OrSpecification.cs:25-44 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:78— src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:78-87 | src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:80-89 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:78` 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.
Duplicated block (10 lines × 2) src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:98— src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:98-107 | src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProviderWithFactory.cs:101-110 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/Query/EfCoreQueryProvider.cs:98` 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.
Duplicated block (10 lines × 2) src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs:85— src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs:85-94 | src/SourceGenerators/Modern.Controllers.SourceGenerators/EntityRequestGenerator.cs:102-111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:109— src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:109-118 | src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:109-118 — 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.
TooManyMethods: ModernEfCoreRepositoryWithFactory src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:0— TooManyMethods — 349 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. 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:0— TooManyMethods — 330 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. 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:0— TooManyMethods — 272 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. 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.
Duplicated block (15 lines × 2) src/Services/Modern.Services.DataStore/ModernService.cs:175— src/Services/Modern.Services.DataStore/ModernService.cs:175-189 | src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:224-238 — 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/ModernService.cs:175` 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/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWherePagedQueryHandler.cs:68— src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetWherePagedQueryHandler.cs:68-82 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetWherePagedQueryHandler.cs:68-82 — 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/QueryHandlers/GetWherePagedQueryHandler.cs:68` 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.
Duplicated block (15 lines × 2) src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:26— src/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:26-40 | src/SourceGenerators/Modern.Controllers.InMemory.SourceGenerators/ModernInMemoryControllerGenerator.cs:26-40 — 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/SourceGenerators/Modern.Controllers.SourceGenerators/ModernControllerGenerator.cs:26` 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/Services/Modern.Services.DataStore/ModernService.cs:200— src/Services/Modern.Services.DataStore/ModernService.cs:200-213 | src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:249-262 — 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/ModernService.cs:200` 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.
Duplicated block (14 lines × 2) src/Services/Modern.Services.DataStore/ModernService.cs:221— src/Services/Modern.Services.DataStore/ModernService.cs:221-234 | src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:270-283 — 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/ModernService.cs:221` 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.
Duplicated block (14 lines × 2) src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:415— src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:415-428 | src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:437-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.LiteDB/ModernLiteDbRepository.cs:415` 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.
Duplicated block (12 lines × 2) src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:28— src/Services/Modern.Services.DataStore/DI/ServicesExtensions.cs:28-39 | src/Services/Modern.Services.DataStore.Cached/DI/ServicesExtensions.cs:38-49 — 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/DI/ServicesExtensions.cs:28` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetAllQueryHandler.cs:55— src/CQRS/Modern.CQRS.DataStore/QueryHandlers/GetAllQueryHandler.cs:55-66 | src/CQRS/Modern.CQRS.DataStore.Cached/QueryHandlers/GetAllQueryHandler.cs:55-66 — 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/QueryHandlers/GetAllQueryHandler.cs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 5) src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:66— src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:66-70 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:75-79 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:84-88 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:93-97 | src/CQRS/Modern.CQRS.DataStore/DI/ServicesExtensions.cs:102-106 — 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.
Duplicated block (5 lines × 5) src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:66— src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:66-70 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:75-79 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:84-88 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:93-97 | src/CQRS/Modern.CQRS.DataStore.Cached/DI/ServicesExtensions.cs:102-106 — 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.
Monorepo: only 1 of 2 solutions was scored — This repository contains 2 .NET solutions, but a scan analyzes ONE. Every score, lens, and finding here reflects only `src/Modern.sln` — the other 1 (`examples/Modern.Examples.sln`) were not analyzed and are not represented in the headline. To cover them, scan each solution as its own target and group them in a Solution or Product for a portfolio roll-up. If a secondary solution is an archived or vendored tree, declare it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — to exclude it from discovery the same way generated code is.
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.
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.
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.notable[4].comment | LineNumber: 0 | BytePositionInLine: 922.
Duplicated block (26 lines × 3) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:636— src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:636-661 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:543-568 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:664-689 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:636` 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 (23 lines × 5) src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.cs:38— src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.cs:38-60 | src/WebApi/Modern.Controllers.DataStore.OData/DI/Features/GenericControllerRouteConvention.cs:37-59 | src/WebApi/Modern.Controllers.DataStore.InMemory/DI/Features/GenericControllerRouteConvention.cs:38-60 | src/WebApi/Modern.Controllers.DataStore.InMemory.OData/DI/Features/GenericControllerRouteConvention.cs:37-59 | src/WebApi/Modern.Controllers.CQRS.DataStore/DI/Features/GenericControllerRouteConvention.cs:38-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/WebApi/Modern.Controllers.DataStore/DI/Features/GenericControllerRouteConvention.cs:38` 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.
Duplicated block (17 lines × 2) src/Services/Modern.Services.DataStore/ModernService.cs:314— src/Services/Modern.Services.DataStore/ModernService.cs:314-330 | src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs:363-379 — 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/ModernService.cs:314` 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.
Duplicated block (16 lines × 2) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:317— src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:317-332 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:226-241 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:317` 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 × 4) src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:23— src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:23-37 | src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:22-36 | src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:23-37 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:23-37 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.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.
Duplicated block (15 lines × 3) src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:23— src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:23-37 | src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:23-37 | src/SourceGenerators/Modern.Services.DataStore.InMemory.SourceGenerators/ModernInMemoryServiceGenerator.cs:23-37 — 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/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.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.
Duplicated block (11 lines × 3) src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:762— src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:762-772 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryForUnitOfWork.cs:667-677 | src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs:790-800 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs:762` 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 × 3) src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:91— src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:91-99 | src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:90-98 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:90-98 — 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.
Duplicated block (8 lines × 5) src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:70— src/SourceGenerators/Modern.Repositories.EFCore.SourceGenerators/ModernEfCoreRepositoryGenerator.cs:70-77 | src/SourceGenerators/Modern.Repositories.MongoDB.SourceGenerators/ModernMongoDbRepositoryGenerator.cs:67-74 | src/SourceGenerators/Modern.Repositories.Dapper.SourceGenerators/ModernDapperRepositoryGenerator.cs:58-65 | src/SourceGenerators/Modern.Repositories.LiteDB.Async.SourceGenerators/ModernLiteDbAsyncRepositoryGenerator.cs:67-74 | src/SourceGenerators/Modern.Repositories.LiteDB.SourceGenerators/ModernLiteDbRepositoryGenerator.cs:67-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. 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 (8 lines × 3) src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:57— src/SourceGenerators/Modern.Services.DataStore.SourceGenerators/ModernServiceGenerator.cs:57-64 | src/SourceGenerators/Modern.Services.DataStore.Cached.SourceGenerators/ModernCachedServiceGenerator.cs:57-64 | src/SourceGenerators/Modern.Services.DataStore.InMemory.SourceGenerators/ModernInMemoryServiceGenerator.cs:57-64 — 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.
Duplicated block (8 lines × 2) src/Repositories/Modern.Repositories.Dapper/Providers/OracleQueryProvider.cs:24— src/Repositories/Modern.Repositories.Dapper/Providers/OracleQueryProvider.cs:24-31 | src/Repositories/Modern.Repositories.Dapper/Providers/PostgresQueryProvider.cs:24-31 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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:24` 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.
Duplicated block (6 lines × 4) src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.cs:20— src/Repositories/Modern.Repositories.Dapper/Providers/MySqlQueryProvider.cs:20-25 | src/Repositories/Modern.Repositories.Dapper/Providers/PostgresQueryProvider.cs:18-23 | src/Repositories/Modern.Repositories.Dapper/Providers/SqliteQueryProvider.cs:18-23 | src/Repositories/Modern.Repositories.Dapper/Providers/SqlServerQueryProvider.cs:18-23 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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:20` 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.
Duplicated block (5 lines × 3) src/Repositories/Modern.Repositories.Dapper/Providers/OracleQueryProvider.cs:16— src/Repositories/Modern.Repositories.Dapper/Providers/OracleQueryProvider.cs:16-20 | src/Repositories/Modern.Repositories.Dapper/Providers/PostgresQueryProvider.cs:16-20 | src/Repositories/Modern.Repositories.Dapper/Providers/SqliteQueryProvider.cs:16-20 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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:16` 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.
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.
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.
Shell project: Modern.Repositories.EFCore.Tests.Integration tests/IntegrationTests/Modern.Repositories.EFCore.Tests.Integration/Modern.Repositories.EFCore.Tests.Integration.csproj— `Modern.Repositories.EFCore.Tests.Integration` contributes only 1 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Modern.Repositories.MongoDB.Tests.Integration tests/IntegrationTests/Modern.Repositories.MongoDB.Tests.Integration/Modern.Repositories.MongoDB.Tests.Integration.csproj— `Modern.Repositories.MongoDB.Tests.Integration` contributes only 1 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Modern.Repositories.Dapper.Tests.Integration tests/IntegrationTests/Modern.Repositories.Dapper.Tests.Integration/Modern.Repositories.Dapper.Tests.Integration.csproj— `Modern.Repositories.Dapper.Tests.Integration` contributes only 1 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.Cached.Tests.Unit tests/UnitTests/Modern.CQRS.DataStore.Cached.Tests.Unit/Modern.CQRS.DataStore.Cached.Tests.Unit.csproj— `Modern.CQRS.DataStore.Cached.Tests.Unit` contributes only 1 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.Tests.Unit tests/UnitTests/Modern.CQRS.DataStore.InMemory.Tests.Unit/Modern.CQRS.DataStore.InMemory.Tests.Unit.csproj— `Modern.CQRS.DataStore.InMemory.Tests.Unit` contributes only 1 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.Tests.Unit tests/UnitTests/Modern.CQRS.DataStore.Tests.Unit/Modern.CQRS.DataStore.Tests.Unit.csproj— `Modern.CQRS.DataStore.Tests.Unit` contributes only 1 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Modern.Services.DataStore.Cached.Tests.Unit tests/UnitTests/Modern.Services.DataStore.Cached.Tests.Unit/Modern.Services.DataStore.Cached.Tests.Unit.csproj— `Modern.Services.DataStore.Cached.Tests.Unit` contributes only 3 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Modern.Services.DataStore.InMemory.Tests.Unit tests/UnitTests/Modern.Services.DataStore.InMemory.Tests.Unit/Modern.Services.DataStore.InMemory.Tests.Unit.csproj— `Modern.Services.DataStore.InMemory.Tests.Unit` contributes only 1 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Modern.Services.DataStore.Tests.Unit tests/UnitTests/Modern.Services.DataStore.Tests.Unit/Modern.Services.DataStore.Tests.Unit.csproj— `Modern.Services.DataStore.Tests.Unit` contributes only 3 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
D34 · Knowledge Freshness· Largest orphaned file · ×3
Largest orphaned file src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepositoryWithFactory.cs— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file src/Repositories/Modern.Repositories.EFCore/ModernEfCoreRepository.cs— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file src/Services/Modern.Services.DataStore.Cached/ModernCachedService.cs— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Thin analysable surface across projects — 11 project(s) carry only a thin slice of real code (e.g. `Modern.Application.Host` with 11 significant line(s)). The mean analysable-surface weight is 19 %, lowering Solution Shape by about 6.45 point(s). Consolidate thin projects or grow them into substantial, well-scoped assemblies.
D19 · Documentation Quality· The single controller README explains how to register controllers but does not cover usage of OData controllers or the OData-specific repository types. · ×1
The single controller README explains how to register controllers but does not cover usage of OData controllers or the OData-specific repository types. WebApi/Modern.Controllers.DataStore/README.md— Add a short Usage section covering OData query syntax and which repositories are used for OData.
D19 · Documentation Quality· The CQRS data-store in-memory abstraction is referenced but the README does not show how to register or use it. · ×1
The CQRS data-store in-memory abstraction is referenced but the README does not show how to register or use it. WebApi/Modern.CQRS.DataStore.InMemory.Abstractions/README.md— Document the DI registration and a minimal constructor example for Modern.CQRS.DataStore.InMemory.
No ADRs found — No ADRs found at common paths; consider documenting architectural decisions in Docs/ADL/ or similar.
D21 · Naming Consistency· Typo in namespace 'Infrastracture' (missing 't') in the 'EntityIncludeQuery' definition, while other query-related types use 'Query' or 'Infrastructure' correctly spelled. · ×1
Typo in namespace 'Infrastracture' (missing 't') in the 'EntityIncludeQuery' definition, while other query-related types use 'Query' or 'Infrastructure' correctly spelled. — Correct the typo in the namespace from 'Infrastracture' to 'Infrastructure'. (symbols: Modern.Repositories.Abstractions.Infrastracture.EntityIncludeQuery<TEntity>, Modern.Repositories.EFCore.Query.IDbQueryProvider, Modern.Repositories.EFCore.Query.EfCoreQueryProviderWithFactory<TDbContext, TEntity>.Execute, Modern.Repositories.EFCore.Query.EfCoreQueryProvider<TDbContext, TEntity>.ExpressionQueryableSourceModifierVisitor)
D23 · Boundary Type-Coupling· Bounded contexts not declared · ×1
Bounded contexts not declared — At 17966 LoC spread over 82 projects the codebase is both large and multi-module, so explicit bounded contexts are needed. 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"]`.
Dormant codebase — 100 of 100 significant files have no living knowledge — the codebase as a whole is dormant, not 100 separate risks. Re-engage owners or document before change.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
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.
dotnet: not applicable — 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 for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
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.
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.
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.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
0
—
Run 019fc874-0a62-7c88-ae66-c492b87b3323 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Warnings: 92 · Recommendations: 22 · Info: 49 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 03-08-2026 @ 16:27 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.