Totem — 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.

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

It is strongest in Architecture (97%) — the structure is clean and changes stay contained.

Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.

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

Leadership focus, highest impact first: Protect endpoints by default-deny (Access Controls); Review each MD5/SHA1 use by what it protects (Web-Security Posture); 10 High CVE finding(s) in Dependency Vulnerabilities (Dependency Vulnerabilities).

For scale: Small (~13,624 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.

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

Code Health 70% Strong Architecture 97% ★ Exemplary Maturity 50% Adequate · gated by D34, M2 Readiness 37% Weak · gated by D12, P3 Security 27% Weak · gated by D30, C2, S1 Performance 60% Adequate

How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.

Security 27% · 46% weightReadiness 37% · 25% weightMaturity 50% · 14% weightPerformance 60% · 8% weightCode Health 70% · 4% weightArchitecture 97% · 2% weight

Raise Security 27 → 70 (the Healthy floor) ⇒ headline 39 → ~49.

Code composition — where the lines go

Business logic 15%Plumbing 73%Tests 11%

New since the last scan (10+)

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

D19 · Low XML-doc coverage: Totem src/Totem/Totem.csproj
D19 · Low XML-doc coverage: Totem.Runtime src/Totem.Runtime/Totem.Runtime.csproj
D19 · Low XML-doc coverage: Totem.Timeline src/Totem.Timeline/Totem.Timeline.csproj
D19 · Low XML-doc coverage: Totem.Timeline.EventStore src/Totem.Timeline.EventStore/Totem.Timeline.EventStore.csproj
D19 · Low XML-doc coverage: Totem.Timeline.Mvc src/Totem.Timeline.Mvc/Totem.Timeline.Mvc.csproj
D19 · Low XML-doc coverage: Totem.Timeline.SignalR src/Totem.Timeline.SignalR/Totem.Timeline.SignalR.csproj
D19 · Low XML-doc coverage: Totem.App.Service src/Totem.App.Service/Totem.App.Service.csproj
D19 · Low XML-doc coverage: Totem.App.Web src/Totem.App.Web/Totem.App.Web.csproj
D30 · High CVE: Microsoft.AspNetCore.Server.Kestrel.Core 2.1.1
D30 · High CVE: Microsoft.AspNetCore.Server.Kestrel.Core 2.1.1

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 — €4,200–€21,000

Cost to rebuild	€4,200–€21,000 (0.1 person-years (71–220 h), ~1 engineer)
Domain complexity	Standard — harder problems cost more per line
Quality factor	0.7× (at 39% quality) — the last 20% of quality is most of the work
Size & shape	Small · 39% boilerplate · 44% straight-line · 17% branching logic

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

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — service/app × 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.

Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.

+11.7 pts · Medium effort · Access Controls

Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.

+11.6 pts · Medium effort · Web-Security Posture

Resolve the 2 Vulnerable finding(s) in Dependency Hygiene.

+4.3 pts · Low effort · Dependency Hygiene

Diagnosis — what's actually going on

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

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

Evidence: valuation: Small, ~0.1 person-years rebuild (13,624 LoC) · weakest lens: Security 27%

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

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. The rest can wait behind it.

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

→ Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.

Architecture — module dependency graph

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

Architecture — module dependency matrix

25 modules, 64 dependencies — 2 dependency cycles, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

At a glance — Code Health · 70% · Strong

The Good

D1 · .NET / C# Cyclomatic Complexity 10.0 D2 · .NET / C# Cognitive Complexity 9.6 D3 · .NET / C# God Classes 8.4 D4 · .NET / C# Code Duplication 10.0 D18 · .NET / C# Solution Shape 10.0 D39 · .NET / C# IL Efficiency 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 9.0 X1 · Repo Async correctness 7.2 X3 · Repo Exception handling 10.0 X4 · Repo Structured logging 10.0

The Bad

D17 · .NET / C# Explicit Debt 6.8

The Ugly

X2 · Repo Cancellation propagation 4.2

At a glance — Architecture · 97% · Exemplary

The Good

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

At a glance — Maturity · 50% · Adequate · gated by D34, M2

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 8.0 D21 · .NET / C# Naming Consistency 10.0 D24 · .NET / C# Comment Value 9.0 M1 · Repo Documentation (README) 7.3 M3 · Repo Folder & project structure 10.0

The Bad

M4 · Repo Documentation accuracy 6.0

The Ugly

D34 · .NET / C# Knowledge Freshness 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 37% · Weak · gated by D12, P3

The Good

D9 · .NET / C# Test Distribution 8.5 D10 · .NET / C# Test Quality 10.0 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 8.5

The Bad

P10 · Repo Library API & versioning 6.0 P2 · Repo Observability 5.5 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0

The Ugly

D12 · .NET / C# Dependency Hygiene 2.7 P3 · Repo Security & performance tooling 0.0

At a glance — Security · 27% · Weak · gated by D30, C2, S1

The Good

D28 · .NET / C# Secrets (history) 10.0 D29 · .NET / C# Static Analysis (SAST) 10.0

The Ugly

D30 · .NET / C# Dependency Vulnerabilities 0.7 C2 · Repo Access Controls 0.0 S1 · Repo Web-Security Posture 3.0

At a glance — Performance · 60% · Adequate

The Bad

PF1 · Repo Benchmark discipline 6.0 PF2 · Repo Allocation hygiene 6.0 PF3 · Repo Async & latency hygiene 6.1

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	15	High / Critical

Roadmap

First, enforce default-deny access controls by implementing role-based authorization or imperative guards in every handler. Next, strengthen the web-security posture by replacing weak MD5/SHA1 hashes with SHA-256 or non-cryptographic alternatives, while also resolving ten high-severity dependency vulnerabilities. Then, address eighteen deprecated dependencies to improve hygiene. Finally, implement readiness probes and a rolling-update strategy to ensure automatic detection and rollback of bad releases.

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

Do this	Helps	Effort	Dimension
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.	+11.7 pts	Medium	Access Controls
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.	+11.6 pts	Medium	Web-Security Posture
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene.	+4.3 pts	Low	Dependency Hygiene
Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities.	+7.5 pts	Medium	Dependency Vulnerabilities
Resolve the 18 Deprecated finding(s) in Dependency Hygiene.	+6.6 pts	Medium	Dependency Hygiene
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.	+6.2 pts	Medium	Deployment & Rollback
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.	+6.2 pts	Medium	Release Hygiene
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities.	+3.1 pts	Low	Dependency Vulnerabilities

File quality

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

File	Score	Band	Worst signal
src/Totem/Totem.csproj	4.9	Mixed	Explicit Debt: NoWarnInCsproj
src/Totem.Timeline/Totem.Timeline.csproj	4.9	Mixed	Explicit Debt: NoWarnInCsproj
src/Totem.Timeline.SignalR/Totem.Timeline.SignalR.csproj	4.9	Mixed	Explicit Debt: NoWarnInCsproj
src/Totem.Timeline.Mvc/Totem.Timeline.Mvc.csproj	4.9	Mixed	Explicit Debt: NoWarnInCsproj
src/Totem.Timeline.EventStore/Totem.Timeline.EventStore.csproj	4.9	Mixed	Explicit Debt: NoWarnInCsproj
src/Totem.Runtime/Totem.Runtime.csproj	4.9	Mixed	Explicit Debt: NoWarnInCsproj
src/Totem.App.Web/Totem.App.Web.csproj	4.9	Mixed	Explicit Debt: NoWarnInCsproj
src/Totem.App.Service/Totem.App.Service.csproj	4.9	Mixed	Explicit Debt: NoWarnInCsproj
src/Totem.App.Tests/Totem.App.Tests.csproj	6.4	Mixed	Explicit Debt: NoWarnInCsproj
tests/Totem.Timeline.IntegrationTests/MultipleWhenEvents.cs	6.5	Mixed	Explicit Debt: Dead code: TopicA
tests/Totem.Timeline.IntegrationTests/RoutingToLatentInstance.cs	6.5	Mixed	Explicit Debt: Dead code: TestTopic
tests/Totem.Timeline.IntegrationTests/ScheduledEvents.cs	6.6	Mixed	Explicit Debt: Dead code: TestTopic
tests/Totem.Timeline.IntegrationTests/Cause.cs	6.9	Mixed	Explicit Debt: Dead code: TestTopic
tests/Totem.Timeline.IntegrationTests/GivenWhenOrder.cs	6.9	Mixed	Explicit Debt: Dead code: TestTopic
tests/Totem.Timeline.IntegrationTests/RoutingToMultiInstance.cs	6.9	Mixed	Explicit Debt: Dead code: TestTopic
tests/Totem.Timeline.IntegrationTests/Queries.cs	7.3	Mixed	Explicit Debt: Dead code: Given
src/Totem/Text.cs	7.8	Mixed	God Classes: TooManyMethods: Text
src/Totem/Reflection/TypeResolver.cs	8.2	Near-clean	Explicit Debt: BarePragmaDisable
src/Totem/IO/HttpHost.cs	8.5	Near-clean	Cognitive Complexity: HttpHost.TryFrom (cognitive 21)
src/Totem.App.Web/ConfigureWebApp.cs	8.5	Near-clean	God Classes: TooManyMethods: ConfigureWebApp

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. 51 of 54 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — 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 — 54 dimensions across the health lenses

D1D2D3D4D5D6D9D10D12D13D14D15D17D18D19D21D24D26D27D28D29D30D34D35D39AX1AX10AX2AX3AX4AX5AX6AX8C2GD1IC1M1M2M3M4P1P10P2P3P4P6PF1PF2PF3S1X1X2X3X4

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, 62 of 133 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.302	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.302	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 019fc840-0c86-71b7-b11d-56775ceb205d.

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

A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.

When something does degrade — a missing scanner, a shallow clone, an LLM hiccup — it is named here explicitly and its exact cause recorded in diagnostics.md, never absorbed silently into the score.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
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.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (4): D19, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

Do you agree with this assessment?

D2 · Cognitive Complexity9.6 / 10Exemplary✓ Tool-verified

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

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

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

1 method(s) exceeded the cognitive complexity threshold of 15; the worst was HttpHost.TryFrom at 21.

HttpHost.TryFrom (cognitive 21)src/Totem/IO/HttpHost.cs:89

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

6 god class(es) detected.

TooManyMethods: Text · ×6src/Totem/Text.cs:0

What to do

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

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

Do you agree with this assessment?

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

0 duplicated block group(s) detected.

✓ On the Gold path — maintain.

Detailed fixes: d4_recommendation.md.

Do you agree with this assessment?

D5 · Coupling9.2 / 10Exemplary✓ Tool-verified

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

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

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

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

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

Off the main sequence: Totem

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

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

1 of 53 classes have LCOM4 above 3.

Low cohesion: FlowContext (LCOM4 4)src/Totem.Timeline/Runtime/FlowContext.cs:11

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D9 · Test Distribution8.5 / 10Strong✓ 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 8.5 / 10 · rule-coverage 100% · ceiling Documented

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

What to do

Improve Test Distribution — currently 8.5/10. — 8 test methods: 0 unit, 8 integration, 0 BDD, 0 e2e.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

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

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

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

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

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8 tests.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene2.7 / 10Weak✓ 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 2.7 / 10 · rule-coverage 100% · ceiling Verified

29 outdated, 2 vulnerable, 18 deprecated packages.

Vulnerable: Newtonsoft.Json · ×2

Deprecated: Microsoft.Extensions.Configuration.Binder · ×18

Outdated: Microsoft.Extensions.Configuration.Binder · ×29

What to do

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

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

Do you agree with this assessment?

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

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

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

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

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

0 of 30 packages use a banned license.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

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

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

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

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

19 deducted debt markers + 25 dead symbols across 13624 LoC (1.6/KLoC) → score 6.8.

NoWarnInCsproj · ×18src/Totem/Totem.csproj:22

Dead code: TestTopic · ×25tests/Totem.Timeline.IntegrationTests/Cause.cs:25

BarePragmaDisablesrc/Totem/Reflection/TypeResolver.cs:60

What to do

Resolve the 18 NoWarnInCsproj finding(s) in Explicit Debt — start with Totem.csproj (2), Totem.Timeline.csproj (2), Totem.Timeline.SignalR.csproj (2). — One of this dimension's main actionable groups (18 issue-level).
Resolve the 25 Dead code finding(s) in Explicit Debt — start with MultipleWhenEvents.cs (5), RoutingToLatentInstance.cs (5), ScheduledEvents.cs (4). — One of this dimension's main actionable groups (25 warning-level).
Resolve the 1 BarePragmaDisable finding(s) in Explicit Debt — start with TypeResolver.cs. — One of this dimension's main actionable groups (1 warning-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

10 projects, 261 source files, 15386 hand-written lines of code (13624 production / 1762 test), 30 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

Do you agree with this assessment?

D19 · Documentation Quality / 10Strong◐ Sampled · advisory

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

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

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

Totem's README is a strong narrative document that explains the framework conceptually and its purpose (facing the spatial metaphor of modern systems) before diving into concrete structure. It covers Purpose, Goals, License, Packages, Getting Started, Concepts, and outlines Testing/Dependencies/Background further in the body, matching the visible content. The visible sections are well connected: Introduction frames knowledge work as the motivation; Purpose states what Totem does (software that feels like storytelling); Goals lists repeatable solutions and batteries included; and the outline is present under clip markers, so completeness of Concepts, Event/Command/Query/Topic/Scheduling, Interacting with the world, App, Reading queries, Issuing commands, Testing, Dependencies, Background, Further Reading is not flagged as missing. The visible content reads smoothly and gives a strong conceptual foundation.

Low XML-doc coverage: Totem · ×8src/Totem/Totem.csproj

What to do

Resolve the 8 Low XML-doc coverage finding(s) in Documentation Quality — start with Totem.csproj, Totem.Runtime.csproj, Totem.Timeline.csproj. — One of this dimension's main actionable groups (8 warning-level).

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

Do you agree with this assessment?

D21 · Naming Consistency / 10Exemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D24 · Comment Value / 10Exemplary◐ Sampled · advisory

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

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

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

32 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

Do you agree with this assessment?

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

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

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

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

0 of 10 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D27 · Navigability9.6 / 10Exemplary✓ 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 9.6 / 10 · rule-coverage 100% · ceiling Documented

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

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)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 across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

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

