Public report — es4j, published 4 Aug 2026. Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version; ask the repo owner for the full report.
Watchdogby Canine Development 04-08-2026 @ 21:06 UTC Public
Code Health Audit

Eventsourcing/es4j

dormant codebase
58% Adequate
CriticalWeakAdequateStrongExemplary
middle
Architecture 99% Exemplary Security 89% Exemplary Code Health 83% Strong Readiness 50% Adequate Maturity 46% Adequate

Small · 14,811 LoC · rebuild ~0.2 person-years · weakest lens: Maturity (46%)

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

18/20dimensions tool-verifieddeterministic · confidence 1.0 · 2 LLM-assisted, advisory
50findings with an exact file:lineof 56 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
20/94dimensions across the health lenses14811 LoC — wide & deep

Executive summary

Read through the Preview lens: this repo is pre-1.0 / in development, so the colour bands are relaxed to what a preview needs — *green* means good enough for a preview, not yet production-stable. Code correctness and security stay near-strict even here; the score itself is absolute and comparable across repos.

eventsourcing/es4j is sound in substance but carries real gaps (58%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.

It is strongest in Architecture (99%) — the structure is clean and changes stay contained. Security (89%) is solid too.

The area that most needs attention is Maturity (46%) — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent. Readiness (50%) is the next concern — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade.

Leadership focus, highest impact first: Record significant decisions one document per decision (Architecture documentation); 3 Largest orphaned file finding(s) (Knowledge Freshness); SAST step to CI running what this repository's stack ships (Security & performance tooling).

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

Encouragingly, the gaps are in documentation and release process — not in the code's correctness, structure or security, which are strong. They're low-risk to close, and doing so would lift the grade without re-engineering anything that already works.

Code Health 83% Strong Architecture 99% ★ Exemplary Maturity 46% Adequate · gated by D34, M2 Readiness 50% Adequate · gated by P3 Security 89% ★ Exemplary
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.
Maturity 46% · 47% weightReadiness 50% · 26% weightCode Health 83% · 14% weightSecurity 89% · 8% weightArchitecture 99% · 4% weight

Raise Maturity 46 → 70 (the Healthy floor) ⇒ headline 58 → ~65.

Code composition — where the lines go
Tests 100%
Rebuild cost & value ~ Modeled — €8,500–€43,000
Cost to rebuild€8,500–€43,000 (0.1–0.3 person-years (142–452 h), ~1 engineer)
Domain complexityStandard — harder problems cost more per line
Quality factor0.8× (at 58% quality) — the last 20% of quality is most of the work
Size & shapeSmall · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

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

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — CQRS × a 0.8× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

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

1
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with QueryFactory.java, EntityQueryFactory.java, PostgreSQLSerialization.java.
+10.4 pts · Low effort · Knowledge Freshness
2
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).
+11.9 pts · Medium effort · Architecture documentation
3
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
+10.4 pts · Medium effort · Security & performance tooling

Diagnosis — what's actually going on

Value concentrated against a weak lens · Medium · Value at risk
This is a Small asset (~0.2 person-years to rebuild), and its weakest lens is Maturity at 46%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
Evidence: valuation: Small, ~0.2 person-years rebuild (14,811 LoC) · weakest lens: Maturity 46%
→ Direct remediation budget at Maturity 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: 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). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ 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).

Architecture — module dependency matrix

28 modules, 88 dependencies — 3 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.)

(global)…rcing.queries.optionsfoodsourcing.utils…sourcing.layout.types…m.eventsourcing.utils….eventsourcing.layoutcom.eventsourcing.hlc…m.eventsourcing.index…ourcing.layout.binary…ing.layout.comparable….eventsourcing.eventscom.eventsourcing…ntsourcing.cep.events…m.eventsourcing.inmem…ntsourcing.jmh.models…ing.migrations.events…ntsourcing.postgresql…eventsourcing.queries…ntsourcing.repository…g.repository.commandsfoodsourcing.events…ourcing.cep.protocolscom.eventsourcing.jmh…ntsourcing.migrations…cing.postgresql.indexfoodsourcing.protocolsfoodsourcingfoodsourcing.commands(global)1…rcing.queries.options2foodsourcing.utils3…sourcing.layout.types4…m.eventsourcing.utils5….eventsourcing.layout6com.eventsourcing.hlc7…m.eventsourcing.index8…ourcing.layout.binary9…ing.layout.comparable10….eventsourcing.events11com.eventsourcing12…ntsourcing.cep.events13…m.eventsourcing.inmem14…ntsourcing.jmh.models15…ing.migrations.events16…ntsourcing.postgresql17…eventsourcing.queries18…ntsourcing.repository19…g.repository.commands20foodsourcing.events21…ourcing.cep.protocols22com.eventsourcing.jmh23…ntsourcing.migrations24…cing.postgresql.index25foodsourcing.protocols26foodsourcing27foodsourcing.commands2822011618146630512412312133197114448113159112227111312024361612652771141110592821736131212121791141332212514321312

