.NET document DB and event store on PostgreSQL
Public report — marten, published 20 Jun 2026. Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version; ask the repo owner for the full report.
Watchdogby Canine Development 20-06-2026 @ 05:22 UTC Public
Code Health Audit

JasperFx/marten

No regression single-maintainerbounded contexts not declared
54% Adequate
CriticalWeakAdequateStrongExemplary
lower third — near Weak
Event-Driven 100% Exemplary Architecture 83% Strong Code Health 71% Strong Maturity 70% Strong Performance 68% Adequate Readiness 54% Adequate Security 43% Weak

Large · 173,789 LoC · 90 projects · rebuild ~7.0 person-years · weakest lens: Security (43%)

Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸

57/57dimensions tool-verifieddeterministic · confidence 1.0
1777findings with an exact file:lineof 1843 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
57/96dimensions across the health lenses173789 LoC · 90 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.

JasperFx/marten is in a workable but fragile state (54%). It is not in crisis, but it carries material risk that makes change slower and incidents harder to contain if left unaddressed.

It is strongest in Event-Driven (100%) — its messaging keeps components properly decoupled. Architecture (83%) is solid too.

The area that most needs attention is Security (43%) — exposure to security and compliance incidents is elevated. Readiness (54%) is the next concern — operating, monitoring and recovering the system safely is harder.

Leadership focus, highest impact first: Encrypt sensitive data at rest (ASP.NET Core Data Protection /… (Data Protection); authorization at every handler (Access Controls); security response headers (Content-Security-Policy (Web-Security Posture).

For scale: Large (~173,789 production lines); rebuilding it from scratch would take roughly ~7.0 person-years (~4–14 engineers). Approximate, ±~30%.

It builds on a genuinely strong Event-Driven foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.

Code Health 71% Strong Architecture 83% Strong Maturity 70% Strong Readiness 54% Adequate · gated by P3 Security 43% Weak · gated by D36, D38, C1, C2 Event-Driven 100% ★ Exemplary Performance 68% Adequate
How the score is built — each lens's share of the headline Width 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.
Security 43% · 46% weightReadiness 54% · 25% weightPerformance 68% · 14% weightMaturity 70% · 8% weightCode Health 71% · 4% weightArchitecture 83% · 2% weightEvent-Driven 100% · 1% weight

Raise Security 43 → 70 (the Healthy floor) ⇒ headline 54 → ~63.

Code composition — where the lines go
Business logic 10%Plumbing 27%Tests 62%Analyzers 0%
Rebuild cost & value ~ Modeled — €340,000–€1,700,000
Cost to rebuild€340,000–€1,700,000 (3.4–10.7 person-years (5,631–17,978 h), ~4–14 engineers)
Domain complexityVery high — harder problems cost more per line
Quality factor0.8× (at 54% quality) — the last 20% of quality is most of the work
Size & shapeLarge · 47% boilerplate · 25% straight-line · 28% branching logic

This codebase represents roughly ~7.0 person-years of build effort (about ~€1,000,000 to rebuild). Its weakest lens is Security at 43% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Very high (×2.1) — microservices, CQRS, event-driven integration, event sourcing × a 0.8× 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
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
+10.0 pts · Medium effort · Data Protection
2
Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.
+10.0 pts · Medium effort · Access Controls
3
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.
+9.4 pts · Medium effort · Web-Security Posture

Diagnosis — what's actually going on

Value concentrated against a weak lens · High · Value at risk
This is a Large asset (~7.0 person-years to rebuild), and its weakest lens is Security at 43%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
Evidence: valuation: Large, ~7.0 person-years rebuild (173,789 LoC) · weakest lens: Security 43%
→ Direct remediation budget at Security 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: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Improving trajectory · Info · Trajectory
The headline is improving steadily (+12.1 pts/run over 4 runs) — whatever you're doing is working; keep the gate.
Evidence: trajectory: +12.1 pts/run over 4 runs

Trajectory

Where this codebase is heading — something a one-shot snapshot cannot show. 54 ▲ 5 over 4 runs.

025507510019 Junnow
OverallCode HealthArchitectureMaturityReadinessSecurityEvent-DrivenPerformance

Architecture — module dependency graph

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

arch AspNetCoreWithMarten AspNetCoreWithMarten Marten Marten AspNetCoreWithMarten->Marten Marten.AspNetCore AspNetCore AspNetCoreWithMarten->Marten.AspNetCore AspNetODataWithMarten AspNetODataWithMarten AspNetODataWithMarten->Marten AspireHeadlessTripService AspireHeadlessTripService AspireHeadlessTripService->Marten AspireHost AspireHost AspireHost->AspireHeadlessTripService EventPublisher EventPublisher AspireHost->EventPublisher CommandLineRunner CommandLineRunner CommandLineRunner->Marten DcbLoadTest DcbLoadTest DcbLoadTest->Marten EventPublisher->Marten EventSourceWorker EventSourceWorker EventSourceWorker->Marten EventSourcingIntro EventSourcingIntro EventSourcingIntro->Marten Helpdesk.Api Api Helpdesk.Api->Marten Helpdesk.Api->Marten.AspNetCore Marten.AspNetCore->Marten Marten.Newtonsoft Newtonsoft Marten.Newtonsoft->Marten Marten.NodaTime NodaTime Marten.NodaTime->Marten Marten.NodaTime->Marten.Newtonsoft Marten.PostGIS PostGIS Marten.PostGIS->Marten Marten.PostGIS->Marten.Newtonsoft Marten.Testing.OtherAssembly OtherAssembly Marten.Testing.OtherAssembly->Marten Marten.Testing.ThirdAssembly ThirdAssembly Marten.Testing.ThirdAssembly->Marten MinimalAPI MinimalAPI MinimalAPI->Marten MinimalAPI->Marten.AspNetCore MultiDatabaseCommandLineRunner MultiDatabaseCommandLineRunner MultiDatabaseCommandLineRunner->Marten.Testing.OtherAssembly MultiDatabaseCommandLineRunner->Marten.Testing.ThirdAssembly TestingSupport TestingSupport TestingSupport->Marten TestingSupport->Marten.Testing.OtherAssembly TestingSupport->Marten.Testing.ThirdAssembly __more__ +15 more projects

At a glance — Code Health · 71% · Strong

The Good
D1 · .NET / C# Cyclomatic Complexity 8.2 D3 · .NET / C# God Classes 8.3 D4 · .NET / C# Code Duplication 9.8 D17 · .NET / C# Explicit Debt 9.5 D18 · .NET / C# Solution Shape 10.0 GD1 · Repo Unfinished & placeholder code 10.0 X1 · Repo Async correctness 7.8 X2 · Repo Cancellation propagation 8.7 X3 · Repo Exception handling 10.0 X4 · Repo Structured logging 10.0
The Bad
D2 · .NET / C# Cognitive Complexity 6.8 X5 · Repo Nullable reference types 6.9
The Ugly
IC1 · Repo Incompleteness & stubs 4.3

At a glance — Architecture · 83% · Strong

The Good
D5 · .NET / C# Coupling 8.9 D6 · .NET / C# Cohesion (LCOM4) 7.1 D26 · .NET / C# Project Cohesion 7.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 9.9 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.5 AX9 · Repo CQS / query purity 10.0
The Bad
AX2 · Repo Stateful singletons 6.2

At a glance — Maturity · 70% · Strong

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 M1 · Repo Documentation (README) 7.4 M3 · Repo Folder & project structure 8.0
The Bad
M2 · Repo Architecture documentation 5.0

At a glance — Readiness · 54% · Adequate · gated by P3

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 8.3 D11 · .NET / C# Test Reliability 10.0 D12 · .NET / C# Dependency Hygiene 10.0 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 7.5 P4 · Repo Deployment & Rollback 7.0 P5 · Repo DR & Backup 10.0 P7 · Repo Outbound HTTP resilience 10.0
The Bad
D8 · .NET / C# Code Coverage 5.0 P6 · Repo Release Hygiene 5.0 P8 · Repo Schema migrations 6.0
The Ugly
ED5 · Repo Idempotency 3.0 P3 · Repo Security & performance tooling 1.0

At a glance — Security · 43% · Weak · gated by D36, D38, C1, C2

The Good
D28 · .NET / C# Secrets (history) 7.0 D29 · .NET / C# Static Analysis (SAST) 10.0 D31 · .NET / C# IaC & Container Security 9.3 D33 · .NET / C# JS/npm Dependency Vulnerabilities 10.0
The Bad
S1 · Repo Web-Security Posture 6.5
The Ugly
D36 · .NET / C# Supply-chain Provenance & Signing 0.0 D38 · .NET / C# OSV Dependency Vulnerabilities 3.4 C1 · Repo Data Protection 3.0 C2 · Repo Access Controls 3.0

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

The Good
ED1 · Repo Handler temporal coupling 10.0 ED4 · Repo Outbox / dual-write 10.0

At a glance — Performance · 68% · Adequate

The Good
PF1 · Repo Benchmark discipline 7.5 PF2 · Repo Allocation hygiene 7.4
The Bad
PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A06:2021 — Vulnerable & Outdated Components21High / Critical
A02:2021 — Cryptographic Failures4High / Critical
A05:2021 — Security Misconfiguration4High / Critical

Roadmap

Top priorities: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.); Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable; 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.

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

Do thisHelpsEffortDimension
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).+10.0 ptsMediumData Protection
Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.+10.0 ptsMediumAccess Controls
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.+9.4 ptsMediumWeb-Security Posture
Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.+4.7 ptsMediumIdempotency
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+4.7 ptsMediumRelease Hygiene
Adopt EF migrations (dotnet ef migrations add + Migrate() on startup) as the explicit, versioned schema strategy — no migration mechanism was detected.+4.6 ptsMediumSchema migrations
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.+4.3 ptsMediumDeployment & Rollback
Extend structured logging to the remaining service-like projects so the whole executable surface is diagnosable in production.+4.2 ptsMediumObservability

File quality

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

FileScoreBandWorst signal
package-lock.json0.0SlopOSV Dependency Vulnerabilities: High CVE: [GHSA redacted]
src/DaemonTests/EventProjections/using_custom_projection_that_depends_on_identity_map_behavior.cs4.3MixedTest Quality: No assertions: rebuild_with_follow_up_operations_should_work
src/EventSourcingTests/Bugs/Bug_3184_Projection_named_Projection.cs4.3MixedTest Quality: No assertions: codegen_works
src/Marten/Internal/CompiledQueries/CompiledQueryPlan.cs5.1MixedCognitive Complexity: CompiledQueryPlan.MatchParameters (cognitive 22)
src/Marten/Events/Fetching/FetchNaturalKeyPlan.cs5.1MixedGod Classes: TooManyMethods: FetchNaturalKeyPlan
build/build.csproj5.3MixedExplicit Debt: NoWarnInCsproj
src/Marten/Storage/DocumentTable.cs5.5MixedCyclomatic Complexity: DocumentTable.DocumentTable.ctor (cyclomatic 16)
src/Marten/Linq/Members/DuplicatedField.cs5.5MixedCognitive Complexity: DuplicatedField.DuplicatedField.ctor (cognitive 22)
src/Marten/AdvancedOperations.cs5.5MixedCognitive Complexity: AdvancedOperations.AddMartenManagedTenantsAsync (cognitive 16)
src/Marten/Events/EventDocumentStorage.cs5.5MixedCognitive Complexity: EventDocumentStorage.ResolveAsync (cognitive 16)
src/Marten/Internal/ClosedShape/ClosedShapeInsertOperation.cs5.5MixedCode Duplication: Duplicated block (13 lines × 3)
src/Marten/MartenServiceCollectionExtensions.cs5.7MixedGod Classes: TooManyMethods: MartenServiceCollectionExtensions
src/Marten/Schema/Identity/FSharpDiscriminatedUnionIdGeneration.cs5.7MixedCode Duplication: Duplicated block (9 lines × 2)
src/Marten.SourceGeneration/Marten.SourceGeneration.csproj5.8MixedExplicit Debt: NoWarnInCsproj
docs/.vitepress/config.mts5.8MixedSecrets (history): Secret: generic-api-key
src/Marten/Linq/Parsing/SimpleExpression.cs6.0MixedExplicit Debt: TodoComment
src/Marten/Linq/SqlGeneration/SelectorStatement.cs6.0MixedExplicit Debt: HackComment
src/Marten/Events/RichEventAppender.cs6.0MixedExplicit Debt: TodoComment
src/Marten/Services/SessionOptions.cs6.0MixedExplicit Debt: TodoComment
src/Marten/Schema/DocumentMapping.cs6.0MixedExplicit Debt: TodoComment

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 57 of 57 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.7 — 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 — 57 dimensions across the health lenses
D1D2D3D4D5D6D8D9D10D11D12D13D14D15D17D18D26D28D29D31D33D36D38AX1AX10AX2AX3AX5AX6AX9C1C2ED1ED4ED5GD1IC1M1M2M3P1P2P3P4P5P6P7P8PF1PF2PF3S1X1X2X3X4X5

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

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1777 of 1843 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 019ee37b-1326-799f-b874-985d560d3e06.

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

Run transparency — what happened this run

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

  • D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
  • D32 Data Compliance (PII/GDPR) — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
  • D37 Vulnerability-disclosure Policy — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.

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 (EF migration scaffolds, *.Designer.cs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only; the generated footprint is reported separately under Solution Shape.
  • 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 suite (`dotnet test --collect`) 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.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (EF migrations, designer files, snapshots) 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.
  • 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.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (1): ED5. 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.

Dimensions

D1 · Cyclomatic Complexity8.2 / 10Strong✓ Tool-verified

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

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

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

12 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DocumentStorageDescriptorBuilder.Build at 35.

DocumentStorageDescriptorBuilder.Build (cyclomatic 35)src/Marten/Internal/ClosedShape/DocumentStorageDescriptorBuilder.cs:19
CollectionUsage.CompileGroupJoin (cyclomatic 28)src/Marten/Linq/CollectionUsage.Compilation.cs:323
StoreOptions.CreateQueryableMember (cyclomatic 24)src/Marten/StoreOptions.MemberFactory.cs:34
DropCycleCommand.Execute (cyclomatic 23)src/Marten.ScaleTesting/Commands/DropCycleCommand.cs:56
CollectionUsage.ProcessSingleValueModeIfAny (cyclomatic 22)src/Marten/Linq/CollectionUsage.Compilation.cs:811

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

What to do

  1. Resolve the 1 DocumentStorageDescriptorBuilder.Build (cyclomatic 35) finding(s) in Cyclomatic Complexity — start with DocumentStorageDescriptorBuilder.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 CollectionUsage.CompileGroupJoin (cyclomatic 28) finding(s) in Cyclomatic Complexity — start with CollectionUsage.Compilation.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 StoreOptions.CreateQueryableMember (cyclomatic 24) finding(s) in Cyclomatic Complexity — start with StoreOptions.MemberFactory.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity6.8 / 10Adequate✓ Tool-verified

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

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

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

45 method(s) exceeded the cognitive complexity threshold of 15; the worst was DocumentStorageDescriptorBuilder.Build at 47.

DocumentStorageDescriptorBuilder.Build (cognitive 47)src/Marten/Internal/ClosedShape/DocumentStorageDescriptorBuilder.cs:19
CollectionUsage.CompileGroupJoin (cognitive 43)src/Marten/Linq/CollectionUsage.Compilation.cs:323
DropCycleCommand.Execute (cognitive 31)src/Marten.ScaleTesting/Commands/DropCycleCommand.cs:56
CollectionUsage.CompileGroupBy (cognitive 28)src/Marten/Linq/CollectionUsage.Compilation.cs:614
StoreOptions.CreateQueryableMember (cognitive 28)src/Marten/StoreOptions.MemberFactory.cs:34

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

What to do

  1. Resolve the 1 DocumentStorageDescriptorBuilder.Build (cognitive 47) finding(s) in Cognitive Complexity — start with DocumentStorageDescriptorBuilder.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 CollectionUsage.CompileGroupJoin (cognitive 43) finding(s) in Cognitive Complexity — start with CollectionUsage.Compilation.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 DropCycleCommand.Execute (cognitive 31) finding(s) in Cognitive Complexity — start with DropCycleCommand.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes8.3 / 10Strong✓ Tool-verified

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

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

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

59 god class(es) detected.

TooManyMethods: EfCoreProjectionStorage · ×53src/Marten.EntityFrameworkCore/EfCoreProjectionStorage.cs:0
ClassTooLong: BulkEventAppender · ×7src/Marten/Events/BulkEventAppender.cs:0
FileTooLong: Schema/DocumentMapping.cs · ×2src/Marten/Schema/DocumentMapping.cs:0

What to do

  1. Resolve the 53 TooManyMethods finding(s) in God Classes — start with AdvancedOperations.cs, AmbientTransactionLifetime.cs, AsyncProjectionTestingExtensions.cs. — One of this dimension's main actionable groups (53 warning-level).
  2. Resolve the 7 ClassTooLong finding(s) in God Classes — start with BulkEventAppender.cs, DocumentStorageDescriptorBuilder.cs, EventLoader.cs. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 2 FileTooLong finding(s) in God Classes — start with DocumentMapping.cs (2). — One of this dimension's main actionable groups (2 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication9.8 / 10Exemplary✓ Tool-verified

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

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

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

53 duplicated block group(s) detected.

Duplicated block (15 lines × 2) · ×5src/Marten.EntityFrameworkCore/EfCoreMultiStreamProjection.cs:91
Duplicated block (12 lines × 2) · ×5src/Marten/Events/Operations/InsertEventTagByEventIdOperation.cs:39
Duplicated block (11 lines × 2) · ×5src/Marten.EntityFrameworkCore/EfCoreMultiStreamProjection.cs:66
Duplicated block (10 lines × 2) · ×5src/Marten/Events/Fetching/FetchAsyncPlan.ForReading.cs:22
Duplicated block (8 lines × 2) · ×5src/Marten/Internal/UnitOfWork.cs:120

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

✓ On the Gold path — maintain.

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

D5 · Coupling8.9 / 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.

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

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

Off the main sequence: Marten.SourceGenerator · ×11
Unstable project EventPublisher

What to do

  1. Resolve the 11 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 1 Unstable project EventPublisher finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)7.1 / 10Strong✓ Tool-verified

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

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

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

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

