cp-ddd-framework — Watchdog Audit

Executive summary

Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.

funkygao/cp-ddd-framework is sound in substance but carries real gaps (57%). 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 (97%) — the structure is clean and changes stay contained. Code Health (90%) is solid too.

The area that most needs attention is Security (38%) — exposure to security and compliance incidents is elevated. Maturity (70%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.

Leadership focus, highest impact first: 6 High finding(s) (Data Compliance (PII/GDPR)); 11 High finding(s) (Static Analysis (SAST)); build/run (quick start) section to the root README (Documentation (README)).

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

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

Code Health 90% ★ Exemplary Architecture 97% ★ Exemplary Maturity 70% Adequate · gated by D34 Readiness 73% Strong Security 38% Weak · gated by D29, D32, D36 Domain Modelling 74% Strong

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

Security 38% · 46% weightMaturity 70% · 25% weightReadiness 73% · 14% weightDomain Modelling 74% · 8% weightCode Health 90% · 4% weightArchitecture 97% · 2% weight

Raise Security 38 → 70 (the Healthy floor) ⇒ headline 57 → ~72.

Code composition — where the lines go

Tests 100%

New since the last scan (6+)

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

D32 · High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/JarUtils.java
D32 · High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/JarUtils.java
D32 · High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/PluginClassLoader.java
D32 · High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/PluginClassLoader.java
D32 · High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/PluginClassLoader.java
D32 · High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/PluginClassLoader.java

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

Rebuild cost & value ~ Modeled — €10,000–€52,000

Cost to rebuild	€10,000–€52,000 (0.1–0.3 person-years (173–547 h), ~1 engineer)
Domain complexity	High — harder problems cost more per line
Quality factor	0.8× (at 57% quality) — the last 20% of quality is most of the work
Size & shape	Small · 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 ~€31,000 to rebuild). Its weakest lens is Security at 38% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain High (×1.4) — DDD/clean architecture, domain model × 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.

Resolve the 6 High finding(s) in Data Compliance (PII/GDPR) — start with PluginClassLoader.java (4), JarUtils.java (2).

+10.1 pts · Low effort · Data Compliance (PII/GDPR)

Resolve the 11 High finding(s) in Static Analysis (SAST) — start with codeql-analysis.yml (5), maven.yml (4), maven-publish.yml (2).

+9.8 pts · Medium effort · Static Analysis (SAST)

Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing.

+2.2 pts · Low effort · Supply-chain Provenance & Signing

Diagnosis — what's actually going on

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

This is a Small asset (~0.2 person-years to rebuild), and its weakest lens is Security at 38%. 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 (12,429 LoC) · weakest lens: Security 38%

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

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Resolve the 6 High finding(s) in Data Compliance (PII/GDPR) — start with PluginClassLoader.java (4), JarUtils.java (2). The rest can wait behind it.

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

→ Resolve the 6 High finding(s) in Data Compliance (PII/GDPR) — start with PluginClassLoader.java (4), JarUtils.java (2).

Architecture — module dependency matrix

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

At a glance — Code Health · 90% · Exemplary

The Good

D1 · .NET / C# Cyclomatic Complexity 9.0 D2 · .NET / C# Cognitive Complexity 7.6 D3 · .NET / C# God Classes 9.7 D4 · .NET / C# Code Duplication 9.8

At a glance — Architecture · 97% · Exemplary

The Good

D35 · .NET / C# Change Coupling 9.5 AX5 · Repo Architecture & structure 10.0

At a glance — Maturity · 70% · Adequate · gated by D34

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D16 · .NET / C# Bus Factor 10.0 D21 · .NET / C# Naming Consistency 10.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

M1 · Repo Documentation (README) 6.7 M2 · Repo Architecture documentation 5.0

The Ugly

D34 · .NET / C# Knowledge Freshness 0.3

At a glance — Readiness · 73% · Strong

The Good

D13 · .NET / C# Secret Scanning 10.0 P1 · Repo CI/CD gates 10.0 P4 · Repo Deployment & Rollback 7.0 P6 · Repo Release Hygiene 10.0

The Ugly

P3 · Repo Security & performance tooling 4.0

At a glance — Security · 38% · Weak · gated by D29, D32, D36

The Good

D28 · .NET / C# Secrets (history) 10.0

The Ugly

D29 · .NET / C# Static Analysis (SAST) 1.5 D32 · .NET / C# Data Compliance (PII/GDPR) 1.2 D36 · .NET / C# Supply-chain Provenance & Signing 2.5

At a glance — Domain Modelling · 74% · Strong

The Good