At a glance — Code Health · 83% · Strong

The Good
D1 · .NET / C# Cyclomatic Complexity 8.3 D3 · .NET / C# God Classes 9.4 D4 · .NET / C# Code Duplication 9.5
The Bad
D2 · .NET / C# Cognitive Complexity 6.1

At a glance — Architecture · 99% · Exemplary

The Good
D35 · .NET / C# Change Coupling 9.8 AX5 · Repo Architecture & structure 10.0

At a glance — Maturity · 46% · 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 M1 · Repo Documentation (README) 6.9 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 8.0
The Ugly
D34 · .NET / C# Knowledge Freshness 0.0 M2 · Repo Architecture documentation 0.0

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

The Good
D13 · .NET / C# Secret Scanning 10.0 P6 · Repo Release Hygiene 10.0
The Bad
P1 · Repo CI/CD gates 5.0
The Ugly
P3 · Repo Security & performance tooling 0.0

At a glance — Security · 89% · Exemplary

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

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2021 — Injection5Medium

Roadmap

Begin by establishing a central repository for architecture decisions and diagrams to capture significant design choices and their consequences. Next, address knowledge freshness by resolving the three largest orphaned files, specifically QueryFactory.java, EntityQueryFactory.java, and PostgreSQLSerialization.java. Implement a static application security testing step in the CI pipeline to fail the build on security regressions. Additionally, configure CI/CD to run the test suite and gate merges on passing tests. Finally, update the root README with a 'Testing' section to document how to run the test suite.

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

Do thisHelpsEffortDimension
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with QueryFactory.java, EntityQueryFactory.java, PostgreSQLSerialization.java.+10.4 ptsLowKnowledge Freshness
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).+11.9 ptsMediumArchitecture documentation
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+10.4 ptsMediumSecurity & performance tooling
Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.+10.4 ptsMediumCI/CD gates
Add a 'Testing' section to the root README — how to run the test suite.+8.8 ptsMediumDocumentation (README)
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness.+4.0 ptsLowKnowledge Freshness
Resolve the 1 The README itself is thin on installation and setup steps; readers must… finding(s) in Documentation Quality — start with README.md.+3.3 ptsLowDocumentation Quality
Reconcile the README with reality: README advertises a RAG / ML engine, but no ML/RAG code or dependency exists.+5.9 ptsMediumDocumentation accuracy

File quality

Per-file score 0–10 — a quality signature. Of 19 files carrying findings, judged against the Preview bar: 0% slop · 21% mixed · 79% near-clean.