220 of 899 classes have LCOM4 above 3.

Low cohesion: StandinDatabase (LCOM4 38) · ×220src/Marten/Storage/StandinDatabase.cs:20

What to do

  1. Resolve the 220 Low cohesion finding(s) in Cohesion (LCOM4) — start with CompositeProjection.cs (10), FSharpDiscriminatedUnionIdGeneration.cs (4), MartenServiceCollectionExtensions.cs (4). — One of this dimension's main actionable groups (220 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D8 · Code Coverage5.0 / 10Adequate✓ Tool-verified

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.

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

Line coverage 1.4%, branch coverage 0.6%.

What to do

  1. Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d8_recommendation.md.

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

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

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

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

8840 test methods: 8840 unit, 0 integration, 0 BDD, 0 e2e.

Unit tests
Integration tests
BDD tests
E2E tests

✓ On the Gold path — maintain.

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

D10 · Test Quality8.3 / 10Strong✓ Tool-verified

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

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

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

22 skipped (22 with a documented reason), 501 zero-assertion, 16 mock references across 8870 tests (1 harness-style project(s) excluded from the assertion penalty).

No assertions: single_stream_should_pass_when_conjoined_with_ITenanted · ×494src/Marten.EntityFrameworkCore.Tests/EfCoreMultiTenancyValidationTests.cs:57
No direct assertions: ResolveCommand_Succeeds · ×7src/samples/Helpdesk/Helpdesk.Api.Tests/Incidents/ResolveIncidentTests.cs:13
Skipped (documented): using_auto_create_field · ×22src/CoreTests/StoreOptionsTests.cs:53
Mock framework: NSubstitute · ×16

What to do

  1. Resolve the 494 No assertions finding(s) in Test Quality — start with guid_based_document_operations.cs (24), int_based_document_operations.cs (24), long_based_document_operations.cs (24). — One of this dimension's main actionable groups (494 issue-level).
  2. Resolve the 7 No direct assertions finding(s) in Test Quality — start with AcknowledgeResolutionIncidentTests.cs, AssignAgentTests.cs, CategoriseIncidentTests.cs. — One of this dimension's main actionable groups (7 recommendation-level).
  3. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

0 flaky across 1 measured tier(s). unit: measured (0 flaky); other: not included — too large to re-run within its budget.

Tier not included (time budget)

✓ On the Gold path — maintain.

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

D12 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 outdated, 0 vulnerable, 0 deprecated packages.

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md.

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 72 packages use a banned license.

Licenses scanned

✓ On the Gold path — maintain.

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

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

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

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

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

No churn × complexity hotspots in the window.

git history depth insufficient

✓ On the Gold path — maintain.

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

D17 · Explicit Debt9.5 / 10Exemplary✓ Tool-verified

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

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

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

157 deducted debt markers + 0 dead symbols across 173789 LoC (0.3/KLoC) → score 9.5.

NoWarnInCsproj · ×21build/build.csproj:7
TodoComment · ×98src/Marten/Events/Daemon/Internals/ProjectionBatch.cs:71
BarePragmaDisable · ×20src/Marten/Events/Daemon/HighWater/PostgresqlListenWakeup.cs:147
CommentedOutCode · ×10src/Marten/Events/Aggregation/SingleStreamProjection.cs:33
HackComment · ×6src/Marten/Events/Projections/ProjectionOptions.cs:146

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

✓ On the Gold path — maintain.

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

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

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

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

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

6 projects, 1868 .cs files, 159187 hand-written lines of code (158623 production / 564 test), 7 inter-project edges (build status unknown — did not finish).

Monorepo: only 1 of 2 solutions was scored
Analyzed solution does not cover the bulk of the repository
Build status unknown
Helpdesk.Api (Production)src/samples/Helpdesk/Helpdesk.Api/Helpdesk.Api.csproj
Helpdesk.Api.Tests (Test)src/samples/Helpdesk/Helpdesk.Api.Tests/Helpdesk.Api.Tests.csproj

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

✓ On the Gold path — maintain.

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

D26 · Project Cohesion7.0 / 10Strong✓ Tool-verified

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

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

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

14 of 90 projects flagged as possibly oversized/incoherent.

Large project: Marten(net9.0) · ×14

What to do

  1. Resolve the 14 Large project finding(s) in Project Cohesion. — One of this dimension's main actionable groups (14 recommendation-level).

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

D28 · Secrets (history)7.0 / 10Strong✓ Tool-verified

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.

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

3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

Secret: generic-api-key · ×3docs/.vitepress/config.mts:55detected by gitleaks finding
Rotate the exposed credentials — git history can't be un-committed

What to do

  1. Resolve the 3 Secret finding(s) in Secrets (history) — start with config.mts (2), fubumvc.json. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

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

Method: Polyglot static analysis via semgrep --config auto across the repo; severity rules (ERROR/WARNING/INFO) map to a 0-10 wide normalizer. Exhaustive, deterministic; degrades on parse failure.

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

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

semgrep found no security issues.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

D31 · IaC & Container Security9.3 / 10Exemplary✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

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

High IaC: DS-0002 · ×2docker/postgres/Dockerfiledetected by trivy finding
Low IaC: DS-0026 · ×2docker/postgres/Dockerfiledetected by trivy finding

✓ On the Gold path — maintain.

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

D33 · JS/npm Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether JavaScript/npm dependencies have known published vulnerabilities (CVEs) — the npm ecosystem's biggest risk.

Method: JS/npm CVE scan via trivy fs --scanners vuln over JS manifests (package.json/yarn.lock/pnpm-lock/bun.lockb); 0-10 tight normalizer. NotApplicable without JS manifests. Exhaustive, deterministic.

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

No known-vulnerable JS/npm dependencies.

✓ On the Gold path — maintain.

Detailed fixes: d33_recommendation.md.

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

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

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

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

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

Unpinned build actions
No build provenance
No artifact signing
No SBOM

What to do

  1. Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 No artifact signing finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

D38 · OSV Dependency Vulnerabilities3.4 / 10Weak✓ Tool-verified

What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — npm and other lockfile ecosystems, parsed natively. Complements D33 (npm via trivy) and D30 (.NET via dotnet).

Method: npm/multi-ecosystem CVE scan via osv-scanner (queries the osv.dev database + parses lockfiles natively: package-lock/yarn/pnpm/bun); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable without a JS lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.

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

21 finding(s): 0 critical, 7 high, 11 medium, 3 low.

High CVE: [GHSA redacted] · ×7package-lock.jsondetected by osv-scanner finding
Medium CVE: [GHSA redacted] · ×11package-lock.jsondetected by osv-scanner finding
Low CVE: [GHSA redacted] · ×3package-lock.jsondetected by osv-scanner finding

What to do

  1. Resolve the 11 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (11). — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 7 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (7). — One of this dimension's main actionable groups (7 issue-level).
  3. Resolve the 3 Low CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (3). — One of this dimension's main actionable groups (3 recommendation-level).

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

Frontend & cross-cutting dimensions

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

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

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

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

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

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.

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).
AX2 · Stateful singletons6.2 / 10Adequate✓ Tool-verified

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

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

  • `SecondaryDocumentStores` is a singleton (one shared instance) but mutates instance state outside any lock (_files; e.g. `_files` at line 25). (×2) — SecondaryStoreConfig.cs:11, SecondaryStoreConfig.cs:11

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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.

  • `IDocumentOperations` declares 33 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. (×2) — IDocumentOperations.cs:14, IDocumentOperations.cs:14
  • `IDocumentSession` declares 20 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. (×2) — IDocumentSession.cs:15, IDocumentSession.cs:15
  • `IDocumentStore` declares 42 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. (×2) — IDocumentStore.cs:21, IDocumentStore.cs:21
  • `IQuerySession` declares 83 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. (×2) — IQuerySession.cs:21, IQuerySession.cs:21
  • `IReadOnlyStoreOptions` declares 27 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. (×2) — IReadOnlyStoreOptions.cs:12, IReadOnlyStoreOptions.cs:12
  • `ISerializer` declares 21 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. (×2) — ISerializer.cs:35, ISerializer.cs:35
  • `IEventStoreOptions` declares 102 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. (×2) — IEventStoreOptions.cs:20, IEventStoreOptions.cs:20
  • `IReadOnlyEventStoreOptions` declares 58 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. (×2) — IReadOnlyEventStoreOptions.cs:14, IReadOnlyEventStoreOptions.cs:14
  • `IDocumentType` declares 46 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. (×2) — DocumentMapping.cs:47, DocumentMapping.cs:47
  • `IMartenSession` declares 21 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. (×2) — IMartenSession.cs:17, IMartenSession.cs:17
  • `IDocumentStorage` declares 28 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. (×2) — IDocumentStorage.cs:26, IDocumentStorage.cs:26
  • `IDocumentStorage` declares 20 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. (×2) — IDocumentStorage.cs:93, IDocumentStorage.cs:93
  • `ICollectionMember` declares 16 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. (×2) — ICollectionMember.cs:10, ICollectionMember.cs:10
  • `IQueryableMember` declares 22 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. (×2) — IQueryableMember.cs:11, IQueryableMember.cs:11
  • `IPagedList` declares 24 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. (×2) — IPagedList.cs:10, IPagedList.cs:10
  • `IBatchedQuery` declares 22 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. (×2) — IBatchedQuery.cs:159, IBatchedQuery.cs:159
  • `IBatchedQueryable` declares 19 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. (×2) — IBatchedQueryable.cs:10, IBatchedQueryable.cs:10
  • `IMartenDatabase` declares 21 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. (×2) — IMartenDatabase.cs:23, IMartenDatabase.cs:23

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls3.0 / 10Weak✓ Tool-verified

Other · Security — Whether access is authorized by default — [Authorize]/policies or imperative guard methods (throw-on-violation) called from handlers.

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

  • Authorization machinery exists but no [Authorize] usage and no imperative guard calls were found at handlers.

What to do

  • Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.
ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

ED5 · Idempotency3.0 / 10Weak◐ Sampled · advisory

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

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

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

  • `Sessions.InsertHandler.Execute` mutates persistent state (a repository write) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. (Configure an LLM to auto-classify this.) (×2) — DocumentSessionBase.cs:511, DocumentSessionBase.cs:511