DM5 · Repo Encapsulated state 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM8 · Repo Value-object opportunities 10.0

The Bad

DM1 · Repo Aggregate boundaries 5.8 DM4 · Repo Rich vs anemic model 6.2

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A03:2021 — Injection	11	High / Critical
A04:2021 — Insecure Design	6	High / Critical

Roadmap

Begin by resolving the six high-severity data compliance issues, specifically in PluginClassLoader.java and JarUtils.java, to address PII and GDPR risks. Next, eliminate the eleven high-severity static analysis findings, prioritizing codeql-analysis.yml, maven.yml, and maven-publish.yml. To improve onboarding, add a build and run quick-start section to the root README. Subsequently, establish architecture decision records in a dedicated docs/adr/ directory to document significant design choices. Finally, address the single high-severity finding related to supply-chain provenance and signing.

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

Do this	Helps	Effort	Dimension
Resolve the 6 High finding(s) in Data Compliance (PII/GDPR) — start with PluginClassLoader.java (4), JarUtils.java (2).	+10.1 pts	Low	Data Compliance (PII/GDPR)
Resolve the 11 High finding(s) in Static Analysis (SAST) — start with codeql-analysis.yml (5), maven.yml (4), maven-publish.yml (2).	+9.8 pts	Medium	Static Analysis (SAST)
Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing.	+2.2 pts	Low	Supply-chain Provenance & Signing
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing.	+2.2 pts	Low	Supply-chain Provenance & Signing
Resolve the 1 Workflow token permissions not restricted finding(s) in Supply-chain Provenance & Signing.	+2.2 pts	Low	Supply-chain Provenance & Signing
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness.	+1.9 pts	Low	Knowledge Freshness
Resolve the 1 Largest orphaned file finding(s) in Knowledge Freshness — start with PlantUmlRenderer.java.	+1.9 pts	Low	Knowledge Freshness
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.	+2.6 pts	Medium	Documentation (README)

File quality

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

File	Score	Band	Worst signal
.github/workflows/codeql-analysis.yml	4.6	Mixed	Static Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/maven.yml	4.8	Mixed	Static Analysis (SAST): High: gha-workflow-env-secret
dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/PluginClassLoader.java	4.8	Mixed	Data Compliance (PII/GDPR): High: watchdog-sensitive-personal-data-in-log
.github/workflows/maven-publish.yml	5.8	Mixed	Static Analysis (SAST): High: github-actions-mutable-action-tag
dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/JarUtils.java	5.8	Mixed	Data Compliance (PII/GDPR): High: watchdog-sensitive-personal-data-in-log
dddplus-visualization/src/main/java/io/github/dddplus/ast/DomainModelAnalyzer.java	6.3	Mixed	Cyclomatic Complexity: DomainModelAnalyzer.analyze (cyclomatic 28)
dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyBehavior.java	6.5	Mixed	Change Coupling: Boundary-crossing change coupling: KeyBehavior.java ↔ KeyFlowAnnotationParser.java
dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyFlowAnnotationParser.java	7.0	Mixed	Code Duplication: Duplicated block (12 lines × 2)
dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyFlow.java	7.0	Mixed	Change Coupling: Boundary-crossing change coupling: KeyFlow.java ↔ KeyFlowAnnotationParser.java
dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.java	7.4	Mixed	Cyclomatic Complexity: PlantUmlRenderer.writeClazzDefinition (cyclomatic 20)
dddplus-visualization/src/main/java/io/github/dddplus/ast/ClassMethodDistributionAstNodeVisitor.java	7.8	Mixed	Cyclomatic Complexity: ClassMethodDistributionAstNodeVisitor.visit (cyclomatic 23)
dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyElementAnnotationParser.java	7.8	Mixed	Cyclomatic Complexity: KeyElementAnnotationParser.parse (cyclomatic 18)
dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlainTextRenderer.java	8.5	Near-clean	Cognitive Complexity: PlainTextRenderer.writeClazzDefinition (cognitive 35)
dddplus-runtime/src/main/java/io/github/dddplus/runtime/registry/DomainArtifacts.java	8.5	Near-clean	Cognitive Complexity: DomainArtifacts.export (cognitive 29)
dddplus-runtime/src/main/java/io/github/dddplus/runtime/registry/InternalIndexer.java	8.5	Near-clean	Cognitive Complexity: InternalIndexer.findEffectiveExtensions (cognitive 26)
dddplus-runtime/src/main/java/io/github/dddplus/runtime/StepsExecTemplate.java	8.5	Near-clean	Cognitive Complexity: StepsExecTemplate.executeSteps (cognitive 21)
dddplus-visualization/src/main/java/io/github/dddplus/ast/algorithm/KMeans.java	8.5	Near-clean	Cognitive Complexity: KMeans.cluster (cognitive 20)
dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/Plugin.java	8.5	Near-clean	Cognitive Complexity: Plugin.preparePlugins (cognitive 19)
dddplus-visualization/src/main/java/io/github/dddplus/ast/enforcer/ExtensionMethodSignatureEnforcer.java	8.5	Near-clean	Cognitive Complexity: ExtensionMethodSignatureEnforcer.enforce (cognitive 18)
dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/AggregateAnnotationParser.java	8.5	Near-clean	Cognitive Complexity: AggregateAnnotationParser.parse (cognitive 17)

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. 27 of 28 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 1 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 28 dimensions across the health lenses