FileScoreBandWorst signal
eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java4.9MixedStatic Analysis (SAST): Medium: use-of-sha1
eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java5.1MixedStatic Analysis (SAST): Medium: use-of-sha1
eventsourcing-layout/src/main/java/com/eventsourcing/layout/Layout.java6.4MixedStatic Analysis (SAST): Medium: use-of-sha1
eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLJournal.java6.4MixedStatic Analysis (SAST): Medium: formatted-sql-string
eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java7.2Near-cleanCognitive Complexity: PostgreSQLAttributeIndex.addAll (cognitive 19)
eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java7.4Near-cleanCode Duplication: Duplicated block (17 lines × 4)
eventsourcing-layout/src/main/java/com/eventsourcing/layout/TypeHandler.java7.8Near-cleanCyclomatic Complexity: TypeHandler.lookup (cyclomatic 30)
eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/OptionalBinarySerializer.java7.8Near-cleanCode Duplication: Duplicated block (8 lines × 2)
eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/MapBinarySerializer.java7.8Near-cleanCode Duplication: Duplicated block (7 lines × 2)
eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/EqualityIndex.java7.9Near-cleanStatic Analysis (SAST): Medium: use-of-sha1
eventsourcing-core/src/main/java/com/eventsourcing/Repository.java8.0Near-cleanChange Coupling: Boundary-crossing change coupling: Repository.java ↔ CommandConsumer.java
eventsourcing-core/src/main/java/com/eventsourcing/index/JavaStaticFieldIndexLoader.java8.5Near-cleanCognitive Complexity: JavaStaticFieldIndexLoader.load (cognitive 29)
examples/foodsourcing/src/main/java/foodsourcing/Address.java8.5Near-cleanCognitive Complexity: Address.<init> (cognitive 19)
eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/ByteArrayBinarySerializer.java8.5Near-cleanCode Duplication: Duplicated block (9 lines × 2)
eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/ListBinarySerializer.java8.5Near-cleanCode Duplication: Duplicated block (9 lines × 2)
src/jmh/java/com/eventsourcing/jmh/PostgreSQLJournalBenchmark.java8.5Near-cleanCode Duplication: Duplicated block (8 lines × 2)
eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/MapComparableSerializer.java8.5Near-cleanCode Duplication: Duplicated block (6 lines × 2)
eventsourcing-layout/src/main/java/com/eventsourcing/layout/types/ListTypeHandler.java8.5Near-cleanChange Coupling: Change coupling: ListTypeHandler.java ↔ OptionalTypeHandler.java
docs/README.md9.5Near-cleanDocumentation Quality: The README itself is thin on installation and setup steps; readers must navigate to getting_started/install.md to find how to add the dependency.

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

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

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 019fce99-ab57-7f76-95b7-5d336ba6ae75.

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

Run transparency — what happened this run

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

  • D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.

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.
  • 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").
  • 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.
  • 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.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

Dimensions

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

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

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

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

8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PostgreSQLSerialization.prepareValue at 42.

PostgreSQLSerialization.prepareValue (cyclomatic 42)eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:316
TypeHandler.lookup (cyclomatic 30)eventsourcing-layout/src/main/java/com/eventsourcing/layout/TypeHandler.java:80
PostgreSQLSerialization.getMappedType (cyclomatic 24)eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:90
PostgreSQLSerialization.setValue (cyclomatic 22)eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:414
PostgreSQLSerialization.getPropertyValue (cyclomatic 21)eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:504

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

What to do

  1. Resolve the 1 PostgreSQLSerialization.prepareValue (cyclomatic 42) finding(s) in Cyclomatic Complexity — start with PostgreSQLSerialization.java. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 TypeHandler.lookup (cyclomatic 30) finding(s) in Cyclomatic Complexity — start with TypeHandler.java. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 PostgreSQLSerialization.getMappedType (cyclomatic 24) finding(s) in Cyclomatic Complexity — start with PostgreSQLSerialization.java. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

12 method(s) exceeded the cognitive complexity threshold of 15; the worst was PostgreSQLSerialization.prepareValue at 240.

PostgreSQLSerialization.prepareValue (cognitive 240)eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:316
PostgreSQLSerialization.getPropertyValue (cognitive 55)eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:504
PostgreSQLSerialization.setValue (cognitive 40)eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:414
PostgreSQLSerialization.getMappedType (cognitive 30)eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:90
JavaStaticFieldIndexLoader.load (cognitive 29)eventsourcing-core/src/main/java/com/eventsourcing/index/JavaStaticFieldIndexLoader.java:35

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

What to do

  1. Resolve the 1 PostgreSQLSerialization.prepareValue (cognitive 240) finding(s) in Cognitive Complexity — start with PostgreSQLSerialization.java. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 PostgreSQLSerialization.getPropertyValue (cognitive 55) finding(s) in Cognitive Complexity — start with PostgreSQLSerialization.java. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 PostgreSQLSerialization.setValue (cognitive 40) finding(s) in Cognitive Complexity — start with PostgreSQLSerialization.java. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

2 god class(es) detected.

TooManyMethods: PostgreSQLAttributeIndexeventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:52
FileTooLong: postgresql/PostgreSQLSerialization.javaeventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:0

✓ On the Gold path — maintain.

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

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

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

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

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