What to do

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

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

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

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×25) — EventDocumentStorage.cs:110, EventDocumentStorage.cs:115, EventMapping.cs:389, …

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs4.3 / 10Weak✓ Tool-verified

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

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `OnBeforeExecute` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — Startup.cs:60, Startup.cs:70
  • `LogFailure` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — Startup.cs:65
  • `Execute` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — ReadCommand.cs:8
  • A test is skipped with reason "TODO -- too unreliable on CI" — the behavior it asserts is UNVERIFIED and this skip is likely the only marker of a real bug. It ages invisibly: fix the flakiness or track the bug somewhere that can't be forgotten. (×4) — EventStreamUnexpectedMaxEventIdExceptionTransformTest.cs:19, EventStreamUnexpectedMaxEventIdExceptionTransformTest.cs:19, EventStreamUnexpectedMaxEventIdExceptionTransformTest.cs:45, …
  • A test is skipped with reason "TODO: Fix it on the linq branch" — the behavior it asserts is UNVERIFIED and this skip is likely the only marker of a real bug. It ages invisibly: fix the flakiness or track the bug somewhere that can't be forgotten. (×2) — hashset_contains.cs:12, hashset_contains.cs:12
  • `NulloMessageOutbox` has 2 unfinished members out of 4 — a scaffolded type that was never implemented. (×2) — NulloMessageOutbox.cs:8, NulloMessageOutbox.cs:8
  • `AfterCommitAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — NulloMessageOutbox.cs:20, NulloMessageOutbox.cs:20
  • `BeforeCommitAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — NulloMessageOutbox.cs:25, NulloMessageOutbox.cs:25
  • `PostprocessAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×6) — ArchiveStreamOperation.cs:53, ArchiveStreamOperation.cs:53, DeleteProjectionProgress.cs:40, …
  • `SetIdentityFromString` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×4) — EventDocumentStorage.cs:108, EventDocumentStorage.cs:108, EventMapping.cs:387, …
  • `SetIdentityFromGuid` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — EventDocumentStorage.cs:113, EventDocumentStorage.cs:113
  • `VersionFor` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — EventDocumentStorage.cs:181, EventDocumentStorage.cs:181

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)7.4 / 10Strong✓ Tool-verified

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

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

What to do

  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 50 of 52 project(s) that lack one — worth up to 1.9 pts.
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

  • No Architecture Decision Records found — decisions aren't captured for future maintainers.

What to do

  • Start an ADR log (docs/adr/) recording significant decisions and their rationale.
M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

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

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

  • Only 40/90 projects share a common root namespace — the code's module identity is inconsistent.

What to do

  • Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability7.5 / 10Strong✓ Tool-verified

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

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

  • Only 6/33 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log).

What to do

  • Extend structured logging to the remaining service-like projects so the whole executable surface is diagnosable in production.
P3 · Security & performance tooling1.0 / 10Critical✓ Tool-verified

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

Method: Filesystem/Roslyn scan: CodeQL, Dependabot, secret-scanning, and BenchmarkDotNet presence in pipelines and projects. Exhaustive, deterministic.

  • No static application security testing (CodeQL / security analyzers / codehealth) detected.

What to do

  • Add a SAST step (e.g. CodeQL) or a security analyzer package.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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

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

  • Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.

What to do

  • Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
P5 · DR & Backup10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Roslyn scan: Polly resilience markers (Retry, CircuitBreaker, Timeout) on outbound HTTP invocations. Computed per type, deterministic.

P8 · Schema migrations6.0 / 10Adequate✓ Tool-verified

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

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage. Exhaustive per project, deterministic.

  • EF Core is used but neither migrations nor EnsureCreated were detected — confirm how the production schema is created and evolved.

What to do

  • Adopt EF migrations (dotnet ef migrations add + Migrate() on startup) as the explicit, versioned schema strategy — no migration mechanism was detected.
PF1 · Benchmark discipline7.5 / 10Strong✓ Tool-verified

Readiness · Performance — Whether the library protects its performance with benchmarks — a BenchmarkDotNet suite, an allocation MemoryDiagnoser, 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.

  • A BenchmarkDotNet suite exists but no [MemoryDiagnoser] — allocations (the main way a library pressures its host's GC) aren't being measured.

What to do

  • Add [MemoryDiagnoser] to the benchmarks so allocation regressions are visible, not just time.
PF2 · Allocation hygiene7.4 / 10Strong✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's GC — Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask, value-type structs and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit. Reward-only. Deterministic, syntax/text detection.

What to do

  • Raise allocation-aware density on the hot paths — currently 485 use(s) across 174,764 production line(s) (~2.8/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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.

  • 7 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock in a consumer with a synchronization context.

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code.
S1 · Web-Security Posture6.5 / 10Adequate✓ Tool-verified

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

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. Deterministic.

  • 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.)
  • No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.)

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.
  • Set secure cookie flags — CookieSecurePolicy.Always, HttpOnly, and SameSite (Strict/Lax) on auth/session cookies. Skip only if the app sets no cookies.
X1 · Async correctness7.8 / 10Strong✓ Tool-verified

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

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

  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Make the caller `async` and `await` instead. (×9) — MartenDatabase.cs:146, MasterTableTenancy.cs:145, ShardedTenancy.cs:102, …

What to do

  • Sync-over-async (deadlock risk)
X2 · Cancellation propagation8.7 / 10Strong✓ Tool-verified

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

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage.

  • Only 884/1137 async methods accept a CancellationToken, so requests can't be cancelled cleanly under load or on client disconnect. In Blazor Server circuits and other short-write hosts, omitting it can be an accepted convention — judge against your hosting model.
  • No CancellationToken parameter — work can't be cancelled cleanly on disconnect/shutdown. (×25) — build.cs:501, MultiplesTestPlan.cs:10, SingleFileFetchForWritingPlan.cs:10, …

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.

X5 · Nullable reference types6.9 / 10Adequate✓ Tool-verified

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

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

  • 29/42 projects enable <Nullable>enable</Nullable>. NRTs catch a whole class of null-deref bugs at compile time.
  • ~1.0 `!` suppressions per 1k syntax nodes — each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

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

Reference — by lens

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

LensScoreRatingImpact
Code Health71%StrongSolid.
Architecture83%StrongSolid.
Maturity70%StrongSolid.
Readiness54%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security43%Weak — gated by D36, D38, C1, C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven100%ExemplaryStrongest area.
Performance68%AdequateAcceptable, with room to improve.
Not included — 34 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 user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data (event-sourced storage — lifecycle is stream archival / event TTL, not row CASCADE) — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
  • D23 Boundary Type-Coupling — Bounded contexts not declared
  • D27 Navigability — Navigability unmeasured — symbol resolution incomplete
  • D30 Dependency Vulnerabilities — Not applicable
  • D32 Data Compliance (PII/GDPR) — Not applicable
  • D34 Knowledge Freshness — early-stage repository — too little history to judge knowledge freshness
  • D35 Change Coupling — no production change history to mine for change-coupling
  • D37 Vulnerability-disclosure Policy — Not applicable
  • D39 IL Efficiency — IL metrics not applicable
  • D7 Architectural Integrity — No checkable ADRs to assess
  • DM1 Domain Modelling — applicable but skipped (2/3 markers — below the conservative bar): 29 value object(s); a Domain/Aggregates/ValueObjects layer
  • ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
  • ED3 Event naming — no domain or integration events detected — event-naming check not applicable
  • ES1 Fold determinism — no Apply/When folds detected — fold-determinism check not applicable
  • ES2 Immutable events — no persisted event types detected — immutability check not applicable
  • ES3 PII in the event store — no persisted event types detected — PII-in-events check not applicable
  • M4 Documentation accuracy — LLM not available — accuracy is the Tier-2 layer and needs a reachable model.
  • P12 CI test-gate honesty — no data
  • P9 Domain vs controller coverage — coverage data present but no domain-layer files were identified (no /Domain//Aggregates/ paths)
  • X6 Hand-rolled structured-format parsing — no data
  • X7 Silent fallback defaults — no data

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.

Issue — 527 finding(s)
D10 · Test Quality · No assertions · ×494
  • No assertions: single_stream_should_pass_when_conjoined_with_ITenanted src/Marten.EntityFrameworkCore.Tests/EfCoreMultiTenancyValidationTests.cs:57 — Test method has no assertions — it may not test anything.
  • No assertions: single_stream_should_pass_without_conjoined_tenancy src/Marten.EntityFrameworkCore.Tests/EfCoreMultiTenancyValidationTests.cs:67 — Test method has no assertions — it may not test anything.
  • No assertions: single_stream_should_pass_when_conjoined_with_ITenanted src/Marten.EntityFrameworkCore.Tests/EfCoreMultiTenancyValidationTests.cs:57 — Test method has no assertions — it may not test anything.
  • No assertions: single_stream_should_pass_without_conjoined_tenancy src/Marten.EntityFrameworkCore.Tests/EfCoreMultiTenancyValidationTests.cs:67 — Test method has no assertions — it may not test anything.
  • No assertions: expected_version_check_is_tenant_isolated src/TenantPartitionedEventsTests/OptimisticConcurrency/Optimistic_concurrency_under_partitioned_events.cs:211 — Test method has no assertions — it may not test anything.
  • No assertions: expected_version_check_is_tenant_isolated src/TenantPartitionedEventsTests/OptimisticConcurrency/Optimistic_concurrency_under_partitioned_events_string.cs:216 — Test method has no assertions — it may not test anything.
  • No assertions: expected_version_check_is_tenant_isolated src/TenantPartitionedEventsTests/OptimisticConcurrency/Optimistic_concurrency_under_partitioned_events.cs:211 — Test method has no assertions — it may not test anything.
  • No assertions: expected_version_check_is_tenant_isolated src/TenantPartitionedEventsTests/OptimisticConcurrency/Optimistic_concurrency_under_partitioned_events_string.cs:216 — Test method has no assertions — it may not test anything.
  • No assertions: can_append_and_query_events src/Marten.NodaTime.Testing/Acceptance/noda_time_acceptance.cs:193 — Test method has no assertions — it may not test anything.
  • No assertions: can_append_and_query_events src/Marten.NodaTime.Testing/Acceptance/noda_time_acceptance.cs:193 — Test method has no assertions — it may not test anything.
  • No assertions: capture_events src/samples/DocSamples/EventSourcingQuickstart.cs:118 — Test method has no assertions — it may not test anything.
  • No assertions: quest_projection src/samples/DocSamples/EventSourcingQuickstart.cs:164 — Test method has no assertions — it may not test anything.
  • No assertions: execute_end_to_end src/ContainerScopedProjectionTests/when_registering_an_eventprojection_through_ioc_as_scoped.cs:119 — Test method has no assertions — it may not test anything.
  • No assertions: execute_end_to_end src/ContainerScopedProjectionTests/when_registering_an_eventprojection_through_ioc_as_singleton.cs:124 — Test method has no assertions — it may not test anything.
  • No assertions: execute_end_to_end src/ContainerScopedProjectionTests/when_registering_an_iprojection_through_ioc_as_scoped.cs:124 — Test method has no assertions — it may not test anything.
  • No assertions: execute_end_to_end src/ContainerScopedProjectionTests/when_registering_an_iprojection_through_ioc_as_singleton.cs:124 — Test method has no assertions — it may not test anything.
  • No assertions: execute_end_to_end src/ContainerScopedProjectionTests/when_registering_an_eventprojection_through_ioc_as_scoped.cs:119 — Test method has no assertions — it may not test anything.
  • No assertions: execute_end_to_end src/ContainerScopedProjectionTests/when_registering_an_eventprojection_through_ioc_as_singleton.cs:124 — Test method has no assertions — it may not test anything.
  • No assertions: execute_end_to_end src/ContainerScopedProjectionTests/when_registering_an_iprojection_through_ioc_as_scoped.cs:124 — Test method has no assertions — it may not test anything.
  • No assertions: execute_end_to_end src/ContainerScopedProjectionTests/when_registering_an_iprojection_through_ioc_as_singleton.cs:124 — Test method has no assertions — it may not test anything.
  • No assertions: pass_in_current_connection src/CoreTests/Bugs/Bug_2135_open_session_should_use_provided_connection_string.cs:20 — Test method has no assertions — it may not test anything.
  • No assertions: can_create_index src/CoreTests/Bugs/Bug_2916_ngram_index_when_multi_tenanted.cs:13 — Test method has no assertions — it may not test anything.
  • No assertions: can_build_index src/CoreTests/Bugs/Bug_3019_gist_gin_index_on_arrays.cs:15 — Test method has no assertions — it may not test anything.
  • No assertions: can_retrofit_to_multitenanted_later src/CoreTests/Bugs/Bug_3145_migration_to_tenanted.cs:20 — Test method has no assertions — it may not test anything.
  • No assertions: do_not_blow_up src/CoreTests/Bugs/Bug_3911_use_sticky_connections_when_otel_connection_tracking_is_on.cs:11 — Test method has no assertions — it may not test anything.
  • + 469 more in this group — see findings.md.
D17 · Explicit Debt · NoWarnInCsproj · ×21
  • NoWarnInCsproj build/build.csproj:7 — CS0649
  • NoWarnInCsproj build/build.csproj:7 — CS0169
  • NoWarnInCsproj build/build.csproj:7 — CA1050
  • NoWarnInCsproj build/build.csproj:7 — CA1822
  • NoWarnInCsproj build/build.csproj:7 — CA2211
  • NoWarnInCsproj build/build.csproj:7 — IDE1006
  • NoWarnInCsproj src/TenantPartitionedEventsTests/TenantPartitionedEventsTests.csproj:79 — xUnit1013
  • NoWarnInCsproj src/StressTests/StressTests.csproj:38 — xUnit1013
  • NoWarnInCsproj src/MultiTenancyTests/MultiTenancyTests.csproj:126 — xUnit1013
  • NoWarnInCsproj src/Marten.Testing/Marten.Testing.csproj:52 — xUnit1013
  • NoWarnInCsproj src/Marten.SourceGenerator/Marten.SourceGenerator.csproj:16 — RS2008
  • NoWarnInCsproj src/Marten.SourceGenerator.Tests/Marten.SourceGenerator.Tests.csproj:14 — xUnit1031
  • NoWarnInCsproj src/Marten.SourceGeneration/Marten.SourceGeneration.csproj:9 — CS8603
  • NoWarnInCsproj src/Marten.SourceGeneration/Marten.SourceGeneration.csproj:9 — CS8602
  • NoWarnInCsproj src/Marten.SourceGeneration/Marten.SourceGeneration.csproj:9 — CS8604
  • NoWarnInCsproj src/Marten.NodaTime.Testing/Marten.NodaTime.Testing.csproj:22 — xUnit1013
  • NoWarnInCsproj src/LinqTests/LinqTests.csproj:128 — xUnit1013
  • NoWarnInCsproj src/EventSourcingTests/EventSourcingTests.csproj:133 — xUnit1013
  • NoWarnInCsproj src/DocumentDbTests/DocumentDbTests.csproj:169 — xUnit1013
  • NoWarnInCsproj src/CoreTests/CoreTests.csproj:131 — xUnit1013
  • NoWarnInCsproj src/ContainerScopedProjectionTests/ContainerScopedProjectionTests.csproj:37 — xUnit1013
D38 · OSV Dependency Vulnerabilities · High CVE · ×7
  • High CVE: [GHSA redacted] package-lock.json — multiparty: [GHSA redacted]
  • High CVE: [GHSA redacted] package-lock.json — multiparty: [GHSA redacted]
  • High CVE: [GHSA redacted] package-lock.json — multiparty: [GHSA redacted]
  • High CVE: [GHSA redacted] package-lock.json — path-to-regexp: [GHSA redacted]
  • High CVE: [GHSA redacted] package-lock.json — preact: [GHSA redacted]
  • High CVE: [GHSA redacted] package-lock.json — vite: [GHSA redacted]
  • High CVE: [GHSA redacted] package-lock.json — ws: [GHSA redacted]
D28 · Secrets (history) · Secret · ×3
  • Secret: generic-api-key docs/.vitepress/config.mts:55 — matched rule 'generic-api-key'
  • Secret: facebook-page-access-token src/Marten.Testing/Github/fubumvc.json:1 — matched rule 'facebook-page-access-token'
  • Secret: generic-api-key docs/.vitepress/config.mts:101 — matched rule 'generic-api-key'
D31 · IaC & Container Security · High IaC · ×2
  • High IaC: DS-0002 docker/postgres/Dockerfile — Image user should not be 'root'
  • High IaC: DS-0002 src/samples/Helpdesk/Helpdesk.Api/Dockerfile — Image user should not be 'root'
Warning — 556 finding(s)
D6 · Cohesion (LCOM4) · Low cohesion · ×220
  • Low cohesion: StandinDatabase (LCOM4 38) src/Marten/Storage/StandinDatabase.cs:20 — StandinDatabase's methods form 38 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: StandinDatabase (LCOM4 38) src/Marten/Storage/StandinDatabase.cs:20 — StandinDatabase's methods form 38 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: EventDocumentStorage (LCOM4 33) src/Marten/Events/EventDocumentStorage.cs:37 — EventDocumentStorage's methods form 33 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: EventDocumentStorage (LCOM4 33) src/Marten/Events/EventDocumentStorage.cs:37 — EventDocumentStorage's methods form 33 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: EventMapping (LCOM4 26) src/Marten/Events/EventMapping.cs:219 — EventMapping's methods form 26 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: DocumentStorage (LCOM4 26) src/Marten/Internal/Storage/DocumentStorage.cs:43 — DocumentStorage's methods form 26 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: EventMapping (LCOM4 26) src/Marten/Events/EventMapping.cs:219 — EventMapping's methods form 26 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: DocumentStorage (LCOM4 26) src/Marten/Internal/Storage/DocumentStorage.cs:43 — DocumentStorage's methods form 26 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: ProjectionUpdateBatch (LCOM4 22) src/Marten/Events/Daemon/Internals/ProjectionUpdateBatch.cs:25 — ProjectionUpdateBatch's methods form 22 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: ProjectionUpdateBatch (LCOM4 22) src/Marten/Events/Daemon/Internals/ProjectionUpdateBatch.cs:25 — ProjectionUpdateBatch's methods form 22 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: EventStore (LCOM4 21) src/Marten/Events/EventStore.FetchForWriting.cs:29 — EventStore's methods form 21 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: BatchedQuery (LCOM4 21) src/Marten/Services/BatchQuerying/BatchedQuery.cs:19 — BatchedQuery's methods form 21 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: EventStore (LCOM4 21) src/Marten/Events/EventStore.FetchForWriting.cs:29 — EventStore's methods form 21 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: BatchedQuery (LCOM4 21) src/Marten/Services/BatchQuerying/BatchedQuery.cs:19 — BatchedQuery's methods form 21 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: DocumentSessionBase (LCOM4 17) src/Marten/Internal/Sessions/DocumentSessionBase.cs:18 — DocumentSessionBase's methods form 17 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: DocumentSessionBase (LCOM4 17) src/Marten/Internal/Sessions/DocumentSessionBase.cs:18 — DocumentSessionBase's methods form 17 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: MartenLinqQueryable (LCOM4 15) src/Marten/Linq/MartenLinqQueryable.cs:32 — MartenLinqQueryable's methods form 15 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: MartenLinqQueryable (LCOM4 15) src/Marten/Linq/MartenLinqQueryable.cs:32 — MartenLinqQueryable's methods form 15 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: JsonLoader (LCOM4 13) src/Marten/JsonLoader.cs:14 — JsonLoader's methods form 13 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: StoreOptions (LCOM4 13) src/Marten/StoreOptions.cs:47 — StoreOptions's methods form 13 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: JsonLoader (LCOM4 13) src/Marten/JsonLoader.cs:14 — JsonLoader's methods form 13 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: StoreOptions (LCOM4 13) src/Marten/StoreOptions.cs:47 — StoreOptions's methods form 13 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: QueryOnlyClosedShapeStorage (LCOM4 11) src/Marten/Internal/ClosedShape/QueryOnlyClosedShapeStorage.cs:25 — QueryOnlyClosedShapeStorage's methods form 11 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: ValueCollectionMember (LCOM4 11) src/Marten/Linq/Members/ValueCollections/ValueCollectionMember.cs:23 — ValueCollectionMember's methods form 11 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • Low cohesion: QueryOnlyClosedShapeStorage (LCOM4 11) src/Marten/Internal/ClosedShape/QueryOnlyClosedShapeStorage.cs:25 — QueryOnlyClosedShapeStorage's methods form 11 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
  • + 195 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×98
  • TodoComment src/Marten/Events/Daemon/Internals/ProjectionBatch.cs:71 — // TODO -- need to pass through the tenant id — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Events/Daemon/Internals/ProjectionUpdateBatch.cs:72 — // TODO -- make this private — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Events/EventStore.Append.cs:13 — //TODO NRT: We're ignoring null here as to not unintentionally change any downstream behaviour - Replace with null guards in the future. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Events/Fetching/FetchAsyncPlan.ExpectedVersion.cs:31 — // TODO -- use read only transaction???? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Events/Fetching/FetchAsyncPlan.ForReading.cs:44 — // TODO -- use read only transaction???? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Events/Projections/EventProjection.cs:117 — // TODO upstream change — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Events/RichEventAppender.cs:92 — // TODO -- look for opportunities to batch up the requests here too! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/EventStorage/Dialects/PostgresEventStoreDialect.cs:554 — // TODO (#4416): remaining binders: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Internal/Sessions/DocumentSessionBase.ProjectionStorage.cs:250 — //TODO fix in IProjectionStorage — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Internal/Sessions/DocumentSessionBase.SaveChanges.cs:123 — // TODO -- double check this isn't getting done multiple times — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Internal/Sessions/IConnectionLifetime.cs:12 — // TODO -- look at how much more could be put here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Internal/Sessions/QuerySession.ChangeTracking.cs:10 — // TODO -- this should be on DocumentSessionBase somehow — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Internal/Sessions/QuerySession.ChangeTracking.cs:29 — // TODO -- try to make this only built out for dirty checking sessions — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Internal/Sessions/TransactionalConnection.cs:100 — // TODO -- this should be ValueTask — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Internal/Storage/DocumentStorage.cs:135 — // TODO -- convert to a method in V8 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Internal/Storage/DocumentStorage.cs:490 — // TODO -- eliminate the downcast here! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Linq/Members/ValueCollections/ValueCollectionMember.cs:186 — // TODO -- this could be memoized a bit — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Linq/Parsing/LinqQueryParser.cs:14 — // TODO -- inject somehow later. See https://github.com/JasperFx/marten/issues/2709 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Linq/Parsing/MemberFinder.cs:12 — // TODO -- this needs to account for Methods too!. See https://github.com/JasperFx/marten/issues/2707 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Linq/Parsing/Methods/Strings/StringComparisonParser.cs:82 — // TODO -- watch the NULL values! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Linq/Parsing/Operators/OperatorLibrary.cs:35 — // TODO -- is this necessary? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Linq/Parsing/SimpleExpression.cs:168 — // TODO -- this will need to evaluate extra methods in the comparison. Looking for StringProp.ToLower() == "foo" — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Linq/SqlGeneration/Filters/CollectionIsEmpty.cs:9 — // TODO -- make it ICollectionAware — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Linq/SqlGeneration/Filters/CollectionIsNotEmpty.cs:49 — // TODO -- come back to this later with — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/Marten/Linq/SqlGeneration/Literal.cs:12 — // TODO -- move this to Weasel itself — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 73 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×53
  • TooManyMethods: EfCoreProjectionStorage src/Marten.EntityFrameworkCore/EfCoreProjectionStorage.cs:0 — TooManyMethods — 140 lines, 32 methods.
  • TooManyMethods: JsonNetSerializer src/Marten.Newtonsoft/Services/JsonNetSerializer.cs:0 — TooManyMethods — 318 lines, 44 methods.
  • TooManyMethods: AdvancedOperations src/Marten/AdvancedOperations.cs:0 — TooManyMethods — 450 lines, 62 methods.
  • TooManyMethods: DocumentStore src/Marten/DocumentStore.CompiledQueryCollection.cs:0 — TooManyMethods — 2084 lines, 224 methods.
  • TooManyMethods: TestingExtensions src/Marten/Events/AsyncProjectionTestingExtensions.cs:0 — TooManyMethods — 358 lines, 32 methods.
  • TooManyMethods: ProjectionUpdateBatch src/Marten/Events/Daemon/Internals/ProjectionUpdateBatch.cs:0 — TooManyMethods — 370 lines, 82 methods.
  • TooManyMethods: EventDocumentStorage src/Marten/Events/EventDocumentStorage.cs:0 — TooManyMethods — 426 lines, 88 methods.
  • TooManyMethods: EventGraph src/Marten/Events/EventGraph.Actions.cs:0 — TooManyMethods — 1056 lines, 128 methods.
  • TooManyMethods: EventMapping src/Marten/Events/EventMapping.cs:0 — TooManyMethods — 332 lines, 70 methods.
  • TooManyMethods: EventStore src/Marten/Events/EventStore.Append.cs:0 — TooManyMethods — 1150 lines, 190 methods.
  • TooManyMethods: FetchNaturalKeyPlan src/Marten/Events/Fetching/FetchNaturalKeyPlan.cs:0 — TooManyMethods — 754 lines, 48 methods.
  • TooManyMethods: QuickAppendEventsOperationBase src/Marten/Events/Operations/QuickAppendEventsOperationBase.cs:0 — TooManyMethods — 328 lines, 38 methods.
  • TooManyMethods: FlatTableProjection src/Marten/Events/Projections/Flattened/FlatTableProjection.cs:0 — TooManyMethods — 290 lines, 48 methods.
  • TooManyMethods: QueryEventStore src/Marten/Events/QueryEventStore.cs:0 — TooManyMethods — 296 lines, 36 methods.
  • TooManyMethods: ProjectionScenario src/Marten/Events/TestSupport/ProjectionScenario.Assertions.cs:0 — TooManyMethods — 624 lines, 84 methods.
  • TooManyMethods: PostgresEventStoreDialect src/Marten/EventStorage/Dialects/PostgresEventStoreDialect.cs:0 — TooManyMethods — 546 lines, 32 methods.
  • TooManyMethods: HostExtensions src/Marten/HostExtensions.cs:0 — TooManyMethods — 174 lines, 36 methods.
  • TooManyMethods: QueryOnlyClosedShapeStorage src/Marten/Internal/ClosedShape/QueryOnlyClosedShapeStorage.cs:0 — TooManyMethods — 78 lines, 32 methods.
  • TooManyMethods: CompiledQueryPlan src/Marten/Internal/CompiledQueries/CompiledQueryPlan.cs:0 — TooManyMethods — 388 lines, 48 methods.
  • TooManyMethods: StorageOperation src/Marten/Internal/Operations/StorageOperation.cs:0 — TooManyMethods — 270 lines, 42 methods.
  • TooManyMethods: AmbientTransactionLifetime src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:0 — TooManyMethods — 292 lines, 44 methods.
  • TooManyMethods: DocumentSessionBase src/Marten/Internal/Sessions/DocumentSessionBase.cs:0 — TooManyMethods — 990 lines, 122 methods.
  • TooManyMethods: ProjectionStorage src/Marten/Internal/Sessions/DocumentSessionBase.ProjectionStorage.cs:0 — TooManyMethods — 182 lines, 32 methods.
  • TooManyMethods: ExternalTransaction src/Marten/Internal/Sessions/ExternalTransaction.cs:0 — TooManyMethods — 270 lines, 42 methods.
  • TooManyMethods: QuerySession src/Marten/Internal/Sessions/QuerySession.AdvancedSql.cs:0 — TooManyMethods — 1184 lines, 198 methods.
  • + 28 more in this group — see findings.md.
D17 · Explicit Debt · BarePragmaDisable · ×20
  • BarePragmaDisable src/Marten/Events/Daemon/HighWater/PostgresqlListenWakeup.cs:147 — #pragma warning disable MA0040
  • BarePragmaDisable src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:121 — #pragma warning disable CS8602
  • BarePragmaDisable src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:139 — #pragma warning disable CS8602
  • BarePragmaDisable src/Marten/Internal/Sessions/TransactionalConnection.cs:214 — #pragma warning disable CS8602
  • BarePragmaDisable src/Marten/Internal/Sessions/TransactionalConnection.cs:230 — #pragma warning disable CS8602
  • BarePragmaDisable src/Marten/Services/Json/SystemTextJsonExtensions.cs:14 — #pragma warning disable
  • BarePragmaDisable src/Marten/Storage/MasterTableTenancy.cs:314 — #pragma warning disable VSTHRD103
  • BarePragmaDisable src/Marten/Storage/MasterTableTenancy.cs:328 — #pragma warning disable VSTHRD103
  • BarePragmaDisable src/Marten/Storage/MasterTableTenancy.cs:384 — #pragma warning disable MA0032
  • BarePragmaDisable src/Marten/Storage/ShardedTenancy.cs:545 — #pragma warning disable MA0032
  • BarePragmaDisable src/Marten/Events/Daemon/HighWater/PostgresqlListenWakeup.cs:147 — #pragma warning disable MA0040
  • BarePragmaDisable src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:121 — #pragma warning disable CS8602
  • BarePragmaDisable src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:139 — #pragma warning disable CS8602
  • BarePragmaDisable src/Marten/Internal/Sessions/TransactionalConnection.cs:214 — #pragma warning disable CS8602
  • BarePragmaDisable src/Marten/Internal/Sessions/TransactionalConnection.cs:230 — #pragma warning disable CS8602
  • BarePragmaDisable src/Marten/Services/Json/SystemTextJsonExtensions.cs:14 — #pragma warning disable
  • BarePragmaDisable src/Marten/Storage/MasterTableTenancy.cs:314 — #pragma warning disable VSTHRD103
  • BarePragmaDisable src/Marten/Storage/MasterTableTenancy.cs:328 — #pragma warning disable VSTHRD103
  • BarePragmaDisable src/Marten/Storage/MasterTableTenancy.cs:384 — #pragma warning disable MA0032
  • BarePragmaDisable src/Marten/Storage/ShardedTenancy.cs:545 — #pragma warning disable MA0032
D38 · OSV Dependency Vulnerabilities · Medium CVE · ×11
  • Medium CVE: [GHSA redacted] package-lock.json — @opentelemetry/core: [GHSA redacted]
  • Medium CVE: [GHSA redacted] package-lock.json — brace-expansion: [GHSA redacted]
  • Medium CVE: [GHSA redacted] package-lock.json — brace-expansion: [GHSA redacted]
  • Medium CVE: [GHSA redacted] package-lock.json — esbuild: [GHSA redacted]
  • Medium CVE: [GHSA redacted] package-lock.json — js-yaml: [GHSA redacted]
  • Medium CVE: [GHSA redacted] package-lock.json — mdast-util-to-hast: [GHSA redacted]
  • Medium CVE: [GHSA redacted] package-lock.json — path-to-regexp: [GHSA redacted]
  • Medium CVE: [GHSA redacted] package-lock.json — vite: [GHSA redacted]
  • Medium CVE: [GHSA redacted] package-lock.json — vite: [GHSA redacted]
  • Medium CVE: [GHSA redacted] package-lock.json — vite: [GHSA redacted]
  • Medium CVE: [GHSA redacted] package-lock.json — ws: [GHSA redacted]
D5 · Coupling · Off the main sequence · ×11
  • Off the main sequence: Marten.SourceGenerator — Marten.SourceGenerator: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: Marten.Testing.ThirdAssembly(net10.0) — Marten.Testing.ThirdAssembly(net10.0): abstractness 0.00, instability 0.10, distance 0.90 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: Marten.Testing.ThirdAssembly(net9.0) — Marten.Testing.ThirdAssembly(net9.0): abstractness 0.00, instability 0.11, distance 0.89 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: Marten.AspNetCore(net10.0) — Marten.AspNetCore(net10.0): abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: Marten.Testing.OtherAssembly(net10.0) — Marten.Testing.OtherAssembly(net10.0): abstractness 0.08, instability 0.10, distance 0.82 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: Marten.Testing.OtherAssembly(net9.0) — Marten.Testing.OtherAssembly(net9.0): abstractness 0.08, instability 0.11, distance 0.81 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: Marten(net9.0) — Marten(net9.0): abstractness 0.22, instability 0.00, distance 0.78 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: Marten(net10.0) — Marten(net10.0): abstractness 0.22, instability 0.00, distance 0.78 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: Marten.AspNetCore(net9.0) — Marten.AspNetCore(net9.0): abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: Marten.Newtonsoft(net9.0) — Marten.Newtonsoft(net9.0): abstractness 0.20, instability 0.08, distance 0.72 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: Marten.Newtonsoft(net10.0) — Marten.Newtonsoft(net10.0): abstractness 0.20, instability 0.08, distance 0.72 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
D17 · Explicit Debt · CommentedOutCode · ×10
  • CommentedOutCode src/Marten/Events/Aggregation/SingleStreamProjection.cs:33 — 4 consecutive commented-code lines
  • CommentedOutCode src/Marten/StoreOptions.cs:1214 — 5 consecutive commented-code lines
  • CommentedOutCode src/Marten/Events/Aggregation/SingleStreamProjection.cs:33 — 4 consecutive commented-code lines
  • CommentedOutCode src/Marten/StoreOptions.cs:1214 — 5 consecutive commented-code lines
  • CommentedOutCode src/EventSourcingTests/Bugs/Bug_3184_Projection_named_Projection.cs:42 — 4 consecutive commented-code lines
  • CommentedOutCode src/EventSourcingTests/Examples/TrackedEventProjection.cs:61 — 13 consecutive commented-code lines
  • CommentedOutCode src/EventSourcingTests/Bugs/Bug_3184_Projection_named_Projection.cs:42 — 4 consecutive commented-code lines
  • CommentedOutCode src/EventSourcingTests/Examples/TrackedEventProjection.cs:61 — 13 consecutive commented-code lines
  • CommentedOutCode src/LinqTests/Acceptance/select_clauses.cs:70 — 4 consecutive commented-code lines
  • CommentedOutCode src/LinqTests/Acceptance/select_clauses.cs:70 — 4 consecutive commented-code lines
D3 · God Classes · ClassTooLong · ×7
  • ClassTooLong: BulkEventAppender src/Marten/Events/BulkEventAppender.cs:0 — ClassTooLong — 436 lines, 24 methods.
  • ClassTooLong: HighWaterDetector src/Marten/Events/Daemon/HighWater/HighWaterDetector.cs:0 — ClassTooLong — 414 lines, 30 methods.
  • ClassTooLong: EventLoader src/Marten/Events/Daemon/Internals/EventLoader.cs:0 — ClassTooLong — 414 lines, 16 methods.
  • ClassTooLong: FetchAsyncPlan src/Marten/Events/Fetching/FetchAsyncPlan.cs:0 — ClassTooLong — 628 lines, 28 methods.
  • ClassTooLong: DocumentStorageDescriptorBuilder src/Marten/Internal/ClosedShape/DocumentStorageDescriptorBuilder.cs:0 — ClassTooLong — 564 lines, 20 methods.
  • ClassTooLong: MartenRegistry src/Marten/MartenRegistry.cs:0 — ClassTooLong — 570 lines, 10 methods.
  • ClassTooLong: Target src/Marten.Testing/Documents/Target.cs:0 — ClassTooLong — 414 lines, 12 methods.
D17 · Explicit Debt · HackComment · ×6
  • HackComment src/Marten/Events/Projections/ProjectionOptions.cs:146 — // Hack to address https://github.com/JasperFx/marten/issues/2610 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • HackComment src/Marten/Linq/Includes/PassthroughSelectStatement.cs:29 — // Hack, but makes SelectMany() work where the exact table gets lost — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • HackComment src/Marten/Linq/SqlGeneration/SelectorStatement.cs:117 — // Hack, but let it go — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • HackComment src/Marten/Events/Projections/ProjectionOptions.cs:146 — // Hack to address https://github.com/JasperFx/marten/issues/2610 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • HackComment src/Marten/Linq/Includes/PassthroughSelectStatement.cs:29 — // Hack, but makes SelectMany() work where the exact table gets lost — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
  • HackComment src/Marten/Linq/SqlGeneration/SelectorStatement.cs:117 — // Hack, but let it go — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×5
  • Duplicated block (15 lines × 2) src/Marten.EntityFrameworkCore/EfCoreMultiStreamProjection.cs:91 — src/Marten.EntityFrameworkCore/EfCoreMultiStreamProjection.cs:91-105 | src/Marten.EntityFrameworkCore/EfCoreSingleStreamProjection.cs:91-105
  • Duplicated block (15 lines × 2) src/Marten/Events/Daemon/Internals/ProjectionUpdateBatch.cs:250 — src/Marten/Events/Daemon/Internals/ProjectionUpdateBatch.cs:250-264 | src/Marten/Events/Daemon/Internals/ProjectionUpdateBatch.cs:275-289
  • Duplicated block (15 lines × 2) src/Marten/Internal/ClosedShape/ClosedShapeOverwriteOperation.cs:85 — src/Marten/Internal/ClosedShape/ClosedShapeOverwriteOperation.cs:85-99 | src/Marten/Internal/ClosedShape/ClosedShapeUpsertOperation.cs:89-103
  • Duplicated block (15 lines × 2) src/Marten/Internal/ClosedShape/NumericClosedShapeOverwriteOperation.cs:77 — src/Marten/Internal/ClosedShape/NumericClosedShapeOverwriteOperation.cs:77-91 | src/Marten/Internal/ClosedShape/NumericClosedShapeUpsertOperation.cs:91-105
  • Duplicated block (15 lines × 2) src/CommandLineRunner/TestCommand.cs:67 — src/CommandLineRunner/TestCommand.cs:67-81 | src/CommandLineRunner/TestCommand.cs:83-97
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×5
  • Duplicated block (12 lines × 2) src/Marten/Events/Operations/InsertEventTagByEventIdOperation.cs:39 — src/Marten/Events/Operations/InsertEventTagByEventIdOperation.cs:39-50 | src/Marten/Events/Operations/InsertEventTagOperation.cs:35-46
  • Duplicated block (12 lines × 2) src/Marten/Internal/ClosedShape/ClosedShapeDirtyTrackingSelector.cs:37 — src/Marten/Internal/ClosedShape/ClosedShapeDirtyTrackingSelector.cs:37-48 | src/Marten/Internal/ClosedShape/ClosedShapeIdentityMapSelector.cs:35-46
  • Duplicated block (12 lines × 2) src/Marten/Linq/QueryHandlers/AdvancedSqlQueryHandler.cs:155 — src/Marten/Linq/QueryHandlers/AdvancedSqlQueryHandler.cs:155-165 | src/Marten/Linq/QueryHandlers/UserSuppliedQueryHandler.cs:116-127
  • Duplicated block (12 lines × 2) src/Marten/Linq/QueryHandlers/CheckExistsByIdHandler.cs:37 — src/Marten/Linq/QueryHandlers/CheckExistsByIdHandler.cs:37-48 | src/Marten/Linq/QueryHandlers/LoadByIdHandler.cs:50-61
  • Duplicated block (12 lines × 2) src/Marten/Linq/QueryHandlers/LoadByIdArrayHandler.cs:30 — src/Marten/Linq/QueryHandlers/LoadByIdArrayHandler.cs:30-41 | src/Marten/Linq/QueryHandlers/LoadByIdHandler.cs:40-50
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×5
  • Duplicated block (11 lines × 2) src/Marten.EntityFrameworkCore/EfCoreMultiStreamProjection.cs:66 — src/Marten.EntityFrameworkCore/EfCoreMultiStreamProjection.cs:66-76 | src/Marten.EntityFrameworkCore/EfCoreSingleStreamProjection.cs:66-76
  • Duplicated block (11 lines × 2) src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:31 — src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:31-41 | src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:252-262
  • Duplicated block (11 lines × 2) src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:61 — src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:61-71 | src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:282-292
  • Duplicated block (11 lines × 2) src/Marten/Internal/ClosedShape/ClosedShapeDirtyTrackingSelector.cs:73 — src/Marten/Internal/ClosedShape/ClosedShapeDirtyTrackingSelector.cs:73-83 | src/Marten/Internal/ClosedShape/ClosedShapeIdentityMapSelector.cs:75-85
  • Duplicated block (11 lines × 2) src/Marten/Patching/PatchExpression.cs:210 — src/Marten/Patching/PatchExpression.cs:210-220 | src/Marten/Patching/PatchExpression.cs:227-236
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×5
  • Duplicated block (10 lines × 2) src/Marten/Events/Fetching/FetchAsyncPlan.ForReading.cs:22 — src/Marten/Events/Fetching/FetchAsyncPlan.ForReading.cs:22-31 | src/Marten/Events/Fetching/FetchLivePlan.ForReading.cs:19-28
  • Duplicated block (10 lines × 2) src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:17 — src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:17-26 | src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:238-247
  • Duplicated block (10 lines × 2) src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:47 — src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:47-56 | src/Marten/Events/TestSupport/ProjectionScenario.EventOperations.cs:268-277
  • Duplicated block (10 lines × 2) src/Marten/Linq/SqlGeneration/SelectorStatement.cs:43 — src/Marten/Linq/SqlGeneration/SelectorStatement.cs:43-52 | src/Marten/Linq/SqlGeneration/StatementOperation.cs:61-70
  • Duplicated block (10 lines × 2) src/Marten/Services/BatchQuerying/BatchedQuery.Events.cs:96 — src/Marten/Services/BatchQuerying/BatchedQuery.Events.cs:96-105 | src/Marten/Services/BatchQuerying/BatchedQuery.Events.cs:161-170
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×5
  • Duplicated block (8 lines × 2) src/Marten/Internal/UnitOfWork.cs:120 — src/Marten/Internal/UnitOfWork.cs:120-126 | src/Marten/Internal/UnitOfWork.cs:145-152
  • Duplicated block (8 lines × 2) src/Marten/Linq/Parsing/GroupBySelectParser.cs:237 — src/Marten/Linq/Parsing/GroupBySelectParser.cs:237-244 | src/Marten/Linq/Parsing/GroupBySelectParser.cs:423-430
  • Duplicated block (8 lines × 2) src/Marten/Linq/Parsing/Methods/IsSubsetOf.cs:26 — src/Marten/Linq/Parsing/Methods/IsSubsetOf.cs:26-33 | src/Marten/Linq/Parsing/Methods/IsSupersetOf.cs:26-32
  • Duplicated block (8 lines × 2) src/Marten/Patching/PatchExpression.cs:155 — src/Marten/Patching/PatchExpression.cs:155-162 | src/Marten/Patching/PatchExpression.cs:181-188
  • Duplicated block (8 lines × 2) src/Marten/Services/MartenActivator.cs:37 — src/Marten/Services/MartenActivator.cs:37-44 | src/Marten/Services/MartenActivator.cs:50-56
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) src/Marten.EntityFrameworkCore/EfCoreMultiStreamProjection.cs:148 — src/Marten.EntityFrameworkCore/EfCoreMultiStreamProjection.cs:148-156 | src/Marten.EntityFrameworkCore/EfCoreSingleStreamProjection.cs:148-156
  • Duplicated block (9 lines × 2) src/Marten/Patching/PatchExpression.cs:143 — src/Marten/Patching/PatchExpression.cs:143-150 | src/Marten/Patching/PatchExpression.cs:168-176
  • Duplicated block (9 lines × 2) src/Marten/Schema/Identity/FSharpDiscriminatedUnionIdGeneration.cs:60 — src/Marten/Schema/Identity/FSharpDiscriminatedUnionIdGeneration.cs:60-68 | src/Marten/Schema/Identity/ValueTypeIdGeneration.cs:133-141
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) src/Marten/Events/Fetching/FetchNaturalKeyPlan.cs:444 — src/Marten/Events/Fetching/FetchNaturalKeyPlan.cs:444-450 | src/Marten/Events/Fetching/FetchNaturalKeyPlan.cs:546-552
  • Duplicated block (7 lines × 2) src/Marten/Events/Fetching/FetchNaturalKeyPlan.cs:511 — src/Marten/Events/Fetching/FetchNaturalKeyPlan.cs:511-517 | src/Marten/Events/Fetching/FetchNaturalKeyPlan.cs:565-571
  • Duplicated block (7 lines × 2) src/Marten/Events/Projections/MultiStreamProjection.cs:58 — src/Marten/Events/Projections/MultiStreamProjection.cs:58-64 | src/Marten/Events/Projections/MultiStreamProjection.cs:67-73
D17 · Explicit Debt · BareSuppressMessage · ×2
  • BareSuppressMessage src/Marten.Testing/GlobalSuppressions.cs:5 — System.Diagnostics.CodeAnalysis.SuppressMessage
  • BareSuppressMessage src/Marten.Testing/GlobalSuppressions.cs:5 — System.Diagnostics.CodeAnalysis.SuppressMessage
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: Schema/DocumentMapping.cs src/Marten/Schema/DocumentMapping.cs:0 — FileTooLong — 537 lines, 0 methods.
  • FileTooLong: Schema/DocumentMapping.cs src/Marten/Schema/DocumentMapping.cs:0 — FileTooLong — 537 lines, 0 methods.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×2
  • Duplicated block (23 lines × 2) src/Marten/EventStorage/Quick/QuickAppendEventsOperation.cs:45 — src/Marten/EventStorage/Quick/QuickAppendEventsOperation.cs:45-67 | src/Marten/EventStorage/QuickWithServerTimestamps/QuickAppendEventsWithServerTimestampsOperation.cs:38-56
  • Duplicated block (23 lines × 2) src/Marten/Linq/Parsing/Methods/EnumerableContains.cs:50 — src/Marten/Linq/Parsing/Methods/EnumerableContains.cs:50-70 | src/Marten/Linq/Parsing/Methods/MemoryExtensionsContains.cs:35-57
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×2
  • Duplicated block (19 lines × 3) src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:225 — src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:225-243 | src/Marten/Internal/Sessions/ExternalTransaction.cs:191-209 | src/Marten/Internal/Sessions/TransactionalConnection.cs:319-337
  • Duplicated block (19 lines × 3) src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:264 — src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:264-282 | src/Marten/Internal/Sessions/ExternalTransaction.cs:230-248 | src/Marten/Internal/Sessions/TransactionalConnection.cs:358-376
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) src/Marten/Events/Daemon/Coordination/ExplicitProjectionCoordinator.cs:108 — src/Marten/Events/Daemon/Coordination/ExplicitProjectionCoordinator.cs:108-125 | src/Marten/Events/Daemon/Coordination/ProjectionCoordinator.cs:156-173
  • Duplicated block (18 lines × 2) src/Marten.PostGIS/PostGISExtensions.cs:139 — src/Marten.PostGIS/PostGISExtensions.cs:139-156 | src/Marten.PostGIS/PostGISExtensions.cs:182-199
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • Duplicated block (17 lines × 2) src/Marten/Internal/ClosedShape/ClosedShapeDirtyTrackingSelector.cs:54 — src/Marten/Internal/ClosedShape/ClosedShapeDirtyTrackingSelector.cs:54-65 | src/Marten/Internal/ClosedShape/ClosedShapeIdentityMapSelector.cs:52-68
  • Duplicated block (17 lines × 2) src/Marten/Internal/ClosedShape/OptimisticClosedShapeUpdateOperation.cs:47 — src/Marten/Internal/ClosedShape/OptimisticClosedShapeUpdateOperation.cs:47-63 | src/Marten/Internal/ClosedShape/OptimisticClosedShapeUpsertOperation.cs:49-65
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) src/Marten/Events/Operations/EventTagOperations.cs:51 — src/Marten/Events/Operations/EventTagOperations.cs:51-63 | src/Marten/Events/Operations/EventTagOperations.cs:87-99
  • Duplicated block (13 lines × 2) src/Marten/Linq/SoftDeletes/DeletedBeforeParser.cs:30 — src/Marten/Linq/SoftDeletes/DeletedBeforeParser.cs:30-42 | src/Marten/Linq/SoftDeletes/DeletedSinceParser.cs:30-42
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) src/Marten/Internal/ClosedShape/ClosedShapeInsertOperation.cs:89 — src/Marten/Internal/ClosedShape/ClosedShapeInsertOperation.cs:89-99 | src/Marten/Internal/ClosedShape/ClosedShapeOverwriteOperation.cs:72-82 | src/Marten/Internal/ClosedShape/ClosedShapeUpsertOperation.cs:76-86
  • Duplicated block (11 lines × 3) src/Marten/Internal/ClosedShape/OptimisticClosedShapeOverwriteOperation.cs:68 — src/Marten/Internal/ClosedShape/OptimisticClosedShapeOverwriteOperation.cs:68-78 | src/Marten/Internal/ClosedShape/OptimisticClosedShapeUpdateOperation.cs:87-97 | src/Marten/Internal/ClosedShape/OptimisticClosedShapeUpsertOperation.cs:89-99
D1 · Cyclomatic Complexity · DocumentStorageDescriptorBuilder.Build (cyclomatic 35) · ×1
  • DocumentStorageDescriptorBuilder.Build (cyclomatic 35) src/Marten/Internal/ClosedShape/DocumentStorageDescriptorBuilder.cs:19 — DocumentStorageDescriptorBuilder.Build has cyclomatic complexity 35 (threshold 15).
D1 · Cyclomatic Complexity · CollectionUsage.CompileGroupJoin (cyclomatic 28) · ×1
  • CollectionUsage.CompileGroupJoin (cyclomatic 28) src/Marten/Linq/CollectionUsage.Compilation.cs:323 — CollectionUsage.CompileGroupJoin has cyclomatic complexity 28 (threshold 15).
D1 · Cyclomatic Complexity · StoreOptions.CreateQueryableMember (cyclomatic 24) · ×1
  • StoreOptions.CreateQueryableMember (cyclomatic 24) src/Marten/StoreOptions.MemberFactory.cs:34 — StoreOptions.CreateQueryableMember has cyclomatic complexity 24 (threshold 15).
D1 · Cyclomatic Complexity · DropCycleCommand.Execute (cyclomatic 23) · ×1
  • DropCycleCommand.Execute (cyclomatic 23) src/Marten.ScaleTesting/Commands/DropCycleCommand.cs:56 — DropCycleCommand.Execute has cyclomatic complexity 23 (threshold 15).
D1 · Cyclomatic Complexity · CollectionUsage.ProcessSingleValueModeIfAny (cyclomatic 22) · ×1
  • CollectionUsage.ProcessSingleValueModeIfAny (cyclomatic 22) src/Marten/Linq/CollectionUsage.Compilation.cs:811 — CollectionUsage.ProcessSingleValueModeIfAny has cyclomatic complexity 22 (threshold 15).
D1 · Cyclomatic Complexity · CollectionUsage.CompileGroupBy (cyclomatic 20) · ×1
  • CollectionUsage.CompileGroupBy (cyclomatic 20) src/Marten/Linq/CollectionUsage.Compilation.cs:614 — CollectionUsage.CompileGroupBy has cyclomatic complexity 20 (threshold 15).
D1 · Cyclomatic Complexity · SimpleExpression.VisitMethodCall (cyclomatic 19) · ×1
  • SimpleExpression.VisitMethodCall (cyclomatic 19) src/Marten/Linq/Parsing/SimpleExpression.cs:309 — SimpleExpression.VisitMethodCall has cyclomatic complexity 19 (threshold 15).
D1 · Cyclomatic Complexity · NpgsqlTypeMap.ResolveSimple (cyclomatic 17) · ×1
  • NpgsqlTypeMap.ResolveSimple (cyclomatic 17) src/Marten.SourceGenerator/NpgsqlTypeMap.cs:32 — NpgsqlTypeMap.ResolveSimple has cyclomatic complexity 17 (threshold 15).
D1 · Cyclomatic Complexity · NamedParameterHelper.AppendSqlWithNamedParameters (cyclomatic 17) · ×1
  • NamedParameterHelper.AppendSqlWithNamedParameters (cyclomatic 17) src/Marten/Linq/QueryHandlers/NamedParameterHelper.cs:29 — NamedParameterHelper.AppendSqlWithNamedParameters has cyclomatic complexity 17 (threshold 15).
D1 · Cyclomatic Complexity · DocumentTable.DocumentTable.ctor (cyclomatic 16) · ×1
  • DocumentTable.DocumentTable.ctor (cyclomatic 16) src/Marten/Storage/DocumentTable.cs:18 — DocumentTable.DocumentTable.ctor has cyclomatic complexity 16 (threshold 15).
D1 · Cyclomatic Complexity · GenericsExtensions.BuildUnwrapper (cyclomatic 16) · ×1
  • GenericsExtensions.BuildUnwrapper (cyclomatic 16) src/Marten/Util/GenericsExtensions.cs:45 — GenericsExtensions.BuildUnwrapper has cyclomatic complexity 16 (threshold 15).
D1 · Cyclomatic Complexity · VectorProjection.ApplyEventsAsync (cyclomatic 16) · ×1
  • VectorProjection.ApplyEventsAsync (cyclomatic 16) src/Marten.PgVector/Projection/VectorProjection.cs:86 — VectorProjection.ApplyEventsAsync has cyclomatic complexity 16 (threshold 15).
D15 · Churn × Complexity Hotspots · git history depth insufficient · ×1
  • git history depth insufficient — git history depth insufficient — install a full clone for reliable trend signal.
D16 · Bus Factor · single-maintainer · ×1
  • single-maintainer — knowledge-concentration (bus factor) risk — single-maintainer — knowledge-concentration (bus factor) risk (0 author(s) across 0 commit(s) sampled).
D18 · Solution Shape · Monorepo · ×1
  • 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/samples/Helpdesk/Helpdesk.sln` — the other 1 (`docs/src/samples/FreightShipping/FreightShipping.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.
D18 · Solution Shape · Analyzed solution does not cover the bulk of the repository · ×1
  • Analyzed solution does not cover the bulk of the repository — The scored solution `src/samples/Helpdesk/Helpdesk.sln` is not representative of this repository — it references only 25 of 2495 discovered C# files (1 %). Lenses that need the product's source (domain modelling, event-driven, event sourcing) abstain because the aggregates, EF configs, and domain events under the product tree were not loaded. Point the scan at the product solution (or scan its directory directly) so the whole codebase is analyzed, not a build-tooling sub-solution.
D2 · Cognitive Complexity · DocumentStorageDescriptorBuilder.Build (cognitive 47) · ×1
  • DocumentStorageDescriptorBuilder.Build (cognitive 47) src/Marten/Internal/ClosedShape/DocumentStorageDescriptorBuilder.cs:19 — DocumentStorageDescriptorBuilder.Build has cognitive complexity 47 (threshold 15).
D2 · Cognitive Complexity · CollectionUsage.CompileGroupJoin (cognitive 43) · ×1
  • CollectionUsage.CompileGroupJoin (cognitive 43) src/Marten/Linq/CollectionUsage.Compilation.cs:323 — CollectionUsage.CompileGroupJoin has cognitive complexity 43 (threshold 15).
D2 · Cognitive Complexity · DropCycleCommand.Execute (cognitive 31) · ×1
  • DropCycleCommand.Execute (cognitive 31) src/Marten.ScaleTesting/Commands/DropCycleCommand.cs:56 — DropCycleCommand.Execute has cognitive complexity 31 (threshold 15).
D2 · Cognitive Complexity · CollectionUsage.CompileGroupBy (cognitive 28) · ×1
  • CollectionUsage.CompileGroupBy (cognitive 28) src/Marten/Linq/CollectionUsage.Compilation.cs:614 — CollectionUsage.CompileGroupBy has cognitive complexity 28 (threshold 15).
D2 · Cognitive Complexity · StoreOptions.CreateQueryableMember (cognitive 28) · ×1
  • StoreOptions.CreateQueryableMember (cognitive 28) src/Marten/StoreOptions.MemberFactory.cs:34 — StoreOptions.CreateQueryableMember has cognitive complexity 28 (threshold 15).
D2 · Cognitive Complexity · JoinSelectParser.StripGroupJoinNavigation (cognitive 27) · ×1
  • JoinSelectParser.StripGroupJoinNavigation (cognitive 27) src/Marten/Linq/Parsing/JoinSelectParser.cs:241 — JoinSelectParser.StripGroupJoinNavigation has cognitive complexity 27 (threshold 15).
D2 · Cognitive Complexity · NamedParameterHelper.AppendSqlWithNamedParameters (cognitive 27) · ×1
  • NamedParameterHelper.AppendSqlWithNamedParameters (cognitive 27) src/Marten/Linq/QueryHandlers/NamedParameterHelper.cs:29 — NamedParameterHelper.AppendSqlWithNamedParameters has cognitive complexity 27 (threshold 15).
D2 · Cognitive Complexity · SelectorStatement.compileAnySubQueries (cognitive 27) · ×1
  • SelectorStatement.compileAnySubQueries (cognitive 27) src/Marten/Linq/SqlGeneration/SelectorStatement.cs:153 — SelectorStatement.compileAnySubQueries has cognitive complexity 27 (threshold 15).
D2 · Cognitive Complexity · QueryMemberClassifier.EnumerateMembers (cognitive 26) · ×1
  • QueryMemberClassifier.EnumerateMembers (cognitive 26) src/Marten.SourceGenerator/QueryMemberClassifier.cs:159 — QueryMemberClassifier.EnumerateMembers has cognitive complexity 26 (threshold 15).
D2 · Cognitive Complexity · EventBoundary.RouteEventByTags (cognitive 26) · ×1
  • EventBoundary.RouteEventByTags (cognitive 26) src/Marten/Events/Dcb/EventBoundary.cs:58 — EventBoundary.RouteEventByTags has cognitive complexity 26 (threshold 15).
D2 · Cognitive Complexity · CollectionUsage.ProcessSingleValueModeIfAny (cognitive 25) · ×1
  • CollectionUsage.ProcessSingleValueModeIfAny (cognitive 25) src/Marten/Linq/CollectionUsage.Compilation.cs:811 — CollectionUsage.ProcessSingleValueModeIfAny has cognitive complexity 25 (threshold 15).
D2 · Cognitive Complexity · BulkEventAppender.writeEventRow (cognitive 24) · ×1
  • BulkEventAppender.writeEventRow (cognitive 24) src/Marten/Events/BulkEventAppender.cs:318 — BulkEventAppender.writeEventRow has cognitive complexity 24 (threshold 15).
D2 · Cognitive Complexity · EventLoader.loadWithWindowStepAsync (cognitive 24) · ×1
  • EventLoader.loadWithWindowStepAsync (cognitive 24) src/Marten/Events/Daemon/Internals/EventLoader.cs:378 — EventLoader.loadWithWindowStepAsync has cognitive complexity 24 (threshold 15).
D2 · Cognitive Complexity · VectorProjection.ApplyEventsAsync (cognitive 24) · ×1
  • VectorProjection.ApplyEventsAsync (cognitive 24) src/Marten.PgVector/Projection/VectorProjection.cs:86 — VectorProjection.ApplyEventsAsync has cognitive complexity 24 (threshold 15).
D2 · Cognitive Complexity · EventStore.BuildTagQuerySql (cognitive 22) · ×1
  • EventStore.BuildTagQuerySql (cognitive 22) src/Marten/Events/EventStore.Dcb.cs:111 — EventStore.BuildTagQuerySql has cognitive complexity 22 (threshold 15).
D2 · Cognitive Complexity · EventsTable.EventsTable.ctor (cognitive 22) · ×1
  • EventsTable.EventsTable.ctor (cognitive 22) src/Marten/Events/Schema/EventsTable.cs:16 — EventsTable.EventsTable.ctor has cognitive complexity 22 (threshold 15).
D2 · Cognitive Complexity · CompiledQueryPlan.MatchParameters (cognitive 22) · ×1
  • CompiledQueryPlan.MatchParameters (cognitive 22) src/Marten/Internal/CompiledQueries/CompiledQueryPlan.cs:380 — CompiledQueryPlan.MatchParameters has cognitive complexity 22 (threshold 15).
D2 · Cognitive Complexity · DuplicatedField.DuplicatedField.ctor (cognitive 22) · ×1
  • DuplicatedField.DuplicatedField.ctor (cognitive 22) src/Marten/Linq/Members/DuplicatedField.cs:30 — DuplicatedField.DuplicatedField.ctor has cognitive complexity 22 (threshold 15).
D2 · Cognitive Complexity · AnySubQueryParser.Parse (cognitive 20) · ×1
  • AnySubQueryParser.Parse (cognitive 20) src/Marten/Linq/Parsing/Methods/AnySubQueryParser.cs:38 — AnySubQueryParser.Parse has cognitive complexity 20 (threshold 15).
D2 · Cognitive Complexity · DocumentTable.DocumentTable.ctor (cognitive 19) · ×1
  • DocumentTable.DocumentTable.ctor (cognitive 19) src/Marten/Storage/DocumentTable.cs:18 — DocumentTable.DocumentTable.ctor has cognitive complexity 19 (threshold 15).
D2 · Cognitive Complexity · TestingExtensions.WaitForNonStaleDataAsync (cognitive 18) · ×1
  • TestingExtensions.WaitForNonStaleDataAsync (cognitive 18) src/Marten/Events/AsyncProjectionTestingExtensions.cs:188 — TestingExtensions.WaitForNonStaleDataAsync has cognitive complexity 18 (threshold 15).
D2 · Cognitive Complexity · HighWaterDetector.calculateHighWaterMark (cognitive 18) · ×1
  • HighWaterDetector.calculateHighWaterMark (cognitive 18) src/Marten/Events/Daemon/HighWater/HighWaterDetector.cs:278 — HighWaterDetector.calculateHighWaterMark has cognitive complexity 18 (threshold 15).
D2 · Cognitive Complexity · EventStore.determineFetchPlan (cognitive 18) · ×1
  • EventStore.determineFetchPlan (cognitive 18) src/Marten/Events/EventStore.FetchForWriting.cs:286 — EventStore.determineFetchPlan has cognitive complexity 18 (threshold 15).
D2 · Cognitive Complexity · QuickAppendEventFunction.WriteCreateStatement (cognitive 18) · ×1
  • QuickAppendEventFunction.WriteCreateStatement (cognitive 18) src/Marten/Events/Schema/QuickAppendEventFunction.cs:22 — QuickAppendEventFunction.WriteCreateStatement has cognitive complexity 18 (threshold 15).
D2 · Cognitive Complexity · CollectionUsage.BuildTopStatement (cognitive 18) · ×1
  • CollectionUsage.BuildTopStatement (cognitive 18) src/Marten/Linq/CollectionUsage.Compilation.cs:31 — CollectionUsage.BuildTopStatement has cognitive complexity 18 (threshold 15).
D2 · Cognitive Complexity · ChildCollectionWhereClause.TryBuildInlineFragment (cognitive 18) · ×1
  • ChildCollectionWhereClause.TryBuildInlineFragment (cognitive 18) src/Marten/Linq/Members/ChildCollectionWhereClause.cs:21 — ChildCollectionWhereClause.TryBuildInlineFragment has cognitive complexity 18 (threshold 15).
D2 · Cognitive Complexity · GroupBySelectParser.TryResolveAggregate (cognitive 18) · ×1
  • GroupBySelectParser.TryResolveAggregate (cognitive 18) src/Marten/Linq/Parsing/GroupBySelectParser.cs:214 — GroupBySelectParser.TryResolveAggregate has cognitive complexity 18 (threshold 15).
D2 · Cognitive Complexity · EventLoader.loadNormalAsync (cognitive 17) · ×1
  • EventLoader.loadNormalAsync (cognitive 17) src/Marten/Events/Daemon/Internals/EventLoader.cs:217 — EventLoader.loadNormalAsync has cognitive complexity 17 (threshold 15).
D2 · Cognitive Complexity · FetchForWritingByTagsHandler.ConfigureCommand (cognitive 17) · ×1
  • FetchForWritingByTagsHandler.ConfigureCommand (cognitive 17) src/Marten/Events/Dcb/FetchForWritingByTagsHandler.cs:38 — FetchForWritingByTagsHandler.ConfigureCommand has cognitive complexity 17 (threshold 15).
D2 · Cognitive Complexity · RichEventAppender.ProcessEventsAsync (cognitive 17) · ×1
  • RichEventAppender.ProcessEventsAsync (cognitive 17) src/Marten/Events/RichEventAppender.cs:17 — RichEventAppender.ProcessEventsAsync has cognitive complexity 17 (threshold 15).
D2 · Cognitive Complexity · CompiledQueryPlan.sortMembers (cognitive 17) · ×1
  • CompiledQueryPlan.sortMembers (cognitive 17) src/Marten/Internal/CompiledQueries/CompiledQueryPlan.cs:68 — CompiledQueryPlan.sortMembers has cognitive complexity 17 (threshold 15).
D2 · Cognitive Complexity · OperationPage.ApplyCallbacksAsync (cognitive 17) · ×1
  • OperationPage.ApplyCallbacksAsync (cognitive 17) src/Marten/Internal/Sessions/OperationPage.cs:68 — OperationPage.ApplyCallbacksAsync has cognitive complexity 17 (threshold 15).
D2 · Cognitive Complexity · CollectionUsage.ParseIncludes (cognitive 17) · ×1
  • CollectionUsage.ParseIncludes (cognitive 17) src/Marten/Linq/CollectionUsage.Includes.cs:28 — CollectionUsage.ParseIncludes has cognitive complexity 17 (threshold 15).
D2 · Cognitive Complexity · AnonProjectionExpander.ExtractBindings (cognitive 17) · ×1
  • AnonProjectionExpander.ExtractBindings (cognitive 17) src/Marten/Linq/Parsing/JoinSelectParser.cs:462 — AnonProjectionExpander.ExtractBindings has cognitive complexity 17 (threshold 15).
D2 · Cognitive Complexity · GenericsExtensions.BuildUnwrapper (cognitive 17) · ×1
  • GenericsExtensions.BuildUnwrapper (cognitive 17) src/Marten/Util/GenericsExtensions.cs:45 — GenericsExtensions.BuildUnwrapper has cognitive complexity 17 (threshold 15).
D2 · Cognitive Complexity · AdvancedOperations.AddMartenManagedTenantsAsync (cognitive 16) · ×1
  • AdvancedOperations.AddMartenManagedTenantsAsync (cognitive 16) src/Marten/AdvancedOperations.cs:397 — AdvancedOperations.AddMartenManagedTenantsAsync has cognitive complexity 16 (threshold 15).
D2 · Cognitive Complexity · ShardStateSelector.ResolveAsync (cognitive 16) · ×1
  • ShardStateSelector.ResolveAsync (cognitive 16) src/Marten/Events/Daemon/Progress/ShardStateSelector.cs:27 — ShardStateSelector.ResolveAsync has cognitive complexity 16 (threshold 15).
D2 · Cognitive Complexity · EventDocumentStorage.ResolveAsync (cognitive 16) · ×1
  • EventDocumentStorage.ResolveAsync (cognitive 16) src/Marten/Events/EventDocumentStorage.cs:381 — EventDocumentStorage.ResolveAsync has cognitive complexity 16 (threshold 15).
D2 · Cognitive Complexity · EventGraph.createAllSchemaObjects (cognitive 16) · ×1
  • EventGraph.createAllSchemaObjects (cognitive 16) src/Marten/Events/EventGraph.FeatureSchema.cs:52 — EventGraph.createAllSchemaObjects has cognitive complexity 16 (threshold 15).
D2 · Cognitive Complexity · QuickEventAppender.registerOperationsForStreams (cognitive 16) · ×1
  • QuickEventAppender.registerOperationsForStreams (cognitive 16) src/Marten/Events/QuickEventAppender.cs:25 — QuickEventAppender.registerOperationsForStreams has cognitive complexity 16 (threshold 15).
D2 · Cognitive Complexity · DocumentStorageDescriptorBuilder.BuildUpdateSql (cognitive 16) · ×1
  • DocumentStorageDescriptorBuilder.BuildUpdateSql (cognitive 16) src/Marten/Internal/ClosedShape/DocumentStorageDescriptorBuilder.cs:525 — DocumentStorageDescriptorBuilder.BuildUpdateSql has cognitive complexity 16 (threshold 15).
D2 · Cognitive Complexity · SourceGeneratedCompiledQueryHandlerBase.ConfigureCommand (cognitive 16) · ×1
  • SourceGeneratedCompiledQueryHandlerBase.ConfigureCommand (cognitive 16) src/Marten/Internal/CompiledQueries/SourceGeneratedCompiledQuery.cs:59 — SourceGeneratedCompiledQueryHandlerBase.ConfigureCommand has cognitive complexity 16 (threshold 15).
D2 · Cognitive Complexity · GroupJoinOuterNavigationStripper.FindOuterMember (cognitive 16) · ×1
  • GroupJoinOuterNavigationStripper.FindOuterMember (cognitive 16) src/Marten/Linq/Parsing/JoinSelectParser.cs:608 — GroupJoinOuterNavigationStripper.FindOuterMember has cognitive complexity 16 (threshold 15).
D2 · Cognitive Complexity · UserSuppliedQueryHandler.ConfigureCommand (cognitive 16) · ×1
  • UserSuppliedQueryHandler.ConfigureCommand (cognitive 16) src/Marten/Linq/QueryHandlers/UserSuppliedQueryHandler.cs:46 — UserSuppliedQueryHandler.ConfigureCommand has cognitive complexity 16 (threshold 15).
D2 · Cognitive Complexity · SessionOptions.buildConnectionLifetime (cognitive 16) · ×1
  • SessionOptions.buildConnectionLifetime (cognitive 16) src/Marten/Services/SessionOptions.cs:108 — SessionOptions.buildConnectionLifetime has cognitive complexity 16 (threshold 15).
D36 · Supply-chain Provenance & Signing · Unpinned build actions · ×1
  • Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity.
D4 · Code Duplication · Duplicated block (56 lines × 2) · ×1
  • Duplicated block (56 lines × 2) src/Marten.SourceGenerator/CompiledQuerySourceGenerator.cs:286 — src/Marten.SourceGenerator/CompiledQuerySourceGenerator.cs:286-333 | src/Marten.SourceGenerator/CompiledQuerySourceGenerator.cs:339-394
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) src/Marten/Events/Schema/EventsTable.cs:182 — src/Marten/Events/Schema/EventsTable.cs:182-212 | src/Marten/Events/Schema/StreamsTable.cs:64-90
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) src/Marten/Internal/Storage/LightweightDocumentStorage.cs:61 — src/Marten/Internal/Storage/LightweightDocumentStorage.cs:61-81 | src/Marten/Internal/Storage/QueryOnlyDocumentStorage.cs:46-66
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) src/Marten/Services/BatchQuerying/BatchedQuery.Events.cs:84 — src/Marten/Services/BatchQuerying/BatchedQuery.Events.cs:84-91 | src/Marten/Services/BatchQuerying/BatchedQuery.Events.cs:134-153
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×1
  • Duplicated block (18 lines × 3) src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:187 — src/Marten/Internal/Sessions/AmbientTransactionLifetime.cs:187-204 | src/Marten/Internal/Sessions/ExternalTransaction.cs:153-170 | src/Marten/Internal/Sessions/TransactionalConnection.cs:281-298
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) src/Marten/Linq/Members/DuplicatedField.cs:226 — src/Marten/Linq/Members/DuplicatedField.cs:226-241 | src/Marten/Linq/Members/StringMember.cs:33-48
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) src/Marten/Events/Dcb/EventsExistByTagsHandler.cs:118 — src/Marten/Events/Dcb/EventsExistByTagsHandler.cs:118-131 | src/Marten/Events/Dcb/FetchForWritingByTagsHandler.cs:92-105
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) src/Marten/Internal/ClosedShape/ClosedShapeInsertOperation.cs:121 — src/Marten/Internal/ClosedShape/ClosedShapeInsertOperation.cs:121-133 | src/Marten/Internal/ClosedShape/ClosedShapeOverwriteOperation.cs:108-120 | src/Marten/Internal/ClosedShape/ClosedShapeUpsertOperation.cs:112-124
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) src/Marten/Storage/StorageFeatures.cs:384 — src/Marten/Storage/StorageFeatures.cs:384-391 | src/Marten/Storage/StorageFeatures.cs:392-398 | src/Marten/Storage/StorageFeatures.cs:399-405
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) src/Marten.ScaleTesting/Commands/DropCycleCommand.cs:260 — src/Marten.ScaleTesting/Commands/DropCycleCommand.cs:260-264 | src/Marten.ScaleTesting/Commands/DropCycleCommand.cs:266-270
D5 · Coupling · Unstable project EventPublisher · ×1
  • Unstable project EventPublisher — EventPublisher has instability 1.00 with 0 dependents.
Recommendation — 39 finding(s)
D26 · Project Cohesion · Large project · ×14
  • Large project: Marten(net9.0) — 77873 LoC, 474 public types across 64 namespaces — review for cohesion.
  • Large project: Marten(net10.0) — 77873 LoC, 474 public types across 64 namespaces — review for cohesion.
  • Large project: TenantPartitionedEventsTests(net9.0) — 0 LoC, 167 public types across 13 namespaces — review for cohesion.
  • Large project: TenantPartitionedEventsTests(net10.0) — 0 LoC, 167 public types across 13 namespaces — review for cohesion.
  • Large project: CoreTests(net9.0) — 0 LoC, 286 public types across 19 namespaces — review for cohesion.
  • Large project: CoreTests(net10.0) — 0 LoC, 286 public types across 19 namespaces — review for cohesion.
  • Large project: DaemonTests(net9.0) — 0 LoC, 349 public types across 17 namespaces — review for cohesion.
  • Large project: DaemonTests(net10.0) — 0 LoC, 349 public types across 17 namespaces — review for cohesion.
  • Large project: DocumentDbTests(net9.0) — 0 LoC, 403 public types across 31 namespaces — review for cohesion.
  • Large project: DocumentDbTests(net10.0) — 0 LoC, 403 public types across 31 namespaces — review for cohesion.
  • Large project: EventSourcingTests(net9.0) — 0 LoC, 996 public types across 58 namespaces — review for cohesion.
  • Large project: EventSourcingTests(net10.0) — 0 LoC, 996 public types across 58 namespaces — review for cohesion.
  • Large project: LinqTests(net9.0) — 0 LoC, 403 public types across 13 namespaces — review for cohesion.
  • Large project: LinqTests(net10.0) — 0 LoC, 403 public types across 13 namespaces — review for cohesion.
D10 · Test Quality · No direct assertions · ×7
  • No direct assertions: ResolveCommand_Succeeds src/samples/Helpdesk/Helpdesk.Api.Tests/Incidents/ResolveIncidentTests.cs:13 — In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
  • No direct assertions: PrioritiseCommand_ChangesIncidentPriority src/samples/Helpdesk/Helpdesk.Api.Tests/Incidents/PrioritiseIncidentTests.cs:13 — In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
  • No direct assertions: LogIncident_ShouldSucceed src/samples/Helpdesk/Helpdesk.Api.Tests/Incidents/LogIncidentsTests.cs:15 — In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
  • No direct assertions: ResolveCommand_Succeeds src/samples/Helpdesk/Helpdesk.Api.Tests/Incidents/CloseIncidentTests.cs:12 — In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
  • No direct assertions: CategoriseCommand_ChangesIncidentCategory src/samples/Helpdesk/Helpdesk.Api.Tests/Incidents/CategoriseIncidentTests.cs:13 — In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
  • No direct assertions: AssignAgentCommand_ChangesIncidentCategory src/samples/Helpdesk/Helpdesk.Api.Tests/Incidents/AssignAgentTests.cs:11 — In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
  • No direct assertions: ResolveCommand_Succeeds src/samples/Helpdesk/Helpdesk.Api.Tests/Incidents/AcknowledgeResolutionIncidentTests.cs:11 — In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
D38 · OSV Dependency Vulnerabilities · Low CVE · ×3
  • Low CVE: [GHSA redacted] package-lock.json — esbuild: [GHSA redacted]
  • Low CVE: [GHSA redacted] package-lock.json — vite: [GHSA redacted]
  • Low CVE: [GHSA redacted] package-lock.json — vite: [GHSA redacted]
D31 · IaC & Container Security · Low IaC · ×2
  • Low IaC: DS-0026 docker/postgres/Dockerfile — No HEALTHCHECK defined
  • Low IaC: DS-0026 src/samples/Helpdesk/Helpdesk.Api/Dockerfile — No HEALTHCHECK defined
D11 · Test Reliability · Tier not included (time budget) · ×1
  • Tier not included (time budget) — other: not included — too large to re-run within its budget
D23 · Boundary Type-Coupling · Bounded contexts not declared · ×1
  • Bounded contexts not declared — large codebase (173,789 production LoC) with no declared bounded contexts — cross-boundary type coupling is unassessed Declare architecture.contexts (≥2) in config to assess cross-boundary type coupling.
D27 · Navigability · Navigability unmeasured · ×1
  • Navigability unmeasured — symbol resolution incomplete — 72 % of sampled invocations could not be resolved to a symbol (the workspace likely loaded without all references) — the indirection fractions would be computed over an unrepresentative slice, so navigability is reported as not measured rather than a misleading score.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • Rotate the exposed credentials — git history can't be un-committed — Some of these secrets are in git HISTORY: deleting the file does not remove them (the commit persists on every clone, fork and backup). The remediation is to ROTATE each historically-exposed credential and treat it as compromised — not to delete the file. Rewriting history is disruptive and unreliable across existing forks. (Working-tree-only secrets — no commit — can instead be removed from the file and moved to a secret store.)
D30 · Dependency Vulnerabilities · Not applicable · ×1
  • 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
D32 · Data Compliance (PII/GDPR) · Not applicable · ×1
  • Not applicable — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D34 · Knowledge Freshness · early-stage repository · ×1
  • early-stage repository — too little history to judge knowledge freshness — early-stage repository — too little history to judge knowledge freshness (0 commit(s) sampled).
D36 · Supply-chain Provenance & Signing · No build provenance · ×1
  • No build provenance — No SLSA provenance generation or build attestation found in CI (e.g. slsa-github-generator, actions/attest-build-provenance).
D36 · Supply-chain Provenance & Signing · No artifact signing · ×1
  • No artifact signing — No artifact signing found in CI (e.g. cosign / sigstore / gitsign).
D36 · Supply-chain Provenance & Signing · No SBOM · ×1
  • No SBOM — No SBOM generation or committed SBOM found (e.g. syft / anchore/sbom-action / *.spdx.json / *.cdx.json).
D37 · Vulnerability-disclosure Policy · Not applicable · ×1
  • Not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 · IL Efficiency · IL metrics not applicable · ×1
  • IL metrics not applicable — The target did not build, so no IL was available to measure.
D7 · Architectural Integrity · No checkable ADRs to assess · ×1
  • No checkable ADRs to assess — No architecture decision records were found and the project graph is acyclic, so architectural integrity could not be assessed. Add ADRs (with `enforcement: analyzer|test`) to make the architecture's rules checkable.
Info — 721 finding(s)
D17 · Explicit Debt · Justified suppression · ×671
  • Justified suppression src/Marten.Newtonsoft/MartenNewtonsoftExtensions.cs:36 — #pragma warning disable CA2255 // ModuleInitializer is intentional here — wires up the package's serializer factory + attribute resolver on assembly load.
  • Justified suppression src/Marten.Newtonsoft/MartenNewtonsoftExtensions.cs:36 — #pragma warning disable CA2255 // ModuleInitializer is intentional here — wires up the package's serializer factory + attribute resolver on assembly load.
  • Justified suppression src/Marten.ScaleTesting/Commands/StressCommand.cs:95 — empty catch — narrow/filtered/commented, treated as intentional
  • Justified suppression src/Marten.ScaleTesting/Instrumentation/ProgressionLockSampler.cs:79 — empty catch (Exception) — narrow/filtered/commented, treated as intentional
  • Justified suppression src/Marten.ScaleTesting/Instrumentation/ProgressionLockSampler.cs:97 — empty catch — narrow/filtered/commented, treated as intentional
  • Justified suppression src/Marten.ScaleTesting/Instrumentation/ProgressionLockSampler.cs:137 — empty catch — narrow/filtered/commented, treated as intentional
  • Justified suppression src/Marten.ScaleTesting/Instrumentation/ProgressSampler.cs:68 — empty catch (Exception) — narrow/filtered/commented, treated as intentional
  • Justified suppression src/Marten.ScaleTesting/Instrumentation/ProgressSampler.cs:87 — empty catch — narrow/filtered/commented, treated as intentional
  • Justified suppression src/Marten.ScaleTesting/Instrumentation/ProgressSampler.cs:137 — empty catch — narrow/filtered/commented, treated as intentional
  • Justified suppression src/Marten.ScaleTesting/Seeding/EventSeeder.cs:120 — empty catch (OperationCanceledException) — narrow/filtered/commented, treated as intentional
  • Justified suppression src/Marten.ScaleTesting/Seeding/EventSeeder.cs:281 — empty catch (Npgsql.PostgresException) when (…) — narrow/filtered/commented, treated as intentional
  • Justified suppression src/Marten/DocumentStore.CompiledQueryCollection.cs:21 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/DocumentStore.cs:41 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/DocumentStore.cs:43 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/DocumentStore.cs:45 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/DocumentStore.EventStore.cs:494 — empty catch (Exception) — narrow/filtered/commented, treated as intentional
  • Justified suppression src/Marten/DocumentStore.EventStore.cs:39 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/DocumentStore.EventStoreExplorer.cs:28 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/DocumentStore.EventStoreExplorer.cs:30 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/DocumentStore.EventStoreExplorer.cs:32 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/DocumentStore.EventStoreExplorer.cs:34 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/DocumentStore.EventStoreExplorer.cs:36 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/DocumentStore.EventStoreExplorer.cs:38 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/Events/Aggregation/SingleStreamProjection.cs:23 — UnconditionalSuppressMessage
  • Justified suppression src/Marten/Events/Aggregation/SingleStreamProjection.cs:25 — UnconditionalSuppressMessage
  • + 646 more in this group — see findings.md.
D10 · Test Quality · Skipped (documented) · ×22
  • Skipped (documented): using_auto_create_field src/CoreTests/StoreOptionsTests.cs:53 — Skipped with a documented reason — a deferral, not lazy debt: sample usage code
  • Skipped (documented): using_auto_create_field src/CoreTests/StoreOptionsTests.cs:53 — Skipped with a documented reason — a deferral, not lazy debt: sample usage code
  • Skipped (documented): example_of_using_fi_to_configure src/DocumentDbTests/Deleting/configuring_mapping_deletion_style.cs:53 — Skipped with a documented reason — a deferral, not lazy debt: sample usage code
  • Skipped (documented): example_of_using_fi_to_configure src/DocumentDbTests/Deleting/configuring_mapping_deletion_style.cs:53 — Skipped with a documented reason — a deferral, not lazy debt: sample usage code
  • Skipped (documented): return_correct_data_after_restarts src/EventSourcingTests/Aggregation/explicit_code_for_aggregation_logic.cs:470 — Skipped with a documented reason — a deferral, not lazy debt: Pre-existing master failure (codegen + closed-shape) — soft-delete + restart flow throws ConcurrencyException. Not caused by #4444's UseVersionFromMatchingStream gap. Needs separate triage.
  • Skipped (documented): snapshot_without_source_generator_should_round_trip src/EventSourcingTests/Bugs/Bug_4557_self_aggregating_snapshot_without_source_generator.cs:70 — Skipped with a documented reason — a deferral, not lazy debt: Validated via packaging (see PR); ProjectReference consumers don't receive a NuGet-bundled analyzer.
  • Skipped (documented): auto_discovered_tag_type_works_for_querying_in_hstore_mode src/EventSourcingTests/Dcb/hstore_auto_discover_tag_types_from_projections.cs:80 — Skipped with a documented reason — a deferral, not lazy debt: Pre-existing master failure (codegen + closed-shape) — inline-projection save raises ConcurrencyException for HsTicketSummary. Hstore tag-based aggregation interacts badly with revision tracking on the projection target. Unrelated to #4444's UseVersionFromMatchingStream gap; needs separate triage.
  • Skipped (documented): auto_discovered_tag_type_works_for_fetch_for_writing_in_hstore_mode src/EventSourcingTests/Dcb/hstore_auto_discover_tag_types_from_projections.cs:105 — Skipped with a documented reason — a deferral, not lazy debt: Pre-existing master failure (codegen + closed-shape) — inline-projection save raises ConcurrencyException for HsTicketSummary. Hstore tag-based aggregation interacts badly with revision tracking on the projection target. Unrelated to #4444's UseVersionFromMatchingStream gap; needs separate triage.
  • Skipped (documented): throw_transformed_exception_with_details_redacted src/EventSourcingTests/EventStreamUnexpectedMaxEventIdExceptionTransformTest.cs:19 — Skipped with a documented reason — a deferral, not lazy debt: TODO -- too unreliable on CI
  • Skipped (documented): throw_transformed_exception_with_details_available src/EventSourcingTests/EventStreamUnexpectedMaxEventIdExceptionTransformTest.cs:45 — Skipped with a documented reason — a deferral, not lazy debt: TODO -- too unreliable on CI
  • Skipped (documented): stream_id_is_set_as_string src/EventSourcingTests/Projections/stream_aggregation.cs:80 — Skipped with a documented reason — a deferral, not lazy debt: 9.0: runtime `Schema.For<T>().Identity(x => x.Key)` overrides aren't visible to the source generator at compile time, so the generated dispatcher is still keyed on (SpecialUsages, Guid) — the aggregate's `Id` property. Users with this pattern can annotate the override member with `[Identity]` instead, which the SG picks up. See the 9.0 migration guide.
  • Skipped (documented): return_correct_data_after_restarts src/EventSourcingTests/Aggregation/explicit_code_for_aggregation_logic.cs:470 — Skipped with a documented reason — a deferral, not lazy debt: Pre-existing master failure (codegen + closed-shape) — soft-delete + restart flow throws ConcurrencyException. Not caused by #4444's UseVersionFromMatchingStream gap. Needs separate triage.
  • Skipped (documented): snapshot_without_source_generator_should_round_trip src/EventSourcingTests/Bugs/Bug_4557_self_aggregating_snapshot_without_source_generator.cs:70 — Skipped with a documented reason — a deferral, not lazy debt: Validated via packaging (see PR); ProjectReference consumers don't receive a NuGet-bundled analyzer.
  • Skipped (documented): auto_discovered_tag_type_works_for_querying_in_hstore_mode src/EventSourcingTests/Dcb/hstore_auto_discover_tag_types_from_projections.cs:80 — Skipped with a documented reason — a deferral, not lazy debt: Pre-existing master failure (codegen + closed-shape) — inline-projection save raises ConcurrencyException for HsTicketSummary. Hstore tag-based aggregation interacts badly with revision tracking on the projection target. Unrelated to #4444's UseVersionFromMatchingStream gap; needs separate triage.
  • Skipped (documented): auto_discovered_tag_type_works_for_fetch_for_writing_in_hstore_mode src/EventSourcingTests/Dcb/hstore_auto_discover_tag_types_from_projections.cs:105 — Skipped with a documented reason — a deferral, not lazy debt: Pre-existing master failure (codegen + closed-shape) — inline-projection save raises ConcurrencyException for HsTicketSummary. Hstore tag-based aggregation interacts badly with revision tracking on the projection target. Unrelated to #4444's UseVersionFromMatchingStream gap; needs separate triage.
  • Skipped (documented): throw_transformed_exception_with_details_redacted src/EventSourcingTests/EventStreamUnexpectedMaxEventIdExceptionTransformTest.cs:19 — Skipped with a documented reason — a deferral, not lazy debt: TODO -- too unreliable on CI
  • Skipped (documented): throw_transformed_exception_with_details_available src/EventSourcingTests/EventStreamUnexpectedMaxEventIdExceptionTransformTest.cs:45 — Skipped with a documented reason — a deferral, not lazy debt: TODO -- too unreliable on CI
  • Skipped (documented): stream_id_is_set_as_string src/EventSourcingTests/Projections/stream_aggregation.cs:80 — Skipped with a documented reason — a deferral, not lazy debt: 9.0: runtime `Schema.For<T>().Identity(x => x.Key)` overrides aren't visible to the source generator at compile time, so the generated dispatcher is still keyed on (SpecialUsages, Guid) — the aggregate's `Id` property. Users with this pattern can annotate the override member with `[Identity]` instead, which the SG picks up. See the 9.0 migration guide.
  • Skipped (documented): Can_query_by_hashset_contains src/LinqTests/Bugs/hashset_contains.cs:12 — Skipped with a documented reason — a deferral, not lazy debt: TODO: Fix it on the linq branch
  • Skipped (documented): Can_query_by_hashset_contains src/LinqTests/Bugs/hashset_contains.cs:12 — Skipped with a documented reason — a deferral, not lazy debt: TODO: Fix it on the linq branch
  • Skipped (documented): can_support_parallel_processing src/PatchingTests/Patching/Bug_2460_parallel_patching.cs:20 — Skipped with a documented reason — a deferral, not lazy debt: Fix in https://github.com/JasperFx/marten/pull/2468
  • Skipped (documented): can_support_parallel_processing src/PatchingTests/Patching/Bug_2460_parallel_patching.cs:20 — Skipped with a documented reason — a deferral, not lazy debt: Fix in https://github.com/JasperFx/marten/pull/2468
D10 · Test Quality · Mock framework · ×16
  • Mock framework: NSubstitute — ContainerScopedProjectionTests(net9.0) references NSubstitute.
  • Mock framework: NSubstitute — ContainerScopedProjectionTests(net10.0) references NSubstitute.
  • Mock framework: NSubstitute — CoreTests(net9.0) references NSubstitute.
  • Mock framework: NSubstitute — CoreTests(net10.0) references NSubstitute.
  • Mock framework: NSubstitute — DocumentDbTests(net9.0) references NSubstitute.
  • Mock framework: NSubstitute — DocumentDbTests(net10.0) references NSubstitute.
  • Mock framework: NSubstitute — EventSourcingTests(net9.0) references NSubstitute.
  • Mock framework: NSubstitute — EventSourcingTests(net10.0) references NSubstitute.
  • Mock framework: NSubstitute — LinqTests(net9.0) references NSubstitute.
  • Mock framework: NSubstitute — LinqTests(net10.0) references NSubstitute.
  • Mock framework: NSubstitute — Marten.Testing(net9.0) references NSubstitute.
  • Mock framework: NSubstitute — Marten.Testing(net10.0) references NSubstitute.
  • Mock framework: NSubstitute — MultiTenancyTests(net9.0) references NSubstitute.
  • Mock framework: NSubstitute — MultiTenancyTests(net10.0) references NSubstitute.
  • Mock framework: NSubstitute — StressTests(net9.0) references NSubstitute.
  • Mock framework: NSubstitute — StressTests(net10.0) references NSubstitute.
D14 · License Compliance · Licenses scanned · ×1
  • Licenses scanned — 72 packages scanned; 4 distinct SPDX licenses.
D18 · Solution Shape · Build status unknown · ×1
  • Build status unknown — The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
D18 · Solution Shape · Helpdesk.Api (Production) · ×1
  • Helpdesk.Api (Production) src/samples/Helpdesk/Helpdesk.Api/Helpdesk.Api.csproj — 12 .cs files, 1126 LoC (898 significant)
D18 · Solution Shape · Helpdesk.Api.Tests (Test) · ×1
  • Helpdesk.Api.Tests (Test) src/samples/Helpdesk/Helpdesk.Api.Tests/Helpdesk.Api.Tests.csproj — 16 .cs files, 654 LoC (536 significant)
D18 · Solution Shape · Marten(net9.0) (Production) · ×1
  • Marten(net9.0) (Production) src/Marten/Marten.csproj — 911 .cs files, 92637 LoC (62478 significant)
D18 · Solution Shape · Marten(net10.0) (Production) · ×1
  • Marten(net10.0) (Production) src/Marten/Marten.csproj — 911 .cs files, 92637 LoC (62478 significant)
D18 · Solution Shape · Marten.AspNetCore(net9.0) (Production) · ×1
  • Marten.AspNetCore(net9.0) (Production) src/Marten.AspNetCore/Marten.AspNetCore.csproj — 9 .cs files, 1081 LoC (607 significant)
D18 · Solution Shape · Marten.AspNetCore(net10.0) (Production) · ×1
  • Marten.AspNetCore(net10.0) (Production) src/Marten.AspNetCore/Marten.AspNetCore.csproj — 9 .cs files, 1081 LoC (607 significant)
D9 · Test Distribution · Unit tests · ×1
  • Unit tests — 8840 unit test method(s).
D9 · Test Distribution · Integration tests · ×1
  • Integration tests — 0 integration test method(s).
D9 · Test Distribution · BDD tests · ×1
  • BDD tests — 0 BDD test method(s).
D9 · Test Distribution · E2E tests · ×1
  • E2E tests — 0 end-to-end test method(s).

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source .3artifacts/raw/gitleaks-history.json
D29 · Static Analysis (SAST)semgrep—semgrep --config auto --json --quiet --timeout 0 --metrics off .0—
D30 · Dependency Vulnerabilitiesdotnet—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 solution0—
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .4artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.0—
D33 · JS/npm Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D38 · OSV Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive .21artifacts/raw/osv-scanner.json

Run 019ee37b-1326-799f-b874-985d560d3e06 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 24 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by name with a deliberately specific classifier (the same one the GDPR dimensions use, so CardDefinition or FileName don't trip); informational — it feeds no score.

Name — 22 field(s)
  • CreateUserRequest.FirstName src/AspNetCoreWithMarten/Program.cs:88
  • CreateUserRequest.LastName src/AspNetCoreWithMarten/Program.cs:88
  • User.FirstName src/AspNetCoreWithMarten/User.cs:7
  • User.LastName src/AspNetCoreWithMarten/User.cs:8
  • FindUserByAllTheThings.FirstName src/CommandLineRunner/FindUserByAllTheThings.cs:12
  • FindUserByAllTheThings.LastName src/CommandLineRunner/FindUserByAllTheThings.cs:13
  • FindUserOtherThings.FirstName src/CommandLineRunner/FindUserByAllTheThings.cs:28
  • FindUserOtherThings.LastName src/CommandLineRunner/FindUserByAllTheThings.cs:29
  • Patient.FirstName src/Marten.ScaleTesting/Domain/ReferenceData.cs:9
  • Patient.LastName src/Marten.ScaleTesting/Domain/ReferenceData.cs:10
  • Provider.FirstName src/Marten.ScaleTesting/Domain/ReferenceData.cs:25
  • Provider.LastName src/Marten.ScaleTesting/Domain/ReferenceData.cs:26
  • AppointmentDetails.PatientFirstName src/Marten.ScaleTesting/Domain/Stage2Projections.cs:34
  • AppointmentDetails.PatientLastName src/Marten.ScaleTesting/Domain/Stage2Projections.cs:35
  • AppointmentDetails.ProviderFirstName src/Marten.ScaleTesting/Domain/Stage2Projections.cs:44
  • AppointmentDetails.ProviderLastName src/Marten.ScaleTesting/Domain/Stage2Projections.cs:45
  • ProviderUtilization.ProviderFirstName src/Marten.ScaleTesting/Domain/Stage3Projections.cs:33
  • ProviderUtilization.ProviderLastName src/Marten.ScaleTesting/Domain/Stage3Projections.cs:34
  • User.FirstName src/Marten.Testing/Documents/User.cs:41
  • User.LastName src/Marten.Testing/Documents/User.cs:42
  • User.FullName src/Marten.Testing/Documents/User.cs:47
  • DotNetTypeArgument._fullName src/Marten/Schema/Arguments/DotNetTypeArgument.cs:12
Address — 2 field(s)
  • Address.PostalCode src/Marten.Testing/Documents/Target.cs:293
  • Address.PostalCode src/Marten.Testing/Documents/TargetIntId.cs:150

Issues: 527 · Warnings: 556 · Recommendations: 39 · Info: 721 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 20-06-2026 @ 05:22 UTC.

Downloadable artifacts

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

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