D1D2D3D4D13D15D16D21D28D29D32D34D35D36AX5DM1DM4DM5DM6DM8M1M2M3M4P1P3P4P6

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

How to trust any code-health report — three questions

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 019fce80-322c-707d-baa8-96c2afb647b0.

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.

D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
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.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
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").
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
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.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (2): 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 Complexity9.0 / 10Exemplary✓ Tool-verified

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

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

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

4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DomainModelAnalyzer.analyze at 28.

DomainModelAnalyzer.analyze (cyclomatic 28)dddplus-visualization/src/main/java/io/github/dddplus/ast/DomainModelAnalyzer.java:86

ClassMethodDistributionAstNodeVisitor.visit (cyclomatic 23)dddplus-visualization/src/main/java/io/github/dddplus/ast/ClassMethodDistributionAstNodeVisitor.java:58

PlantUmlRenderer.writeClazzDefinition (cyclomatic 20)dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.java:250

KeyElementAnnotationParser.parse (cyclomatic 18)dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyElementAnnotationParser.java:55

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D2 · Cognitive Complexity7.6 / 10Strong✓ 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 7.6 / 10 · rule-coverage 100% · ceiling Prevented

14 method(s) exceeded the cognitive complexity threshold of 15; the worst was DomainModelAnalyzer.analyze at 50.

DomainModelAnalyzer.analyze (cognitive 50)dddplus-visualization/src/main/java/io/github/dddplus/ast/DomainModelAnalyzer.java:86

PlantUmlRenderer.writeClazzDefinition (cognitive 36)dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.java:250

PlainTextRenderer.writeClazzDefinition (cognitive 35)dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlainTextRenderer.java:119

KeyElementAnnotationParser.parse (cognitive 32)dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyElementAnnotationParser.java:55

DomainArtifacts.export (cognitive 29)dddplus-runtime/src/main/java/io/github/dddplus/runtime/registry/DomainArtifacts.java:50

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

What to do

Resolve the 1 DomainModelAnalyzer.analyze (cognitive 50) finding(s) in Cognitive Complexity — start with DomainModelAnalyzer.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PlantUmlRenderer.writeClazzDefinition (cognitive 36) finding(s) in Cognitive Complexity — start with PlantUmlRenderer.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PlainTextRenderer.writeClazzDefinition (cognitive 35) finding(s) in Cognitive Complexity — start with PlainTextRenderer.java. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes9.7 / 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.7 / 10 · rule-coverage 100% · ceiling Prevented

1 god class(es) detected.

TooManyMethods: PlantUmlRendererdddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.java:26

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

6 duplicated block group(s) detected.

Duplicated block (7 lines × 2) · ×2dddplus-runtime/src/main/java/io/github/dddplus/runtime/registry/PartnerDef.java:62

Duplicated block (12 lines × 3)dddplus-visualization/src/main/java/io/github/dddplus/ast/KeyBehaviorAstNodeVisitor.java:36

Duplicated block (12 lines × 2)dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyFlowAnnotationParser.java:42

Duplicated block (11 lines × 2)dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyBehaviorAnnotationParser.java:42

Duplicated block (6 lines × 2)dddplus-maven-plugin/src/main/java/io/github/dddplus/maven/ClassHierarchyMojo.java:48

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D16 · Bus Factor10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

No source file's living knowledge is concentrated in a single author.

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md.

Do you agree with this assessment?

D21 · Naming Consistency / 10Exemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

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

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

Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)1.5 / 10Critical✓ 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 1.5 / 10 · rule-coverage 100% · ceiling Documented

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

High: github-actions-mutable-action-tag · ×11.github/workflows/codeql-analysis.yml:33detected by semgrep finding

What to do

Resolve the 11 High finding(s) in Static Analysis (SAST) — start with codeql-analysis.yml (5), maven.yml (4), maven-publish.yml (2). — One of this dimension's main actionable groups (11 issue-level).

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

