Public report — AxonFramework, published 4 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
145findings with an exact file:lineof 162 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
35/104dimensions across the health lenses196022 LoC — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
AxonIQ/AxonFramework is in good overall health (72%), but at least one category below sits in Adequate-or-worse territory — most items are improvements, and the weakest category contains work to schedule, not shelve.
It is strongest in Domain Modelling (100%) — the domain model is expressive and well-guarded. Event Sourcing (100%) is solid too.
The area that most needs attention is Security (63%) — exposure to security and compliance incidents is elevated.
Leadership focus, highest impact first: 23 High finding(s) (Static Analysis (SAST)); Keep a changelog (e.g. Keep-a-Changelog) recording what shipped… (Release Hygiene); 2 High finding(s) (Data Compliance (PII/GDPR)).
For scale: Large (~196,022 production lines); rebuilding it from scratch would take roughly ~5.8 person-years (~3–11 engineers). Approximate, ±~30%.
It builds on a genuinely strong Domain Modelling foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth 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.
1.0× (at 72% quality) — the last 20% of quality is most of the work
Size & shape
Large · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~5.8 person-years of build effort (about ~€840,000 to rebuild). Its weakest lens is Security at 63% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain High (×1.6) — CQRS, domain model, event sourcing × a 1.0× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 2 High finding(s) in Data Compliance (PII/GDPR) — start with DefaultComponentRegistry.java, SpringComponentRegistry.java.
Value concentrated against a weak lens · Medium · Value at risk
This is a Large asset (~5.8 person-years to rebuild), and its weakest lens is Security at 63%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ 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 23 High finding(s) in Static Analysis (SAST) — start with release-notes.yml (6), docs.yml (3), examples.yml (3). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Resolve the 23 High finding(s) in Static Analysis (SAST) — start with release-notes.yml (6), docs.yml (3), examples.yml (3).
Architecture — module dependency matrix
226 modules, 872 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.)
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
28
High / Critical
A04:2021 — Insecure Design
2
High / Critical
Roadmap
Begin by resolving the 23 high-priority static analysis findings, focusing first on release-notes.yml, docs.yml, and examples.yml. Next, address the two high-severity data compliance issues in DefaultComponentRegistry.java and SpringComponentRegistry.java. Then, update the ADR conformance by addressing the single non-compliant ADR in 0001-jackson-converter-jackson2-handling.md. Finally, ensure release hygiene by maintaining a changelog and add a testing section to the root README to clarify how to run the test suite.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 High finding(s) in Data Compliance (PII/GDPR) — start with DefaultComponentRegistry.java, SpringComponentRegistry.java.
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. 31 of 35 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 35 dimensions across the health lenses
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, 145 of 162 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
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
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.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
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.
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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 (5): D19, D20, D21, D25, 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.
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.
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CoordinationTask.run at 20. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SequencingPolicyEventMessageHandlingMember.parseParameter at 19 — they are counted neither in the figure above nor in this dimension's score.
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.
+ 15 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType… finding(s) in Cognitive Complexity — start with MigrateSnapshotTriggerDefinitionToAnnotation.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 1.removeGatewayFromConstructors (cognitive 36) finding(s) in Cognitive Complexity — start with MigrateCommandGatewayInEventHandler.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 AvroConverter.convert (cognitive 27) finding(s) in Cognitive Complexity — start with AvroConverter.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.8 / 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.
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.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
Of 1 mechanizable ADRs, 0 are prevented by analyzers, 1 by tests, 0 exist only in prose. Coverage: 100 %. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
Enforce Architectural Integrity in CI to reach Prevented (currently Verified). — Hardens enforcement from Verified toward Prevented — provenance only; does not change the score.
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.
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.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.4 / 10Strong✓ 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.
92 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java.
Off-boarding risk: anonymized user #1 · ×7
Further sole-owners (lower concentration)
What to do
Resolve the 7 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (7 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The Axon Framework project has strong documentation: an authoritative README with product links, a dedicated Migration guide covering top-level recipes, and a Documentation For Axon Framework folder listing Antora components (getting-started, identifier-generation-guide, message-handler-tunning-guide, meta-annotations-guide, reference-guide) plus contributing instructions. The README also references the repository-transferred note and SonarCloud status badges, giving it an extra organizational edge.
The 'Documentation For Axon Framework' section lists Antora components but does not mention how to build and preview them locally.docs/README.md
What to do
Resolve the 1 The 'Documentation For Axon Framework' section lists Antora components… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. 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.
What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.
ADR not followed: 1. JacksonConverter rejects Jackson 2 tree nodes (fail loud)decisions/0001-jackson-converter-jackson2-handling.md
What to do
Resolve the 1 ADR not followed finding(s) in ADR Conformance — start with 0001-jackson-converter-jackson2-handling.md. — One of this dimension's main actionable groups (1 issue-level).
Enforce ADR Conformance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d25_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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).
High: dependabot-missing-cooldown · ×23.github/dependabot.yml:4detected by semgrep finding
Medium: formatted-sql-string · ×5common/src/main/java/org/axonframework/common/jdbc/Oracle11Utils.java:47detected by semgrep finding
What to do
Resolve the 23 High finding(s) in Static Analysis (SAST) — start with release-notes.yml (6), docs.yml (3), examples.yml (3). — One of this dimension's main actionable groups (23 issue-level).
Resolve the 5 Medium finding(s) in Static Analysis (SAST) — start with FacultyInitializer.java (3), Oracle11Utils.java (2). — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)5.0 / 10Adequate✓ 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.
High: watchdog-sensitive-personal-data-in-log · ×2common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:413detected by semgrep finding
What to do
Resolve the 2 High finding(s) in Data Compliance (PII/GDPR) — start with DefaultComponentRegistry.java, SpringComponentRegistry.java. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
23 of 611 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/TimeoutProperties.java.
Further orphaned files (smaller)
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
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 PR-triggered workflow without a permissions block 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.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
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.
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.
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.
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.
Other · Event Sourcing — Whether Apply/When folds reconstruct state purely from the event (no DateTime.Now, Guid.NewGuid, Random or IO) so replay is reproducible.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether persisted events are immutable facts (init-only/readonly) — a settable event member lets stored history be rewritten.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Do you agree with this assessment?
ES3 · PII in the event store10.0 / 10Exemplary○ Nothing flagged
Other · Event Sourcing — Whether the append-only event log avoids un-erasable personal data (or has a crypto-shredding strategy) — a GDPR right-to-erasure risk.
Method: Roslyn (event-sourcing gated): high-confidence PII flagged Warning; ambiguous name-like fields adjudicated by language model as person versus fictional. Advisory without model, definitive with.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 32 of 37 project(s) that lack one — worth up to 1.7 pts.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README advertises a microservices architecture, but the repo is a single project with no service manifests
What to do
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests.
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
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Do you agree with this assessment?
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.
Not included — 69 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over a document set that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — vertical-slice architecture detected, but individual slices could not be resolved from namespaces or project layout
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 — ~189251 lines of test source are present (.java, .kt) 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.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.java, .kt) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
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.
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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .java, .kt, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.java, .kt) 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
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 10 event handler(s); 6 CQRS handler(s)
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
High: dependabot-missing-cooldown .github/dependabot.yml:4— This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown. 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. This configuration file has 4 such entries; one cooldown decision clears them all — reported once.
High: github-actions-mutable-action-tag .github/workflows/add-to-project.yml:14— 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/add-to-project@<40-character SHA>`. This step references `actions/add-to-project@main`; resolve the SHA it points at today with `gh api repos/actions/add-to-project/commits/main --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/dependabot-automation.yml:17— 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: dependabot/fetch-metadata@<40-character SHA>`. This step references `dependabot/fetch-metadata@v3`; resolve the SHA it points at today with `gh api repos/dependabot/fetch-metadata/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/dependabot-automation.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: dependabot/fetch-metadata@<40-character SHA>`. This step references `dependabot/fetch-metadata@v3`; resolve the SHA it points at today with `gh api repos/dependabot/fetch-metadata/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/docs.yml:25— 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@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/docs.yml:28— 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-node@<40-character SHA>`. This step references `actions/setup-node@v6`; resolve the SHA it points at today with `gh api repos/actions/setup-node/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/docs.yml:47— 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/github-script@<40-character SHA>`. This step references `actions/github-script@v9`; resolve the SHA it points at today with `gh api repos/actions/github-script/commits/v9 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/examples.yml:28— 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@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/examples.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: actions/setup-java@<40-character SHA>`. This step references `actions/setup-java@v5.5.0`; resolve the SHA it points at today with `gh api repos/actions/setup-java/commits/v5.5.0 --jq .sha`. Note that `v5.5.0` is an exact release tag rather than a floating major: it is still mutable (a tag can be repointed), but by convention it moves only on a force-push, so pin the floating-major and branch references in this file first.
High: github-actions-mutable-action-tag .github/workflows/examples.yml:58— 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: test-summary/action@<40-character SHA>`. This step references `test-summary/action@v2`; resolve the SHA it points at today with `gh api repos/test-summary/action/commits/v2 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/main.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: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/main.yml:34— 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@v5.5.0`; resolve the SHA it points at today with `gh api repos/actions/setup-java/commits/v5.5.0 --jq .sha`. Note that `v5.5.0` is an exact release tag rather than a floating major: it is still mutable (a tag can be repointed), but by convention it moves only on a force-push, so pin the floating-major and branch references in this file first.
High: github-actions-mutable-action-tag .github/workflows/main.yml:77— 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: rtCamp/action-slack-notify@<40-character SHA>`. This step references `rtCamp/action-slack-notify@v2`; resolve the SHA it points at today with `gh api repos/rtCamp/action-slack-notify/commits/v2 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pullrequest.yml:29— 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@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pullrequest.yml:32— 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@v5.5.0`; resolve the SHA it points at today with `gh api repos/actions/setup-java/commits/v5.5.0 --jq .sha`. Note that `v5.5.0` is an exact release tag rather than a floating major: it is still mutable (a tag can be repointed), but by convention it moves only on a force-push, so pin the floating-major and branch references in this file first.
High: github-actions-mutable-action-tag .github/workflows/pullrequest.yml:67— 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: test-summary/action@<40-character SHA>`. This step references `test-summary/action@v2`; resolve the SHA it points at today with `gh api repos/test-summary/action/commits/v2 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release-notes.yml:22— 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@v7`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v7 --jq .sha`.
High: run-shell-injection .github/workflows/release-notes.yml:33— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/workflows/release-notes.yml:44— 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/cache@<40-character SHA>`. This step references `actions/cache@v6`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release-notes.yml:51— 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/create-release@<40-character SHA>`. This step references `actions/create-release@v1`; resolve the SHA it points at today with `gh api repos/actions/create-release/commits/v1 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release-notes.yml:69— 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/cache@<40-character SHA>`. This step references `actions/cache@v6`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/release-notes.yml:76— 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: juliangruber/read-file-action@<40-character SHA>`. This step references `juliangruber/read-file-action@v1`; resolve the SHA it points at today with `gh api repos/juliangruber/read-file-action/commits/v1 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/slack-release-notification.yml:15— 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: slackapi/slack-github-action@<40-character SHA>`. This step references `slackapi/slack-github-action@v3.0.5`; resolve the SHA it points at today with `gh api repos/slackapi/slack-github-action/commits/v3.0.5 --jq .sha`. Note that `v3.0.5` is an exact release tag rather than a floating major: it is still mutable (a tag can be repointed), but by convention it moves only on a force-push, so pin the floating-major and branch references in this file first.
High: watchdog-sensitive-personal-data-in-log common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:413— 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 extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:271— 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.
ADR not followed: 1. JacksonConverter rejects Jackson 2 tree nodes (fail loud) decisions/0001-jackson-converter-jackson2-handling.md— The summary shows no JacksonConverter type, so it cannot reject Jackson 2 tree nodes as the ADR requires. (decisions/0001-jackson-converter-jackson2-handling.md)
Duplicated block (7 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java:353— eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java:353-359 | messaging/src/main/java/org/axonframework/messaging/core/annotation/MethodInvokingMessageHandlingMember.java:199-205 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java:353` 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.
Duplicated block (7 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/read/coursestats/CourseStatsConfiguration.java:20— examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/read/coursestats/CourseStatsConfiguration.java:20-26 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CourseStatsConfiguration.java:49-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/read/coursestats/CourseStatsConfiguration.java:20` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:94— examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:94-100 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:95-101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/UniversityAxonApplication.java:60— examples/university-demo/src/main/java/org/axonframework/examples/demo/university/UniversityAxonApplication.java:60-66 | examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/CourseCatalogApplication.java:72-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/UniversityAxonApplication.java:60` 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) examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/InteractiveShell.java:291— examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/InteractiveShell.java:291-297 | update/src/main/java/org/axonframework/update/api/UpdateCheckResponse.java:137-143 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/InteractiveShell.java:291` 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.
Duplicated block (7 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/annotation/AnnotatedCommandHandlingComponent.java:87— messaging/src/main/java/org/axonframework/messaging/commandhandling/annotation/AnnotatedCommandHandlingComponent.java:87-93 | messaging/src/main/java/org/axonframework/messaging/queryhandling/annotation/AnnotatedQueryHandlingComponent.java:88-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/commandhandling/annotation/AnnotatedCommandHandlingComponent.java:87` 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) messaging/src/main/java/org/axonframework/messaging/core/DelayedMessageStream.java:59— messaging/src/main/java/org/axonframework/messaging/core/DelayedMessageStream.java:59-65 | messaging/src/main/java/org/axonframework/messaging/core/DelayedMessageStream.java:90-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/core/DelayedMessageStream.java:59` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:533— messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:533-539 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:573-580 — 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.
Duplicated block (7 lines × 2) migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java:166— migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java:166-172 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:276-282 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:313— migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:313-319 | migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:323-329 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:313` 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) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:220— migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:220-227 | migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:135-141 — 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 `migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:220` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:231— migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:231-237 | migration/src/main/java/org/axonframework/migration/MigrateAggregateTestFixtureSetup.java:218-225 — 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 `migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:231` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:131— migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:131-137 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:166-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:373— migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:373-379 | migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:218-224 — 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 `migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:373` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:356— migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:356-362 | migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:432-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Change coupling: GetterEvolverChildEntityFieldDefinition.java ↔ GetterSetterChildEntityFieldDefinition.java modelling/src/main/java/org/axonframework/modelling/entity/child/GetterEvolverChildEntityFieldDefinition.java— `modelling/src/main/java/org/axonframework/modelling/entity/child/GetterEvolverChildEntityFieldDefinition.java` and `modelling/src/main/java/org/axonframework/modelling/entity/child/GetterSetterChildEntityFieldDefinition.java` change together 70% of the time (7 of the 10 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: FieldChildEntityFieldDefinition.java ↔ GetterEvolverChildEntityFieldDefinition.java modelling/src/main/java/org/axonframework/modelling/entity/child/FieldChildEntityFieldDefinition.java— `modelling/src/main/java/org/axonframework/modelling/entity/child/FieldChildEntityFieldDefinition.java` and `modelling/src/main/java/org/axonframework/modelling/entity/child/GetterEvolverChildEntityFieldDefinition.java` change together 70% of the time (7 of the 10 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: FieldChildEntityFieldDefinition.java ↔ GetterSetterChildEntityFieldDefinition.java modelling/src/main/java/org/axonframework/modelling/entity/child/FieldChildEntityFieldDefinition.java— `modelling/src/main/java/org/axonframework/modelling/entity/child/FieldChildEntityFieldDefinition.java` and `modelling/src/main/java/org/axonframework/modelling/entity/child/GetterSetterChildEntityFieldDefinition.java` change together 70% of the time (7 of the 10 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: DetectedVulnerabilitySeverity.java ↔ UpdateCheckRequest.java update/src/main/java/org/axonframework/update/api/DetectedVulnerabilitySeverity.java— `update/src/main/java/org/axonframework/update/api/DetectedVulnerabilitySeverity.java` and `update/src/main/java/org/axonframework/update/api/UpdateCheckRequest.java` change together 64% of the time (7 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: ArtifactAvailableUpgrade.java ↔ DetectedVulnerabilitySeverity.java update/src/main/java/org/axonframework/update/api/ArtifactAvailableUpgrade.java— `update/src/main/java/org/axonframework/update/api/ArtifactAvailableUpgrade.java` and `update/src/main/java/org/axonframework/update/api/DetectedVulnerabilitySeverity.java` change together 64% of the time (7 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: FailedMessageStream.java ↔ MappedMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/FailedMessageStream.java— `messaging/src/main/java/org/axonframework/messaging/core/FailedMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/core/MappedMessageStream.java` change together 60% of the time (15 of the 25 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: MappedMessageStream.java ↔ OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/MappedMessageStream.java— `messaging/src/main/java/org/axonframework/messaging/core/MappedMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/core/OnErrorContinueMessageStream.java` change together 60% of the time (15 of the 25 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: ConcatenatingMessageStream.java ↔ DelayedMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/ConcatenatingMessageStream.java— `messaging/src/main/java/org/axonframework/messaging/core/ConcatenatingMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/core/DelayedMessageStream.java` change together 60% of the time (15 of the 25 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: ConcatenatingMessageStream.java ↔ OnNextMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/ConcatenatingMessageStream.java— `messaging/src/main/java/org/axonframework/messaging/core/ConcatenatingMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/core/OnNextMessageStream.java` change together 60% of the time (12 of the 20 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: FailedMessageStream.java ↔ OnNextMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/FailedMessageStream.java— `messaging/src/main/java/org/axonframework/messaging/core/FailedMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/core/OnNextMessageStream.java` change together 60% of the time (12 of the 20 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.
Duplicated block (11 lines × 2) common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:71— common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:71-83 | common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:105-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:71` 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 (11 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:135— conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:135-145 | conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:109-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:135` 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.
Duplicated block (11 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AnnotationBasedTagResolver.java:92— eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AnnotationBasedTagResolver.java:92-102 | eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AnnotationBasedTagResolver.java:126-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AnnotationBasedTagResolver.java:92` 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.
Duplicated block (11 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:145— examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:145-155 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:166-176 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:145` 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.
Duplicated block (11 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java:53— examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java:53-65 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentToCourseController.java:53-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:119— extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:119-129 | extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MetricsConfigurationEnhancer.java:149-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:119` 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 (11 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:554— migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:554-564 | migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java:160-170 — 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 `migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:554` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:338— common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:338-347 | extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:511-520 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:338` 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 (10 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:115— examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:115-124 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:136-145 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:115` 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 (10 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:130— examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:130-139 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:151-160 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:130` 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 (10 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java:205— messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java:205-214 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java:243-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java:205` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringEventDispatchInterceptor.java:54— messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringEventDispatchInterceptor.java:54-63 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringSubscriptionQueryUpdateDispatchInterceptor.java:54-63 — 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 `messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringEventDispatchInterceptor.java:54` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:304— migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:304-313 | migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:372-383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:304` 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.
Duplicated block (10 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java:470— modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java:470-479 | modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java:491-500 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
TooManyMethods: PooledStreamingEventProcessorConfiguration messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorConfiguration.java:92— TooManyMethods — 45 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MessagingConfigurer messaging/src/main/java/org/axonframework/messaging/core/configuration/MessagingConfigurer.java:86— TooManyMethods — 35 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: JdbcTokenStore messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:63— TooManyMethods — 35 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ReflectionUtils common/src/main/java/org/axonframework/common/ReflectionUtils.java:56— TooManyMethods — 34 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ResourceOverridingProcessingContext messaging/src/main/java/org/axonframework/messaging/core/unitofwork/ResourceOverridingProcessingContext.java:41— TooManyMethods — 34 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PooledStreamingEventProcessor messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessor.java:90— TooManyMethods — 33 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.
Duplicated block (9 lines × 2) common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java:139— common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java:139-147 | common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java:174-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java:139` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:38— examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:38-46 | examples/university-java/src/main/java/org/axonframework/examples/university/ConfigurationProperties.java:54-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:38` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:73— examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:73-81 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:135-144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:73` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorModule.java:169— messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorModule.java:169-177 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/subscribing/SubscribingEventProcessorModule.java:122-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorModule.java:169` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:344— migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:344-352 | migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:193-201 — 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 `migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:344` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:507— migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:507-515 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:629-637 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:507` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:203— common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:203-210 | extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:225-232 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:203` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/CommandHandlingModule.java:217— messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/CommandHandlingModule.java:217-224 | messaging/src/main/java/org/axonframework/messaging/queryhandling/configuration/QueryHandlingModule.java:219-226 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/CommandHandlingModule.java:217` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventHandlingComponentsConfigurer.java:110— messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventHandlingComponentsConfigurer.java:110-117 | messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventHandlingComponentsConfigurer.java:133-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventHandlingComponentsConfigurer.java:110` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:234— messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:234-241 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java:205-212 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:234` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:400— messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:400-407 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:420-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:400` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:341— migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:341-348 | migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:394-401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:341` 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 (6 lines × 2) common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:58— common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:58-63 | common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:97-102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:58` 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.
Duplicated block (6 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/inmemory/InMemoryEventStorageEngine.java:297— eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/inmemory/InMemoryEventStorageEngine.java:297-302 | eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/inmemory/InMemoryEventStorageEngine.java:313-318 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:162— extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:162-167 | extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:176-181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/FlatMappedMessageStream.java:58— messaging/src/main/java/org/axonframework/messaging/core/FlatMappedMessageStream.java:58-63 | messaging/src/main/java/org/axonframework/messaging/core/MapMultiMessageStream.java:59-64 — 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.
Duplicated block (6 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/MergedMessageStream.java:76— messaging/src/main/java/org/axonframework/messaging/core/MergedMessageStream.java:76-81 | messaging/src/main/java/org/axonframework/messaging/core/MergedMessageStream.java:92-97 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/core/MergedMessageStream.java:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:136— migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:136-141 | migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java:93-98 — 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 `migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:136` 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.
Medium: formatted-sql-string common/src/main/java/org/axonframework/common/jdbc/Oracle11Utils.java:47— Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements (java.sql.PreparedStatement) instead. You can obtain a PreparedStatement using 'connection.prepareStatement'. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: formatted-sql-string common/src/main/java/org/axonframework/common/jdbc/Oracle11Utils.java:52— Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements (java.sql.PreparedStatement) instead. You can obtain a PreparedStatement using 'connection.prepareStatement'. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: weak-random examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/FacultyInitializer.java:115— Detected use of the functions `Math.random()` or `java.util.Random()`. These are both not cryptographically strong random number generators (RNGs). If you are using these RNGs to create passwords or secret tokens, use `java.security.SecureRandom` instead. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
Medium: weak-random examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/FacultyInitializer.java:115— Detected use of the functions `Math.random()` or `java.util.Random()`. These are both not cryptographically strong random number generators (RNGs). If you are using these RNGs to create passwords or secret tokens, use `java.security.SecureRandom` instead. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
Medium: weak-random examples/university-java/src/main/java/org/axonframework/examples/university/FacultyInitializer.java:88— Detected use of the functions `Math.random()` or `java.util.Random()`. These are both not cryptographically strong random number generators (RNGs). If you are using these RNGs to create passwords or secret tokens, use `java.security.SecureRandom` instead. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
Duplicated block (12 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:21— examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:21-32 | examples/university-java/src/main/java/org/axonframework/examples/university/ConfigurationProperties.java:37-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:48— examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:48-59 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java:63-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/interception/annotation/MessageHandlerInterceptorDefinition.java:106— messaging/src/main/java/org/axonframework/messaging/core/interception/annotation/MessageHandlerInterceptorDefinition.java:106-117 | messaging/src/main/java/org/axonframework/messaging/core/interception/annotation/MessageHandlerInterceptorDefinition.java:176-187 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/core/interception/annotation/MessageHandlerInterceptorDefinition.java:106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessor.java:455— messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessor.java:455-466 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/subscribing/SubscribingEventProcessor.java:212-223 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessor.java:455` 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 (12 lines × 2) migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:160— migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:160-187 | migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToStaticMethod.java:113-124 — 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 `migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:160` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Hotspot: messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java— messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java changed 16 times in last 90 days, max complexity 20. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java— migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java changed 3 times in last 90 days, max complexity 18. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: messaging/src/main/java/org/axonframework/messaging/eventhandling/annotation/MethodSequencingPolicyEventHandlerDefinition.java messaging/src/main/java/org/axonframework/messaging/eventhandling/annotation/MethodSequencingPolicyEventHandlerDefinition.java— messaging/src/main/java/org/axonframework/messaging/eventhandling/annotation/MethodSequencingPolicyEventHandlerDefinition.java changed 2 times in last 90 days, max complexity 19. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java— migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java changed 2 times in last 90 days, max complexity 17. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Duplicated block (5 lines × 2) common/src/main/java/org/axonframework/common/ReflectionUtils.java:388— common/src/main/java/org/axonframework/common/ReflectionUtils.java:388-392 | common/src/main/java/org/axonframework/common/ReflectionUtils.java:404-408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:97— conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:97-101 | conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:81-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:237— eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:237-241 | modelling/src/main/java/org/axonframework/modelling/configuration/SimpleStateBasedEntityModule.java:187-192 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:237` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:724— migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:724-728 | migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:749-753 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:724` 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.
FileTooLong: pooled/Coordinator.java messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:0— FileTooLong — 853 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: Coordinator (87-1487). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: migration/MigrateCommandGatewayInEventHandler.java migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:0— FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: MigrateCommandGatewayInEventHandler (69-836). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Duplicated block (13 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:405— common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:405-417 | extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:263-276 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:405` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:111— conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:111-123 | conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:95-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/segmenting/AddedTrackerStatus.java:44— messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/segmenting/AddedTrackerStatus.java:44-54 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/segmenting/RemovedTrackerStatus.java:44-54 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/segmenting/TrackerStatus.java:261-271 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringCommandHandlerInterceptor.java:56— messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringCommandHandlerInterceptor.java:56-66 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringEventHandlerInterceptor.java:54-64 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringQueryHandlerInterceptor.java:56-66 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
CoordinationTask.run (cyclomatic 20) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:765— CoordinationTask.run has cyclomatic complexity 20 (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.
1.visitMethodInvocation (cyclomatic 18) migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java:91— 1.visitMethodInvocation has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
1.removeGatewayFromConstructors (cyclomatic 17) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:760— 1.removeGatewayFromConstructors has cyclomatic complexity 17 (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.
MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType (cyclomatic 17) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:367— MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType has cyclomatic complexity 17 (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.
AvroConverter.convert (cyclomatic 16) conversion/src/main/java/org/axonframework/conversion/avro/AvroConverter.java:123— AvroConverter.convert has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType (cognitive 37) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:367— MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType has cognitive complexity 37 (threshold 15). Drivers by points: if/else 32, boolean chains 4, loops 1 (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.
1.removeGatewayFromConstructors (cognitive 36) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:760— 1.removeGatewayFromConstructors has cognitive complexity 36 (threshold 15). Drivers by points: if/else 21, loops 6, ternaries 5, boolean chains 4 (nesting depth added 20). 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.
AvroConverter.convert (cognitive 27) conversion/src/main/java/org/axonframework/conversion/avro/AvroConverter.java:123— AvroConverter.convert has cognitive complexity 27 (threshold 15). Drivers by points: if/else 26, boolean chains 1 (nesting depth added 8). 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.
AddCommandAnnotation.hasRoutingKeyAttribute (cognitive 27) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:338— AddCommandAnnotation.hasRoutingKeyAttribute has cognitive complexity 27 (threshold 15). Drivers by points: if/else 22, loops 3, boolean chains 2 (nesting depth added 15). 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.
AddEventAnnotation.findRevisionValue (cognitive 27) migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java:176— AddEventAnnotation.findRevisionValue has cognitive complexity 27 (threshold 15). Drivers by points: if/else 23, boolean chains 3, loops 1 (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.
CoordinationTask.run (cognitive 26) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:765— CoordinationTask.run has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18, ternaries 4, boolean chains 3, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
JacksonConverter.convert (cognitive 25) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:107— JacksonConverter.convert has cognitive complexity 25 (threshold 15). Drivers by points: if/else 24, error handling 1 (nesting depth added 11). 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.
12330.classFields (cognitive 25) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:582— 12330.classFields has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16, loops 8, boolean chains 1 (nesting depth added 15). 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.
Jackson2Converter.convert (cognitive 24) conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:91— Jackson2Converter.convert has cognitive complexity 24 (threshold 15). Drivers by points: if/else 23, error handling 1 (nesting depth added 11). 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.
12330.resolveIndent (cognitive 23) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:509— 12330.resolveIndent has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17, loops 4, boolean chains 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.
AddCommandAnnotation.findFieldName (cognitive 22) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:309— AddCommandAnnotation.findFieldName has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16, loops 4, 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.
6947.visitClassDeclaration (cognitive 21) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:157— 6947.visitClassDeclaration has cognitive complexity 21 (threshold 15). Drivers by points: if/else 18, boolean chains 2, loops 1 (nesting depth added 8). 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.
MigrateSnapshotTriggerDefinitionToAnnotation.isSnapshotTriggerDefinitionMethod (cognitive 21) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:287— MigrateSnapshotTriggerDefinitionToAnnotation.isSnapshotTriggerDefinitionMethod has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16, boolean chains 3, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SpringUtils.isQualifierMatch (cognitive 20) extensions/spring/spring/src/main/java/org/axonframework/extension/spring/SpringUtils.java:63— SpringUtils.isQualifierMatch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16, boolean chains 3, error handling 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.
6861.visitAnnotation (cognitive 20) migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:148— 6861.visitAnnotation has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13, ternaries 7 (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.
CoordinationTask.coordinateWorkPackages (cognitive 18) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:1268— CoordinationTask.coordinateWorkPackages has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, loops 4, boolean chains 1 (nesting depth added 8). 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.
AnnotationBasedEventSourcedEntityFactory.addEntityCreatorExecutable (cognitive 17) eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java:178— AnnotationBasedEventSourcedEntityFactory.addEntityCreatorExecutable has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15, boolean chains 1, loops 1 (nesting depth added 8). 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.
1.visitNewClass (cognitive 17) migration/src/main/java/org/axonframework/migration/MigrateAggregateTestFixtureSetup.java:105— 1.visitNewClass has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 9, if/else 7, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CoordinationTask.coordinateEvents (cognitive 16) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:924— CoordinationTask.coordinateEvents has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, boolean chains 2, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
1.extractClassLiteralType (cognitive 16) migration/src/main/java/org/axonframework/migration/MigrateAggregateTestFixtureSetup.java:186— 1.extractClassLiteralType has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 21 floating ref(s) across 8 workflow file(s), 1 of them mutable BRANCH refs — pin those first. Each floating ref is itemized at file:line by the SAST (D29) lens.
D36 · Supply-chain Provenance & Signing· PR-triggered workflow without a permissions block · ×1
PR-triggered workflow without a permissions block — 4 workflow(s) triggered by pull_request declare no `permissions:` block (pullrequest.yml, examples.yml, docs.yml …) and so run with the repository's default GITHUB_TOKEN scope, while 1 sibling workflow in the same repository is already scoped. Pull-request runs build the least-trusted code in the repository; give each of these workflows its own least-privilege block — `permissions: {contents: read}` at the top of the workflow, widened per job only where a job genuinely writes.
Duplicated block (10 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/CommandHandlingModule.java:249— messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/CommandHandlingModule.java:249-259 | messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventHandlingComponentsConfigurer.java:194-203 | messaging/src/main/java/org/axonframework/messaging/queryhandling/configuration/QueryHandlingModule.java:251-261 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/CommandHandlingModule.java:249` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 6) messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandMessage.java:156— messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandMessage.java:156-164 | messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandResultMessage.java:126-134 | messaging/src/main/java/org/axonframework/messaging/core/GenericResultMessage.java:113-121 | messaging/src/main/java/org/axonframework/messaging/eventhandling/GenericEventMessage.java:174-182 | messaging/src/main/java/org/axonframework/messaging/queryhandling/GenericQueryMessage.java:109-117 | messaging/src/main/java/org/axonframework/messaging/queryhandling/GenericQueryResponseMessage.java:134-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
Duplicated block (8 lines × 3) extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/DefaultReactorCommandGateway.java:137— extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/DefaultReactorCommandGateway.java:137-144 | extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/eventhandling/gateway/DefaultReactorEventGateway.java:131-138 | extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/queryhandling/gateway/DefaultReactorQueryGateway.java:144-151 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/DefaultReactorCommandGateway.java:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:291— migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:291-301 | migration/src/main/java/org/axonframework/migration/MigrateMessageInterceptorSignatures.java:361-367 | migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:562-568 — 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.
Duplicated block (19 lines × 2) extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:74— extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:74-92 | messaging/src/main/java/org/axonframework/messaging/core/interception/DefaultHandlerInterceptorRegistry.java:67-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:74` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/SimpleCommandHandlingModule.java:112— messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/SimpleCommandHandlingModule.java:112-136 | messaging/src/main/java/org/axonframework/messaging/queryhandling/configuration/SimpleQueryHandlingModule.java:107-131 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 24 significant file(s) lose their only recent owner: migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java, migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java, migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java, migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java, migration/src/main/java/org/axonframework/migration/MigrateMessageInterceptorSignatures.java, migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java, migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java, migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java (+16 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 29 significant file(s) lose their only recent owner: messaging/src/main/java/org/axonframework/messaging/core/configuration/MessagingConfigurer.java, eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/jpa/AggregateBasedJpaEventStorageEngineConfiguration.java, messaging/src/main/java/org/axonframework/messaging/core/interception/DispatchInterceptorRegistry.java, messaging/src/main/java/org/axonframework/messaging/monitoring/configuration/MessageMonitorRegistry.java, messaging/src/main/java/org/axonframework/messaging/monitoring/configuration/DefaultMessageMonitorRegistry.java, extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MetricsConfigurationEnhancer.java, extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java, conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java (+21 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 8 significant file(s) lose their only recent owner: common/src/main/java/org/axonframework/common/configuration/ComponentRegistry.java, messaging/src/main/java/org/axonframework/messaging/core/timeout/UnitOfWorkTimeoutInterceptorBuilder.java, eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/StorageEngineBackedEventStore.java, eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/jpa/JpaPollingEventCoordinator.java, eventsourcing/src/main/java/org/axonframework/eventsourcing/handler/InitializingEntityEvolver.java, messaging/src/main/java/org/axonframework/messaging/core/ConcatenatingMessageStream.java, eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/EventCoordinator.java, eventsourcing/src/main/java/org/axonframework/eventsourcing/snapshot/api/Snapshot.java. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 8 significant file(s) lose their only recent owner: messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/SimpleCommandHandlingModule.java, messaging/src/main/java/org/axonframework/messaging/queryhandling/configuration/SimpleQueryHandlingModule.java, messaging/src/main/java/org/axonframework/messaging/core/annotation/MessageStreamResolverUtils.java, messaging/src/main/java/org/axonframework/messaging/commandhandling/annotation/Command.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/annotation/Event.java, messaging/src/main/java/org/axonframework/messaging/queryhandling/annotation/QueryResponse.java, messaging/src/main/java/org/axonframework/messaging/commandhandling/CommandHandlingExceptionHandler.java, messaging/src/main/java/org/axonframework/messaging/queryhandling/annotation/Query.java. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 7 significant file(s) lose their only recent owner: extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/DefaultReactorCommandGateway.java, extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/queryhandling/gateway/DefaultReactorQueryGateway.java, extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/queryhandling/gateway/ReactorQueryGateway.java, extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/eventhandling/gateway/DefaultReactorEventGateway.java, extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/ReactorAutoConfiguration.java, extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/ReactorCommandGateway.java, extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/eventhandling/gateway/ReactorEventGateway.java. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 6 significant file(s) lose their only recent owner: messaging/src/main/java/org/axonframework/messaging/queryhandling/QueryUpdateEmitter.java, messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/CommandSequencingInterceptor.java, common/src/main/java/org/axonframework/common/TypeReference.java, messaging/src/main/java/org/axonframework/messaging/core/sequencing/FallbackSequencingPolicy.java, messaging/src/main/java/org/axonframework/messaging/core/sequencing/ExtractionSequencingPolicy.java, messaging/src/main/java/org/axonframework/messaging/core/sequencing/HierarchicalSequencingPolicy.java. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #7 — If anonymized user #7 becomes unavailable, 5 significant file(s) lose their only recent owner: messaging/src/main/java/org/axonframework/messaging/eventstreaming/EventCriteria.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java, common/src/main/java/org/axonframework/common/ProcessUtils.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/ClaimTask.java. Pair on, review, or document these before any departure.
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.java, .kt) 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.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (92 single-owned of 611 analysed files in total, counted over production source files of roughly 100 lines or more, excluding tests, vendored, generated and example/demo trees, largest first). They are anonymized user #8 (3 file(s)), anonymized user #9 (1 file(s)), anonymized user #10 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.
D19 · Documentation Quality· The 'Documentation For Axon Framework' section lists Antora components but does not mention how to build and preview them locally. · ×1
The 'Documentation For Axon Framework' section lists Antora components but does not mention how to build and preview them locally. docs/README.md— Add a brief Build & Preview guide pointing readers to the Antora docs site or the local antora.sh command.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 23 of 611 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 100 lines or more, excluding tests, vendored, generated and example/demo trees, largest first). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — largest first: extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/TimeoutProperties.java, extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/ReactorDispatchInterceptorRegistry.java, extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java (and 20 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
Coverage not included — suite not readable by the collector — Coverage NOT MEASURED: test source is present (.java, .kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — `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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
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.
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.
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.
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 019fce79-981b-7281-91f9-9a5992d44629 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 26 · Warnings: 120 · Recommendations: 14 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 04-08-2026 @ 20:31 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.