17 duplicated block group(s) detected.

Duplicated block (7 lines × 2) · ×4eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/MapBinarySerializer.java:28
Duplicated block (8 lines × 2) · ×3eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/OptionalBinarySerializer.java:36
Duplicated block (9 lines × 2) · ×2eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/ByteArrayBinarySerializer.java:34
Duplicated block (6 lines × 2) · ×2eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/MapComparableSerializer.java:23
Duplicated block (5 lines × 2) · ×2eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java:341

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

✓ On the Gold path — maintain.

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

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.

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.

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

The READMEs are clear and complete for a Java eventsourcing library. The main document is an excellent rationale-driven overview that explains what ES4J addresses and lists key benefits (domain flexibility, late domain binding, causal persistence, serializable conflict resolution), plus links to Why Use Eventsourcing Database and a YouTube video on lazy event sourcing. A dedicated getting-started guide covers installation, overview, layout, commands, events, indexing, and publishing with runnable code examples for StandardRepository, including OSGi glueing and the RegisterRestaurant publish example. The architecture is well-documented via plantuml diagrams (command-entity relationships, repository boundaries) and a roadmap section.

The README itself is thin on installation and setup steps; readers must navigate to getting_started/install.md to find how to add the dependency.docs/README.md

What to do

  1. Resolve the 1 The README itself is thin on installation and setup steps; readers must… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).

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

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 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

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

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

Method: 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.

D29 · Static Analysis (SAST)7.7 / 10Strong✓ Tool-verified

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

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

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

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

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

Medium: use-of-sha1 · ×5eventsourcing-layout/src/main/java/com/eventsourcing/layout/Layout.java:135detected by semgrep finding

What to do

  1. Resolve the 5 Medium finding(s) in Static Analysis (SAST) — start with Layout.java, PostgreSQLJournal.java, PostgreSQLSerialization.java. — One of this dimension's main actionable groups (5 warning-level).

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

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

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

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

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

57 of 57 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is eventsourcing-core/src/main/java/com/eventsourcing/queries/QueryFactory.java.

Largest orphaned file · ×3eventsourcing-core/src/main/java/com/eventsourcing/queries/QueryFactory.java
Dormant codebase

What to do

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

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

D35 · Change Coupling9.8 / 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 9.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: ListTypeHandler.java↔OptionalTypeHandler.java 54%; Repository.java↔CommandConsumer.java 50%

Boundary-crossing change coupling: Repository.java ↔ CommandConsumer.javaeventsourcing-core/src/main/java/com/eventsourcing/Repository.java
Change coupling: ListTypeHandler.java ↔ OptionalTypeHandler.javaeventsourcing-layout/src/main/java/com/eventsourcing/layout/types/ListTypeHandler.java

✓ On the Gold path — maintain.

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

Frontend & cross-cutting dimensions

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

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.

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

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

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

What to do

  • Add a 'Testing' section to the root README — how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 9 of 10 project(s) that lack one — worth up to 1.8 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.

What to do

  • Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

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

What to do

  • Reconcile the README with reality: README advertises a RAG / ML engine, but no ML/RAG code or dependency exists.
P1 · CI/CD gates5.0 / 10Adequate✓ 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 but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
  • A CI pipeline exists but no build/compile step was matched — changes may merge without being compiled. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.

