Chronicle — Watchdog Audit

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.

Cratis/Chronicle carries serious risk (38%). Several issues below can materially affect reliability, security, or the cost of change and warrant near-term attention.

The area that most needs attention is Readiness (30%) — operating, monitoring and recovering the system safely is harder. Code Health (38%) is the next concern — changes there are slower and more error-prone.

Leadership focus, highest impact first: tests that import the unreached modules (directly or through… (Test Coverage); unused dependencies, declare unlisted imports explicitly,… (Dependency Hygiene); `AddStandardResilienceHandler()` (or Polly policies) to your… (Outbound HTTP resilience).

For scale: Medium (~59,077 production lines); rebuilding it from scratch would take roughly ~1.7 person-years (~1–4 engineers). Approximate, ±~30%.

Code Health 38% Weak · gated by D17, R7 Architecture 83% Strong Maturity 65% Adequate Readiness 30% Weak · gated by D13, R4, R8, P7 Security 48% Weak · gated by D36, D38, C2 Accessibility 45% Weak · gated by AC4 Performance 47% Weak · gated by PF3

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.

Readiness 30% · 46% weightCode Health 38% · 25% weightAccessibility 45% · 14% weightPerformance 47% · 8% weightSecurity 48% · 4% weightMaturity 65% · 2% weightArchitecture 83% · 1% weight

Raise Readiness 30 → 70 (the Healthy floor) ⇒ headline 38 → ~44.

Code composition — where the lines go

Business logic 6%Plumbing 22%Tests 71%Generated 0%Analyzers 1%

New since the last scan (2+)

2 finding(s) are new versus the previous scan (2026-06-20) — surfaced by this scheduled scan itself, no pull request required.

D4 · Duplicated block (15 lines × 2) Source/Kernel/Storage.MongoDB/Sinks/Sink.cs ↻ reappeared after being resolved
D5 · Off the main sequence: AspNetCore ↻ reappeared after being resolved

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €80,000–€400,000

Cost to rebuild	€80,000–€400,000 (0.8–2.5 person-years (1,337–4,233 h), ~1–4 engineers)
Domain complexity	High — harder problems cost more per line
Quality factor	0.7× (at 38% quality) — the last 20% of quality is most of the work
Size & shape	Medium · 62% boilerplate · 15% straight-line · 22% branching logic
Dead frontend code	~11425 LoC unreachable (180 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)

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

How we model this: boilerplate at a scaffolding rate + logic × domain High (×1.3) — microservices × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with run-mssql.sh, run.sh.

+7.0 pts · Low effort · Secret Scanning

Add tests that import the unreached modules (directly or through their public entry).

+7.3 pts · Medium effort · Test Coverage

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

+7.3 pts · Medium effort · Dependency Hygiene

Diagnosis — what's actually going on

Value concentrated against a weak lens · High · Value at risk

This is a Medium asset (~1.7 person-years to rebuild), and its weakest lens is Readiness at 30%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Medium, ~1.7 person-years rebuild (59,077 LoC) · weakest lens: Readiness 30%

→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Add tests that import the unreached modules (directly or through their public entry). The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Add tests that import the unreached modules (directly or through their public entry).

Improving trajectory · Info · Trajectory

The headline is improving steadily (+3.6 pts/run over 6 runs) — whatever you're doing is working; keep the gate.

Evidence: trajectory: +3.6 pts/run over 6 runs

Trajectory

The Ugly

PF3 · Repo Async & latency hygiene 2.3

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A06:2021 — Vulnerable & Outdated Components	53	High / Critical
A05:2021 — Security Misconfiguration	13	High / Critical
A02:2021 — Cryptographic Failures	7	High / Critical

Roadmap

Top priorities: Add tests that import the unreached modules (directly or through their public entry); Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.

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

Do this	Helps	Effort	Dimension
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with run-mssql.sh, run.sh.	+7.0 pts	Low	Secret Scanning
Add tests that import the unreached modules (directly or through their public entry).	+7.3 pts	Medium	Test Coverage
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+7.3 pts	Medium	Dependency Hygiene
Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.	+7.3 pts	Medium	Outbound HTTP resilience
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.	+7.0 pts	Medium	Release Hygiene
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.	+6.7 pts	Medium	Library API & versioning
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.	+6.4 pts	Medium	Deployment & Rollback
Resolve the 21 Deprecated finding(s) in Dependency Hygiene.	+6.3 pts	Medium	Dependency Hygiene

File quality

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

File	Score	Band	Worst signal
Source/Workbench/yarn.lock	0.0	Slop	JS/npm Dependency Vulnerabilities: High CVE: [CVE redacted]
Docker/Local/Dockerfile	4.4	Mixed	IaC & Container Security: High IaC: DS-0002
Integration/Client/Projections/Scenarios/when_projecting_with_children_within_children_using_parent_key_from_context/and_all_events_are_appended_in_one_transaction.cs	5.3	Mixed	Test Quality: No assertions: should_have_no_failed_partitions
Integration/Client/Projections/Scenarios/when_projecting_with_children_within_children_using_parent_key_from_context/and_metric_event_arrives_before_hub_is_added.cs	5.3	Mixed	Test Quality: No assertions: should_have_no_failed_partitions
Integration/Client/Projections/Scenarios/when_projecting_with_children_within_children_using_parent_key_from_context/and_parent_key_is_resolved_from_sink.cs	5.3	Mixed	Test Quality: No assertions: should_have_no_failed_partitions
Source/Tools/GrpcClients/ILInstruction.cs	5.4	Mixed	Explicit Debt: EmptyCatchBlock
Source/Clients/Api/Api.csproj	5.4	Mixed	Explicit Debt: NoWarnInCsproj
Source/Kernel/Core/Core.csproj	5.8	Mixed	Explicit Debt: NoWarnInCsproj
Source/Kernel/Contracts/Contracts.csproj	5.8	Mixed	Explicit Debt: NoWarnInCsproj
Source/Workbench/Web/.yarn/releases/yarn-4.5.3.cjs	5.8	Mixed	Secrets (history): Secret: aws-access-token
Source/Workbench/.yarn/releases/yarn-4.5.3.cjs	5.8	Mixed	Secrets (history): Secret: aws-access-token
Source/Clients/Elixir/mix.lock	5.9	Mixed	OSV Dependency Vulnerabilities: Medium CVE: EEF-[CVE redacted]
Source/Kernel/Storage.MongoDB/EventSequences/EventSequenceStorage.cs	5.9	Mixed	God Classes: FileTooLong: EventSequences/EventSequenceStorage.cs
Source/Kernel/Storage.Sql/Database.cs	6.0	Mixed	Explicit Debt: BarePragmaDisable
Source/Infrastructure/Schemas/JsonSchema.cs	6.3	Mixed	Cognitive Complexity: JsonSchema.Validate (cognitive 17)
Source/Kernel/GlobalUsings.cs	6.4	Mixed	Explicit Debt: BarePragmaDisable
Integration/Api/Api.csproj	6.4	Mixed	Explicit Debt: NoWarnInCsproj
Source/Tools/GrpcCodeGenerator/GrpcCodeGenerator.csproj	6.4	Mixed	Explicit Debt: NoWarnInCsproj
Source/Kernel/Server/Server.csproj	6.4	Mixed	Explicit Debt: NoWarnInCsproj
Source/Clients/DotNET.CodeAnalysis/DotNET.CodeAnalysis.csproj	6.4	Mixed	Explicit Debt: NoWarnInCsproj

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. 71 of 71 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 71 dimensions across the health lenses

D1D2D3D4D5D6D8D9D10D11D12D13D14D17D18D26D27D28D29D30D31D33D36D38AC1AC2AC3AC4AC6AC7AX1AX10AX2AX3AX4AX5AX6AX8C1C2GD1IC1M1M2M3P1P10P2P3P4P6P7P8PF1PF2PF3R1R10R2R3R4R6R7R8R9S1X1X2X3X4X5

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

How to trust any code-health report — three questions

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 019ee425-56d1-76ac-8bcc-e95910f2148a.

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.

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.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct, and component-wrapped fields (e.g. a <TextField>) are skipped. A clean result is "no unlabelled native control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — only literal inline colours and in-repo <style>-block CSS are read; external stylesheets, CSS-in-JS, computed/runtime/theme colour, and image contrast are all out of reach, so a clean result is bounded by what the markup itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity7.0 / 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 7.0 / 10 · rule-coverage 100% · ceiling Prevented

18 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ReadModelMigrator.GetColumnType at 63.

toEditorPath (cyclomatic 18) · ×2Source/Workbench/.yarn/sdks/typescript/lib/tsserverlibrary.js:55

ReadModelMigrator.GetColumnType (cyclomatic 63)Source/Kernel/Storage.Sql/EventStores/Namespaces/ReadModels/ReadModelMigrator.cs:199

BsonValueExtensions.ToBsonValue (cyclomatic 34)Source/Kernel/Storage.MongoDB/BsonValueExtensions.cs:26

BsonValueExtensions.ToTargetType (cyclomatic 31)Source/Kernel/Storage.MongoDB/BsonValueExtensions.cs:189

ObjectComparer.CompareValues (cyclomatic 30)Source/Infrastructure/Changes/ObjectComparer.cs:220

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

What to do

Resolve the 2 toEditorPath (cyclomatic 18) finding(s) in Cyclomatic Complexity — start with tsserver.js, tsserverlibrary.js. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 ReadModelMigrator.GetColumnType (cyclomatic 63) finding(s) in Cyclomatic Complexity — start with ReadModelMigrator.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 BsonValueExtensions.ToBsonValue (cyclomatic 34) finding(s) in Cyclomatic Complexity — start with BsonValueExtensions.cs. — One of this dimension's main actionable groups (1 warning-level).
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.

Do you agree with this assessment?

D2 · Cognitive Complexity6.7 / 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.7 / 10 · rule-coverage 100% · ceiling Prevented

31 method(s) exceeded the cognitive complexity threshold of 15; the worst was KeyJsonConverter.Read at 53.

toEditorPath (cognitive 21) · ×2Source/Workbench/.yarn/sdks/typescript/lib/tsserverlibrary.js:55

onMessage (cognitive 19) · ×2Source/Workbench/.yarn/sdks/typescript/lib/tsserverlibrary.js:191

KeyJsonConverter.Read (cognitive 53)Source/Kernel/Concepts/Keys/KeyJsonConverter.cs:16

BsonValueExtensions.ToTargetType (cognitive 45)Source/Kernel/Storage.MongoDB/BsonValueExtensions.cs:189

ExpandoObjectExtensions.EnsurePath (cognitive 42)Source/Infrastructure/Dynamic/ExpandoObjectExtensions.cs:150

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

What to do

Resolve the 2 toEditorPath (cognitive 21) finding(s) in Cognitive Complexity — start with tsserver.js, tsserverlibrary.js. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 onMessage (cognitive 19) finding(s) in Cognitive Complexity — start with tsserver.js, tsserverlibrary.js. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 KeyJsonConverter.Read (cognitive 53) finding(s) in Cognitive Complexity — start with KeyJsonConverter.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes9.3 / 10Exemplary✓ Tool-verified

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

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

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

8 god class(es) detected.

TooManyMethods: ApplicationStore · ×5Source/Kernel/Server/Authentication/OpenIddict/ApplicationStore.cs:0

FileTooLong: EventSequences/EventSequenceStorage.cs · ×3Source/Kernel/Storage.MongoDB/EventSequences/EventSequenceStorage.cs:0

ClassTooLong: EventSequenceStorage · ×2Source/Kernel/Storage.MongoDB/EventSequences/EventSequenceStorage.cs:0

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D4 · Code Duplication9.9 / 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.9 / 10 · rule-coverage 100% · ceiling Verified

16 duplicated block group(s) detected.

Duplicated block (13 lines × 2) · ×3Source/Kernel/Storage.MongoDB/EventStoreNamespaceDatabase.cs:188

Duplicated block (17 lines × 2) · ×2Source/Clients/DotNET.CodeAnalysis/Analyzers/ConstraintSideEffectAnalyzer.cs:41

Duplicated block (16 lines × 2) · ×2Source/Clients/Api/Program.cs:50

Duplicated block (11 lines × 2) · ×2Source/Kernel/Storage.MongoDB/EventSequences/EventSequenceStorage.cs:363

Duplicated block (21 lines × 2)Source/Kernel/Storage.Sql/EventStores/Namespaces/EventSequences/EventEntryConverter.cs:485

+ 6 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.

Do you agree with this assessment?

D5 · Coupling8.3 / 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.3 / 10 · rule-coverage 100% · ceiling Prevented

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

Layer violation: Domain → Infrastructure

Off the main sequence: DotNET.CodeAnalysis · ×8

Unstable project Server

What to do

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

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

Do you agree with this assessment?

D6 · Cohesion (LCOM4)8.8 / 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 8.8 / 10 · rule-coverage 100% · ceiling Verified

12 of 116 classes have LCOM4 above 3.

Low cohesion: NullSink (LCOM4 13) · ×12Source/Kernel/Storage/Sinks/NullSink.cs:20

What to do

Resolve the 12 Low cohesion finding(s) in Cohesion (LCOM4) — start with JsonSchema.cs (2), EncryptionKeySerializer.cs, EventSequenceDbContext.cs. — One of this dimension's main actionable groups (12 warning-level).
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.

Do you agree with this assessment?

D8 · Code Coverage9.9 / 10Exemplary✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Verified

Line coverage 84.3%, branch coverage 63.2%.

✓ On the Gold path — maintain.

Detailed fixes: d8_recommendation.md.

Do you agree with this assessment?

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

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

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

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

5601 test methods: 5213 unit, 388 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.

Do you agree with this assessment?

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

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

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

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

7 skipped (7 with a documented reason), 62 zero-assertion, 1 mock references across 5726 tests (1 harness-style project(s) excluded from the assertion penalty).

No assertions: should_have_no_failed_partitions · ×3Integration/Client/Projections/Scenarios/when_projecting_with_children_within_children_using_parent_key_from_context/and_all_events_are_appended_in_one_transaction.cs:75

No direct assertions: should_report_imperative_expression_diagnostic · ×59Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ConstraintExpressionLambdaAnalyzer/when_analyzing_constraint_expression_lambdas/and_expression_lambda_contains_method_call.cs:27

Skipped (documented): should_have_correct_next_sequence_number · ×7Integration/Client/for_Reactors/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:42

Mock framework: NSubstitute

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

0 flaky across 1 measured tier(s). integration: 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.

Do you agree with this assessment?

D12 · Dependency Hygiene7.4 / 10Strong✓ Tool-verified

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

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

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

113 outdated, 0 vulnerable, 21 deprecated packages.

Deprecated: xunit · ×21

Outdated: Cratis.Arc · ×113

What to do

Resolve the 21 Deprecated finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (21 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D13 · Secret Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

2 secret(s) detected.

Leaked secret: hardcoded-credential · ×2Source/Kernel/Server/run.sh:90

What to do

Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with run-mssql.sh, run.sh. — One of this dimension's main actionable groups (2 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

0 of 85 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.

Do you agree with this assessment?

D17 · Explicit Debt0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Prevented

144 deducted debt markers + 3327 dead symbols across 58999 LoC (14.9/KLoC) → score 0.0.

NoWarnInCsproj · ×26TestApps/SimpleConsole/SimpleConsole.csproj:8

EmptyCatchBlock · ×2Source/Clients/AspNetCore/ChronicleClientServiceCollectionExtensions.cs:68

Dead code: Establish · ×3312Integration/Api/for_EventStoreQueries/when_getting_event_stores.cs:18

BarePragmaDisable · ×100Integration/GlobalUsings.cs:4

TodoComment · ×15Source/Clients/DotNET/Projections/ChildrenBuilder.cs:36

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

What to do

Resolve the 3312 Dead code finding(s) in Explicit Debt — start with all_dependencies.cs (25), when_creating_analyzer.cs (17), and_value_is_random.cs (14). — One of this dimension's main actionable groups (3312 warning-level).
Resolve the 26 NoWarnInCsproj finding(s) in Explicit Debt — start with Api.csproj (7), Contracts.csproj (3), Core.csproj (3). — One of this dimension's main actionable groups (26 issue-level).
Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with ChronicleClientServiceCollectionExtensions.cs, ILInstruction.cs. — One of this dimension's main actionable groups (2 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

40 projects, 5395 .cs files, 204560 hand-written lines of code (58999 production / 145561 test), plus 91 generated (EF migrations / designer / snapshots, excluded from quality), 158 inter-project edges (build failed).

Analyzed solution does not cover the bulk of the repository

Api (Production) · ×2Integration/Api/Api.csproj

Build did not complete in the analyzer

Client (Production)Integration/Client/Client.csproj

Kernel (Production)Integration/Kernel/Kernel.csproj

+ 36 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.

Do you agree with this assessment?

D26 · Project Cohesion4.5 / 10Weak✓ 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 4.5 / 10 · rule-coverage 100% · ceiling Documented

11 of 40 projects flagged as possibly oversized/incoherent.

Large project: Client · ×11

What to do

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

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

Do you agree with this assessment?

D27 · Navigability6.0 / 10Adequate✓ Tool-verified

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

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.

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

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

97 % of calls cross a namespace and 26 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.

What to do

Improve Navigability — currently 6.0/10. — 97 % of calls cross a namespace and 26 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

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

Secret: aws-access-token · ×4Source/Workbench/Web/.yarn/releases/yarn-4.5.3.cjs:149detected by gitleaks finding

Rotate the exposed credentials — git history can't be un-committed

What to do

Resolve the 4 Secret finding(s) in Secrets (history) — start with yarn-4.5.3.cjs (4). — One of this dimension's main actionable groups (4 issue-level).
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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.

Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.

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

No known-vulnerable NuGet packages (direct or transitive).

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

Do you agree with this assessment?

D31 · IaC & Container Security7.7 / 10Strong✓ 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 7.7 / 10 · rule-coverage 100% · ceiling Documented

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

High IaC: DS-0002 · ×6Docker/Development/Dockerfiledetected by trivy finding

Medium IaC: DS-0001Docker/Local/Dockerfiledetected by trivy finding

Low IaC: DS-0026 · ×6Docker/Development/Dockerfiledetected by trivy finding

What to do

Resolve the 6 High IaC finding(s) in IaC & Container Security — start with Dockerfile (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 6 Low IaC finding(s) in IaC & Container Security — start with Dockerfile (6). — One of this dimension's main actionable groups (6 recommendation-level).
Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with Dockerfile. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D33 · JS/npm Dependency Vulnerabilities6.5 / 10Adequate✓ Tool-verified

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

20 finding(s): 0 critical, 1 high, 14 medium, 5 low.

High CVE: [CVE redacted]Source/Workbench/yarn.lockdetected by trivy finding

Medium CVE: [CVE redacted] · ×14Source/Workbench/yarn.lockdetected by trivy finding

Low CVE: [GHSA redacted] · ×5Source/Workbench/yarn.lockdetected by trivy finding

What to do

Resolve the 14 Medium CVE finding(s) in JS/npm Dependency Vulnerabilities — start with yarn.lock (14). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 1 High CVE finding(s) in JS/npm Dependency Vulnerabilities — start with yarn.lock. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 5 Low CVE finding(s) in JS/npm Dependency Vulnerabilities — start with yarn.lock (5). — One of this dimension's main actionable groups (5 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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

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

Unpinned build actions

No build provenance

No artifact signing

No SBOM

What to do

Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
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.

Do you agree with this assessment?

D38 · OSV Dependency Vulnerabilities2.6 / 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 2.6 / 10 · rule-coverage 100% · ceiling Documented

33 finding(s): 0 critical, 5 high, 21 medium, 7 low.

High CVE: [GHSA redacted] · ×5Source/Workbench/yarn.lockdetected by osv-scanner finding

Medium CVE: EEF-[CVE redacted] · ×21Source/Clients/Elixir/mix.lockdetected by osv-scanner finding

Low CVE: [GHSA redacted] · ×7Source/Workbench/yarn.lockdetected by osv-scanner finding

What to do

Resolve the 21 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (15), mix.lock (6). — One of this dimension's main actionable groups (21 warning-level).
Resolve the 5 High CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 7 Low CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (7). — One of this dimension's main actionable groups (7 recommendation-level).

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, and video has a captions track. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Do you agree with this assessment?

AC2 · Forms & labels5.4 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, fieldsets have a legend, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×4) — viewer.html:604, viewer.html:604, viewer.html:604, …

What to do

Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.

Do you agree with this assessment?

AC3 · Page structure5.3 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language and title, expose a main landmark and a sane heading order, keep zoom enabled, title their iframes and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×9) — eval_review.html:2, viewer.html:2, eval_review.html:2, …
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — index.html:3

What to do

Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.

Do you agree with this assessment?

AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no positive tabindex, no href-less anchor. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×12) — viewer.html:581, viewer.html:592, viewer.html:581, …