Maturity: Documented → Verified → Prevented · effective 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 Vulnerabilities0.7 / 10Critical✓ Tool-verified

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

15 vulnerable package(s): 2 critical, 10 high, 3 medium, 0 low.

High CVE: Newtonsoft.Json 12.0.1 · ×10detected by dotnet list package --vulnerable

Critical CVE: System.Text.Encodings.Web 4.5.0 · ×2detected by dotnet list package --vulnerable

Medium CVE: System.Security.Cryptography.Xml 4.5.0 · ×3detected by dotnet list package --vulnerable

What to do

Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (10 issue-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (3 warning-level).

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

Do you agree with this assessment?

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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

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

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

62 of 62 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Totem/TextExtensions.cs.

Largest orphaned file · ×2src/Totem/TextExtensions.cs

Dormant codebase

What to do

Resolve the 2 Largest orphaned file finding(s) in Knowledge Freshness — start with TextExtensions.cs, Expectable.cs. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

D39 · IL Efficiency10.0 / 10Exemplary✓ Tool-verified

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

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

0 of 2271 first-party methods have an oversized IL body.

✓ On the Gold path — maintain.

Detailed fixes: d39_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

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

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

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

Do you agree with this assessment?

AX10 · Code composition9.0 / 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 segregation10.0 / 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.

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?

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

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

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

No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.

What to do

Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

IC1 · Incompleteness & stubs9.0 / 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.

`IsEnabled` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — Notion.cs:58

What to do

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

Do you agree with this assessment?

M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

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

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

What to do

Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 10 of 10 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

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

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

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

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

What to do

Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

M4 · Documentation accuracy6.0 / 10Adequate◐ Sampled · advisory

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

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

README advertises a RAG / ML engine, but no ML/RAG code or dependency exists
README advertises a microservices architecture, but the repo is a single project with no service manifests

What to do

Reconcile the README with reality: README advertises a RAG / ML engine, but no ML/RAG code or dependency exists; README advertises a microservices architecture, but the repo is a single project with no service manifests.

Do you agree with this assessment?

P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified

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

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

A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Check the coverage dimensions first: if this repo has no test suite yet, that is the finding and this row follows from it. If a suite does exist, make the runner step explicit so the gate is unambiguous.

What to do

Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.

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.

262/301 types (87%) 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 · Observability5.5 / 10Adequate✓ Tool-verified

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

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

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

What to do

Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.

Do you agree with this assessment?

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

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

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

No static application security testing detected. For this repository's stack, add CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step.

What to do

Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

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

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

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

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.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.

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?

PF1 · Benchmark discipline6.0 / 10Adequate✓ Tool-verified

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

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

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

What to do

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

Do you agree with this assessment?

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

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

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

No Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask or buffer-writer usage was found. If this library sits on a hot path, these reduce the GC pressure it puts on its host — a bonus, not a requirement.

What to do

On hot paths, prefer Span<T>/ReadOnlySpan<T>, ArrayPool<T>, stackalloc and ValueTask to cut allocations a consumer would otherwise inherit.

Do you agree with this assessment?

PF3 · Async & latency hygiene6.1 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code keeps its host responsive — a library awaits with ConfigureAwait(false) (so it never captures and stalls the host's context) and avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock.

Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a library with ≥5 awaits — the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

Only 2/115 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

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?

S1 · Web-Security Posture3.0 / 10Weak✓ 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.

MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — Sha1.cs:124
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.)
No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)