What to do

  • Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
  • Add an explicit build/compile step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is compiled before merge.
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 spotbugs with find-sec-bugs (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: spotbugs with find-sec-bugs — 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.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health83%StrongSolid.
Architecture99%ExemplaryStrongest area.
Maturity46%Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness50%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security89%ExemplarySolid.
Not included — 74 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.
  • AX1 Captive dependencies — no DI registrations detected
  • AX10 Code composition — not assessed — code composition is computed by ROLE over a document set that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX2 Stateful singletons — no singleton implementations detected
  • AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D10 Test Quality — ~5709 lines of test source are present (.java) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included
  • D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
  • D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (a Gradle version catalogue), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
  • D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
  • D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • 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 — Production source is present (.java, .kt) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. 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"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle version catalogue — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
  • D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • 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.
  • D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
  • D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .java, .kt, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • D9 Test Distribution — Test source is present (.java) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 31 value object(s); 10 domain event(s)
  • ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this check looks for (15 CQRS handler(s))
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
  • GD1 Unfinished & placeholder code — no source files
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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'.
  • P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
  • P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
  • P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) 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
  • PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
  • PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
  • PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository

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 — 1 finding(s)
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: Repository.java ↔ CommandConsumer.java eventsourcing-core/src/main/java/com/eventsourcing/Repository.java — `eventsourcing-core/src/main/java/com/eventsourcing/Repository.java` (context eventsourcing-core) and `eventsourcing-repository/src/main/java/com/eventsourcing/repository/CommandConsumer.java` (context eventsourcing-repository) sit in DIFFERENT parts of the tree yet change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Warning — 46 finding(s)
D29 · Static Analysis (SAST) · Medium · ×5
  • Medium: use-of-sha1 eventsourcing-layout/src/main/java/com/eventsourcing/layout/Layout.java:135 — Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Instead, use PBKDF2 for password hashing or SHA256 or SHA512 for other hash function applications. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
  • Medium: formatted-sql-string eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLJournal.java:389 — Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements (java.sql.PreparedStatement) instead. You can obtain a PreparedStatement using 'connection.prepareStatement'. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
  • Medium: use-of-sha1 eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:205 — Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Instead, use PBKDF2 for password hashing or SHA256 or SHA512 for other hash function applications. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
  • Medium: use-of-sha1 eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/EqualityIndex.java:82 — Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Instead, use PBKDF2 for password hashing or SHA256 or SHA512 for other hash function applications. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
  • Medium: use-of-sha1 eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:126 — Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Instead, use PBKDF2 for password hashing or SHA256 or SHA512 for other hash function applications. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×4
  • Duplicated block (7 lines × 2) eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/MapBinarySerializer.java:28 — eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/MapBinarySerializer.java:28-34 | eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/MapComparableSerializer.java:28-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/MapBinarySerializer.java:28` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/MapBinarySerializer.java:48 — eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/MapBinarySerializer.java:48-54 | eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/MapComparableSerializer.java:46-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/MapBinarySerializer.java:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/OptionalBinarySerializer.java:21 — eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/OptionalBinarySerializer.java:21-27 | eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/OptionalComparableSerializer.java:22-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:167 — eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:167-173 | eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:384-390 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/OptionalBinarySerializer.java:36 — eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/OptionalBinarySerializer.java:36-43 | eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/OptionalComparableSerializer.java:35-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/OptionalBinarySerializer.java:36` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:312 — eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:312-319 | eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:369-377 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:312` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/jmh/java/com/eventsourcing/jmh/PostgreSQLJournalBenchmark.java:22 — src/jmh/java/com/eventsourcing/jmh/PostgreSQLJournalBenchmark.java:22-29 | src/jmh/java/com/eventsourcing/jmh/PostgreSQLRepositoryBenchmark.java:27-34 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/ByteArrayBinarySerializer.java:34 — eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/ByteArrayBinarySerializer.java:34-42 | eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/ByteArrayComparableSerializer.java:33-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/ByteArrayBinarySerializer.java:34` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/ListBinarySerializer.java:23 — eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/ListBinarySerializer.java:23-31 | eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/ListComparableSerializer.java:24-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-layout/src/main/java/com/eventsourcing/layout/binary/ListBinarySerializer.java:23` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/MapComparableSerializer.java:23 — eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/MapComparableSerializer.java:23-28 | eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/MapComparableSerializer.java:41-46 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-layout/src/main/java/com/eventsourcing/layout/comparable/MapComparableSerializer.java:23` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:414 — eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:414-419 | eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:444-449 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:414` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • Duplicated block (5 lines × 2) eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java:341 — eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java:341-345 | eventsourcing-core/src/main/java/com/eventsourcing/queries/QueryFactory.java:320-324 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLJournal.java:274 — eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLJournal.java:274-278 | eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLJournal.java:287-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D1 · Cyclomatic Complexity · PostgreSQLSerialization.prepareValue (cyclomatic 42) · ×1
  • PostgreSQLSerialization.prepareValue (cyclomatic 42) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:316 — PostgreSQLSerialization.prepareValue has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TypeHandler.lookup (cyclomatic 30) · ×1
  • TypeHandler.lookup (cyclomatic 30) eventsourcing-layout/src/main/java/com/eventsourcing/layout/TypeHandler.java:80 — TypeHandler.lookup has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PostgreSQLSerialization.getMappedType (cyclomatic 24) · ×1
  • PostgreSQLSerialization.getMappedType (cyclomatic 24) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:90 — PostgreSQLSerialization.getMappedType has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PostgreSQLSerialization.setValue (cyclomatic 22) · ×1
  • PostgreSQLSerialization.setValue (cyclomatic 22) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:414 — PostgreSQLSerialization.setValue has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PostgreSQLSerialization.getPropertyValue (cyclomatic 21) · ×1
  • PostgreSQLSerialization.getPropertyValue (cyclomatic 21) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:504 — PostgreSQLSerialization.getPropertyValue has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PostgreSQLSerialization.getValue (cyclomatic 21) · ×1
  • PostgreSQLSerialization.getValue (cyclomatic 21) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:574 — PostgreSQLSerialization.getValue has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PostgreSQLSerialization.getMappedSqlType (cyclomatic 19) · ×1
  • PostgreSQLSerialization.getMappedSqlType (cyclomatic 19) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:260 — PostgreSQLSerialization.getMappedSqlType has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · NavigableIndex.retrieve (cyclomatic 16) · ×1
  • NavigableIndex.retrieve (cyclomatic 16) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:281 — NavigableIndex.retrieve has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D16 · Bus Factor · dormant codebase · ×1
  • dormant codebase — no living knowledge left to concentrate — Every one of the 57 significant source file(s) was last meaningfully changed so long ago that no living knowledge remains, so there is no concentration to measure — the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
D2 · Cognitive Complexity · PostgreSQLSerialization.prepareValue (cognitive 240) · ×1
  • PostgreSQLSerialization.prepareValue (cognitive 240) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:316 — PostgreSQLSerialization.prepareValue has cognitive complexity 240 (threshold 15). Drivers by points: ternaries 171, if/else 68, boolean chains 1 (nesting depth added 195). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgreSQLSerialization.getPropertyValue (cognitive 55) · ×1
  • PostgreSQLSerialization.getPropertyValue (cognitive 55) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:504 — PostgreSQLSerialization.getPropertyValue has cognitive complexity 55 (threshold 15). Drivers by points: if/else 33, loops 9, ternaries 8, boolean chains 5 (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgreSQLSerialization.setValue (cognitive 40) · ×1
  • PostgreSQLSerialization.setValue (cognitive 40) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:414 — PostgreSQLSerialization.setValue has cognitive complexity 40 (threshold 15). Drivers by points: if/else 36, ternaries 3, boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgreSQLSerialization.getMappedType (cognitive 30) · ×1
  • PostgreSQLSerialization.getMappedType (cognitive 30) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:90 — PostgreSQLSerialization.getMappedType has cognitive complexity 30 (threshold 15). Drivers by points: if/else 29, boolean chains 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · JavaStaticFieldIndexLoader.load (cognitive 29) · ×1
  • JavaStaticFieldIndexLoader.load (cognitive 29) eventsourcing-core/src/main/java/com/eventsourcing/index/JavaStaticFieldIndexLoader.java:35 — JavaStaticFieldIndexLoader.load has cognitive complexity 29 (threshold 15). Drivers by points: if/else 21, ternaries 4, loops 3, boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TypeHandler.lookup (cognitive 29) · ×1
  • TypeHandler.lookup (cognitive 29) eventsourcing-layout/src/main/java/com/eventsourcing/layout/TypeHandler.java:80 — TypeHandler.lookup has cognitive complexity 29 (threshold 15). Drivers by points: if/else 18, boolean chains 10, error handling 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · PostgreSQLSerialization.getValue (cognitive 26) · ×1
  • PostgreSQLSerialization.getValue (cognitive 26) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:574 — PostgreSQLSerialization.getValue has cognitive complexity 26 (threshold 15). Drivers by points: if/else 24, loops 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · NavigableIndex.retrieve (cognitive 23) · ×1
  • NavigableIndex.retrieve (cognitive 23) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:281 — NavigableIndex.retrieve has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11, ternaries 8, boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgreSQLAttributeIndex.addAll (cognitive 19) · ×1
  • PostgreSQLAttributeIndex.addAll (cognitive 19) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:209 — PostgreSQLAttributeIndex.addAll has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9, loops 6, error handling 2, boolean chains 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Address.<init> (cognitive 19) · ×1
  • Address.<init> (cognitive 19) examples/foodsourcing/src/main/java/foodsourcing/Address.java:64 — Address.<init> has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15, loops 3, boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgreSQLSerialization.getMappedSqlType (cognitive 18) · ×1
  • PostgreSQLSerialization.getMappedSqlType (cognitive 18) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:260 — PostgreSQLSerialization.getMappedSqlType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · Layout.deriveProperties (cognitive 16) · ×1
  • Layout.deriveProperties (cognitive 16) eventsourcing-layout/src/main/java/com/eventsourcing/layout/Layout.java:198 — Layout.deriveProperties has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 2, ternaries 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: PostgreSQLAttributeIndex eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:52 — TooManyMethods — 36 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.
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: postgresql/PostgreSQLSerialization.java eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:0 — FileTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: PostgreSQLSerialization (37-690). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: ListTypeHandler.java ↔ OptionalTypeHandler.java eventsourcing-layout/src/main/java/com/eventsourcing/layout/types/ListTypeHandler.java — `eventsourcing-layout/src/main/java/com/eventsourcing/layout/types/ListTypeHandler.java` and `eventsourcing-layout/src/main/java/com/eventsourcing/layout/types/OptionalTypeHandler.java` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
D4 · Code Duplication · Duplicated block (17 lines × 4) · ×1
  • Duplicated block (17 lines × 4) eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java:1007 — eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java:1007-1023 | eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java:1084-1100 | eventsourcing-core/src/main/java/com/eventsourcing/queries/QueryFactory.java:946-962 | eventsourcing-core/src/main/java/com/eventsourcing/queries/QueryFactory.java:1021-1037 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java:1007` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:123 — eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:123-136 | eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:160-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 5) · ×1
  • Duplicated block (11 lines × 5) eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:308 — eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:308-318 | eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:348-358 | eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/NavigableIndex.java:395-405 | eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:420-430 | eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:450-460 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/index/PostgreSQLAttributeIndex.java:450` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java:189 — eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java:189-198 | eventsourcing-core/src/main/java/com/eventsourcing/queries/QueryFactory.java:177-186 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java:189` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Recommendation — 7 finding(s)