Do you agree with this assessment?

D32 · Data Compliance (PII/GDPR)1.2 / 10Critical✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR pattern scan via semgrep across the repo, using Watchdog's own ruleset (personal data reaching log/console sinks, URLs and query strings, or unprotected browser storage); matches map to severity and a 0-10 wide normalizer. NotApplicable when the scan runs and detects no PII/GDPR surface (no unearned 10); reported LOUDLY as a measurement gap, never as not-applicable, if the ruleset is missing from the analyzer image. Exhaustive, advisory-leaning; degrades on parse failure.

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

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

High: watchdog-sensitive-personal-data-in-log · ×6dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/JarUtils.java:27detected by semgrep finding

What to do

Resolve the 6 High finding(s) in Data Compliance (PII/GDPR) — start with PluginClassLoader.java (4), JarUtils.java (2). — One of this dimension's main actionable groups (6 issue-level).

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

Do you agree with this assessment?

D34 · Knowledge Freshness0.3 / 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.3 / 10 · rule-coverage 100% · ceiling Documented

67 of 69 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.java.

Dormant codebase

Largest orphaned filedddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.java

What to do

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

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

Do you agree with this assessment?

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

Strongest change-coupling: KeyBehavior.java↔KeyFlow.java 73%; KeyFlowAnnotationParser.java↔PlantUmlRenderer.java 67%; KeyFlow.java↔KeyFlowAnnotationParser.java 67%

Boundary-crossing change coupling: KeyFlow.java ↔ KeyFlowAnnotationParser.java · ×3dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyFlow.java

Change coupling: KeyBehavior.java ↔ KeyFlow.java · ×3dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyBehavior.java

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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

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

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

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

Unpinned build actions

Workflow token permissions not restricted

No build provenance

No SBOM

What to do

Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Workflow token permissions not restricted finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

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

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

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

Do you agree with this assessment?

DM1 · Aggregate boundaries5.8 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

`CheckTask` references the aggregate root `ShipmentOrder` directly (via `shipmentOrders`) — hold its `ShipmentOrderId` instead.

What to do

Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.

Do you agree with this assessment?

DM4 · Rich vs anemic model6.2 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

`Student` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — BaseAggregateRootTest.java:63
`Book` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×2) — ListBagTest.java:39, SetBagTest.java:40
`CheckTask` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — CheckTask.java:27
`ShipmentOrder` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — ShipmentOrder.java:17
`ContainerDiff` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — ContainerDiff.java:15

What to do

Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.

Do you agree with this assessment?

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state (private/init-only setters) instead of exposing public setters that bypass invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): public setters on entities detected; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

Do you agree with this assessment?

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

Do you agree with this assessment?

DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

Do you agree with this assessment?

M1 · Documentation (README)6.7 / 10Adequate✓ 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 build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add a README to the 8 of 8 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

What to do

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

Do you agree with this assessment?

P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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

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

Do you agree with this assessment?

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.

Do you agree with this assessment?

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	90%	Exemplary	Solid.
Architecture	97%	Exemplary	Strongest area.
Maturity	70%	Adequate — gated by D34	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	73%	Strong	Solid.
Security	38%	Weak — gated by D29, D32, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	74%	Strong	Solid.

Not included — 73 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 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
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 — ~9941 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 Maven POM), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
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.
D19 Documentation Quality — LLM evaluation failed
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) 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 Maven POM — 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.
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.
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 — Scanner failed to run — not a clean result
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, 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.
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this check looks for (1 event handler(s))
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this check looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
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 — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
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.
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 — `mvn jacoco:report`) 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 — 20 finding(s)

D29 · Static Analysis (SAST) · High · ×11