What to do

Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
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.
Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.

Do you agree with this assessment?

X1 · Async correctness7.2 / 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.

`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — Monitor.cs:42

What to do

async void method: StartMonitoring

Do you agree with this assessment?

X2 · Cancellation propagation4.2 / 10Weak✓ 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 2/64 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×25) — Connection.cs:41, Connection.cs:87, Connection.cs:128, …

What to do

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

Do you agree with this assessment?

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

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

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

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?

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	70%	Strong	Solid.
Architecture	97%	Exemplary	Strongest area.
Maturity	50%	Adequate — gated by D34, M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	37%	Weak — gated by D12, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	27%	Weak — gated by D30, C2, S1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	60%	Adequate	Acceptable, with room to improve.

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

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

AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D11 Test Reliability — Test runner surfaced no tests
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this check looks for
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this check looks for (a message-bus package)
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this check looks for (an event-store package (Marten/EventStore))
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P7 Outbound HTTP resilience — no outbound HTTP usage detected
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X5 Nullable reference types — no NRT-eligible projects
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.

Appendix A — Findings (grouped)

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

Issue — 32 finding(s)

D17 · Explicit Debt · NoWarnInCsproj · ×18

NoWarnInCsproj src/Totem/Totem.csproj:22 — 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.Timeline/Totem.Timeline.csproj:22 — 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.Timeline.SignalR/Totem.Timeline.SignalR.csproj:22 — 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.Timeline.Mvc/Totem.Timeline.Mvc.csproj:22 — 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.Timeline.EventStore/Totem.Timeline.EventStore.csproj:22 — 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.Runtime/Totem.Runtime.csproj:22 — 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.App.Web/Totem.App.Web.csproj:22 — 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.App.Tests/Totem.App.Tests.csproj:22 — 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.App.Service/Totem.App.Service.csproj:22 — 1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem/Totem.csproj:22 — NU5105 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.Timeline/Totem.Timeline.csproj:22 — NU5105 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.Timeline.SignalR/Totem.Timeline.SignalR.csproj:22 — NU5105 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.Timeline.Mvc/Totem.Timeline.Mvc.csproj:22 — NU5105 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.Timeline.EventStore/Totem.Timeline.EventStore.csproj:22 — NU5105 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.Runtime/Totem.Runtime.csproj:22 — NU5105 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.App.Web/Totem.App.Web.csproj:22 — NU5105 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.App.Tests/Totem.App.Tests.csproj:22 — NU5105 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Totem.App.Service/Totem.App.Service.csproj:22 — NU5105 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.

D30 · Dependency Vulnerabilities · High CVE · ×10

High CVE: Newtonsoft.Json 12.0.1 — Newtonsoft.Json 12.0.1 (direct) has a High advisory; affects 9 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Text.RegularExpressions 4.3.0 — System.Text.RegularExpressions 4.3.0 (transitive) has a High advisory; affects 6 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.Http 2.1.1 — Microsoft.AspNetCore.Http 2.1.1 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.WebSockets 2.2.0 — Microsoft.AspNetCore.WebSockets 2.2.0 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: System.Net.WebSockets.WebSocketProtocol 4.5.1 — System.Net.WebSockets.WebSocketProtocol 4.5.1 (transitive) has a High advisory; affects 2 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.NETCore.App 2.2.0 — Microsoft.NETCore.App 2.2.0 (direct) has a High advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.NETCore.App 2.2.0 — Microsoft.NETCore.App 2.2.0 (direct) has a High advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.Server.Kestrel.Core 2.1.1 — Microsoft.AspNetCore.Server.Kestrel.Core 2.1.1 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.Server.Kestrel.Core 2.1.1 — Microsoft.AspNetCore.Server.Kestrel.Core 2.1.1 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1.1 — Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets 2.1.1 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]

D12 · Dependency Hygiene · Vulnerable · ×2

Vulnerable: Newtonsoft.Json — Newtonsoft.Json 12.0.1 — High severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: Microsoft.NETCore.App — Microsoft.NETCore.App [2.2.0, — ) severity. 2.2.0

D30 · Dependency Vulnerabilities · Critical CVE · ×2

Critical CVE: System.Text.Encodings.Web 4.5.0 — System.Text.Encodings.Web 4.5.0 (transitive) has a Critical advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Critical CVE: Microsoft.AspNetCore.Server.Kestrel.Core 2.1.1 — Microsoft.AspNetCore.Server.Kestrel.Core 2.1.1 (transitive) has a Critical advisory. https://github.com/advisories/[GHSA redacted]

Warning — 66 finding(s)

D17 · Explicit Debt · Dead code · ×25

Dead code: TestTopic tests/Totem.Timeline.IntegrationTests/Cause.cs:25 — NamedType TestTopic — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/Cause.cs:27 — Method When — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/Cause.cs:30 — Method When — no references found in solution.
Dead code: TestTopic tests/Totem.Timeline.IntegrationTests/GivenWhenOrder.cs:27 — NamedType TestTopic — no references found in solution.
Dead code: Given tests/Totem.Timeline.IntegrationTests/GivenWhenOrder.cs:31 — Method Given — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/GivenWhenOrder.cs:34 — Method When — no references found in solution.
Dead code: TopicA tests/Totem.Timeline.IntegrationTests/MultipleWhenEvents.cs:23 — NamedType TopicA — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/MultipleWhenEvents.cs:25 — Method When — no references found in solution.
Dead code: TopicB tests/Totem.Timeline.IntegrationTests/MultipleWhenEvents.cs:35 — NamedType TopicB — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/MultipleWhenEvents.cs:37 — Method When — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/MultipleWhenEvents.cs:40 — Method When — no references found in solution.
Dead code: Given tests/Totem.Timeline.IntegrationTests/Queries.cs:39 — Method Given — no references found in solution.
Dead code: Given tests/Totem.Timeline.IntegrationTests/Queries.cs:40 — Method Given — no references found in solution.
Dead code: TestTopic tests/Totem.Timeline.IntegrationTests/RoutingToLatentInstance.cs:27 — NamedType TestTopic — no references found in solution.
Dead code: Route tests/Totem.Timeline.IntegrationTests/RoutingToLatentInstance.cs:29 — Method Route — no references found in solution.
Dead code: RouteFirst tests/Totem.Timeline.IntegrationTests/RoutingToLatentInstance.cs:30 — Method RouteFirst — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/RoutingToLatentInstance.cs:32 — Method When — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/RoutingToLatentInstance.cs:35 — Method When — no references found in solution.
Dead code: TestTopic tests/Totem.Timeline.IntegrationTests/RoutingToMultiInstance.cs:32 — NamedType TestTopic — no references found in solution.
Dead code: RouteFirst tests/Totem.Timeline.IntegrationTests/RoutingToMultiInstance.cs:34 — Method RouteFirst — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/RoutingToMultiInstance.cs:36 — Method When — no references found in solution.
Dead code: TestTopic tests/Totem.Timeline.IntegrationTests/ScheduledEvents.cs:26 — NamedType TestTopic — no references found in solution.
Dead code: GivenScheduled tests/Totem.Timeline.IntegrationTests/ScheduledEvents.cs:30 — Method GivenScheduled — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/ScheduledEvents.cs:33 — Method When — no references found in solution.
Dead code: When tests/Totem.Timeline.IntegrationTests/ScheduledEvents.cs:36 — Method When — no references found in solution.

D12 · Dependency Hygiene · Deprecated · ×18

Deprecated: Microsoft.Extensions.Configuration.Binder — Microsoft.Extensions.Configuration.Binder 2.2.0 — Other,Legacy
Deprecated: Microsoft.Extensions.DependencyInjection.Abstractions — Microsoft.Extensions.DependencyInjection.Abstractions 2.2.0 — Other,Legacy
Deprecated: Microsoft.Extensions.Hosting.Abstractions — Microsoft.Extensions.Hosting.Abstractions 2.2.0 — Other,Legacy
Deprecated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 2.2.0 — Other,Legacy
Deprecated: Microsoft.Extensions.Options — Microsoft.Extensions.Options 2.2.0 — Other,Legacy
Deprecated: EventStore.ClientAPI.NetCore — EventStore.ClientAPI.NetCore 4.1.0.23 — Other,Legacy — the publisher's replacement is `EventStore.Client`; migrate the reference to it.
Deprecated: Microsoft.Extensions.Configuration — Microsoft.Extensions.Configuration 2.2.0 — Other,Legacy
Deprecated: Microsoft.AspNetCore.SignalR — Microsoft.AspNetCore.SignalR 1.1.0 — Other,Legacy
Deprecated: Microsoft.AspNetCore.SignalR.Core — Microsoft.AspNetCore.SignalR.Core 1.1.0 — Other,Legacy
Deprecated: Microsoft.Extensions.Configuration.CommandLine — Microsoft.Extensions.Configuration.CommandLine 2.2.0 — Other,Legacy
Deprecated: Microsoft.Extensions.Configuration.EnvironmentVariables — Microsoft.Extensions.Configuration.EnvironmentVariables 2.2.0 — Other,Legacy
Deprecated: Microsoft.Extensions.Configuration.Json — Microsoft.Extensions.Configuration.Json 2.2.0 — Other,Legacy
Deprecated: Microsoft.Extensions.Configuration.UserSecrets — Microsoft.Extensions.Configuration.UserSecrets 2.2.0 — Other,Legacy
Deprecated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 2.2.0 — Other,Legacy
Deprecated: Microsoft.NETCore.App — Microsoft.NETCore.App [2.2.0, — ) — the publisher's replacement is `2.2.0` Other,Legacy; migrate the reference to it.
Deprecated: Microsoft.AspNetCore.Hosting.Abstractions — Microsoft.AspNetCore.Hosting.Abstractions 2.2.0 — Other,Legacy
Deprecated: xunit — xunit 2.4.1 — Legacy — the publisher's replacement is `xunit.v3`; migrate the reference to it.
Deprecated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 2.2.0 — Other,Legacy

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

Low XML-doc coverage: Totem src/Totem/Totem.csproj — Totem: 5 % XML-doc coverage (59/1166).
Low XML-doc coverage: Totem.Runtime src/Totem.Runtime/Totem.Runtime.csproj — Totem.Runtime: 15 % XML-doc coverage (48/323).
Low XML-doc coverage: Totem.Timeline src/Totem.Timeline/Totem.Timeline.csproj — Totem.Timeline: 19 % XML-doc coverage (80/424).
Low XML-doc coverage: Totem.Timeline.EventStore src/Totem.Timeline.EventStore/Totem.Timeline.EventStore.csproj — Totem.Timeline.EventStore: 16 % XML-doc coverage (18/114).
Low XML-doc coverage: Totem.Timeline.Mvc src/Totem.Timeline.Mvc/Totem.Timeline.Mvc.csproj — Totem.Timeline.Mvc: 24 % XML-doc coverage (11/45).
Low XML-doc coverage: Totem.Timeline.SignalR src/Totem.Timeline.SignalR/Totem.Timeline.SignalR.csproj — Totem.Timeline.SignalR: 29 % XML-doc coverage (4/14).
Low XML-doc coverage: Totem.App.Service src/Totem.App.Service/Totem.App.Service.csproj — Totem.App.Service: 5 % XML-doc coverage (4/79).
Low XML-doc coverage: Totem.App.Web src/Totem.App.Web/Totem.App.Web.csproj — Totem.App.Web: 2 % XML-doc coverage (3/123).

D3 · God Classes · TooManyMethods · ×6

TooManyMethods: Text src/Totem/Text.cs:0 — TooManyMethods — 241 significant lines (blank, comment-only and punctuation-only lines excluded), 76 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ConfigureWebApp src/Totem.App.Web/ConfigureWebApp.cs:0 — TooManyMethods — 181 significant lines (blank, comment-only and punctuation-only lines excluded), 61 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Configure src/Totem.App.Web/Configure.cs:0 — TooManyMethods — 111 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Writer src/Totem/Text.cs:0 — TooManyMethods — 55 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ConfigureServiceApp src/Totem.App.Service/ConfigureServiceApp.cs:0 — TooManyMethods — 117 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Configure src/Totem.App.Service/Configure.cs:0 — TooManyMethods — 63 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.

D30 · Dependency Vulnerabilities · Medium CVE · ×3

Medium CVE: System.Security.Cryptography.Xml 4.5.0 — System.Security.Cryptography.Xml 4.5.0 (transitive) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.NETCore.App 2.2.0 — Microsoft.NETCore.App 2.2.0 (direct) has a Medium advisory; affects 3 projects — one upgrade fixes all. https://github.com/advisories/[GHSA redacted]
Medium CVE: Microsoft.AspNetCore.Server.Kestrel.Core 2.1.1 — Microsoft.AspNetCore.Server.Kestrel.Core 2.1.1 (transitive) has a Medium advisory. https://github.com/advisories/[GHSA redacted]

D16 · Bus Factor · dormant codebase · ×1

dormant codebase — no living knowledge left to concentrate — All 2 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).

D17 · Explicit Debt · BarePragmaDisable · ×1

BarePragmaDisable src/Totem/Reflection/TypeResolver.cs:60 — #pragma warning disable 618, 612 — the disable has no matching restore, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later. Close it with the matching restore directive immediately after the construct it covers, or fix the cause and drop the directive entirely.

D2 · Cognitive Complexity · HttpHost.TryFrom (cognitive 21) · ×1

HttpHost.TryFrom (cognitive 21) src/Totem/IO/HttpHost.cs:89 — HttpHost.TryFrom has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: Totem — Totem: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.

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

Low cohesion: FlowContext (LCOM4 4) src/Totem.Timeline/Runtime/FlowContext.cs:11 — FlowContext'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.

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — analyzer environment — Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, no coverage collector was found in your CI either, so there is no existing report to hand us — add a collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and real coverage will be read.

Recommendation — 5 finding(s)

D34 · Knowledge Freshness · Largest orphaned file · ×2

Largest orphaned file src/Totem/TextExtensions.cs — One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file src/Totem/Expectable.cs — One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.

D11 · Test Reliability · Test runner surfaced no tests · ×1

Test runner surfaced no tests — Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 8 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.

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

Bounded contexts not declared — At 13624 LoC spread over 10 projects the codebase is large and multi-module, so explicit bounded contexts are needed. Name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.

D34 · Knowledge Freshness · Dormant codebase · ×1

Dormant codebase — 62 of 62 significant files have no living knowledge — the codebase as a whole is dormant, not 62 separate risks. Re-engage owners or document before change.

Info — 30 finding(s)

D12 · Dependency Hygiene · Outdated · ×29

Outdated: Microsoft.Extensions.Configuration.Binder — Microsoft.Extensions.Configuration.Binder 2.2.0 → 10.0.10 available (referenced by Totem.Runtime).
Outdated: Microsoft.Extensions.DependencyInjection.Abstractions — Microsoft.Extensions.DependencyInjection.Abstractions 2.2.0 → 10.0.10 available (referenced by Totem.Runtime).
Outdated: Microsoft.Extensions.Hosting.Abstractions — Microsoft.Extensions.Hosting.Abstractions 2.2.0 → 10.0.10 available (referenced by Totem.Runtime).
Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 2.2.0 → 10.0.10 available (referenced by Totem.Runtime).
Outdated: Microsoft.Extensions.Options — Microsoft.Extensions.Options 2.2.0 → 10.0.10 available (referenced by Totem.Runtime).
Outdated: Newtonsoft.Json — Newtonsoft.Json 12.0.1 → 13.0.4 available (referenced by Totem.Runtime).
Outdated: System.Reactive.Linq — System.Reactive.Linq 4.1.2 → 6.1.0 available (referenced by Totem.Timeline).
Outdated: System.Reactive.PlatformServices — System.Reactive.PlatformServices 4.1.2 → 6.1.0 available (referenced by Totem.Timeline).
Outdated: Microsoft.Extensions.Configuration — Microsoft.Extensions.Configuration 2.2.0 → 10.0.10 available (referenced by Totem.Timeline.EventStore).
Outdated: Microsoft.AspNetCore.Mvc — Microsoft.AspNetCore.Mvc 2.1.1 → 2.3.11 available (referenced by Totem.Timeline.Mvc).
Outdated: Microsoft.AspNetCore.Mvc.Core — Microsoft.AspNetCore.Mvc.Core 2.1.1 → 2.3.11 available (referenced by Totem.Timeline.Mvc).
Outdated: Microsoft.AspNetCore.SignalR — Microsoft.AspNetCore.SignalR 1.1.0 → 1.2.11 available (referenced by Totem.Timeline.SignalR).
Outdated: Microsoft.AspNetCore.SignalR.Core — Microsoft.AspNetCore.SignalR.Core 1.1.0 → 1.2.11 available (referenced by Totem.Timeline.SignalR).
Outdated: Microsoft.Extensions.Configuration.CommandLine — Microsoft.Extensions.Configuration.CommandLine 2.2.0 → 10.0.10 available (referenced by Totem.App.Service).
Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables — Microsoft.Extensions.Configuration.EnvironmentVariables 2.2.0 → 10.0.10 available (referenced by Totem.App.Service).
Outdated: Microsoft.Extensions.Configuration.Json — Microsoft.Extensions.Configuration.Json 2.2.0 → 10.0.10 available (referenced by Totem.App.Service).
Outdated: Microsoft.Extensions.Configuration.UserSecrets — Microsoft.Extensions.Configuration.UserSecrets 2.2.0 → 10.0.10 available (referenced by Totem.App.Service).
Outdated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 2.2.0 → 10.0.10 available (referenced by Totem.App.Service).
Outdated: Serilog.Extensions.Hosting — Serilog.Extensions.Hosting 2.0.0 → 10.0.0 available (referenced by Totem.App.Service).
Outdated: Serilog.Settings.Configuration — Serilog.Settings.Configuration 3.0.1 → 10.0.1 available (referenced by Totem.App.Service).
Outdated: Serilog.Sinks.Console — Serilog.Sinks.Console 3.1.1 → 6.1.1 available (referenced by Totem.App.Service).
Outdated: Microsoft.AspNetCore — Microsoft.AspNetCore 2.1.1 → 2.3.11 available (referenced by Totem.App.Web).
Outdated: Microsoft.AspNetCore.Hosting — Microsoft.AspNetCore.Hosting 2.1.1 → 2.3.11 available (referenced by Totem.App.Web).
Outdated: Microsoft.AspNetCore.Hosting.Abstractions — Microsoft.AspNetCore.Hosting.Abstractions 2.2.0 → 2.3.11 available (referenced by Totem.App.Web).
Outdated: Microsoft.AspNetCore.StaticFiles — Microsoft.AspNetCore.StaticFiles 2.1.1 → 2.3.11 available (referenced by Totem.App.Web).
+ 4 more in this group — see findings.md.

D22 · Internal API Consistency · No exposed public API · ×1

No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.

Appendix B — Reproduction & audit trail

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

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 .	0	artifacts/raw/gitleaks-history.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --json --quiet --timeout 0 --metrics off .	0	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list Totem.sln package --vulnerable --include-transitive --format json	15	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.	0	—
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: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.	0	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D38 · OSV Dependency Vulnerabilities	osv-scanner	—	osv-scanner: not applicable — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—

Run 019fc840-0c86-71b7-b11d-56775ceb205d · 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 — 2 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.

Name — 2 field(s)

Field.FullName src/Totem.Runtime/Field.cs:25
TypeIndex._byFullName src/Totem/Reflection/TypeResolver.cs:38

Bwatts/Totem

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency graph

Architecture — module dependency matrix

At a glance — Code Health · 70% · Strong

At a glance — Architecture · 97% · Exemplary

At a glance — Maturity · 50% · Adequate · gated by D34, M2

At a glance — Readiness · 37% · Weak · gated by D12, P3

At a glance — Security · 27% · Weak · gated by D30, C2, S1

At a glance — Performance · 60% · Adequate

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

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Appendix C — Personal-data map

Downloadable artifacts