What to do

Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.

Do you agree with this assessment?

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: only inline styles and in-repo CSS literals are visible, never computed or runtime colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Do you agree with this assessment?

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an a11y linter (eslint-plugin-jsx-a11y / vuejs-accessibility) configured, and axe/pa11y/Lighthouse wired into tests or CI — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an a11y linter (eslint-plugin-jsx-a11y / vuejs-accessibility) configured, and axe/pa11y/Lighthouse in tests or CI, graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y / vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time.

What to do

Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y (or vuejs-accessibility), assert with jest-axe / playwright-axe in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

AX10 · Code composition7.3 / 10Strong✓ 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).

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.

`IChangeset` 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. — IChangeset.cs:13
`IServices` declares 44 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. — IServices.cs:27
`IEventStoreNamespaceStorage` declares 32 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. — IEventStoreNamespaceStorage.cs:23
`IEventStoreStorage` declares 25 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. — IEventStoreStorage.cs:22
`IEventSequenceStorage` 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. — IEventSequenceStorage.cs:16

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

C1 · Data Protection5.5 / 10Adequate✓ 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.

What to do

Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — EventSequenceCommands.cs:195, JobStepStorage.cs:141

What to do

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

Do you agree with this assessment?

IC1 · Incompleteness & stubs7.8 / 10Strong✓ Tool-verified

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

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

`RedactMany` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — EventSequenceCommands.cs:188
`ListRevisions` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — AzureKeyVaultEncryptionKeyStorage.cs:168
`ReadOnlyObservableSubject` has 2 unfinished members out of 4 — a scaffolded type that was never implemented. — LiveQuery.cs:69
`OnNext` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — LiveQuery.cs:71
`OnError` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — LiveQuery.cs:75
A test is skipped ("Not waiting for the observer does not work") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×6) — and_not_waiting_for_observer_to_be_active.cs:42, and_not_waiting_for_observer_to_be_active.cs:47, and_not_waiting_for_observer_to_be_active.cs:52, …
A test is skipped ("Orleans TestKit does not implement GrainFactory.GetGrain(GrainId)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — when_reporting_new_successfully_handled_event.cs:11
`CountAsync`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional. (×4) — ApplicationStore.cs:30, AuthorizationStore.cs:23, ScopeStore.cs:37, …
`GetAsync`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional. (×4) — ApplicationStore.cs:80, AuthorizationStore.cs:98, ScopeStore.cs:91, …
`ListAsync`'s body only throws NotSupportedException — sometimes a deliberate contract, often an unfinished stub. Confirm it's intentional. (×4) — ApplicationStore.cs:207, AuthorizationStore.cs:151, ScopeStore.cs:141, …
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×3) — EventStoreNamespaceDatabase.cs:48, MongoDBChronicleBuilderExtensions.cs:45, MongoDBChronicleBuilderExtensions.cs:46
`OnCompleted` has an empty body — confirm it's an intentional no-op and not an unfinished method. — LiveQuery.cs:79

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.

Do you agree with this assessment?

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 a 'Testing' section to the root README — how to run the test suite.
Add a README to the 39 of 40 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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.

Test projects aren't grouped under a tests/ folder — the test surface isn't separable from production code at a glance.

What to do

Group test projects under tests/ (or test/, spec/) so the test surface is discoverable and CI can scope it.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries. Exhaustive, deterministic.

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

What to do

Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.

Do you agree with this assessment?

P2 · Observability8.1 / 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 5/14 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.

Do you agree with this assessment?

P3 · Security & performance tooling5.0 / 10Adequate✓ 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.

What to do

Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & 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.

Do you agree with this assessment?

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.

Do you agree with this assessment?

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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.

The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.

What to do

Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.

Do you agree with this assessment?

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

PF1 · Benchmark discipline6.0 / 10Adequate✓ 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.

No BenchmarkDotNet suite was found. For a performance-sensitive library, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

Add a BenchmarkDotNet project for the hot paths (with [MemoryDiagnoser] to track allocations), and run it in CI to catch regressions.

Do you agree with this assessment?

PF2 · Allocation hygiene7.2 / 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 141 use(s) across 59,570 production line(s) (~2.4/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.

Do you agree with this assessment?

PF3 · Async & latency hygiene2.3 / 10Critical✓ 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.

13 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock in a consumer with a synchronization context.
Only 89/1406 awaits use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.

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.
In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.

Do you agree with this assessment?

R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication5.6 / 10Adequate✓ Tool-verified

React / JS · Code Health — Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm over JS/TS tokens, D-386).

Method: Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm run over JS/TS tokens). Deterministic.

Source/Workbench/Api/EventSequences/Append.ts:14 · Source/Workbench/Api/EventSequences/Revise.ts:14 — Append.ts:14
Source/Workbench/Api/EventSequences/Redact.ts:11 · Source/Workbench/Api/EventSequences/RedactMany.ts:11 — Redact.ts:11
Source/Workbench/Api/Observation/ReplayPartition.ts:11 · Source/Workbench/Api/Observation/TryRecoverFailedPartition.ts:11 · Source/Workbench/Api/Projections/GenerateDeclarativeCode.ts:13 · Source/Workbench/Api/Projections/GenerateModelBoundCode.ts:13 — ReplayPartition.ts:11
Source/Workbench/Api/Observation/GetReplayableObserversForEventTypes.ts:46 · Source/Workbench/Api/ReadModels/ReadModelOccurrences.ts:46 — GetReplayableObserversForEventTypes.ts:46
Source/Workbench/Api/Events/EventContext.ts:12 · Source/Workbench/Api/Events/EventRevision.ts:9 · Source/Workbench/Api/Jobs/Job.ts:12 · Source/Workbench/Api/Jobs/JobProgress.ts:8 — EventContext.ts:12
Source/Workbench/Api/Jobs/DeleteJob.ts:11 · Source/Workbench/Api/Jobs/ResumeJob.ts:11 · Source/Workbench/Api/Jobs/StopJob.ts:11 · Source/Workbench/Api/Observation/ClearObserverQuarantine.ts:10 — DeleteJob.ts:11
Source/Workbench/Api/EventTypes/AllEventTypeGenerations.ts:53 · Source/Workbench/Api/Identities/GetIdentities.ts:53 · Source/Workbench/Api/Observation/GetObservers.ts:35 · Source/Workbench/Api/Recommendations/GetRecommendations.ts:62 — AllEventTypeGenerations.ts:53
Source/Workbench/Api/Projections/GenerateDeclarativeCode.ts:18 · Source/Workbench/Api/Projections/GenerateModelBoundCode.ts:18 · Source/Workbench/Api/Projections/PreviewProjection.ts:18 · Source/Workbench/Api/Projections/SaveProjection.ts:18 — GenerateDeclarativeCode.ts:18