High: github-actions-mutable-action-tag .github/workflows/codeql-analysis.yml:33 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v2`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v2 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/codeql-analysis.yml:37 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: github/codeql-action/init@<40-character SHA>`. This step references `github/codeql-action/init@v1`; resolve the SHA it points at today with `gh api repos/github/codeql-action/commits/v1 --jq .sha`. `github/codeql-action/init` is hosted INSIDE the `github/codeql-action` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `github/codeql-action/init` path in `uses:` and query only `github/codeql-action`.
High: github-actions-mutable-action-tag .github/workflows/codeql-analysis.yml:46 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-java@<40-character SHA>`. This step references `actions/setup-java@v2`; resolve the SHA it points at today with `gh api repos/actions/setup-java/commits/v2 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/codeql-analysis.yml:54 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: github/codeql-action/autobuild@<40-character SHA>`. This step references `github/codeql-action/autobuild@v1`; resolve the SHA it points at today with `gh api repos/github/codeql-action/commits/v1 --jq .sha`. `github/codeql-action/autobuild` is hosted INSIDE the `github/codeql-action` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `github/codeql-action/autobuild` path in `uses:` and query only `github/codeql-action`.
High: github-actions-mutable-action-tag .github/workflows/codeql-analysis.yml:68 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: github/codeql-action/analyze@<40-character SHA>`. This step references `github/codeql-action/analyze@v1`; resolve the SHA it points at today with `gh api repos/github/codeql-action/commits/v1 --jq .sha`. `github/codeql-action/analyze` is hosted INSIDE the `github/codeql-action` repository (a subdirectory action or a reusable workflow), so the SHA to pin is that repository's commit — keep the full `github/codeql-action/analyze` path in `uses:` and query only `github/codeql-action`.
High: github-actions-mutable-action-tag .github/workflows/maven-publish.yml:16 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v2`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v2 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/maven-publish.yml:18 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-java@<40-character SHA>`. This step references `actions/setup-java@v1`; resolve the SHA it points at today with `gh api repos/actions/setup-java/commits/v1 --jq .sha`.
High: gha-workflow-env-secret .github/workflows/maven.yml:13 — A secret is exposed in the workflow-level `env:` block, making it available to every job and step in this workflow — including any untrusted code run in pull-request workflows. Scope secrets as narrowly as possible: prefer step-level `env:` so the secret is only available where it is actually needed. This is a semgrep security-AUDIT rule reporting a POLICY that is absent or weaker than its recommendation, not an exploitable defect. Confirm whether the current setting is a deliberate decision for this repository — and apply the change where it is not; where it is (a policy your release process already enforces elsewhere, or one this repository has consciously opted out of), record the decision and leave the configuration as it is.
High: github-actions-mutable-action-tag .github/workflows/maven.yml:21 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v2`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v2 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/maven.yml:23 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-java@<40-character SHA>`. This step references `actions/setup-java@v1`; resolve the SHA it points at today with `gh api repos/actions/setup-java/commits/v1 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/maven.yml:31 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: codecov/codecov-action@<40-character SHA>`. This step references `codecov/codecov-action@v1`; resolve the SHA it points at today with `gh api repos/codecov/codecov-action/commits/v1 --jq .sha`.

D32 · Data Compliance (PII/GDPR) · High · ×6

High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/JarUtils.java:27 — Special-category or directly-identifying personal data appears to be written to a log or console sink. Logs are copied, shipped to third parties and retained far longer than the data itself is lawfully needed. Log a stable pseudonymous reference instead of the value.
High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/JarUtils.java:38 — Special-category or directly-identifying personal data appears to be written to a log or console sink. Logs are copied, shipped to third parties and retained far longer than the data itself is lawfully needed. Log a stable pseudonymous reference instead of the value.
High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/PluginClassLoader.java:65 — Special-category or directly-identifying personal data appears to be written to a log or console sink. Logs are copied, shipped to third parties and retained far longer than the data itself is lawfully needed. Log a stable pseudonymous reference instead of the value.
High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/PluginClassLoader.java:75 — Special-category or directly-identifying personal data appears to be written to a log or console sink. Logs are copied, shipped to third parties and retained far longer than the data itself is lawfully needed. Log a stable pseudonymous reference instead of the value.
High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/PluginClassLoader.java:85 — Special-category or directly-identifying personal data appears to be written to a log or console sink. Logs are copied, shipped to third parties and retained far longer than the data itself is lawfully needed. Log a stable pseudonymous reference instead of the value.
High: watchdog-sensitive-personal-data-in-log dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/PluginClassLoader.java:97 — Special-category or directly-identifying personal data appears to be written to a log or console sink. Logs are copied, shipped to third parties and retained far longer than the data itself is lawfully needed. Log a stable pseudonymous reference instead of the value.

D35 · Change Coupling · Boundary-crossing change coupling · ×3

Boundary-crossing change coupling: KeyFlow.java ↔ KeyFlowAnnotationParser.java dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyFlow.java — `dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyFlow.java` (context dddplus-spec) and `dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyFlowAnnotationParser.java` (context dddplus-visualization) sit in DIFFERENT parts of the tree yet change together 67% of the time (8 of the 12 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.
Boundary-crossing change coupling: KeyBehavior.java ↔ KeyFlowAnnotationParser.java dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyBehavior.java — `dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyBehavior.java` (context dddplus-spec) and `dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyFlowAnnotationParser.java` (context dddplus-visualization) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 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.
Boundary-crossing change coupling: KeyFlow.java ↔ KeyFlowEntry.java dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyFlow.java — `dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyFlow.java` (context dddplus-spec) and `dddplus-visualization/src/main/java/io/github/dddplus/ast/model/KeyFlowEntry.java` (context dddplus-visualization) sit in DIFFERENT parts of the tree yet 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) — 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 — 31 finding(s)