D34 · Knowledge Freshness · Largest orphaned file · ×3
  • Largest orphaned file eventsourcing-core/src/main/java/com/eventsourcing/queries/QueryFactory.java — 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 eventsourcing-core/src/main/java/com/eventsourcing/index/EntityQueryFactory.java — 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 eventsourcing-postgresql/src/main/java/com/eventsourcing/postgresql/PostgreSQLSerialization.java — 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 reliability not included · ×1
  • Test reliability not included — Test source is present (.java) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D19 · Documentation Quality · The README itself is thin on installation and setup steps; readers must navigate to getting_started/install.md to find how to add the dependency. · ×1
  • The README itself is thin on installation and setup steps; readers must navigate to getting_started/install.md to find how to add the dependency. docs/README.md — Add a one-line 'Getting started' line in the top of the README pointing to docs/getting_started.
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 57 of 57 significant files have no living knowledge — the codebase as a whole is dormant, not 57 separate risks. Re-engage owners or document before change.
D8 · Code Coverage · Coverage not included · ×1
  • Coverage not included — suite not readable by the collector — Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored.
Info — 2 finding(s)
D12 · Dependency Hygiene · Dependency hygiene not measured · ×1
  • Dependency hygiene not measured — dependency manifest found but not parsed for hygiene — This repository's dependency manifest (a Gradle version catalogue) was found, but this pass cannot parse it for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D38 wherever the manifest is OSV-readable.
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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source .0artifacts/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 .5artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (no readable dependency manifest)—none (no readable dependency manifest): not present in this environment0—
D31 · IaC & Container Securitytrivy—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 Vulnerabilitiestrivy—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 & Signingprovenance—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 Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D38 · OSV Dependency Vulnerabilitiesosv-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 Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—

Run 019fce99-ab57-7f76-95b7-5d336ba6ae75 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 1 · Warnings: 46 · Recommendations: 7 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 04-08-2026 @ 21:06 UTC.

Downloadable artifacts

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

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