What to do

Extract the duplicated blocks into shared functions/components.

Do you agree with this assessment?

R2 · Cyclomatic Complexity9.9 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×8) — generate-generated-index.mjs:39, Projections.tsx:86, EventDetails.tsx:31, …

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

Do you agree with this assessment?

R3 · Large Files9.6 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many components/modules exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

What to do

Split the oversized components into smaller, focused ones.

Do you agree with this assessment?

R4 · Test Coverage0.4 / 10Critical✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

No test imports this module directly or transitively — its behavior is unverified. (×8) — ProjectionDefinitionLanguageCompletionProvider.ts, Projections.tsx, ProjectionDefinitionLanguageValidator.ts, …

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

Do you agree with this assessment?

R7 · Dead Code0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

Unreachable from the 3 application, 4 tooling and 10 test entry point(s) detected in this repo. Gate removals on your build/type-check — an undetected custom entry would make these reachable.
no import path from any entry point (3 application, 4 tooling, 10 test roots considered) (×7) — ProjectionDefinitionLanguageCompletionProvider.ts, Projections.tsx, ProjectionDefinitionLanguageValidator.ts, …

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×3) — AllEventSequences.ts:8, Causation.ts:8, TimeMachineDialog.stories.tsx:9
Declared in Source/Clients/TypeScript/package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing. (×3)

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

R9 · Circular Imports8.3 / 10Strong✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

Source/Workbench/Components/ProjectionEditor/ProjectionEditor.tsx → Source/Workbench/Components/ProjectionEditor/index.ts → Source/Workbench/Components/ProjectionEditor/ProjectionEditor.tsx — ProjectionEditor.tsx

What to do

Break each cycle by extracting the shared piece into a module both sides can import.

Do you agree with this assessment?

S1 · Web-Security Posture6.0 / 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 UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)

What to do

Add security response headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) — defense in depth, even when a reverse proxy could set them.
Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.

Do you agree with this assessment?

X1 · Async correctness7.4 / 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. (×14) — ChronicleClientServiceCollectionExtensions.cs:99, ChronicleClientWebApplicationBuilderExtensions.cs:78, ChronicleClientWebApplicationBuilderExtensions.cs:79, …

What to do

Sync-over-async (deadlock risk)

Do you agree with this assessment?

X2 · Cancellation propagation5.5 / 10Adequate✓ 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 146/586 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) — CausationMiddleware.cs:76, EventSequenceCommands.cs:35, EventSequenceCommands.cs:84, …

What to do

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

Do you agree with this assessment?

X3 · Exception handling7.3 / 10Strong✓ Tool-verified

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

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

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — ChronicleClientServiceCollectionExtensions.cs:68, ILInstruction.cs:69

What to do

Swallowed exception (empty catch)

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X5 · Nullable reference types9.3 / 10Exemplary✓ 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.

~0.8 `!` 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 `!`.

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria — partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC4 · Keyboard semantics	2.1.1, 2.4.3	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	38%	Weak — gated by D17, R7	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	83%	Strong	Strongest area.
Maturity	65%	Adequate	Acceptable, with room to improve.
Readiness	30%	Weak — gated by D13, R4, R8, P7	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	48%	Weak — gated by D36, D38, C2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	45%	Weak — gated by AC4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	47%	Weak — gated by PF3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.

Not included — 27 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.

AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
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.
D15 Churn × Complexity Hotspots — single-commit history — no churn to measure hotspots
D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
D23 Boundary Type-Coupling — Bounded contexts not declared
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 — not run — only 1/3 markers (56 value object(s))
ED1 Event-Driven — not run — only 1/3 markers (a message-bus package)
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not run — only 1/3 markers (an append-only event-store seam (IEventStore/Append-of-events))
M4 Documentation accuracy — LLM not available — accuracy is the Tier-2 layer and needs a reachable model.
P12 CI test-gate honesty — no data
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P9 Domain vs controller coverage — coverage data present but no domain-layer files were identified (no /Domain//Aggregates/ paths)
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D33 (JS/npm Dependency Vulnerabilities)
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 — 50 finding(s)

D17 · Explicit Debt · NoWarnInCsproj · ×26

NoWarnInCsproj TestApps/SimpleConsole/SimpleConsole.csproj:8 — IDE0060
NoWarnInCsproj Integration/Api/Api.csproj:15 — CS0436
NoWarnInCsproj Integration/Api/Api.csproj:15 — CS7022
NoWarnInCsproj Source/Tools/ProtoGenerator/ProtoGenerator.csproj:6 — SA1600
NoWarnInCsproj Source/Tools/GrpcCodeGenerator/GrpcCodeGenerator.csproj:7 — SA1600
NoWarnInCsproj Source/Tools/GrpcCodeGenerator/GrpcCodeGenerator.csproj:7 — RCS1201
NoWarnInCsproj Source/Tools/GrpcCodeGenerator.Specs/GrpcCodeGenerator.Specs.csproj:7 — SA1600
NoWarnInCsproj Source/Tools/GrpcClients/GrpcClients.csproj:7 — SA1600
NoWarnInCsproj Source/Kernel/Server/Server.csproj:9 — RCS1093
NoWarnInCsproj Source/Kernel/Server/Server.csproj:9 — CS0436
NoWarnInCsproj Source/Kernel/Core/Core.csproj:7 — ORLEANS0010
NoWarnInCsproj Source/Kernel/Core/Core.csproj:7 — CS8618
NoWarnInCsproj Source/Kernel/Core/Core.csproj:7 — MA0182
NoWarnInCsproj Source/Kernel/Contracts/Contracts.csproj:9 — CS8618
NoWarnInCsproj Source/Kernel/Contracts/Contracts.csproj:9 — PBN2008
NoWarnInCsproj Source/Kernel/Contracts/Contracts.csproj:9 — PBN0022
NoWarnInCsproj Source/Clients/DotNET.Specs/DotNET.Specs.csproj:7 — MA0182
NoWarnInCsproj Source/Clients/DotNET.CodeAnalysis/DotNET.CodeAnalysis.csproj:19 — NU5128
NoWarnInCsproj Source/Clients/DotNET.CodeAnalysis/DotNET.CodeAnalysis.csproj:19 — NU1507
NoWarnInCsproj Source/Clients/Aspire/Aspire.csproj:5 — ASPIREPROBES001
NoWarnInCsproj Source/Clients/Aspire/Aspire.csproj:5 — NU1903
NoWarnInCsproj Source/Clients/Api/Api.csproj:15 — RCS1140
NoWarnInCsproj Source/Clients/Api/Api.csproj:15 — CS1998
NoWarnInCsproj Source/Clients/Api/Api.csproj:15 — IDE0005
NoWarnInCsproj Source/Clients/Api/Api.csproj:15 — SA0001
+ 1 more in this group — see findings.md.

D31 · IaC & Container Security · High IaC · ×6

High IaC: DS-0002 Docker/Development/Dockerfile — Image user should not be 'root'
High IaC: DS-0002 Docker/DevelopmentSlim/Dockerfile — Image user should not be 'root'
High IaC: DS-0002 Docker/Local/Dockerfile — Image user should not be 'root'
High IaC: DS-0002 Docker/LocalSlim/Dockerfile — Image user should not be 'root'
High IaC: DS-0002 Docker/Production/Dockerfile — Image user should not be 'root'
High IaC: DS-0002 Docker/Workbench/Dockerfile — Image user should not be 'root'

D38 · OSV Dependency Vulnerabilities · High CVE · ×5

High CVE: [GHSA redacted] Source/Workbench/yarn.lock — serialize-javascript: [GHSA redacted]
High CVE: [GHSA redacted] Source/Workbench/yarn.lock — undici: [GHSA redacted]
High CVE: [GHSA redacted] Source/Workbench/yarn.lock — validator: [GHSA redacted]
High CVE: [GHSA redacted] Source/Workbench/yarn.lock — vite: [GHSA redacted]
High CVE: [GHSA redacted] Source/Workbench/yarn.lock — ws: [GHSA redacted]

D28 · Secrets (history) · Secret · ×4

Secret: aws-access-token Source/Workbench/Web/.yarn/releases/yarn-4.5.3.cjs:149 — matched rule 'aws-access-token'
Secret: generic-api-key Source/Workbench/Web/.yarn/releases/yarn-4.5.3.cjs:576 — matched rule 'generic-api-key'
Secret: aws-access-token Source/Workbench/.yarn/releases/yarn-4.5.3.cjs:149 — matched rule 'aws-access-token'
Secret: generic-api-key Source/Workbench/.yarn/releases/yarn-4.5.3.cjs:576 — matched rule 'generic-api-key'

D10 · Test Quality · No assertions · ×3

No assertions: should_have_no_failed_partitions Integration/Client/Projections/Scenarios/when_projecting_with_children_within_children_using_parent_key_from_context/and_all_events_are_appended_in_one_transaction.cs:75 — Test method has no assertions — it may not test anything.
No assertions: should_have_no_failed_partitions Integration/Client/Projections/Scenarios/when_projecting_with_children_within_children_using_parent_key_from_context/and_metric_event_arrives_before_hub_is_added.cs:79 — Test method has no assertions — it may not test anything.
No assertions: should_have_no_failed_partitions Integration/Client/Projections/Scenarios/when_projecting_with_children_within_children_using_parent_key_from_context/and_parent_key_is_resolved_from_sink.cs:68 — Test method has no assertions — it may not test anything.

D13 · Secret Scanning · Leaked secret · ×2

Leaked secret: hardcoded-credential Source/Kernel/Server/run.sh:90 — hardcoded-credential detected.
Leaked secret: hardcoded-credential Source/Kernel/Server/run-mssql.sh:17 — hardcoded-credential detected.

D17 · Explicit Debt · EmptyCatchBlock · ×2

EmptyCatchBlock Source/Clients/AspNetCore/ChronicleClientServiceCollectionExtensions.cs:68 — empty catch block
EmptyCatchBlock Source/Tools/GrpcClients/ILInstruction.cs:69 — empty catch block

D33 · JS/npm Dependency Vulnerabilities · High CVE · ×1

High CVE: [CVE redacted] Source/Workbench/yarn.lock — react-router: [CVE redacted]

D5 · Coupling · Layer violation · ×1

Layer violation: Domain → Infrastructure — Core (Domain) references Infrastructure (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).

Warning — 3583 finding(s)

D17 · Explicit Debt · Dead code · ×3312

Dead code: Establish Integration/Api/for_EventStoreQueries/when_getting_event_stores.cs:18 — Method Establish — no references found in solution.
Dead code: Because Integration/Api/for_EventStoreQueries/when_getting_event_stores.cs:20 — Method Because — no references found in solution.
Dead code: Establish Integration/Api/for_EventTypes/when_getting_all_event_types.cs:18 — Method Establish — no references found in solution.
Dead code: Because Integration/Api/for_EventTypes/when_getting_all_event_types.cs:35 — Method Because — no references found in solution.
Dead code: Establish Integration/Api/for_EventTypes/when_getting_all_event_type_registrations.cs:18 — Method Establish — no references found in solution.
Dead code: Because Integration/Api/for_EventTypes/when_getting_all_event_type_registrations.cs:35 — Method Because — no references found in solution.
Dead code: Establish Integration/Api/given/an_http_client.cs:22 — Method Establish — no references found in solution.
Dead code: WaitForOutOfProcessMongoDbPrimary Integration/Client/ChronicleConfigurableFixture.cs:508 — Method WaitForOutOfProcessMongoDbPrimary — no references found in solution.
Dead code: Handle Integration/Client/for_EventAppendCollection/ACommandThatAppendsAnEvent.cs:15 — Method Handle — no references found in solution.
Dead code: Establish Integration/Client/for_EventAppendCollection/given/an_event_append_collection_scope.cs:19 — Method Establish — no references found in solution.
Dead code: Destroy Integration/Client/for_EventAppendCollection/given/an_event_append_collection_scope.cs:21 — Method Destroy — no references found in solution.
Dead code: Establish Integration/Client/for_EventAppendCollection/given/a_reactor_that_directly_appends_unique_events_scope.cs:20 — Method Establish — no references found in solution.
Dead code: Destroy Integration/Client/for_EventAppendCollection/given/a_reactor_that_directly_appends_unique_events_scope.cs:22 — Method Destroy — no references found in solution.
Dead code: Establish Integration/Client/for_EventAppendCollection/given/a_reactor_that_executes_a_command_scope.cs:35 — Method Establish — no references found in solution.
Dead code: Destroy Integration/Client/for_EventAppendCollection/given/a_reactor_that_executes_a_command_scope.cs:37 — Method Destroy — no references found in solution.
Dead code: Because Integration/Client/for_EventAppendCollection/when_a_reactor_directly_appends_unique_events/and_the_constraint_is_satisfied.cs:18 — Method Because — no references found in solution.
Dead code: Because Integration/Client/for_EventAppendCollection/when_a_reactor_executes_a_command/and_collecting_the_appended_events.cs:15 — Method Because — no references found in solution.
Dead code: Because Integration/Client/for_EventAppendCollection/when_a_reactor_handles_an_event/and_collecting_the_appended_event.cs:14 — Method Because — no references found in solution.
Dead code: Because Integration/Client/for_EventAppendCollection/when_a_reactor_handles_two_events/and_collecting_both_appended_events.cs:14 — Method Because — no references found in solution.
Dead code: Because Integration/Client/for_EventAppendCollection/when_committed_via_a_unit_of_work/and_collecting_the_appended_events.cs:13 — Method Because — no references found in solution.
Dead code: Establish Integration/Client/for_EventSequence/when_appending/an_event.cs:19 — Method Establish — no references found in solution.
Dead code: Because Integration/Client/for_EventSequence/when_appending/an_event.cs:24 — Method Because — no references found in solution.
Dead code: Establish Integration/Client/for_EventSequence/when_appending/an_event_without_occurred.cs:21 — Method Establish — no references found in solution.
Dead code: Because Integration/Client/for_EventSequence/when_appending/an_event_without_occurred.cs:26 — Method Because — no references found in solution.
Dead code: Establish Integration/Client/for_EventSequence/when_appending/an_event_with_occurred.cs:20 — Method Establish — no references found in solution.
+ 3287 more in this group — see findings.md.

D17 · Explicit Debt · BarePragmaDisable · ×100

BarePragmaDisable Integration/GlobalUsings.cs:4 — #pragma warning disable
BarePragmaDisable Integration/GlobalUsings.cs:4 — #pragma warning disable
BarePragmaDisable Integration/Client/for_Reactors/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:41 — #pragma warning disable xUnit1004
BarePragmaDisable Integration/Client/for_Reactors/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:46 — #pragma warning disable xUnit1004
BarePragmaDisable Integration/Client/for_Reactors/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:51 — #pragma warning disable xUnit1004
BarePragmaDisable Integration/Client/for_ReadModels/when_getting_instance_for_passive_projection/and_child_element_is_updated.cs:4 — #pragma warning disable SA1402
BarePragmaDisable Integration/Client/for_ReadModels/when_getting_instance_for_passive_projection/and_parent_event_exists.cs:4 — #pragma warning disable SA1402
BarePragmaDisable Integration/Client/for_Reducers/given/a_reducer_able_to_delete.cs:21 — #pragma warning disable CA2213
BarePragmaDisable Integration/Client/for_Reducers/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:41 — #pragma warning disable xUnit1004
BarePragmaDisable Integration/Client/for_Reducers/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:46 — #pragma warning disable xUnit1004
BarePragmaDisable Integration/Client/for_Reducers/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:51 — #pragma warning disable xUnit1004
BarePragmaDisable Integration/Client/Projections/Scenarios/ModelBound/when_projecting_with_deep_hierarchy_using_event_source_as_child_key/and_projection_is_replayed.cs:4 — #pragma warning disable SA1402
BarePragmaDisable Integration/Client/Specification.cs:4 — #pragma warning disable SA1402
BarePragmaDisable Integration/GlobalUsings.cs:4 — #pragma warning disable
BarePragmaDisable Integration/Kernel/for_JobsManager/given/TheJobStepProcessor.cs:76 — #pragma warning disable MA0106
BarePragmaDisable Integration/Kernel/for_JobsManager/given/TheJobStepProcessor.cs:97 — #pragma warning disable MA0106
BarePragmaDisable Integration/Kernel/for_JobsManager/given/TheJobStepProcessor.cs:127 — #pragma warning disable MA0106
BarePragmaDisable Integration/Kernel/for_JobsManager/given/TheJobStepProcessorHelpers.cs:23 — #pragma warning disable RCS1238
BarePragmaDisable Integration/GlobalUsings.cs:4 — #pragma warning disable
BarePragmaDisable Source/Infrastructure.Specs/Changes/for_ObjectsComparer/MyComparable.cs:5 — #pragma warning disable CS0144, CA1036
BarePragmaDisable Source/Infrastructure.Specs/Changes/for_ObjectsComparer/MyGenericComparable.cs:6 — #pragma warning disable CS0144, CA1036
BarePragmaDisable Source/Infrastructure/Properties/PropertyPath.cs:338 — #pragma warning disable MA0190
BarePragmaDisable Source/Clients/Api/ApiApplicationBuilderExtensions.cs:4 — #pragma warning disable SA1600
BarePragmaDisable Source/Clients/Api/ApiServiceCollectionExtensions.cs:4 — #pragma warning disable SA1600
BarePragmaDisable Source/Clients/Api/CustomControllerActivator.cs:4 — #pragma warning disable SA1600
+ 75 more in this group — see findings.md.

D12 · Dependency Hygiene · Deprecated · ×21

Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: Microsoft.CodeAnalysis.CSharp.Analyzer.Testing.XUnit — Microsoft.CodeAnalysis.CSharp.Analyzer.Testing.XUnit 1.1.2 — Legacy Microsoft.CodeAnalysis.CSharp.Analyzer.Testing >= 0.0.0
Deprecated: Microsoft.CodeAnalysis.CSharp.CodeFix.Testing.XUnit — Microsoft.CodeAnalysis.CSharp.CodeFix.Testing.XUnit 1.1.2 — Legacy Microsoft.CodeAnalysis.CSharp.CodeFix.Testing >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: SQLitePCLRaw.lib.e_sqlite3 — SQLitePCLRaw.lib.e_sqlite3 3.50.3 — Legacy SourceGear.sqlite3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0
Deprecated: xunit — xunit 2.9.3 — Legacy xunit.v3 >= 0.0.0

D38 · OSV Dependency Vulnerabilities · Medium CVE · ×21

Medium CVE: EEF-[CVE redacted] Source/Clients/Elixir/mix.lock — cowlib: EEF-[CVE redacted]
Medium CVE: EEF-[CVE redacted] Source/Clients/Elixir/mix.lock — cowlib: EEF-[CVE redacted]
Medium CVE: EEF-[CVE redacted] Source/Clients/Elixir/mix.lock — grpc: EEF-[CVE redacted]
Medium CVE: EEF-[CVE redacted] Source/Clients/Elixir/mix.lock — grpc: EEF-[CVE redacted]
Medium CVE: EEF-[CVE redacted] Source/Clients/Elixir/mix.lock — grpc: EEF-[CVE redacted]
Medium CVE: EEF-[CVE redacted] Source/Clients/Elixir/mix.lock — grpc: EEF-[CVE redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — brace-expansion: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — js-yaml: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — js-yaml: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — serialize-javascript: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — undici: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — validator: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — validator: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — vite: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — ws: [GHSA redacted]

D17 · Explicit Debt · TodoComment · ×15

TodoComment Source/Clients/DotNET/Projections/ChildrenBuilder.cs:36 — // TODO: This is not used, but it should be - figure out what the purpose was. The FromEventProperty method is called from ReadModelPropertiesBuilder — 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 Source/Kernel/Core/Configuration/ConfigurationForObserverProvider.cs:19 — // TODO: Merge with persisted config and attributes. — 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 Source/Kernel/Core/Jobs/JobStep.cs:354 — // TODO: Should we do something here if it fails? — 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 Source/Kernel/Core/Observation/Jobs/ReplayObserver.cs:142 — // TODO: Do we need to do anything special if any replaying partitions failed? — 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 Source/Kernel/Core/Projections/Engine/Pipelines/Steps/SaveChanges.cs:68 — // TODO: Return the number of affected records and pass this along to the changeset storage — 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 Source/Kernel/Core/Projections/Engine/Pipelines/Steps/SetInitialState.cs:73 — // TODO: Ideally we should do this recursively, as properties can be joined deep in the hierarchy and we want to — 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 Source/Kernel/Core/Projections/Engine/Pipelines/Steps/SetInitialState.cs:93 — // TODO: We should improve how we work with Keys and not just "magic strings" like id or _id (MongoDB): — 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 Source/Kernel/Core/Projections/Engine/ProjectionFactory.cs:668 — // TODO: This has an implication in that only one key resolver can exist for each event type, meaning that an event type — 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 Source/Kernel/Core/Services/Observation/Observers.cs:137 — // TODO: We will be formalizing these things in Grains, until then this is less than optimal. — 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 Source/Kernel/Core/Setup/ChronicleServerSiloBuilderExtensions.cs:74 — // TODO: Store Grain state in Database — 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 Source/Kernel/Server/Authentication/OpenIddict/OpenIddictServiceCollectionExtensions.cs:187 — // TODO: Re-enable audience validation when we have a way to set audiences on tokens — 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 Source/Kernel/Storage.MongoDB/Database.cs:79 — // TODO: The name of the database should be configurable or coming from a configurable provider with conventions — 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 Source/Kernel/Storage.MongoDB/EventStoreDatabase.cs:46 — // TODO: The name of the database should be configurable or coming from a configurable provider with conventions — 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 Source/Kernel/Storage.MongoDB/EventStoreNamespaceDatabase.cs:47 — // TODO: Performance optimization - separate reads from writes in a clustered setup. Read from secondary. — 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 Source/Kernel/Storage/Storage.cs:53 — // TODO: This logic should be replaced by formalizing event stores as a Grain and it ensuring existence. Service layer should do this. — 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.

D33 · JS/npm Dependency Vulnerabilities · Medium CVE · ×14

Medium CVE: [CVE redacted] Source/Workbench/yarn.lock — dompurify: [CVE redacted]
Medium CVE: [CVE redacted] Source/Workbench/yarn.lock — dompurify: [CVE redacted]
Medium CVE: [CVE redacted] Source/Workbench/yarn.lock — dompurify: [CVE redacted]
Medium CVE: [CVE redacted] Source/Workbench/yarn.lock — dompurify: [CVE redacted]
Medium CVE: [CVE redacted] Source/Workbench/yarn.lock — dompurify: [CVE redacted]
Medium CVE: [CVE redacted] Source/Workbench/yarn.lock — dompurify: [CVE redacted]
Medium CVE: [CVE redacted] Source/Workbench/yarn.lock — dompurify: [CVE redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Medium CVE: [CVE redacted] Source/Workbench/yarn.lock — ts-deepmerge: [CVE redacted]

D6 · Cohesion (LCOM4) · Low cohesion · ×12

Low cohesion: NullSink (LCOM4 13) Source/Kernel/Storage/Sinks/NullSink.cs:20 — NullSink'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: ExtensionDataDictionary (LCOM4 7) Source/Infrastructure/Schemas/JsonSchema.cs:707 — ExtensionDataDictionary's methods form 7 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: JobStepStorage (LCOM4 7) Source/Kernel/Storage.MongoDB/Jobs/JobStepStorage.cs:22 — JobStepStorage's methods form 7 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: JsonSchema (LCOM4 6) Source/Infrastructure/Schemas/JsonSchema.cs:14 — JsonSchema's methods form 6 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: JobStorage (LCOM4 6) Source/Kernel/Storage.MongoDB/Jobs/JobStorage.cs:24 — JobStorage's methods form 6 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: EventSequenceStorage (LCOM4 5) Source/Kernel/Storage.MongoDB/EventSequences/EventSequenceStorage.cs:41 — EventSequenceStorage's methods form 5 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: InMemorySink (LCOM4 5) Source/Kernel/Storage/Sinks/InMemory/InMemorySink.cs:31 — InMemorySink's methods form 5 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: EncryptionKeySerializer (LCOM4 4) Source/Kernel/Storage.MongoDB/Encryption/EncryptionKeySerializer.cs:13 — EncryptionKeySerializer's methods form 4 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: EventTypeIdSerializer (LCOM4 4) Source/Kernel/Storage.MongoDB/Serializers/EventTypeIdSerializer.cs:12 — EventTypeIdSerializer's methods form 4 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: EventTypeSerializer (LCOM4 4) Source/Kernel/Storage.MongoDB/Serializers/EventTypeSerializer.cs:12 — EventTypeSerializer's methods form 4 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: EventSequenceDbContext (LCOM4 4) Source/Kernel/Storage.Sql/EventStores/Namespaces/EventSequences/EventSequenceDbContext.cs:21 — EventSequenceDbContext's methods form 4 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: EventStoreNamespaceStorage (LCOM4 4) Source/Kernel/Storage.Sql/EventStores/Namespaces/EventStoreNamespaceStorage.cs:37 — EventStoreNamespaceStorage's methods form 4 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.

D5 · Coupling · Off the main sequence · ×8

Off the main sequence: DotNET.CodeAnalysis — DotNET.CodeAnalysis: 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: GrpcCodeGenerator — GrpcCodeGenerator: 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: ResourceEmbedder — ResourceEmbedder: 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: Concepts — Concepts: abstractness 0.02, instability 0.05, distance 0.93 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Infrastructure — Infrastructure: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Contracts — Contracts: abstractness 0.12, instability 0.00, distance 0.88 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: Connections — Connections: abstractness 0.06, instability 0.07, distance 0.87 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
Off the main sequence: AspNetCore — AspNetCore: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and heavily depended-on, so it's rigid to change.

D3 · God Classes · TooManyMethods · ×5

TooManyMethods: ApplicationStore Source/Kernel/Server/Authentication/OpenIddict/ApplicationStore.cs:0 — TooManyMethods — 109 lines, 42 methods.
TooManyMethods: AuthorizationStore Source/Kernel/Server/Authentication/OpenIddict/AuthorizationStore.cs:0 — TooManyMethods — 115 lines, 32 methods.
TooManyMethods: TokenStore Source/Kernel/Server/Authentication/OpenIddict/TokenStore.cs:0 — TooManyMethods — 97 lines, 43 methods.
TooManyMethods: Database Source/Kernel/Storage.Sql/Database.cs:0 — TooManyMethods — 333 lines, 31 methods.
TooManyMethods: Sink Source/Kernel/Storage.Sql/Sinks/Sink.cs:0 — TooManyMethods — 696 lines, 56 methods.

D3 · God Classes · FileTooLong · ×3

FileTooLong: EventSequences/EventSequenceStorage.cs Source/Kernel/Storage.MongoDB/EventSequences/EventSequenceStorage.cs:0 — FileTooLong — 587 lines, 0 methods.
FileTooLong: Sinks/Sink.cs Source/Kernel/Storage.Sql/Sinks/Sink.cs:0 — FileTooLong — 720 lines, 0 methods.
FileTooLong: statistics/coverage-data.js Documentation/statistics/coverage-data.js:0 — FileTooLong — 2111 lines, 0 methods.

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

Duplicated block (13 lines × 2) Source/Kernel/Storage.MongoDB/EventStoreNamespaceDatabase.cs:188 — Source/Kernel/Storage.MongoDB/EventStoreNamespaceDatabase.cs:188-200 | Source/Kernel/Storage.MongoDB/EventStoreNamespaceDatabase.cs:201-213
Duplicated block (13 lines × 2) Source/Kernel/Storage.Sql/EventStores/Namespaces/Seeding/EventSeedingStorage.cs:42 — Source/Kernel/Storage.Sql/EventStores/Namespaces/Seeding/EventSeedingStorage.cs:42-54 | Source/Kernel/Storage.Sql/EventStores/Seeding/EventSeedingStorage.cs:42-54
Duplicated block (13 lines × 2) Source/Kernel/Storage/Compliance/CacheEncryptionKeyStorage.cs:23 — Source/Kernel/Storage/Compliance/CacheEncryptionKeyStorage.cs:23-35 | Source/Kernel/Storage/Compliance/InMemoryEncryptionKeyStorage.cs:55-67

D1 · Cyclomatic Complexity · toEditorPath (cyclomatic 18) · ×2

toEditorPath (cyclomatic 18) Source/Workbench/.yarn/sdks/typescript/lib/tsserverlibrary.js:55 — toEditorPath has cyclomatic complexity 18 (threshold 15).
toEditorPath (cyclomatic 18) Source/Workbench/.yarn/sdks/typescript/lib/tsserver.js:55 — toEditorPath has cyclomatic complexity 18 (threshold 15).

D2 · Cognitive Complexity · toEditorPath (cognitive 21) · ×2

toEditorPath (cognitive 21) Source/Workbench/.yarn/sdks/typescript/lib/tsserverlibrary.js:55 — toEditorPath has cognitive complexity 21 (threshold 15).
toEditorPath (cognitive 21) Source/Workbench/.yarn/sdks/typescript/lib/tsserver.js:55 — toEditorPath has cognitive complexity 21 (threshold 15).

D2 · Cognitive Complexity · onMessage (cognitive 19) · ×2

onMessage (cognitive 19) Source/Workbench/.yarn/sdks/typescript/lib/tsserverlibrary.js:191 — onMessage has cognitive complexity 19 (threshold 15).
onMessage (cognitive 19) Source/Workbench/.yarn/sdks/typescript/lib/tsserver.js:191 — onMessage has cognitive complexity 19 (threshold 15).

D3 · God Classes · ClassTooLong · ×2

ClassTooLong: EventSequenceStorage Source/Kernel/Storage.MongoDB/EventSequences/EventSequenceStorage.cs:0 — ClassTooLong — 570 lines, 24 methods.
ClassTooLong: EventSequenceStorage Source/Kernel/Storage.Sql/EventStores/Namespaces/EventSequences/EventSequenceStorage.cs:0 — ClassTooLong — 429 lines, 24 methods.

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

Duplicated block (17 lines × 2) Source/Clients/DotNET.CodeAnalysis/Analyzers/ConstraintSideEffectAnalyzer.cs:41 — Source/Clients/DotNET.CodeAnalysis/Analyzers/ConstraintSideEffectAnalyzer.cs:41-57 | Source/Clients/DotNET.CodeAnalysis/Analyzers/ProjectionSideEffectAnalyzer.cs:41-57
Duplicated block (17 lines × 2) Source/Kernel/Storage.Sql/EventStores/Namespaces/Seeding/Migrations/v15_0_0.cs:20 — Source/Kernel/Storage.Sql/EventStores/Namespaces/Seeding/Migrations/v15_0_0.cs:20-36 | Source/Kernel/Storage.Sql/EventStores/Seeding/Migrations/v15_0_0.cs:20-29

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

Duplicated block (16 lines × 2) Source/Clients/Api/Program.cs:50 — Source/Clients/Api/Program.cs:50-65 | Source/Kernel/Server/Program.cs:299-314
Duplicated block (16 lines × 2) Source/Clients/DotNET.CodeAnalysis/Analyzers/ReactorEventStoreAndEventSequenceAnalyzer.cs:40 — Source/Clients/DotNET.CodeAnalysis/Analyzers/ReactorEventStoreAndEventSequenceAnalyzer.cs:40-55 | Source/Clients/DotNET.CodeAnalysis/Analyzers/ReducerEventStoreAndEventSequenceAnalyzer.cs:40-55

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

Duplicated block (11 lines × 2) Source/Kernel/Storage.MongoDB/EventSequences/EventSequenceStorage.cs:363 — Source/Kernel/Storage.MongoDB/EventSequences/EventSequenceStorage.cs:363-370 | Source/Kernel/Storage.MongoDB/EventSequences/EventSequenceStorage.cs:378-388
Duplicated block (11 lines × 2) Source/Kernel/Storage.Sql/EventStores/Namespaces/Seeding/EventSeedingStorage.cs:25 — Source/Kernel/Storage.Sql/EventStores/Namespaces/Seeding/EventSeedingStorage.cs:25-34 | Source/Kernel/Storage.Sql/EventStores/Seeding/EventSeedingStorage.cs:24-34

D1 · Cyclomatic Complexity · ReadModelMigrator.GetColumnType (cyclomatic 63) · ×1

ReadModelMigrator.GetColumnType (cyclomatic 63) Source/Kernel/Storage.Sql/EventStores/Namespaces/ReadModels/ReadModelMigrator.cs:199 — ReadModelMigrator.GetColumnType has cyclomatic complexity 63 (threshold 15).

D1 · Cyclomatic Complexity · BsonValueExtensions.ToBsonValue (cyclomatic 34) · ×1

BsonValueExtensions.ToBsonValue (cyclomatic 34) Source/Kernel/Storage.MongoDB/BsonValueExtensions.cs:26 — BsonValueExtensions.ToBsonValue has cyclomatic complexity 34 (threshold 15).

D1 · Cyclomatic Complexity · BsonValueExtensions.ToTargetType (cyclomatic 31) · ×1

BsonValueExtensions.ToTargetType (cyclomatic 31) Source/Kernel/Storage.MongoDB/BsonValueExtensions.cs:189 — BsonValueExtensions.ToTargetType has cyclomatic complexity 31 (threshold 15).

D1 · Cyclomatic Complexity · ObjectComparer.CompareValues (cyclomatic 30) · ×1

ObjectComparer.CompareValues (cyclomatic 30) Source/Infrastructure/Changes/ObjectComparer.cs:220 — ObjectComparer.CompareValues has cyclomatic complexity 30 (threshold 15).

D1 · Cyclomatic Complexity · MethodBodyReader.ConstructInstructions (cyclomatic 24) · ×1

MethodBodyReader.ConstructInstructions (cyclomatic 24) Source/Tools/GrpcClients/MethodBodyReader.cs:161 — MethodBodyReader.ConstructInstructions has cyclomatic complexity 24 (threshold 15).

D1 · Cyclomatic Complexity · TypeFormats.GetJsonTypeForClrType (cyclomatic 21) · ×1

TypeFormats.GetJsonTypeForClrType (cyclomatic 21) Source/Infrastructure/Schemas/TypeFormats.cs:96 — TypeFormats.GetJsonTypeForClrType has cyclomatic complexity 21 (threshold 15).

D1 · Cyclomatic Complexity · ILInstruction.GetCode (cyclomatic 21) · ×1

ILInstruction.GetCode (cyclomatic 21) Source/Tools/GrpcClients/ILInstruction.cs:33 — ILInstruction.GetCode has cyclomatic complexity 21 (threshold 15).

D1 · Cyclomatic Complexity · TypeHelper.GetTypeName (cyclomatic 21) · ×1

TypeHelper.GetTypeName (cyclomatic 21) Source/Tools/GrpcCodeGenerator/TypeHelper.cs:155 — TypeHelper.GetTypeName has cyclomatic complexity 21 (threshold 15).

D1 · Cyclomatic Complexity · getExportedSymbols (cyclomatic 21) · ×1

getExportedSymbols (cyclomatic 21) Source/Clients/TypeScript/generate-generated-index.mjs:39 — getExportedSymbols has cyclomatic complexity 21 (threshold 15).

D1 · Cyclomatic Complexity · ExpandoObjectConverter.ConvertJsonValueFromUnknownFormat (cyclomatic 20) · ×1

ExpandoObjectConverter.ConvertJsonValueFromUnknownFormat (cyclomatic 20) Source/Infrastructure/Json/ExpandoObjectConverter.cs:246 — ExpandoObjectConverter.ConvertJsonValueFromUnknownFormat has cyclomatic complexity 20 (threshold 15).

D1 · Cyclomatic Complexity · ExpandoObjectConverter.ConvertToJsonNodeFromUnknownFormat (cyclomatic 20) · ×1

ExpandoObjectConverter.ConvertToJsonNodeFromUnknownFormat (cyclomatic 20) Source/Infrastructure/Json/ExpandoObjectConverter.cs:427 — ExpandoObjectConverter.ConvertToJsonNodeFromUnknownFormat has cyclomatic complexity 20 (threshold 15).

D1 · Cyclomatic Complexity · ChronicleConnectionStringBuilder.Build (cyclomatic 19) · ×1

ChronicleConnectionStringBuilder.Build (cyclomatic 19) Source/Clients/Connections/ChronicleConnectionStringBuilder.cs:216 — ChronicleConnectionStringBuilder.Build has cyclomatic complexity 19 (threshold 15).

D1 · Cyclomatic Complexity · MethodBodyReader.Write (cyclomatic 17) · ×1

MethodBodyReader.Write (cyclomatic 17) Source/Tools/GrpcClients/MethodBodyReader.cs:81 — MethodBodyReader.Write has cyclomatic complexity 17 (threshold 15).

D1 · Cyclomatic Complexity · ExpandoObjectExtensions.EnsurePath (cyclomatic 16) · ×1

ExpandoObjectExtensions.EnsurePath (cyclomatic 16) Source/Infrastructure/Dynamic/ExpandoObjectExtensions.cs:150 — ExpandoObjectExtensions.EnsurePath has cyclomatic complexity 16 (threshold 15).

D1 · Cyclomatic Complexity · BsonValueExtensions.ToBsonValueBasedOnSchemaPropertyType (cyclomatic 16) · ×1

BsonValueExtensions.ToBsonValueBasedOnSchemaPropertyType (cyclomatic 16) Source/Kernel/Storage.MongoDB/BsonValueExtensions.cs:298 — BsonValueExtensions.ToBsonValueBasedOnSchemaPropertyType has cyclomatic complexity 16 (threshold 15).

D1 · Cyclomatic Complexity · Sink.CoerceForColumn (cyclomatic 16) · ×1

Sink.CoerceForColumn (cyclomatic 16) Source/Kernel/Storage.Sql/Sinks/Sink.cs:1094 — Sink.CoerceForColumn has cyclomatic complexity 16 (threshold 15).

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 · Analyzed solution does not cover the bulk of the repository · ×1

Analyzed solution does not cover the bulk of the repository — The scored solution `Chronicle.slnx` is not representative of this repository — it references only 0 of 5681 discovered C# files (0 %). 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 · KeyJsonConverter.Read (cognitive 53) · ×1

KeyJsonConverter.Read (cognitive 53) Source/Kernel/Concepts/Keys/KeyJsonConverter.cs:16 — KeyJsonConverter.Read has cognitive complexity 53 (threshold 15).

D2 · Cognitive Complexity · BsonValueExtensions.ToTargetType (cognitive 45) · ×1

BsonValueExtensions.ToTargetType (cognitive 45) Source/Kernel/Storage.MongoDB/BsonValueExtensions.cs:189 — BsonValueExtensions.ToTargetType has cognitive complexity 45 (threshold 15).

D2 · Cognitive Complexity · ExpandoObjectExtensions.EnsurePath (cognitive 42) · ×1

ExpandoObjectExtensions.EnsurePath (cognitive 42) Source/Infrastructure/Dynamic/ExpandoObjectExtensions.cs:150 — ExpandoObjectExtensions.EnsurePath has cognitive complexity 42 (threshold 15).

D2 · Cognitive Complexity · getExportedSymbols (cognitive 38) · ×1

getExportedSymbols (cognitive 38) Source/Clients/TypeScript/generate-generated-index.mjs:39 — getExportedSymbols has cognitive complexity 38 (threshold 15).

D2 · Cognitive Complexity · ObjectComparer.CompareValues (cognitive 34) · ×1

ObjectComparer.CompareValues (cognitive 34) Source/Infrastructure/Changes/ObjectComparer.cs:220 — ObjectComparer.CompareValues has cognitive complexity 34 (threshold 15).

D2 · Cognitive Complexity · ExpandoObjectConverter.ConvertToJsonNodeFromUnknownFormat (cognitive 25) · ×1

ExpandoObjectConverter.ConvertToJsonNodeFromUnknownFormat (cognitive 25) Source/Infrastructure/Json/ExpandoObjectConverter.cs:427 — ExpandoObjectConverter.ConvertToJsonNodeFromUnknownFormat has cognitive complexity 25 (threshold 15).

D2 · Cognitive Complexity · ILInstruction.GetCode (cognitive 25) · ×1

ILInstruction.GetCode (cognitive 25) Source/Tools/GrpcClients/ILInstruction.cs:33 — ILInstruction.GetCode has cognitive complexity 25 (threshold 15).

D2 · Cognitive Complexity · Changeset.AddChild (cognitive 23) · ×1

Changeset.AddChild (cognitive 23) Source/Infrastructure/Changes/Changeset.cs:102 — Changeset.AddChild has cognitive complexity 23 (threshold 15).

D2 · Cognitive Complexity · ExpandoObjectConverter.ConvertJsonValueFromUnknownFormat (cognitive 23) · ×1

ExpandoObjectConverter.ConvertJsonValueFromUnknownFormat (cognitive 23) Source/Infrastructure/Json/ExpandoObjectConverter.cs:246 — ExpandoObjectConverter.ConvertJsonValueFromUnknownFormat has cognitive complexity 23 (threshold 15).

D2 · Cognitive Complexity · Changeset.ConsolidateConflictingOperations (cognitive 22) · ×1

Changeset.ConsolidateConflictingOperations (cognitive 22) Source/Infrastructure/Changes/Changeset.cs:403 — Changeset.ConsolidateConflictingOperations has cognitive complexity 22 (threshold 15).

D2 · Cognitive Complexity · TypeDiscovery.DiscoverServices (cognitive 21) · ×1

TypeDiscovery.DiscoverServices (cognitive 21) Source/Tools/GrpcCodeGenerator/TypeDiscovery.cs:23 — TypeDiscovery.DiscoverServices has cognitive complexity 21 (threshold 15).

D2 · Cognitive Complexity · ExpandoObjectConverter.ToJsonObject (cognitive 20) · ×1

ExpandoObjectConverter.ToJsonObject (cognitive 20) Source/Infrastructure/Json/ExpandoObjectConverter.cs:25 — ExpandoObjectConverter.ToJsonObject has cognitive complexity 20 (threshold 15).

D2 · Cognitive Complexity · OpenIddictServiceCollectionExtensions.AddOpenIddictIfEnabled (cognitive 20) · ×1

OpenIddictServiceCollectionExtensions.AddOpenIddictIfEnabled (cognitive 20) Source/Kernel/Server/Authentication/OpenIddict/OpenIddictServiceCollectionExtensions.cs:27 — OpenIddictServiceCollectionExtensions.AddOpenIddictIfEnabled has cognitive complexity 20 (threshold 15).

D2 · Cognitive Complexity · TypeHelper.GetTypeName (cognitive 20) · ×1

TypeHelper.GetTypeName (cognitive 20) Source/Tools/GrpcCodeGenerator/TypeHelper.cs:155 — TypeHelper.GetTypeName has cognitive complexity 20 (threshold 15).

D2 · Cognitive Complexity · ExpandoObjectExtensions.Clone (cognitive 18) · ×1

ExpandoObjectExtensions.Clone (cognitive 18) Source/Infrastructure/Dynamic/ExpandoObjectExtensions.cs:29 — ExpandoObjectExtensions.Clone has cognitive complexity 18 (threshold 15).

D2 · Cognitive Complexity · ObjectExtensions.EnsurePath (cognitive 18) · ×1

ObjectExtensions.EnsurePath (cognitive 18) Source/Infrastructure/Objects/ObjectExtensions.cs:60 — ObjectExtensions.EnsurePath has cognitive complexity 18 (threshold 15).

D2 · Cognitive Complexity · ReadModelMigrator.GetColumnType (cognitive 18) · ×1

ReadModelMigrator.GetColumnType (cognitive 18) Source/Kernel/Storage.Sql/EventStores/Namespaces/ReadModels/ReadModelMigrator.cs:199 — ReadModelMigrator.GetColumnType has cognitive complexity 18 (threshold 15).

D2 · Cognitive Complexity · Sink.RemoveChildFromAllEntries (cognitive 18) · ×1

Sink.RemoveChildFromAllEntries (cognitive 18) Source/Kernel/Storage.Sql/Sinks/Sink.cs:471 — Sink.RemoveChildFromAllEntries has cognitive complexity 18 (threshold 15).

D2 · Cognitive Complexity · MethodBodyReader.Write (cognitive 18) · ×1

MethodBodyReader.Write (cognitive 18) Source/Tools/GrpcClients/MethodBodyReader.cs:81 — MethodBodyReader.Write has cognitive complexity 18 (threshold 15).

D2 · Cognitive Complexity · MethodBodyReader.ConstructInstructions (cognitive 18) · ×1

MethodBodyReader.ConstructInstructions (cognitive 18) Source/Tools/GrpcClients/MethodBodyReader.cs:161 — MethodBodyReader.ConstructInstructions has cognitive complexity 18 (threshold 15).

D2 · Cognitive Complexity · Changeset.ConsolidatePropertiesChangedIntoChildAdded (cognitive 17) · ×1

Changeset.ConsolidatePropertiesChangedIntoChildAdded (cognitive 17) Source/Infrastructure/Changes/Changeset.cs:319 — Changeset.ConsolidatePropertiesChangedIntoChildAdded has cognitive complexity 17 (threshold 15).

D2 · Cognitive Complexity · JsonSchema.Validate (cognitive 17) · ×1

JsonSchema.Validate (cognitive 17) Source/Infrastructure/Schemas/JsonSchema.cs:479 — JsonSchema.Validate has cognitive complexity 17 (threshold 15).

D2 · Cognitive Complexity · BsonValueExtensions.ToBsonValueBasedOnSchemaPropertyType (cognitive 17) · ×1

BsonValueExtensions.ToBsonValueBasedOnSchemaPropertyType (cognitive 17) Source/Kernel/Storage.MongoDB/BsonValueExtensions.cs:298 — BsonValueExtensions.ToBsonValueBasedOnSchemaPropertyType has cognitive complexity 17 (threshold 15).

D2 · Cognitive Complexity · UnitOfWorkMiddleware.InvokeAsync (cognitive 16) · ×1

UnitOfWorkMiddleware.InvokeAsync (cognitive 16) Source/Clients/AspNetCore/Transactions/UnitOfWorkMiddleware.cs:27 — UnitOfWorkMiddleware.InvokeAsync has cognitive complexity 16 (threshold 15).

D2 · Cognitive Complexity · BsonValueExtensions.ToBsonValue (cognitive 16) · ×1

BsonValueExtensions.ToBsonValue (cognitive 16) Source/Kernel/Storage.MongoDB/BsonValueExtensions.cs:26 — BsonValueExtensions.ToBsonValue has cognitive complexity 16 (threshold 15).

D2 · Cognitive Complexity · Sink.ApplyChanges (cognitive 16) · ×1

Sink.ApplyChanges (cognitive 16) Source/Kernel/Storage.MongoDB/Sinks/Sink.cs:86 — Sink.ApplyChanges has cognitive complexity 16 (threshold 15).

D2 · Cognitive Complexity · Sink.CoerceForColumn (cognitive 16) · ×1

Sink.CoerceForColumn (cognitive 16) Source/Kernel/Storage.Sql/Sinks/Sink.cs:1094 — Sink.CoerceForColumn has cognitive complexity 16 (threshold 15).

D31 · IaC & Container Security · Medium IaC · ×1

Medium IaC: DS-0001 Docker/Local/Dockerfile — ':latest' tag used

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 (21 lines × 2) · ×1

Duplicated block (21 lines × 2) Source/Kernel/Storage.Sql/EventStores/Namespaces/EventSequences/EventEntryConverter.cs:485 — Source/Kernel/Storage.Sql/EventStores/Namespaces/EventSequences/EventEntryConverter.cs:485-500 | Source/Kernel/Storage.Sql/Sinks/Sink.cs:1184-1204

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

Duplicated block (20 lines × 2) Source/Clients/DotNET.CodeAnalysis/Analyzers/ConstraintExpressionLambdaAnalyzer.cs:45 — Source/Clients/DotNET.CodeAnalysis/Analyzers/ConstraintExpressionLambdaAnalyzer.cs:45-64 | Source/Clients/DotNET.CodeAnalysis/Analyzers/ProjectionExpressionLambdaAnalyzer.cs:45-64

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

Duplicated block (19 lines × 2) Source/Clients/DotNET.CodeAnalysis/Analyzers/ConstraintImperativeCodeAnalyzer.cs:41 — Source/Clients/DotNET.CodeAnalysis/Analyzers/ConstraintImperativeCodeAnalyzer.cs:41-59 | Source/Clients/DotNET.CodeAnalysis/Analyzers/ProjectionImperativeCodeAnalyzer.cs:41-59

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

Duplicated block (15 lines × 2) Source/Kernel/Storage.MongoDB/Sinks/Sink.cs:438 — Source/Kernel/Storage.MongoDB/Sinks/Sink.cs:438-452 | Source/Kernel/Storage/Sinks/InMemory/InMemorySink.cs:278-292

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

Duplicated block (12 lines × 3) Source/Clients/DotNET.CodeAnalysis/Analyzers/ModelBoundProjectionMultipleEventStoresAnalyzer.cs:65 — Source/Clients/DotNET.CodeAnalysis/Analyzers/ModelBoundProjectionMultipleEventStoresAnalyzer.cs:65-76 | Source/Clients/DotNET.CodeAnalysis/Analyzers/ReactorMultipleEventStoresAnalyzer.cs:53-64 | Source/Clients/DotNET.CodeAnalysis/Analyzers/ReducerMultipleEventStoresAnalyzer.cs:53-64

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

Duplicated block (10 lines × 2) Source/Kernel/Storage.Sql/EventStores/Namespaces/JobSteps/JobStepStorage.cs:184 — Source/Kernel/Storage.Sql/EventStores/Namespaces/JobSteps/JobStepStorage.cs:184-193 | Source/Kernel/Storage.Sql/EventStores/Namespaces/JobSteps/JobStepStorage.cs:243-252

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

Duplicated block (9 lines × 2) Source/Kernel/Storage.Sql/EventStores/Namespaces/ReadModels/ReadModelMigrator.cs:288 — Source/Kernel/Storage.Sql/EventStores/Namespaces/ReadModels/ReadModelMigrator.cs:288-296 | Source/Kernel/Storage.Sql/EventStores/Namespaces/ReadModels/ReadModelMigrator.cs:300-308

D5 · Coupling · Unstable project Server · ×1

Unstable project Server — Server has instability 0.92 with 1 dependents.

Recommendation — 101 finding(s)

D10 · Test Quality · No direct assertions · ×59

No direct assertions: should_report_imperative_expression_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ConstraintExpressionLambdaAnalyzer/when_analyzing_constraint_expression_lambdas/and_expression_lambda_contains_method_call.cs:27 — 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: should_not_report_any_diagnostics Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ConstraintExpressionLambdaAnalyzer/when_analyzing_constraint_expression_lambdas/and_expression_lambda_only_accesses_members.cs:24 — 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: should_report_imperative_code_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ConstraintImperativeCodeAnalyzer/when_analyzing_constraint_define_methods/and_define_contains_if_statement.cs:30 — 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: should_not_report_any_diagnostics Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ConstraintImperativeCodeAnalyzer/when_analyzing_constraint_define_methods/and_define_only_contains_builder_calls.cs:24 — 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: should_not_report_any_diagnostics Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ConstraintSideEffectAnalyzer/when_analyzing_constraint_types/and_constraint_has_no_side_effect_injections.cs:24 — 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: should_report_side_effect_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ConstraintSideEffectAnalyzer/when_analyzing_constraint_types/and_constraint_injects_command_pipeline.cs:25 — 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: should_report_side_effect_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ConstraintSideEffectAnalyzer/when_analyzing_constraint_types/and_constraint_injects_event_log.cs:25 — 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: should_report_event_type_attribute_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_DeclarativeProjectionAnalyzer/when_analyzing_projection_builder_methods/and_generic_event_type_is_missing_event_type_attribute.cs:36 — 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: should_not_report_any_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_DeclarativeProjectionMultipleEventStoresAnalyzer/when_analyzing_projection_builder_methods/and_all_event_types_have_same_event_store_from_assembly_attribute.cs:40 — 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: should_not_report_any_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_DeclarativeProjectionMultipleEventStoresAnalyzer/when_analyzing_projection_builder_methods/and_all_event_types_have_the_same_event_store.cs:40 — 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: should_report_multiple_event_stores_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_DeclarativeProjectionMultipleEventStoresAnalyzer/when_analyzing_projection_builder_methods/and_event_types_have_different_event_stores.cs:41 — 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: should_not_report_diagnostics Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_EventSequenceAppendAnalyzer/when_analyzing_append/and_type_is_marked_with_client_event_type.cs:59 — 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: should_not_report_diagnostics Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_EventSequenceAppendAnalyzer/when_analyzing_append/and_type_is_marked_with_event_type.cs:31 — 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: should_report_event_type_attribute_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_EventSequenceAppendAnalyzer/when_analyzing_append/and_type_is_not_marked_with_event_type.cs:30 — 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: should_not_report_diagnostics Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_EventTypeNullablePropertiesAnalyzer/when_analyzing_event_types/and_event_type_has_no_nullable_properties.cs:21 — 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: should_report_warning_for_each_nullable_property Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_EventTypeNullablePropertiesAnalyzer/when_analyzing_event_types/and_event_type_has_nullable_properties.cs:26 — 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: should_report_record_type_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_EventTypeRecordAnalyzer/when_analyzing_event_types/and_event_type_is_a_class.cs:25 — 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: should_not_report_any_diagnostics Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_EventTypeRecordAnalyzer/when_analyzing_event_types/and_event_type_is_a_record.cs:19 — 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: should_not_report_any_diagnostics Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_EventTypeRecordAnalyzer/when_analyzing_event_types/and_type_has_no_event_type_attribute.cs:21 — 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: should_report_event_type_attribute_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ModelBoundProjectionAttributeAnalyzer/when_analyzing_model_bound_projection_attributes/and_event_type_is_missing_event_type_attribute.cs:26 — 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: should_not_report_any_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ModelBoundProjectionMultipleEventStoresAnalyzer/when_analyzing_model_bound_projection_types/and_all_event_types_have_same_event_store_from_assembly_attribute.cs:28 — 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: should_not_report_any_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ModelBoundProjectionMultipleEventStoresAnalyzer/when_analyzing_model_bound_projection_types/and_all_event_types_have_the_same_event_store.cs:28 — 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: should_report_multiple_event_stores_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ModelBoundProjectionMultipleEventStoresAnalyzer/when_analyzing_model_bound_projection_types/and_event_types_have_different_event_stores.cs:29 — 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: should_report_multiple_event_stores_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ModelBoundProjectionMultipleEventStoresAnalyzer/when_analyzing_model_bound_projection_types/and_one_event_type_uses_the_default_store_and_another_uses_an_explicit_store.cs:30 — 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: should_report_imperative_expression_diagnostic Source/Clients/DotNET.CodeAnalysis.Specs/Analyzers/for_ProjectionExpressionLambdaAnalyzer/when_analyzing_projection_expression_lambdas/and_expression_lambda_contains_method_call.cs:34 — In a harness-style test project (most tests assert via a verifier/approval harness or step indirection) — no conventional assertion call was detected.
+ 34 more in this group — see findings.md.

D26 · Project Cohesion · Large project · ×11

Large project: Client — 0 LoC, 589 public types across 122 namespaces — review for cohesion.
Large project: Infrastructure.Specs — 0 LoC, 169 public types across 30 namespaces — review for cohesion.
Large project: DotNET.Specs — 0 LoC, 1022 public types across 221 namespaces — review for cohesion.
Large project: DotNET — 0 LoC, 510 public types across 34 namespaces — review for cohesion.
Large project: Concepts — 5953 LoC, 236 public types across 29 namespaces — review for cohesion.
Large project: Contracts — 7309 LoC, 237 public types across 23 namespaces — review for cohesion.
Large project: Core.Specs — 0 LoC, 803 public types across 245 namespaces — review for cohesion.
Large project: Core — 0 LoC, 640 public types across 61 namespaces — review for cohesion.
Large project: Storage.MongoDB.Specs — 0 LoC, 133 public types across 44 namespaces — review for cohesion.
Large project: Storage.MongoDB — 10126 LoC, 181 public types across 27 namespaces — review for cohesion.
Large project: Storage.Sql — 12747 LoC, 172 public types across 64 namespaces — review for cohesion.

D38 · OSV Dependency Vulnerabilities · Low CVE · ×7

Low CVE: [GHSA redacted] Source/Workbench/yarn.lock — diff: [GHSA redacted]
Low CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Low CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Low CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Low CVE: [GHSA redacted] Source/Workbench/yarn.lock — esbuild: [GHSA redacted]
Low CVE: [GHSA redacted] Source/Workbench/yarn.lock — undici: [GHSA redacted]
Low CVE: [GHSA redacted] Source/Workbench/yarn.lock — undici: [GHSA redacted]

D31 · IaC & Container Security · Low IaC · ×6

Low IaC: DS-0026 Docker/Development/Dockerfile — No HEALTHCHECK defined
Low IaC: DS-0026 Docker/DevelopmentSlim/Dockerfile — No HEALTHCHECK defined
Low IaC: DS-0026 Docker/Local/Dockerfile — No HEALTHCHECK defined
Low IaC: DS-0026 Docker/LocalSlim/Dockerfile — No HEALTHCHECK defined
Low IaC: DS-0026 Docker/Production/Dockerfile — No HEALTHCHECK defined
Low IaC: DS-0026 Docker/Workbench/Dockerfile — No HEALTHCHECK defined

D33 · JS/npm Dependency Vulnerabilities · Low CVE · ×5

Low CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Low CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Low CVE: [GHSA redacted] Source/Workbench/yarn.lock — dompurify: [GHSA redacted]
Low CVE: [CVE redacted] Source/Workbench/yarn.lock — quill: [CVE redacted]
Low CVE: [CVE redacted] Source/Workbench/yarn.lock — react-router: [CVE redacted]

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

D15 · Churn × Complexity Hotspots · single-commit history · ×1

single-commit history — no churn to measure hotspots — single-commit history — no churn to measure hotspots: no production file changed in the last 90 days, so the churn × complexity hotspot signal is unavailable — not scored for this run.

D17 · Explicit Debt · ObsoleteWithoutCallers · ×1

ObsoleteWithoutCallers Source/Kernel/Storage/Observation/ObserverState.cs:91 — [Obsolete] HandledEventTypesCount

D23 · Boundary Type-Coupling · Bounded contexts not declared · ×1

Bounded contexts not declared — large codebase (58,999 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.

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

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 — 504 finding(s)

D17 · Explicit Debt · Justified suppression · ×337

Justified suppression Integration/Api/ChronicleOutOfProcessFixtureWithLocalImage.cs:66 — #pragma warning disable MA0039 // Do not write your own certificate validation method
Justified suppression Integration/Api/given/an_http_client.cs:13 — #pragma warning disable IDE0290 // Use primary constructor
Justified suppression Integration/Api/given/an_http_client.cs:29 — #pragma warning disable MA0039 // Do not write your own certificate validation method
Justified suppression Integration/Api/HttpsHealthWait.cs:26 — #pragma warning disable MA0039 // Do not write your own certificate validation method
Justified suppression Integration/Api/HttpsHealthWait.cs:35 — #pragma warning disable CA5400 // HttpClient may be created without enabling CheckCertificateRevocationList
Justified suppression Integration/Client/ChronicleConfigurableFixture.cs:150 — empty catch in test code (best-effort teardown)
Justified suppression Integration/Client/ChronicleConfigurableFixture.cs:521 — empty catch in test code (best-effort teardown)
Justified suppression Integration/Client/ChronicleConfigurableFixture.cs:66 — #pragma warning disable CA2213 // _outOfProcessKernelContainer is a reference to the container the base class owns and disposes via base.DisposeAsync.
Justified suppression Integration/Client/Projections/Scenarios/ModelBound/when_projecting_child_with_class_level_parent_key/and_child_event_is_appended_to_its_own_event_source.cs:4 — #pragma warning disable SA1402 // File may only contain a single type
Justified suppression Integration/Client/Projections/Scenarios/ModelBound/when_projecting_self_referential_children_declaratively/and_sub_feature_is_added.cs:4 — #pragma warning disable SA1402 // File may only contain a single type
Justified suppression Integration/Client/Projections/Scenarios/ModelBound/when_projecting_self_referential_children_declaratively/and_sub_feature_is_added.cs:11 — #pragma warning disable RCS1181 // Convert comment to documentation comment
Justified suppression Integration/Client/Projections/Scenarios/ModelBound/when_renaming_a_nested_self_referential_feature/and_rename_carries_module_as_parent_key.cs:4 — #pragma warning disable SA1402 // File may only contain a single type
Justified suppression Integration/Client/Projections/Scenarios/ModelBound/when_renaming_a_nested_self_referential_feature/and_rename_carries_module_as_parent_key.cs:13 — #pragma warning disable RCS1181 // Convert comment to documentation comment
Justified suppression Integration/Client/Projections/Scenarios/when_projecting_with_nested_in_children/setting_the_nested_object.cs:4 — #pragma warning disable SA1402 // File may only contain a single type
Justified suppression Integration/Client/Projections/Scenarios/when_projecting_with_nested_in_nested/setting_the_outer_nested_object.cs:4 — #pragma warning disable SA1402 // File may only contain a single type
Justified suppression Integration/Client/Projections/Scenarios/when_projecting_with_nested_in_nested_from_pdl/given/a_compiled_pdl_nested_projection.cs:4 — #pragma warning disable SA1402 // File may only contain a single type
Justified suppression Integration/Client/Projections/Scenarios/when_projecting_with_nested_in_nested_from_pdl/given/a_compiled_pdl_nested_projection.cs:5 — #pragma warning disable SA1649 // File name should match first type name
Justified suppression Integration/Client/Projections/Scenarios/when_projecting_with_nested_object/setting_the_nested_object.cs:4 — #pragma warning disable SA1402 // File may only contain a single type
Justified suppression Integration/Client/Projections/Scenarios/when_projecting_with_watcher.cs:24 — #pragma warning disable CA2213 // Disposable fields should be disposed
Justified suppression Integration/MongoDB/Jobs/IntegrationJob.cs:8 — #pragma warning disable SA1649 // File name should match first type name
Justified suppression Source/GlobalUsings.Specs.cs:4 — #pragma warning disable IDE0005 // Using directive is unnecessary.
Justified suppression Source/Infrastructure.Specs/Changes/for_ObjectsComparer/when_comparing_complex_nested_expando_object_with_changes.cs:34 — #pragma warning disable IDE0300 // Simplify collection initialization
Justified suppression Source/Infrastructure.Specs/Changes/for_ObjectsComparer/when_comparing_complex_nested_expando_object_with_changes.cs:49 — #pragma warning disable IDE0300 // Simplify collection initialization
Justified suppression Source/Infrastructure.Specs/Objects/for_ObjectExtensions/Types.cs:6 — #pragma warning disable SA1649 // File name should match first type name
Justified suppression Source/Infrastructure.Specs/Objects/for_ObjectExtensions/Types.cs:7 — #pragma warning disable SA1402 // File may only contain a single type
+ 312 more in this group — see findings.md.

D12 · Dependency Hygiene · Outdated · ×113

Outdated: Cratis.Arc — Cratis.Arc 20.43.6 → 20.44.0 available.
Outdated: Cratis.Arc.MongoDB — Cratis.Arc.MongoDB 20.43.6 → 20.44.0 available.
Outdated: Cratis.Arc.Swagger — Cratis.Arc.Swagger 20.43.6 → 20.44.0 available.
Outdated: Cratis.Fundamentals — Cratis.Fundamentals 7.16.0 → 7.16.1 available.
Outdated: Meziantou.Analyzer — Meziantou.Analyzer 3.0.104 → 3.0.105 available.
Outdated: Cratis.Arc — Cratis.Arc 20.43.6 → 20.44.0 available.
Outdated: Cratis.Arc.MongoDB — Cratis.Arc.MongoDB 20.43.6 → 20.44.0 available.
Outdated: Cratis.Fundamentals — Cratis.Fundamentals 7.16.0 → 7.16.1 available.
Outdated: Meziantou.Analyzer — Meziantou.Analyzer 3.0.104 → 3.0.105 available.
Outdated: Cratis.Arc.Core — Cratis.Arc.Core 20.43.6 → 20.44.0 available.
Outdated: Cratis.Arc.MongoDB — Cratis.Arc.MongoDB 20.43.6 → 20.44.0 available.
Outdated: Cratis.Fundamentals — Cratis.Fundamentals 7.16.0 → 7.16.1 available.
Outdated: Meziantou.Analyzer — Meziantou.Analyzer 3.0.104 → 3.0.105 available.
Outdated: Cratis.Fundamentals — Cratis.Fundamentals 7.16.0 → 7.16.1 available.
Outdated: Meziantou.Analyzer — Meziantou.Analyzer 3.0.104 → 3.0.105 available.
Outdated: Cratis.Arc — Cratis.Arc 20.43.6 → 20.44.0 available.
Outdated: Cratis.Arc.Core — Cratis.Arc.Core 20.43.6 → 20.44.0 available.
Outdated: Cratis.Fundamentals — Cratis.Fundamentals 7.16.0 → 7.16.1 available.
Outdated: Meziantou.Analyzer — Meziantou.Analyzer 3.0.104 → 3.0.105 available.
Outdated: Cratis.Fundamentals — Cratis.Fundamentals 7.16.0 → 7.16.1 available.
Outdated: Meziantou.Analyzer — Meziantou.Analyzer 3.0.104 → 3.0.105 available.
Outdated: Cratis.Arc — Cratis.Arc 20.43.6 → 20.44.0 available.
Outdated: Cratis.Arc.Core — Cratis.Arc.Core 20.43.6 → 20.44.0 available.
Outdated: Cratis.Arc.ProxyGenerator.Build — Cratis.Arc.ProxyGenerator.Build 20.43.6 → 20.44.0 available.
Outdated: Cratis.Arc.Swagger — Cratis.Arc.Swagger 20.43.6 → 20.44.0 available.
+ 88 more in this group — see findings.md.

D10 · Test Quality · Skipped (documented) · ×7

Skipped (documented): should_have_correct_next_sequence_number Integration/Client/for_Reactors/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:42 — Skipped with a documented reason — a deferral, not lazy debt: Not waiting for the observer does not work
Skipped (documented): should_have_correct_tail_sequence_number Integration/Client/for_Reactors/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:47 — Skipped with a documented reason — a deferral, not lazy debt: Not waiting for the observer does not work
Skipped (documented): should_have_handled_the_event Integration/Client/for_Reactors/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:52 — Skipped with a documented reason — a deferral, not lazy debt: Not waiting for the observer does not work
Skipped (documented): should_have_correct_next_sequence_number Integration/Client/for_Reducers/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:42 — Skipped with a documented reason — a deferral, not lazy debt: Not waiting for the observer does not work
Skipped (documented): should_have_correct_tail_sequence_number Integration/Client/for_Reducers/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:47 — Skipped with a documented reason — a deferral, not lazy debt: Not waiting for the observer does not work
Skipped (documented): should_have_handled_the_event Integration/Client/for_Reducers/when_appending_event/and_not_waiting_for_observer_to_be_active.cs:52 — Skipped with a documented reason — a deferral, not lazy debt: Not waiting for the observer does not work
Skipped (documented): should_not_fail Source/Kernel/Core.Specs/Observation/Jobs/for_HandleEventsForPartition/when_reporting_new_successfully_handled_event.cs:11 — Skipped with a documented reason — a deferral, not lazy debt: Orleans TestKit does not implement GrainFactory.GetGrain(GrainId)

D18 · Solution Shape · Api (Production) · ×2

Api (Production) Integration/Api/Api.csproj — 15 .cs files, 691 LoC (479 significant)
Api (Production) Source/Clients/Api/Api.csproj — 120 .cs files, 4761 LoC (2306 significant)

D10 · Test Quality · Mock framework · ×1

Mock framework: NSubstitute — MongoDB references NSubstitute.

D14 · License Compliance · Licenses scanned · ×1

Licenses scanned — 85 packages scanned; 4 distinct SPDX licenses.

D18 · Solution Shape · Build did not complete in the analyzer · ×1

Build did not complete in the analyzer — `dotnet build` reported 2 error(s) but no C# compiler diagnostic — an SDK / target-framework / restore mismatch in the analyzer environment, not a code defect (common for an older codebase whose target framework the analyzer's SDK can't build). Solution Shape is scored on structure and is NOT capped; the C# semantic analysis loads independently and is unaffected.

D18 · Solution Shape · Client (Production) · ×1

Client (Production) Integration/Client/Client.csproj — 523 .cs files, 18401 LoC (12797 significant)

D18 · Solution Shape · Kernel (Production) · ×1

Kernel (Production) Integration/Kernel/Kernel.csproj — 31 .cs files, 1328 LoC (1004 significant)

D18 · Solution Shape · MongoDB (Test) · ×1

MongoDB (Test) Integration/MongoDB/MongoDB.csproj — 19 .cs files, 849 LoC (613 significant)

D18 · Solution Shape · Infrastructure.Specs (Production) · ×1

Infrastructure.Specs (Production) Source/Infrastructure.Specs/Infrastructure.Specs.csproj — 167 .cs files, 4889 LoC (3271 significant)

D18 · Solution Shape · Infrastructure (Production) · ×1

Infrastructure (Production) Source/Infrastructure/Infrastructure.csproj — 57 .cs files, 4976 LoC (2960 significant)

D18 · Solution Shape · Aspire (Production) · ×1

Aspire (Production) Source/Clients/Aspire/Aspire.csproj — 7 .cs files, 396 LoC (147 significant)

D18 · Solution Shape · AspNetCore.Specs (Production) · ×1

AspNetCore.Specs (Production) Source/Clients/AspNetCore.Specs/AspNetCore.Specs.csproj — 20 .cs files, 596 LoC (416 significant)

D18 · Solution Shape · AspNetCore (Production) · ×1

AspNetCore (Production) Source/Clients/AspNetCore/AspNetCore.csproj — 20 .cs files, 864 LoC (487 significant)

D18 · Solution Shape · Connections (Production) · ×1

Connections (Production) Source/Clients/Connections/Connections.csproj — 40 .cs files, 2680 LoC (1661 significant)

D18 · Solution Shape · DotNET.CodeAnalysis.Specs (Test) · ×1

DotNET.CodeAnalysis.Specs (Test) Source/Clients/DotNET.CodeAnalysis.Specs/DotNET.CodeAnalysis.Specs.csproj — 106 .cs files, 3431 LoC (2458 significant)

D18 · Solution Shape · DotNET.CodeAnalysis (Analyzer) · ×1

DotNET.CodeAnalysis (Analyzer) Source/Clients/DotNET.CodeAnalysis/DotNET.CodeAnalysis.csproj — 24 .cs files, 2589 LoC (1729 significant)

D18 · Solution Shape · DotNET.Specs (Production) · ×1

DotNET.Specs (Production) Source/Clients/DotNET.Specs/DotNET.Specs.csproj — 762 .cs files, 25213 LoC (17498 significant)

D18 · Solution Shape · DotNET (Test) · ×1

DotNET (Test) Source/Clients/DotNET/DotNET.csproj — 553 .cs files, 27946 LoC (13879 significant)

D18 · Solution Shape · Testing.Specs (Production) · ×1

Testing.Specs (Production) Source/Clients/Testing.Specs/Testing.Specs.csproj — 54 .cs files, 1295 LoC (729 significant)

D18 · Solution Shape · Testing (Test) · ×1

Testing (Test) Source/Clients/Testing/Testing.csproj — 53 .cs files, 5252 LoC (3066 significant)

D18 · Solution Shape · Workbench (Production) · ×1

Workbench (Production) Source/Clients/Workbench/Workbench.csproj — 9 .cs files, 394 LoC (222 significant)

D18 · Solution Shape · XUnit.Integration (Test) · ×1

XUnit.Integration (Test) Source/Clients/XUnit.Integration/XUnit.Integration.csproj — 31 .cs files, 3068 LoC (1594 significant)

D18 · Solution Shape · Concepts.Specs (Production) · ×1

Concepts.Specs (Production) Source/Kernel/Concepts.Specs/Concepts.Specs.csproj — 53 .cs files, 914 LoC (532 significant)

D18 · Solution Shape · Concepts (Production) · ×1

Concepts (Production) Source/Kernel/Concepts/Concepts.csproj — 238 .cs files, 7191 LoC (2285 significant)

D18 · Solution Shape · Contracts (Production) · ×1

Contracts (Production) Source/Kernel/Contracts/Contracts.csproj — 238 .cs files, 8783 LoC (3124 significant)

D18 · Solution Shape · Core.Specs (Production) · ×1

Core.Specs (Production) Source/Kernel/Core.Specs/Core.Specs.csproj — 726 .cs files, 28775 LoC (21176 significant)

D18 · Solution Shape · Core (Test) · ×1

Core (Test) Source/Kernel/Core/Core.csproj — 801 .cs files, 49428 LoC (29841 significant)

D18 · Solution Shape · Server (Production) · ×1

Server (Production) Source/Kernel/Server/Server.csproj — 22 .cs files, 2606 LoC (1777 significant)

D18 · Solution Shape · Storage.MongoDB.Specs (Production) · ×1

Storage.MongoDB.Specs (Production) Source/Kernel/Storage.MongoDB.Specs/Storage.MongoDB.Specs.csproj — 136 .cs files, 4496 LoC (3220 significant)

D18 · Solution Shape · Storage.MongoDB (Production) · ×1

Storage.MongoDB (Production) Source/Kernel/Storage.MongoDB/Storage.MongoDB.csproj — 187 .cs files, 11992 LoC (7388 significant)

D18 · Solution Shape · Storage.Specs (Production) · ×1

Storage.Specs (Production) Source/Kernel/Storage.Specs/Storage.Specs.csproj — 22 .cs files, 719 LoC (518 significant)

D18 · Solution Shape · Storage.Sql.Specs (Production) · ×1

Storage.Sql.Specs (Production) Source/Kernel/Storage.Sql.Specs/Storage.Sql.Specs.csproj — 21 .cs files, 1188 LoC (829 significant)

D18 · Solution Shape · Storage.Sql (Production) · ×1

Storage.Sql (Production) Source/Kernel/Storage.Sql/Storage.Sql.csproj — 179 .cs files, 14924 LoC (9312 significant)

D18 · Solution Shape · Storage.Vault.Specs (Production) · ×1

Storage.Vault.Specs (Production) Source/Kernel/Storage.Vault.Specs/Storage.Vault.Specs.csproj — 13 .cs files, 345 LoC (227 significant)

D18 · Solution Shape · Storage.Vault (Production) · ×1

Storage.Vault (Production) Source/Kernel/Storage.Vault/Storage.Vault.csproj — 5 .cs files, 290 LoC (201 significant)

D18 · Solution Shape · Storage (Production) · ×1

Storage (Production) Source/Kernel/Storage/Storage.csproj — 100 .cs files, 4896 LoC (1584 significant)

D18 · Solution Shape · AssemblyFixer (Production) · ×1

AssemblyFixer (Production) Source/Tools/AssemblyFixer/AssemblyFixer.csproj — 2 .cs files, 135 LoC (108 significant)

D18 · Solution Shape · GrpcClients (Production) · ×1

GrpcClients (Production) Source/Tools/GrpcClients/GrpcClients.csproj — 5 .cs files, 640 LoC (491 significant)

D18 · Solution Shape · GrpcCodeGenerator.Specs (Production) · ×1

GrpcCodeGenerator.Specs (Production) Source/Tools/GrpcCodeGenerator.Specs/GrpcCodeGenerator.Specs.csproj — 14 .cs files, 483 LoC (279 significant)

D18 · Solution Shape · GrpcCodeGenerator (Production) · ×1

GrpcCodeGenerator (Production) Source/Tools/GrpcCodeGenerator/GrpcCodeGenerator.csproj — 12 .cs files, 1233 LoC (857 significant)

D18 · Solution Shape · InternalsVerifier (Production) · ×1

InternalsVerifier (Production) Source/Tools/InternalsVerifier/InternalsVerifier.csproj — 3 .cs files, 162 LoC (114 significant)

D18 · Solution Shape · ResourceEmbedder (Production) · ×1

ResourceEmbedder (Production) Source/Tools/ResourceEmbedder/ResourceEmbedder.csproj — 2 .cs files, 60 LoC (44 significant)

D18 · Solution Shape · Storage.AzureKeyVault (Production) · ×1

Storage.AzureKeyVault (Production) Source/Kernel/Storage.AzureKeyVault/Storage.AzureKeyVault.csproj — 5 .cs files, 312 LoC (211 significant)

D9 · Test Distribution · Unit tests · ×1

Unit tests — 5213 unit test method(s).

D9 · Test Distribution · Integration tests · ×1

Integration tests — 388 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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source .	4	artifacts/raw/gitleaks-history.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config auto --json --quiet --timeout 0 --metrics off .	0	—
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list Chronicle.slnx package --vulnerable --include-transitive --format json	0	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	13	artifacts/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 Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ .	20	artifacts/raw/trivy-fs.json
D37 · Vulnerability-disclosure Policy	disclosure	—	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 Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive .	33	artifacts/raw/osv-scanner.json

Run 019ee425-56d1-76ac-8bcc-e95910f2148a · 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 — 6 field(s) across 1 category, 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.

Email — 6 field(s)

AddUser.Email Source/Clients/Api/Security/AddUser.cs:19
User.Email Source/Clients/Api/Security/User.cs:23
AddUser.Email Source/Kernel/Contracts/Security/AddUser.cs:28
User.Email Source/Kernel/Contracts/Security/User.cs:28
UserEntity.Email Source/Kernel/Storage.Sql/Cluster/Security/UserEntity.cs:27
User.Email Source/Kernel/Storage/Security/User.cs:26

Executive summary

Top priorities

Diagnosis — what's actually going on

Trajectory

Architecture — bounded-context dependency graph

At a glance — Code Health · 38% · Weak · gated by D17, R7

At a glance — Architecture · 83% · Strong

At a glance — Maturity · 65% · Adequate

At a glance — Readiness · 30% · Weak · gated by D13, R4, R8, P7

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

At a glance — Accessibility · 45% · Weak · gated by AC4

At a glance — Performance · 47% · Weak · gated by PF3

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Appendix C — Personal-data map

Downloadable artifacts