D35 · Change Coupling · Change coupling · ×3

Change coupling: KeyBehavior.java ↔ KeyFlow.java dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyBehavior.java — `dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyBehavior.java` and `dddplus-spec/src/main/java/io/github/dddplus/dsl/KeyFlow.java` change together 73% of the time (8 of the 11 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.
Change coupling: KeyFlowAnnotationParser.java ↔ PlantUmlRenderer.java dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyFlowAnnotationParser.java — `dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyFlowAnnotationParser.java` and `dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.java` change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking.
Change coupling: DomainModelAnalyzer.java ↔ KeyModelReport.java dddplus-visualization/src/main/java/io/github/dddplus/ast/DomainModelAnalyzer.java — `dddplus-visualization/src/main/java/io/github/dddplus/ast/DomainModelAnalyzer.java` and `dddplus-visualization/src/main/java/io/github/dddplus/ast/report/KeyModelReport.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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking.

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

Duplicated block (7 lines × 2) dddplus-runtime/src/main/java/io/github/dddplus/runtime/registry/PartnerDef.java:62 — dddplus-runtime/src/main/java/io/github/dddplus/runtime/registry/PartnerDef.java:62-68 | dddplus-runtime/src/main/java/io/github/dddplus/runtime/registry/PatternDef.java:77-83 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `dddplus-runtime/src/main/java/io/github/dddplus/runtime/registry/PartnerDef.java:62` 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) dddplus-visualization/src/main/java/io/github/dddplus/ast/KeyElementAstNodeVisitor.java:53 — dddplus-visualization/src/main/java/io/github/dddplus/ast/KeyElementAstNodeVisitor.java:53-59 | dddplus-visualization/src/main/java/io/github/dddplus/ast/KeyElementAstNodeVisitor.java:101-107 — 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.

D1 · Cyclomatic Complexity · DomainModelAnalyzer.analyze (cyclomatic 28) · ×1

DomainModelAnalyzer.analyze (cyclomatic 28) dddplus-visualization/src/main/java/io/github/dddplus/ast/DomainModelAnalyzer.java:86 — DomainModelAnalyzer.analyze has cyclomatic complexity 28 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · ClassMethodDistributionAstNodeVisitor.visit (cyclomatic 23) · ×1

ClassMethodDistributionAstNodeVisitor.visit (cyclomatic 23) dddplus-visualization/src/main/java/io/github/dddplus/ast/ClassMethodDistributionAstNodeVisitor.java:58 — ClassMethodDistributionAstNodeVisitor.visit has cyclomatic complexity 23 (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 · PlantUmlRenderer.writeClazzDefinition (cyclomatic 20) · ×1

PlantUmlRenderer.writeClazzDefinition (cyclomatic 20) dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.java:250 — PlantUmlRenderer.writeClazzDefinition has cyclomatic complexity 20 (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 · KeyElementAnnotationParser.parse (cyclomatic 18) · ×1

KeyElementAnnotationParser.parse (cyclomatic 18) dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyElementAnnotationParser.java:55 — KeyElementAnnotationParser.parse has cyclomatic complexity 18 (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.

D19 · Documentation Quality · LLM evaluation failed · ×1

LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[1].docPath | LineNumber: 0 | BytePositionInLine: 1188.

D2 · Cognitive Complexity · DomainModelAnalyzer.analyze (cognitive 50) · ×1

DomainModelAnalyzer.analyze (cognitive 50) dddplus-visualization/src/main/java/io/github/dddplus/ast/DomainModelAnalyzer.java:86 — DomainModelAnalyzer.analyze has cognitive complexity 50 (threshold 15). Drivers by points: loops 26, if/else 24 (nesting depth added 23). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · PlantUmlRenderer.writeClazzDefinition (cognitive 36) · ×1

PlantUmlRenderer.writeClazzDefinition (cognitive 36) dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.java:250 — PlantUmlRenderer.writeClazzDefinition has cognitive complexity 36 (threshold 15). Drivers by points: if/else 27, loops 8, boolean chains 1 (nesting depth added 14). 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 · PlainTextRenderer.writeClazzDefinition (cognitive 35) · ×1

PlainTextRenderer.writeClazzDefinition (cognitive 35) dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlainTextRenderer.java:119 — PlainTextRenderer.writeClazzDefinition has cognitive complexity 35 (threshold 15). Drivers by points: if/else 21, loops 14 (nesting depth added 21). 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 · KeyElementAnnotationParser.parse (cognitive 32) · ×1

KeyElementAnnotationParser.parse (cognitive 32) dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyElementAnnotationParser.java:55 — KeyElementAnnotationParser.parse has cognitive complexity 32 (threshold 15). Drivers by points: if/else 20, loops 7, match/switch 3, boolean chains 2 (nesting depth added 16). 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 · DomainArtifacts.export (cognitive 29) · ×1

DomainArtifacts.export (cognitive 29) dddplus-runtime/src/main/java/io/github/dddplus/runtime/registry/DomainArtifacts.java:50 — DomainArtifacts.export has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15, loops 14 (nesting depth added 16). 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 · InternalIndexer.findEffectiveExtensions (cognitive 26) · ×1

InternalIndexer.findEffectiveExtensions (cognitive 26) dddplus-runtime/src/main/java/io/github/dddplus/runtime/registry/InternalIndexer.java:118 — InternalIndexer.findEffectiveExtensions has cognitive complexity 26 (threshold 15). Drivers by points: if/else 21, loops 3, boolean chains 2 (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 · ClassMethodDistributionAstNodeVisitor.visit (cognitive 24) · ×1

ClassMethodDistributionAstNodeVisitor.visit (cognitive 24) dddplus-visualization/src/main/java/io/github/dddplus/ast/ClassMethodDistributionAstNodeVisitor.java:58 — ClassMethodDistributionAstNodeVisitor.visit has cognitive complexity 24 (threshold 15). Drivers by points: if/else 21, loops 2, boolean chains 1 (nesting depth added 2). 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.

D2 · Cognitive Complexity · StepsExecTemplate.executeSteps (cognitive 21) · ×1

StepsExecTemplate.executeSteps (cognitive 21) dddplus-runtime/src/main/java/io/github/dddplus/runtime/StepsExecTemplate.java:106 — StepsExecTemplate.executeSteps has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16, boolean chains 3, error handling 1, loops 1 (nesting depth added 7). 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 · KMeans.cluster (cognitive 20) · ×1

KMeans.cluster (cognitive 20) dddplus-visualization/src/main/java/io/github/dddplus/ast/algorithm/KMeans.java:37 — KMeans.cluster has cognitive complexity 20 (threshold 15). Drivers by points: loops 11, if/else 9 (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · Plugin.preparePlugins (cognitive 19) · ×1

Plugin.preparePlugins (cognitive 19) dddplus-plugin/src/main/java/io/github/dddplus/runtime/registry/Plugin.java:125 — Plugin.preparePlugins has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12, loops 4, boolean chains 3 (nesting depth added 7). 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 · ExtensionMethodSignatureEnforcer.enforce (cognitive 18) · ×1

ExtensionMethodSignatureEnforcer.enforce (cognitive 18) dddplus-visualization/src/main/java/io/github/dddplus/ast/enforcer/ExtensionMethodSignatureEnforcer.java:37 — ExtensionMethodSignatureEnforcer.enforce has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10, loops 7, boolean chains 1 (nesting depth added 10). 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 · AggregateAnnotationParser.parse (cognitive 17) · ×1

AggregateAnnotationParser.parse (cognitive 17) dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/AggregateAnnotationParser.java:25 — AggregateAnnotationParser.parse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, loops 5, match/switch 2 (nesting depth added 10). 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 · BasePattern.match (cognitive 16) · ×1

BasePattern.match (cognitive 16) dddplus-runtime/src/main/java/io/github/dddplus/runtime/BasePattern.java:56 — BasePattern.match has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, error handling 4 (nesting depth added 5). 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 · KeyRuleAstNodeVisitor.visit (cognitive 16) · ×1

KeyRuleAstNodeVisitor.visit (cognitive 16) dddplus-visualization/src/main/java/io/github/dddplus/ast/KeyRuleAstNodeVisitor.java:38 — KeyRuleAstNodeVisitor.visit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, boolean chains 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: PlantUmlRenderer dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.java:26 — 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.

D36 · Supply-chain Provenance & Signing · Unpinned build actions · ×1

Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 10 floating ref(s) across 3 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.

D36 · Supply-chain Provenance & Signing · Workflow token permissions not restricted · ×1

Workflow token permissions not restricted — No workflow declares a `permissions:` block, so every job runs with the repository's default GITHUB_TOKEN scope (3 workflow file(s) checked). On a repository whose default is read/write, a compromised action or a malicious pull request inherits write access to code, issues, releases and packages. Declare a least-privilege `permissions:` block — `permissions: {contents: read}` at the top of each workflow, widened per job only where a job genuinely writes.

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

Duplicated block (12 lines × 3) dddplus-visualization/src/main/java/io/github/dddplus/ast/KeyBehaviorAstNodeVisitor.java:36 — dddplus-visualization/src/main/java/io/github/dddplus/ast/KeyBehaviorAstNodeVisitor.java:36-47 | dddplus-visualization/src/main/java/io/github/dddplus/ast/KeyRuleAstNodeVisitor.java:69-80 | dddplus-visualization/src/main/java/io/github/dddplus/ast/KeyUsecaseAstNodeVisitor.java:36-47 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `dddplus-visualization/src/main/java/io/github/dddplus/ast/KeyBehaviorAstNodeVisitor.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.

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

Duplicated block (12 lines × 2) dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyFlowAnnotationParser.java:42 — dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyFlowAnnotationParser.java:42-54 | dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyRuleAnnotationParser.java:38-49 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyFlowAnnotationParser.java:42` 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.

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

Duplicated block (11 lines × 2) dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyBehaviorAnnotationParser.java:42 — dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyBehaviorAnnotationParser.java:42-53 | dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyUsecaseAnnotationParser.java:36-46 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `dddplus-visualization/src/main/java/io/github/dddplus/ast/parser/KeyBehaviorAnnotationParser.java:42` 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. 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 (6 lines × 2) · ×1

Duplicated block (6 lines × 2) dddplus-maven-plugin/src/main/java/io/github/dddplus/maven/ClassHierarchyMojo.java:48 — dddplus-maven-plugin/src/main/java/io/github/dddplus/maven/ClassHierarchyMojo.java:48-53 | dddplus-maven-plugin/src/main/java/io/github/dddplus/maven/ModelingVisualizationMojo.java:52-57 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `dddplus-maven-plugin/src/main/java/io/github/dddplus/maven/ClassHierarchyMojo.java:48` 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.

Recommendation — 7 finding(s)

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.

D34 · Knowledge Freshness · Dormant codebase · ×1

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

D34 · Knowledge Freshness · Largest orphaned file · ×1

Largest orphaned file dddplus-visualization/src/main/java/io/github/dddplus/ast/view/PlantUmlRenderer.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.

D36 · Supply-chain Provenance & Signing · No build provenance · ×1

No build provenance — No SLSA provenance generation or build attestation found in CI — nothing binds a released artifact to the build that produced it, so a consumer cannot tell your artifact from a substituted one. Your release already signs its artifacts, so this is the remaining step rather than a new pipeline: attestation records HOW the artifact was built, which a signature over the finished file does not. On GitHub Actions, `actions/attest-build-provenance` (or slsa-github-generator) emits one from the job's own OIDC identity; elsewhere, run `cosign attest` over the released artifact from the release pipeline and publish the attestation beside it.

D36 · Supply-chain Provenance & Signing · No SBOM · ×1

No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (the `cyclonedx-maven-plugin` bound to the package phase, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Publish it as a release asset (`*.spdx.json` / `*.cdx.json`) so consumers can see what they are installing.

D38 · OSV Dependency Vulnerabilities · Scanner failed to run · ×1

Scanner failed to run — not a clean result — osv-scanner exited 128 with no findings — the advisory database was likely unreachable. The scanner exited non-zero and produced no findings (typically the advisory DB was unreachable), so this is reported as a measurement gap rather than a clean pass.

D8 · Code Coverage · Coverage not included · ×1

Coverage not included — suite not readable by the collector — Coverage NOT READ here — but this repository measures it: a Codecov configuration (codecov.yml) and a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.java), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) 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 Maven POM) 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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --json --quiet --timeout 0 --metrics off .	11	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	none (no readable dependency manifest)	—	none (no readable dependency manifest): not present in this environment	0	—
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 0 --metrics off .	6	artifacts/raw/semgrep-gdpr.json
D33 · JS/npm Dependency Vulnerabilities	trivy	—	trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D38 · OSV Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive .	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—

Run 019fce80-322c-707d-baa8-96c2afb647b0 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Funkygao/cp-Ddd-Framework

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency matrix

At a glance — Code Health · 90% · Exemplary

At a glance — Architecture · 97% · Exemplary

At a glance — Maturity · 70% · Adequate · gated by D34

At a glance — Readiness · 73% · Strong

At a glance — Security · 38% · Weak · gated by D29, D32, D36

At a glance — Domain Modelling · 74% · Strong

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts